winoutreach5

When you apply the image to the other machines are you using a USB to Ethernet dongle with those deployments also? Is the USB port on the Panasonic a USB3 port by chance? Also, according to the article I linked previously, you should remove the AppX package for the user that is going to run sysprep first and then remove the provisioning to ensure the configuration is correct. From your most recent response, it is clear that you are removing the provisioned apps but it appears that you may not be removing them for the admin user first. Again, in the article I linked above, under the “resolution” section, it states “The correct way of removing the package is to remove the package for the user running sysprep and also remove the provisioning. This can be done using the following Powershell cmdlets: Import-Module Appx Import-Module Dism Get-AppxPackage -AllUser | Where PublisherId -eq 8wekyb3d8bbwe | Format-List -Property PackageFullName,PackageUserInformation Notes: From the output of the above command, check the users for whom the package is showing up as Installed. Delete these user accounts from the reference machine, or log in to the machine using these user accounts and run Step 4 to remove the Appx Package. The above command lists all packages that were published by Microsoft and installed by any user of that reference machine. Since the machine is to be sysprepped, we assume that these user profiles no longer need the package. If you have manually provisioned apps belonging to other publishers, then use the command below to list them: Get-AppxPackage -AllUser | Format-List -Property PackageFullName,PackageUserInformation Remove-AppxPackage -Package <packagefullname> Remove the Provisioning using the following cmdlet: Remove-AppxProvisionedPackage -Online -PackageName <packagefullname>”If you do not remove the packages properly as outlined above it can affect sysprep and imaging settings for Windows 8.1 specifically for certain hardware. My suspicion is either the USB to Ethernet dongle driver, the USB port itself or the AppX package configuration is the culprit in this scenario. Please keep me posted! Jessica Windows Outreach Team – IT Pro The Springboard Series on TechNet

Just a thought after re-reading this – are you editing the Windows 8.1 image by chance? Are you updating apps or removing certain apps prior to your sysprep / capture? The reason I ask is because of this Microsoft support knowledge base article which provides 3 possible scenarios and offers a potential resolution. Another thought I had came after I read that you were using a USB to Ethernet dongle which brings a concern of a driver issue into play. From within MDT, you might try to create bootable USB media and use that to deploy your image to the Panasonic. If that works then you might take a look at your USB dongle and drivers for said dongle. This TechNet forums thread will provide insight on how to use MDT to make a bootable USB stick. Jessica Windows Outreach Team – IT Pro The Springboard Series on TechNet

You’re welcome. Again, I would strongly suggest checking out the logs for any indication into why the deployment might be failing. If there is an existing recovery partition on the hard drive you might want to clear that out in case the RE partition is causing the deployment of the image to fail. Another thought is if there is a driver that is interfering. Can you try to deploy the image without any drivers and see if the ToughPad accepts the driver-free image? Presuming that the issue does lie within the driver store there are a few things you will also want to check; there are three steps in the driver injection process and each one needs to be verified: · Were the needed drivers copied locally by ZTIDrivers.wsf? · Did SETUP inject the drivers into the driver store? · Did PNP install the drivers from the driver store? The log files to review for the driver store are ZTIDrivers.log, setupact.log, cbs.log and setupapi.dev.log Also, while looking for a solution to your problem I came across this thread from the TechNet forums in which Johan helped a poster with a similar issue to your own by checking the driver store; it might be worth it to check the thread out and see if any of Johan’s tips assist you. Keep me posted! Jessica Windows Outreach Team – IT Pro The Springboard Series on TechNet

Depending on where your deployment is failing we might be able to check the logs for insight into why. Since it appears that your deployment is failing during the specialize phase of Setup, you will want to check the setuperr.log file which is typically found in the %windir%\panther\ directory. More information on where log files are located can be found on in the TechNet library articles, ‘Deployment Troubleshooting and Log Files’ and ‘Windows Setup Log Files and Event Logs’. In the second article, we can see that the %windir%\panther\ location typically contains log information the correlates to the setup actions after disk configuration. With that in mind, it might be helpful to check the disk partitions of the Panasonic FZ-G1 Tough Pad; in some situations, we have seen Sysprep failures be the direct result of a recovery partition by the manufacturer. Hopefully after you check the log files we will be able to take a look at why it may be failing further. Keep me posted. Jessica Windows Outreach Team – IT Pro The Springboard Series on TechNet