PVS Automatic vDisk Update Script
Description
This workflow allows for automatic updates of vDisks on a scheduled or on-call basis.
It uses a dedicated machine as an "updater" to make the process hypervisor/device agnostic, and allows for someone without dedicated PVS admin abilities to update the vDisk, as well as give it a "personality" to run scripts that aren't executed on other machines, such as copying files or running update processes.
The script:
- Restarts the updater machine with a standard vDisk to free up the Update vDisk ("standby")
- Makes a copy of the standby vDisk
- Imports and turns the copy standby into standard
- Increments the standby disk versioning and forces PVS to recognize the update
- Restores the standby disk to the update machine to continue gathering updates
The script requires no manual intervention, and can be scheduled nightly, weekly, or any other required time basis. The older disk is preserved, allowing for simple rollback, and disks are datestamped to allow for easy identification.
Required Activity Libraries
The standard Windows activity library is required for this, v. 1.0.0.0 . It can be obtained through Citrix.com
Download
Click the link below to download the workflow, then go to the Workflows section of Workflow Studio and import the file:
Follow the instructions in the Readme.txt file for configuration and setup. If you have any issues, please leave a comment here or contact me on Twitter @mcbogo.
Disclaimer
These software applications are provided to you as is with no representations, warranties or conditions of any kind. You may use and distribute it at your own risk. CITRIX DISCLAIMS ALL WARRANTIES WHATSOEVER, EXPRESS, IMPLIED, WRITTEN, ORAL OR STATUTORY, INCLUDING WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NONINFRINGEMENT. Without limiting the generality of the foregoing, you acknowledge and agree that (a) the software application may exhibit errors, design flaws or other problems, possibly resulting in loss of data or damage to property; (b) it may not be possible to make the software application fully functional; and (c) Citrix may, without notice or liability to you, cease to make available the current version and/or any future versions of the software application. In no event should the code be used to support of ultra-hazardous activities, including but not limited to life support or blasting activities. NEITHER CITRIX NOR ITS AFFILIATES OR AGENTS WILL BE LIABLE, UNDER BREACH OF CONTRACT OR ANY OTHER THEORY OF LIABILITY, FOR ANY DAMAGES WHATSOEVER ARISING FROM USE OF THE SOFTWARE APPLICATION, INCLUDING WITHOUT LIMITATION DIRECT, SPECIAL, INCIDENTAL, PUNITIVE, CONSEQUENTIAL OR OTHER DAMAGES, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. You agree to indemnify and defend Citrix against any and all claims arising from your use, modification or distribution of the code.
Comments (2)
Jul 27
Anonymous says:
What versions of Provisioning Server are compatible with this workflow?What versions of Provisioning Server are compatible with this workflow?
Jul 27
Michael Bogobowicz says:
The script was built on PVS build 5.0.2.2188, but it should work on any 5.x vers...The script was built on PVS build 5.0.2.2188, but it should work on any 5.x version, as it's based on the MCLI. It may work on earlier 4.x versions as well, but it hasn't been tested and may need some minor modifications.
Anonymous replies:
Add Comment