Jump to content
DeployCentral

SmartDeploySupport

Administrators
  • Content count

    445
  • Joined

  • Last visited

Everything posted by SmartDeploySupport

  1. 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
  2. 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
  3. 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
  4. 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.
  5. Error 1392

    Glad to hear it - please let us know if we can assist with anything else. Regards, SmartDeploy Support
  6. 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
  7. Error 1392

    When you said it originally worked, did you also use wipe and load?
  8. 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
  9. Error 1392

    Usually we see this if anti-virus is installed on the image. Is that the case in this scenario? Thanks, SmartDeploy Support
  10. Platform Pack for Dell Semi Rugged Latitude 5414?

    Hi there, Yes, you can download this pack from within the console. The official model name (as listed by Dell) is Latitude 14 Rugged 5414 - a search for '5414' should allow you to find it. 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
  11. Win 10 Creators Update

    Restart the machine back into the SmartDeploy boot environment and click Collect Logs. Save the resulting zip to a usb or network share and send it to us and we can see what the issue is. Please submit the logs here and refer to this thread https://www.smartdeploy.com/support/support-request/ Thanks, SmartDeploy Support
  12. Desktop Background image black

    To customize copy the wallpaper to default users, I have included the needed files and instructions for setting up Default Profile (Copy Profile) in the CopyProfile.ren attachment, please rename to CopyProfile.zip before opening. That being said, with the Windows 10 1709 release it does seem as it may not work sometimes due to the build in appx packages. This is sadly out of our control, but you can still try it. Sysprep may be resetting the applications settings, what specific application settings are you trying to set? Thanks, SmartDeploy Support CopyProfile.ren
  13. Keep on getting this error when capturing image

    Hello, Please send the following information to us at support (at) smartdeploy.com: -Whether there is any antivirus software running on the computer where SmartDeploy is installed -Whether there is any a/v installed on the VM you're capturing -Whether you have successfully captured a VM on this computer previously Also, please send your Capture Wizard log: C:\SmartDeploy\Logs\Capture.log 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
  14. W10 1709 Deploys as 1607?

    Hi Lee, We really need to see a log set in order to answer this question. Please go ahead and submit one via the Support Form link above. 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. W10 1709 Deploys as 1607?

    If the Windows version in the reference machine library is showing as 1607, then that is how the VM appears to SmartDeploy externally. You'll want to go ahead and power on the VM and run that winver command to confirm which version is installed. 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
  16. W10 1709 Deploys as 1607?

    If you mean within the VM, you can confirm this by running the command winver. Determining this from the captured image (.wim) is also possible, but we'll need to have a look at the log set referenced above. 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. W10 1709 Deploys as 1607?

    Hi Lee, There's really no plausible mechanism for this other than capturing the VM in the wrong state/snapshot (which you've ruled out above), or accidentally deploying an old image. Have you updated your answer file to point to the new image, recreated your WDS boot media, and replaced it on your WDS server? If you've omitted any of these steps, it's possible you're still deploying the old image. If you're not sure which image you deployed, you can retrieve a log set from the deployed device and we can take a look. Boot to SmartDeploy media on the affected device (ideally with USB boot media with no answer file, to avoid starting another deployment and wiping the previous logs), click the Collect logs option, save the resulting zip file to an external location, and email to us at support (at) smartdeploy.com. Note that some organizations restrict sending zip files over email, so you may want to check with your IT department to make sure the email made it out with the attachment. Alternately, you can fill out our Support form, which includes a file upload option. 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
  18. Dell Latitude 3580 - CTRL ALT DEL Screen Message

    This is a new feature in Windows 10 1709. Would need to be disabled via Group Policy, if that's possible.
  19. Media Wizard Unmounting Image Error

    Hi Michael, Glad to hear it's going well otherwise! Per our message, we'll continue troubleshooting this one with the log that you sent via email. For anyone else reading, if you have experienced any errors with Media Wizard, feel free to contact us at support (at) smartdeploy.com, and send your Media Wizard log, which is located in the SmartDeploy directory (default location: C:\SmartDeploy\Logs\Media.log). 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
  20. HP Softpaq Download Manager shows drivers not installed

    Very interesting. We'll test, and if that is the case, we can certainly include those files. Thanks!
  21. HP Softpaq Download Manager shows drivers not installed

    Many of these update programs verify the installed version by looking for application or registry entries left by running the install packages. For the most part with SmartDeploy we install device drivers via Plug-n-Play. Lenovo's System Update tool for example used to have this same issue, buy they have updated it to actually check the installed driver versions, so it works fine now. No real way to fix HP's tool, unless they change it to query actual driver versions. Thanks, SmartDeploy Support Team
  22. Remote Deployment prompt not appearing on some computer

    Hi Stephen, Have you successfully performed any console-initiated deployments? If so - was this on clients that are on the same network and subnet as the ones that are currently failing? Are all of the clients running the same version of the SmartDeploy client as the console version that you have installed? You can check the client version in the Computer Management view, or in Programs and Features on the target device. You can check the console version in the Tools view of the console. If any devices are running outdated version of the client, they will need to be updated. That should occur automatically, but you can uninstall and reinstall the client manually if needed. See P. 40 of the User's Guide for details on how to locate and install the client. As for the USB device failing to boot, that may indicate a hardware problem with the target device, or with your USB media - or a problem with the boot settings in the BIOS of the target device. Try changing the variables a bit: different USB stick, different port, different device - determine whether it's a persistent problem on all devices, or confined to a single unit. Depending on those answers, we can advise further. If you're unable to resolve the connectivity problem with your console-initiated deployments, go ahead and email us at support (at) smartdeploy.com (and be sure to reference this thread), and we can help troubleshoot this further. 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
  23. Try capturing the VM while it’s powered on. You will mount the SmartDeploy_x64.iso to the VM, boot to it and select the capture option. This process is documented on page 76 in our User Guide Thanks, SmartDeploy Support
  24. Upgrade issue

    Hi Kirk, We did change the way databases are stored to localdb, which may take a bit to re-populate. Did they eventually show up? If not, open an administrative command prompt and type: net stop sdeconsoleservice Go to C:\Windows\System32\ and send us the following files: SmartDeploy.mdf SmartDeploy.sdf SmartDeploy_log.ldf Send to support @ smartDeploy .com Thanks, SmartDeploy Support
  25. Windows 10 ADK

    Hi there, We added this check and warning for the Windows ADK installation to the latest version of SmartDeploy, to prevent users from running Media Wizard without the ADK installed, as this will lead to a common failure. At present, it only checks for the ADK in the default install location. However, we have received feedback like this from other users who have it installed on a secondary hard drive, so we will be widening this check to look for the ADK in any valid install location (as recorded in the registry) in a future version. In the meantime, the workaround would be to uninstall the ADK and reinstall it in the default location on C:\. The three required components would be Deployment Tools, WindowsPE, and the User State Migration Tools. You can run the installer from here (1703 is fine at this time): https://developer.microsoft.com/en-us/windows/hardware/windows-assessment-deployment-kit Sorry for any inconvenience, and please let us know if you have any questions or issues - you can reach 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
×