The Citrix Client resides on the majority of workstation and Citrix servers. Periodically the client requires upgrading to the latest available version to take advantage of new functionality and to fix compatibility issues with other software.
The procedure to upgrade Citrix client from the current version involves downloading the software from Citrix and testing the installation of the variety of platforms used in the Testcorp environment.
The next step is to get the software packaged for mass installation. This installation also needs to be tested.
Once testing is complete the software IT owners need to test the new client with their software for issues.
When approval of the Citrix Client has been received by Wintel Workplace Hosting from all IT Application owners then the rollout of the software may commence.
The workstation rollout starts with IT Pilot testers globally receiving the software. After a suitable time period, the Business Pilot tester workstations receive the new Citrix Client. And finally, all business workstations can receive the new Citrix Client.
The Citrix Server rollout commences the development Citrix servers, followed by UAT and finally production servers.
Pre-requisites:
Internet access
New built workstation(s) with current OS(‘s) in production for testing (can be VM machine).
Download the software.
1. Connect to www.citrix.com.
2. Select Downloads from menu.
3. Click Citrix Clients.
4. Click Online Plug-in ver_no.
5. Next to Citrix Online plug-in All Languages click Download.
6. Follow instructions and save in test shared area
7. You may also need to download a new lockdown agent for the Launchpad virtual workstations
For each OS in TESTCORP environment e.g. Win 7 / Win XP, run CitrixOnlinePluginFull.exe on a new built workstation(s).
Make a note of any settings that are required as default e.g. pass-through authentication on and the url(s) to be used.
The new client needs to be tested on the Virtual desktop’s and a test Launchpad. (If the virtual workstations are updated the Launchpad’s should be the same version also). The launchpads need to have the Lockdown agent installed.
NOTE: Virtual PC’s use XDAgent url’s.
Testing required of each Citrix Client installation:
1. Ensure url is correct in PN Agent, http://xenapp-eu.prd.Testcorp.net/Citrix/pnAgent/config.xml
2. Reboot PC ensure connect seamlessly via PN Agent to Citrix.
3. Open several published applications.
4. Save
5. Print
Testing required of each Citrix Client installation:
1. Log onto Launchpad machine and ensure Virtual Workstation and a GPD launches automatically.
2. Ensure url is correct in PN Agent, it should be the XDAgent url, not PNAgent, http://xenapp-eu.prd.Testcorp.net/Citrix/XDAgent/config.xml
3. Reboot PC ensure connect seamlessly via PN Agent to Citrix.
4. Open several published applications.
5. Save
6. Print
2.4 Request Citrix Client is packaged
Fill out New Script Request form at http://sharepoint/sites/itinfrastructureportal/wintel/wps/packaging/Lists/Script%20Tracking1/NewForm.aspx with Workplace Build team by clicking New. Specifying the location of the source files and any settings that need to be set. (Noted in step 3.1 above).
Also log a helpdesk ticket with this information to Workplace Build team.
The client needs to be packaged with a URL for each location, and with a XDagent URl as well.
URLs are:
EU: http://xenapp-eu.prd.Testcorp.net/Citrix/pnAgent/config.xml
http://xenapp-eu.prd.Testcorp.net/Citrix/XDAgent/config.xml
NA: http://xenapp.prd.Testcorp.net/Citrix/pnAgent/config.xml
http://xenapp.prd.Testcorp.net/Citrix/xdAgent/config.xml
AP: http://xenapp-ap.prd.Testcorp.net/Citrix/pnAgent/config.xml
http://xenapp.prd.Testcorp.net/Citrix/XDAgent/config.xml
Once script has been created. Test again on workstations including virtual PC’s . Tests to be performed as 3.2 Testing.
Once the package(s) to install Citrix Client has been tested the job and package needs to moved to the production area i.e. \\corp\dfsroot\global\dp
To do this complete a Change Control using the template specified in Guide to Creating a Change Management for Production Package deployment from Workplace Sharepoint site. i.e. or follow your company change control or CAB
Ensure that Business Justification, Install Plan, Test Plan, Back Out Plan & Risk Assessment are completed in Tasks.
Also, add Config. Services as Approvers.
Ensure that a deployment job has been created in SCCM for the package,
Prior to the rollout of the new Citrix Client sign-off from each IT Application Owner must be obtained for all business critical applications.
list them and do a quick test
This is not a finite listing and any other major software judged to be affected by Citrix Client should be tested.
Each team must be emailed as we need written proof that testing has been completed successfully for each application.
This is an example email to be sent to each team for testing of the Citrix Client.
Wintel – Wintel Workplace Hosting team are proposing to upgrade the Citrix Client software on all workstations to version xx.x in the near future. This is so that we can utilise the benefits of the new Citrix client.
Prior to the widespread roll-out of the new software we would like to ensure that all major applications hosted by Citrix continue to function correctly with the new Citrix client.
To this end please would you
a, provide names from within IT who would be willing to test the Citrix client with the applications that you support and contact the Vendor to ensure this version of Citrix Client is supported by them, and
b, provide names of clients who would be willing to test the Citrix client once your testing is complete?
List the Major client apps
The package for the new Citrix Client version should be sent to each testers workstation via Software deployment tool e.g. SCCM job. Testers are to ensure full functionality of their software, including printing.
Once IT Application owner teams confirm they have successfully tested the new Citrix Client for the software to be installed the usual procedure for rolling out software is to be implemented. Do NOT proceed until all software has been signed-off and any issues resolved.
Any issues that arise should be documented, with the resolution, for future reference.
Any dependencies or software that requires re-installation post Citrix Client upgrade should be noted.
E.g. version 11.2 had pre-requisites of Microsoft .NET Framework 2.0.
The Citrix Client 11.2 SCCM job requires a reboot after install so that Single Sign On is enabled correctly.
in Some unites we may need to re-installed after the Citrix Client installation. (This was due to the drivers for Citrix Client no longer use ini files but stored in registry from version 10 onwards).
Also, at present there are jobs for each url required e.g. 2 installations for each location; one is for PNAgent url the other for XDAgent url. There are 3 locations; AP, EU and NA therefore there are a total of 6 installations.
The process for rolling out software to workstations in the business must be followed for Citrix Client upgrades.
That is software is sent to the global IT Pilot Testers before sending to global Business Pilot testers. Both virtual and physical workstations are targeted.
Only when there are no reported issues from these clients are we able to proceed to add the Citrix Client into production.
For each rollout; Change Controls must be completed and communication approved and sent to clients. A resource in Workplace Build team must be contacted and agree to own the software deployment jobs sent to the workstations.
A resource in Workplace Build team must be contacted and agree to own the software deployment jobs for the IT Pilot and Business Pilot rollouts. Dates and times of the rollout must be mutually convenient to Workplace Build team member and Wintel Workplace Hosting team.
Please ensure the date and time agreed for the rollout does not coincide with any other software rollouts including Microsoft patches.
Workplace Build team member will set up the Citrix Client install to run overnight and report back to Wintel Workplace Hosting team member with job results.
Members of the groups targeted to receive the jobs are the responsibility of Workplace Build team.
Change Control should be raised using the in Guide to Creating a Change Management for Production Package deployment as per section 3.5.
To do this:
1. complete a Change Control using the template specified in Guide to Creating a Change Management for Production Package deployment
2. Ensure that Business Justification, Install Plan, Test Plan, Back Out Plan & Risk Assessment are completed in Tasks.
3. Ensure the Notes field of the Change has all the details of Installation Process see 4.6 with pre- & post requisites. Also, detail if there are different jobs for Virtual machines to physical machines.
4. Also, add Config. Services as Approvers.
A Change Control is required for both IT Pilot and Business Pilot.
Communication must be sent to clients when their Citrix Client software is updated.
The communication must be approved by our team manager, (Workplace Services - Mitch Stead), at least 3 working days prior to the communication being received by the intended clients.
Please refer to the Testcorp Global IT Client Communication Process documentation for additional information. (Although Mitch is not mentioned on the list, he is the manager for approval of communications for Workplace Services).
The communication has to be approved by our immediate manager, Mitch Stead, we can then send on to Client Communication with date and time of communication and email addresses to send it to, 3 days before it needs to be sent. Which should be 2 days before the install is sent to workstations.
