There are a few weeks, Citrix announced XenDesktop web output 7. Many of you are probably thinking the best way to spend what you have today to XenDesktop 7. If you are not sure whether to build a new, upgrade or migration, you should check out this blog by Joe Vaccaro.
Now, if you think about upgrading, read on ... With XenDesktop 7.0 you can easily choose to upgrade your existing XenDesktop 5.x site. To do this, you can follow the steps detailed here - http://support.citrix.com/proddocs/topic/xendesktop-7/cds-xd-upgrade-procedure.html
One important and final stages of the upgrade process is to register the auditors with the site using the studio. In this blog, I want to explain how it is when you have one or more controllers in the site.
The in place upgrade option offers its customers the greatest possible uptime for your website. If you have only one controller handling your site, you should plan downtime throughout the upgrade binary and the process of making the database level. However, if you have multiple monitors, you can reduce downtime by improving window half of your controllers at a time, allowing the appropriate controllers to manage user connections during the various stages of upgrade.
If you have a single or multi-controller site, the general process is to improve your license server, your workers (ADV) and the Controller software. After that, you will need to use Studio to upgrade the database schema and register services on your controllers updated.
Start upgrading ...
Let's start with upgrading half of the Site Controllers running the Metainstaller on controllers. In this example, I had license server and studio installed on the controller, so that all installed components I upgraded simultaneously.
The database can be updated automatically or manually. If you do not have database rights required, you can select "Manual Update" to generate scripts that can be transmitted to a DB administrator. I chose "Start auto-update site" in the screen below.
You will be prompted to confirm that you have backed up your data. As a best practice to ensure that no production server is upgraded without taking a backup of the security database.
Upgrading the database schema starts, runs some tests and complete. Once completed, you can view the upgrade report by clicking on "View Report" that displays the details of all the successful work performed, warnings and failures if any, have taken place. Note that this upgrade report can not be re-generated, so save it in case you need to refer to the details of the report in the future.
If you have only one controller on your site or have updated all controllers at once, you have completed your upgrade the site and studio automatically new services registered on this controller on site.
If you have more than one controller only and updated some of them, you must continue with the upgrade of the remaining controllers in the Metainstaller. In the example below, I have the controller and Studio component is installed on the second controller.
Save the services come next
Once the components have been updated on the remaining controllers, services on these controllers must be registered with the site so that the site services (eg logging services delegated administration and configuration) are working properly.
to register the new services on the controllers with the site, you can run the studio on one controller and navigate to the top node that highlights one or more controllers in the site must be registered with the upgraded site.
Click "Perform the recording." This displays the list of controllers that should be recorded.
Click OK to save all the controllers on the site.
Note that before this stage, studio on one of the controllers can already be used for all administrative tasks that will be using site services through the controller that was updated and registered with the site. the site seems to function normally, but does not work correctly in a failover. to ensure full capacity of the site and the availability, you must complete the above registration for the remaining controllers on your site
once the controllers are registered the site upgrade is now complete and all services on the remaining controllers must be running.
It is essential to record the remaining controllers
If you have more than one controller in the site, let's say you have upgraded and registered services on one of the controllers, and then all site operations will be running throughout the upgrade controller only. This means that if there is a hardware failure or network controller, your site will be in danger. Notice that the studio console on the second and third controller stops responding that these controllers are not yet properly registered with the site. At this stage, you will not even be able to save the controllers on the site that the registration process requires the Delegated Administration Service to be operational. This can potentially cause a shutdown or failure of the site until you can grab the controller properly updated.
If you have 4 or more controllers in the site and you choose to upgrade half of controllers, you may not experience this issue you have other controllers that have been updated and recorded on the site even if one of the upgrade controllers down. However, if all controllers that have been updated and stored on the site down for unforeseen reasons, you will experience failure mentioned above.
As such, Citrix strongly recommends following the upgrade process as mentioned in the updated guidance document and perform a health check after each step in the process for that there is minimal disruption during the upgrade
If any questions, you can contact -.
Email us @ @ DesignEngineering citrix.com
Tweet @CitDesEngTest we
0 Komentar