Use Custom PSImage Behaviors

PSImage is an unsupported alternative to FileWave Network Imaging / IVS, so FileWave Support does not troubleshoot it. For paid setup or customization help, contact Professional Services. Community discussion is available on the FileWave Discord server. For the supported Windows imaging workflow, use Network Imaging / IVS.

1. To prevent client certificate issues when reimaging
   • Do not delete old device entries.
   • Enable "Automatically resolve conflicts - Replace old clients with new" in the New Client From Server window.
2. If z:\scripts\debug.on exists, restore stops at a command prompt instead of rebooting so you can review output. Toggle this behavior with edit_config.ps1 in the config folder.
3. If z:\scripts\mode.reimage exists, PSImage goes directly to imaging and skips the main menu. Toggle it with edit_config.ps1 in the config folder.
4. If z:\extra exists, PSImage copies its contents to w:\windows\temp\psimage, which becomes c:\windows\temp\psimage after the new operating system starts.
5. If z:\scripts\to_do.bat exists, PSImage copies it to the temporary PSImage folder and runs it during post-imaging. A sample to_do.bat is included by default.
6. Set server=prompt in x:\imaging\config.ini to ask for the server address while reading the remaining credentials from config.ini. This supports distributed sites that should image from a local share instead of across the WAN.
7. Set mode=usb in the config.ini stored in boot.wim for dual-partition USB disk imaging.
8. If z:\fwclient\custom exists, PSImage copies its contents to C:\Program Files (x86)\FileWave\custom to customize FileWave Kiosk.
9. Enter z to open a command prompt at either of these points:
   • The main PSImage menu and
   • When asked to press Return to reboot after successful image capture.
10. PSImage creates C:\Windows\Temp\restore.done immediately before the final post-imaging reboot. Requirement scripts can use this marker to postpone Filesets until post-imaging is complete.