Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

1 Follower

About SmartDeploySupport

  • Rank
    Advanced Member

Profile Information

  • Gender

Recent Profile Visitors

8,177 profile views
  1. Hi Jay, This typically indicates a problem with your answer file, but in order to diagnose the problem, we'll need to see a logset from the same WindowsPE session where the error occurs. We've opened a support ticket, and we'll be in touch. Glenn SmartDeploy Support
  2. SmartDeploySupport

    Answer file wizard skips product key page

    Most likely this is because a product key is baked into your image when you ran the Capture Wizard to capture your virtual reference machine. Re-run the Capture Wizard and do not enter a key during the process. Then when you create your answer file, you will be prompted for a product key.
  3. SmartDeploySupport

    Custom Rename

    Hi Aaron, I've emailed you the file - please email us at support@smartdeploy.com if you do not receive it in the next few minutes. Glenn SmartDeploy Support
  4. SmartDeploySupport

    Custom Rename

    Hi Aaron, Sure thing - here you go. There are comments in the script to indicate where to change the prefix (currently "PRE-"), as well as the number of characters you want from the serial number. Note that Dell devices use only 7 characters in the serial number ("Service Tag", they call it - but it's the same WMI field) - that's the shortest standard that I'm aware of, but it would probably be safest to go with something shorter, like the last 5 characters. GenerateCompName-PrefixplusLast7SerialNumber.txt Feel free to reach out (support@smartdeploy.com) if you have any questions, and be sure to reference the URL of this thread. Glenn SmartDeploy Support
  5. SmartDeploySupport

    Windows 10 Default user

    Unfortunately, at this point, we really can’t recommend using the Sysprep\CopyProfile procedure with Windows 10 any longer. It has become less and less reliable with each successive version of Windows 10. The documentation for this procedure is limited and out-of-date, but it looks like Microsoft is trying to push people away from using Sysprep\CopyProfile to copy settings into the default user profile, and toward using group policy instead. You can use a custom Start Menu and Task Bar layout XML to choose how it looks. Here are the instructions for that: Configure the Start Menu and Task Bar as you would like it to be for all users. Open PowerShell and run Export-StartLayout -Path [Path\Filename.xml] Copy the XML file to C:\Users\Default\AppData\Local\Microsoft\Windows\Shell\ on your reference virtual machine. Alternatively, you can download the LayoutModification.xml file (attached as .rename), and copy it to the location above. This layout creates an Office app collection in the Start Menu, and puts Outlook, Explorer, and IE in the task bar. You can visit these links for more information. 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 LayoutModification.rename
  6. SmartDeploySupport

    Custom Rename

    Hi Martin & Ray, I thought I'd chime in here - looking at Ray's script, it does appear that - with some modifications (as the script is currently in debugging mode and merely echoes the modified computer name back to the console, rather than updating the UnattendXML files), it would do something close to what Martin is asking for. Although I did notice one possible error - the parsed versions of the serial number and model (respectively) use a Left([serial number or model], 4) command, which would return the first four digits of the item requested, not the last 4. Switching this for a Right (item, 4) command would fix this issue, but could introduce some additional complexity. Unfortunately, even with the fixes above added, there are two potential issues with the script as written: The script is looking for the Model name under Win32_ComputerSystem. This will indeed work for most computers. However, Lenovo does model naming in the system firmware differently than other manufacturers. In that Model field, they put in the the "Machine Type" - something like 20HF###### - and the unique identifier for that model is actually the first four of that machine type. If you're looking for the friendly name for the model, Lenovo puts this into Version under Win32_ComputerSystemProduct (among other places). To behave in a reliable manner, the script would have to be modified with a tree of separate actions for Lenovo products only. Some model names contain spaces in the last 4 characters. HPs in particular are notorious for this - often incrementing model numbers with generational identifiers such as G1, G3, etc. - with a space before this. Adding a space to a computer name is not recommended, so for models which include spaces, it would be preferable to remove these spaces before proceeding. It is possible to design a script with a branching series of if/then/else statements that accounts for all of these possibilities, but it would necessarily be specific to the hardware in your individual environment, require testing on multiple units of that hardware to ensure that it behaves consistently, and it could likely need to be updated to account for the variations of every new model that is added to your environment. For this reason, we generally do not recommend such a potentially cumbersome approach. We have had users set up more basic versions of what you're asking for - grabbing the last 4 or 5 digits of the serial number, and appending this to an identifier prefix which corresponds to the location or role that the computer will be utilized in - something like LAB-12345 or NYC-54321. This is a pretty reliable naming convention, since nearly every device will have a serial number (unless it has had its system board replaced), and the prefix is not hardware-dependent or variable. If either of you have any questions on this, please feel free to reach out at support@smartdeploy.com, and be sure to reference this thread. Glenn SmartDeploy Support
  7. SmartDeploySupport

    Unable to login since version 2.0.3020

    2.0.2030 was actually working fine yesterday. It seems to be something that occurred last night. We are currently looking into it now and will report back. We appreciate the patience. Thanks, SmartDeploy Support
  8. SmartDeploySupport

    Answer file wizard not mapping drive once selected

    Hi Geoffrey, Certainly, we can assist with that. Please send us your Answer File Wizard log - C:\SmartDeploy\Logs\Answer.log - and send it to support@smartdeploy.com (you will receive an email from us shortly; you can just reply to that). Regards, Glenn SmartDeploy Support
  9. Hi camlen92, This is an interesting problem - I can tell you that Windows Sysprep definitely has changed, but SmartDeploy's changes have generally been responsive to changes in Windows 10 - that's to say, we've updated the software as needed to support each new major OS version of Windows 10, including its various changes to Windows Sysprep. One of these changes is that as of Windows 10 Version 1607, we no longer recommend using the Sysprep\CopyProfile procedure on your reference VM prior to capture, as much of this procedure has been deprecated by Microsoft and will no longer work reliably, including Start Menu layout and Taskbar items. You're the first user I'm aware of that has asked specifically about the language bar visibility, but it appears that this is one of the items that has changed in the newer updates of Windows 10. I should also mention - it is no longer our recommendation to install major Windows 10 version upgrades on your reference VM, since they install as in-place upgrades and often leave the VM in an unreliable state for capture and deployment. So you may want to build a fresh VM with Windows 10 Version 1803 media before continuing with your Taskbar customization. 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 (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. Unfortunately, it appears that hiding the language bar is the default setting in Windows 10 (definitely in Version 1703 or later - not exactly sure when this change was made), and there does not seem to be any reliable registry method to enable it - and it does not appear that the XML file generated above contains any specific reference to the Language bar. It can be enabled manually via Control Panel\All Control Panel Items\Language\Advanced settings (check the box labeled Use the desktop language bar when it's available). And as always, the keyboard shortcuts of Alt+Shift or Win+Spacebar will allow the user to switch between installed languages. If you have any questions, feel free to reach out to support@smartdeploy.com, and please reference this DeployCentral thread. LayoutModification.txt Regards, Glenn SmartDeploy Support
  10. SmartDeploySupport

    Recommendations for October 1809 Update

    Hi Aaron, We appreciate you taking the time to evaluate SmartDeploy. We don't recommend upgrading to new versions of Windows 10 via in-place upgrades. i.e. Windows Updates. These new versions of Windows 10 are essentially new operating systems, so it's best practice to get the latest volume license media and then create a virtual machine and then capture/deploy that. You could let the PCs update after deployment and that shouldn't affect sysprep or anything on the deployment side, but just know your virtual reference machine will eventually need to be updated to the latest version anyway, and we recommend the above. Also, doing the above will provide you with the cleanest image. When in-place upgrades happens Windows 10 essentially backups the old operating system which can take a lot of space and will manually need to be deleted. Hope this answers your question. Thanks, SmartDeploy Support
  11. Hi Tim, How did you copy the the VMS? Did you simply just copy the VM's folders and place them on the new computer?
  12. SmartDeploySupport

    USB-C Thunderbolt dock and deploying

    No problem! Glad everything worked out
  13. SmartDeploySupport

    Cloud Deployment Token

    OneDrive the cloud token doesn't expire, but you will have to login every 90 days.
  14. SmartDeploySupport

    USB-C Thunderbolt dock and deploying

    You will need to create boot media via the Media Wizard and select the Precision 5530 platform pack. This will inject the USB Ethernet driver into the boot media and allow you to get an IP address. Thanks, SmartDeploy Support
  15. SmartDeploySupport

    Cloud Deployment Token

    What cloud service are you using? SmartDeploy Support