Jump to content

Recommended Posts

Posted

Hi, im totaly stuped deploying ltsb2106,

 

Im using WDS on server 2012r2 , capture seems to be fine but im unable to deploy, even if it turn off all unatted and answer files and tell it not to join a domain.

 

I have attached Setupact.txt and setuperr.txt (were .log but i dont think i can upload) and i have had to cut tons out as a max of 400kb is tiny..

 

I would be greatfull if anyone could help me out here

setupact.txt

setuperr.txt

Posted

Thanks Colin

 

Are those files in the original image (install.wim) file??

If so, could you backup the wim file, mount the original, remove those two files, and try the deployment again.

Alternatively, change the two files to look like the following...

unattend.xml


 
   
   *
 

 

specialize.uaq


               command="C:\Windows\SYSTEM32\RUNDLL32.EXE"
           arguments="shsetup.dll,SHUnattendedSetup"
           identity="Microsoft-Windows-Shell-Setup, Culture=neutral, Version=10.0.14393.0, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
           manifestPath="C:\Windows\Winsxs\Manifests\amd64_microsoft-windows-shell-setup_31bf3856ad364e35_10.0.14393.0_none_ffcf3e270052d303.manifest"
           pass="specialize"/>

Posted
Just out of interest, what's the reason you're not doing a vanilla build and capture with MDT handling the sysprep?

 

 

I have no idea how, I’ve only ever used WDS, I have been looking for some good online video training,as i would like to know how how to deploy app etcv to windows 10 i have previously used CBT nuggets which were excellent but are too expensive

Posted

The Deployment Fundamentals books by Johan Ardwidmark and colleagues are indispensible, in my opinion. They're light on theory but great as practical how-tos. You need Volume 6 - Deploying Windows 10 using Microsoft Deployment Toolkit by Ardwidmark and Nystrom.

 

We're deploying 1607, and have had no problems. Just created a simple build and capture reference image with just the OS and Office 2016, then a separate deployment share that deploys that image with applications depending on the target machine's role and/or model.

  • 1 year later...
Posted
Did anyone find an answer to this issues please? We are having the same issue with Windows 10 LSTB image not applying after it has been captured. I should say that we have been trying this for several weeks now and we are able to take a basic image of Windows 10 Enterprise through WDS and apply it to another machine when captured with no issues or errors at all. If wee try the same basic image using Windows 10 LSTB however, despite it capturing ok without errors when you try and deploy the image you get an error message saying that the file is missing or has been moved to another location. This is of course not the case. We have already tried the suggest answer above with the install.wim and unattend files. this did not provide a solution. We have also removed the Windows.old files, as this has caused issues with Windows 10 Enterprise in the past. Any solutions or ideas would be great.
Posted
No it's saying the entire image file is missing. similar as it would do if the image had become crypt.

 

Sorry I meant corrupt not crypt.

Posted
No unfortunately not. It captures fine so there are no error messages. it;s just when you go to deploy it's like the image is no longer there. I have just taken a basic blank image (created an image with just Windows 10 LSTB, removed Windows.old files, sysprept and imaged)again it captures fine but when you try and deploy to another machine it tells you that the image is not there. the WDS is not at fault either as I have tried the same with Windows 10 Enterprise and this worked fine both capturing and deploying. It's just LSTB which has an issue somewhere.
Posted

i assume you have the windows.old folder as the OS has been upgraded at some point, if you attempt to deploy the image without doing anything to it so straight off the media does it still fail.

 

i will be honest and think that if you used MDT for controlling your imaging process and just using WDS to provide PXE booting it will be easier to trouble shoot

Posted
Yes it still fails, we tried that first. MDT for what we have to install is not an option for us, but thank you for the suggestion anyway.
Posted
Any particular reason for needing to deploy a full image rather than just the OS? Found it was generally less work all round deploying the OS from the DVD image or is there a particular reason that MDT isn't doable? (as you'd then need to use that to push the apps you're no doubt embedding in the image). Very much a K.I.S.S. approach.
Posted
A full image is required for our proposes in this case. Given the number of applications/type of applications this is not a workable option for us. Either way the real issue that for some reason the image will not capture and deploy when using Windows LSTB. I appreciate your help, we are going to run a few further tests .

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



×
×
  • Create New...