Erik

Administrators
  • Content count

    145
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Erik

  • Rank
    Advanced Member

Profile Information

  • Gender
    Male

Recent Profile Visitors

11,145 profile views
  1. Hello, You can find information about network booting with SmartDeploy on our White Papers page here. On this page is a guide for integrating SmartDeploy with Windows Deployment Services, which SmartDeploy uses for PXE boot. Hope that helps! Thanks, Erik
  2. Hi Shana, To know what is going on with the domain join I would need to take a look at the C:\Windows\Debug\Netsetup.log from a machine that went through the deployment process and failed to join the domain. You can either reply to this thread with it, or send it over to support and I will take a look. Thanks, Erik
  3. Hi Shana, What is the error that you receive when choosing the boot.wim? Also when in the process does it occur? Also when you mention that it works with fr-FR, does that mean that the locales are updated when booting to the pre-installation environment, or the DISM commands complete? Thanks, Erik
  4. Hi Danny, It looks like you had some correspondence with our support team, but I would like to close the loop on this one. We generally try and be as exact as possible when adding drivers to the Platform Packs, meaning we only add INF's and binaries that are needed, not everything from a downloaded package. This keeps things clean and avoids any conflicts. However if you are in a bind and need to get a pack built quickly, you can leave all the ancillary files that are downloaded with the driver, it will just cause your pack to be larger. Below are a few links to documentation on the process of building a Platform Pack as well. SmartDeploy Users Guide Creating Custom Platform Packs Video Hope that helps, Erik
  5. Hi Shana, The Windows Preinstallation Environment that we utilize is sealed with the QWERTY keyboard layout. This is changeable, however would take some custom work on your end. Create boot media through the Media Wizard Get the Boot.wim out of the Sources folder on the root of the media created in step 1 Mount the Boot.wim with DISM (dism /mount-wim /wimfile:c:\boot.wim /index:1 /mountdir:c:\mount) Use DISM to change the keyboard layout (dism /image:c:\mount /Set-InputLocale:nl-NL) there is a list of InputLocales here Unmount the WIM and commit changes (dism /unmount-wim /mountdir:c:\mount /commit) Add the Boot.wim that was modified back to the Sources folder of the media created in step 1 Thanks, Erik
  6. Hi Shana, To install a driver, application, or run a command after deployment you can use tasks. Tasks exist in two places, the Platform Pack and the Deploy Wizard. The tasks in the Platform Pack are targeted to a specific computer type, while the task created in the Deploy Wizard will be targeted at all computer types. If the driver you are installing is for a specific machine type you may want to use the Platform Pack, if its not you can use the Deploy Wizard task. Creating a task in a Platform Pack: Add your executable to a folder, for instance C:\Setup Open the Platform Pack, expand the Make/Model nodes Right click the OS that you would like to use the installer with and select Add Browse to C:\Setup and select OK You should now see a subnode of the OS that is labled Setup, click this In the right hand pane there is a Tasks section, select Add Change the Phase to Specialized Mini Setup, First boot or First logon Change the Command to [platformfolder]\Setup\Setup.exe /s (where the file name and silent install switch match that of your installer) Save the Platform Pack The process is much the same in the Deploy Wizard, however the installer will need to be in a location that is accessible to the OS during deployment, for instance in the image. To locate the Deploy Wizard task section boot a target device to SmartPE, select Deploy an image, select Advanced and then navigate to the Tasks tab. Thanks, Erik
  7. Hi Steve, Unfortunately Sysprep can only accept one answer file. If you wanted to combined your answer file with the SmartDeploy answer file at deployment time this could be done, however would require a custom script to merge the two XML files, or add the new settings to the SmartDeploy created unattend.xml. Thanks, Erik
  8. The regional settings can be changed through the operating system's control panel. For example in the Windows 7 Control Panel you will see the option for Clock, Language, Region.
  9. Hi Shana, When you say move the data, are you referring to user data and settings, or a complete backup of the OS? If it is user data and settings SmartDeploy would handle this with the integration of the User State Migration Tool from Microsoft. This integration can be implemented in one of two ways; Hardlink Migration: All data/settings are preserved in a migration store on the local HDD of the machine that you are deploying to. Once deployment is complete the data/settings are put back to their normal location. Network Migration: All data/settings are copied to a network location while deployment takes place. Once deployment is complete the data/settings are copied back down to the machine. You can find a whitepaper that further details the integration here. Thanks, Erik
  10. Hi Allen, When creating offline deployment media the Platform Pack is copied to a z folder created on the media. It is also renamed Default.ppk automatically. If you change your answer file to reflect this you should be good to go. In regards to renaming your combined pack, no you do not have to as the Media Wizard will do that automatically when creating offline deployment media. Thanks, Erik
  11. Hi Allen, If your Platform Pack is called Default.ppk and resides in the same folder as the image it should be used automatically, no need to change the XML file to point to the pack. If that all looks good it could be a problem with the WMI query that is being run from the Platform Pack. Each Platform Pack queries the Manufacturer and Model fields of WMI, in some instances the OEM doesn't all ways set these values correctly. If you want to post the Deploy.log from C:\Windows\Debug on a deployed machine we can see if the Pack was used. Thanks, Erik
  12. When entering the product key during deployment the key is passed off to sysprep to process. Assuming that the version of Windows you are deploying matches the version of Windows your key is intended for you shouldn't have a problem. To check the SKU of Windows you can run "slmgr.vbs -dlv" from an administrative command prompt on your virtual reference machine. This command will return all the licensing information from the OS, you will want to ensure the Channel is Volume. If this all looks good our support team could have a look at the Setupact.log from C:\ Windows\Panther to see why sysprep isn't processing your key or you could try installing the product key via a task created from the Deploy Wizard. If you want to create a Task you can follow the steps below. Boot a target device to the SmartDeploy boot environment Select Deploy an image Select Advanced, and then the Tasks tab Select Add to create a new task Change the Command to "cmd.exe /c C:\Windows\System32\slmgr.vbs -ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx" where the x's are your product key Change the Phase to First boot as system or First logon to desktop If you want to automatically activate the machine you can create another task in the same phase to run "cmd.exe /c C:\Windows\System32\slmgr.vbs -ato" Continue your deployment as normal If you would like to automate this process in the future you can Export an answer file on the Summary page of the Deploy Wizard
  13. Hi Paul, It looks like Microsoft made some major changes in SP1. Namely the default boot environment was updated from Windows PE 3.1 to Windows PE 4.0. Unfortunately SCCM will no longer accept boot media that is based on Windows PE 3.1 (like SmartDeploy's). In order for SmartDeploy to work with SCCM 2012 SP1 we will need to update our boot environment to Windows PE 4.0 as well. This is on the road map however is a large undertaking. At this time I currently do not have a time frame for completion. For now SCCM 2012 and below will need to be used if you intend to integrate. Thanks, Erik
  14. Hi Paul, The log is located in %temp%, which is the signed in users temporary directory. If you open a run dialog box and type in %temp% it will open the folder for you. Let me know how the reinstall goes. Thanks, Erik
  15. If you want to see what level the BIOS will be updated too you can check the Platform Pack. Inside the Platform Pack, under the OS node you will see a folder called BIOS. Select the BIOS node and check the right hand pane for the version that is being queried. If the version on the machine is already higher than this it will not be updated. You could also check the Deploy.log that is in C:\ Windows\Debug after a deployment completes to see if the BIOS task was executed.