How To Update Windows Server 2016

If you accept virtual machine (VM) instances running earlier versions of Windows Server, y'all can upgrade them to later versions of Windows Server:

Upgrade from	Upgrade to
Windows Server 2008 R2 (Desktop Experience)	Windows Server 2012 R2 (Desktop Experience)
Windows Server 2012 R2 (Core)	Windows Server 2016 (Core)
Windows Server 2012 R2 (Cadre)	Windows Server 2019 (Cadre)
Windows Server 2012 R2 (Desktop Experience)	Windows Server 2016 (Desktop Feel)
Windows Server 2012 R2 (Desktop Experience)	Windows Server 2019 (Desktop Experience)
Windows Server 2016 (Core)	Windows Server 2019 (Core)
Windows Server 2016 (Desktop Experience)	Windows Server 2019 (Desktop Experience)

Upgrades are bailiwick to the following constraints:

If you program to upgrade Windows Server 2008 R2 to a version later than Windows Server 2012 R2, you lot must outset perform an upgrade to Windows Server 2012 R2, and then perform a second upgrade to Windows Server 2016 or Windows Server 2019.

This guide describes how to perform a transmission in-place upgrade of Windows Server. For upgrades from Windows Server 2008 R2 to Windows Server 2012 R2, yous can also perform automatic in-place upgrades by using the Google Cloud CLI.

Objectives

This guide describes how to perform an in-place upgrade of Windows Server by:

Planning the in-identify upgrade
Performing the in-identify upgrade
Troubleshooting the in-place upgrade
Cleaning up after the in-place upgrade

Costs

At that place is no accuse for performing an in-place upgrade of Windows Server. Yous are merely charged for the resource consumed during the upgrade, including:

Compute Engine

Use the pricing calculator to generate a cost guess based on your projected usage.

Before you brainstorm

The guide assumes that yous take basic knowledge of:

Compute Engine
Performing unattended Windows Server installations past using Windows Setup.

Plan the in-place upgrade

Performing an in-identify upgrade of a virtual auto (VM) case that is running an earlier version of Windows Server tin be a businesslike way to modernize your infrastructure and to mitigate the risks of approaching the end of the support lifecycle of Windows Server versions.

Alternatives to consider

Before you decide to use an in-place upgrade to migrate to a newer version of Windows Server, be aware of the post-obit limitations:

Downtime: Depending on the configuration and software installed, the upgrade might accept an hour or longer. During the upgrade, access to the VM instance is express considering:
- Workloads running on the VM instance are unavailable to users
- Remote Desktop Protocol (RDP) is not available
- There are limited ways to check the upgrade progress and the fourth dimension remaining in the upgrade
Risk: Depending on the configurations of your existing instances and the installed software:
- The upgrade can fail
- Some configuration options tin be overridden
- Incompatibilities can cause your workload to malfunction on the upgraded instance

Depending on the workload running on your Windows Server instance, y'all can reduce downtime and chance by pursuing dissimilar approaches.

Workload	Approach
Your VM case is running a workload that supports replication, such as: Agile Directory Domain Services DNS SQL Server	Consider setting up a new VM example that is running a more recent version of Windows Server, and then use replication to shift the workload from your existing VM case to the new VM example.
You take a VM example that is running a multitude of workloads	Consider migrating these workloads to dissever VM instances so that each VM instance runs only a unmarried workload. Even if you can't migrate all workloads, reducing the number of workloads running on a single VM instance tin can assistance reduce risks during an in-place upgrade.

Production keys

A Windows Server production key is valid for simply a specific version; when you perform an upgrade to a later on version of Windows Server, you must supply a new product key. In that location are two primary scenarios:

You are upgrading a VM instance that is based on a public operating system image provided by Google: In this scenario, you must use the predefined KMS client setup keys for the version of Windows Server that you are upgrading to. The upgrade does not incur additional charges.
You are upgrading a VM instance for which yous brought an existing license: In BYOL, you lot need to acquire a product key from your license vendor to perform the upgrade. Check the Microsoft documentation to determine which edition y'all can upgrade to and whether you are eligible for license conversion.

Installation media

To perform the upgrade, you need an installation media. There are 2 primary scenarios:

You are upgrading a VM instance that is based on a public operating system prototype provided past Google: In this scenario, yous can use the volume license installation media provided by Google. The steps to access this installation media are provided below.
You are upgrading a VM instance that is based on an imported disk or image: In this scenario, you cannot use the installation media provided by Google. Instead, you accept to utilise an installation media that matches the type of media that yous used to install Windows Server on the imported disk or image.

Other prerequisites

Before you lot begin your upgrade, review the Microsoft documentation virtually prerequisites and potential limitations for the version of Windows Server you are planning to upgrade to:

Perform the in-identify upgrade

The post-obit sections guide you through the procedure of upgrading your VM instance.

Create a snapshot

Before you start the upgrade, we recommend that you create a snapshot of your VM example, so that you can revert to a safety state in case anything goes wrong:

Create a regular snapshot for the boot disk of your VM case.
If the VM case has additional data disks fastened, create snapshots for the data disks past using the Volume Shadow Copy Service (VSS).

Prepare your Windows Server configuration

Verify the configuration of your Windows Server VM instance:

Connect to your VM example with an RDP client.
Verify that Windows Server is up to date by using Windows Update.
Disable or uninstall antivirus, antispyware, and other agents that can interfere with the upgrade or are incompatible with the Windows Server version that y'all're upgrading to.

Adhere the install media

Earlier y'all can perform the upgrade, attach the necessary installation media to the VM instance. The correct media to utilise depends on your scenario:

You are upgrading a VM case that is based on a public operating organization prototype provided by Google: In this scenario, you only demand to attach the volume license installation media provided by Google. This media contains both the necessary scripts to run the upgrade and the files for the new version of Windows Server.
You lot are upgrading a VM instance that is based on an imported disk or paradigm: In this scenario, you also need to attach the volume license installation media provided by Google so that yous can admission the necessary scripts.

Additionally, you lot have to adhere a custom installation media that matches the blazon of media that you used to install Windows Server on the imported disk or image.

To attach the book license installation media provided by Google, follow these steps:

In the Google Cloud Console, open up Deject Beat by clicking the Activate Cloud Vanquish button.

Become to the Google Cloud Console
Ready the default project ID. Replace PROJECT_ID with the name of your Compute Engine project:
```
gcloud config prepare project              PROJECT_ID            
```
Create a disk based on the installation media. Replace ZONE with the name of the zone where the VM example is located:
```
gcloud compute disks create win-installers --prototype-family=windows-install-media --image-project=compute-image-tools --zone=ZONE            
```
This command adds a disk named win-installers to your project. This disk is not attached to any VM example.
Attach the disk to your VM instance by using read-only (ro) mode, so that y'all can attach the disk to multiple VM instances if necessary:
```
gcloud compute instances attach-disk              VM_NAME              --disk=win-installers --mode=ro --zone=ZONE            
```
Replace the following:
- VM_NAME : the name of the VM case to upgrade
- ZONE : the name of the zone where the VM instance is located

If y'all are upgrading a VM case that is based on an imported disk or image, adhere the custom installation media as an additional disk:

Follow the steps in Creating an paradigm from an ISO file to create a disk from the ISO image that you desire to use every bit custom installation media.
Attach the disk to your VM instance, past using read-but (ro) style so that you can attach the disk to multiple VM instances if necessary:
```
gcloud compute instances attach-disk              VM_NAME              --deejay=CUSTOM_MEDIA_DISK              --way=ro --zone=ZONE            
```
Supplant the following:
- VM_NAME : the name of the VM case to upgrade
- CUSTOM_MEDIA_DISK : the name of the disk containing your custom installation media
- ZONE : the name of the zone where the VM example is located

Start the upgrade

By default, Windows Setup prompts you for input at various points during an upgrade. Because yous tin can't connect to the VM instance past using RDP during the upgrade and therefore can't provide any input, run the upgrade in unattended mode.

Connect to your VM example with an RDP customer. For more information, encounter Connecting to instances.
Open an elevated control prompt:
- If you lot employ Server Core, an elevated control prompt should open automatically after login.
- If y'all utilize Windows Server with full Desktop Experience, right-click the Start button and select Command Prompt (Admin).
Change the working directory to the installation media. The correct working directory depends on the Windows Server version that you lot are upgrading to:
2012 R2
```
cd /d d:\*2012*                
```
2016
```
cd /d d:\*2016*                
```
2019
```
cd /d d:\*2019*                
```
Kickoff the Windows upgrade. The required steps to outset the upgrade depend on the Windows Server version that you are upgrading to and whether your VM instance is based on a public operating system image or on an imported disk or image:
2012 R2

Run upgrade.ps1 to first the Windows upgrade. The script completes the following steps:
- Install the latest Google driver packages, which are critical for the Windows Server upgrade to succeed.
- Apply Windows settings that are required for Compute Engine.
- Enable access to the Emergency Management Services (European monetary system) console during the upgrade.
- Launch Windows Setup (setup.exe) from the install media to perform an upgrade in unattended mode.
- Select the right edition of Windows Server 2012 R2 to install.
- Provide a product key for the new version of Windows Server.
```
powershell -ExecutionPolicy Bypass -File upgrade.ps1                
```
2012 R2 (imported)

Run upgrade.ps1 to outset the Windows upgrade. The script completes the post-obit steps:
- Install the latest Google driver packages, which are critical for the Windows Server upgrade to succeed.
- Utilize Windows settings that are required for Compute Engine.
- Enable access to the Emergency Management Services (EMS) console during the upgrade.
- Launch Windows Setup (setup.exe) from the install media to perform an upgrade in unattended mode.
- Select the correct edition of Windows Server 2012 R2 to install.
```
powershell -ExecutionPolicy Bypass -File upgrade.ps1 -SetupExePath                  SETUP_PATH                  -Unattend                  UNATTEND_PATH                
```
Replace the following:
- SETUP_PATH : the path to setup.exe on your custom installation media
- UNATTEND_PATH : the path to a custom unattend.xml file that contains a valid production primal
The -Unattend parameter is merely required if yous are upgrading a VM instance for which you lot brought an existing license (BYOL)
2016 or 2019

Run upgrade.ps1 to first the Windows upgrade. The script completes the following steps:
- Install the latest Google driver packages, which are critical for the Windows Server upgrade to succeed.
- Utilise Windows settings that are required for Compute Engine.
- Enable access to the Emergency Direction Services (EMS) console during the upgrade.
- Launch Windows Setup (setup.exe) from the install media to perform an upgrade in silent manner.
- Provide a production central for the new version of Windows Server.
```
powershell -ExecutionPolicy Bypass -File upgrade.ps1                
```
On the Select Epitome screen, select the configuration that matches your current configuration:
- If yous currently use Server Core, select Windows Server Datacenter.
- If you currently utilise Windows Server with full desktop experience, select Windows Server Datacenter (Desktop Feel).
- Click Next to begin the upgrade.
It might have several minutes for the setup to initialize.
2016 or 2019 (imported)

Run upgrade.ps1 to start the Windows upgrade. The script completes the following steps:
- Install the latest Google driver packages, which are critical for the Windows Server upgrade to succeed.
- Apply Windows settings that are required for Compute Engine.
- Enable admission to the Emergency Management Services (Ems) console during the upgrade.
- Launch Windows Setup (setup.exe) from the install media to perform an upgrade in silent mode.
```
powershell -ExecutionPolicy Bypass -File upgrade.ps1 -SetupExePath                  SETUP-PATH                  -ProductKey                  Production-KEY                
```
Replace the following:
- SETUP_PATH : the path to setup.exe on your custom installation media
- PRODUCT_KEY : a valid product fundamental for Windows Server 2016
The -ProductKey parameter is only required if you are upgrading a VM instance for which you brought an existing license (BYOL).

On the Select Epitome screen, select the configuration that matches your current configuration:
- If y'all currently use Server Cadre, select Windows Server 2016 Datacenter.
- If you currently use Windows Server with total desktop feel, select Windows Server 2016 Datacenter (Desktop Feel).
- Click Next to begin the upgrade.
Information technology might have several minutes for the setup to initialize.
The upgrade process might event the post-obit alarm. If so, you can ignore it:
```
[package name] or a newer version is already installed on the system            
```
After most five minutes, the automobile reboots, and RDP disconnects.

Observe the upgrade procedure

Depending on the machine type of your VM instance and your Windows Server configuration, the upgrade might take between 10 and hr to consummate. During that time, you can observe the status through the series port output:

In Cloud Shell, observe the boot process by running the following command:
```
gcloud compute instances tail-serial-port-output              VM_NAME              --zone=ZONE            
```
Replace the following:
- VM_NAME : name of your VM instance
- ZONE : proper noun of the zone where the VM case is located
Wait until the machine has rebooted four times. Depending on the configuration of your VM instance, it might accept 30 minutes or more for these reboots to occur. You can recognize a reboot by output that looks similar to this:
```
SeaBIOS (version i.8.two-20190620_103534-google) Total RAM Size = 0x00000001e0000000 = 7680 MiB CPUs plant: ii     Max CPUs supported: two            
```
Later on the fourth reboot, await until the output GCEMetadataScripts: Finished running startup scripts or No startup scripts to run appears.

Perform post-upgrade steps

Y'all can now connect to the VM instance to verify that the upgrade has been successfully completed.

Connect to the VM instance by using an RDP client. For more information, see Connecting to instances.
Log in using a user account with local administrator privileges.
Open up an elevated command prompt:
- If you lot utilise Server Cadre, an elevated command prompt should open automatically later login.
- If you use Windows Server with full desktop experience, correct-click the Starting time button and select Command Prompt (Admin).
Run the following command to query the version of Windows Server:
Windows Server Core
```
ver                
```
Windows Server with Desktop Experience
```
winver                
```
Verify that the version matches the expected version of Windows Server.
Change the working directory to the installation media. The correct working directory depends on the Windows Server version that yous are upgrading to:
2012 R2
```
cd /d d:\*2012*                
```
2016
```
cd /d d:\*2016*                
```
2019
```
cd /d d:\*2019*                
```
Run upgrade.ps1 again to re-apply specific Compute Engine settings that might have been lost during the upgrade:
```
powershell -ExecutionPolicy Bypass -File upgrade.ps1            
```
Restart the VM case to ensure all changes have consequence. Information technology might take ane to 2 minutes for the reboot to complete before you can connect to the VM case again.

Disassemble the installation disk

You can now disassemble the installation disk from the VM example:

In Cloud Beat, detach the installation deejay from your VM case, replacing VM_NAME with the name of your VM example:

gcloud compute instances detach-disk              VM_NAME              --disk=win-installers

Install updates and restore access

Later the upgrade is complete, run Windows Update to download and install whatsoever security updates. To install the security updates, follow these steps:

Connect to the auto by using an RDP customer. For more information, see Connecting to instances.
Use Windows Update to install the latest Windows updates. You might accept to restart the VM instance multiple times during this process.
Re-enable whatsoever agents, antivirus, or antimalware software that yous disabled before the upgrade.

Troubleshoot the in-place upgrade

While running Windows Setup, you can't connect to the VM instance with RDP. If you doubtable that the upgrade failed or is not progressing, use the post-obit approaches, in order, to diagnose the situation:

Check the serial port output

To bank check the progress of the upgrade procedure, view the series port output of the VM instance:

Serial port 1 captures the boot condition
Serial port iii captures the log output of Windows Setup

During the upgrade, y'all should observe four reboots. If you lot don't discover any progress for more than 30 minutes afterward the first reboot, it is likely that the upgrade failed.

Bank check CPU and I/O metrics

Running a Windows Server upgrade is a CPU and disk I/O intensive operation. By checking the CPU and I/O metrics, yous tin get an indication for whether the setup is progressing.

View the CPU and I/O metrics in the Google Cloud Console:

In the Cloud Console, go to the VM instances page.

Get to VM instances
Click the example that you're upgrading.
Click the Monitoring tab.

Connect to the Emergency Management Services console

Both during and later on running Windows Setup, you tin connect to the Emergency Direction Services (EMS) panel. Using the EMS console, check the Windows Setup log files and the event log for indications that the upgrade is however progressing or for data about any errors that might take occurred.

Connect remotely past using WinRM

If connecting by using RDP or European monetary system fails, you can try using WinRM to establish a remote PowerShell session:

Connect to a different Windows Server case in the aforementioned VPC.
Open up PowerShell.

Institute a remote PowerShell session, replacing VM_NAME with the name of the example to upgrade:

Enter-PSSession -ComputerName              VM_NAME              -UseSSL -SessionOption (New-PsSessionOption -SkipCACheck) -Credential (Get-Credential)

When prompted for credentials, enter the username and password of an administrative user account.
Apply the remote PowerShell session to cheque the Windows Setup log files and the event log.

Analyze log files offline

If you tin't connect to the instance past using Windows Remote Management (WinRM), you can cancel the upgrade and clarify the log files from a unlike VM instance. To do this, follow these steps:

Stop the VM case.

This tin can take several minutes if Windows Server is unresponsive.
Disassemble the kicking disk from the example.
Create a new, temporary Windows Server case, and attach the boot disk of the original instance every bit an additional disk.
Use the temporary Windows Server instance to analyze the setup log and event log files of the instance that y'all were trying to upgrade.
After you accept completed the assay, detach the disk from the temporary example and reattach it every bit a kick disk to the original VM example.

Troubleshoot RDP

For data well-nigh troubleshooting RDP, come across Troubleshooting RDP.

Troubleshoot your Windows Server instances

For information about troubleshooting your Windows Server instances, see Tips and troubleshooting for Windows instances.

Clean up

To avoid incurring further costs after you take completed this process, delete the installation disk.

Delete the installation disk

You can create an installation deejay based on the Google-provided image at any fourth dimension. If you lot don't plan to upgrade more than VM instances in the same zone, delete the installation deejay:

In Cloud Shell, delete the win-installers disk that you lot created earlier:
```
gcloud compute disks delete win-installers            
```

What's next

Learn how to bring existing licenses to Compute Engine.
Acquire how to connect to Windows instances.
Acquire well-nigh sole-tenant nodes on Compute Engine.
Work through more than Windows tutorials.

Source: https://cloud.google.com/compute/docs/tutorials/performing-in-place-upgrade-windows-server

Posted by: reedindraviverry.blogspot.com

How To Update Windows Server 2016

Objectives

Costs

Before you brainstorm

Plan the in-place upgrade

Alternatives to consider

Production keys

Installation media

Other prerequisites

Perform the in-identify upgrade

Create a snapshot

Prepare your Windows Server configuration

Adhere the install media

Start the upgrade

2012 R2

2016

2019

2012 R2

2012 R2 (imported)

2016 or 2019

2016 or 2019 (imported)

Observe the upgrade procedure

Perform post-upgrade steps

Windows Server Core

Windows Server with Desktop Experience

2012 R2

2016

2019

Disassemble the installation disk

Install updates and restore access

Troubleshoot the in-place upgrade

Check the serial port output

Bank check CPU and I/O metrics

Connect to the Emergency Management Services console

Connect remotely past using WinRM

Analyze log files offline

Troubleshoot RDP

Troubleshoot your Windows Server instances

Clean up

Delete the installation disk

What's next

0 Response to "How To Update Windows Server 2016"

Post a Comment

Iklan Atas Artikel

Iklan Tengah Artikel 1

Iklan Tengah Artikel 2

Iklan Bawah Artikel