For testing purposes it is often necessary to restart the services in order to collect data or when troubleshooting. This is done by ensuring there is no entry on the ‘LastScheduledActionCompleted’ registry key and then restarting the Data Collector ...
Zum Testen oder Troubleshooting der verschiedenen Connectors im Data Collector ist es notwendig den Registry Eintrag ‘LastScheduledActionCompleted’ zu löschen und den Data Collector Service neu zu starten. Diese zwei Aktionen können mit einem Doppelk...
Zum Konfigurieren des Microsoft-Intune-Connector wird die Microsoft Graph API verwendet. Diese Berechtigung kann man in App registration in Microsoft Azure finden und anfordern. Hier wählt man die Berechtigung DeviceManagementManagedDevices.Read.All...
Dieser Artikel beschreibt das Erstellen und Gewähren von Azure Berechtigungen Im Spider Data Collector Ordner (DC\Microsoft-Azure-Connector) befinden sich die folgenden Connector PowerShell Scripts: Microsoft-AzureAD-Connector, Microsoft-AzureAD-Get...
This article describes the API permissions that must be setup in Azure for the following connectors: 'Microsoft-AzureAD-Connector', 'Microsoft-AzureAD-GetGroups' and 'Microsoft-AzureAD-GetUsers'. The above mentioned connectors all use the 'Windows A...
This article describes the API permissions that must be setup in Azure for the following connector: 'Microsoft-Intune-Connector'. The 'Microsoft-Intune-Connector connector uses the 'Microsoft Graph' API. Permissions for this can be viewed and reques...
Scenario Customer builds a new Data Collector Server, as a result a new Data Collector Unique ID (GUID) is created in its registry, thereafter the Data Collector Server is no longer synchronising with the Spider Application Server. Technical Backgro...
Symptoms: Remnants of Inactive and obsolete Spider Data Collectors visible in Spider Web UI Info and Settings. Diagnosis: Findings of Data Collectors with "Inactive" or "Last contact more than four hours ago". Despite the Server being obsolete, ei...
