SmartDeploySupport

We have not seen this issue before. Was this a network admin account by chance? Does this happen on all your images? Thanks, SmartDeploy Support

Hi Dennis, Thanks for reaching out. These settings can be configured via the Deploy Wizard at deployment time. You mentioned you're using an Answer File - was this Answer File generated via the SmartDeploy Deploy Wizard, or did it come from some other source? Go ahead and retry these settings via Deploy Wizard, and if the issue persists, locate and email us the following logs/files from the device after deployment: C:\Windows\Debug\Deploy.log C:\Windows\Panther\Unattend.xml You can send these to us at support (at) smartdeploy.com. Please be sure to reference this DeployCentral post in your email, and we can advise further. Regards, SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL

Hello Mike, I noticed you sent us an e-mail to support@smartdeploy.com which I've responded to. Please take a look and get back to us. Thanks, SmartDeploy Support

Hello, We don't recommend running scripts off network shares. We have had some customers be successful, but there are times that the network drivers aren't initialized in time for the script to run. It's a timing issue. We would recommend putting the script in your pack or on the image itself. Thanks, SmartDeploy Support

Must be something with your image, as the Setup Wrapper has to start the inbox Windows services necessary for Sysprep to run. Did you create this image by creating a new VM, and installing Windows from a Windows VL .iso or disc? Please try creating a new VM that way, once it's at the desktop, shut it down, capture it and then test deploying with it. If you continue to have issues, please email us directly at support@smartdeploy.com Thanks, SmartDeploy Support

Make sure you have started up and shutdown your VM several times after running updates. If you have done that, and still recieve the error, then the registry keys probably didn't get properly cleaned up. In your virtual reference machine, check the following registry keys. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackagesPending If that key exists, and you are sure all the updates are complete, you can delete it and it should resolve the issue. Thanks, SmartDeploy Support

Hi James, We see this issue occasionally with devices that have a small SSD cache included, so that's a possibility. Let's have a look at your WinPE deploy log, and that should hopefully tell us what's going on. Boot to SmartDeploy media on the device. Launch Deploy Wizard. Click through the same steps as before to reproduce the "Not enough space" error. When you see this error, close the error, and close Deploy Wizard. Click the link at the bottom of the Welcome screen to open a WinPE command prompt. Enter the following commands, pressing Enter after each one: X: cd X:\Windows\Temp Notepad Deploy.log In the Notepad window, click File | Save As (or press Alt-F-A), and save the log to your external thumbstick. Go ahead and send this log to support (at) smartdeploy.com, and we'll take a look. SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL

You can capture both images into a single image file (.wim). If you do this then the Deploy Wizard will have a drop down for which image index you want to deploy. When running the Capture Wizard, browse to the existing .wim file, and you will be prompted to add this image to the existing file. Thanks, SmartDeploy Support

If you're only using a single physical disk, can you just skip the RAID configuration entirely? TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL

Hi Scott, RAID is not generally an issue with SmartDeploy - although I doubt we've tested much with JBOD, since there's so much variability in that configuration. Can you elaborate on how the disks are configured? (i.e. how many physical disks configured as how many volumes)? You mentioned that you "can immediately switch the hard drive to be connected to the SATA port and it will boot" - how was it connected before you made this switch? Are you referring to just one of the hard drives in the JBOD configuration (suggesting that SmartDeploy did not see the RAID configuration, and instead deployed to the first physical disk)? SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL

Hi Javier, Unfortunately, the computer assigns the drive letters, not the SmartDeploy media. When you boot to our boot environment the %SmartDeploy_Media% variable is set to reflect the drive letter of the device used to boot the machine. That way you can use that variable no matter your drive structure for tasks, etc. Thanks, SmartDeploy Support

Alan, We don’t currently support Windows 10. We do plan supporting it in the next version that should be out soon. Here is more information regarding Windows 10 support. Thanks, SmartDeploy Support

Hi Javier, Unfortunately, this isn't supported as the product wasn't designed for this. If you deploy without a platform pack, Windows in box drivers will be used and you should be able to get to the desktop. Thanks, SmartDeploy Support

Hi Martin, Using SmartDeploy media, you can apply an image to a VM or a physical machine without any Platform Pack. To do so, you would simply not include any Platform Packs in the same folder alongside the image. You'll be warned in Deploy Wizard that no Platform Pack has been found, but you can click Yes to proceed nonetheless. Capture Wizard will always run Sysprep when it captures the image (this is a necessary step for capturing an image to be applied onto another device). Sysprep is also executed on the target device, as a component of Windows setup. This process does not spoil your virtual machine in any way; you can fire up that same VM right after capture, install additional Windows Updates (for instance), then shut it down and recapture it. I mention all of that by way of background. Your specific scenario - using a SmartDeploy-captured WIM to recreate your virtual reference machine - is not a recommended backup solution, but there's no theoretical reason why it wouldn't work, except perhaps that you would use up a rearm when you apply the image, so there would be a limited number of times that this could be done. And of course, with multiple Sysprep runs involved, it's possible that a resulting deployment might fail, and our first recommendation at that point (based on this history) would be to rebuild your reference VM from scratch. So our best recommendation, if you're concerned about backups (a fine thing to be concerned about!) is to back up your VM to a safe location, perhaps multiple locations, so that you'll always be able to spin it back up and capture it. Please let us know if you have any other questions. SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL

Hello, Only the drivers for the target machine will be installed. A C:\Platform directory will be created on the deployed machine with the drivers that were used. Thanks, SmartDeploy Support

We have verified the latest packs are on our website. You shouldn't be receiving that error as that is the old task. If you click on the BIOS node the following task should be displayed: cscript.exe [PlatformFolder]\BIOS\Setup.vbs Thanks, SmartDeploy Support

Hello, It looks as though you're using an outdated pack of the Compaq Elite 8300 pack. They were last updated on 8/8/2015 to fix this issue. Download the latest versions and you should not recieve that error. It does look like the Compaq Elite 8300 All in One needs to be updated though. Are you using the All in One pack? Thanks, SmartDeploy Support

Hi Scott, We'll need some logs from the affected device to diagnose the issue - go ahead and pull these, then email them to us at support (at) smartdeploy.com: C:\Windows\Debug\Deploy.log C:\Platform\Dism.txt C:\Windows\Inf\Setupapi.dev.log Be sure to include a link to this DeployCentral thread with your reply. SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL

Hi Tom, It's an older model, but it's likely that the pack needs an update; it hasn't been touched since 2013. Go ahead and submit the Platform Pack Request Form (here), and we'll see if there are updated (or alternate) hard disk drivers available. SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL

Which version of the pack are you having issues with? Windows 7, 8 or 81?

Hello, We haven't seen this before. Can you let us know the steps taken to receive this error? Is this from booting from WDS boot media? Thanks, SmartDeploy Support

Hi Flexim, · Open a command prompt and perform the following commands: o Diskpart o List Disk (determine which disk is your USB stick, probably disk 1 if you only have 1 hard drive) o Select Disk 1 (use the correct disk number here) o Detail Disk (ensure you have your USB drive selected) o Clean (this destroys all data) o Create partition primary o Active o Format quick fs=fat32 o Assign letter e: (any drive letter that works is fine) o Exit Run Media Wizard again and let us know your results. If you still encounter issues, we can get a log and see what may be going on. Thanks, SmartDeploy Support

Hello, If i'm understanding correctly, you won't need to update the SmartDeploy.xml and run your task as a pre-image task. Here is a good forum post regarding tasks: http://deploycentral.com/topic/272-adding-a-task-or-multiple-tasks-to-smartdeploy-image/?hl=tasks Thanks, SmartDeploy Support

In addition to a number of fixes and performance improvements, SmartDeploy Enterprise v1.1.4000 and later supports UEFI enabled devices, such as the Microsoft Surface Pro 3. If you’re upgrading from a previous version of SmartDeploy, you may notice a few changes. We’ve prepared this blog post to help you understand what has changed in order to make your upgrade process as smooth as possible. Simple SmartDeploy upgrade Simply download and run the installer. That’s it! Your previous SmartDeploy license key automatically carries forward into the new version. If you need to install SmartDeploy on a different computer and do not have your license key on file, email licensing@smartdeploy.com. Track your SmartDeploy license utilization SmartDeploy, like most enterprise software offerings, is licensed on a per-machine basis. You need a license for the total number of computers that you deploy with the software. You can login and see what devices that you’ve deployed through the SmartDeploy Licensing Portal. UEFI support requires Windows PE x64 There is a new dropdown available in Media Wizard to create x86 or x64 boot or deployment media. Support for UEFI requires an x64 WinPE environment, and this is now the default option in SmartDeploy. Optionally, you can still select an x86 environment to deploy x86 or x64 Windows operating systems to legacy devices. UEFI requires FAT32 media formatting UEFI is an industry standard replacement for legacy BIOS. All UEFI-enabled USB media must be formatted with a FAT32 file system. SmartDeploy has always used NTFS formatting for boot media but in order to support UEFI devices, we had to make this change. Existing customers that have WIMs or PPKs larger than 4GB should be aware of this change. As you may already realize, the FAT32 standard does not support single files larger than 4GB. If you select offline deployment media, SmartDeploy will automatically split WIMs that exceed the 4GB size limitation when you run the Media Wizard. However, if you have a PPK larger than 4GB, you will need to use individual PPKs. SmartDeploy can still process a Default.ppk file that is less than 4GB, but you no longer need to combine PPK files. Simply download each PPK and place them in the same directory. When you run the Media Wizard, browse to that directory and SmartDeploy will take care of the rest. Please note, if you’re currently using network (PXE) boot to distribute your boot image over WDS, or if you’re using USB boot media to point to an image that is stored on a mapped network drive, you don’t need to worry about 4GB FAT32 file size limitations. Your WIM files and Platform Packs will continue to work exactly as they did before. Download the latest Platform Packs We have updated nearly every PPK in the library to support the newer versions of our product as well as new drivers from the manufacturers. Please check the version of the PPK that you have against the latest version on the website. If there is a newer version available, it is recommended that you use that version. After you’ve updated you PPK library, simply re-run the Media Wizard before your next deployment.