Skip to main content

Track PSImage Imaging and Add Windows PE Drivers

PSImage is not supported by FileWave SupportTechnical soSupport. pleaseThis domaterial not submit tickets with them about it. The informationis provided here is for educational purposesuse. only.For Ifpaid you would like to purchase professional services hours for consulting assistance setting up PSImagesetup or customizingcustomization it pleasehelp, contact professional.services@filewave.com withor review Professional Services. If your request.organization If you have existinghas unused professionalProfessional servicesServices hourshours, youask maywhether they can be able to use themused for this purpose.work. Any feedback onSend PSImage can also be sentfeedback to the same email address. AnyYou workcan discuss community use on this would be done onthe FileWave Discord or in working with Professional Servicesserver. For theFileWave's officialsupported Windows Imagingimaging solutionworkflow, please seeuse Network Imaging / IVS.

View imaging history

Browse to the logs folder on the psimagePSImage share or the Imaging volume of the USB thumb drive, right-click search_history.ps1,ps1, and choose "Run with PowerShell"PowerShell. You may need to expandExpand the window sidewayshorizontally to adequately viewif the query results.results are clipped. Transcripts of each image restore operation are loggedsaved as .log files in the \logs\restore. folder and named __

BeginningPSImage writes the beginning and ending imaging times are written to registryHKLM\Software\PSImage ofon the reimaged clientclient. at HKLM\Software\PSImage.  TheThis duration herecovers only includes the post-imaging time.phase. The namesame ofRegistry key records the restored image restoredname. Custom Field data from image_mappings.txt is also written here.there Customwhen fieldanother dataimaging specified in image_mappings.txt will also be written here if the client devicemethod is reimagedused usinginstead someof othera methods besides via fileset.Fileset.

APSImage log ofwrites the post-imaging phase is writtenlog to c:C:\windows\temp\Windows\Temp\psimage.log on the restored client itself.client. When addingyou add custom post-imaging actions into to_do.bat, havedirect their output directed to this psimage.log file for troubleshooting purposes.troubleshooting.

Adding drivers to boot.wim

If you find that there is no network access or degraded network access when booted into Windows PE, you may need to inject the appropriate Windows 10 NIC drivers for some of your PC models.

  1. Create c:C:\windows\temp\driver.Windows\Temp\drivers.
  2. On a working PC of the model you are having an issue with boot into Windows and open a CMD prompt with admin privileges to export all 3rd party drivers. If you have already extracted drivers for this PC model then just check the models folder on your psimage share for the ethernet NIC driver. 
    dism /online /export-driver /destination:c:\windows\temp\drivers
  3. View c:\windows\temp\drivers or \\psimage\models and check folder names to determine which one holds the ethernet NIC drivers for your PC. Copy the folder containing your ethernet NIC driver to your desktop.
  4. Mount your boot.wim image using the instructions from Building Your Imaging Environment (PSImage).
  5. Inject the drivers for your ethernet NIC with 
    dism /image:C:\WinPE_amd64\mount /add-driver /driver:"C:\fully\qualified\path\to\driver\folder" /recurse
  6. Unmount and commit your changes to boot.wim using the instructions from Building Your Imaging Environment (PSImage).
Back to top