SCCM 2012 Secondary Site Installation Benoit Lecours December 1, 2014 SCCM 2 Comments Determining if you need a Primary Site, Secondary Site or only a Site System Role (MP,SUP) in your SCCM hierarchy can lead to confusion.
Service Type Account Description SCCM Group lab1 SCCMAdmins SCCM Administrators Global Security Group SCCM User lab1 svc-confmgrlocaladm SCCM Client Push account SCCM User lab1 svc-sccmnaa SCCM OSD in WinPE to access content on the network SCCM User lab1 svc-sccmjd SCCM OSD – “Join Domain”. Add your account to the SCCMAdmins group. Add SCCMAdmins group to Local Administrators of M-SCCM1 server Account: svc-confmgrlocaladm This account is needed if you deploy SCCM client by using the client push installation method. The Client Push Installation Account is used to connect to computers and install the Configuration Manager client software. This account must be a member of the local Administrators group on the computers where the Configuration Manager client software is to be installed. This account does not require Domain Admin rights.
You can specify one or more Client Push Installation Accounts, which Configuration Manager tries in turn until one succeeds. Account: svc-sccmnaa This account (is needed during OS deployment in WinPE to access content on the network which is referenced by the task sequence. This account might also be used during operating system deployment when the computer installing the operating system does not yet have a computer account on the domain.
I will configure it later. Account: svc-sccmjd This account will be used for join computer to domain during a deployment. To do that, this account required AD permission: On the “Join to Domain” task, you can specify the OU where you want to add the computer. So you have to Delegate Control on each OU that you want to use. Start /w adksetup /quiet /installpath D: WindowsKits 8.1 /features OptionId.DeploymentTools OptionId.WindowsPreinstallationEnvironment OptionId.UserStateMigrationTool Size Installed: around 1.7 GB Install SCCM Primary Site OK, now we can install the Primary Site.
0. System Center 2012 R2 Configuration Manager (ConfigMgr 2012 R2) has now been released and it’s time to upgrade your site servers. This guide will help you along the way to successfully upgrade your current ConfigMgr 2012 SP1 site server to ConfigMgr 2012 R2. I will keep this post upgraded with the latest developments regarding the upgrade process.
Overview. Verify your hiearchy. Download software. Upgrade to Windows ADK 8.1. Install the latest Windows Updates. Disable Site Maintenance tasks. Determine if the SQL Server is supported by ConfigMgr 2012 R2.
Backup the database. Perform a test upgrade of the database. Install ConfigMgr 2012 R2. Upgrade stand alone ConfigMgr consoles Verify your hiearchy In order to upgrade to ConfigMgr 2012 R2 all your site servers need to be running ConfigMgr 2012 SP1 at minimum. Only Primary Site server and Central Administration Servers are applicable for upgrading as described in this post. Upgrading Secondary sites will be performed within the console. When you begin with the upgrade process, begin from the top and work your way down.
That means that if you have a CAS, you’ll need to upgrade that first. Then continue with the Primary Site servers and finally the Secondary Site servers. If your hierarchy has a CAS, once you’ve upgraded that you’ll have to wait until the replication links between the CAS and Primary Site servers have been established again before you continue with upgrading the Primary Site servers. This process can take a while, so be patient. Download software Download the following software to the site server:. System Center 2012 R2 Configuration Manager Upgrade to Windows ADK 8.1 1.
Uninstall the current Windows ADK 8.0 from the site server. Launch an elevated command prompt and browse to the location where you saved adksetup.exe from the link above. Run the following command line: adksetup.exe /norestart /q /ceip off /features OptionId.WindowsPreinstallationEnvironment OptionId.DeploymentTools OptionId.UserStateMigrationTool Windows ADK 8.1 will now be installed in the background. It takes some time since it downloads the three necessary components from the web. The components that are being installed is the following:.
Windows Preinstallation Environment (Windows PE). Deployment Tools. User State Migration Tool (USMT) Install the latest Windows Updates Make sure that you’ve installed the latest updates from Windows Update on the site server before you continue. Reboot the server before you continue. Disable Site Maintenance tasks Go through the enabled tasks in Site Maintenance for the site server that you’ll upgrade and determine if any of the tasks could interfere with the upgrade. If Site Maintenance tasks run during the upgrade, the upgrade could fail.
Disable at least these tasks:. Backup Site Server. Delete Aged Client Operations. Delete Aged Data Discovery Remember to take a note of those tasks that you’ve disabled and re-enable them once again when the upgrade is complete.
Determine if the SQL Server is supported by ConfigMgr 2012 R2 Check the version of the SQL Server that is running the database of the site server that are about to be upgraded. It would need to be running a supported version for the upgrade to work.
More information about the supported configurations can be found here: Backup the database Before we continue, go ahead and perform a backup of the database on the site server in question that are being upgraded. If you’ve not backed up the site servers database before, perform the following steps: 1. Open the ConfigMgr console. Go to Administration - Site Configuration - Sites -, right-click on the site and choose Site Maintenance.
![Sccm 2012 Secondary Site Installation Logiciel Sccm 2012 Secondary Site Installation Logiciel](/uploads/1/2/5/4/125402603/394452378.jpg)
Select Backup Site Server and select Edit. Check Enable this task. Click on Set Paths and enter an UNC path to the folder where you wish to backup the database. It’s important that the site server that has the database is given Full Control permissions for both Sharing Permissions and NTFS Permissions. Open services.msc and locate the SMSSITEBACKUP service. Right-click on the service and choose Start. The backup will now run and after a while your database will be backed up in the folder your specified.
Perform a test upgrade of the database Perform the steps in the to make sure your database is ready to be updated. Install ConfigMgr 2012 R2 Before you continue, restart the site server so there’s no pending restarts. Mount the downloaded ConfigMgr 2012 R2 ISO to the site server. Launch splash.hta. Click Install. On the Before You Begin page, click Next.
On the Getting Started page, make sure Upgrade this Configuration Manager site is selected and click Next. Enter your product key if necessary on the Product Key page and click Next. On the Microsoft Software License Terms page, accept the license terms and click Next.
On the Prerequisite Licenses page, accept all license terms and click Next. On the Prerequisite Downloads page, select Download required files and select a folder to store the files. For example store them in C: ConfigMgr2012R2Prereqs.
Wait for the downloads to complete. On the Server Language Selection page, make sure the correct languages for your environment is selected and click Next. On the Client Language Selection page, make sure the correct languages for your environment is selected and click Next. On the Settings Summary page, click Next. On the Prerequisite Check page, remediate any error messages shown in the wizard.
If you see any warnings, determine if you’re able to continue without fixing them. When ready, click Begin Install. The upgrade will now start. Wait for it to finish.
Once the upgrade has finished click on Close. Upgrade stand alone ConfigMgr consoles When upgrading a CAS or Primary Site server, the ConfigMgr console is updated automatically. But for stand alone consoles, they need to be updated manually. Mount the ConfigMgr 2012 R2 ISO on the system in question. Launch splash.hta. Click on Install Configuration Manager console. The installation will now begin, wait for it to finish.
The ConfigMgr console has now been upgraded to R2 aswell. That’s all, the site server has now been upgraded to ConfigMgr 2012 R2. Principal Consultant and Enterprise Mobility MVP since 2016. Nickolaj has been in the IT industry for the past 10 years specializing in Enterprise Mobility and Security, Windows devices and deployments including automation.
Currently working for TrueSec as a Principal Consultant. Awarded as PowerShell Hero in 2015 by the community for his script and tools contributions. Creator of ConfigMgr Prerequisites Tool, ConfigMgr OSD FrontEnd, ConfigMgr WebService to name a few. Frequent speaker at conferences and user groups.
Author Principal Consultant and Enterprise Mobility MVP since 2016. Nickolaj has been in the IT industry for the past 10 years specializing in Enterprise Mobility and Security, Windows devices and deployments including automation.
Currently working for TrueSec as a Principal Consultant. Awarded as PowerShell Hero in 2015 by the community for his script and tools contributions. Creator of ConfigMgr Prerequisites Tool, ConfigMgr OSD FrontEnd, ConfigMgr WebService to name a few. Frequent speaker at conferences and user groups.