Jump to content
DeployCentral

Recommended Posts

Is anyone else having an issue with version 3030 and images added through WDS? Whenever I import an image into WDS as an install image and WDS creates a Res.RWM file (so multicast is supported) I get an Insert Disk 1 prompt after the entire image is pushed out from the server. It gets to about 10 seconds left then I get the prompt and it does not work.

If I revert to version 3005 in my console, and recreate the boot media (booted through PXE boot from WDS server) it will push out the image fine but will cause a bootloop since it is an 1809 image and will not work with that version of the console media.

If I do NOT import the WIM install image into WDS, it will push out just fine using any other method. But this is not ideal since I image about 100 machines at a time in the summers and need proper multicast support from PXE boot within WDS.

I have tried re-creating my images using Virtual Box, Hyper-V, etc. Rebuilding my WDS server multiple times. Completely uninstalling the console and reinstalling, completely starting from scratch on a new console host machine and rebuilding my image. No dice! I am attaching my logs with the hope someone sees something obvious.

MININT-AUSO5BM.Logs.zip

Share this post


Link to post
Share on other sites

Nope... no resolution. Haven't heard any updates from support in over two weeks since they mentioned they would work with their Dev team. I had this issue before with version 3010 and reverting back to 3005 and rebuilding the boot image fixed it too.

Not sure what to do here... the multicast support built into the console is not very reliable when I have tried it. In the meantime I have been setting up MDT on the WDS server in case this doesn't get resolved.

Share this post


Link to post
Share on other sites

I got the deploy log and below is what happens I have been working with support on this. I had it happen twice before and they told me to go back a version. I just updated to 3030 from 3000 and it happened.

1/16/2019 3:29:56 PM : 1  : #mic,GetWimInformationModel,WriteToLog : Current file: Z:\Images\Smart Deploy Images\FS64 Win10 1803 12-18.wim
1/16/2019 3:29:56 PM : 1  : #mic,GetWimInformationModel,WriteToLog : Cached file:
1/16/2019 3:29:56 PM : 1  : #mic,GetWimInformationModel,WriteToLog : Returning information for file: Z:\Images\Smart Deploy Images\FS64 Win10 1803 12-18.wim
1/16/2019 3:29:56 PM : 1  : #mic,GetMaximumSplitPartNumber,WriteToLog : Searching for split parts in Z:\Images\Smart Deploy Images
1/16/2019 3:29:56 PM : 1  : GetMaximumSplitPartNumber,WriteToLog,WriteToLog : System.NullReferenceException: Object reference not set to an instance of an object.     at Common.SmartDeploy.SL.Managers.SmartWIMManager.GetMaximumSplitPartNumber()
1/16/2019 3:29:56 PM : 1  : <.ctor>b__4,ShowModal,WriteToLog : MessageBox : Deploy Wizard : Please insert disc 1.

Share this post


Link to post
Share on other sites

Hello,

This is a known issue. It occurs if the Windows 10 image is 1803 or greater. There is a chance that it won't import correctly into WDS on Server that isn't 2016.  But, not all images have the issue, so you may have luck recreating the image. The older version of Wingapi.dll isn't handling some of the new file properties in 1803.  Unfortunately this is something we cannot fix and it even happens when importing a .WIM that isn't create by SmartDeploy but even dism.exe.

Share this post


Link to post
Share on other sites

I've rebuilt my WDS server using Windows Server 2016 and the issue persists. Rebuilt and captured image countless times. Thanks for the info but I'd rather not rely on luck while using your product.

Share this post


Link to post
Share on other sites

Well the problem is with importing the image with WDS into Install images. I have a captured image folder that I copy the images to after captured and then import them. If I select the image from the captured folder everything works fine.

Share this post


Link to post
Share on other sites

Tom, yes the problem occurs when you import the wim into WDS and the Res.rwm file is created. But you need to do that for multicast to work in WDS. If I just copy the file to the images folder on my WDS server it will work fine but it's only unicast.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×