<h2>Windows discovery without 'domain admin' or 'local admin' privileges ?</h2><br/><div style="overflow-x:auto"><article><div ><h3 >Issue </h3><section><ul style="list-style-position: inside;"><li>Can a separate set of access rules be configured on Windows Domain Controller to grant the following permissions ?<br /><br /> <ol style="list-style-position: inside;"><li>Access to the WMI service to the current namespace and sub-namespaces.<br /><br /></li><li>Access to the Powershell service.<br /><br /></li><li>Membership in the Distributed COM Users local security group.<br /><br /></li></ol> </li><li> If yes, is there any relevant documentation to set up the configurations on Windows Domain Controller end ?<br /><br /></li><li>Is there a possibility to reconfigure the ServiceNow discovery share in a different location and not in the admin shares location ?</li></ul></section></div><div ><h3 >Release</h3><section><ul style="list-style-position: inside;"><li>All</li></ul></section></div><div ><h3 >Resolution</h3><section><ul style="list-style-position: inside;"><li>There is one basic rule for all queries related to WMI and PowerShell that mid should be able to run WMI and PowerShell commands on remote system.<br /><br /></li><li>If the commands requires admin privileges, admin share is required.<br /><br /></li><li>In case of discovery, most of the system detail commands requires admin privilege.<br /><br /></li><li>The below listed commands are all governed by the Windows user<br /><br /> <ol style="list-style-position: inside;"><li>Access to the WMI service to the current namespace and sub-namespaces.<br /><br /></li><li>Access to the Powershell service.<br /><br /></li><li>Membership in the Distributed COM Users local security group.<br /><br /></li></ol> </li><li>This user may or may not have admin privileges based on the requirement.<br /><br /></li><li>From Servicenow, it is suggested that the customer should have the admin or equivalent privileges for the successful discovery execution.<br /><br /></li><li>If you do not wish to provide admin privileges, we can only suggest you to create the users with the required permissions and test. This is out of the scope of the support to comment beyond this.<br /><br /></li><li><strong>Question</strong> : If yes, would it be possible for you to share the relevant configurations to be carried on Windows DC end ?<br /><br /></li><li>Servicenow does not hold any documentation related to the configuration set up on the Windows end. you may have to check with the Microsoft team for the same.<br /><br /></li><li>Alternately, you can allow non-administrator users limited access to run the specific commands, scripts, and executables necessary for Discovery via <strong>Microsoft JEA</strong>. Microsoft JEA enables role-based administration through PowerShell Remoting, which uses Windows Remote Management (WinRM) to manage communication and authentication. More details are provided in the below page:<br /><a href="https://www.servicenow.com/docs/bundle/vancouver-it-operations-management/page/product/discovery/concept/microsoft-jea-discovery.html">https://www.servicenow.com/docs/bundle/vancouver-it-operations-management/page/product/discovery/concept/microsoft-jea-discovery.html<br /></a></li><li>The sample JEA profile provided in KB0965705 is configured to discover many basic CIs and attributes. The profile can be modified and should only serve as a baseline for Discovery with JEA.<br /><a href="https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0965705">https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0965705</a><br /><br /></li><li><strong>Question</strong> : Is there a possibility to reconfigure the ServiceNow discovery share in a different location and not in the admin shares location ?<br /><br /></li><li>Yes this can be achieved by the property "<strong>glide.discovery.adme.base_dir_windows</strong>".<br /><br /></li><li>Check for this property under "<strong>sys_properties</strong>" table.<br /><br /></li><li>If you do not find an entry, create one with the Type: string and update the Value with the path of the desired location.</li></ul></section></div><div ><h3 >Related Links</h3><section><ul style="list-style-position: inside;"><li>Please refer the below documentation for the same<br /><br /><a href="https://docs.servicenow.com/bundle/paris-it-operations-management/page/product/discovery/reference/r_DiscoveryProperties.html">https://docs.servicenow.com/bundle/paris-it-operations-management/page/product/discovery/reference/r_DiscoveryProperties.html</a><br /><br /><a href="https://docs.servicenow.com/bundle/paris-it-operations-management/page/product/discovery/reference/r_ApplicationDependencyMapping.html">https://docs.servicenow.com/bundle/paris-it-operations-management/page/product/discovery/reference/r_ApplicationDependencyMapping.html</a><br /><br /><br /></li></ul></section></div></article></div>