ConfigMgr 2007 to 2012 R2 – Hung Conversions

Posted on October 31, 2015 Updated on January 16, 2016

Recently when helping a customer migrate to ConfigMgr 2012 R2 SP1 + CU1, the site had major problems with fully completing DP upgrades.  First, it would start the uninstall of a CM07 secondary site, then do nothing.  So we would restart the process to which it reassigns the DP and then stalls again…but even worse, it never completed the process and it couldn’t be restarted again.  So the status never came to a full completion and the old content (SMSPKG, PCK files, etc.) were not removed.  Additionally, the state of the migration status never went beyond “Reassigning distribution point” as in the image below.

Ultimately I had to engage Microsoft to get an answer.  Even they had to dig through the SQL stored procedure (sp_MIG_ UpgradeDistributionPoint) to understand for themselves what the conversion process does.  Essentially the stages boil down to these high-level steps:

1. Uninstall of the 2007 components, then delete the values in MIG_DistributionPointSource in the database
2. Drop a .dpu file into the distmgr.box  (for more info, see TechNet article “DP converts, but content fails“)
3. Convert DP values of various package and DP mapping values in SQL
4. And finally, set the DPUPgrade status where Action=2 and Status=0 for complete.  The example below shows an incomplete “hung” state of a DP with Action=2 and Status=1.

To get these statuses, the following SQL query was used so that we would know when the remote server had completed the uninstall of the secondary site and was ready to have a manual .dpu file dropped in distmgr.box to initiate the content conversion.

-- Result must be empty
select * from MIG_DistributionPointSource where PKGServer like '%ServerName%'

-- Result must have content listed
select * from PkgServers_G where NALPath like '%ServerName%'
select * from PkgServers_L where NALPath like '%ServerName%' 
select * from PkgStatus where PkgServer like '%ServerName%'
select * from ContentDPMap where ServerName like '%ServerName%'
select * from DistributionStatus where DPNALPath like '%ServerName%'

-- Result must have Action=2 and Status=1 to know server is ready to convert content
select * from DPUpgradeStatus where NALPath like '%ServerName%'

-- Use the DDPID number to create the .dpu file name
select * from DistributionPoints where ServerName like '%ServerName%'

The secondary site conversion woes occurred in primarily three ways:

• First problem – a rerun the stored procedure did not occur after the uninstall of 2007 components.  While this is still unsolved and would take ‘significant’ effort to diagnose the cause, PSS provided a query to identify if the site is ready for the content conversion by creating a dummy .dpu entry.
• Second problem – A manual restart of the conversion tools led to the system having a “failed to convert content”.  This was occurring because a couple dozen of the packages had mysteriously updated their source files, so there is a hash mismatch between 2007 and 2012.  The solution will be to delete those identified packages in 2012, re-migrate from 2007, and then restart the failed DP conversion (or drop a dummy .dpu)
• Third problem – On a “completed” DP, files were leftover on the DP, both the PCK and extracted SMSPKG$ files.  Since we did not migrate ALL packages that were on the 2007 DP into 2012, those files are left behind such that they still could be converted at some point if desired.  Otherwise they need to be manually deleted after the conversion process completes.  Then, any package that had a CM07 advertisement that is set to “run from server” will migrate over to CM12 with the option to “Copy content to a package share on DP” – meaning the files in the SMSPKG$ share will remain.  These files should not be deleted from the SMSPKG$, but rather it would be better to change the package setting to not copy the contents (if appropriate for that package).

ConfigMgr 2012 R2 SP1 – Setup Site Maintenace Unavailable

Posted on September 10, 2015 Updated on September 11, 2015

I recently needed to add multi-language clients that I had missed during the initial install of ConfigMgr 2012 R2 SP1.  Typically this is accomplished through site maintenance of the setup wizard.  New with the ConfigMgr 2012 R2 SP1 install is to first install ConfigMgr “RTM” SP2, then update the server with the lightweight R2 SP1 bits.

But when I ran the setup from the original ConfigMgr 2012 SP2 media, the only options available were to recover a site or uninstall the site.  The option to perform site maintenance was grayed out (see image below)!

Fortunately there was an easy workaround.  Instead of running setup from the media, instead run it from the current ConfigMgr installation directory, under \bin\X64\.  Optionally, run Configuration Manager Setup from the program files menu.  Then voila, the option was available!

Windows Deployment Services (WDS) startup error 0x2

Posted on October 22, 2014 Updated on October 23, 2014

On some distribution points in ConfigMgr, the WDS service may not start on Windows Server 2012 R2, which would prevent PXE boot. Trying to start the service produce error 0x2 in the event logs. This problem is likely being caused by the multicast option for the DP.

The fix is simple:
1. Remove the multicast option on the ConfigMgr DP role for that server. The logs can be monitored for removal completion in \\servername\drive$\sms\logs\
2. Start the WDS service.  If there is still an error, a reinstall of WDS may be necessary prior to continuing.
3. Re-add the multicast option and monitor the logs for completion
4. Restart the WDS service to verify it can still start

It also does not appear that Update 1 (KB2883200) for WinSvr 2012 R2 has a positive impact to prevent this, but it may. So I recommend setting up your monitoring tools to watch the state of this service.

WSUS install error “Log on as a service”

Posted on August 6, 2014

During installation of WSUS (a prerequisite for the ConfigMgr 2012 R2 SUP role), a GPO prevented the installation of WSUS on a Windows Server 2012 R2 system. The specific policy that caused the problem was for the “Log on as a service”.  In this specific instance, the GPO was restricting access to two AD groups. WSUS needs to create a local service and grant the logon rights during the install process, even if not selecting to use the Windows Internal Database (WID).

KB2832204 describes the issue precisely, even though it was written with regard to ADFS (and not WSUS). The workaround was to do the following:

1. Move the server into the Computers container (so the GPO was not applied)
2. Install WSUS (database on SQL Server, not the WID)
3. Perform the WSUS server role post install tasks
4. Uninstall Windows Internal Database
5. Move the server back into the proper OU