The goal of this article is to provide guidance for upgrading your Publisher resources, such as CPU, memory, or the storage size. This article also provides details about how to upgrade resources for new as well as existing Publisher deployments, and across different platforms such as AWS, Azure, OVA, Hyper-V.
For sizing guidance, in order to support the Browser Access AnyApp (RDP/SSH) feature, the server hosting the Publisher needs to be sized according to your requirements. To support up to 30 concurrent RDP connections on a single Publisher instance, here are the requirements:
- 6 CPU cores
- 8 GB RAM
- 30 GB HDD (Available disk space)
Upgrade a Publisher’s CPU, Memory
AWS AMI Publisher
Set up CPU and Memory Resources while Creating a New AWS AMI Publisher
The new AWS AMI Publisher’s instance type can be set in the AWS EC2 console.
In the Instance type section, select the instance type you want to use. 
Upgrade CPU and Memory Resources for an Existing AWS AMI Publisher
The existing AWS AMI publisher’s instance type can be changed from the AWS EC2 console.
- Stop the instance in your EC2 dashboard, and click on the Instance ID.
- Open the Actions dropdown menu at the top of the page. Go to Instance settings, and click Change instance type.
- Select a new instance type in the New instance type field, and then click Apply.
- Restart the instance.
Azure VHD Publisher
Set up CPU and Memory Resources while Creating a New Azure VHD Publisher
The new Azure VHD publisher’s instance type can be set in the Azure Web console.
In the Size section, select the instance type you want to use. To see all available options, click See all sizes for more information.
Upgrade CPU and Memory Resources for an Existing Azure VHD Publisher
The Azure VHD Publisher’s instance type can be changed in the Azure VM console.
- First, check your current instance type in the Azure Web Console. As the following figure shows, we’re using the instance type Standard D2s v3 (2 vCPU / 8GB RAM) as an example. Make sure your Publisher is working without any other issue here. This resizing process does not require a manual instance restart.
- Scroll down and select Size in the left panel. In this example, we’re resizing the instance from Standard D2s v3 to Standard D8s v3. Select Standard D8s v3, verify the instance type, and then click Resize. Choose the instance type that would meet your current requirements or future needs.
- The Instance status turns to Updating, and the size will be updated as per your choice in the previous step. This update will take a few minutes.
- Check that all related resource information is updated while the instance status turns to Running.
- Also, log into the instance via a terminal to confirm this machine is working without any issue after the update.
OVA Publisher
Upgrade CPU and Memory Resources for an Existing OVA Publisher
The OVA Publisher’s CPU/Memory can be changed in the hypervisor console (like ESXi 5.1.0 and Vcenter 5.5.0, for example).
The expand_drive.sh script is only required to be run in on-premises hypervisor environments. Cloud Hypervisor environments automatically expand attached storage partitions upon reboot, after modifying in the hypervisor.
- Log in to your instance and check current Memory and CPU information.
- In the ESXi console, select your Publisher VM. Go to Summary, and then shut down the Publisher by clicking Shut Down Guest.
- After the instance has completely stopped, click Edit Settings.
- Update the Memory and CPU to the desired value, and then click OK.
- Click Power On for the Publisher VM.
. - After the Publisher VM is powered on, log in to the instance and recheck the Memory and CPU information.
VHDX Publisher
Upgrade CPU and Memory Resources for an Existing VHDX Publisher
The VHDX publisher’s CPU/memory can be changed in the hypervisor console (like Hyper-V, for example).
The expand_drive.sh script is only required to be run in on-premises hypervisor environments. Cloud Hypervisor environments automatically expand attached storage partitions upon reboot, after modifying in the hypervisor.
- Log into your instance and check the current CPU and Memory information.
- In the Hyper-V console, select your instance and click Shutdown tin the right side menu.
- After the instance is completely stopped, find Edit Disk to resize the disk.
- Enter the desired values,and then click OK to apply all.
- Restart your instance and check the CPU and Memory information again.
Upgrade a Publisher’s HDD storage
AWS AMI Publisher
Set up Storage while Creating a New AWS AMI Publisher
The new AWS AMI Publisher’s storage size can be set in the AWS EC2 console.
In Configure storage section, change the storage size to the capacity you want to use.
Upgrade Volume Size for an Existing AWS AMI Publisher
The AWS AMI Publisher’s HDD storage can be changed in the AWS EC2 console.
- Stop the instance in your EC2 dashboard, and click on the Instance ID.
- Click on the Storage tab, and then on the Volume ID.
- Locate the Volume ID and click Modify Volume in the Actions dropdown menu at the top of the page.
- Set the new size and click Modify.
- Log in to the Publisher instance and check that the storage capacity has been updated.
Azure VHD Publisher
Set up Disk Resources while Creating a New Azure VHD Publisher
The new Azure VHD Publisher’s storage size can be set in the Azure VM console.
In the Disk section, choose the disk size and type that meet your needs.
Upgrade Disk Size for an Existing Azure VHD Publisher
The Azure VHD Publisher’s disk storage can be changed in the Azure VM console.
- In order to resize disk on Azure instance, stopping your instance is required.
- Before resizing, take a look at current disk status. Select Size on the left hand side panel. Click on the disk name you would like to resize for more details. Next, select Size and Performance on the left panel.
- Choose the disk size you would like to resize to and click Save to apply the update. In this example, we are resizing the instance disk from 30 GiB to 64 GiB.
- You’ll receive a message when this update is complete. Check the updated disk information on the disk page. Updating the disk size may take a while.
- Restart the instance.
- After the instance reaches the Running state without any issue, log in to your instance via a terminal to verify this change has been applied properly.
OVA Publisher
Upgrade Disk Size for an Existing OVA Publisher
The OVA Publisher’s HDD storage can be changed in the hypervisor console (like ESXi, for example).
- Check the current available disk size mounted on root:
The recommendation is 30 GB of available disk space. Please adjust the total required size accordingly. - Log in to ESXi, select the virtual machine, and power it off. Click Edit Settings, change the size of the Hard Disk according to any needed adjustment, click OK, and then power it on.
- Log in to your Publisher instance, choose 6 for Browser Access AnyApp settings, and then choose 2 for Expand disk space for Browser Access AnyApp.
- Press yes.
If the script successfully expands the partition, you will see Successfully expand the partition, current publisher partition size is xxx.
If the current available size is already larger than 30 GB, then the script will exit directly: 
If the disk has already been expanded to its maximum size, the script will terminate with a failure. If further expansion is required, increase the physical size via the ESXi console and repeat step 3. 
VHDX Publisher
Upgrade Disk Size for an Existing VHDX Publisher
The VHDX Publisher’s HDD storage can be changed from the hypervisor (like ESXi, for example).
- Log in to your instance and check current disk information. The recommendation is 30 GB of available disk space. Adjust the total required size accordingly.
- From the Hyper-V console, select your instance and shutdown the instance from the right side menu.
- After the instance has completely stopped, scroll up and find Edit Disk to resize the disk.
- Click Next.
- Provide the actual disk path for this instance.
- Select the Expand option.
- Enter the desired disk size for resizing.
- Verify the information and click Finish. Restart your instance and repeat step 1 to check disk information.
You would find that the disk has not been updated to the desired size you configured in previous steps. Continue executing the following script in order to mount the resized disk properly.
- Log in to your Publisher instance, choose 6 for “Browser Access AnyApp settings” and then choose 2 for “Expand disk space for Browser Access AnyApp”
- If the script successfully expands the partition, you will see Successfully expand the partition, current publisher partition size is xxx. Check the disk information again to see the desired disk size you configured.
If the current available size is already larger than 30 GB, the script will exit directly: 
If the disk has already been expanded to its maximum size, the script will terminate with a failure. If further expansion is required, increase the physical size via the ESXi console and repeat Step 3. 