Please add the ability in discoveries to:
- exclude OU's
- exclude Virtual Cluster resource154 votes
This is fixed in #SCCM 1806
The UBR registry key is responsible for displaying the subversion of a Windows 10 build to the end-user. For example 14393.*** where *** is the UBR string. If this is added to the HINV list of default classes this will allow for administrators to retrieve this information!
This is located in: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion
This will help administrators differentiate what intermediate builds of Windows 10 they have install and also support patch management because they can easily compare the released patches to the subversion build each month.60 votes
This is fixed in the #SCCM 1802 production build released today.
Have the ability to include/exclude certain OU's from both Active Directory User and System Discovery.
E.G. I might have an "All Users and Groups" OU at the root domain level, which may contain sub OU's containing service accounts or mailbox accounts etc. that I don't want being picked up by discovery. The ability to pick which sub OU's to discover/not discover would be really handy in this scenario. The same applies for system/computer discovery also.45 votes
Fixed in #SCCM 1806.
It would be great if we could exclude certain OS's from discovery. I have over 5500 machines in my DB that I couldn't care less about but they reside in an OU where I have machines I do care about.3 votes
In 1902, you can exclude OUs you do not want to discover
- Don't see your idea?