Search the Community

Encountered a problem with one of my DPs which had multicast enabled after CU4 update to SCCM 2012. After the update, the WDS server failed to start with error 0x2. Every was fine previously. The CU4 update failed to update, presentig error messages on the SMS_Multicast_service component for that DP. Her is what the troubleshooting led to, helpdesk by the post in http://www.jniesen.de/?p=1916: - uninstall and reinstall of the multicast property does not resolve the problem. - reinstalling WDS role on the DP does not resolve the problem. - one needs to disable the PXE property of the DP also, on SCCM, to properly be able to reinstall the WDS role on the DP wdsutil /Verbose /Progress /Uninitialize-Server After this process, the wds role can be uninstalled and reinstalled. In order to enable the PXE and multicast properties in SCCM for that DP, you first need to reconfigure the WDS service with this command: wdsutil /Verbose /Progress /Initialize-Server /REMINST:"E:\RemoteInstall" If all goes well, the WDS server should be able to start (as a service on the DP) Do not enable Multicast property yet. - I the tried to run the update on the local DP from the update comand line, with verbose activated (Drive E:\ is the location where the DP settings are): E:\SMS\bin\x64\mcs.msi CCMINSTALLDIR=E:\SMS_CCM CCMSERVERDATAROOT=E:\SMS USESMSPORTS=TRUE SMSPORTS=80 USESMSSSLPORTS=TRUE SMSSSLPORTS=443 USESMSSSL=TRUE SMSSSLSTATE=0 MCSENABLELOGGING=TRUE MCSLOGLEVEL=1 MCSLOGMAXSIZE=1000000 MCSLOGMAXHISTORY=1 CURRENTDIRECTORY=E:\SMS\bin\x64 CLIENTUILEVEL=3 MSICLIENTUSESEXTERNALUI=1 CLIENTPROCESSID=3836 /l*v "e:\log.log" In the log.log file I could see, among other errors, this lines: [10:14:32] ERROR: Failed to compile migrated pre-V4 Beta 2 policies. Error 8004400A, lines 0 - 0 [10:14:32] Policy settings migration failed. CustomAction CcmMigratePolicySettings returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox) Which means 1603 “Fatal Error During Installation” On http://www.jniesen.de/?p=1916 we can read: Root Cause The default installation of Windows Server 2012 R2 is a SCCM 2007 client had crept through the automatic distribution on the server. This was duly removed before installing the ConfigMgrs 2012 R2. (Of course, the automatic client push of SCCM 2007 has been disabled.) Despite the uninstallation of SCCM 2007 client seems to have come to or leave some policy residues that installation can not handle the management point. Due to this, the management point could not install properly. Solution Since the management point installation, the problem that the SCCM client was launched in 2007 to life, can not eliminate, the new ConfigMgr client (2012 R2) on the server must be installed because the installation is capable of the legacy of the 2007 clients to eliminate. However, without a functioning management point of the new client must be run with certain parameters so that the installation goes through. Before this, however, install the Management Point role (management point) should be removed! Client installation: ccmsetup.exe / force install / source: "% ProgramFiles% \ Microsoft Configuration Manager \ Client" SMSSITECODE PS1 = (The source directory and the site code must be adapted accordingly!) After installing the client, the management point can (management point) can be added as a role again. The installation now runs through successfully. (Control using the setup logs "MPSetup.log") That is precisely what I did; the DP had not the sccm 2007 client but probably had it previously. I installed the SCCM 2012 client and updated it to CU4 version on the DP. After that, I could successfuly activate the Multicast property on SCCM for that DP.