Tuesday, November 29, 2011
You will be presented with a list of Prerequisites. This will take a while to install all Prerequisites, however this will fail if your server is pending a reboot. You can check this by opening up Server Manger, and look down at the bottom left. If it states that it can't refresh until the server is rebooted this section WILL FAIL.
If you are installing the first XenApp 6 Server you will click on Create a new server farm. You will then be prompted with a Screen asking you for a SQL Server. It is almost the same as the screen shots below, and the rest of the install is the same.
Click on Existing Microsoft SQL Server Database
Enter the Server Name and Existing Database Name, Most of the time this will be Integrated Windows authentication
Enter in your SQL Credentials then click Test Connection.
These are the Defaults I always put into place.
This step really isn't to important as we will have to add Version and Server to the base Citrix Policy.
I have always chosen port 8080 this however can be any port number just remember what it is.
You will need to apply the below hotfix for things to work correctly.
You should be good to go...
And as always before installing anything on a Citrix Server first run the command below.
Once the installation is complete run the below command.
Thanks for reading
Friday, November 18, 2011
First log into your NetScaler, Navigate to your Session Profile you want to change the default Session Timeout. The below screen shot we are extended the Default 20 minute Timeout to 4 Hours (240 Minutes)
Once we change the value on the NetScaler we need to change the Timeout value on the Web Interface Server(s). Screen shot below shows the configuration Screen.
Also note if you are using a Load Balanced VIP for your Web Interface Servers (Highly Recommended if your not). You will want to change the Persistent cookie timeout value to match.
Thanks for reading hope this helps
Tuesday, November 15, 2011
Notice this vDisk already has one Version Plus the Base image. Also note that the one version is in “Test” Mode (we will get to this later). Click New
Now we have a new Version in “Maintenance” Mode. Click Done
Now within the Provisioning Service’s console, Under Device Collections... Select the Base/Golden image, Right Click and Select Properties, under Type Select Maintenance
Under your Hyper Visor Console... XenServer is being used in this example, Select the Base/Golden Machine
Notice we now get a few option’s when we boot up our base machine now
We are going to select Option 1, which is the new Version in Maintenance Mode.
Once the Machine boots up all the way and we login, we can verify the state of our image/Version by double clicking on the Provisioning Virtual Disk status agent.
Notice the Mode is in Read/Write now.
So here is the break down of the differences between Versions
Maintenance = Read/Write
Test = Read Only, Without affecting any other device using the base image
Production = Read Only, Pushes all changes to any device using the base image on next reboot
So to change the version, simply go back to your vDisk store, select the correct vDisk, Right Click on the vDisk and Select Versions. Click on Promote, and select Test, I highly recommend Setting to test and log back into the Base Machine, and test all applications.
Once you are satisfied with new Version following the same steps as above, Click on Promote and now we have two options, either Push this image immediate (Next reboot) or you can schedule to release the version for next reboot on a scheduled day.
So how does this look and how do I keep my vDisks in sync between local Provisioning Servers Drives.
So if you notice we have a new file type “.avhd” instead of the standard “.vhd” basically all this is doing is creating “Snapshots” and “Delta Files. So now instead of having to copy the full Flat VHD, all we have to do now is copy the Delta files too the other Provisioning Servers. So take for example the latest Version Win7_V1.3 we now only have a 320Mb file to copy across the wire instead of another 9Gb file.
Tuesday, November 8, 2011
Monday, November 7, 2011
Sunday, November 6, 2011
The bug is it works for all OS's except Windows which most people use. The fast work around (Still trying to find the fix) is to do the following:
Under c:\Program file (x86)\Citrix\Web interface\5.4.0\Clients\Windows
Create a folder named "Online Plug-in"
Copy CitrixReceiver.exe and CitrixReceiverEnterprise.exe from c:\Program file (x86)\Citrix\Web interface\5.4.0\Clients\Windows\Receiver to c:\Program file (x86)\Citrix\Web interface\5.4.0\Clients\Windows\Online Plug-in
Rename CitrixReceiver.exe to CitrixOnlinePluginWeb.exe
Rename CitrixReceiverEnterprise.exe to CitrixOnlinePluginFull.exe
That's it pretty simply work-a-round. Thanks for Reading
Saturday, November 5, 2011
Just in case you are impatient like me you just have to run the VDA installer manually as follows:
This can be found under the XenDesktop 5.5 Installer DVD
Friday, November 4, 2011
Tuesday, November 1, 2011
Updating and Testing new releases of images has never been easier. I should have a full write up pretty soon.
Anyways just wanted to give my quick opinion that this is one update you should go with! Still playing with all the new features introduced in Provisioning services 6.0.
Thanks for reading