Jump to content

All Activity

This stream auto-updates     

  1. Yesterday
  2. As Support mentioned, volume licensing is the correct way to go about this. But we've had luck pulling the OEM key from BIOS using something like ShowKeyPlus, then activating with that key. There are ways to automate this with a PS script.
  3. Last week
  4. Earlier
  5. Deployment Wizard - Not enough disc space?

    I've seen this sort of failure with Wipe and Load in instances where the target devices previously had Windows 7 installed, and the image is for WIndows 10. The reason is that the system partition for Windows 7 is smaller than 10, and thus it can't fit. We always recommend using Wipe and Load whenever possible.
  6. To follow up, for some reason it looks like our deployment doesn't like the "Wipe & Load" option now. The "Recreate drives" option seems to be working. We have three machines currently installing the image.
  7. Just to add to this, It doesn't appear to be related to network deployment. We just made another offline media USB stick and tried to image one of the additional laptops and received the same error.
  8. We have 10 brand new, same model laptops that we are trying to deploy. We have tested deploying to one of them via an offline USB stick. We were wanting to test deployment via usb boot media accessing the image over the network. The device we have previously imaged with the offline USB successfully was able to re-image itself with just the smartdeploy boot media. The rest of the laptops we have tried to do the same way and the deployment wizard cancels and puts an error up stating that there wasnt enough disc space. Any ideas?
  9. Imaging brand new pc

    Hi there, Network-based deployment packages can only be used for console-initiated deployments, which can only be performed for target devices that have a functional OS and the SmartDeploy client installed. For new computers - which may have no OS installed, or may have an OEM image installed - we would recommend using some other method to boot these devices. PXE boot is indeed an option, but it requires integrating SmartDeploy with Windows Deployment Services - see our white paper here (direct link to PDF) for details. You can also boot the target devices using USB boot media, or offline deployment media (see P. 34 of the User's Guide for detail on the various media types available). Feel free to shoot us an email at support (at) smartdeploy.com if you have any questions or issues. Regards, Glenn SmartDeploy Support 888.7DEPLOY toll-free _____________________________ SmartDeploy® Learn about our award winning Windows deployment solutions www.smartdeploy.com www.deploycentral.com Twitter: @SmartDeploy Facebook: SmartDeploy Spiceworks: Spiceworks
  10. Imaging brand new pc

    I have a dozen brand new computers that have never been turned on so the SmartDeploy client isn't installed. I want to PXE boot these computers to the network and have a package be deployed to the computer. Where are the steps to do this in the manual? I have already created 2 deployment packages for testing, but I don't see where to get a new computer to find the package and install
  11. Unattended deployment not unattended

    You can create an empty platform pack that may help in this case.
  12. I built a package with an answer file that is supposed to be unattended. The particular machine I am working with does not have a platform pack as all needed drivers are built into Windows 10 (HP Folio 13). In the middle of the "unattended" deployment it stops to tell me there is no platform pack for this machine and asks if I want to continue anyway. Is there a way to prevent this? I really want the entire process unattended. Thanks
  13. Win 10 Fall Creator's Update in place upgrade on ref image?

    I agree with eburnett. I"d like to have SmartDeploy installed on a server (always on) but be able to run a console from my desktop and create media to the USB drive at my desk rather than in the server room. Also, like for SDE to recognize fully being installed on a drive other than C:\ (And Windows adksetup installed on a drive other than c:\
  14. Win 10 not Activating on new deployment

    Hi Don, OEM licenses do not include reimaging rights from Microsoft. We have had some customers report success with such licenses, but it is inconsistent and unreliable (by design), as the license is only intended to be used to revert the device back to its original factory image. SmartDeploy has no interaction with this process, so we have no control over whether or not Microsoft allows the device to activate if you do not provide a license key for us to pass through at deployment time. Our recommendation is to look into getting a volume license. We are not a volume license reseller, but we can put you in touch with one - go ahead and email us and we can send you their info. Regards, Glenn SmartDeploy Support 888.7DEPLOY toll-free _____________________________ SmartDeploy® Learn about our award winning Windows deployment solutions www.smartdeploy.com www.deploycentral.com Twitter: @SmartDeploy Facebook: SmartDeploy Spiceworks: Spiceworks
  15. no product key was entered in the answer file of the image that worked. After the new pc booted up, the OEM license would then be activated. Maybe I am missing something. Is there a support telephone number that I can call? Don
  16. Win 10 not Activating on new deployment

    Hi Don, Activating Windows on the reference VM has no bearing on whether it will activate on the target PC. The Sysprep\Generalize process which runs on every image at deployment time strips out any existing license info from the image. SmartDeploy provides two opportunities to enter a Windows product key - either in Capture Wizard (in which case it is hashed and written into the metadata of the image to be used at deployment time), or in Deploy Wizard (in which case it is written into the Sysprep Unattend.xml to be used at deployment time). If you do not provide a Windows product key at one of these times, then we cannot guarantee that the target device will activate. If you have any questions, feel free to email us at support (at) smartdeploy.com Regards, Glenn SmartDeploy Support 888.7DEPLOY toll-free _____________________________ SmartDeploy® Learn about our award winning Windows deployment solutions www.smartdeploy.com www.deploycentral.com Twitter: @SmartDeploy Facebook: SmartDeploy Spiceworks: Spiceworks
  17. I created a VM image and deployed it without any probs. Had a hardware problem and had to install SD on new pc. Created a new VM image and activated Win 10. New deployments will not activate now Win 10. Any suggestions? Thanks Don
  18. I will give this a try. Thanks.
  19. Preconfigure Wireless Network Settings ?

    On a workstation that's connected to the network, run the following command: (You may need to verify your interface name) netsh wlan export profile name="NameOfWirelessNetwork" folder=c:\temp interface="Wireless Network Connection" Then copy the NameOfWirelessNetwork.xml file to a place on your reference VM like C:\Temp\ Then you'd add a 'At First Logon' task to your Answer File, using the Tasks tab in the Advanced settings of the Answer File wizard with the following command: cmd /c netsh wlan add profile filename="C:\Temp\NameOfWirelessNetwork.xml" Alternatively, you could keep the xml on a network share, and use GPO to import the wlan profile. You may also need to do some tweaking to the xml file dpending on which security method you use. You an find examples on TechNet for this.
  20. Is there a way to preconfigure wireless networks that we would like the imaged devices to connect to?
  21. Error 1392

    Glad to hear it - please let us know if we can assist with anything else. Regards, SmartDeploy Support
  22. Error 1392

    I actually found the error in event log. The filename was typed incorrectly. After correcting that the image deployment and first boot install completed successfully. Thank you for your help!
  23. Error 1392

    Can we please see your C:\Windows\Debug\Deploy.log from the deployed machine where the task did not work? Thanks, SmartDeploy Support
  24. Error 1392

    Yes. I have gotten a step further by formatting the partition Windows was originally installed on. The image installed successfully, however the first boot install does not appear to have worked. Are there any logs that I can check to figure out what went wrong with that?
  25. Error 1392

    When you said it originally worked, did you also use wipe and load?
  26. Error 1392

    I have tried that also. I should mention that the disk option I am using when deploying the image is wipe & load drives. If there is any other information that might be useful let me know and I will try to provide it. Thank you.
  27. Error 1392

    Have you tried doing a full format on the USB stick? If not, try performing a full format on the USB, then rerun the Media Wizard and recreate your boot media. Let us know your results. Thanks, SmartDeploy Support
  1. Load more activity