Today I want to start a new tradition - a series of blog posts on useful scripts that you can use to simplify the management and troubleshooting your PVS Environment. To give you a sneak peak, I'll talk about automatic replication of your vDisk, I would like to receive balloon notifications when your write cache is running out of space or how you can write event log entries when your goals are exceeding permitted number of attempts.
But that's for the future, then what am I to you today?
As I said, I like to automate and streamline repetitive tasks. PVS servers brewing is quite repetitive, especial the first building when you need to patch everything from scratch. Scenario I would share with you is used to simplify patch management for your PVS servers
First of all, let me waiting right and warn limits -. This script does not update the target devices. There, I said, now turn to the good news! 
Features
1.) Archive (.zip) is automatically analyzed
2.) correct location which files must be replaced is automatically detected
3.) the files are replaced based on the version hash (patch will not overwrite the newer file)
4.) the information is stored in the Event log (replaced + original patch file)
5.) the original files are saved automatically
6.) Detects conflict in patches (same file in multiple patches)
7.) Platform (32 64bit) is automatically selected
8.) PVS services are automatically stoped started
9.) supports -WhatIf switch, so that you can see in advance what will happen
use
I tried to keep as easy to use as possible. All you need to do is download all the patches at once, save it in a folder and run patch. By default, patch will try to find the patches in the CD-ROM, so if you do not use .iso file with the latest patches, you must specify "-Source" argument to show where you store your patches (file ).
You must not modify or extract the patch - patch will automatically and if patch is specific platform (32 64bit OS), it will automatically select subfolder okay to use
[ supported arguments
basic arguments (optional):
- Source -> folder where you store the patches
- Verbose -> Used for troubleshooting only
- WhatIf -> Patcher does not replace the files, just show what he would do
- nobackup -> not to create backup copies of the replaced files
- NOSUMMARY -> Skip summary at the end
- NoEventLog -> not write information to the Event log
arguments (even optional):
- WorkingDirectory -> current working directory
- filter -> Archive file filter (default * .zip)
- ScanLocations -> folder where PVS stores all executable
When you run the patch PVS, you should see output similar to this (notice I did not say - Source, since I'm using mounted .iso)
At the end of the performance, you will also get a summary where you can see what was done:
However, if you have Powershell ISE installed (not installed by default on Windows OS), you will get beautiful table (ignoring the state - I just used my laptop to catch without PVS) installation:
status codes
"update file" - successfully updated file
"file update failed (file in use)? "- Patcher tried to replace the file, but the operation failed
" same file (info Version) "- in the patch file is the same version as the target file (can be used with -WhatIf to identify current level patch)
"same file (hash)" - hashes are the same (can be used with -WhatIf to identify the current level of patch)
"the existing file is newer" - file versions are different, but existing file is newer than the patch file
"customer patch" - patch is used for the target device, and not for the server
"multiple destination files, conflicts" - He are several files with the same name (destination), can not decide which one is valid. Should not occur
"Destination not found" -Destination was not found
Now, before presenting the download link, please read word by word our popular warning:
"This software application is provided for" as is "without representation, warranty or condition of any kind. You can use and distribute it at your own risk. CITRIX DISCLAIMS ALL WARRANTIES, EITHER EXPRESS, IMPLIED, WRITTEN, ORAL OR STATUTORY, INCLUDING WITHOUT LIMITATION WARRANTIES oF MERCHANTABILITY, FITNESS fOR a PARTICULAR PURPOSE, TITLE aND NON-INFRINGEMENT. Without limiting the generality of the foregoing, you acknowledge and agree that (a ) 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 fully functional software application ; and (c) Citrix may, without notice or liability to you, cease to provide the current and / or future versions of the software application. In any case, the code must be used to support ultra-hazardous activities, including but not limited to life support or blasting operations. CITRIX, ITS AFFILIATES OR AGENTS BE LIABLE FOR BREACH OF CONTRACT OR ANY OTHER THEORY OF LIABILITY FOR ANY DAMAGES ARISING FROM THE USE OF THE APPLICATION SOFTWARE, INCLUDING WITHOUT LIMITATION DIRECT, INCIDENTAL, PUNITIVE, OR CONSEQUENTIAL OTHER SPECIAL, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. You agree to indemnify and defend Citrix against any claim arising from your use, modification or distribution of the code "
And now promised link to PVS same patch :.
https: // citrix . sharefile.com/d/s64542ae93f94964a
and do not forget - if you like, comment, share and spread the word
Martin Zugec
!
0 Komentar