ConfigMgr 2012 SP1 - Primary Site Installation Step by Step

Here we see a step by step procedure to install ConfigMgr 2012 SP1 Primary site installation.

I used Windows 2008 Enterprise SP2 64 bit for the server, Preinstalled with WSUS 3.0 SP2, Powershell 3.0, and ADK.

Also below Patches for WSUS:
KB2734608 and KB2720211

Refer to Supported Configurations for Configuration Manager below.
http://technet.microsoft.com/en-us/library/gg682077.aspx

Download Prereq files using the command from the setup as shown below.

SMSSETUP\BIN\\setupdl.exe

1. Login into the server using local admin ID.

2. From the Configmgr setup disk, double click the splash.hta and select Install.

3. In the Before you Begin screen, read the checklist and click Next.

4. Select Install a Configuration Manager primary site and click Next.

5. Enter the product key and click Next. And accept the License Terms in the next screen.

6. Select all Checkboxes and Click Next.

7. Select Use previously downloaded files. Click Browse and select the path where you downloaded the prerequisites and click Next.

8. In the Server Language Selection window, select the languages. (By default English is selected) and click Next.

9. In the Client Language Selection window, choose the needed languages click Next. You may choose Enable all languages for mobile device clients if needed.

10. Type the three digits Site Code, the Site Name and the Installation folder. Select “Install the Configuration Manager Console Admin Console” and click Next.

11. Select either of the options. If you choose 1 then specify the CAS server FQDN in the box and click next. I chose option 1 since I had a CAS in my hierarchy.

12. Type in the below.
SQL server name.
SQL Instance(default is blank)
DB Name(Default is CM_Sitecode)
SSB Port(Default is 4022)
Click Next.

13. Type Provider Name (default is Primary server) and click Next.

14. Select second option and click next.

15. Uncheck both options and click Next.

16. Select appropriate one and click Next.

17. Click Next in the Settings Summary.

18. The Prerequisite Check may show if anything is missing. Then you may have to rectify them and Run check again. At this point you can view the log for more details.
%SystemDrive%\configmgrprereq.log
Click Begin Install if all success.

19. Click View Log to see the progress.
Note: Log file is found here.
%SystemDrive%\ConfigMgrSetup.log

It's Done..!
We will see Roles configuration in later posts.

 

SCCM 2012 - App stuck at downloading 0%

I was testing SCCM 2012 Application Management in the lab and there was an issue in the beginning where any app I tried were hanging at 0% downloading. I tried packages and Applications both.

It looked like it was content downloading issue.. It’s true. It was not able to find any DPs in the network.

The hierarchy is with a CAS and two primaries under it. For the primaries DP and MP are remote servers.

The CAS.log showed the below errors.  

Download request only, ignoring location update ContentAccess 1/16/2013 3:09:58 AM 7056 (0x1B90) Location update from CTM for content 00000007.2 and request {B969A22E-8A5E-416E-8BC2-655ECFAFEE42} ContentAccess 1/16/2013 3:31:21 AM 7228 (0x1C3C) Download request only, ignoring location update ContentAccess 1/16/2013 3:31:21 AM 7228 (0x1C3C) Location update from CTM for content 00000007.2 and request {B969A22E-8A5E-416E-8BC2-655ECFAFEE42} ContentAccess 1/16/2013 4:09:58 AM 7576 (0x1D98) Download request only, ignoring location update ContentAccess 1/16/2013 4:09:58 AM 7576 (0x1D98) Requesting locations synchronously for content Content_13d9fc7b-4246-4449-bd6a-404fc9177ed1.1 with priority Foreground ContentAccess 1/16/2013 4:52:59 AM 5848 (0x16D8) Begin checking Alternate Network Configuration ContentAccess 1/16/2013 4:53:21 AM 5848 (0x16D8) Finished checking Alternate Network Configuration ContentAccess 1/16/2013 4:53:21 AM 5848 (0x16D8) The number of discovered DPs(including Branch DP and Multicast) is 0 ContentAccess 1/16/2013 4:53:21 AM 5848 (0x16D8) Requesting locations synchronously for content Content_13d9fc7b-4246-4449-bd6a-404fc9177ed1.1 with priority Foreground ContentAccess 1/16/2013 4:53:57 AM 2644 (0x0A54) Begin checking Alternate Network Configuration ContentAccess 1/16/2013 4:53:57 AM 2644 (0x0A54)

And the Locationservices.log showed as below.  

Begin checking Alternate Network Configuration LocationServices 1/17/2013 1:09:38 AM 5244 (0x147C) Finished checking Alternate Network Configuration LocationServices 1/17/2013 1:09:38 AM 5244 (0x147C) Current AD site of machine is Default-First-Site-Name LocationServices 1/17/2013 1:09:38 AM 5244 (0x147C) Begin checking Alternate Network Configuration LocationServices 1/17/2013 1:09:38 AM 5244 (0x147C) Finished checking Alternate Network Configuration LocationServices 1/17/2013 1:09:38 AM 5244 (0x147C) Calling back with empty distribution points list LocationServices 1/17/2013 1:09:38 AM 5244 (0x147C) Current AD site of machine is Default-First-Site-Name LocationServices 1/17/2013 1:09:38 AM 6088 (0x17C8) Begin checking Alternate Network Configuration LocationServices 1/17/2013 1:09:38 AM 6088 (0x17C8) Finished checking Alternate Network Configuration LocationServices 1/17/2013 1:09:38 AM 6088 (0x17C8) Calling back with empty distribution points list LocationServices 1/17/2013 1:09:38 AM 6088 (0x17C8)

In the software center I saw this error code.

The software change returned error code 0x87D00607 (-2016410105)

It’s definitely because of client can’t find the content. But the content was available in the DP, but it can’t find the DP. I went back and forth with all the settings and permissions. All looked perfect. Reinstalled roles and IIS and breaking my head for couple of days with no success.

Then suddenly when I was going through the boundary groups properties I just saw that, In references tab under Content Location all the site servers are listed.

I added that, not knowing this would cause any issue. I overlooked it although it was clearly mentioned that only DP and SMP must be added.

So I removed all other site systems except the DP, then software deployment started working fine.

Local Group Policies affected by ConfigMgr 2007 Software Updates

                   When ConfigMgr Software Updates client agent is enabled, the local group policy used by windows update agent "Specify intranet Microsoft update service location" will be modified by ConfigMgr agent at the client side. There are 15 other policies which are related to Windows Update Agent as well. Those will not be modified by the ConfigMgr.

            It's advised to not configure other policies in AD. Although disabling the policies in AD won't make any difference it's better to leave it NOT CONFIGURED. But if the "Specify intranet Microsoft update service location" policy is configured in AD, it will cause the below error in WUAhandler.log
"Group policy settings were overwritten by a higher authority" and scan gets affected.
The above Group policies can be found under: Computer Configuration > Administrative Templates > Windows Components in GPO editor.

Peer Mohamed | Senior System Engineer