Configure PSImage

PSImage is notan supportedunsupported byalternative to FileWave Network Imaging / IVS, so FileWave Support so please dodoes not submit tickets with them abouttroubleshoot it. TheFor informationpaid provided here is for educational purposes only. If you would like to purchase professional services hours for consulting assistance setting up PSImagesetup or customizingcustomization it pleasehelp, contact professional.services@filewave.com with your request. If you have existing unused professional services hours you may be able to use them for this purpose. Any feedback on PSImage can also be sent to the same email address. Any work on this would be done on Discord or in working with Professional Services. Community discussion is available on the FileWave Discord server. For the officialsupported Windows Imagingimaging solutionworkflow, please seeuse Network Imaging / IVS.

Adding the FileWave Client

1. Using File Explorer, navigate to the fwclient folder on the psimage share or the Imaging volume on youra thumbUSB stick.drive.
2. Right-click upload_client.ps1 and choose "Run with PowerShell".
3. upload_client.ps1 will write a fw_client_version.txt file to the sysprep folder so you know the version of your customized FileWave client that is being installed on client devices during post-imaging. This allows you to update the FileWave client without having to recapture your master image.
4. If you have files for kiosk customization create a subfolder named "custom" within the fwclient folder and add those files there. They will be deployed automatically immediately after the FileWave client is installed during post-imaging.

Adding drivers for computer models

1. On the computer model you wish to capture drivers for, open a PowerShell session with admin privileges, connect to the psimages share, and navigate to the models folder. If imaging locally change directory to the models folder on the Imaging volume of the USB thumb stick.drive.
2. Run the upload_driver_pack.ps1 script to extract 3rd partythird-party, non-Microsoft drivers. AThe script creates a folder named after the computer model will be created in the models folder on the psimagePSImage share containing the extracted drivers.share.

Custom fieldCustom Field setup

Set the FileWave serverServer address and appapplication token with the instructionsfiles below. Youbelow, canor alsorun setedit_config.ps1 them using the edit_config.ps1 script infrom the config folder on the psimagePSImage share.

1. Within the config folder on the psimage share create a server.dns file that containcontains the DNS address for your FileWave server.
2. Within the config folder on the psimage share create an app.token file that containcontains the base64 API token for a FileWave admin account that has at least permission to "Modify Custom Fields".

Pre-assigning computer names and disk images

1. Browse to the config folder on the psimage share or Imaging volume of the USB thumb drive.
2. Edit image_mappings.txt to pre-assign disk images and computernames to client devices by serial number. To avoid syntax issues from missing commas it is recommended you edit this file with a spreadsheet or CSV editing app. Entries should be in the format below. If no mapping is available or a client a client PC or the the assigned disk image does not exist, you'll be prompted to enter a disk image name.

   Serial Number,Computer Name,Image Name
   1a2b3c4d,test-restore,image.wim
   

3. There should be no spaces in the serial number, computer name, and image name fields and they should be separated by commas. ComputernamesComputer names should meet Windows naming requirements and should be 15 characters or less.fewer. If testing with a VMware VM, remove all spaces from the VM serial number when adding an entry for it. There must beLeave one blank line at the end of the line.file.
4. If you would like to set custom fields by their internal name, add them at the end after the image name. Custom fields need to be referenced by their internal names, followed by a colon, and then the value to set. The value for the custom field can have spaces in it, as illustrated in the example below. Only custom fields of the string data type are supported.

   1a2b3c4d,test-restore,image.wim,school:Washington Elementary,grade:5,classroom:218,user_type:student
   

5. If the assigned disk image is set to "capture" for a particular PC in image_mappings.txt while \config\mode.reimage is present, it will attempt to capture a disk image instead of restoring one.

Adding a Wi-Fi profile

For laptops that do not have awithout built-in ethernet port,Ethernet, you may prefer tocan switch to Wi-Fi as soon as possible for the post-imaging phase.phase Thisand allowsreuse you to disconnect yourthe USB ethernetEthernet dongle/dockadapter soon itanother candevice. used to reimage additional PCs. Remember that post Post-imaging requiresstill needs network access so the FileWave clientClient can sendsubmit inits an initialfirst inventory toand create the FileWave server to trigger the creation of a client entry. This network access can be via wireless and does not have to be a wired connection.record.

1. Configure a test PC to connect to your Wi-Fi.
2. Run the following command to list available profiles.

   netsh wlan show profiles
   

3. Use the command below to export the desired profile to the current folder. Change ProfileName to the name of the profile from the list displayed in the previous step. NoteThis thatexport this will storestores the Wi-Fi password for the wireless connection in clear text. TheRestrict Wi-Fiaccess to the XML file and remove it when it is no longer needed. PSImage deletes the imported profile will be deleted from the client system after import during post-imaging.

   netsh wlan export profile name="ProfileName" key=clear folder="%cd%"
   

4. Rename this profile to Wi-Fi.xml and copy it to the extra folder in the psimage share.

Changing configuration settings via edit_config.ps1

A text-based GUI is available for viewing and configuring many of the settings for PSImage. Navigate to the config folder on the psimages share, right-click edit_config.ps1, and choose "Run with PowerShell".