Last active 3 months ago

  1. 3 months ago
    Fri Sep 7 20:02:03 2018
    N NMGAdmin posted in Image deploy not getting new SID.

    I am not doing a manual sysprep. I was under the assumption that the answer file and the image deploy would be doing the sysprep.

  2. Fri Sep 7 20:00:54 2018
    N NMGAdmin posted in Win 10 Imaging.

    Thank you hrumph2!

  3. Thu Sep 6 19:52:00 2018
    N NMGAdmin started the conversation Image deploy not getting new SID.

    I have been able to capture an image and deploy it to a new machine AND have the computer name change! Yay! But, since this image will be applied to many PCs that will all be added to a Windows 2016 AD network, the SID of each PC needs to be unique.

    Can the image deploy generate a new SID? Is there a setting for this in the unattend.xml file?

  4. Thu Sep 6 13:41:20 2018
    N NMGAdmin posted in Win 10 Imaging.

    Ok, I have a sample file now. Does the unattend.xml file goes on the PC that is being captured as the source image?

  5. Thu Sep 6 13:08:19 2018
    N NMGAdmin posted in Win 10 Imaging.

    Aaaaahhhhhhhhh .... do you have a sample of the most basic answer file that would simply allow for a computer to be renamed after the image was deployed?

  6. Thu Sep 6 13:00:05 2018
    N NMGAdmin posted in Win 10 Imaging.

    That is kind of where some of the prior posts never really showed any solutions. What are the steps, sections of the program, etc. to create the contents of the "answer file"?

    I would go into Global Settings and set the sysprep tag for <computername></computername> and the content to be the new name.

    It didn't work.

  7. Wed Sep 5 17:30:03 2018
    N NMGAdmin posted in Win 10 Imaging.

    I have already tried using Microsoft WDS but that led to errors with the capture routine not finding a boot device in the PC. I needed to load into the image the disk drivers or something and it never worked. Similar results with Microsoft MDT.

    I have some software deployment using AD and GPO policies in the past. If I can't get an imaging solution to work, this is the route I will go. Just seems like there should be a better way than this. And, for machines that are already deployed and just "break", you then have to fresh install Windows 10 first and then add to domain, etc. ... just tedious.

  8. Wed Sep 5 17:25:44 2018
    N NMGAdmin started the conversation Win 10 Imaging.

    I love Clone Deploy and how simple it is to setup. But, I've been having trouble getting my Windows 10 pro machines to image properly. I have looked through the forum and there are a lot of posts, but not many have a final answer posted. I can capture the image from the PC. I can deploy the image to a new PC. I can't, however, get the machine to sysprep properly or change computer name.

    My environment is a Windows 2016 AD network with 75 brand new Dell PCs. I have taken 1 machine new out of the box and performed all the windows updates, installed all my ERP software, anti-virus, MS Office, etc. This PC is not part of the domain at all yet. This is my "golden goose" PC. I would like to capture this machine's image and deploy it to the other 74 machines.

    Can I use this post to solve my issue and become a case study on how to properly capture and deploy Windows 10 Pro images? Is anyone willing to help me figure this out?

    I will post every screenshot and setting necessary to make this a fully functional case study to help me and those in the future.

  9. Tue Sep 4 21:08:53 2018
    N NMGAdmin joined the forum.