Erik

The command will fail without the quotes around the usernames. You can simply put this command into a batch file with the quotes, then run the batch file. The batch file will need to be available locally when the machine is in the first boot phase, so you will either need to copy it over after the image is deployed or add it to your image.

It looks like the Administrator account is being recreated based on the answer file passed to sysprep by the Deploy Wizard. You can simply delete it "Net user administrator /delete" using a task like was done to enable the built-in administrator account. The easiest solution would probably be to just leave the administrator account disabled, and create a new administrator account named sysadmin but the net user commands will work as well. In regards to the built-in guest account it is being renamed by default sysprep behavior. If you wish to have it renamed you can run "wmic useraccount where name="Guest" call rename name="Your Guest Account Name"". This task will not run during Specialize / Mini-Setup and will need to be run at the First boot as system or First logon phase.

By default when deploying an image of Windows 6.x sysprep will disable the built-in administrator account. If you go to advanced options in the Deploy Wizard and select Enable administrator account it will try and enable the "Administrator" account. Since you have the administrator account renamed this results in creating a new administrator account. What you can do is leave the enable administrator account check box unchecked and create a task to enable your admin account. You can follow the steps below to do so. From the Deploy Wizard select Advanced Select the Tasks tab Select Add to create a new task Enter "Net user (your admin account user name) /active:yes" Change the phase to Specialized / Mini-Setup Complete your deployment Once the image is deployed the renamed admin account should be activated and you should not be prompted for a new password.

Sorry you are having so many problems! In regards to the boot manager error, does this occur when booting a machine from the DVD or after the image has been deployed? It would probably be good to send the Media.log from your machine to our support team (support [at] smartdeploy.com). They will be able to help you get it all fixed up in a more timely fashion. You can find the Media.log by opening the %temp% folder on the machine you are creating media from.

You could try the following to see if it resolves the problem for you. Clear the contents of the %temp% folder Download and install SmartDeploy version 1990 Ensure you have enough disk space to store the image 3 times (i.e. 24GB) Try to create your media again

Hi Jesse, Glad to hear you got it worked out. Thanks for closing the loop on this one! Regards, Erik

Hi Steve, Does the image you are using deploy fine when not used with SCCM? For example can you create offline media with the image and deploy it. I ask because this behavior can occur when the image file does not have the correct metadata. When an image is captured with the SmartDeploy Enterprise Capture Wizard custom metadata is added to the WIM, that details the information about the source virtual disk. If this information is missing the check for valid disk structure which runs after selecting next, at the recreate drives page, will fail. This leads to the next question of how the image was created? Thanks, Erik

Thanks for the error information, at what point in the process does this error pop up? During the image apply, before or after? Also if you could get the Deploy.log from the machine it would be helpful. To do this you will need to enable command support on the boot.wim that you imported to SCCM. Once you have this you can run through the deployment until it fails, hit F8 to open a command prompt and copy x:\Windows\Temp\Debug.log. If you could then paste or attach it to a reply I will have a look.

Hi Steve, There isn't yet an updated guide for SCCM 2012, however the process should be largely the same as the SCCM 2007 integration guide. It sounds like you have already worked through most of the process if you are to the deployment stage. Can you please let me know what the error you receive is and we can go about troubleshooting form there. Regards, Erik

Hi, There are a number of logs that will show you what has occurred during a deployment. Deploy.log: The deploy log is generated by the Deploy Wizard and can be found in two places. When in the SmartDeploy Boot Media you can find the Deploy.log in X:\Windows\Temp. Once the image deployment is completed the Deploy.log is copied to %systemroot%\Debug. This log will give you information on settings used in the Deploy Wizard, if the image applied successfully, and Platform Pack support/usage. Setupact.log: Once SmartDeploy finishes with applying the image the machine is rebooted and Sysprep is run. In Windows Vista/7 Sysprep logs success/failure to two logs depending on the phase of Sysprep. You can find information on the generalize phase at %systemroot%\System32\Sysprep\Panther\Setupact.log. You can find information for the additional stages of Sysprep at %systemroot%\Panther\Setupact.log. In Windows XP you can find the Setupact.log at %systemroot%\. This is generally where we see the most issue during deployment, you can find more information about common Sysprep problems here. Netsetup.log: If you experience problems joining a domain you can find logging information at %systemroot%\Debug\Netsetup.log. Hope that helps, Erik

Yes it will work with XP as well.

Hello, We recommend that you combine the Platform Packs for all models you want to support into a single Platform Pack file. During deployment the Deploy Wizard will then parse through the Platform Pack getting only the drivers that are needed for the machine type and OS you are deploying. The size of the pack will grow however all drivers are compressed and single instance stored. Thanks, Erik

Hi Steve, The proper channel for requesting a Platform Pack is to contact the SmartDeploy Support team at support[at]smartdeploy.com. They will be able to get this built for you. In regards to releasing packs for new models, we create Platform Packs as a service based on customer demand. Meaning we will create the Platform Pack for new models when they are requested by a customer. Thanks, Erik

Hello, SmartDeploy runs Sysprep by default when deploying an image, so this information should be getting reset. It sounds like you also had a ticket in with support on this one that they resolved. Just wanted to double check with you and make sure everything is working properly? Thanks, Erik

Hello, You can give the Deploy.exe a try as the Silverlight version may be having a problem running on that hardware for some reason. To launch Deploy.exe hit Shift + F10 at the main splash screen, then type Deploy.exe and hit enter. This will open the more classic looking version of the Deploy Wizard which you can give a go. Let me know if that works out. Thanks, Erik

Hi Justin, SmartDeploy was designed to be a hardware independent imaging solution. To ensure that an image created can go to any device, thus making it hardware independent, we made it a requirement to start with a virtual machine. The virtual machine requirement ensures that there is a very limited amount of hardware specific information in the image. When capturing from a physical machine you end up with all of the device drivers in your image, which can cause conflicts when going to another device. This is why it is so important to start with a fresh install to a virtual machine. If you must capture from the physical machine you could try removing as much of the device information as possible and ensure there are no errors, or problems with the machine before capture. You could also try using VMware Converter rather than the Disk2VHD and resizer process. Thanks, Erik

Hi Justin, The first thing that sticks out is the P2V process. We do not recommend starting with a physical machine. Can you try installing Windows XP to a virtual machine (you can use VPC, VMware Player/Workstation, Hyper-V, etc...), then capture an image from there. If it deploys fine we will know the problem was with the P2V. Thanks, Erik

Hi Paul, Sorry to hear that you are having troubles with these models. Are you using the Platform Pack from SmartDeploy.com? If not you can give those a download and see if it fixes up the problem. If you are using the packs from the website could you please get me the following info? What OS are you deploying? Are you able to successfully deploy without the Platform Pack? Also it would be great for our support team to have a look at a few logs. First we would need the Deploy.log from C:\Windows\Debug, you can get this by rebooting the machine to SmartPE, hitting Shift + F10 to open a command prompt and then copying it to a USB or network drive. The other log to look at would be the minidump file from the BSOD. You can find it in the C:\Windows\Minidump folder. If you could send both of those over to support@smartdeploy.com we will take a look at them. Thanks, Erik

Hello, It looks like the language isn't picking up correctly with the unattended answer file. I imagine if you try this without the answer file it will work. As a work around you can follow the informaotin in this blog post to set the custom regional settings. You will want to set all four options to 0413 and your answer file should look like the example below. Once you have edited the answer file it should work in unattended mode and correctly set the regional settings. I will look into what is causing the default setting to be ignored during the unattended deployment. <regional_settings> <time_zone>(GMT-08:00) Pacific Time (US and Canada)</time_zone> <input_locale> <ui_language>0413</ui_language> <system_locale>0413</system_locale> <user_locale>0413</user_locale> <input_locale>0413</input_locale> </input_locale> </regional_settings> Thanks, Erik

Hi Neil, It sounds like you have already engaged support on this and the work around so far was to revert back to 1960. We are still looking into the problem and trying to get a repro, which to this point has been elusive. Support will update you when something concrete comes across, but just wanted to close the loop here. Thanks, Erik

Hi Barry, Disk 0 should be the disk that you want. You can always double check by opening a command prompt in the boot media (hit Shift + F10 once the machine boots to SmartPE) and using diskpart. Once the command prompt is open type diskpart, then hit enter and type list disk and hit enter again, this should show you all of the disks. You will want to use the number corresponding to the internal HDD. If the internal HDD doesn't show up in diskpart let me know what computer model you are deploying too, as it may need a driver for the disk controller in SmartPE. Thanks, Erik

Hello Barry, It sounds like you want to install the image to the first partition which is 40GB and create a blank formatted partition the fills the rest of the disk, is that correct? If so you can check out this forum post that addresses the same setup. Let me know if that's not what you are looking for, or if there are problems. Cheers, Erik

Hello, Platform Pack creation is done as part of the support contract with the software. We generally create Platform Packs for business class devices from the major OEM's at customer demand. There hasn't been any customer demand for this device to this point which is why we don't have the Platform Pack created. To request a pack be built you will need to contact the support team and have a current support contract. I can tell you Toughbook Platform Packs are notoriously hard to create because Panasonic has so many software tools that need to be installed in a specific order for the device to work correctly. Support will probably ask that you send in one of the devices so we can build and certify the Platform Pack. Thanks! Erik

Has anything changed with the Platform Pack? Do you have another copy? Can you post the Deploy.log from the machine that is having the deployment problem? To get the log you will progress through the deployment until you see the error, close the error and then hit Shift + F10 to open a command prompt. The Deploy.log can be found in x:\Windows\Temp.

It sounds like the Platform Pack you are using is corrupt. Is it a new pack, or did you recently make changes to your default Platform Pack? You can try the following: If using a combined Platform Pack, try using just the single Platform Pack. Download the Platform Pack again to ensure the download didn't have problems. Check that the downloaded Platform Pack is not "Blocked" (Right click, Properties, you will see an Unblock at the bottom of the Properties sheet if it is blocked.) Let support know the problem and what pack you are using so we can check if the source file was corrupt or had a replication problem to your edge server.