Applying a "Virtual Patch" in Ten Easy Steps
The ability to apply a virtual patch to a software application is one of the exciting features we've been told to look forward to in a future version of SVS. Jared Payne has found a way to get this functionality today ... and he's given us the steps!
The ability to apply a virtual patch to a software application is one of the exciting features we've been told to look forward to in a future version of SVS. Here a few steps that will allow you to apply virtual patches using today's SVS.
- Start with an application installed to an SVS application layer.
- Reset the layer to make sure it is clean.
- Activate the layer.
- Run the application's update feature (do not enter capture mode).
- Create an empty layer (for this example, we'll name the layer "App_PATCH_1").
- Run WriteableSwap.
WriteableSwap application App_Patch_1 -F - Export App_Patch_1
- Send App_Patch_1 to all your client machines.
- Run WriteableSwap on the client.
WriteableSwap application App_Patch_1 -F - Enjoy a virtually patched version of your application.
If something goes wrong and the patch breaks a program or process on your client machine, there are two things you can do:
- Reset the application.
The patch was in the writeable sublayer and will be discarded. - Run WriteableSwap:
WriteableSwap application App_Patch_1 -F
This will swap the patch sublayer out and the old version of the application will work just like before.
- Login or register to post comments
- 3690 reads
- Printer-friendly version















User specific settings
Just to confirm:
This process will eleminate any user specific setting in the writeable sublayer of every client machine.
-Hamlet
WriteableSwap will cause
WriteableSwap will cause the user variables to be lost. I am working on a tool that will press the patch and the current writeable sub layer together allowing the user variables to stick.
Jared Payne
Software Engineer
WriteableSwap usable?
I guess this tool is only usable for machine specific settings?
Due to User-specific (Writeable sub layer) only containing the SID for the user created the "patch" any new user will only get the unpatched USER_TEMPLATE files and HU registries.
Great!
Sounds easy enough for most to use! Thanks for the quick and easy 10 step process...