day 1 - upgrade

8/13/2019 Day 1 - Upgrade

1/18

www

.technocorp.co.in

Upgrade & Migrations


2/18


3/18

www

.technocorp.co.in

Upgrading to Windows Server 2008

Upgrades to Windows Server 2008 R2 from the following operating synot supported:

Windows 95, Windows 98, Windows Millennium Edition, Windows XP, WindowWindows Vista Starter, or Windows 7

Windows NT Server 4.0, Windows 2000 Server, Windows Server 2003 RTM, W2003 with SP1, Windows Server 2003 Web, Windows Server 2008 R2 M3, or W2008 R2 Beta

Windows Server 2003 for Itanium-based Systems, Windows Server 2008 for ItaSystems, Windows Server 2008 R2 for Itanium-based Systems

Cross-architecture in-place upgrades (for example, x86 to x64) are not Cross-language in-place upgrades (for example, en-us to de-de) are no

supported.

Cross-edition upgrades (for example, the Windows Server 2008 Foundto the Windows Server 2008 Datacenter SKU) are not supported.

Cross-build type in-place upgrades (for example, fre to chk) are not su


4/18


5/18


6/18

www

.technocorp.co.in

Upgrading to Windows Server 2008(cont.)

Microsoft recommends a clean installation instead of aupgrade

Upgrade is similar to clean install, with some exception Instead of booting to the install media, the upgrade install be

the operating system to be upgraded

Upgrading on a domain controller Consider changing Active Directorys functional level


7/18

www

.technocorp.co.in

Server Core: Windows That DoesntWindows

Server Core is suited for the following situations: Acting as a secondary DC to provide redundancy for Active D

Branch office servers when remote administration is likely

RODC server role for a branch office server

As a virtual machine to reduce the amount of resources used

Specialized single role server providing services such as DN

Web, or File Services Departmental server


8/18

www

.technocorp.co.in

Windows Server Core (cont.)

Server Core installation is identical to a full installation Command-line is the only option for configuring many aspe

Server Core

Server Core can be managed to some extent by MMC on a rmachine

Many network related tasks are handled in Server Core by tnetsh commands


9/18

www.technocorp.co.in

When Not to Use Server Core

When its the first server in a network

When you need to install server roles and features that Server Csupport

When the server administrator isnt well versed in using commaprograms

When you need to run applications that require the Microsoft .N

framework When youre upgrading from Windows Server 2003 (No upgrade

When you want to run Windows Web Server 2008 (No Server Co

When you cannot live without a GUI running on your server


10/18


Chapter Summary

Most of the work involved with Windows Server 2008 takesthe planning phase.

Postinstallation configuration tasks include giving the serverconfiguring network protocols, setting time zone informatioselecting a network model, and installing and configuring WUpdates

When adding new servers to an existing network, you must whether the server will be: a domain controller, read only dcontroller, member server, or a stand-alone server


11/18


Chapter Summary

You can upgrade to Windows Server 2008 only if the existingWindows Server 2003

Windows Server Core is a new installation option in StandarEnterprise, and Datacenter editions. Server Core lacks the trWindows GUI, requiring most tasks to be done via comman


12/18


Migration Scenarios

Advantages / Disadvantages Need to install Windows Server Migration Tools feature

Windows Server Migration Tools

File Service migrations

IP configuration migration

DHCP Migration

Active Directory / DNS role Migration

Transfer local users & groups (workgroup)


13/18


Windows Server Migration Tools

Requires .Net Framework 2.0 and PowerShell 1.0 or later Local admin rights on source & destination servers

Used to transfer server roles


14/18


File Migration tools

Export-SmigServerSetting Import-SmigServerSetting

Get-SmigServerFeature

Send-SmigServerData

Receive-SmigServerData


15/18


Ip config migration

Export-SmigServerSetting -IPConfig -Path


16/18


Migrate local Users & Groups

Export-SmigServerSetting -User All -Group -Path localgroups.txt

Logs: %windir%\Logs\SmigDeploy.log %windir%\Logs\ServerMigration.log On Windows Server 2008 and Windows Server 2008 R2: %localappdata%\SvrM On Windows Server 2003: %userprofile%\Local Settings\Application Data\SvrM


17/18


DHCP migration


18/18


AD DS and DNS server migration

day 1 - upgrade

Documents