Unable to Add Secondary servers after installing Cu2 for SCCM sp1

Have you installed Cu2 for ConifgMgr 2012 Sp1?  If so you might see a error when installing a Secondary Site.  This problem has been document in the forrum

Microsoft has released a blog detailing the work around for the post CU2 for ConfigMgr 20 12 SP1 problem while adding a Secondary site.  Microsoft is investigating but as a workaround here is what you can do to get around the issue.

 One way is to use a network location of the secondary install files.  The second method was created by one of the MVP and details changing out XML files from the initial Sp1 installation media.

 

http://blogs.technet.com/b/configmgrteam/archive/2013/07/02/known-issue-secondary-site-installation-failure-with-cumulative-update-2.aspx

 

Once I have more information I will email everyone, I will also try to update my blog with the information as well.

More information on what Cu2 fixes is detailed here: http://support.microsoft.com/kb/2854009

 ---
update.


Microsoft has released a hotfix to fix the issue:
http://support.microsoft.com/kb/2867422

FIX: Errors when you try to install or recover a secondary site in System Center 2012 Configuration Manager

Description of Cumulative Update 2 for System Center 2012 Configuration Manager Service Pack 1

http://support.microsoft.com/kb/2854009

Microsoft has publicly announced the availably of CU2 for ConfigMgr 2012 Sp1.

I will let you read the information for yourself but it fixes several issues for us.

CU1: Alternate port download for Windows update
CU2: Imaging over Alternate ports and BGB issue when using Custom Websites.

Like Cu1 you will need to have an update to the client pushed as well as an update to the Task Sequence for the client.

One thing I will need to test with this release is the need to repush the Boot.wim.  This would be necessary for the companies running over alternate ports.  It is also a good practice to create new boot media for your machines.

I hope to have this fully tested soon but none of what I have suggested is destructive to your enviroment. 
 

Locating a broken Software Update package

Scenario:

Onsite complains that the machine hangs when installing patches during imaging (or all machines for a given patch).  It could also be that the user has the dialog box for Software Update but it continually says "failed"

 

Solution:

1. Location the machine name

2. Open Status Messages for the given machine.  Locate the patch that failed, assuming the status message was sent back. 

    In 2007: System Status -> Status Message Queires - > all Status Message from a specific Machine

    in 2012: Monitoring Pane -> All Status Messages from a Specific System

3. Type in the machine name, time range and select OK.  A faster way is a right click tool I created a while back (http://www.sccm-tools.com/tools/rightclick/Rightclick-statusmessages.html) I don't have this in 2012 yet.  I need to also update my tools site to support 2012, look for the changes.

 

 

 

Locate this line:

Bundle update "93fa39c7-1f23-4549-b3ba-71021177bcc4" failed to get content for update "2cefe0ef-f4e1-4c3d-97f9-10a608c46c52". Please check the enforcement status of update "2cefe0ef-f4e1-4c3d-97f9-10a608c46c52" to get further details. The operating system reported error 2147500036: Operation aborted

 

If we pull the updateid "2cefe0ef-f4e1-4c3d-97f9-10a608c46c52" you can hunt for the specific update.  In this case you need to open your Content Location folder and search your Microsoft Updates for the folder..

 

 

Here we can see this is from the Q2 updates for the 2013 patches from the year of 2013. 

 

From here there are several things you can do:

1. remove the update frrom the DP and then repush

2. Refresh the package on the DP.

3. Delete the update and redownload (Provision) it from Microsoft and repush.

 

The end result should be the same.  Hopefully you can back track the bad update and fix it.

 

Note:  This assume you have already determined there are problems with the source and not the machine.  This can be determined by uninstalling the update from a machine and attempting to reinstall it or seeing all machines pulling from the given DP with errors.

 

Utilizing Fall back for Software Updates in 2012 Sp1

"Starting in Configuration Manager SP1, you can configure a client on the intranet to download software updates from Microsoft Update if a distribution point is not available. " http://technet.microsoft.com/en-us/library/gg712304.aspx

Now that we have a way to make clients download updates from the Internet when an update is not found on a distribution point.   This is a unique feature but it does require updates be download and on at least 1 DP.

Now how can we utilize this new feature to cheat the clients.  This is how:

Scenario: Company of 15,000 machines has 300 machines left on Vista and 400 on Windows XP.  Network bandwith to the DP is limited and there are no more than 10 machines at each site.  This company is special because they have a proxy link to the Internet so all non-business traffic is sent directly to the internet.  But they must still patch all these computers.

Solution: Pick a single DP to hold the Vista and XP patches.  Create your Software Update Groups as usual but only deploy them to a single DP.  Why?  The XP/Vista clients will look at the local and remote DPs for software updates.  You must check both Boxes to "Download and install".  They will not find the updates so it will fail over to the Internet. Because the number of machines is small the company will not feel the internet traffic download and the admins don't need to distribute Vista or XP patches all over the world. 

This was not meant for the way I am pushing it but it does work. 

What it solves:
1. No network traffic to random DPS for Vista and XP patches
2. DP queue is open for other distributions.
3. Clients patch and compliance number will continue to rise
4. OS patches only need to be on 1 DP


Note: CU1 is required is you are running over alternate ports.  This corrects and issue of the client trying to use the alternate ports to contact Microsoft Updates