This means that, each day since the last vDisk 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.
The problem is that the SEP client does not have a configuration option that will allow you to do that. So I decided to create my own redirection solution. After the SEP service starts the client checks the current files, which are located in this folder: If the files are out of date, updates will be downloaded to the corresponding subfolders. The CurrentVersion folder is actually a symbolic link to the folder named after the SEP version in this case You can tell by the little arrow symbol on the folder: And what do you know?
That was easy enough. 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. Create a folder named SEP on your persistent drive. The name is not important but if your persistent disk is D: Once the SEP client runs on the new settings you should be able to remove the old folder. Change the following registry values: To be absolutely sure open the management console and check if no problems where detected.
For this I created a PowerShell script which will do just that. It has full help capabilities so you should be able to run it with ease. It might still be useful to check it out, though. It will use Invoke-Command to run a scriptblock on these machines, that copies the definition files to the persistent disk. By default it will limit the execution to 10 concurrend sessions, in other words: When the group is online the scriptblock will run.
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. VM's must be online. Check the notification icon and the log file right after a VM has booted up. Keep an eye on this for the next couple of days. You should start to see changes in the log file pretty soon. Give it a try and let me know what you think. The only thing left to do is give you the migration script: