Within ConfigMgr 2007 it was normal to install Secondary site servers because of bandwidth management. In ConfigMgr 2012 this isn't needed anymore, because this functionality is available on remote Distribution points too. Therefore I installed a new ConfigMgr 2012 Primary site server and eight (8) remote Distribution points. For MAC OS X management I installed another Site server with multiple roles needed for HTTPS communication.
Special tasks provided during implementation:
-Application Catalog (doesn't work out-of-the-box always)
-Asset Intelligence - Software (empty by default, but useful when configured)
-Compliance Settings - Configuration Items and Baselines (Windows and Mac systems)
-Mac OS X management (PKI, certificates and roles for HTTPS communication)
-Shavlik Patch (download and publish third-party updates)
Special collections created for overview:
-Departments (all departments)
-Locations (all locations)
-Operating Systems (all operating systems)
-System Type (all system types)
Queries on Computer name, Model and System Type are used.
With all queries available and nested collections, you can create anything you want! :-)
Special tasks provided during OS deployment:
-BIOS Configuration Utility (HP)
-Define Active Directory OU Location
-Set BIOS Password when not available (HP)
-Use applications instead of packages
-Configure BitLocker for notebooks
Very cool to manage Mac OS X systems and deploy applications to them! Furthermore Rate Limits on Remote Site servers are great to configure bandwidth usage. Again: You can do so much in ConfigMgr, that almost everything is possible :-)
0 Response to "My findings after a ConfigMgr migration with Site servers through Europe"
Posting Komentar