The SCCM Console is accessible only from on campus (not wireless or resnet) and only to members of the NCSU-Departmental OU Admins group.
Note: The 2012 Console can be installed side by side with the 2007r3 console. During the migration, you will probably reference both consoles to be able to track the status of your clients through the migration.
- Install the SCCM 2012 Console from here:
\\wolftech.ad.ncsu.edu\files\ncsu\SW-Package-Prestaging\Microsoft-SCCM Console-2012 R2 SP1\ConsoleSetup.exe
- Enter: OIT200SCCM-SS.OIT.NCSU.EDU for the Site Server
- Install the Configuration Manager Toolkit from here (optional):
\\wolftech.ad.ncsu.edu\files\ncsu\SW-Package-Prestaging\Microsoft-SCCM Console-2012 R2 SP1\ConfigMgrTools.msi
Note that you should only install the client portion of the toolkit!
- Install the SCCM 2012 Right Click Tools from here (may not be updated for SP1):
\\wolftech.ad.ncsu.edu\files\ncsu\SW-Package-Prestaging\Microsoft-SCCM Console-2012 R2 SP1\Right Click Tools.msi
Right Click Tools for 2012 currently require the Powershell Execution Policy to be set to RemoteSigned in order to function as it generates a Powershell script on the fly as part of its execution.
- If you skipped installing the Configuration Manager Toolkit, Get a copy of cmtrace (replacement for trace32):
\\wolftech\engr\coedean\ou_admins\SCCM 2012 Console\cmtrace.exe
- SCCM Client Center has been updated for SCCM 2012. It is installable from http://sccmclictr.codeplex.com/ as a ClickOnce package. This will ensure that you get the latest version available each time you launch the application.
- Microsoft Deployment Toolkit 2012 SP1 (optional): http://www.microsoft.com/en-us/download/details.aspx?id=25175
- The UI of the 2012 console has been changed to be consistent with other Microsoft products. Namely: The Ribbon.
- The list of nodes from the 2007r3 console have been put into 4 categories: Assets and Compliance, Software Library, Monitoring, Administration. Each of these categories has sections that correspond to the nodes in the 2007r3 console.
- While the 2007r3 console had long lists or nested folders or collections, the 2012 console is built around searching and filtering results.
- Two people cannot edit the same object at the same time. If a second administrator attempts to edit the same object, they will receive an error.
- Folders in SCCM 2012 are globally visible, so every folder will appear for all users in the console. It is therefore requested that you do not create folders to keep the administration interface sane for other users.
- There will be only two folders present in the 2012 environment after the migration is complete: Software Package Collections and Operating System Collections. All collections that are used for software package deployment or operating system deployment should be created in these two folders. The reason for this is that there is a bug in the SCCM 2012 permissions, in that you must have the Modify Folder permission to create a Collection. And all Folders are seen by all users. This means you cannot delete these folders, but you can rename them. If you rename them, you will be warned… Once.
- Historical inventory data does not migrate. So all inventory will begin at migration time.
- The 2012 console will report that it is operating in evaluation mode until after we decommission the 2007r3 environment and migrate the license over to the 2012 environment.
- The ability to “group by” certain fields and then followed by collapsing some and sorting within the groups makes getting useful info much faster.
- Removing computer objects from a collection is something that can only be performed upon an object that has been added to the collection through a direct membership rule. Memberships granted through a query or an include rule will not allow objects to remove themselves. Most of the time, this functionality was needed to remove computer objects that had become obsolete. We are therefore setting permissions that will allow you to delete computer objects from your OU root collection. Remember: deleting an object will remove it from the console, and you will have to wait for it to re-register with SCCM in order for it to become manageable again.