This means that, each day since the last v Disk version, the client will have to re-download all definition files after every reboot.The obvious solution to this unwanted behavior is to move the definition files to a location on the persistent disk attached to the VM.This is useful if you wish to deploy a definition update that is different from the current definition file supported in the Fixlet content.
The problem is that the SEP client does not have a configuration option that will allow you to do that. Even after a reboot I now have up to date definition files and I have an extra GB of data on my system disk where the files used to be.So I decided to create my own redirection solution. So here’s a Step-By-Step instruction on how to accomplish this.If you do want to process all VM’s in one run just use an asterisk (*) for the Catalog Name parameter.It’s also possible to run the script on an array of VM’s using the VMName parameter: .Here’s how I did it: folder to a location on my persistent disk, made my registry changes and started the client. Follow these steps in your client OS (in Read/Write mode): Now that we’ve prepared our image for this change we have to make sure that the definition files are present on the persistent disks on all VM’s in the environment.
For this I created a Power Shell script which will do just that.The default setting can be overruled bij using the .EXAMPLE Migrate-SEPDefinition Folders -Catalog Name XD7_TEST -Delivery Controller XD7-CDC-001 -Credential DOMAIN\XDAdmin Retreives the VM's in catalog XD7_TEST from Delivery Controller XD7-CDC-001 as user DOMAIN\XDAdmin.The online VM's will be processed first, after which the offline VM's will be powered on and processed with a maximum of 10 at a time.This way you can migrate your test VM’s first, without touching your production catalogs. You can always download teh latest definitions to a USB drive or other media and sneakernet them to the system.