• Sccm 2012 Logs Location
• Sccm 2012 Client Logs
• Construction Site Installation

Configuration Manager 2012 SP1 - Part 3: Upgrading Secondary Sites. The first clue will be found in the Installation Status log view, with an entry something like. Deploying the Secondary Sites. Configuration Manager 2012 secondary sites are deployed through the console, via a push from a Primary Site Server. In the root of the system drive of the Primary Site Server doing the push installation, the log file ConfigMgrSetup.log will show the status of the install.

Installing SCCM Current Branch (CB) secondary server is a straight forward task however we can get into some of the issues. Some of the design considerations are very important before taking a decision to introduce a secondary site in SCCM CB infrastructure. I would personally avoid installing secondary unless you have a real need of it. Another fact is Secondary sites cannot be restored, and must be reinstalled. Each primary site supports up to 250 secondary sites and each Secondary sites can handle 15,000 clients. Another important point is you can’t throttle the SQL based replication link between SCCM secondary and primary sites as I explained in the post here (the post talks about SCCM 2012 but still applicable for SCCM CB). Remember secondary sites still need NET Framework 3.5 SP1 (or later) !! Some other design topics are discussed in the post here.

To install SCCM CB secondary server, you need to browse through CM console “AdministrationOverviewSite ConfigurationSites“. As you can see in the screen capture below, select the SCCM primary server and click on create Secondary Site.

Create SCCM CB secondary site Wizard. We can use this wizard to create a ConfigMgr secondary site under the primary site. Also you have to remember that when you install a secondary site it will automatically install the site system roles like DPs and MPs.

In this screen, you can specify the properties of SCCM secondary like site code, Site Server name, Site Name and installation folder.

In the page, you have 3 options to get installation source files of SCCM CB secondary site. In this scenario as it’s LAB setup I used the 1st option. However, I would recommend to use the option 3 when your secondary server is at the end of slow bandwidth connection.

1. Copy installation source files over network from parent site server.

Hard Drive: 500 MB free. Zuma Deluxe Free Download Full PC Game. Click On Below Button Link To Zuma Deluxe Free Download Full PC Game. It Is Full And Complete Game. Just Download, Run Setup And Install. No Need To Crack Or Serial Number Or Any Key. Start Playing After Installation. We Have Provided Direct Links Full Setup Of This Game.

2. Use the source files at the following network location.

3. Use the source files at the following location on the secondary site computer.

I set the default configurations for SQL server settings. For the DP configuration, I selected install and configure IIS if required by ConfigMgr. Rest all other configurations related to DP is set as default.

There are two ways to check the status of SCCM CB secondary site installation. 1. ConfigMgrSetup.log in the primary site (not the log file in the remote secondary site). 2. The other way of checking the status of installation is Show Install Status button in SCCM console ribbon.

The SCCM CB secondary site installation failed in my lab and I retried it and it failed again for the second time. When I checked the log file there an error related to .NET 3.5 SP1. The prerequisite checking was not completed successfully because it was not able to install .NET 3.1 SP1. When you choose to have SCCM install SQL Server Express as part of the secondary site installation, ensure the server meets the requirements to run SQL Server Express.

The problem with .Net 3.5 SP1 and Server 2012 is an old famous problem. Without the source files of Server 2012 R2, we can’t install .Net 3.5 SP1. When I tried install it without providing alternate path for SXS folder in the source files, it got failed with the following message :- “Do you want to specify an alternate source path? One or more installation selections are missing source files…”. I was able to get the .Net 3.5 Sp1 installed successfully after providing the source files. I also installed BITs and RDC components on the secondary server before retrying the installation.

I did retried the SCCM CB secondary site installation after that it worked very well. In the secondary site installation status you could see all the details and status of the installation.

Once the secondary site is installed successfully, we could see the status of secondary server as active in the console.

Installation of Secondary Site in Configmgr SCCM 2012 is not as simple as compared to SCCM 2007 due to several changes in SCCM Configmgr 2012 secondary site.

Before you proceed to install the secondary site,you need to ensure all the prerequisites are met including SQL server installation,IIS etc else you may have to come back to finish all the required prereq.

In My previous blog post here, i listed down the prerequisites to install secondary site. Below is little more descriptive:

Install IIS, BITS, RDC,.net framework 3.5

Add Primary site computer Account and secondary site(which you are going to install on) as member of local administrators group on secondary site server.

Add secondary site computer computers as member of sitesystem-to-siteserver connection group in Primary Site.

Install SQL server 2008 R2 SP1 Express with Cumulative Update 6 or above. Please refer to MS for more information about SQL server. http://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_SupConfigSQLSrvReq

I installed SQL server 2008 R2 SP1 Express with CU6 using default instance. Database Collation: SQL_Latin1_General_CP1_CI_AS.

check if the SQL server agent is not disabled and set to automatic and log on as ' local system account'.

Sccm 2012 Logs Location

Installation is straight forward without any special settings.

To know more about how to install SQL server, you can either refer my previous blog post here or Internet search will provide you lot of articles.

Once you are done with installation of SQL Server and CU, you will have to enable/configure couple of things.

1. Check if you SQL server service is not running in network account (should be either domain account or local system account) and set to automatic.

2. Enable TCP/IP Protocol with Port:1433 in IPALL for Dynamic Port as blank and TCPIP as 1433 . How do to this ?

Open SQL Server Configuration Manager

Sccm 2012 Client Logs

Move onto SQL Server Network Configuration-->Protocols for SQLExpress

Enable TCP/IP and Named Pipes

Also check if you have set the TCP port as Static with port number 1433 for all else you will not succeed with installation of Secondary site.

Now Restart the SQL server Service to make changes into effective.

We are now done with all the prereq needed to install Secondary Site.

Go back to your Primary Site administration node and start the installation of secondary site by selecting the right Primary site.

Sitecode,site name and where do you want to install SCCM.

Since I have already installed SQL server Express 2008 Version with Default instance on the server manually with required Cumulative Updates with Database Location etc.I leave instance as blank.If you have used other than default,Please specify it.

Click next ,Next and close.

Now we will monitor the progress of site Installation.

Once the prerequisites check list is completed, Primary site will start copying the required files for sccm installation on to secondary site installation drive with extension .pkg which will be decompressed to .tmp folder before the installation starts.

Monitor sender.log on the primary site to see the progress of .PKG File

Construction Site Installation

sending the package file is completed.

Go back to your secondary site and see what is it doing ?

You can see couple of files with extension .INI and .log

Look at .ini file with site information like Site name, Primary site, Installation Drive etc.

You may not be able to open the .ini file due to permission issues but try to copy to desktop/different folder to view the content on it.

Watch out for the installation/Errors either from console or log located in Primary site Root folder C:configmgrsetup.log

You see from above,The installation is Completed successfully.