Overview
Active Directory Discovery queries Active Directory for a list of network subnets and discovers each in turn.
NOTE - You will need the ports for WMI on the Windows firewall opened on each target Windows computer. For Windows Core servers, ensure you allow the firewall connections as per - http://blogs.technet.com/b/brad_rutkowski/archive/2007/10/22/unable-to-remotely-manage-a-server-core-machine-mmc-wmi-device-manager.aspx (note, page removed by Microsoft. Contents are below).
How To
To use Discovery we require access credentials on the target devices. Go to Discover -> Credentials -> Create Credentials and create credentials for all the types of devices you have. They may be for Windows, SSH (Linux / OSX / etc), SNMP, etc.
Once these have been completed you can go to Discover -> Discoveries -> Create Discoveries.
If you have set the "Local Network Address" in the config (Menu -> Admin -> Community -> Discovery Configuration) the Network Address will be pre-populated. This should be the URL of your Open-Audit server. You can use HTTPS if preferred (and you have installed a SSL certificate).
Open the advanced options by clicking on the "Advanced" button. Change the 'type' attribute to Active Directory, input the AD server you would like to query and the domain name.
Click the "Submit" button and you will be directed to the Discovery list page.
When you click Execute to start the Discovery, Open-AudIT will query the specified Domain Controller for a list of network subnets belonging to the domain. Open-AudIT will then create a discovery entry for each subnet (if it doesn't already exist) and commence discovery for that subnet.
Once the initial list of target devices has been obtained you should see details of each target as it is scanned and input into Open-AudIT.
TechNet Blog
Unable to remotely manage a Server Core machine (MMC, WMI, Device Manager)
BooRadely 22 Oct 2007 5:56 PM
I've been seeing a lot of churn internally and externally about installing a role on a server core machine and then trying to connect to it remotely only to find that the remote server core machine won't allow you to connect.
Remote Management:
To allow remote management of a server core machine run this locally on the box:
C:\>netsh advfirewall set currentprofile settings remotemanagement enable Ok.
After which point the firewall should allow all your remote admin tools to connect (computer management and DNS snap-in for example).
WMI:
If you're looking for WMI to be open on your servers:
C:\>netsh advfirewall firewall set rule group="windows management instrumentation (wmi)" new enable=yes Updated 4 rule(s). Ok.
Device Manager:
You can enable a read-only view of device manager remotely by doing the following:
1) On the server core machine enable remote management (see above).
2) On a full server open gpedit.msc and connect to the server core machine.
3) Go to: Computer Configuration\Administrative Templates\System\Device Installation
4) Enable the following policy: Allow remote access to the PnP interface.
5) Reboot the Server Core machine.
6) Now you should be able to access the device manager snap-in remotely from a full server.
Commands for a lot of different situations:
Want to know how to add.remove devices locally on a server core machien via the command line and every other command you'd ever need? See this:
