Jump to content

Jeff Harris

  • Content count

  • Joined

  • Last visited

Everything posted by Jeff Harris

  1. 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.
  2. Unattended deployment not unattended

    You can create an empty platform pack that may help in this case.
  3. You'll want to have a site-local host running SmartDeploy, and any clients on that site configured to use that host. You can do a one-time copy of your corporate image to that host, then use RDP to download packs, create answer files and network deployment packages, and initiate your network deployments.
  4. Automate Wifi Connection

    (UpdateD) You could do something like this; 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. I'd be interested to see the file count between the 2 images once complete. Capture time is most related to the make up of the reference VM disk, but can also be affected by disk/network speed, or any real-time file scanning in place. It sounds like you would need to look at what's in your reference VMs.
  6. Keyboard

    Steve, we may need to look at your logs to get a better idea of what's going on. Reach out to support@smartdeploy.com for assistance.
  7. Sysprep with CopyProfile is sort of broken in Windows 10 1709. Here's a lengthy TechNet post with users reporting different behavior. We're hoping it's resolved in the next update. There are some work-arounds to get it working well enough, but nothing seems to be a magic bullet.
  8. I've seen instances where Windows Defender real-time scanning affects capture time. I would look at that first. Also; SmartDeploy does a file-by-file copy to create the image. The difference in your images doesn't just have to be file size to make a difference in image creation time. The 35GB and 40GB VHD sizes aren't necessarily a reliable indicator of what's being used by files.
  9. Keyboard

    Here's a link to a blog topic that covers manually specifying the local settings in greater detail. You'll have better luck explicitly setting the language this way.
  10. Keyboard

    The Answer File wizard offers you the opportunity to set the locale for the deployment. Have you set your locale there?
  11. Deploying Windows 10 sysprep error

    We do recommend to avoid in-place upgrades, of Windows, and any other software if possible.
  12. Migration Stuck/Paused

    Glad to hear it completed the copy. That stage of the deployment is using the normal Windows copy commands. There's no standard time to copy regardless of size since given all the factors that can affect the copy time. If there's an error, or it doesn't progress you can cancel to return to the SmartDeploy boot menu, open a command prompt and locate the X:\Windows\Temp\Scanstate.log file. This can shed some light on what's happening. (Alternatively, you can click the Collect Logs button on the SD boot menu and this log will be included in the zip file.)
  13. CaptureVirtual Disks. Capture returned: 87

    This sort of error could be caused by; Anti-Virus or some other security software installed on your reference VM Snap-shots of your reference VM The reference VM configured to use EFI mode Anti-virus software on your SmartDeploy host I would address those items first, and try again. If you need to have A/V software on your image, I recommend using the Tasks pane to script the installation post image. Following that, if you still have issues try a warm capture which is outlined on page 76 of the user guide. https://www.smartdeploy.com/wp-content/uploads/SmartDeployUsersGuide_V2.pdf
  14. Computer Management

    This isn't a common problem. Something like this would require a review of the logs after deployment. You can contact support@smartdeploy.com (attach the logs from deployment) and we'll take a look. My first step would be creating a new answer file, and new boot media and re-trying deployment to rule out those pieces as potential culprits.
  15. M.2 SSD

    We have changed methods for this particular driver. We have a patch for installing direct to your Windows 7 reference VM, instead of placing the driver in the platform pack. Contact support@smartdeploy.com for details and access to this patch.
  16. New to SmartDeploy

    As of this time, SmartDeploy does not install software packages on their own. You would need to include your desired software in your image by installing in on your reference VM before capturing.
  17. WDS Image error

    You can use the SmartDeploy Cmd Prompt command; smartwim /info [wim file] to view details of the wim to make sure it's ok. Other than that I'd make sure you have the latest version of SmartDeploy installed, and try uploading a different boot wim to your WDS host to rule out a problem there. If you have a support contract with SmartDeploy, you can contact support@smartdeploy.com for additional help.
  18. WDS Image error

    You'll need to make sure you are using the Media wizard to create and upload your WDS boot media, before uploading your Windows 10 image file. Here's the link to the SmartDeploy guide for integrating with WDS. Try starting back at the top of this document. https://www.smartdeploy.com/wp-content/uploads/SmartDeploy_WDS.pdf
  19. Desktop Background image black

    I re-sent that file attached to a private message. Check that and let us know if you can access it.
  20. You're installing Smart Deploy? Check the properties of the downloaded setup.exe file to make sure that it's not being blocked. If you have any anti-virus or other security software installed; that could also be interfering with installation.
  21. It looks like you contacted support, but for anyone else who's reading this thread with the same problem; I would manually check the wim info by opening a command prompt using the tile in the Tools section of SmartDeploy, and then running smartwim /info [pathToWimFile] The Answer File wizard uses this same tool to retrieve this info, so you can use it to verify the retrieval of the image name without stepping through the wizard. If it's not working, I would try copying the wim file locally.
  22. SmartDeploy has the ability to do console initiated deployments. If you install the SmartDeploy Client on a computer, and it can reach the SmartDeploy console system, you could "push" a deployment form the console to the remote computer. The caveat here, is remote/VPN network connections may not office the best performance and could lead to problems in the imaging process.
  23. SmartDeploy.iso

    The files in "C:\Program Files (x86)\SmartDeploy\SmartDeploy Enterprise" would be SmartDeploy_x64.iso and SmartDeploy_x86.iso. If those files are missing, then you'll need to re-install SmartDeploy. There's no official 'wds.iso' so I'm assuming that's just DVD boot media that was created by someone, and named as such. Whenever you update SmartDeploy, you have to re-create your boot media. I suspect your wds.iso if from an older version. Also; the absence of any wims/images following the 'get-mounted' is good, as it means there isn't a mounted image stuck. That would be related to a problem creating new boot media. But if the SmartDeploy_x64.iso and SmartDeploy_x86.iso files are missing; you need to re-install SmartDeploy.
  24. You can send them a USB drive with SmartDeploy boot media on it, but it's going to either follow the answer file as an unattended deployment, or require action from a user at the remote site. You could in theory perform deployments remotey, while using USB if you have VPN and KVM access to the systems.
  25. Negative delta

    I would expect your assumption to be correct. But, as with most things, I'd recommend thorough testing.