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.

SCUP 2011 Help File

System Center Updates Publisher 2011 is an application that can be used with System Center Configuration Manager to enable independent software vendors or line-of-business application developers and IT administrators to:

Import software updates from catalogs created by non-Microsoft organizations or created from within the administrator's organization.

Create and modify software update definitions.

Create applicability and deployment metadata for software updates.

Export software update definitions to other Updates Publisher 2011 consoles.

Publish software updates to a configured update server

 
 By using Updates Publisher to define software updates and publish them to the update server, administrators you can begin detecting and deploying published software updates with System Center Configuration Manager to client and server computers in your organization.

It is a free download from Microsoft. It can be downloaded from the below link.

http://www.microsoft.com/en-us/download/details.aspx?id=11940

There will be a help file installed in chm format along with the instalaltion. If you need the help file without installing the software for reference purpose, it can be downloaded from the below link.

https://dl.dropbox.com/u/67572103/scup2011.chm

Remote Fallback Status Point installation error message after reinstalling the Primary site

I had a CAS and two primary sites installed in my Lab under CAS.


For all the sites, SQL was in remote server. One day, I was unable to open the console in the primary 1 since it was not connecting to the remote SQL server for some reason.

I tried to reset the primary site using the configmgr setup. But it was not possible. So I removed the primary site manually using preinst.exe /delsite from CAS and cleaned up the primary site server registry entries (below) and services.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS

Even after that, when I tried to reinstall the primary site with new site code after reinstalling SQL and removed DB etc., it was not working. After several attempts, finally I had to rename the SQL server and reinstall the primary with new site code. It worked then.

Then I added all the roles one by one. I had FSP role in a dedicated server earlier. When I added the FSP role again in the primary 1, it was not installing and I saw the below error in component status from the console.

SMS_SITE_COMPONENT_MANAGER 1048 SMS Site Component Manager detected that site system \\xxxx is currently in use by SMS site xxx. Possible cause: You accidentally configured SMS to use this site system as part of this site and as part of site xxx. Solution: Remove this site system from the list of site systems for this site or for site xxx

I found that it was because of the residual registry entries from the old site code in the remote FSP server. After I removed the entire registry key (see below) from the FSP server and reinstalled the role it worked fine.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS