ACC discovery error unexpected token at ''DescriptionDiscovery of a server via Agent Client Collector fails with error unexpected token at ''. Example error: C:/Program Files/ServiceNow/agent-client-collector/embedded/lib/ruby/gems/2.7.0/gems/json-2.3.0/lib/json/common.rb:156:in `parse': 783: unexpected token at '' (JSON::ParserError)\r\n\tfrom C:/Program Files/ServiceNow/agent-client-collector/embedded/lib/ruby/gems/2.7.0/gems/json-2.3.0/lib/json/common.rb:156:in `parse'\r\n\tfrom C:/ProgramData/ServiceNow/agent-client-collector/cache/acc-f-commons/bin/endpoint_discovery.rb:179:in `block in <main>'\r\n\tfrom C:/ProgramData/ServiceNow/agent-client-collector/cache/acc-f-commons/bin/endpoint_discovery.rb:166:in `each'\r\n\tfrom C:/ProgramData/ServiceNow/agent-client-collector/cache/acc-f-commons/bin/endpoint_discoverySteps to Reproduce Example steps how to reproduce issue on a windows server: Install agent on a windows serverStop the agent (need to stop the agent to clear up the environment variables for the user session)Remove wmic command from global path of the windows server by: Opening the Start Search, typing in "env", and choose "Edit the system environment variables"Click the "Environment Variables…" buttonUnder the "System Variables" section (the lower half), find the row with "Path" in the first column, and click editThe "Edit environment variable" UI will appear.Select the variable which value contains "Wbem" and click "Delete" Start the agentRun a new ACC discovery and review the resultsWorkaroundWindows Server - wmic is not in System variables To confirm this is the root cause: Open the command promptRun "wmic CSProduct get IdentifyingNumber /format:list"Command fails with error wmic is not recognized as an internal oor external command This error has been seen on some windows servers hosted on the cloud, however could also happen to on premise servers, when the wmic software path is not in the System Variables. As a soluttion: Stop the agent (need to stop the agent to clear up the environment variables for the user session)Add wmic command to global path of the affected windows server by: Opening the Start Search, and typing in "env", and choose "Edit the system environment variables"Click the "Environment Variables…" buttonUnder the "System Variables" section (the lower half), find the row with "Path" in the first column, and click editThe "Edit environment variable" UI will appear.Click on "New" and a new row will be addedPopulate the row with %SystemRoot%\System32\WbemClick "Ok" Start the agentRun a new ACC discovery and review the resultsRelated Problem: PRB1509426