# Legacy Client Upgrade (Windows) *Applies to version 9.2 or earlier* The Legacy Client Upgrade (Windows) feature is available to upgrade devices using Adaptiva client versions 9.2, 9.1, or earlier. If you have devices using the 9.3 or later version of the Adaptiva Client, use the new [Client Upgrade](/platform-guide/client-management/client-auto-upgrade.md) feature to automatically upgrade Adaptiva client versions. Since the Legacy Client Upgrade (Windows) feature only supports Windows devices, any Linux or macOS devices will need to be upgraded manually or an unattended installation using a software distribution tool. See the [Client Installation on Linux or MacOS](https://docs.adaptiva.com/platform-install/client-install-and-uninstall/client-install/client-install-linux-macos) section of the OneSite Platform Installation Guide. Once you have upgraded all devices to the 9.3 Adaptiva client, you can [disable the Legacy Client Upgrade (Windows) feature](#disable-legacy-client-upgrade-windows). This will allow you to use the automatic Client Upgrade feature moving forward. ## Enable legacy client upgrade 1. Connect to the Admin Portal using a web browser (except Internet Explorer) -- `http://AdaptivaServerFQDN[:port]`. 2. Enter the appropriate credentials or click on **Login with Active Directory**. 3. Click on the gear icon ![](/files/IZ1YqeJ3mXKyyrvGw3C6) **> Settings > Legacy Client Upgrade (Windows)**. 4. The dashboard will show the current coverage for different client versions and the upgrade status by location. ![](/files/YhIQunXWMxp9HHmD40Tf) ![](/files/04d4p1wPiVcOjB4wTr7r) 5. Toggle ON **Enable Client Auto Upgrade**. The settings below can now be configured. ![](/files/Ua199Q63QgxLHJtkqFuX) If it is already enabled, the last saved settings will be set in each section below. ### Scheduling The Schedule settings configure when clients begin upgrading to the client version of the server. ![](/files/edEJUX49oiAdfuDfvlmT) Click the calendar icon ![](/files/VaXcqUNEF6CGgQp8xr8E) to open a calendar widget and select a start date and time. ![](/files/QmUcL7xCPNsO5NNRcum3) Click anywhere off the widget to close it. The date and time has been entered into Schedule Start Time. You can toggle **Use Server Time Zone** to have this start time use the time zone of the Adaptiva Server. Once the upgrade policy is saved and deployed, clients that come online after this start time will apply the policy immediately. ### Target Groups You can target clients for upgrade by group or simply target all clients registered with the Adaptiva server. ![](/files/WvGmHRPfSNr2J9kih1GM) To target all Adaptiva clients for upgrade, toggle **Use All Adaptiva Clients**. To target a collection of clients for upgrade, click **Browse**. In the Select Group pane, check the box next one or more Adaptiva Groups or ConfigMgr collections, then click **OK**. ### Load Balancing By default, all targeted clients will begin to upgrade on the start date and time. If you want to balance the rollout of client upgrades over a period of time, configure the load balancing settings. ![](/files/C1vMpV2TU2oH417zAwwS) Toggle **Use Load Balancing**. You can set a load balance interval between 0 and 100 Days, Hours or Minutes. Once enabled, each client will be randomly divided across the load balance interval for their upgrade schedule. ### Installation You can configure all of the upgrade settings for your clients. Any setting configured on the page will update the command line reference below. ![](/files/0MClWNtUOcD8clP0GvZ0) * **Use Server FQDN** or **Use Server IP Address** You can choose either **Use Server FQDN** or **Use Server IP Address**. The Adaptiva Client can only be installed using either the `-servername` or `-serverip` switches. You can verify the Server Name or IP Address is correct by reviewing the command line below. * **Override Server FQDN** To override the Server FQDN or IP Address, toggle **Override Server FQDN** and enter the new Name or IP Address to use. When you override the Name or IP Address, it will cause the client to be inactivated and re-activated. This will trigger a review of all content in the AdaptivaCache folder as well as new policy downloads. If the FQDN or IP Address needs to be changed to support a DNS CNAME Alias see [How-To: Redirect OneSite client to a different Adaptiva server](https://support.adaptiva.com/hc/en-us/articles/206503713-How-To-Redirect-OneSite-client-to-a-different-Adaptiva-server) Choose any of the below options: * **Use Cloud Relay**: Allows the Adaptiva client to communicate with `http://services.adaptiva.cloud` when unable to communicate via UDP to the on-premises Adaptiva Server. {% hint style="info" %} If any of the in-scope clients have been previously configured to use the Cloud Relay Service, be sure to enable this setting otherwise client communications will stop using the Adaptiva Cloud Relay server. {% endhint %} * **Bind to HTTP URL**: Allows the Adaptiva client to communicate with the on-premises Adaptiva Server via the defined HTTP Port. This adds the `-serverurl ` to the command line. When the Bind to HTTP URL is enabled, enter the URL of the on-premises Adaptiva server. For example: `http://adaptivaserver.mydomain.com:9678` * **No Add/Remove Programs Entry**: Enabling this setting will prevent Adaptive Client from being added to the Add & Remove Programs/Programs & Features list in Windows. Do not select this option if this information is required. Adds the `-noarp` switch to the command line. * **No Firewall Entries**: Enabling this setting will prevent Windows Firewall entries from being created automatically. Adds the `-nofirewall` switch to the command line. * **No WoL**: Enabling this setting will disable Wake on LAN. Do not select this option if it is desirable for machines to be woken using Wake on LAN magic packets in the event that content is available on the device, but the machine is offline. Adds the `-nowol` switch to the command line. * **Memory Allocation (in MB)**: This setting configures the maximum JVM memory allocation for the client. As of Adaptiva Client version 9.1, the default memory allocation is 512MB. Do not set this number below 512. It is recommended to set this value in powers of 2 starting at 512. The Memory value in the CLI Input shows the last value used and may differ from the Memory Allocation selection. Change the Memory Allocation to sync the CLI Input. Review the value of the command line to ensure that the `servername | serverip` is correct and that any required or desired command-line switches are present and displaying the correct values. > NOTE: The command line will always contain the `-delay 30` switch on the end. This cannot be overridden. ### Save and Deploy Once you have configured the client upgrade settings, click **Save and Deploy** to start the upgrade process. You will be prompted to validate the command line. ![](/files/MBRcAuNczNb9uc3gyggF) Click **OK** after reviewing the installation command line. These settings are saved in the database in the table `AUTOUPGRADESETTINGS`. When Save is clicked, the latest Adaptiva Client will be published as Adaptiva Content, a hidden schedule, group and content push policy will be created. When the specified start date/time is reached, the clients will download the content. The content will get unpacked into a local folder on the client `%TEMP%\AdaptivaClientUpgrade` (normally `C:\Windows\TEMP`). The client upgrade status will update at the top of the window. ### Disable Legacy Client Upgrade (Windows) Once you have upgraded all devices to the 9.3 Adaptiva client, disable the Legacy Client Upgrade (Windows) feature and use the automatic [Client Upgrade](/platform-guide/client-management/client-auto-upgrade.md) feature moving forward. 1. Toggle OFF Enable Auto Client Upgrade. 2. Click **Save and Deploy**. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.adaptiva.com/platform-guide/client-management/legacy-client-upgrade.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.