SamuelBaughan asked a question.
Recognition of MS System Center products
I struggle with the recognition of System Center (DPM and SCCM) on our environment.
It seems that the recognition rules mix servers and clients ...
Has anyone seen the same thing? Is it a problem with the rules?
The SCCM agent was always the same whether Server or Client - I'd expect recognition to show the same thing
Data Protection Management is something else. What are you seeing?
SCCM server also has its own main EXE as far as I understand (SMS_EXEC.exe), there is even a file that allows to distinguish a main SCCM server from a distribution point (smsdpusage.exe).
But I constantly see weird stuff in SLM. Take "Microsoft System Center Server Configuration Manager 2012 Client ML" on all our servers ... well, there sure is a requirement, but not for a "Client" ML, that would require a "Server" ML rather.
Have you managed to use Snow to accurately check your System Center compliance?
It seems to me that mainstream MS apps like SCCM/DPM should be detected with 99% accuracy by now.
It seems the bundle is a 'loose' bundle and you can pick-n-choose which elements to install. We weren't getting recognition because the rules say only a registry entry needs to be installed, which wasn't. Also, the folks using STandard edition install a couple and the folks using Datacenter edition install something else, so we're experimenting with local application records.
This is also impacting recognition of our Core Infrastructure Suite editions.
Yes, I was tempted to go down the custom applications route but I feel like those applications should definitely feature strong detection out of the box