For all the power of PVS, a large management around can prove a tedious and time consuming task.
[1945001mehrereGoldplattenDutzendevonAnwendungsgruppenundverschiedeneBenutzerSilosmitspeziellenAnforderungenmit], it is not just a spin on it and forget it type of thing. The right automation provides the foundation you need to: - providing updated gold discs
- spin up and spin-down capacity in a silo based on thresholds you determine
- Begin your ability to deal with such. on demand not static silos
PVS comes with a PowerShell add-in to tame not an easy animal.
with the PowerShell SDK for other Citrix products such as XenDesktop and XenApp, use the cmdlets there PowerShell objects back. These are easy to manipulate, query and change. The PVS PowerShell snap-in, which is not the case. Commands problem, although the PVS PowerShell snap-in, MCliPSSnapin, any items back. Instead, we are presented with large unsightly blocks of text. For example, if I run a query that was the details of a device to get in my yard, this is the kind of issue that I can expect to get:
For if you add details about multiple objects that are capturing the text block just keeps on growing! The more objects that you have, the harder it is to manage the output. How can we exploit what could possibly be some very powerful automation functionality for our PVS environment so?
The key is the ability to predict what text appears in the issue and where it will appear. Let's take the above command and output as an example. If you issue the command, we can return the output to a variable array. By knowing which line of output containing the piece of information that we will need to extract to appear, we will be able to detect it. If I wanted the device ID field, I could do:
$ result = MCLI-Get-unit p = device DEVICE001
$ line info = $ result [4]
I know that the 5-slot includes the arrangement of the text line, which corresponds to the device ID field. is This leaves us with the entire line of text, however, so some additional manipulation required
$ split position = result.IndexOf ( ":") ;.
$ deviceID = $ lineinfo.Substring ($ split position + 2 $ lineInfo.Length, - (split position $ + 2));
I can see the position of the colon against the string and then used to split the string, so I have only the information on the right hand side of the separator.
as part of our Synergy Geek Speak Live off! Session, we will show you how to use how these techniques to on demand capacity provide automation of PVS PowerShell in 9 simple steps for your PVS environment available with:
- Get Explore the name of the replacement device in the source collection.
- to the details of this replacement.
- to get the name of a device in the target collection.
- to the vDisk details of this device.
- to delete the replacement device from the source collection.
- , add to the replacement device to the target collection.
- assign the vDisk to spare.
- to add the device to AD Group / delivery. Group
- boot on it to connect the device
Make us at Synergy 2015 breakout session SYN514 in Orlando. Turn XenApp and XenDesktop in Capacity on Demand with Provisioning Services Automation and learn how you can shine your PVS infrastructure!
Paul Stansel is a 18-year Citrix lawyer who is currently working as an architect focusing on EUC and cloud solutions for a large insurance company. He has architected and implemented solutions for several Fortune 100 companies and has participated in the Citrix Customer Advisory Council. Paul speaks at various industry events and runs the popular blog citrixtips.com. Follow Paul on Twitter.
Shane O'Neill is a senior engineer for a large insurance company with responsibility for more than 50,000 virtual users. Shane is a strong supporter of the use of automation where possible to optimize various processes associated with Citrix products and improve. He has used experience in developing and providing solutions for reporting, managing and optimizing XenDesktop, XenApp, PVS and VMWare # PowerShell and C. You can follow Shane on Twitter.
Citrix invited at Citrix Synergy to present the author of this blog post 2015 and in a related competition participate. The author has received an entry in the competition this blog for tabling
0 Komentar