Plan a PSImage Deployment

PSImage is not supported by FileWave SupportTechnical soSupport. pleaseUse dothis not submit tickets with them about it. The information provided here ismaterial for educational purposes only.and Ifdo younot wouldopen likeTechnical toSupport purchase professional services hourstickets for consultingPSImage. assistanceFor setting up PSImagesetup or customizingcustomization it pleasehelp, contact professional.services@filewave.com with your request. If you have; existing unused professionalProfessional servicesServices hours you may be able to use themavailable for this purpose.work. Any feedback on PSImage can also be sent toUse the sameFileWave emailDiscord address. Any work on this would be done on Discordcommunity orfor inpeer working with Professional Services.discussion. For theFileWave's officialsupported Windows Imagingimaging solutionworkflow, please seeuse Network Imaging / IVS.

Deployment workflow

AsA mentionedPSImage beforedeployment therehas aretwo 2required components to the disk imaging - 1)components: an SMB share named psimage and 2) a bootable WinPEWindows WIMPE image -named boot.wim. To set up the disk imaging you'll need towim.

1. Set upPrepare the psimage SMB share forand accessits over the networkshare and grantNTFS adequate share access.

   permissions.
2. Choose

   Makeone theor boot.wim available to your client device to be reimaged. There are 4 differentmore ways to dostart this.boot.wim Anyon ortarget allcomputers: of

   these
3. Deploy methodsit canas bea usedFileset atthat loads into a RAM disk. This requires a working FileWave Client on the same time to reimage client PCs. target.

4. Deploy boot.wim with a fileset and have it load via RAM disk (requires device have functional FileWave client installed).

Create a bootable USB thumb drive. ThereA aresingle-partition 2drive versionsstarts ofnetwork imaging and reads images and drivers from the thumbpsimage drive.share. A dual-partition drive stores boot.wim, images, and drivers locally. The local method still needs network access after imaging so the FileWave Client can send its first inventory and create the Client record. See Building Your Imaging Environment for instructions.

A single partition thumb drive to host boot.wim for network imaging. Disk images and driver packs are pulled from the psimage share.. APublish dual partition thumb drive for local imaging. The first partition hosts boot.wim. Disk images and driver packs are pulled from a secondary partition on the same thumb drive. In this case there is no interaction with the psimage share. However, network access must still be available during post-imaging so the FileWave client can send in an initial inventory to the FileWave server to trigger the creation of client device entry.

Make boot.wim available to PXE clients over the network withthrough a PXE serverservice such as WDS.

Windows Deployment Services (WDS).

Create a bootable ISOISO. thatUse hostsit boot.wim.to start a virtual machine for image capture or write it to optical media for older hardware. See Building Your Imaging Environment.

for instructions. This can be used to boot a VM for image capture. It can also be burned to optical media for older devices that have an optical drive for image restoration.

Prepare yourthe physical reference computer, VMcomputer or physical,virtual formachine imagewith captureprep_ref_vm.ps1, usingwhich runs Sysprep.

Start the provided prep_ref_vm.ps1 script. This will syprep it.

Boot your reference VMcomputer from the ISO, orUSB a physical PC from a thumb stickdrive, or the network toand capture athe master image.

Run

Uploadupload_driver_pack.ps1 driver packs fromon each PCcomputer model youwhose needdrivers toPSImage reimagemust using the upload_driver_pack.ps1 script.

deploy.

Add the customized FileWave clientClient and any optional kioskKiosk customizations.

customization.

Add a Wi-Fi profile for laptops withoutthat do not have a built-in ethernetEthernet NIC.

adapter.

Optionally pre-assignuse diskimage_mappings.txt to preassign images, computernames,computer names, and customCustom fieldField valuesvalues. Without a mapping, the technician is prompted to clientchoose PCs via image_mappings.txt. If there is no association, tech will be prompted for diskan image and computername.

computer name. Start

Bootthe PCtarget computer from USBUSB, thumb stick, network,PXE, or viathe filesetFileset-based RAM disk to reimagerestore it.

the image.

Setting upPrepare the psimage SMB share

1. Extract the contents of the PSImage_v0.3.zip file to a folder.folder on the file server.
2. Share thatthe folder with sharethe name of psimage.psimage.
3. Grant EveryoneEveryone: Full Control shareat permissions.the share-permission layer.
4. Create a dedicated domain account account, e.g.such fwadmin,as fwadmin, and grant itthat account Modify NTFS securitypermission on the folder. NTFS permissions toprovide the effective access restriction for this folder.configuration.
5. From another PC,Windows verify that you cancomputer, connect to the the psimage share usingwith the abovededicated domain account.account and confirm that it can create, modify, and read a test file.