You can check the system log for console outputs or refer to Amazon Cloud Watch monitors for disk and CPU activity to determine if the upgrade is not progressing.This topic describes two methods for upgrading an older version of a Windows Server EC2 instance to a newer version: in-place upgrade and migration (also called side-by-side upgrade).Microsoft has traditionally recommended migrating to a newer version of Windows Server instead of upgrading.
After several minutes, your Remote Desktop session closes.
Migrating can result in fewer upgrade errors or issues, but can take longer than an in-place upgrade because of the need to provision a new instance, plan for and port applications, and adjust configurations settings on the new instance.
An in-place upgrade can be faster, but software incompatibilities can produce errors.
The time it takes to upgrade will depend on the number of applications and server roles running on your Windows Server instance.
The upgrade process could take as little as 40 minutes or as long as several hours.
PV drivers enable you to access your instance by using Remote Desktop.
Windows Server 2012 RTM and R2 instances use Important AWS provides upgrade support for issues or problems with the Upgrade Helper Service, an AWS utility that helps you perform in-place upgrades involving Citrix PV drivers.
Note This topic includes information about a known issue during the upgrade process where Setup removes portions of the para-virtual (PV) drivers that enable a user to connect to the instance by using Remote Desktop.
Before you perform an in-place upgrade of an EC2 Windows Server instance you must determine which PV drivers the instance is running.
The instance will fail status check 1 of 2 in the EC2 console during the upgrade process.
When the upgrade completes, both status checks pass.