Config Manager Update R2 PXE dont work, WDS stops

After you Update Config Manager 2012 Sp1 to R2 with the following steps:

– Uninstall old ADK 8.0
– Install new ADK 8.1
– Ubdate Configmgr 2012 to R2

After that your PXE dosn’t work with the updated und the ols WinPE Boot images.
If you would to start the WDS manually he gives you an Error like this: “ unaccapted error 1704”

If you set the Flag in the porperties of a WinPE for “Deploy this boot Image from the PXE-Enabled distribution point”

image

And Apply this Window, your WDS Service stops to work.
In the distmgr.log file you can see the following entries:

WDSServer is NOT STARTED SMS_DISTRIBUTION_MANAGER 21.10.2013 16:01:39 4404 (0x1134)
Failed to restart WDS service SMS_DISTRIBUTION_MANAGER 21.10.2013 16:01:39 4404 (0x1134)
Running: WDSUTIL.exe /Initialize-Server /REMINST:”G:\RemoteInstall” SMS_DISTRIBUTION_MANAGER 21.10.2013 16:01:39 4404 (0x1134)
Waiting for the completion of: WDSUTIL.exe /Initialize-Server /REMINST:”G:\RemoteInstall” SMS_DISTRIBUTION_MANAGER 21.10.2013 16:01:39 4404 (0x1134)
Failed to run: WDSUTIL.exe /Initialize-Server /REMINST:”G:\RemoteInstall”. Program returned 0000041d SMS_DISTRIBUTION_MANAGER 21.10.2013 16:01:50 4404 (0x1134)
Machine is running Windows Server. (NTVersion=0X602, ServicePack=0) SMS_DISTRIBUTION_MANAGER 21.10.2013 16:01:50 4404 (0x1134)
Finding Wimgapi.Dll SMS_DISTRIBUTION_MANAGER 21.10.2013 16:01:50 4404 (0x1134)
MsiEnumRelatedProducts failed SMS_DISTRIBUTION_MANAGER 21.10.2013 16:01:50 4404 (0x1134)
FindProduct failed; 0x80070103 SMS_DISTRIBUTION_MANAGER 21.10.2013 16:01:50 4404 (0x1134)
MsiEnumRelatedProducts failed SMS_DISTRIBUTION_MANAGER 21.10.2013 16:01:50 4404 (0x1134)
FindProduct failed; 0x80070103 SMS_DISTRIBUTION_MANAGER 21.10.2013 16:01:50 4404 (0x1134)
Found C:\Windows\system32\wimgapi.dll SMS_DISTRIBUTION_MANAGER 21.10.2013 16:01:50 4404 (0x1134)
SetNamedSecurityInfo() failed. SMS_DISTRIBUTION_MANAGER 21.10.2013 16:01:50 4404 (0x1134)
SetObjectOwner() failed. 0x80070003. SMS_DISTRIBUTION_MANAGER 21.10.2013 16:01:50 4404 (0x1134)
SetFileSecurity() failed. SMS_DISTRIBUTION_MANAGER 21.10.2013 16:01:50 4404 (0x1134)

If you remove the Images from the Distribution Point the WDS Service can be started with no porblems.

The Log File Say’s you have a Problem with wimgapi.dll
and here are the solution, you where to early on the downloding Button for the adk 😉
Thank you Michael that i found your Article: http://blogs.technet.com/b/mniehaus/archive/2013/10/21/the-adk-for-windows-8-1-has-been-updated.aspx

Thank you Jürg Koller to find the Link 🙂

————————————————————————————————————————————————–

And now i found the solution:

First i have to say what configuration i have tested and found the solution;

We have a Server 2012 installation with SQL 2012 SP1 on it, Installed RMT, then Updated the normal Way like SP1, CU1, CU2, CU3 and finaly the R2

After the update to R2 the WDS Service bloked and never run after set the following Flag on a Boot image “Deploy this boot Image from the PXE-Enabled distribution point” The boot Image can send to the Distribution Point without any Problem, but never set the Flagg.
This Distribution Point is located on your Primary Site Server and use WDS on the same Machine as the ADK 8.1 is installed.

The Work arround is you can use the Boot Media or Build a another Server that work as a Distribution Point.

Solution:

Go to Configmgr console to your Boot Images, remove all from your local DP and also uncheck the flag in it.
Open the Explorer and navigate to your Remoteinstall folder, open the folder SMSImages, this folder should be empty.

Start a command promt on your Server as administrator of corse.

Type the following Command
msiexec.exe /quiet /i <install DIR from Configmanager>\wim\wimgapi.msi /log c:\temp\wimgapi.log

Run the Command and Have look in the Log-File, there should no Error.

Got to your Boot Images and Send it to your Distribution Point and set the Flagg.

Have a look to the WDS-Service now he runs without a stop.

Controll the distmgr.log and the smspxe.log and test your PXE environment, now this should run smoothly

Be not shocked about the Errors, it runs 🙂

Library path mismatch: \\?\G:\SCCMContentLib, G:\SCCMContentLib    SMS_DISTRIBUTION_MANAGER    07.11.2013 11:31:37    1800 (0x0708)
Expanding G:\SCCMContentLib\FileLib\9B0A\9B0AC03428C5551D01AB49B8EC198A6DDE488EB0459942A96CA61639BA11E149 from package XXX00028    SMS_DISTRIBUTION_MANAGER    07.11.2013 11:31:37    1800 (0x0708)
Finding Wimgapi.Dll    SMS_DISTRIBUTION_MANAGER    07.11.2013 11:31:37    1800 (0x0708)
MsiEnumRelatedProducts failed    SMS_DISTRIBUTION_MANAGER    07.11.2013 11:31:37    1800 (0x0708)
FindProduct failed; 0x80070103    SMS_DISTRIBUTION_MANAGER    07.11.2013 11:31:37    1800 (0x0708)
MsiEnumRelatedProducts failed    SMS_DISTRIBUTION_MANAGER    07.11.2013 11:31:37    1800 (0x0708)
FindProduct failed; 0x80070103    SMS_DISTRIBUTION_MANAGER    07.11.2013 11:31:37    1800 (0x0708)
Found C:\Windows\system32\wimgapi.dll    SMS_DISTRIBUTION_MANAGER    07.11.2013 11:31:37    1800 (0x0708)

Expanding AL200028 to G:\RemoteInstall\SMSImages    SMS_DISTRIBUTION_MANAGER    07.11.2013 11:31:37    1800 (0x0708)
Error opening file: G:\RemoteInstall\SMSImages\AL200028\winpe.AL200028.wim. Win32=32    SMSPXE    07.11.2013 11:31:38    5888 (0x1700)
Retrying G:\RemoteInstall\SMSImages\AL200028\winpe.AL200028.wim    SMSPXE    07.11.2013 11:31:38    5888 (0x1700)
Sleep 30 minutes…    SMS_DISTRIBUTION_MANAGER    07.11.2013 11:31:39    1736 (0x06C8)
Used 1 out of 3 allowed processing threads.    SMS_DISTRIBUTION_MANAGER    07.11.2013 11:31:39    4536 (0x11B8)

Hope it helps, the infos are as is, test it first in your Lab.

————————————————————————————————————————————————–

The Solution that iwrote is not Supported, the wimgapi.msi is for old 2008 Server installations, so if you used my Solution do the following:

Uninstall the ADK 8.1, after a reboot install it again and reboot another time.

Now you have a supported state, and now you can install this Patch from MS http://support.microsoft.com/kb/2905002

Taht should work.

I tested this Fix and do the steps above

Hope it help’s and test it before use it in produktive


Comments

Leave a Reply

Follow

Get every new post delivered to your Inbox

Join other followers:

%d bloggers like this: