Last active 2 weeks ago

  1. 2 weeks ago
    Mon Nov 5 06:49:09 2018
    W Wizman87 posted in Cloning And Drivers Question:.

    Ah. That doesn't sound too bad!

    Normally during image deployment, CloneDeploy changes the computer name in the Windows registry if no answer file is found in the image. However, that functionality doesn't seem to be working at the moment. CloneDeploy most likely needs a small update to fix that functionality. As far as the answer file goes, once sysprep is run, that is when the answer file gets executed. As CloneDeploy is not currently changing the Windows registry, you will have to make an answer file for auto renaming. You will also have to add sysprep tags under Sysprep in the image profile for any changes that you want CloneDeploy to make to your image. Overall, it's generally best practice to upload pre-sysprepped and sysprepped images.

    Usually, what you would do first is prepare a Windows image in audit mode before running sysprep. While in audit mode, you would install any drivers, software applications, scripts, and unattend.xml answer files. Then, you would upload the pre-sysprepped image with CloneDeploy. After that, you would run sysprep on the Windows image. Once sysprep has been run on the Windows image, the computer shuts itself down. This is when CloneDeploy steps in with the sysprep tags. Also, this is when you would upload a second image with CloneDeploy. This second image is the sysprepped image. The first pre-sysprepped image will be used for updating the image later on down the line. Next, the answer file gets executed after boot. However, before any execution of the answer file takes place, CloneDeploy changes your defined sysprep tags that were under Sysprep in the image profile. After CloneDeploy is done changing the syprep tags, the Windows image executes the answer file and boots up like normal (e.g. into OOBE mode or the desktop).

    Does that help at all?

  2. Sun Nov 4 18:28:23 2018
    W Wizman87 posted in Cloning And Drivers Question:.

    Anytime, Iheartautomation.

    I was recently looking into using PDQ Deploy alongside CloneDeploy as well, though the free "trial" seemed to have limited functionality. I'll have to check it out some time. As for changing the sysprep tags, the sysprep tag entries are entered manually within the image profile (e.g. under Images > [Image Name] > Profiles > View > Sysprep).

    To create an unattend.xml file for sysprep, you will have to use Windows System Image Manager (SIM) , which is included in the Windows Assessment and Deployment Kit (ADK) . Have a look at this forum post for more information on auto renaming: https://forum.clonedeploy.org/912-win-10-imaging .

  3. Sun Nov 4 08:17:58 2018
    W Wizman87 posted in Cloning And Drivers Question:.

    To help chime in here, my college's computer lab runs a near identical setup, but with Dell workstations. Currently, we have DHCP running on a Windows 2016 Standard Edition server. Though, you can certainly use CloneDeploy for DHCP if you want. For PXE booting, the DHCP service is configured with the PXE boot file option. All of the workstations are configured with the PXE boot option set to enabled (e.g. in the BIOS). This was very easy to do and all configured in an isolated network.

    As far as HP restore partitions go, the partitions can all be kept in tact with CloneDeploy. If you want to separate or change any of the partitions, you can always use a custom schema in CloneDeploy for your other workstations. Also, you can push one image out with all of your drivers and applications installed. Though, I highly recommend that you keep a previous image as a backup just in case something goes wrong during image deployment. Be sure to upload an image before running sysprep as well.

    Have a look at these forum posts to get an idea of which method you might prefer to use for image deployment: https://forum.clonedeploy.org/69-domain-join-install-software and https://forum.clonedeploy.org/574-clone-deploy-the-v-way

    As for auto renaming workstations, you will have to use sysprep in some way to do this. CloneDeploy can be configured to change the sysprep tags (e.g. computer hostname tag) in your unattend.xml file during image deployment. Take a look at the official documentation for that here: https://clonedeploy.org/docs/global-properties .

    I hope that helps!

  4. Fri Nov 2 15:39:45 2018

    Ah, I see. I will have to look into using sysprep on our workstations. Currently, we're using Windows 8.1 Enterprise (Version 6.3 Build 9600). Though, we're planning to roll out a Windows 10 Enterprise image very soon.

    Given our available options, we will most likely have to use a base Windows 10 Enterprise image with an unattend.xml script. At the moment, we're using a pre-deployed workstation for our Windows 8.1 Enterprise image. In order to generalize our Windows 8.1 Enterprise image, we'd have to either use sysprep or start over from scratch with a base image and unattend.xml script. During image deployment, the unattend.xml script would have to generalize the image with sysprep.

  5. Wed Oct 31 22:18:30 2018

    I was able to deploy our image to one of the workstations today. Needless to say, unchecking the "Change Computer Name" option in the image profile deploy options worked perfectly! Thank you so much!!

    With that said, is there any possible way to get the "Change Computer Name" option working? We currently have 24 workstations in our computer lab. It would be amazing if we could rename them according to their name designations and MAC addresses in CloneDeploy.

    Also, here are the logs from today.

    Thanks again!

  6. 3 weeks ago
    Tue Oct 30 13:51:01 2018

    I'll definitely try turning off that option come Friday! Last week, I tried deploying with a custom schema, but to no avail. The workstations would still not boot. I'm also planning to try out some different upload and compression options next time. Are there any big differences between the compression levels and gzip, lz4, and none compression options? I'll be sure to post some new logs on Friday. Thanks for the response!

  7. Thu Oct 25 05:28:52 2018
    W Wizman87 started the conversation NTFS Disk Repairs After Image Deployment.


    I am currently running into an issue with the image deployment process in my college's computer lab. Long story short, the upload and deploy processes both work flawlessly with our Windows 8 workstations. However, after image deployment, the workstations all receive the following error message upon boot: "Repairing disk errors. This might take over an hour to complete."

    I believe I followed all of the common suggestions, such as: disabling hibernation with powercfg, ensuring no windows updates are marking the disk as dirty, running a chkdsk /F, defragmenting the disk before upload, etc. Likewise, I also attempted uploading the image with and without the shrink partition option. If someone can take a look at the attached logs, I would be greatly appreciated! Any help, feedback, or advice is most welcome!

    Luckily, my college's computer lab has CrucibleWDS for imaging the workstations. Though, after the image deployment process is confirmed to be working, we'll be migrating everything over to CloneDeploy!

    With that said, I truly cannot appreciate the author enough for creating and supporting both of these software applications over the past few years!

    Thank you so much!

  8. Wed Oct 24 22:03:12 2018
    W Wizman87 joined the forum.