Jump to content
DeployCentral

Jeff C

Members
  • Content Count

    6
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Jeff C

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. My apologies, I have been on other projects and never returned to this topic. I know this is a very late reply, but the answer is no. I did not put the product key in the deploy wizard. That said, I have had the best success when the newly imaged computer is started for the first time with an active LAN connection (ethernet) rather than WiFi. My total deployments now are around 64, including re-imaging a few machines after employee turnover. I still have not had a single one fail to activate. I'm sure you know this already, but just in case... you cannot upgrade an OS (say from Windows 7 to Windows 10) and have it activate. Windows 10 must be OEM.
  2. I have captured a Windows 10 1809 image. When attempting to create USB media the Wizard proceeds through "creating split image file" and then starts "copying image files". At this point it immediately fails with the message "unable to copy the image file Media wizard will now close". SD version 2.0.3025 This error happened on consecutive attempts. I have now deleted the captured image and am now capturing a new one to try again. I searched for this error and did not find anything.
  3. That worked! The image is still being deployed, but I can already tell the issue has been resolved. Thank you
  4. Thank you, I will give that a try and reply with the results.
  5. I have deployed 50 OEM Windows 10 machines without a VL. What I noticed is that a few machines were activated immediately, whereas others had to be online for anywhere from 24-72 hours before they would activate. But everyone of them did eventually activate with the OEM license.
  6. I have successfully deployed around 50 machines from a USB drive. Today I tried to reimage one of those machines. I created new boot media from SD version 2.0.3005. The first time I tried deploying from this I didn't see the problem in time and my USB drive was overwritten. I had to fix the drive which now had a hidden partition (reformatting by itself was not enough) and then prepare the boot media again. When I booted from the USB, the computer (Dell Latitude 7480) shows the USB drive as being local storage (C:\) and the existing Windows as being Boot (X:\). The USB drive apparently tried imaging itself, destroying the drive contents. I have tried changing BIOS settings to get around this, but so far it seems to continue that way.
×
×
  • Create New...