Customize Windows 10 Image in Audit Mode with Sysprep  

Page 19 of 70 FirstFirst ... 917181920212969 ... LastLast

  1. Posts : 5
    WIN10
       #180

    I remember saying ' if you talk like the rooster and don't listen like the turtle you be alone like the fox'!!!! It mean you don't always must have the last word when you talk or you look like the bully.... you have a nice day too
      My Computer


  2. Posts : 17,661
    Windows 10 Pro
    Thread Starter
       #181

    So, I'm on one more ignore list. Acceptable, I have no interest in having a dialog with users who cannot accept the fact they have done something wrong, who rather would like to leave their wrong conclusions posted as facts than see them corrected.

    That being said, guys be careful when sysprepping Build 10547. It seems that once again MS has managed to break the CopyProfile component; since the release of this build yesterday I have some 20+ sysprep runs, various scenarios, all have failed if the CopyProfile was used.
      My Computer


  3. Posts : 4
    Windows 10
       #182

    I am facing issue with computer name after sysprep. My script should ask me computer name after running the sysprep and a script would run that would join the machine to domain. Same settings in the unattended file working fine with Windows 7 and 8.1, but Windows 10 is taking auto generated name of the machine instead of asking the name. CopyName field is empty in the Specialize part of the unattended file. Need your expert opinion.
      My Computer


  4. Posts : 4
    Win 10 Ent
       #183

    Create post, followed along and everything went great creating the image and even building the installation media. I used a volume license enterprise version for the image and have run into one snag that maybe you can help with:

    When trying to use the build I get an error that the product key does not match any of the Windows images available.

    I have tries the old PID file method to no avail. Any pointers?
      My Computer


  5. Posts : 5,478
    2004
       #184

    nazar1968 said:
    I am facing issue with computer name after sysprep. My script should ask me computer name after running the sysprep and a script would run that would join the machine to domain. Same settings in the unattended file working fine with Windows 7 and 8.1, but Windows 10 is taking auto generated name of the machine instead of asking the name. CopyName field is empty in the Specialize part of the unattended file. Need your expert opinion.
    I had the same issue - have a look at the log files in C:\Windows\Panther. In my case it saw the name in unattended.xml but ignored it and generated it's own.
      My Computer


  6. Posts : 17,661
    Windows 10 Pro
    Thread Starter
       #185

    foglema said:
    Create post, followed along and everything went great creating the image and even building the installation media. I used a volume license enterprise version for the image and have run into one snag that maybe you can help with:

    When trying to use the build I get an error that the product key does not match any of the Windows images available.

    I have tries the old PID file method to no avail. Any pointers?
    You need an Enterprise Volume Licencing Key to activate Enterprise. Your domain or network should have a KMS server for this purpose, read more here: Deploying KMS Activation
      My Computer


  7. Posts : 4
    Win 10 Ent
       #186

    Kari said:
    You need an Enterprise Volume Licencing Key to activate Enterprise. Your domain or network should have a KMS server for this purpose, read more here: Deploying KMS Activation
    That is not the issue. I can build from DVD and activate without issue using our VL keys. The error occurs when trying to install Win 10 from the USB media created from the build. I.E. right after you select INSTALL for the initial build.
      My Computer


  8. Posts : 17,661
    Windows 10 Pro
    Thread Starter
       #187

    foglema said:
    That is not the issue. I can build from DVD and activate without issue using our VL keys. The error occurs when trying to install Win 10 from the USB media created from the build. I.E. right after you select INSTALL for the initial build.
    I am sorry but I do not understand that, "select INSTALL...". You should not have that selection when deploying, you simply mount the deployment image and the installation (deployment) will be automatic.

    • Configure your image in Audit Mode
    • Create the Answer File
    • Sysprep
    • Capture the image
    • Deploy

    That's it. The Microsoft TechNet article I linked to in my previous post explains the procedure.
      My Computer


  9. Posts : 4
    Win 10 Ent
       #188

    Kari said:
    I am sorry but I do not understand that, "select INSTALL...". You should not have that selection when deploying, you simply mount the deployment image and the installation (deployment) will be automatic.

    • Configure your image in Audit Mode
    • Create the Answer File
    • Sysprep
    • Capture the image
    • Deploy

    That's it. The Microsoft TechNet article I linked to in my previous post explains the procedure.

    1. You link for was setting up a KMS host and configuring the environment for use.
    2. we are not deploying an image through SCCM or WDS. We are using a USB drive that was configured to install Win 10 at boot-up.

    The "INSTALL" selection is the same here as if you were inserting the base VL DVD and installing Windows as a fresh install.
      My Computer


  10. Posts : 17,661
    Windows 10 Pro
    Thread Starter
       #189

    Yes, the link was to TechNet article about KMS activation. That's what you have to do.
      My Computer


 

Tutorial Categories

Customize Windows 10 Image in Audit Mode with Sysprep Tutorial Index Network & Sharing Instalation and Upgrade Browsers and Email General Tips Gaming Customization Apps and Features Virtualization BSOD System Security User Accounts Hardware and Drivers Updates and Activation Backup and Restore Performance and Maintenance Mixed Reality Phone


  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 10:13.
Find Us




Windows 10 Forums