Troubleshooting (PSImage)

PSImage is not supported by FileWave SupportSupport. so please doDo not submitopen Support tickets withfor themPSImage abouttroubleshooting. it.This Thepage informationis provided here is for educational purposes only.use. If you would like to purchase professional services hours forwant consulting assistance setting upwith PSImage setup or customizing it pleasecustomization, contact professional.services@filewave.com. with your request. If you have existingExisting unused professionalProfessional servicesServices hours you may be able to use themusable for this purpose.work. Any feedback on PSImageFeedback can also be sent to the same email address. AnyPSImage workdiscussion onhappens this would be done onthrough Discord or in working with Professional Services. For the official Windows Imaging solution pleasesolution, see Network Imaging / IVS.

Q: Error copying files from z:\scripts when booting from physical PC. Works fine when booting from VM.

A: Windows PE either 1) does not have the appropriatecorrect drivers or  2) non-optimal driversdriver for the ethernetEthernet NIC in this PC.PC, Asor it has a result,driver thethat is not optimal. The network connection iscan be slow to come up and notmay presentbe unavailable when the the imaging attempts to map the psimagePSImage share. Inject the the appropriate drivers for thecorrect NIC driver into boot.wim, andthen update it inon your USB thumb sticks,drives, WDS server, or fileset.Fileset. See above section Tracking Imaging and Adding Drivers for details.

Q: Sysprep fails with the following error in setuperr.log - "Audit mode cannot be turned on if reserved storage is in use. An update or servicing operation may be using reserved storage."

A: Open Windows Updates and install all pending OS updates to clear out the reserved storage and re-sysprep again. More info here.

Q: Sysprep fails with the following error in setuperr.log - "Package <PackageFullName> was installed for a user, but not provisioned for all users. This package will not function properly in the sysprep image."

A: Run remove_app.ps1 on the client PC from the sysprepSysprep folder to remove the offending Microsoft Store appapp, andthen try syspreppingSysprep again. Keep checking the setuperr.log. as thisThis can happen with multiple appapps, but sysprepSysprep willstops fail as soon as it runs intoat the first app it finds with this condition.

QQ:: Sysprep fails with the following message in setuperror.setuperr.log - "Failure occurred while executing 'CAPISysPrep_Generalize' from C:\Windows\system32\capisp.dll."

A: Trigger sysprep locally from the reference system with the following command.

c:\Windows\System32\Sysprep\sysprep.exe /generalize /oobe /shutdown /unattend:c:\Windows\System32\Sysprep\unattend.xml

Q: Dism fails with an error 2 when restoring a disk image to a PC that has a client mapping in image_mappings.txt.

A: Verify that  the disk image name specifiedmapped forto thethat device by that serial number exists in the images folder. Edit the mapping entry so that the assigned disk image name matches one of the captured disk images in the images folder.images.

Q: Post-imaging hangs with repeated message "Waiting 10 seconds for initial inventory to complete" for longer than 5 minutes. 

A: CausedThis is caused by the client being unable to communicate with the FileWave server,Server, such as when there is a device conflict. Check that "Automatically resolve conflicts"conflicts is enabled and set to "Replace old clients with new"new.