Citrix XenApp integration and reference guide for Citrix Provisioning Server

Do you need any additional license in order to integrate Ardence into PS4.x? Will it work on all editions of PS4.x (Platinum, Advanced, etc.)?

P.S.  Sorry for not calling the products by their new names, but I think this whole name change thing is really ridiculous considering all of the screenshots in the included PDF doucumenting the inegration steps still use the old names PS4.x and Ardence.  I sort of understand using the new names for new products, but don't confuse everyone by giving a new name, and using a new name on an already existing product; it just adds to the confusion.

Hey Ruben,

Thanks for the post!  I appreciate the support.  Just clarify a bit, the concept was orginated by Brian March 26, 2007:

http://www.brianmadden.com/content/article/Using-Ardence-Disk-Streaming-with-Citrix-Servers

I then took this concept and wrote a follow-on procedure (no link sorry) in January 2007.

With the help of the community, Citrix dev team, partners and great feedbackl from Wilco van Bragt I developed this tool (with the help of a few collegues) and updated the document.  The tool itself has been around for about six months and with constaint feedback and QA and we finalized it last month.

The download mentioned above is the example of the community coming together and  helping create a solid utility!

Oh and this is the officially supported method for prepping a server to be streamed by Provisioning Server.

Regards,

Pete Downing

Provisioning Server (PVS) license model is per stream target device.  So for example, if you have 100 XenApp servers, you need a 100 licenses of PVS for Datacenters.

This concept works with all bundles of XenApp.  Proper licensing applies there as well. 

I don't think Citrix is naming its products for techies like you who already use them. They're naming them for all the people who will buy them in the future. Names like "Ardance" are meaningless. Changing it to Provisioning Server makes a ton of sense because it describes what the product does. And Citrix is hardly alone in changing the name of a product when it is aquired - unless the acquired company has huge brand recognition, which Ardance clearly did not, it makes no sense keep the old name - in fact, it makes things far more confusing for new customers who have to figure out what the heck an ardance is and what it does.

I just had a (very) quick look at that vbs scripting that accompanies the utility.  I wonder if this could be modified to quickly alter traditionally cloned servers post clone... Maybe put in the "runonce" value within HKLM prior to cloning.   Hmmmm

Gav Smythe