Performing a SCCM 2012 R2 installation is not a walk in the park. The product itself can be complex for inexperienced administrators. There’s already tons of SCCM 2012 R2 Installation Guide available, written by experienced blogger and MVPs but I think that very few gives the whole picture from the start to the last component. Our goal is to bring it a bit further, explaining concepts and best practice rather than just guide the user through the installation process.
We was hesitant to post this SCCM 2012 R2 Installation Guide because SCCM VNext is coming pretty fast (Release date could be announced at Microsoft Ignite) but I finally decided to release it anyway. We still get consulting contract to install SCCM 2012 R2 so it’s definitely still relevant information.
The SCCM 2012 R2 Installation Guide blog post series will describe everything about the installation process, from the server prerequisites to the various site role installation and configurations.
At one of my customers I am currently building a System Center 2012 R2 Configuration Manager environment that must be able to support and manage their enterprise environment but also multiple not trusted forests in their environment. When adding one of the not trusted Active Directory Forests, the Active Directory Forest the Configuration Manager site information was published correctly but the discovery of the Active Directory Forest failed every time with an error that it failed to connect to forest.
Read the complete blog here: http://configmgrblog.com/2014/01/27/untrusted-forest-discovery-failed-error-2147474744/
At a customer lately I had an issue that my ConfigMgr 2012 R2 installation failed after the database has been configured during the setup process. After looking at the ConfigMgrSetup.log I noticed that the ConfigMgrSQLCert_PS1.cer file could not be saved to the location where the Configuration Manager Database was created.
Read the complete blog: http://configmgrblog.com/2014/01/10/configmgr-installation-failed-backslash-default-sql-database-path/
For some reason my Windows Intune connector stopped working correctly recently. While testing I was able to enroll devices to Configuration Manager / Windows Intune but the devices never showed up in the Configuration Manager console.
Same behavior was for newly applications deployed to the collection with all the Windows Intune enabled users. The deployed application did not became available in the Company Portal after logging on.
Read my complete blog here: http://configmgrblog.com/2014/01/06/configmgr-windows-intune-connector-stops-working-error-0x8013150c/