In a live production environment you wouldnt want to set it any lower than about once ever twenty-four hours as it will cause increased network traffic during the scans. Click OK Back on the Device collection window you will see your newly created collection.It may take a few minutes to query depending on the size of your environment but if you refresh after a few minutes you should see servers being added to the collection.

This can be useful if you need to isolate specific devices for one reason or another, such as software polices or specific client settings.

There are quite a few different ways to setup Device Collections.

I am going to focus on creating a collection based on OU's in Active Directory which in my opinion is one of the best ways to manage device collections long term as long as the device has the client installed on it.

In Assets and Compliance, Click Device Collections.

You will see a few that are created automatically by default. Right Click on Device Collections and Select Create Device Collection.

You will be presented with all of the available OU's in your Active Directory structure.In the case of this lab we only have Domain Controllers and Servers (manually created).We highlight Servers and Click OK So we have returned to our Membership Rules window.You can define if you want to run incremental scans by checking Use incremental updates for this collection.We are going to just use scheduled scans for this segment so lets go ahead and modify the discovery scan.Click Schedule Since we have a fairly small amount of servers in our lab we are going to set the interval low.