Confirm that the MECM hardware inventory is properly set up MECM needs to be set up properly for vScope to be able to view the latest patch dates. Enable the following values under ‘Hardware Invento...
Category Archives : Troubleshooting RSS feed for this section
vScope shows incorrect values for password attributes in Active Directory
If your domain uses Fine-Grained Password Policies (FGPP) it is possible that the service account used as a credential for the Active Directory doesn’t have sufficient permissions to read Passwo...
Missing Primary User values for Clients in vScope
vScope retrieves the information about clients from the MCEM (SCCM) SQL database. If information about your devices is missing in vScope, you need to troubleshoot to see if vScope has read access to t...
How to reduce long Discovery times
Long discovery times is most likely caused by a faulty Discovery Manager setup. Before we start to optimize the discovery time, we first need to understand how a discovery is performed. How the discov...
Common MECM (SCCM) errors for vScope discoveries
“SYSTEM NOT SUPPORTED” The first thing vScope checks for in the MECM (SCCM) database is the Sites table. If it does not find one vScope will show “SYSTEM NOT SUPPORTED” and abo...
Last logon from Active Directory is incorrect
Follow these troubleshooting steps if the last logon in vScope doesn’t match the one in the AD. Troubleshooting Ensure that vScope inventories all DC:s Compare to value found in script: Get-ADUs...
Azure Security Center – Suspicious command line: powershell -exec bypass -encodedcommand
Azure Security Center can report about the command line “powershell -exec bypass -encodedcommand” being used during vScope discoveries. The command “-exec bypass” makes it poss...
Wrong/missing patch date for machines in vScope
You might sometimes experience that Windows Patch Date tag does not show the same value as shown on the server. This is most likely due to an error in WMI on the target computer. In general, start off...
Common email server errors
java.net.SocketTimeoutException: The email server is not responding as expected. This is known to be caused by either of the following: Exchange servers have Message Throttling – A significant ...
How to confirm WMI access through DCOM and WinRM
Ways to access WMI vScope accesses WMI on a target machine in two ways. DCOM (the default way) Executes queries remotely High Round-trip time (RTT) between vScope and target machine times affects scan...