Friday, July 23, 2021

Lakeside Systrack - License violation

 In Systrack deployment tool, if you run license tree it will shows there are no violations. But when Systrack client agent try to communicate with server and it fails with license violation.

Solution: Even the licenses are out, the license validation tool shows there  are no violations because used license  number shows only 5 or 6 digits which are always less than the total licenses. I added more licenses and then clients start to talk to Systrack servers.

Have a nice day


Saturday, April 25, 2020

Migrating Citrix Virtual Apps and Desktops from on-premises to Citrix Cloud


Found an excellent article on "Migrating Citrix Virtual Apps and Desktops from on-premises to Citrix Cloud"


Source is Citrix Docs -docs.citrix.com

Migration Design and Strategies

#1 – Migrating the Control and Access Layer components to Citrix Cloud, integrating with Citrix Gateway Service

In this approach, the Control Layer components named Delivery Controllers, Database Servers, License Servers, and the Access Layer components named StoreFront Servers and Gateway are provisioned on Citrix Cloud and integrated with Citrix Gateway Service. The Cloud Connectors are deployed at customer-hosted locations known as resource locations. Users can securely access the Citrix Cloud environment through the Citrix Gateway Service from anywhere. The Gateway Service provides a secure remote access solution with diverse identity and access management capabilities to deliver a unified experience for apps and desktops. After the migration, the users need to access the Citrix Cloud Workspace URL for example, https://examplecustomer.cloud.com to access the Citrix environment.
cloud-migration-strategies-Image-2

#2 - Migrating the Control Layer components integrating with On-Premises StoreFront and Gateway

In this approach, the Control Layer components are migrated to Citrix Cloud, but the Access Layer components remain at the on-premises environment. This approach provides extended access utilizing existing StoreFront and Citrix Gateway deployments to retain their access methodology. Users access the environment through on-premises Gateway and StoreFront which communicate with Citrix Cloud for resource enumeration. After the migration, users can access the Citrix environment with the existing On-Premises Gateway URL https://CVAD.Customer.com.
cloud-migration-strategies-Image-3

#3 - Migrating the Control Layer components and StoreFront Services to Citrix Cloud and integrating Citrix Workspace with On-Premises Gateway

In this approach, the Control Layer components and StoreFront services are migrated to Citrix Cloud and Citrix Workspace is configured with On-Premises Gateway for accessing the workloads. This approach provides extended and optimal access utilizing existing On-Premises Citrix Gateway deployments to enable remote access for the workloads. Users access the environment through Citrix Workspace URL for the resource enumeration. When users launch a desktop or application, the ICA connection is then established via the on-premises Gateway to the workloads(VDA). After the migration, the users need to access the Citrix Cloud Workspace URL for example, https://examplecustomer.cloud.com to access the Citrix environment and the On-Premises Gateway for ICA Proxy.
cloud-migration-strategies-Image-4
Have a nice day!

Monday, October 9, 2017

Upgrade to XenApp 7.15 LTSR/XenDesktop 7.15 LTSR


Upgrade Sequence

The following diagram summarizes the upgrade sequence.

localized image

Which product component versions:

XenApp version 7.5 or later
XenDesktop 5.6 or later

See the list for other components:
https://docs.citrix.com/en-us/xenapp-and-xendesktop/7-15-ltsr/upgrade-migrate/upgrade.html

Upgrade procedure

To run the product installer graphical interface, log on to the machine and then insert the media or mount the ISO drive for the new release. Double-click AutoSelect. To use the command-line interface, see Install using the command line.
Step 1. If more than one core component is installed on the same server (for example, the Controller, Studio, and License Server) and several of those components have new versions available, they will all be upgraded when you run the installer on that server.
If any core components are installed on machines other than the Controller, run the installer on each of those machines. The recommended order is: License Server, StoreFront, and then Director.
Step 2. If you use Provisioning Services, upgrade the PVS servers and target devices, using the guidance in the Provisioning Services documentation.
Step 3. Run the product installer on machines containing VDAs. (See Step 12 if you use master images and Machine Creation Services.)
Step 4. Run the product installer on half of the Controllers. (This also upgrades any other core components installed on those servers.) For example, if your Site has four Controllers, run the installer on two of them.
  • Leaving half of the Controllers active allows users to access the Site. VDAs can register with the remaining Controllers. There may be times when the Site has reduced capacity because fewer Controllers are available. The upgrade causes only a brief interruption in establishing new client connections during the final database upgrade steps. The upgraded Controllers cannot process requests until the entire Site is upgraded.
  • If your Site has only one Controller, the Site is inoperable during the upgrade.
Step 5. If Studio is installed on a different machine than one you've already upgraded, run the installer on the machine where Studio is installed.
Step 6. From the newly upgraded Studio, upgrade the Site database. For details, see Upgrade the databases and the Site.
Step 7. From the newly upgraded Studio, select Citrix Studio site-name in the navigation pane. Select the Common Tasks tab. Select Upgrade remaining Delivery Controllers.
Step 8. After completing the upgrade and confirming completion, close and then reopen Studio.
Step 9. In the Site Configuration section of the Common Tasks page, select Perform registration. Registering the Controllers makes them available to the Site.
Step 10. After you select Finish when the upgrade completes, you are offered the opportunity to enroll in the Citrix telemetry programs, which collect information about your deployment. That information is used to improve product quality, reliability, and performance.
Step 11. After upgrading components, the database, and the Site, test the newly-upgraded Site. From Studio, select Citrix Studio site-name in the navigation pane. Select the Common Tasks tab and then select Test Site. These tests were run automatically after you upgraded the database, but you can run them again at any time.
The Test Site functionality might fail for a Controller installed on Windows Server 2016, when a local SQL Server Express is used for the Site database, if the SQL Server Browser service is not started. To avoid this, complete the following tasks.
1. Enable the SQL Server Browser service (if required) and then start it.
2. Restart the SQL Server (SQLEXPRESS) service.
Step 12. If you use Machine Creation Services and want to use upgraded VDAs: After you upgrade and test the deployment, update the VDA used in the master images (if you haven't done that already). Update master images that use those VDAs. See Update or create a new master image. Then update machine catalogs that use those master images, and upgrade Delivery Groups that use those catalogs.

Upgrade the databases and the Site

After upgrading the core components and VDAs, use the newly upgraded Studio to initiate an automatic or manual database and Site upgrade.
Remember: Check the Preparation section above for permission requirements.
  • For an automatic database upgrade, the Studio user's permissions must include the ability to update the SQL Server database schema. 
  • For a manual upgrade, the Studio user runs some of the generated scripts from Studio. The database administrator runs other scripts, using either the SQLCMD utility or the SQL Server Management Studio in SQLCMD mode. Otherwise, inaccurate errors can result.
Important: Citrix strongly recommends that you back up the database before upgrading. See CTX135207.
During a database upgrade, product services are disabled. During that time, Controllers cannot broker new connections for the Site, so plan carefully.
After the database upgrade completes and product services are enabled, Studio tests the environment and configuration, and then generates an HTML report. If problems are identified, you can restore the database backup. After resolving issues, you can upgrade the database again.
Upgrade the database and Site automatically:
Launch the newly upgraded Studio. After you choose to start the Site upgrade automatically and confirm that you are ready, the database and Site upgrade proceeds.
Upgrade the database and Site manually:
Step 1. Launch the newly-upgraded Studio. After you choose to manually upgrade the Site, the wizard checks for License Server compatibility and requests confirmation. After you confirm that you have backed up the database, the wizard generates and displays the scripts and a checklist of upgrade steps.
Step 2. Run the following scripts in the order shown.
Script
Description
DisableServices.ps1
PowerShell script to be run by the Studio user on a Controller to disable product services.
UpgradeSiteDatabase.sql
SQL script to be run by the database administrator on the server containing the Site database.
UpgradeMonitorDatabase.sql
SQL script to be run by the database administrator on the server containing the Monitor database.
UpgradeLoggingDatabase.sql
SQL script to be run by the database administrator on the server containing the Configuration Logging database. Run this script only if this database changes (for example, after applying a hotfix).
EnableServices.ps1
PowerShell script to be run by the Studio user on a Controller to enable product services.
Step 3. After completing the checklist tasks. click Finish upgrade.

XenApp 6.5 Migration to XenApp/XenDesktop 7.15 LTSR

Here are the recommendations from Citrix to migrate XenApp 6.5 farms to XenApp/XenDesktop 7.15 LTSR. I too recommend this and followed it..

XenApp 6.5 migration

In Place Upgrade of VDAs:
The XenApp 6.5 migration process helps you more efficiently and quickly transition from a XenApp 6.5 farm to a Site running XenApp 7.15 LTSR (or a later supported release). This is helpful in deployments that contain large numbers of applications and Citrix group policies, lowering the risk of inadvertently introducing errors when manually moving applications and Citrix group policies to the new XenApp Site.
After you install the XenApp 7.15 LTSR core components and create a Site, the migration process follows this sequence:
  • Run the XenApp 7.15 installer on each XenApp 6.5 worker, which automatically upgrades it to a new Virtual Delivery Agent for Server OS for use in the new Site.
  • Run PowerShell export cmdlets on a XenApp 6.5 controller, which exports application and Citrix policy settings to XML files.
  • Edit the XML files, if desired, to refine what you want to import to the new Site. By tailoring the files, you can import policy and application settings into your XenApp 7.15 LTSR Site in stages: some now and others later.
  • Run PowerShell import cmdlets on the new XenApp 7.15 Controller, which import settings from the XML files to the new XenApp Site.
Reconfigure the new Site as needed, and then test it.
Here you are going to transfer application glitches or bugs from previous farm.
https://docs.citrix.com/en-us/xenapp-and-xendesktop/7-15-ltsr/upgrade-migrate/xenapp-worker-upgrade.html


Parallel migration:
Build new farm using XenApp/XenDesktop 7.15 LTSR with new site and controllers. Create Machine catalogs, Delivery groups and application groups for new farm. Upgrade license server /or install a new license server to cater licenses to new farm.
New two farms are up and running. Follow the application migration life cycle to migrate apps from legacy farm to new farm.
I prefer Parallel migration as such there is no downtime for business. Applications can be migrated cleanly by this method.
Have a nice day!

XenApp 7.15 LTSR & XenDesktop 7.15 LTSR

Citrix has released new version of  XenApp 7.15 LTSR/XenDesktop 7.15 LTSR last month. Enterprise community was waiting for LTSR version after 7.6 for so long time.

Download:
https://www.citrix.com/downloads/xenapp-and-xendesktop/

Product documentation:
https://docs.citrix.com/en-us/xenapp-and-xendesktop.html

Have a nice Day!

Friday, February 24, 2017

Citrix released XenApp 7.13 & XenDesktop 7.13

Yesterday 2/23/2017 Citrix released a CR of XenApp 7.13 & XenDesktop 7.13.


http://docs.citrix.com/en-us/xenapp-and-xendesktop/7-13/whats-new.html


Have a nice day!!!

Tuesday, February 14, 2017

Customization of Storefront web pages



Here is the good article on customization:


http://www.citrixguru.com/2016/03/08/lab-ultimate-storefront-customization-guide/


I got issues even after modifying script.js and style.css files. I couldn't see changes.


Cause: The Text is too long with breaks.


Sol:I removed breakes/gaps and made it as single line text.


Cause 2: I didn't remove one of the quotes  "/*" o& "*/" .


Sol: Removed it and it started working.