What’s New for Clients in SCCM 2012 R2?

With the release of SCCM 2012 R2, Microsoft has introduced many new features and made many changes in regards to the Client. In this article, we look at What’s New for Clients in SCCM 2012 R2:

• Microsoft Intune can manage Windows 8.1 devices – If you have non-domain joined Windows 8.1 devices that also don’t have the SCCM Client installed on them, these devices can be managed via Microsoft Intune.
• New “Resultant Client Settings” feature – Although SCCM 2012 allows multiple Client Settings to be deployed to the same Client, one of the biggest problems prior to R2 was trying to identify from the SCCM Console what the end result would be on a Client. SCCM R2 now includes the Resultant Client Settings feature that will show you what settings will be deployed to a Client from within the SCCM Console.

Wipe and Retire functions can remove just company data

What’s New for Clients in SCCM 2012?

With the release of SCCM 2012, Microsoft has introduced many new features and made many changes in regards to the Client. In this article, we look at What’s New for Clients in SCCM 2012:

• New 64-bit SCCM Client – SCCM 2012 now includes a native 64-bit client.
• Location of the “CCM” directory has changed – In SCCM 2007 the CCM directory containing pretty much everything relating to the SCCM Client was located in the %windir%\system32 directory. However, as the SCCM 2012 Client is 64-bit the location of the CCM directory has been changed to the %windir% directory.

NOTE: If you’ve got your own scripts that reference the old location you’ll need to update these to the new location to work with SCCM 2012. Although you can control where the Client gets installed (my recommendation would be you leave it installing to its default location), you cannot install the 64-bit SCCM 2012 Client (and therefore create the CCM directory), to a path that supports redirection such as Program Files or %windir%\system32 (which is the prime reason Microsoft had to move it in the first place).