Month: September 2015
Recently when helping a customer with a ConfigMgr 2007 to 2012 R2 upgrade and migration, we were planning to upgrade their secondary sites to standard DPs. When setting up ConfigMgr 2012 R2 migration tools in the console, none of secondary sites were showing as being available for DP sharing. In reviewing the site’s migctrl.log file, there was an entry for an error that stated “The DP is NOT eligible for sharing because no ports between the legacy site and the current site are the same.”
In this case, the customer had configured the 2007 primary site to have clients communicate on a custom port, and not use the standard default port 80, of which the 2012 primary site was configured to use.
By changing 2012 to also use that same custom port, re-running the source hierarchy gathering process, the migration tool (and migctrl.log) now displayed the secondary site servers available for upgrade.
When setting up ConfigMgr 2012 R2 to use a remote server to host the Software Update Point on Windows Server 2012 R2, configuration of the SUP may fail. The WCM.log will show entries such as:
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608) Checking runtime v2.0.50727... Failed to create assembly name object for Microsoft.UpdateServices.Administration. Error = 0x80131701 Checking runtime v4.0.30319... Did not find supported version of assembly Microsoft.UpdateServices.Administration Supported WSUS version not found Remote configuration failed on WSUS Server
The error implies that WSUS 3.0 SP2 is required for the remote SUP, however it is not for Windows Server 2012 R2. Rather, since the SUP is on a remote server, the WSUS admin console server feature is required to be installed on the primary site server.
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!
I’ve come across this for a couple of customers. During installation of prerequisites for ConfigMgr 2012 R2 Software Updates, it is necessary to have the server WSUS role installed. If any domain GPO for WSUS is being applied, it may prevent the installation of the WSUS role on Windows Server 2012 R2. The specific policy is for the “Log on as a service”, which in GPO can be set to restrict access to specific AD groups. WSUS needs to create a local service and grant the logon rights during the install process, even when not selecting the setup 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:
- Move the server into the Computers container (so the GPO is not applied)
- Install WSUS (either as a database on SQL Server or the WID)
- Perform the WSUS post install tasks
- Move the server back into the proper OU