Jump to content
DeployCentral

Erik

Administrators
  • Posts

    145
  • Joined

  • Last visited

Everything posted by Erik

  1. Hello There, We generally do not build Platform Packs for the more consumer grade devices like this but we do happen to have the model you mention covered. You can download it directly from http://download.smartdeploy.com/Platform/DellXPS13.ppk. Thanks, Erik
  2. Hi James, The Deploy Wizard is the wizard you use to deploy images. When you boot a target device to the SmartDeploy Boot Environment (SmartPE) and select "Deploy an image" the Deploy Wizard is launched. After opening the Deploy Wizard you will see "Advanced" in the lower right hand corner of the wizard, clicking this will get you to the Advanced options. Thanks, Erik
  3. No worries. In the current stable release there is not an option to skip everything but the computer name screen. You would need to cause an error on this screen. This can be done by specifying that you want to join a domain and then removing the domain name from the answer file. In the next release of SmartDeploy (coming in the next few weeks) there will be a skip option for every wizard page. As soon as this version is released I will be writing a blog post about the new feature, but essentially you will set the skip value to 1 to skip past that page.
  4. Hi Bruce, Thanks for sending the WMI information to support, they should have the Platform Pack up on the website soon
  5. Hello James, Tasks can be implemented in so many different ways that it is hard to document everything. To get you started here is some information. Tasks can be accessed by going to the Advanced option of the Deploy Wizard and selecting the Tasks tab. To create a new Task select Add. In the resulting window you will see an option for Phase and Command. There are five different phases in which tasks can be run: Before image is applied: This processes in the boot environment at the end of the Deploy Wizard before the disk is prepared and the image is applied. After image is applied: This processes in the boot environment after the image is applied but before rebooting the machine. Specialize / Mini-Setup: This takes place during the Specialized phase of Sysprep. Tasks in this phase will be run from the Operating System of the image that was deployed utilizing the system account. First boot as system: Tasks in this phase take place while the computer is sitting at the logon screen. You will not see them process like you would in the other phases as the tasks run in session 0 as the system account. First logon to desktop: Tasks in this phase happen as the users logs into the desktop for the first time. The task will be processed using the users credentials and security settings. [*]The Command field will let you enter the command to be run. Here are some examples of commands that can be run, but basically you can expect anything that would be valid running from the Run dialog box of the OS to work as a command. Running a command line utility, i.e. copying a file: Command = "Copy c:\test.txt c:\users\test\desktop\test.txt" Running a batch file: Command = "Cmd.exe /c c:\test.bat" Running a VBScript: Command = "Wscript.exe c:\test.vbs" If you are unsure the command is working properly one great troubleshooting method is to create another task in the same phase that runs the command "Cmd.exe /k" this will open a command prompt that you can interact with. When the command prompt is open you can test your command as many times as you need without the deployment continuing. When you are satisfied with your testing you can close the command prompt to continue deployment. I hope that is enough to get you up and started but if you have any further questions please let me know. Thanks, Erik
  6. Hello, When capturing an image with SmartDeploy Sysprep is not run as this is taken care of behind the scenes at deployment time. In order to use a WIM created with SmartDeploy you would need to Sysprep the virtual machine prior to shutdown and capture. Thanks, Erik
  7. Hi Bruce, We are in the process of working on Platform Packs for the new Latitude line. If you want to help us expedite the process you could run the script file here on one of the machines. The script will create a text file in the folder from which it was run that needs to be sent to support. The text file contains all of the PnP ID's from the hardware devices in the machine. Thanks, Erik
  8. The error is likely do to the name of the .wim file that is copied to the C:\Program Files\LANDesk\PXE\System\images\boot. If this .wim file name is not the same as what is entered in the BCD commands (the commands in this forum post expect the file to be C:\Program Files\LANDesk\PXE\System\images\boot\SmartDeploy.wim). You can certainly contact us directly at 'Support at SmartDeploy dot com'.
  9. Hi James, It looks like I have a typo above (fixed now). The brackets around boot in the command will need to be straight not squiggly . BCDEdit /store BCD /set {GUID} device ramdisk=[boot]\boot\SmartDeploy.wim,{ramdiskoptions}. The same is true for the next command BCDEdit /store BCD /set {GUID} osdevice ramdisk=[boot]\boot\SmartDeploy.wim,{ramdiskoptions}. Thanks, Erik
  10. Hello James, Sorry for the delayed response on this one. The easiest way I have found to get LANDesk to PXE boot a custom version of Windows PE is to make a change to the BCD on the PXE representative. If you make this change you will be able to chose from the LANDesk supplied Windows PE and the SmartDeploy Windows PE. You can follow the steps below to make the change. Create new SmartDeploy media by opening the Media Wizard When prompted for Media Type select Build Boot Media and check For use With WDS Multicast (This will create a Boot.wim file that will be used for PXE boot) [*]Rename the Boot.wim created by the Media Wizard to SmartDeploy.wim [*]Copy the SmartDeploy.wim to C:\Program Files\LANDesk\PXE\System\images\boot on your PXE representative [*]Open an administrative command prompt on the PXE representative [*]Change directories to C:\Program Files\LANDesk\PXE\System\images\boot [*]Create a backup of the BCD file (copy BCD BCD.old) this will make it easy to revert back if something goes wrong [*]Now for the BCDEdit commands to create the new boot entry for the SmartDeploy.wim BCDEdit /store BCD /create /d "SmartDeploy" /application osloader (this will return a GUID that looks like this:{7312763b-6fbb-11e1-9ebd-a088b41084fc}, copy the GUID as it will need to be used in the following commands in replace of {GUID}). BCDEdit /store BCD /set {GUID} device ramdisk=[boot]\boot\SmartDeploy.wim,{ramdiskoptions} BCDEdit /store BCD /set {GUID} osdevice ramdisk=[boot]\boot\SmartDeploy.wim,{ramdiskoptions} BCDEdit /store BCD /set {GUID} systemroot \Windows BCDEdit /store BCD /set {GUID} detecthal Yes BCDEdit /store BCD /set {GUID} WinPE Yes BCDEdit /store BCD /displayorder {GUID} /addlast You can then run "BCDEdit /store BCD /enum all" and check that it looks correct [*]Now PXE boot a machine, select F8 and then WinPE Menu, the machine will start PXE booting and open to another Menu which lists the boot options, select the bottom option to boot to the SmartDeploy boot media. Let me know if you run into any problems! Erik
  11. Hello Ken, Yes we do Sysprep a little bit differently than you are probably used to. We automate the running of Sysprep and create an answer file for it based on the information you provide in the Deploy Wizard. This is an answer file that is separate from the answer file that you export to automate the Deploy Wizard and is never seen by the user. Because of the exacting state that the reference machine needs to be in for Copy Profile to work correctly we have chosen to leave the option out of the Deploy Wizard. There is still a path to get this setup and working however. You can follow the information in this post or contact our support team. Thanks, Erik
  12. Hi Cory, Could you please contact support directly. They will need to have you run a script and get some logs so we can figure out why the driver isn't installing. Thanks, Erik
  13. Hello, From a trial perspective we ask that you use a computer model that we currently have in the Platform Pack library. Should you chose to purchase the software in the future we can work with you to get this pack created. Thanks, Erik
  14. Hello Tom, If you open the answer file and scroll to the bottom you should see the <unattend_delay/> on the fourth line from the end of the XML. It is here that you will want to make the edit, you can change the <unattend_delay/> to <unattend_delay>30</unattend_delay>. Thanks, Erik
  15. Hello, Sorry for the delayed response on this, it is always quicker to just email support directly if you need immediate assistance. In regards to your problem, yes it is do to the rearm limit in Windows 7 based on the following two lines in the logs, but it looks like you have come to that conclusion. 2012-05-11 18:23:41, Error [0x0f0082] SYSPRP LaunchDll:Failure occurred while executing 'C:\Windows\System32\slc.dll,SLReArmWindows', returned error code -1073425657 2012-05-11 18:23:41, Error [0x0f0070] SYSPRP RunExternalDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = -1073425657 The only way around this problem without rebuilding would be to make an alteration to the unattend.xml that SmartDeploy passes to sysprep. You would need to set skiprearm to 1 in the answer file: http://support.microsoft.com/kb/929828. To do this you would need to use a vbscript to edit the file, if you contact support we can get you setup with this. In the future when doing the copy profile process you can also set skiprearm to 1 in your answer file. I will update the previous post you linked to with this information as well. Windows 7 x86 &lt;?xml version="1.0" encoding="utf-8"?&gt; &lt;unattend xmlns="urn:schemas-microsoft-com:unattend"&gt; &lt;settings pass="generalize"&gt; &lt;component name="Microsoft-Windows-Security-SPP" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"&gt; &lt;SkipRearm&gt;1&lt;/SkipRearm&gt; &lt;/component&gt; &lt;/settings&gt; &lt;settings pass="specialize"&gt; &lt;component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"&gt; &lt;CopyProfile&gt;true&lt;/CopyProfile&gt; &lt;/component&gt; &lt;/settings&gt; &lt;cpi:offlineImage cpi:source="catalog:d:/os media/en_windows_7_enterprise_with_sp1_x86_dvd_620186/sources/install_windows 7 enterprise.clg" xmlns:cpi="urn:schemas-microsoft-com:cpi" /&gt; &lt;/unattend&gt; Windows 7 x64 &lt;?xml version="1.0" encoding="utf-8"?&gt; &lt;unattend xmlns="urn:schemas-microsoft-com:unattend"&gt; &lt;settings pass="generalize"&gt; &lt;component name="Microsoft-Windows-Security-SPP" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"&gt; &lt;SkipRearm&gt;1&lt;/SkipRearm&gt; &lt;/component&gt; &lt;/settings&gt; &lt;settings pass="specialize"&gt; &lt;component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"&gt; &lt;CopyProfile&gt;true&lt;/CopyProfile&gt; &lt;/component&gt; &lt;/settings&gt; &lt;cpi:offlineImage cpi:source="catalog:d:/smartdeploy/tools/install_windows 7 ultimate.clg" xmlns:cpi="urn:schemas-microsoft-com:cpi" /&gt; &lt;/unattend&gt; Thanks and sorry for the frustrations, Erik
  16. Problem: During the Sysprep phase of Windows 7 deployment the following error is received: "Windows could not finish configuring the system. To attempt to resume configuration, restart the computer." Resolution: This error is caused by the inability of Sysprep to process one or more registry keys either due to the size, security settings or state of the key. Microsoft has released a hotfix to fix the registry key size problems which can be found here. This hotfix is included in Windows 7 SP1. If the behavior continues after the hotfix is installed, or you are using Windows 7 SP1 the problem is likely due to an application that has a registry key with restrictive permissions. To fix this problem you will need to identify the application that is blocking Sysprep and remove it from the virtual reference machine, recapturing the image.
  17. Problem: During the Sysprep phase of a Windows 7 deployment you receive the error: "Windows could not parse or process the unattended answer file for pass [specialize]. The settings specified in the answer file cannot be applied. The error was detected while processing settings for component [Microsoft-Windows-Shell-Setup]." Resolution: This is generally caused by a mistyped Windows 7 product key. Please verify the product key that was entered into the Capture or Deploy Wizard is correct and works with the SKU of Windows 7 you are deploying. If the product key was entered in the Capture Wizard you will need to recreate your image using the correct product key.
  18. Problem: After deployment of a Windows 7 image has completed, during the Sysprep stage you receive an error stating: "Windows Setup could not configure Windows to run on this computer's hardware." Resolution:This is generally due to the use of an advanced format hard drive, especially on older hardware that wasn’t shipped with the advanced format hard drive. There are two considerations that need to be made to fix the issue. First insure that hotfix KB982018 is installed in the virtual reference machine. Next check whether the Platform Pack contains a SATA node, if the node exists check the date/version of the driver by exporting it form the Platform Pack. If the driver doesn’t match the version information located here remove it from the Platform Pack. The SATA drivers come directly from the device manufacturer, with older devices the drivers are not always updated to support advanced format hard drives. By removing the SATA node the inbox drivers that were updated by the hotfix will be used.
  19. Problem: When capturing an image with the Capture Wizard you receive an error stating: "The virtual disk must contain at least one volume." Resolution: This error can occur for many reasons however the root cause is generally one of the following. Be sure that the virtual disk file you are capturing the image from is once contiguous file that doesn’t have any snapshots. Snapshots and split disks cannot be used when capturing an image offline. If you must use the snapshot or split disk files capture the image in a booted state by booting to the SmartDeploy Boot Environment. If the virtual disk file is one contiguous file and doesn’t have snapshots check that the file path is less than 125 characters long. If the path is more than 125 characters move or rename the virtual disk to get under the 125 character limit. If the previous items look good there is likely a problem with the SmartVDK service. SmartVDK is the component that is used to mount virtual disks offline. Reinstalling this component will fix the corrupt state so an image can be captured. Open Device Manager on the machine with SmartDeploy Installed Select View>Show Hidden Devices Expand Non Plug and Play devices Locate SmartVDKSrv, right click and Uninstall it Reboot the computer and run through the Capture Wizard again (the Capture Wizard will automatically reinstall the SmartVDK service.)
  20. Problem: During image deployment you receive an error stating: "An error has occurred while applying the image". Resolution: This is generally due to a network drive being mapped to the S: or T: drive. SmartDeploy uses the S: and T: drive letters for deployment. Please do not map network drives to these letters.
  21. Hello, The best place to look when having domain join problems is the Netsetup.log located in c:\windows\debug. This will tell you why the domain joined failed. If you want you can send it over to Support (It has company info in it so you probably wont want to post it on the forum) and we can have a look at it as well. Thanks, Erik
  22. The Deploy Wizard will only be able to enable the Administrator account if it is not renamed. We will be adding support for renamed admin accounts in the future. In the meantime the easiest way to solve the problem is to simply leave the Administrator account disabled and create a new account with the name that you like and administrative privileges. If you do this sysprep will not disable your custom administrator account and you wont have to worry about the Deploy Wizard enabling it. The other option would be to create a task in the Deploy Wizard to run "cmd.exe /k net user [your renamed admin account name] /active:yes" (without the quotes) during the specialized phase of deployment.
  23. Hi Paul, There are a few factors that could be at play here. First the 8GB USB drive is really only 7.45GB. That 7.45GB is raw size, once the disk is formatted you end up with 7.38GB of usable space. You mention your image is 4GB which leaves 3.38GB left on the disk. We also have to account for the Platform Pack and the size of the boot environment that are being used. By default the boot environment is only ~300MB but this can increase quite a bit when using a Platform Pack with a number of Windows PE nodes (we inject the network drivers in that node to the boot environment). What is the size of the Platform Pack you are using? Also if you create Boot Media as opposed to Offline Deployment Media how much free space is left (this will tell us how big just the boot environment is)? If there is enough for your image and pack you can copy them over, otherwise you will need to decrease the size of one, or use a bigger USB drive. Thanks, Erik
  24. The best way of calling a vbs file is really based on how you are doing deployment. If for instance you use offline deployment media you can stick the vbs file on the media and call it from there. The %SmartDeploy_Media% variable is the drive letter of that media and was created to deal with scenarios where the CD/DVD or USB can have different drive letters on different hardware configurations. If you are using WDS you could simply call the script from the z:\ drive which is mapped to reminst on the WDS server. The easiest way is just putting the script in your image, you can then reference what was the C: drive in the booted VM as the T: drive (we automatically assign to the OS partition after deployment, while still in the boot media). Your task in this scenario would be: Phase ‘After image has been applied’, Command ‘wscript.exe t:\scripts\locale.vbs’. Hope this helps, Erik
  25. Server deployment is supported with SmartDeploy. The deployment to servers is the exact same process you would use to deploy to a desktop or laptop. There is a Platform Pack for the ProLiant server line that is comprised of the PSP from HP. You can give that a shot. If you have any problems with the pack the support team can help you out. Thanks, Erik
×
×
  • Create New...