Jump to content

lottielu

Members
 View Profile  See their activity

  • Posts

    6

  • Joined

  • Last visited

Reputation

0 Neutral

About lottielu

Personal Information

  • Location
    Northamptonshire
  1. lottielu
    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 .
  2. lottielu
    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.
  3. lottielu
    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.
  4. lottielu
    Sorry I meant corrupt not crypt.
  5. lottielu
    No it's saying the entire image file is missing. similar as it would do if the image had become crypt.
  6. lottielu
    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.
×
×
  • Create New...