Before starting Upgradation you should follow the below prerequisites
ISO file or setup file should be copied on local drive or network drive
Servers must be in Correct Sequence while upgrading.
Backup is very important, if any thing goes wrong then we can restore it back with backup. Recommendation : a. Snapshot backup b. Disk level ( Clone )
Note : Below is the sequence for Servers.
Licence Server should be upgraded with 7.5
StoreFront should be upgraded with 2.5
Then DDC with 7.5
Supported operating systems:
Windows Server 2012 R2, Standard and Datacenter Editions Windows Server 2012, Standard and Datacenter Editions Windows Server 2008 R2 SP1, Standard, Enterprise, and Datacenter Editions
Disk space: 100 MB Microsoft .NET Framework 3.5 SP1 (Windows Server 2008 R2 only) Microsoft .NET Framework 4.5 Windows PowerShell 2.0 (included with Windows Server 2008 R2) or 3.0 (included with Windows Server 2012 R2 and Windows Server 2012) Visual C++ 2005, 2008 SP1, and 2010 Redistributable packages
Supported Microsoft SQL Server versions for the Site Configuration Database (which initially includes the Configuration Logging Database and the Monitoring Database):
Recommendation: Must use SQL 2012 with cluster (Always ON)
Note: Be very careful while giving Database name because if once the database name has been put, it can not be changed. Only Logging Database and Monitoring Database can be changed.
SQL Server 2012 SP1, Express, Standard, and Enterprise Editions. By default, SQL Server 2012 Express is installed when installing the Controller, if an existing supported SQL Server installation is not detected.
SQL Server 2008 R2 SP2, Express, Standard, Enterprise, and Datacenter Editions.
The following database features are supported (except SQL Server Express, which supports only standalone mode):
SQL Server Clustered Instances
SQL Server Mirroring
SQL Server 2012 AlwaysOn Availability Groups
Windows authentication is required for connections between the Controller and the SQL Server database.
Studio Supported operating systems:
Windows 8.1, Professional and Enterprise Editions Windows 8, Professional and Enterprise Editions Windows 7 Professional, Enterprise, and Ultimate Editions Windows Server 2012 R2, Standard and Datacenter Editions Windows Server 2012, Standard and Datacenter Editions Windows Server 2008 R2 SP1, Standard, Enterprise, and Datacenter Editions
Requirements: Disk space: 75 MB Microsoft .NET Framework 3.5 SP1 (Windows Server 2008 R2 and Windows 7 only) Microsoft .NET Framework 4.5 Microsoft Management Console 3.0 (included with all supported operating systems) Windows PowerShell 2.0 (included with Windows 7 and Windows Server 2008 R2) or 3.0 (included with Windows 8.1, Windows 8, Windows Server 2012 R2, and Windows Server 2012)
Director Supported operating systems:
Windows Server 2012 R2, Standard and Datacenter Editions Windows Server 2012, Standard and Datacenter Editions Windows Server 2008 R2 SP1, Standard, Enterprise, and Datacenter Editions Requirements: Disk space: 50 MB. Microsoft .NET Framework 4.5. Microsoft Internet Information Services (IIS) 7.0 and ASP.NET 2.0. If these are not already installed, you are prompted for the Windows Server installation media, then they are installed for you. Supported browsers for viewing Director: Internet Explorer 11, 10, and 9. Compatibility mode is not supported for Internet Explorer. You must use the recommended browser settings to access Director. When you install Internet Explorer, accept the default to use the recommended security and compatibility settings. If you already installed the browser and chose not to use the recommended settings, go to Tools > Internet Options > Advanced > Reset and follow the instructions.
# Centralized User Authentication Using vCenter Single Sign On (vCenter SSO):
We are discussing on users authentication to an ESXi host in the prospective of a user account created & stored locally on that host. Generally without vCenter server you would need a separate user account on each ESXi host for each administrator who needed access to the server. As the number of ESXi hosts & required administrators grows the number of accounts to manage grows exponentially. There are workarounds for this overhead that is integrating your ESXi hosts into Active Directory (AD). Administrative effort required for a small virtualized infrastructure is not a big deal or major concern. In this situations, vCenter server management might not be missed but it is very important for big infra. In addition to it’s management capabilities, vCenter can perform vMotion, Configure DRS, establish vSphere HA, use vSphere fault tolerance & these features are not accessible without vCenter server and also the key functionality such as host profiles, vSphere distributed switches, profile driven storage & vSphere update manager.
Take an example here we have 20 hosts and 10 Administrators, the administrative efforts of maintaining all these local accounts on ESXi hosts becomes difficult. In a new account is needed to create to manage these 20 hosts then you have to create that account to each host separately & if you need to change your account password then also you need to change it on 20 different hosts. Then add this equation into other VMware components such as vCloud director or vCenter orchestrator with their own possible account and passwords.
vCenter SSO ( Single Sign ON) is the exact solution for the above problem and it is prerequisite for installing vCenter server. In 5.x Version vCenter cannot be installed without installing SSO first.
# How SSP works and What other software it interacts with (Both VMware and Non-VMware):
In the earlier versions of vSphere 5.1 when you logged onto vCenter your authentication request was forwarded to either the local security authority on vCenter server OS or Active Directory. With SSO the request can still going to Active Directory but it can also go to the list of locally defined users within SSO itself or to open LDAP. SSO is attached with vCenter, vCloud Director (VCD), vCenter Orchestrator (VCO), vCloud Networking & Security (vCNS), SSO can take a single user & provide than access to everything they need through virtual infra with a single username & password & with a secured way.
1. First Copy the setup file locally (Recommendation is to copy it on local disk) Since we already have an existing installation of XenDesktop 7.5 Which is having all these roles (Director, License Server, StoreFront, and Studio). Double click on Auto Select and start the installation.
2. Then it will prompt you a license agreement window, accept the licence agreement and click next to proceed further. 3. Following are the steps below to upgrade the XenDesktop from 7.1 to 7.5 :
 Back up the Delivery Controller databases  Upgrade the Virtual Delivery Agent and perform an image update on all master images  upgrade half of the delivery Controllers (all components)  use the upgraded version of studio to perform the site upgrade, and then finally  upgrade the remaining Delivery Controllers (all components).
Click on ready to continue check box and click next. 4. Here you will get a License Message (Upgrade your license server first which is recommended) .Click on let me continue check box and Next. 5. click on Automatic configuring firewall rules and click next. 6.You can review the prerequisites and click on upgrade. 7.Then you can see the upgradation installation process completing .This will upgrade all the Core Components and installing component initialization post Installation and click on finish. 8. After installing you can launch citrix studio. 9. Click on automatic site upgrade . 10. You will get a new window for Upgrading a site and click on ready to upgrade. 11. Then it will prompt you a progress bar for upgrading your site. 12. After successfully upgrading it, the below screen is prompted, then click on Test site and do the validation. DDC is successfully upgraded.
How to install an ESXi in a VMware workstation or in Virtual Server ?
1. Power On the ESXi Host then it will ask you to continue.Click inside the screen and press enter ,then it starts installing the installer and not yet started installing ESXi (as it is installing all the components and loading the files that are needed).
2. Press enter to start the installation process.
3. Then it will ask you to format your disk drive in VMFS format and you can preview the details by pressing F1. Press Enter to continue further.
4. It will ask you for the keyboard by pressing arrow keys to scroll up and down for selecting US Default or you can choose as per your language. Press Enter to continue.
5. It will ask you for the Root password and click on Enter to continue.
6. It will ask you for the confirmation to install ESXi ,for that you need to press F11.
7. It starts installing with a progress bar.
8. After installation you will get below screen which will ask you to reboot your system but before that you need to be very careful as you have to remove your installation disc else it will start installing it again. After unmount the ISO file or CD, reboot the system.
How to create a virtual machine in VMware workstation 10 ?
1. Click on VMware workstation icon.
2. Click on create a new virtual machine.
3. It will prompt you a welcome wizard. Choose any of the options between Typical and Custom as per your convenience. I choose typical and click next.
4. Now in this wizard you need to put your ESXi iso image that is either through your CD/DVD drive or from your local computer from browse button. I choose the second option and select an iso image from my local computer.
5. Then it will ask you for the Virtual machine’s name as per your naming convention and provide location to save this virtual machine by clicking on browse button. Click next.
6. Then it will ask you for maximum disc space, you can select as per your requirement and select split virtual disk in to multiple files rather than into a single file option. Click next
7. In this step you can edit your hardware settings by clicking on customize Hardware tab.You can edit your Virtual machine hardware like if you want to increase RAM and add HDD . Click next and finish
XenServer 6.2 has been installed on Physical hosts.
1. Need to open Firewall Ports.
TCP/UDP 53, 137 – for DNS (2) TCP/UDP 123- for NTP Time Service (3) TCP/UDP 139, 445 – for ISO Management, File share
For More please refer : http://support.citrix.com/servlet/KbServlet/download/2389-102-704421/CTX101810_28th_June_2013.pdf
2. You have to choose which method you want to select like Local Media or PXE Boot from TFTP Server. I have choose local media for the XenServer installation.
3. After that you have to decide which storage like local drive or SAN storage. For Best practice it is recommended to have SAN storage only ,which will be used for the XenServer Installation location and the Virtual Machine Storage.
4. You have to choose the host which have multiple Network Interface Cards so that these can be used for the purposes like System Management, Virtual Machine Management, XenMotion.
5. A static IP address and Server name.
6. A NTP server is required for the installation of XenServer.
Installation Steps :
1. Connect host iLO on http://10.10.10.5.
2. Enter Username and Password for iLO Access
3. Select Remote Console and Launch the Integrated Remote Console
4. Press F9 Key to access the BIOS at boot up time.
5.Go to 2nd option HP Power Profile and then Enter and select Balanced Power and Performance (for Better performance).
6. Then Go to HP Power Regulator > select HP Dynamic Power Savings Mode and then Enter to proceed further.
7. Then Go to Energy/Performance Bias and select Balanced Performance. Press Enter to proceed.
8. Apply the settings and Restart the Server.
9. After that you have to click on Virtual Drive to Add the ISO or CD ROM.
10. Locate the ISO file for XenServer.
11. Initiate a restart for the host server.
12. In the first XenServer screen do not press ‘Enter’,Press F2 as quickly as possible
13. Here you have enabled multipath for the Server
14. Type multipath for this server so that this server will acknowledged about multipath enabled for Root disk cause this server will boot from SAN.
16. In the Welcome screen for this XenServer Setup and select ‘OK’.
17. It will ask you for the citrix license agreement, choose ‘Accept EULA’ to proceed further.
18. Select the Boot LUN that will contain the XenServer Host Installed on. Click Ok.
19. Select the disk which would use for storing the Virtual Machine. This storage will used for storing virtual machine files. In my case i am not selecting any LUN as of now.
20. You can select “Enable for Thin Provisioning” here or if the LUN is already thin provisioned for the Storage then you can leave it blank as above.
21. Select ‘Continue’ to confirm no LUN’s have been selected for Virtual Machine storage.
22. Select the Installation Source as ‘Local Media’ and choose ‘OK.
23. Select ‘Yes’ to installing ‘Supplemental Packs’
24. Select ‘Skip verification’ on the Verify Installation Source screen and click Ok.
25. Put the password and confirm it. Select ‘OK’
26. Choose the primary Network Management Interface that will be used to connect to XenCenter, and choose ‘OK’ to proceed.
27. Configure the Management NIC with a static IP address in this range (10.10.10.x) and click on Ok.
b) Subnet Mask
c) Default Gateway
28. Specify the new hostname and associated DNS information in the DNS configuration section. Select ‘OK’ to proceed.
29. Select the Time Zone, as per your geographical area where you Host is located and then by city. Choose ‘OK’ to proceed.
30. Enter the name of the local NTP server and choose ‘OK’
31. Select ‘Install XenServer’
32. The installation starts and it will come up with a progress bar.
33. Set the date and time accordingly and click Ok.
34. Once the installation completes, eject the installation CD before reboot it else it will start XenServer installation again from beginning and then select ‘OK’ to reboot the server.
After the server reboots, XenServer display the ‘xsconsole’ which is a system configuration console. To access a local shell from the xsconsole, press ALT+F3, and to return it back to the xsconsole, press ALT+F1.