System Center 2012 Configuration Manager SP1 – Don’t install it in production


System Center 2012 Configuration Manager SP1 – Don’t install it in production if downloaded from MSDN or Technet, wait until General Availability.


This blog is copied from Niall C. Brady, Configuration Manager MVP.

There’s been a lot of talk lately about System Center 2012 Configuration Manager Service Pack 1 being released to MSDN and Technet and I (like a lot of people) have downloaded and installed it in my lab.
The key part of that sentence above is ‘in my lab‘.
It is not permitted by Microsoft to install System Center 2012 Configuration Manager SP1 in production if you downloaded it from either of these two locations:-
  • MSDN
  • Technet
but why ?
The answer is found here on Microsofts’ MSDN site and it explains that you are not permitted to install this software in Production (highlighted in red below).
Use Microsoft software in Production
In fact what you can also clearly see from the screenshot above  is that you are better off using a MSDN subscription in regards to testing the software in your LAB from a licensing perspective.
The moral of the story is you have to wait until General Availability  to get System Center 2012 Configuration Manager Service Pack 1 and download it from theVolume Licensing site (or appropriate) to use in production, don’t use the MSDN or Technet versions of the software in production, it’s not allowed by Microsoft.

Help link : 

Comments

Post a Comment

Popular posts from this blog

Message ID: 4912 Configuration Manager cannot update the already existing object "SMS-Site-SXX" in Active Directory (XXX.XXX)

Image
Error in component SMS_HIERARCHY_MANAGER Possible cause: The site server's machine account may not have full control rights for the "System Management" container in Active Directory Solution: Give the site server's machine account full control rights to the "System Management" container, and all child objects in Active Directory. Possible cause: The Active Directory object "SMS-Site-S15" has been moved to a location outside of the "System Management" container, or has been lost. Solution: Delete the object from its current location, and let the site create a new object. Possible cause: The Active Directory schema has not been extended with the correct ConfigMgr Active Directory classes and attributes. Solution: Turn off Active Directory publishing for each site in the forest, until the schema can be extended.  The schema can be extended with the tool "extadsch.exe" from the installation media. Solution which is wor...
Read more

Internet explorer 11 deployment issues and few solution step

I know this blog is the old one but hope it will help someone. Microsoft released IE11 on 06-11-2013 and till now most of the organization on their way to deploy it. Therefore I am trying to list down some of the issues and steps to resolve it. First of all, Microsoft has already released deployment tool kit for IE11. Link Second there is a log file for checking the deployment issues which is I have always preferred IE11_main.log (typically c:\windows). Other log files are link . Most of the time found an issue with prerequisite failure (based on log IE11_main.log)  ~Version Check for (KB2834140) of C:\WINDOWS\System32\d3d11.dll: 6.1.7601.17514 >= 6.2.9200.16570 (False) ~Version Check for (KB2882822) of C:\WINDOWS\System32\tdh.dll: 6.1.7600.16385 >= 6.1.7601.18247 (False) And after that if we integrate this to script / admin kits then it will success. Here is few prerequisite for IE11 KB2834140, KB2670838, KB2639308, KB2533623, KB2731...
Read more

SCCM 2012 Client Package waiting for prestaged content

Image
During DP installation on CM 2012 some of my friends are getting this error like “Distribution Manager is waiting for Package XXX00001 content to be prestaged on the distribution point” in DP details view .isn’t it ? So where is the issue then, very strange...? Think about package distribution in SCCM 2007 there is error in package source version mismatch right!  This error is quite similar in CM 2012 and in troubleshooting of this part which I have noticed just redistribute the package again or the last option update the DP which is strongly prohibited in all DP’s infrastructure. Please see below the screenshot hope it will help. 1. First of all check the DP is having Prestage option enable or not. If yes then disable it for short term. 2. Now locate the package and redistribute the package. And the last option is update the DP, which is update the all DP (might be a bad suggestion)
Read more