My first question when reading this post was why is your colleague looking to replace vCM with SCCM? Is it a license cost issue or are they moving from VMWare to Windows HyperV etc? Is their focus on problem management and any related patch management or compliance reporting with the change?
I have read some blog posts where SCCM users have complained about the detail provided in SCCM's compliance reports - where the user needs to consider their device naming and CMDB records to take advantage of the out of the box reporting. Posters noted customization of reports can lead to very long report run times and oversized detail. Specific to vCM, there are some available add on tools that address its weaknesses in compliance reporting so that gives another option - ie staying with vCM but installing an add on app to improve its compliance reporting/remediation.
Find out in this report how the two Configuration Management solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI.
My first question when reading this post was why is your colleague looking to replace vCM with SCCM? Is it a license cost issue or are they moving from VMWare to Windows HyperV etc? Is their focus on problem management and any related patch management or compliance reporting with the change?
I have read some blog posts where SCCM users have complained about the detail provided in SCCM's compliance reports - where the user needs to consider their device naming and CMDB records to take advantage of the out of the box reporting. Posters noted customization of reports can lead to very long report run times and oversized detail. Specific to vCM, there are some available add on tools that address its weaknesses in compliance reporting so that gives another option - ie staying with vCM but installing an add on app to improve its compliance reporting/remediation.