From release, SCCM 2012 R2 has been extremely solid and you may never run into any of the issues resolved by updates that have been released since; however in working with a Microsoft PFE (Premier Field Engineer) it was recommended to me to stay with the current version or current version -1. And if you read through what has been added in each version CU1 – CU5 you will likely find some nice fixes or additions that you can use in your environment. This is especially true for myself when it comes to the PowerShell improvements.
If you have never installed a SCCM 2012 R2 CU before you don’t need to worry about the previous updates, you can just install the latest version to get the improvements added since release. To read more about and obtain CU5 just take a look at the Microsoft Knowledge Base article here (https://support.microsoft.com/en-us/kb/3054451?wa=wsignin1.0).
The CU5 update can be applied directly to the following:
- Central administration site
- Primary site (Standalone)
- Primary site (Hierarchy)
- Secondary site
- Configuration Manager console
You should apply this update from the top down starting with your CAS if you have one or your Primary if you do not use a CAS.
Continue reading SCCM 2012 R2 CU5 Installation
System Center 2012 Configuration Manager comes with a lot of great built-in requirements out of the box; however they’re generally just generic conditions that are specific to the Windows Operating Systems or User accounts. This makes sense because not only would it be impossible to take into consideration every possible condition for even their own software, someone who is using ConfigMgr for purely server management isn’t going to care about settings for software like Microsoft Office even!
Fortunately, Microsoft made it quite simple to create your own custom conditions which can be used as Application Requirements.
Here’s a real-life example I used for a deployment in my company:
I was asked to deploy Lync 2013 throughout the company (around 1900 computers/users). Sounds simple enough except for a few things that needed to be taken into consideration. In the organization we have people using both Office 2010 Standard/Professional and Office 2013 Standard/Professional. On top of that, there are people using both the x86 and x64 versions of Office. Not only that but people using Office 2013 Professional don’t need Lync 2013 installed because it already ships with Lync.
While it is possible to deploy a version of Lync 2013 that includes both x86 and x64 versions, this version is around 1GB in size! The individual versions, while still large are about 300-400MB smaller which certainly would make a difference to VPN users who are connecting from home or more importantly tethering with their company cell phones. So I opted to use separate versions of each to try and make the deployments as small as possible.
This left me with two choices:
1. Determine all the users of each version of Office before-hand and deploy each version to a separate collection based on which version of Office each person uses. Extremely cumbersome.
2. Use requirements and deployment types and let SCCM figure out which version of Office should go on each computer. (DING DING DING! WE HAVE A WINNER!)
Continue reading Using Custom Requirements for Application Deployment