SmartDeploySupport

Hi all, Certainly - here they are. If you want to customize the Start Menu or Taskbar, then there are new ways to do that for Windows 10 1607 and later. Doing it through Group Policy is probably the easiest most manageable way, but if you want to do it directly then you basically need to create a layout XML file, and then import it. There are a few articles on doing this. http://www.scconfigmgr.com/2016/08/03/customize-pinned-items-on-taskbar-in-windows-10-1607-during-osd-with-configmgr/ http://ccmexec.com/2015/09/customizing-the-windows-10-start-menu-and-add-ie-shortcut-during-osd/ https://msdn.microsoft.com/en-us/windows/hardware/commercialize/customize/desktop/customize-the-taskbar We have one that we use, it’s attached to this post (renamed to .txt). Basically makes an Office Start Menu collection, and then puts Outlook, Explorer and IE in the taskbar. You copy this .xml into the folder below in your reference VM (that is basically what the PowerShell Import-StartLayout cmdlet does): C:\Users\Default\AppData\Local\Microsoft\Windows\Shell\DefaultLayouts.xml Or you can use the PowerShell Export-StartLayout cmdlet to generate an XML of your own, and copy it to the same location. Feel free to reach out to support (at) smartdeploy.com if you have any questions or issues. SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL LayoutModification.txt

Hi Dennis, Hmmm... This is a known bug in a previous version of SmartDeploy, but it was fixed several versions ago. I know you said you're on 2.0.2050 above, but please go ahead and double check that your media was created with this version - you can boot to the media on the device and look in the lower-right corner in SmartDeploy WindowsPE to confirm. Assuming it's the correct version, this could be a recurrence of the same bug under slightly different conditions. Would it be possible for you to grab a log set from a device that has experienced this failure? It's easiest to do this with SmartDeploy USB media - you can then boot to USB, click the Collect logs button, and save the resulting zip to the USB stick to send with your reply. Then you can email this to support (at) smartdeploy.com. Note that zip files are sometimes restricted by email security policy, so you may want to double check that the log set makes it out of your server. SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL

Hi Dennis, It's unlikely that the SmartDeploy version is an issue in this case - if the C:\Platform directory is missing, this generally indicates that the Platform Pack was not used. Is this a make/model of device that you've deployed to before? If you browse to the 'z' folder on the root of the DVD, is there a Windows 10 platform pack there that matches the make/model of the target device? If the Platform Pack is missing, go ahead and re-run Media Wizard, and be sure to select this Platform Pack on the appropriate screen so that it is included in the media. If the pack seems to be present but is still not being used, then we'll need you to download and run our wmi.vbs script from Step 1 on the Platform Pack Request Form: https://www.smartdeploy.com/support/platform-pack-request/ Send the resulting wmi.txt file to support (at) smartdeploy.com (and be sure to reference this DeployCentral thread), and we can advise further. SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL

Since Dell doesn't support Windows 10 on the OptiPlex 960, we can't support it, and that's why there is no platform pack. That being said, you can load Windows 10 on older devices and then try to use Windows Update for any missing drivers. But, you're own your own for any missing drivers, or driver issues on this device. If you are booting from USB, and it's never making it to SmartDeploy, then it's one of two things. Could be bad USB boot media, in which case try re-creating the boot media or using a different USB drive. Or it could also be bad or not enough RAM in the machine. Trying a different machine if you have one is a good way to know if this particular machine is the problem. Thanks, SmartDeploy Support Team

Please send us your media.log from your C:\SmartDeploy\Logs\ folder on your SmartDeploy host. support @ smartdeploy .com Thanks, SmartDeploy Support

Hello, Unfortunately, SmartDeploy does not support capturing UEFI virtual machines. SmartDeploy supports deploying via BIOS or UEFI, just not capturing UEFI so you will have to recreate the VM. Thanks, SmartDeploy Support

Hello, You received the following error: "An error occurred while applying the image", with an error code of 5, which means "Access is denied". Have you successfully applied this particular image (.wim file) to any other devices? Was there any antivirus software installed on the reference VM prior to capture? Does the error reliably occur at about the same point in the imaging process? (you can look at the timestamps in Deploy.log for this) Go ahead and email us at support (at) smartdeploy.com with the answers above, and we'll help troubleshoot further. Be sure to reference this thread. SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL

Especially for capture, try disabling any anti-virus software that is running. Ensure you are capturing from and saving to local physical disks. If you still have issues, email us your c:\smartdeploy\logs\capture.log, or media.log to support @ smartdeploy.com Thanks, SmartDeploy Support

This error occurs when the Windows 10 ADK is not installed on the SmartDeploy host. Download it here and then re-run the Media Wizard and you should be successful. Thanks, SmartDeploy Support

Hi Iver, You can have an image of Windows 7 on a USB and then deploy that, but if you're asking if SmartDeploy supports actually running Windows 7 on a USB that is something the product isn't intended to do. Thanks, SmartDeploy Support

Hi Palle, Most likely this is due to you not using the latest version of SmartDeploy. Ensure you're using SmartDeploy 2.0.2050, which supports the Windows 10 Creator's update. Recapture/deploy with the latest version and let us know your results. Thanks, SmartDeploy Support

Hi Alex, Are you running SmartDeploy version 2.0.2040 by chance? There is a known issue with Platform Pack downloading. We've just posted another service release (2.0.2050) which should resolve this issue. If it persists after installing the new version, please email us at support (at) smartdeploy.com and we can assist further. SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL

Hi Justin, SmartDeploy does not support capturing UEFI-based VMs (regardless of the platform). SmartDeploy has supported deployment to UEFI-based target devices since version 1.1.4000, but it is not necessary (or supported) to match the UEFI boot method from the source VM to the target device. You can simply create the VM as a BIOS-based VM, capture it, create UEFI-compatible SmartDeploy media (which is the default), and you should be able to deploy the image without issue. If you have any questions or issues, please feel free to reach out at support (at) smartdeploy.com. SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL

Platform packs are created based entirely upon customer request. If you are a customer, you can submit a platform pack request here. Please note that packs are created based on your support level, and the associated platform pack creation tiers. Intel NUC is Tier 2, so depending on your support level they're may or may not be a small fee to create the pack. If you have any other issues do please contact us directly, support @ smartdeploy.com. We take great pride in our product and our support, and look forward to resolving any issues you may have. Thanks, SmartDeploy Support Team

If you go to C:\SmartDeploy\Platform Packs are the packs downloading fully? Thanks, SmartDeploy Support

The new update is available that should fix creator's update sysprep error. You can download it here: Download the new version here and recreate your boot media via the Media Wizard and attempt to deploy again. We only send notifications for big releases and this is one of our smaller releases. The SmartDeploy console should show you that there is an update available in the top right corner as well. Thanks, SmartDeploy Support

Microsoft added some new AppX packages, and it’s causing issues with SmartDeploy and how we handle sysprep. We are working on a fix but it will take another new release of SmartDeploy, which should be out very soon. Sorry for the inconvenience If you use Windows 10 1607, you should be able to deploy without issue. Thanks, SmartDeploy Support

Hi Mossmak, Differencing images (.dwms) aren't really designed to be used in the manner you've described above. They are designed to be used to re-capture a VM that you've previously captured into a larger .wim file. They work by creating a smaller differencing image (.dwm) file that only contains those files that have changed since the previous .wim (which you specify) was captured. At deployment time, you would only need the original .wim and the most current .dwm. The intended use of this feature was so that a central office could support branch offices with limited connectivity, and reduce the frequency with which they need to transfer large .wim files over their network, by allowing them to send a smaller file for each update. The .dwms would gradually increase in size as the VM gets more and more different from its original state, so they would eventually need to capture and send a new .wim - but this could happen less frequently. Deploying with multiple .dwms is not supported. You could conceivably use .dwms to manage different application loads, you would have to choose one .dwm that corresponds to an existing .wim, and it would be difficult to update the VM - unless you created multiple copies of that VM after the initial creation, which would be updated, maintained, and recaptured in parallel from that point onward. However, this would not offer much of an space or time savings over simply creating and maintaining the VMs separately. If the goal is to save space on the deployed media or on a network share, you could store multiple images in the same .wim file (simply capture one image from VM #1, then capture another image from VM #2, and select the previous .wim as the save location - you'll be asked whether you want to add another image to the .wim file or overwrite the whole thing). If you opt to go with this method, you would need to make use of the SmartWIM command to delete old versions of each image as you add new ones, but it would save space, as the .wim format utilizes Single-Instance Storage, so any files in common between your images (including all OS files) would only be stored once inside the .wim file. I hope this answers your question - please feel free to email us at support (at) smartdeploy.com if you need any further assistance, and be sure to reference this thread. SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL

You are receiving the following error when deploying: Unable to update the disk or filesystem boot code. Your deployment is starting, and the target machine is receiving your image it’s just generating an error when applying it. Was the VM created by creating a fresh virtual machine, then capture/deploying that correct? It wasn’t converted from a physical -> virtual, correct? We do see that error if that was the case. According to your log, you’re deploying Windows 10 to a Latitude 7480. Ensure the target machine’s BIOS is set to the following: General -Boot Sequence = UEFI -Advanced Boot Options = Enable Legacy Option ROMs (not checked) Secure Boot -Secure Boot Enable = Enabled There is one other thing that you'll want to check. On certain Dell devices, one-time the boot menu (which appears if you press F12) will give you multiple options to boot the USB either in UEFI or legacy mode. This can be confusing when you look at it, because it doesn't always give the same name to each item in the boot list – one might say "USB flash drive" or "Removable disk", whereas the other might say "UEFI: [the specific brand name of the USB stick]". If you've configured the BIOS settings as they appear above, then you will need to make sure to select the "UEFI" option for the USB stick in the F12 boot menu. You can confirm this once you are booted into the SmartDeploy PE environment, but looking in the lower right corner. You will see "Boot method", followed by either "BIOS" or "UEFI". Make sure that it is UEFI. Thanks, SmartDeploy Support

Hi @amedley, Glad to see that Jaikele answered your question. If I recall correctly, back when this thread started, there was a method available to decommission individual machines through the website, but it didn't end up sticking around, as users generally had to decommission more than one machine at a time, and found the website method cumbersome. Thank you for bringing this old info to our attention - I've updated the post above for reference, and feel free to reach out to support (at) smartdeploy.com if you have any other questions we can assist with. SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL

Restart the machine to the SmartDeploy boot environment and click Collect Logs. Save the zip to a USB/Network share and then send it to us and we can investigate what may be going on. support @ smartdeploy .com and refer to this thread. Thanks, SmartDeploy Support

Hi Dave, Certainly, you can open a Support ticket for this - either via the support form on the SmartDeploy website, or by emailing support (at) smartdeploy.com. Your feedback is much appreciated! SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL

Hi Devin, Unfortunately, if you have a valid IP address, but you're not able to reach the network path from the target device, there's not a lot we can do to assist with that - you'll need to double-check that the network path is correct and reachable from that network connection. You can try plugging another Windows device into the same network connection and see if you're able to reach the network share using that path. If the share path is invalid, you may need to recreate the share and double-check the path. You may also need to check that you do not have a firewall blocking traffic (either on the server or on the network connection). SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL

Hi Devin, Error 67 is "The network name cannot be found," which indicates that the network path you're specifying is not reachable from the target device, usually due to the network environment. This is often due to the target device being on a different subnet, or otherwise being unable to access the network share using the hostname that you've specified. You can try using the IP address instead: \\192.168.0.1\exampleshare You can also try pinging the hostname or IP address from the target device and see if it's reachable. SmartDeploy Support Team TECH RESOURCES SmartDeploy User Guides DeployCentral Forum Platform Pack RSS SOCIAL

You cannot have two answer files on the same boot media unfortunately. You would have to have two different boot media. i.e. USBs Thanks, SmartDeploy Support