Zip Express v2.7.14.1 serial key or number
Zip Express v2.7.14.1 serial key or number
Citrix Virtual Apps and Desktops (CVAD) Upgrades
Navigation
Change Log
Citrix Virtual Apps and Desktops (CVAD) Versions
Version Numbering
Citrix Virtual Apps and Desktops (CVAD) is the new name for XenApp and XenDesktop.
The most recent version of Citrix Virtual Apps and Desktops (CVAD) 7 is . The version number is based on YYMM (Year Month) format.
XenApp and XenDesktop 7.x versions range from through . is the last version of XenApp and XenDesktop. Citrix Virtual Apps and Desktops (CVAD) , , , , , , and are newer than XenApp and XenDesktop
Release Notifications
Follow my Twitter or EUC Weekly Digests for new release notifications.
Sometimes release notifications are posted to Citrix Blogs, but this is not comprehensive.
Watch Citrix Discussions and Citrix Support Knowledgebase to learn about known issues that are fixed in a later release.
Release Classifications &#; LTSR, CR
Image from Citrix Blog Post What’s New in XenApp, XenDesktop and XenServer November
There are three classifications for on-premises releases:
- LTSR (Long Term Service Release) &#; these releases get 5 years of mainstream support from the release date, plus up to 5 more years of paid extended support
- CR (Current Release) &#; 6 months support from the release date. Updated quarterly.
- LTSR Compatible Components &#; non-LTSR components running in a LTSR implementation. This classification provides exceptions to the requirement that all components must be LTSR versions.
Citrix Virtual Apps and Desktops (CVAD) is a bundle of components. Long Term Support requires the components to be specific versions. Any deviation from the required versions results in loss of Long Term Support, and instead is classified and supported as a Current Release. Use Citrix LTSR Assistant tool to confirm LTSR compliance.
LTSR Programs
There are three different LTSR programs:
LTSR Licensing requirement
LTSR requires you to be on Customer Success Services Select, formerly known as Software Maintenance.
LTSR vs CR
Support Duration
LTSR is supported for 5 years from the LTSR release date, plus 5 more years of optional, paid extended support.
- LTSR Cumulative Updates (similar to service packs) are released periodically. Cumulative Updates for LTSR are installed exactly like upgrading to a newer Current Release, except you don&#;t get any new features.
- Cumulative Updates are released only for LTSR versions. To patch a Current Release, upgrade to the newest Current Release.
- Be prepared to install these LTSR Cumulative Updates every 6 months. Workspace app LTSR (or Receiver LTSR) too.
Current Releases are end-of-maintenance after 6 months, and end-of-life after 18 months.
- Be prepared to upgrade to a newer Current Release every 6 months. Workspace app too.
See Lifecycle Milestones for Citrix Virtual Apps & Citrix Virtual Apps and Desktops for an explanation of support durations for each release classification.
In either case, you are expected to perform some sort of upgrade or update approximately twice per year.
Release Frequency
New LTSR versions are released every months.
There are three LTSR releases: LTSR , LTSR , and LTSR
Cumulative Updates (CU) for LTSR are released every few months. Don&#;t forget to install these patches. I&#;ve seen CUs fix LTSR issues.
- Cumulative Updates do not include new features.
- Citrix has released one Cumulative Update for LTSR , bumping up the version to
- Citrix has released eight Cumulative Updates for LTSR , bumping up the version to
- Citrix has released six Cumulative Updates for LTSR , bumping up the version to
- Citrix will continue to release Cumulative Updates for all currently supported LTSR versions.
New Current Release versions are released every quarter. Sometimes longer for Workspace app.
Some Citrix Virtual Apps and Desktops (CVAD) components are released on a separate schedule from the main LTSR or Current Release releases:
- App Layering
- Workspace Environment Management
Citrix Provisioning version numbers don&#;t line up with Citrix Virtual Apps and Desktops (CVAD) LTSR Cumulative Update version numbers:
- Citrix Virtual Apps and Desktops (CVAD) LTSR CU1 comes with Provisioning Services CU1
- XenApp/XenDesktop (LTSR CU6) comes with Provisioning Services
- XenApp/XenDesktop (LTSR CU8) comes with Provisioning Services
Current Release cons
New Current Releases add new features, and new bugs. For example:
- The initial release of Citrix Virtual Apps and Desktops (CVAD) Current Release had some upgrade issues and disconnect issues which required it to be pulled and re-released.
- The initial release of Citrix Virtual Apps and Desktops (CVAD) Current Release had some upgrade issues which required it to be pulled and re-released.
- The initial release of XA/XD Current Release had some issues which required it to be pulled and re-released.
- Current Release had issues (e.g. VDA registration error message), that weren&#;t fixed until
- Receiver has some issues with drop-down boxes that requires a newer version of Receiver or Workspace app to fix.
No hotfixes will be released for Current Releases. To get hotfixes, upgrade to the newest Current Release.
LTSR cons
Features not in LTSR &#; Some features are not included in the LTSR program. In other words, these features don&#;t get 5 years of support, and might not even be included in the LTSR installer.
- Personal vDisk and AppDisks &#; Note: these are replaced by User Personalization Layers.
- Framehawk
Features in Current Release but not LTSR:
- Upcoming CVAD Current Release Version will have new features that are not in LTSR. Will you upgrade to CVAD , which puts you on the Current Release upgrade train? Or will you wait until the next LTSR, probably released sometime in ?
- Another option is to remain on LTSR (with latest cumulative update) until you see a Current Release with new features that are desirable enough to upgrade to. You can then upgrade directly from LTSR to the latest Current Release (e.g. ). There&#;s no need to upgrade to intermediary versions.
- See XenApp & XenDesktop LTSR Feature Summary Comparison with LTSR for the list of features added to the Current Releases but not available in LTSR until LTSR was released. This should give you a sense of what you&#;re missing out by staying with LTSR.
XenApp features added to Current Release but not LTSR &#; For migrations from , you definitely want LTSR or LTSR instead of LTSR Much prior XenApp functionality was added to Current Releases released after LTSR &#; e.g. zones/local host cache, app limits, multiple license types, tags, idle time in Director, TLS , etc. These features are not in LTSR
Don&#;t mix Current Release and LTSR components &#; As soon as you upgrade one LTSR component to Current Release, upgrade all other LTSR components to Current Release, and keep them updated with new Current Releases every 6 months.
- When the next LTSR is released, you can stop upgrading (except for Cumulative Updates).
- Or, deploy Current Release in a separate environment.
- Use Citrix LTSR Assistant tool to confirm LTSR compliance.
- Some app vendors require you to remain on LTSR.
LTSR &#;compatible&#; components require frequent upgrades &#; Some components, like App Layering, are LTSR &#;compatible&#;, meaning there&#;s no LTSR version, but it&#;s OK to use them in an LTSR environment. Since they&#;re Current Release and not LTSR, you&#;re expected to update the Current Release components to the latest release every 6 months.
- There&#;s no LTSR version of Citrix Licensing. Instead, always upgrade Citrix Licensing to the latest Current Release version.
- There&#;s no LTSR version of App Layering. Instead, always upgrade App Layering to the latest Current Release version.
Windows 10 and LTSR : LTSR VDA is not supported on Windows Here are some options:
- Upgrade the entire deployment from LTSR to LTSR or LTSR , which fully support Windows
- For Windows 10 support on LTSR , on the Windows 10 machine, install the the newest LTSR VDA or LTSR VDA. VDA versions LTSR and (LTSR CU6) fully support Windows 10, including version See CTX Windows 10 Compatibility with Citrix Virtual Desktops (XenDesktop).
- For all other VDA machines running other OS versions, install LTSR VDA
Windows 7 and Windows Server R2 support: VDA and newer, including LTSR VDA, are not supported on Windows 7 or Windows Server R2. For these operating system versions, install LTSR VDA. The LTSR VDA can register with newer Delivery Controllers. However, the LTSR VDAs cannot take advantage of the newer features in the newer releases.
Citrix Virtual Apps and Desktops (CVAD) Supported versions
The most recent release of Citrix Virtual Apps and Desktops (CVAD) is version
There are three LTSR versions of XenApp and XenDesktop: LTSR , LTSR , and LTSR
- Cumulative Update 1 has been released for LTSR , resulting in version number
- Cumulative Update 6 has been released for LTSR , resulting in version number
- Several XA/XD LTSR Cumulative Updates have been released, resulting in version number
Examples of non-supported versions:
- XenDesktop is not LTSR, and is more than 18 months since release date, so it&#;s not supported. LTSR didn&#;t start until
- Citrix Virtual Apps and Desktops (CVAD) is not LTSR, and is more than six months past release date, so Citrix will not provide any code fixes. Once 18 months have elapsed, Citrix will not support it at all.
Workspace app (and Receiver) Supported versions
Starting in August , Current Releases of Receiver have been renamed to Workspace app. Also, versioning has changed from 4.x to a YYMM format.
The most recent release of Workspace app is version Workspace app , which is a Current Release.
The LTSR version of Workspace app is version Cumulative Update 2 (aka ).
- Browser Content Redirection does not work in LTSR Workspace app because Embedded browser is removed due to infrequent updates of LTSR versus frequent updates of the embedded browser.
The LTSR version of Receiver is version
- Several Cumulative Updates have been released for Receiver , resulting in version number
Citrix Virtual Apps and Desktops (CVAD) Component Version Dependencies
Citrix Virtual Apps and Desktops (CVAD) is a collection of installable components:
- Citrix Licensing Server
- Delivery Controller
- Citrix Studio
- Virtual Delivery Agent
- AppDisks / Personal vDisk
- Director
- StoreFront
- Federated Authentication Service
- App Layering
- Citrix Provisioning
- Citrix Group Policy Management Plug-in
- Profile Management
- Workspace Environment Management
- Session Recording
- AppDNA
- Citrix SCOM Packs
- Receiver or Workspace app for Windows, Linux, Mac, iOS, and Android
- Receiver or Workspace app for HTML5
- Skype for Business HDX RealTime Optimization Pack
- Citrix ADC (aka NetScaler) Load Balancing
- Citrix Gateway
Component behaviors:
- Each component can be installed separately.
- Some components can be combined onto the same machine.
- Some components are completely standalone with no dependency on other components.
- Some components communicate with other components, and thus are dependent on those other components.
The fewest components that make up a Citrix Virtual Apps and Desktops (CVAD) site/farm are License Server + Delivery Controller + Studio + VDA + SQL Databases.
- A farm/site is a collection of Delivery Controllers that share the same SQL databases.
- The official term is Citrix Virtual Apps and Desktops (CVAD) Site. However, since the word &#;site&#; has multiple meanings, this article instead refers to a Citrix Virtual Apps and Desktops (CVAD) Site as a Farm, which is the same terminology used in XenApp and older.
Some of the components can be used with multiple sites/farms.
- Citrix Licensing Server can be used by multiple sites/farms.
- StoreFront can pull icons from multiple sites/farms, including XenApp This enables multi-farm capabilities for the following components that are dependent on StoreFront:
- Federated Authentication Service can be used by multiple StoreFront servers.
- Receiver / Workspace app for Windows, Linux, Mac, iOS, and Android can connect to multiple StoreFront stores, which can be on different StoreFront servers.
- Each StoreFront server has its own Receiver or Workspace app for HTML5
- Citrix Gateway connects to one StoreFront server
- Citrix Studio can connect to multiple sites/farms.
- Virtual Delivery Agent can register with only one site/farm at a time, but the farm registration can be easily changed by modifying the ListOfDDCs registry key.
- Director can display monitoring data from multiple sites/farms.
- App Layering has no relationship to Citrix Virtual Apps and Desktops (CVAD) sites/farms, and thus can be used with any number of them.
- Citrix Provisioning has no relationship to Citrix Virtual Apps and Desktops (CVAD) sites/farms, and thus can be used with any number of them.
- Citrix Group Policy Management Plug-in can be used to create Citrix Policies that can apply to multiple sites/farms.
- Profile Management has no relationship to Citrix Virtual Apps and Desktops (CVAD) sites/farms, and thus can be used with any number of them. The profiles are usually tied to a VDA operating system version.
- Workspace Environment Management has no relationship to Citrix Virtual Apps and Desktops (CVAD) sites/farms, and thus can be used with any number of them.
- Session Recording has no relationship to Citrix Virtual Apps and Desktops (CVAD) sites/farms, and thus can be used with any number of them.
- AppDNA has no relationship to Citrix Virtual Apps and Desktops (CVAD) sites/farms, and thus can be used with any number of them.
- For Citrix SCOM Packs, the agents can be deployed to Delivery Controllers in multiple sites/farms.
- Skype for Business HDX RealTime Optimization Pack has no relationship to Citrix Virtual Apps and Desktops (CVAD) sites/farms, and thus can be used with any number of them. This component only cares about the RealTime Connector that is installed on the VDA.
The Citrix components that don&#;t have any relationship to Citrix Virtual Apps and Desktops (CVAD) sites/farms can be used with XenApp too.
Some components communicate with other components, and thus are dependent on the versions of those other components.
- Citrix Licensing Server should always be the newest version. Citrix Virtual Apps and Desktops (CVAD) Components will verify the Licensing Server version.
- StoreFront can usually work with any Delivery Controller version, including XenApp
- Citrix Studio should be the same version as the Delivery Controllers it is managing.
- Virtual Delivery Agents can be any version, including older or newer than the Delivery Controllers.
- Director uses the Citrix Monitoring Service that is installed on the Delivery Controllers.
- Workspace Environment Management (WEM) &#; newer WEM can configure newer Profile Management features. Otherwise, WEM is independent from Citrix Virtual Apps and Desktops (CVAD).
- Citrix SCOM Packs should be the same version or newer than the Components that they are monitoring. Check each SCOM Pack release notes for supported component versions.
- Workspace app &#; Many newer Citrix Virtual Apps and Desktops (CVAD) features require a specific version of Workspace app.
- If you are deploying Current Releases, then deploy the newest Current Release Workspace app.
- If you are deploying LTSR, then deploy the latest LTSR Workspace app or LTSR Receiver.
- If you need Browser Content Redirection, then deploy the latest Current Release Workspace app since LTSR Workspace app does not support Browser Content Redirection.
- Citrix Gateway &#; Some Newer Citrix features require newer Citrix ADC firmware. For example:
- EDT (Enlightened Data Transport) / Adaptive Transport
- Gateway Configuration export/import with StoreFront
- Citrix ADC builds have bug fixes that affect the Citrix Virtual Apps and Desktops (CVAD) experience.
7.x Upgrade Overview
7.x Components
Citrix Virtual Apps and Desktops (CVAD) 7 is composed of multiple Components, each of which is upgraded separately.
Newer versions of Citrix components enable Customer Experience Improvement Program (CEIP) automatically. If you wish to disable CEIP, see cromwellpsi.com#ceip.
Component Upgrade Process
In-place upgrades &#; 7.x components can be upgraded in-place. No need to rebuild like you did in XenApp and older.
Here&#;s the general, in-place upgrade process for each component. Detailed instructions for each component are detailed later.
- In-place upgrade one (or half) of the component&#;s servers.
- Upgrade the component&#;s database. Requires temporary sysadmin permission on SQL Server. Not all components have databases.
- In-place upgrade the remaining component&#;s servers.
- In-place upgrade the agents.
- Rebuilding of master images might be preferred, assuming you have time to automate it.
Mix and match VDA/Controller versions &#; You can upgrade VDAs without upgrading Delivery Controllers. Or vice versa.
- Newer VDA features sometimes require Citrix Policy to enable or configure. The newest Citrix Policy settings are included in Delivery Controller / Citrix Studio upgrades. Or, if you haven&#;t upgraded your Delivery Controllers yet, you can simply upgrade the Citrix Group Policy Management component.
VDA Operating System version Upgrade &#; Considerations when upgrading the VDA operating system version:
- VDA Version &#; VDA and newer no longer support Windows Server R2, Windows 7, or Windows 8/ If you need these older operating system versions, then install VDA instead. VDA can register with Delivery Controllers.
- App compatibility &#; Verify app compatibility with the new OS version. For compatibility with a Server OS version, check compatibility with the equivalent Desktop OS version.
- Windows Server R2 = bit Windows
- Windows Server = bit Windows 10
- Windows Server = bit Windows 10
- Start Menu in published desktop &#; If you publish desktops, is the Windows R2 Start Menu acceptable to the users? Windows R2 Start Menu is the same as Windows Start Menu.
- Windows Server Start Menu is the same as Windows 10 Start Menu.
- Windows Server Start Menu is the same as Windows 10 Start Menu.
- GPO settings&#; Newer OSs have newer Microsoft GPO settings.
- Profile version &#; Newer OS means newer profile version. Older profile versions do not work on newer operating system versions. For example, you can&#;t use Windows 7 profiles on Windows This means that an OS upgrade results in new profiles for every user.
- Write a script to copy profile settings from the old profiles to the new profiles.
- Remote Desktop Services (RDS) Licensing &#; if you are building RDSH (Server OS) VDAs, then every user that connects must have an RDS License for the RDSH operating system version. If RDSH is Windows , then every user needs a Windows RDS License. Windows R2 RDS Licenses won&#;t work.
- RDS Licensing Server &#; RDS Licensing Server is a built-in Windows Server Role. It must be installed on servers with the same or newer operating system version than the RDSH VDAs.
- Windows 10 Branches &#; Windows 10 Semi-Annual Channel Targeted (aka Current Branch) is only partially supported. Semi-Annual Channel Broad (aka Current Branch for Business), and LTSB are fully supported. See CTX
- Upgrade Windows 10 Version &#; In-place upgrade of Windows 10 versions is not recommended. For example, upgrading from Windows 10 to Windows 10 broke several features. Rebuild is cleaner.
- App Layering &#; However, due to dependencies between App Layers and OS Layer, you might have to in-place upgrade your OS Layer.
- Citrix Virtual Apps and Desktops (CVAD)Component Agents &#; ensure the Citrix component agents (WEM Agent, Profile Management, Session Recording Agent, App Layering Tools, etc.) are supported on the new OS version.
Considerations for upgrading the operating system version on component servers:
- Do not in-place upgrade the operating system version. Instead, build new VMs, and join them to the existing infrastructure.
- New OS version requires newer component versions. The required component version might be newer than what you&#;re currently running.
- When adding a server to the existing component farm/site, the new server must be running the same component version as the existing servers. That means you might have to in-place upgrade your existing component servers before you can add new component servers running a newer operating system version.
- For example:
- Existing Delivery Controllers are version on Windows R2.
- You desire to migrate to new Windows Delivery Controllers.
- Only Delivery Controller and newer can be installed on Windows But you can&#;t add Delivery Controller to a Delivery Controller farm/site.
- Upgrade the existing Delivery Controllers to or newer first.
- Then you can add the new Windows Delivery Controllers VMs to the existing farm/site.
Here are general instructions to upgrade component server OS version. Detailed instructions for each component are detailed later.
- In-place upgrade the existing component servers to a version that supports the new OS. Check the System Requirements documentation for each component to verify OS version compatibility.
- Build new machine(s) with desired OS version.
- On the new machines, install the same component version as the existing component servers.
- The new machines must be the same component version as the existing machines. You can&#;t add machines with newer component versions.
- Add the new component servers to the existing farm/site/server group.
- Migrate load balancer, VDAs, Targets, etc. from old to new. See below for detailed instructions for each component.
- Decommission old servers.
Upgrade Guidelines
Test farms &#; Test Citrix infrastructure upgrades in separate test environments (separate test farms):
- Due to forwards and backwards compatibility, VDA upgrades can usually be tested in production.
- Everything else requires global server-side upgrades first, so you can&#;t test them in production.
- Upgrade procedures for High Availability components (e.g. multiple Delivery Controllers) are different than upgrade procedures for singe, standalone components. The Test environment should look like production, which means HA too.
- The separate Test environments should include multi-datacenter capabilities (StoreFront icon aggregation, GSLB, etc.) so those multi-datacenter features can be tested.
Known upgrade issues &#; Read Citrix Discussions, or ask your Citrix Support TRM, for known upgrade issues. Don&#;t upgrade production immediately after a new version is released.
- Read the release notes, especially the known issues.
Smart Check the environment before upgrading. It&#;s free. Access it at cromwellpsi.com
Backup/snapshot &#; Backup databases, snapshot machines, etc. before starting the in-place upgrade.
- Have a rollback plan, including the databases.
Citrix Licensing Server &#; Always upgrade the Citrix Licensing Server before upgrading anything else.
- Check Subscription Advantage (SA) date on the installed licenses. Some components require SA expiration date to be later than the component&#;s release date.
In-place upgrade preparation:
- Make sure other admins are logged off before starting the upgrades.
- Close all consoles and PowerShell.
- Snapshot the machines.
Upgrade Citrix Virtual Apps and Desktops (CVAD) 7.x
All 7.x components can be upgraded in-place.
- Current Release upgrades are cumulative. You can skip intermediary versions.
- LTSR Cumulative Updates are also cumulative, hence the name.
- LTSR Cumulative Updates are performed using the same process as Current Release upgrades. The only difference is that you don&#;t get new features with LTSR updates.
Some components (Delivery Controllers, Citrix Provisioning, Session Recording, WEM, etc.) require the person doing the upgrade to have temporary sysadmin permissions on the SQL server so the database can be upgraded.
Upgrade order &#; For the most part, upgrade order doesn&#;t matter. That&#;s because there are few dependencies between each component, as detailed earlier.
- Before upgrading anything else, upgrade the Citrix Licensing Server.
- Install updated license files with non-expired Subscription Advantage dates.
- VDAs and Delivery Controllers can be different versions.
- VDAs can be upgraded before Controllers, or vice/versa.
- If Zones, upgrade all Delivery Controllers in all zones at the same time.
- For Director, upgrading Director won&#;t do you much good if the Controllers aren&#;t upgraded, since Director uses the Monitoring service that&#;s installed on the Controllers.
- Director and newer will warn you if your Delivery Controllers are not the same version as Director.
- For Citrix Provisioning, the Citrix Provisioning servers must be upgraded before you upgrade the Target Device Software.
- For Session Recording, the Session Recording server(s) must be upgraded before you upgrade the Session Recording agent.
- For WEM, the WEM server(s) must be upgraded before you upgrade the WEM agent.
If you upgrade to a version that has CEIP functionality, decide if you want to disable CEIP, or leave it enabled.
After upgrading, configure new functionality.
Additional general upgrade guidance can be found at Upgrade a deployment at Citrix Docs.
Citrix Licensing Server
It&#;s a simple in-place upgrade.
- After upgrading, download the latest license files from cromwellpsi.com, and install the license files on the license server. Make sure the Subscription Advantage date hasn&#;t expired.
To upgrade the Licensing Server Operating System version:
- Build a new VM with desired OS version.
- Install the latest Current Release License Server.
- At cromwellpsi.com, reallocate licenses to the new case-sensitive hostname, and install the license file on the new Licensing Server.
- For 7.x sites/farms, in Citrix Studio, go to Configuration > Licensing, and change the License Server to the new Licensing Server.
- For XenApp , in AppCenter > Policies, or a GPO with Citrix Policies, find the Citrix Policy that defines the Licensing Server name, and change it.
- Or, run the XenApp Server Role Manager on each server and change Licensing configuration.
Delivery Controllers
Both of the following types of upgrades/updates use the same upgrade process:
- Install latest LTSR Cumulative Update
- Upgrade to latest Current Release
To in-place upgrade Delivery Controllers:
- If High Availability is configured correctly, then Delivery Controllers can be upgraded during the day.
- Upgrade the Citrix Licensing Server if you haven&#;t already. Install current licenses if you haven&#;t already.
- Ask a DBA for temporary sysadmin permission to the SQL server.
- Prepare: run Smart Check, logoff other admins, close consoles.
- In-place upgrade one (or half) of the Delivery Controllers. Upgrade to one of the following:
- Delivery Controller
- Delivery Controller LTSR CU1
- Delivery Controller LTSR Cumulative Update 6
- Delivery Controller LTSR Cumulative Update 8
- Launch Studio. Upgrade the database when prompted.
- In-place upgrade the remaining Delivery Controllers.
- Run Smart Check again.
- Temporary sysadmin permissions can now be removed.
- For Citrix Studio that&#;s installed on administrator machines other than Delivery Controllers, in-place upgrade Studio by running cromwellpsi.com from the Current Release or LTSR XenApp/XenDesktop ISO.
To upgrade the operating system version of the Delivery Controllers:
- In-place upgrade the existing Delivery Controllers to a version that supports the new operating system version.
- For Windows Server , upgrade to version or newer.
- For Windows Server , upgrade to version or newer
- does not support Windows R2 Controllers so you might have to upgrade to Windows Server first.
- Build one or more new virtual machines with the new operating system version.
- Install Delivery Controller software with the same version as the other Delivery Controllers.
- Run Citrix Studio and join the new machines to the existing farm/site.
- Push SCOM Agent with XAXD Agent to the new Delivery Controllers.
- Reconfigure VDAs to point to the new Delivery Controllers. Edit the ListOfDDCs registry key.
- Reconfigure Director server > IIS Admin > Default Web Site > Director > Application Settings > cromwellpsi.comscoveryAddresses to point to the new Delivery Controllers.
- Reconfigure StoreFront console > MyStore > Manage Delivery Controllers to point to the new Delivery Controllers.
- Secure Ticket Authorities:
- Add the new Delivery Controllers to firewall rules between Citrix ADC SNIP and STAs.
- In Citrix Gateway > Edit Virtual Server > scroll down to the Published Applications section > click the line to edit the Secure Ticket Authorities. Add the new Delivery Controllers as Secure Ticket Authorities. Don&#;t remove the old ones yet.
- In StoreFront Console, go to Manage Citrix Gateways > edit each Gateway > on the Secure Ticket Authority page, add the new Delivery Controllers as Secure Ticket Authorities, and remove the old ones.
- In Citrix Gateway > Edit Virtual Server > scroll down to the Published Applications section > click the line to edit the Secure Ticket Authorities. Remove the older Controllers as Secure Ticket Authorities.
- In Citrix Studio, at Configuration > Controllers, remove the old Delivery Controllers.
- Note: if this doesn&#;t work, then you might have to manually evict the old Delivery Controllers from the SQL database.
- Decommission the old Delivery Controllers.
App Layering
To in-place upgrade Citrix App Layering:
- In-place upgrade the ELM appliance.
- From and newer, newer versions should be downloaded automatically. Just click the link to start the upgrade.
- From and older, download the upgrade package and upload it to the ELM.
- Upgrade the App Layering Citrix Provisioning Agent by uninstalling the Citrix Provisioning Agent and re-installing it.
- Create a new OS Layer version and install the latest OS Machine Tools.
- When the images are published, the drivers will be updated automatically by the ELM.
Workspace Environment Management (WEM)
To in-place upgrade Citrix Workspace Environment Management (WEM):
- In-place upgrade the Citrix Licensing Server if you haven&#;t already.
- Ensure the installed licenses have a non-expired Subscription Advantage date.
- Ask a DBA for temporary sysadmin permission to the SQL server.
- In-place upgrade the first WEM Server. Consider removing it from load balancing before performing the upgrade.
- Use the Database Maintenance tool to upgrade the WEM database.
- Run the WEM Broker Configuration Tool on the upgraded Broker to point to the upgraded database.
- In-place upgrade the remaining WEM Servers. Consider removing them from load balancing before performing the upgrade.
- Temporary sysadmin permissions can now be removed.
- In-place upgrade the WEM Console on all non-server machines where it is installed.
- In-place upgrade the WEM Agents.
- If you are upgrading from WEM and older, in the WEM Console, add the WEM Agents (computer accounts) to Configuration Sets instead of the old WEM Sites.
To upgrade the operating system version of the Workspace Environment Management servers, it&#;s easier if you have a custom DNS name, or load balanced DNS name for WEM, instead of using a server name :
- In-place upgrade the existing WEM servers to a version that supports the OS you intend for the new WEM servers.
- Build new WEM servers with the same version as the existing WEM servers.
- Configure the new WEM servers to point to the same database as the old WEM servers.
- Cutover options:
- If you have a load balanced DNS name for WEM, reconfigure the load balancer to point to the new WEM servers.
- If you have a custom DNS name for WEM, change it to resolve to the new WEM server&#;s IP address.
- If you were previously using the actual server name, then you can either change the WEM Agent group policy to point to the new WEM server name, or delete the old WEM server and rename the new WEM server, or delete the old WEM server and reconfigure the old DNS name as a custom DNS name for the new WEM server.
- Decommission the old WEM servers.
Session Recording
To in-place upgrade Session Recording:
- In-place upgrade the Citrix Licensing Server if you haven&#;t already.
- Ensure the installed licenses have a non-expired Subscription Advantage date.
- Ask a DBA for temporary sysadmin permission to the SQL server.
- In-place upgrade the first Session Recording server to one of the following.
- Session Recording and newer are on the main Citrix Virtual Apps and Desktops (CVAD) ISO.
- Only Session Recording and newer fully support load balancing. Consider removing the Session Recording server from load balancing before performing the upgrade.
- Session Recording
- Session Recording LTSR CU1
- Session Recording LTSR Cumulative Update 6
- There is an LTSR version of Session Recording. The install/upgrade process for LTSR is quite different than and newer. The version supports XenApp (RDSH), but not virtual desktops.
- The upgrade of the first Session Recording server should automatically upgrade the database.
- In-place upgrade the remaining Session Recording Servers. Consider removing them from load balancing before performing the upgrade.
- Temporary sysadmin permissions can now be removed.
- In-place upgrade the Session Recording Agents.
- In-place upgrade the Session Recording Player on all machines where it is installed.
To upgrade the operating system version of the Session Recording servers, it&#;s easier if you have a custom DNS name or load balanced DNS name for Session Recording, instead of using a server name:
- In-place upgrade the existing Session Recording servers to a version that supports the OS you intend for the new Session Recording servers. Windows support was added to Session Recording and newer.
- Build new Session Recording servers with the same version as the existing Session Recording servers.
- Configure the new Session Recording servers to point to the same database as the old Session Recording servers.
- Configure the new Session Recording servers to store recordings on the same UNC path as the old Session Recording servers.
- The certificate on the Session Recording servers or load balancer must match the DNS name used by the Session Recording Agents and Player.
- Cutover:
- If you have a load balanced DNS name for Session Recording, reconfigure the load balancer to point to the new Session Recording servers.
- If you have a custom DNS name for Session Recording, change it to resolve to the new Session Recording server&#;s IP address.
- If you were previously using the actual server name, then you can either: change the Session Recording Agents and Players to point to the new Session Recording server name, or delete the old Session Recording server and rename the new Session Recording server, or delete the old Session Recording server and reconfigure the old DNS name as a custom DNS name for the new Session Recording server.
- If the Session Recording DNS name changed, reconfigure Director to point to the new Session Recording DNS name.
- Decommission the old Session Recording servers.
Citrix Provisioning
Citrix Provisioning servers must be upgraded before you can upgrade Target Devices.
To in-place upgrade Citrix Provisioning servers:
- Make sure Citrix Provisioning High Availability (HA) is working for target devices. If HA is functional, in-place upgrade can be done during the day.
- In the Citrix Provisioning console, you should see an even distribution of Target Devices across all Citrix Provisioning servers.
- Check the WriteCache folders on Citrix Provisioning servers to make sure they&#;re empty. If any Target Device is caching on Server, then those Target Devices will not failover to another Citrix Provisioning server.
- Get temporary sysadmin permissions to the SQL Server that hosts the Citrix Provisioning database.
- Get the one of the following installation media:
- Citrix Provisioning
- Citrix Provisioning LTSR CU1
- Citrix Provisioning LTSR from LTSR Cumulative Update 6
- Citrix Provisioning LTSR from LTSR Cumulative Update 8
- On the first Citrix Provisioning Server:
- In-place upgrade Citrix Provisioning Console by running the LTSR CU1, LTSR , or LTSR Citrix Provisioning Console installer.
- Re-register the cromwellpsi.com snap-in: "C:\Windows\cromwellpsi.com\Framework64\v\cromwellpsi.com" "c:\program files\citrix\provisioning services console\cromwellpsi.com"
- In-place upgrade Citrix Provisioning Server by running the LTSR CU1, LTSR , or LTSR Citrix Provisioning Server installer
- Run the Citrix Provisioning Configuration Wizard. The farm should already be configured, so just click Next a few times and let it upgrade the database and restart the services.
- In-place upgrade the Console and Server software on the remaining Citrix Provisioning Servers. After installation, run the Citrix Provisioning Configuration Wizard, and click Next until the end.
- Temporary sysadmin permissions can now be removed.
- Target Device Software can now be upgraded.
There are several methods of upgrading the Citrix Provisioning Target Device Software that&#;s inside a vDisk:
- If Target Device Software is version or newer, in-place upgrade the Target Device Software while doing your normal vDisk update process.
- Completely rebuild the vDisk. An automated build process like MDT is recommended.
- If Target Device Software is or older, then you must reverse image.
- To upgrade VMware Tools (or any software that modifies the NIC), you must reverse image.
To in-place upgrade Target Device software and newer:
- Create a new vDisk Maintenance version, or put the vDisk in Private Image mode. Then boot an Updater Target Device. This is the normal process for updating a vDisk.
- Run the LTSR CU1, LTSR or LTSR Target Device software installer to upgrade the software. The Target Device software must be the same version or older than the Citrix Provisioning Servers.
- Shut down the Updater. Promote the Maintenance version to Production, or change the vDisk to Standard Image mode. This is the normal process for updating a vDisk.
Reverse image methods:
- Boot from VHD &#; Build a VM. Copy Citrix Provisioning vDisk VHD/VHDX to VM. Boot from VHD/VHDX.
- Hyper-V can boot from a VHD directly. Copy Citrix Provisioning vDisk VHD/VHDX to Hyper-V host. Create a VM that boots from VHD/VHDX.
- Once VHD/VHDX is updated, copy the VHD/VHDX back to Citrix Provisioning, import to a Citrix Provisioning Store, which creates a new vDisk, and assign the new vDisk to target devices. Takes effect at next Target Device reboot.
If using Citrix Provisioning Accelerator, keep XenServer patched.
To upgrade the operating system version of the Citrix Provisioning Servers:
- In-place upgrade the existing Citrix Provisioning Servers to a version that supports the new operating system version. For Windows , upgrade to version or newer.
- Build one or more new virtual machines with the new operating system version.
- Install Citrix Provisioning Server software with the same version as the other Citrix Provisioning Servers.
- Run Citrix Provisioning Configuration Wizard and join the new machines to the existing Citrix Provisioning farm and Citrix Provisioning database.
- Copy the vDisk files from an existing Citrix Provisioning Server to the new Citrix Provisioning Servers. Check Replication Status of each vDisk.
- Install the App Layering Citrix Provisioning Agent.
- Push SCOM Agent with Citrix SCOM Provisioning Agent to the new Citrix Provisioning Servers.
- In Citrix Provisioning Console, reconfigure Bootstrap to point to the new Citrix Provisioning Servers. Go to Sites > MySite > Servers > right-click each server, and click Configure Bootstrap.
- Reconfigure DHCP Options or BDM to point to the new Citrix Provisioning Servers. Do one or more of the following:
- Reconfigure TFTP load balancing to point to the new Citrix Provisioning Servers.
- Change DHCP Scope Options 66/67 to the new Citrix Provisioning Servers.
- Create a new Boot ISO with the new Citrix Provisioning Servers.
- Use the Citrix Provisioning Console to update the BDM Partition on each Target Device.
- Start the PXE Service on the new Citrix Provisioning Servers and stop the PXE Service on the old Citrix Provisioning Servers.
- Reboot some Target Devices to make sure they work.
- In Citrix Provisioning Console, delete the old Citrix Provisioning Servers.
- Decommission the old Citrix Provisioning Servers.
Virtual Delivery Agents (VDA)
To in-place upgrade the Virtual Delivery Agent software:
Instead of in-place upgrading the VDAs, you can also rebuild them with the new software versions. If rebuilding, use an automated method, like MDT.
To upgrade the operating system version of the Virtual Delivery Agents, it&#;s recommended to rebuild the VDA. But keep in mind the following:
- Windows 10 Semi-Annual Channel Targeted (aka Current Branch) is only partially supported.
- Windows 10 version upgrades should be a rebuild, not an in-place upgrade.
- If you in-place upgrade, uninstall VDA software, upgrade Windows, then reinstall VDA software.
- Citrix App Layering might require in-place upgrade of Windows 10 due to other layers being linked to the OS Layer.
- Newer VDA operating system versions use newer profile versions, which means older profiles will not work.
- Newer RDSH operating system versions require newer RDS Licensing Servers and newer RDS Licenses.
- GPO settings&#; Newer OSs have newer Microsoft GPO settings.
StoreFront
StoreFront is the most problematic component to upgrade so be prepared to roll back.
- Newer versions of StoreFront installer are adding pre-upgrade checks to prevent known upgrade issues &#; e.g. stop SCOM Service
Citrix does not support mixing StoreFront versions within a single Server Group and they instead prefer that you do this: (source = Upgrade StoreFront at Citrix Docs)
- It&#;s critical that you snapshot the StoreFront machines before beginning the upgrade.
- Remove a StoreFront sever from the Server Group and load balancing.
- Prep: close consoles, close PowerShell, logoff other admins, stop SCOM Agent.
- Upgrade the removed server by installing one of the following:
- CVAD comes with StoreFront Cumulative Update 1. There is no StoreFront
- StoreFront LTSR CU1
- StoreFront LTSR from Cumulative Update 6
- StoreFront LTSR
- If upgrade fails, review the install logs to determine the cause. Once the cause is determined, revert the VM to prior snapshot, and try the upgrade again.
- Upgrade the HTML5 Workspace app (formerly known as Receiver for HTML5) installed on StoreFront. The instructions for StoreFront LTSR CU1, StoreFront LTSR () and StoreFront LTSR () are the same.
- Swap out the upgraded server on the load balancer so all traffic goes to the new server.
- Uninstall/reinstall StoreFront on the remaining StoreFront servers and join the first server that was already upgraded.
To upgrade the operating system version of the StoreFront Servers:
- Build one or more new virtual machines with the new operating system version.
- Install StoreFront software.
- Do one of the following: (Note: Citrix does not support mixing operating system versions in the same StoreFront server group)
- Export the StoreFront configuration from the old servers and import to the new servers. This only works if the older servers are StoreFront and newer.
- Manually configure the new StoreFront Server Group to match the old StoreFront Server Group. This configuration includes: Base URL, entries under Manage Delivery Controllers (case sensitive), SRID (c:\inetpub\wwwroot\Citrix\Roaming\cromwellpsi.com), export/import subscriptions, Beacons, Gateways, Icon Aggregation, etc.
- This option is probably unsupported: In-place upgrade the existing StoreFront Servers to the same version as the new servers. Run StoreFront Console on the new servers, and join the new machines to the existing Server Group. This causes configuration and subscriptions to replicate to the new server.
- Push SCOM Agent with StoreFront Agent to the new StoreFront servers.
- Upgrade the HTML5 Workspace app (formerly known as Receiver for HTML5) installed on StoreFront. The instructions for StoreFront LTSR CU1, StoreFront LTSR (), and StoreFront LTSR () are the same.
- Reconfigure the load balancer to point to the new StoreFront servers instead of the old StoreFront servers.
- In StoreFront console, remove the old StoreFront servers.
- Decommission the old StoreFront servers.
Workspace app for HTML5
Workspace app for HTML5 is usually released on a different schedule than StoreFront and is upgraded out-of-band.
- Workspace app for HTML5 is formerly known as Receiver for HTML5. There is no LTSR version of Receiver for HTML5 so you should upgrade to the latest Workspace app for HTML5, especially for the newer features (e.g. multi-monitor, USB redirection).
To in-place upgrade Workspace app for HTML5 or Receiver for HTML5:
- Upgrade the HTML5 Workspace app installed on StoreFront. The instructions for StoreFront LTSR CU1, LTSR () and LTSR () are the same.
- For VDA machines that are version or older, upgrade the HTML5 Citrix PDF Printer software that&#;s installed on the .
- VDA and newer install the PDF Printer automatically so you don&#;t have to install the Citrix PDF printer yourself.
- Upgrade the
- License Information User Manual Oracle® Developer Studio
- Document Information
- Chapter 1 Introduction
- About this Document
- Chapter 2 Licensing Information
- Third Party Notices and Licenses
- Open Source Software
- Common Licenses
- Apache License v
- Eclipse Public License - v
- GNU General Public License, version 2 (June )
- GNU LESSER GENERAL PUBLIC LICENSE Version , February
- GNU GENERAL PUBLIC LICENSE Version 3, 29 June
- H2 License Version
- GCC RUNTIME LIBRARY EXCEPTION Version
- Open Source Software, NetBeans IDE
-
You can use H2 for free. You can integrate it into your applications (including in commercial applications) and distribute it.
-
Files containing only your code are not covered by this license (it is 'commercial friendly').
-
Modifications to the H2 source code must be published.
-
You don't need to provide the source code of H2 if you did not modify anything.
-
If you distribute a binary that includes H2, you need to add a disclaimer of liability - see the example below.
-
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
-
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
-
The names of the authors may not be used to endorse or promote products derived from this software without specific prior written permission.
-
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
-
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
-
Neither the name of Lawrence Berkeley National Laboratory, U.S. Dept. of Energy nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
-
The origin of this software must not be misrepresented; you must not claim that you wrote the original software. If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required.
-
Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software.
-
This notice may not be removed or altered from any source distribution.
Jean-loup Gailly Mark Adler
-
Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files.
"Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.
-
Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.
-
Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.
-
Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:
1. You must give any other recipients of the Work or Derivative Works a copy of this License; and
2. You must cause any modified files to carry prominent notices stating that You changed the files; and
3. You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and
4. If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.
-
Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.
-
Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.
-
Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.
-
Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.
-
Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.
-
DEFINITIONS
"Contribution" means:
-
in the case of the initial Contributor, the initial code and documentation distributed under this Agreement, and
-
in the case of each subsequent Contributor:
i) changes to the Program, and
ii) additions to the Program; where such changes and/or additions to the Program originate from and are distributed by that particular Contributor. A Contribution 'originates' from a Contributor if it was added to the Program by such Contributor itself or anyone acting on such Contributor's behalf. Contributions do not include additions to the Program which: (i) are separate modules of software distributed in conjunction with the Program under their own license agreement, and (ii) are not derivative works of the Program.
"Contributor" means any person or entity that distributes the Program. "Licensed Patents" mean patent claims licensable by a Contributor which are necessarily infringed by the use or sale of its Contribution alone or when combined with the Program. "Program" means the Contributions distributed in accordance with this Agreement. "Recipient" means anyone who receives the Program under this Agreement, including all Contributors.
-
-
GRANT OF RIGHTS
-
Subject to the terms of this Agreement, each Contributor hereby grants Recipient a non-exclusive, worldwide, royalty-free copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, distribute and sublicense the Contribution of such Contributor, if any, and such derivative works, in source code and object code form.
-
Subject to the terms of this Agreement, each Contributor hereby grants Recipient a non-exclusive, worldwide, royalty-free patent license under Licensed Patents to make, use, sell, offer to sell, import and otherwise transfer the Contribution of such Contributor, if any, in source code and object code form. This patent license shall apply to the combination of the Contribution and the Program if, at the time the Contribution is added by the Contributor, such addition of the Contribution causes such combination to be covered by the Licensed Patents. The patent license shall not apply to any other combinations which include the Contribution. No hardware per se is licensed hereunder.
-
Recipient understands that although each Contributor grants the licenses to its Contributions set forth herein, no assurances are provided by any Contributor that the Program does not infringe the patent or other intellectual property rights of any other entity. Each Contributor disclaims any liability to Recipient for claims brought by any other entity based on infringement of intellectual property rights or otherwise. As a condition to exercising the rights and licenses granted hereunder, each Recipient hereby assumes sole responsibility to secure any other intellectual property rights needed, if any. For example, if a third party patent license is required to allow Recipient to distribute the Program, it is Recipient's responsibility to acquire that license before distributing the Program.
-
Each Contributor represents that to its knowledge it has sufficient copyright rights in its Contribution, if any, to grant the copyright license set forth in this Agreement.
When the Program is made available in source code form:
-
it must be made available under this Agreement; and
-
a copy of this Agreement must be included with each copy of the Program. Contributors may not remove or alter any copyright notices contained within the Program. Each Contributor must identify itself as the originator of its Contribution, if any, in a manner that reasonably allows subsequent Recipients to identify the originator of the Contribution.
-
-
COMMERCIAL DISTRIBUTION
Commercial distributors of software may accept certain responsibilities with respect to end users, business partners and the like. While this license is intended to facilitate the commercial use of the Program, the Contributor who includes the Program in a commercial product offering should do so in a manner which does not create potential liability for other Contributors. Therefore, if a Contributor includes the Program in a commercial product offering, such Contributor ("Commercial Contributor") hereby agrees to defend and indemnify every other Contributor ("Indemnified Contributor") against any losses, damages and costs (collectively "Losses") arising from claims, lawsuits and other legal actions brought by a third party against the Indemnified Contributor to the extent caused by the acts or omissions of such Commercial Contributor in connection with its distribution of the Program in a commercial product offering. The obligations in this section do not apply to any claims or Losses relating to any actual or alleged intellectual property infringement. In order to qualify, an Indemnified Contributor must: a) promptly notify the Commercial Contributor in writing of such claim, and b) allow the Commercial Contributor to control, and cooperate with the Commercial Contributor in, the defense and any related settlement negotiations. The Indemnified Contributor may participate in any such claim at its own expense.
For example, a Contributor might include the Program in a commercial product offering, Product X. That Contributor is then a Commercial Contributor. If that Commercial Contributor then makes performance claims, or offers warranties related to Product X, those performance claims and warranties are such Commercial Contributor's responsibility alone. Under this section, the Commercial Contributor would have to defend claims against the other Contributors related to those performance claims and warranties, and if a court requires any other Contributor to pay any damages as a result, the Commercial Contributor must pay those damages.
-
NO WARRANTY
EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, THE PROGRAM IS PROVIDED ON AN "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Each Recipient is solely responsible for determining the appropriateness of using and distributing the Program and assumes all risks associated with its exercise of rights under this Agreement , including but not limited to the risks and costs of program errors, compliance with applicable laws, damage to or loss of data, programs or equipment, and unavailability or interruption of operations.
-
DISCLAIMER OF LIABILITY
EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NEITHER RECIPIENT NOR ANY CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING WITHOUT LIMITATION LOST PROFITS), HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OR DISTRIBUTION OF THE PROGRAM OR THE EXERCISE OF ANY RIGHTS GRANTED HEREUNDER, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
-
GENERAL
If any provision of this Agreement is invalid or unenforceable under applicable law, it shall not affect the validity or enforceability of the remainder of the terms of this Agreement, and without further action by the parties hereto, such provision shall be reformed to the minimum extent necessary to make such provision valid and enforceable.
If Recipient institutes patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Program itself (excluding combinations of the Program with other software or hardware) infringes such Recipient's patent(s), then such Recipient's rights granted under Section 2(b) shall terminate as of the date such litigation is filed.
All Recipient's rights under this Agreement shall terminate if it fails to comply with any of the material terms or conditions of this Agreement and does not cure such failure in a reasonable period of time after becoming aware of such noncompliance. If all Recipient's rights under this Agreement terminate, Recipient agrees to cease use and distribution of the Program as soon as reasonably practicable. However, Recipient's obligations under this Agreement and any licenses granted by Recipient relating to the Program shall continue and survive.
Everyone is permitted to copy and distribute copies of this Agreement, but in order to avoid inconsistency the Agreement is copyrighted and may only be modified in the following manner. The Agreement Steward reserves the right to publish new versions (including revisions) of this Agreement from time to time. No one other than the Agreement Steward has the right to modify this Agreement. The Eclipse Foundation is the initial Agreement Steward. The Eclipse Foundation may assign the responsibility to serve as the Agreement Steward to a suitable separate entity. Each new version of the Agreement will be given a distinguishing version number. The Program (including Contributions) may always be distributed subject to the version of the Agreement under which it was received. In addition, after a new version of the Agreement is published, Contributor may elect to distribute the Program (including its Contributions) under the new version. Except as expressly stated in Sections 2(a) and 2(b) above, Recipient receives no rights or licenses to the intellectual property of any Contributor under this Agreement, whether expressly, by implication, estoppel or otherwise. All rights in the Program not expressly granted under this Agreement are reserved.
This Agreement is governed by the laws of the State of New York and the intellectual property laws of the United States of America. No party to this Agreement will bring a legal action under this Agreement more than one year after the cause of action arose. Each party waives its rights to a jury trial in any resulting litigation.
Third Party Notices and Licenses
Open Source Software
Required notices for open source software products or components distributed in Oracle Developer Studio are identified in the following table along with the applicable licensing information. Additional notices and/or licenses may be found in the included documentation or readme files of the individual third party open source software.
|
Common Licenses
This section includes required notices and licenses that are referenced by one or more of the Oracle Developer Studio open source software products or components in the table above. The following common licenses are provided below:
Apache License v
Apache License
Version , January
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work
To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
cromwellpsi.com://cromwellpsi.com
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
You may obtain a copy of the License at cromwellpsi.comcromwellpsi.com
Eclipse Public License - v
THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS ECLIPSE PUBLIC LICENSE ("AGREEMENT"). ANY USE, REPRODUCTION OR DISTRIBUTION OF THE PROGRAM CONSTITUTES RECIPIENT'S ACCEPTANCE OF THIS AGREEMENT.
GNU General Public License, version 2 (June )
Version 2, June
Copyright (C) , Free Software Foundation, Inc.,
51 Franklin Street, Fifth Floor, Boston, MA USA
Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
Preamble
The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Lesser General Public License instead.) You can apply it to your programs, too.
When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things.
To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the cromwellpsi.com restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it.
For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.
We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software.
Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations.
Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all.
The precise terms and conditions for copying, distribution and modification follow.
GNU GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The "Program", below,refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law:that is to say, a work containing the Program or a portion of it,either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you".
Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does.
1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty;and give any other recipients of the Program a copy of this License along with the Program.
Tdtrtrtd2017tdtd2016tdtdAdded active ransomware countermeasures, blockchain-based notary services, and electronic signing (premium version only). tdtrtrtd2018tdtd2017tdtdAdded cloning of active disks and continuous backups. tdtrtbodytableh3File format[edit]h3pAcronis True Image guarantees backward compatibility for image files (with the. tib extension) created with a single previous version, that is, images created with an immediate previous version can be successfully restored (older versions may or may not work).
Backups are created to be compatible between different editions of Acronis True Image within the same version (Home, Enterprise), e.
.What’s New in the Zip Express v2.7.14.1 serial key or number?
Screen Shot
System Requirements for Zip Express v2.7.14.1 serial key or number
- First, download the Zip Express v2.7.14.1 serial key or number
-
You can download its setup from given links:
Zip Express v2.7.14.1 serial key or number & PC Free Download
Zip Express v2.7.14.1 serial key or number& Key Download
Zip Express v2.7.14.1 serial key or number
About Author
