Windows Server 2003 Migration Planning Assistant – File Server Migration


The next series of posts will be focused on the Windows Server 2003 Migration Planning Assistant recommendations for OEM server related workloads, starting with File Server Migration.

Upgrade on new hardware
Hardware requirements define the minimum hardware required to run the Windows Server 2012 R2 server, but your actual hardware requirements might be greater, depending on the server’s load and responsiveness and the services that it hosts. Each role service and feature places a unique load on network, disk I/O, processor, and memory resources. For example, the File Server role places different stresses on server hardware than the DHCP role does.
Top Considerations:

Confirm that running this workload on a physical server is required. Running workloads as Virtual Machines offer more flexibility and tend to be more cost effective

Upgrade on virtual machine
 
Windows Server 2012 R2 can be deployed on a virtual machine in your Microsoft Hyper-V or other hypervisor environment for increased operational efficiency, flexibility, and ease of management. Windows Server 2012 R2 virtualized deployments need to match the same hardware specifications as physical deployments. For example, when you create a virtual machine to host Windows Server 2012 R2, you need configure the virtual machine with enough memory and hard disk space.
Top Considerations:

When deploying Virtual Workloads verify you are building with capacity to support all workloads that the Virtualization Host supports

 
Implementing Virtualization
Virtual Licenses
Designing Virtual Machines
Comments (2)
  1. Anonymous says:

    After focusing on the File Server migration recommendations in the last post , it’s time to focus

  2. Anonymous says:

    Following on from File Server and Web Server migration, today’s focus is on Active Directory migration

Comments are closed.

Skip to main content