Solution for Migrating From Novell Netware to Windows Server 2003

8/11/2019 Solution for Migrating From Novell Netware to Windows Server 2003

1/69

Solution for Migrating File, Print, and Directory Servicesfrom Novell NetWare to Windows Server 2003

Microsoft Corporation

Published: November 2004

Abstract

T is guide demonstrates t e first stage of a Novell NetWare migration !ro"ect# migrating directory, file, and !rint

services to Microsoft $ Windows Server% 2003 &ctive Directory $ directory services' T is stage (uilds t e

infrastructure on w ic you will migrate t e directory and file and !rint services' Wit an &ctive Directory

infrastructure in !lace, you can t en define future stages suc as moving mail and ot er a!!lications or adding

&ctive Directory features' )ou will learn ow to !lan your !ro"ect, develo! t e solution for t e new environment,

determine t e (est migration strategy for your environment, and migrate directory and file and !rint services to

t e new environment'


2/69

2004 Microsoft Corporation. This wor is licensed under t he Creative Commons !ttribution"NonCommercial #icense. To view a cop$ of this license%

visit http:&&creativecommons.or'&licenses&b$"nc&2.(& or send a letter to Creative Commons% (4) *oward +treet% (th ,loor% +an ,rancisco% California%

-4 0(% /+!.


3/69

Contents

Preface'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' *+verview''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''*

ntended &udiences''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' *Sco!e''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' ' 2-ow to .se T is Migration /uide''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' '2

ntroduction'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' '''''Tec nology +verview'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''

1nvisioning )our Novell to Windows Migration Pro"ect''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''**ntroduction and /oals''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' **

Setting .! t e ore Pro"ect Team for a Novell to Windows Migration Pro"ect'''''''''''''''''''''''*3reating t e ision'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' *4reating t e Solution once!t''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' *5

Defining t e Sco!e of t e Pro"ect'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 20Pro"ect Timeline''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 2*

&ssessing Pro"ect 6is7s'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' '''' 2*Planning )our Novell8to8Windows Migration Pro"ect''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''23

ntroduction and /oals'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''231valuating t e 19isting 1nvironment'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' ''''' 24Develo!ing t e Solution Design and &rc itecture'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 25Migration Planning''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 30

reating t e Functional S!ecification'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 3:Develo!ing t e Pro"ect Sc edule'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''3:Test Planning''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' 3:

Migrating# Prototy!ing t e Migration to Windows Server 2003''''''''''''''''''''''''''''''''''''''''''''''''''43ntroduction and /oals'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''43alidating Test ;a( om!onents'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' ''''''' 43

Testing t e Design and Migration Process'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''44Sta(ili


4/69

ontri(utorsWriter

>at i -onegger @ onvergent om!utingA

Editors

Trelawney /oodell @ oltAT omas +lsen @ oltA

Program Manager

Pa(lo ?Brcenas (inarriaga @Microsoft or!orationA

Project Manager

6ic Dorfman @ onvergent om!utingA

Reviewers

Fred &ntro(us @19cell Data or!orationA

risto! er West!oint @Microsoft or!orationA

i


5/69

Preface

Overview6egardless of t e si


6/69

C 18DirectoryENDS conce!ts

C entrali


7/69

C De!loying

1ac guide !resents t e information @!rocess or tec nicalA needed for a ! ase wit inc a!ters named for t at ! ase' For e9am!le, in t e solution guide, (usiness andtec nical information needed for t e initial decision8ma7ing is in t e 1nvisioning c a!ter,detailed !rocedures and scri!ts are in t e Migrating c a!ters, and so onA'

T e .MP/ is essentially MSF a!!lied to migration !ro"ects' t (egins wit an overviewof MSF and t en descri(es t e !rocesses t at (elong to eac ! ase and t e team rolesres!onsi(le for t em it is not% owever % meant to serve as a com!re ensive introductionto MSF' n8de!t information a(out MSF is availa(le to interested readers on t eMicrosoft Solutions Framewor7s We( site at tt!#EEwww'microsoft'comEmsf '

T e reason for se!arating t e !rocess guidance from tec nical and !ro"ect8s!ecificguidance is to 7ee! t is guide as lean as !ossi(le' Some readers will need to focusnarrowly on !ro"ect tas7s, w ile !ersons wit !ro"ect management and team leadres!onsi(ilities need to digest t e .MP/ guidance and a!!ly it to t e !ro"ect'

?ecause organi


8/69

Organi&ation o' C$a tersFollowing an introductory c a!ter, t is guide is divided into four sections, Plan, ?uild,De!loy, and +!erate, t at cover t e entire s!an of t e T solution life cycle' T e fiveMicrosoft Solutions Framewor7 ! ases fall into t e first t ree sections, and t e Microsoft+!erations Framewor7 is t e reference framewor7 for t e final section'

C Introduction- T e ntroduction c a!ter defines t e !ro"ect, !rovides an overview of t e tec nologies discussed in t is guide, and introduces migration o!tions andtools'

C Plan- T e Plan section is divided into two c a!ters, 1nvisioning and Planning'T ese c a!ters corres!ond wit t e first two MSF ! ases' n t e 1nvisioningP ase t e team and s!onsor agree on t e ig 8level reHuirements and goals of t e!ro"ect' T e Planning P ase is w ere t e team defines w at to (uild and de!loyalong wit ow and w en to (uild it'

C .uild- T e ?uild section is divided into two c a!ters, Migrating and Sta(ili


9/69

*ntroductionT is document is a guide to migrate a Novell NetWare environment to t eWindows Server 2003 o!erating system and &ctive Directory'

#ec$nolog* OverviewT is section !rovides a (rief overview of t e tec nologies addressed in t is guide' Forlin7s to more information on any of t ese tec nologies, see t e

?i(liogra! yE6eferences section in &!!endi9 &'

+ovell +etWareNovell NetWare is a (ase o!erating system' Novell NetWare s ould not (e confused witeDirectory or NDS, w ic are t e directories t at run on to! of NetWare' NetWare asevolved from NetWare =5, 2=5, 3=5, 2'9, 3'*, 3'2, 4'0, 4'*, 4'*2, 4'2, '0, '*, and 5' T ecurrent version is t e NetWare 5 !roduct owever, most organi


10/69

Novell and ;inu9 along wit Windows increases administrative and training reHuirements'n addition, resource availa(ility (ecomes an issue, as it is difficult to find engineers t at

are well versed in all t ree o!erating systems'

Windows Server 0112

T e Windows Server 2003 !roduct is a com!re ensive networ7 o!erating system t atcan serve many roles suc as a file and !rint server, We( server, an a!!lication server,and a Windows 'N1T a!!lication ost' Windows Server 2003 comes wit several!rograms and tools to !rovide networ7ing functionality' Some of t e a!!lication serverfunctions include domain controller, glo(al catalog server, DNS server, D- P server,cluster server, terminal services server, remote access server, We( server, media server,and Distri(uted File System @DFSA server'

During t e design and !lanning !rocess an organi


11/69

&fter t e Windows Server 2003 environment is esta(lis ed, Windows Storage Server2003 !rovides you wit an additional storage o!tion for file service'

For additional information a(out Windows Storage Server and N&S de!loymentscenarios see Windows Servers in a Storage &rea Networ7 1nvironment

tt!#EEwww'microsoft'comEwindowsserversystemEwss2003Etec infoE!lande!loyEmssans'm

s!9 '

:
http://www.microsoft.com/windowsserversystem/wss2003/techinfo/plandeploy/mssans.mspxhttp://www.microsoft.com/windowsserversystem/wss2003/techinfo/plandeploy/mssans.mspxhttp://www.microsoft.com/windowsserversystem/wss2003/techinfo/plandeploy/mssans.mspxhttp://www.microsoft.com/windowsserversystem/wss2003/techinfo/plandeploy/mssans.mspx


12/69

Part *# P;&N


13/69

21nvisioning )our Novell toWindows Migration Pro"ect

Introduction and %oalsT is c a!ter !rovides t e (ac7ground and tec nical information reHuired to com!lete t efirst ! ase of a Novell to Windows migration !ro"ect, t e 1nvisioning P ase, w icre!resents an early form of !lanning' T e !ur!ose of t is initial wor7 is to get t e !ro"ectstarted (y ac ieving a (asic agreement (etween (usiness sta7e olders and T, asre!resented (y t e !ro"ect team, on t e goals for t e !ro"ect as well as its constraints'

T e guide ma7es t e following (asic assum!tions a(out t e state of t e organi


14/69

Major #as)s and /eliverables?y t e end of t e ! ase, t e team and all ma"or sta7e olders for t e !ro"ect s ould aveagreed u!on t e following conce!tual areas and documented t eir understanding in avisionEsco!e document#

C & vision for t e solutionC Defines t e (usiness o!!ortunities or !ro(lems t at t e solution is e9!ected to

address, including ma"or (usiness and user reHuirements'

C Descri(es t e current state of t e environment @at a ig levelA wit res!ect tot e tec nology (eing considered'

C Descri(es t e desired future state of t e organi


15/69

Envisioning P$ase Major Milestone, 3ision4Sco eA rovedT e 1nvisioning P ase ends w en t e team, t e customer @(usiness s!onsorA, and ma"or !ro"ect sta7e olders @ot er mem(ers of t e organi


16/69

Creating t$e 3ision?efore you can migrate to a new Windows Server 2003 &ctive Directory environment youmust first determine w at t at environment will loo7 li7e and t en develo! a migrationstrategy for ow to get t ere'

A 3ision 'or t$e SolutionT e vision starts wit a (usiness !ro(lem' T is !ro(lem s ould (e t e driving factor inyour investigating migration to Windows Server 2003'

Some common (usiness drivers for migrating from Novell NetWare toWindows Server 2003 include#

C Discontinued su!!ort for Novell NetWare' n t e ne9t version of Novell, t eo!erating systems will no longer (e NetWare it will (e Novell on to! of ;inu9'

C Difficulty of u!grade to new Novell NetWare version' +rgani


17/69

C W at is t e cost of a!!lication downtime to your (usinessQ

C W at is t e cost of system maintenanceQ -ow many !eo!le would you need tomaintain t e systemQ

C W at is t e cost of su!!ortQ

C ncreasing t e usa(ility of t e systemT e a!!lications on t e system s ould (e easy to develo! and use' Systems t atoffer integrated security and develo!ment environments for a!!lications areo!timal'

C Providing ease of managea(ilityT e system s ould !rovide easy, secure, relia(le, and scala(le ways for t eadministrators to install, manage, and maintain t e o!erating system, newsoftware, e9isting software, and !atc es'

C Providing ease of scala(ilityT e system s ould (e scala(le to meet t e ever8increasing !erformancereHuirements of a!!lications' Scala(ility of t e system includes t e ca!a(ility toscale u! (y adding more !rocessors to t e e9isting system or scale out (y addingmore com!uters and faster interconnects' t is im!ortant to understand t escala(ility of t e initial system configuration and ow well it can (e u!graded in t efuture as wor7loads and data volumes increase over time'

C -aving a system t at is fully su!!orted

C ;imiting t e num(er of o!erating systems

C Minimier(eros aut entication, 1ncry!ted PSec communications, andPu(lic >ey nfrastructure @P> A su!!ort'

*


18/69

C ncreased relia(ility wit su!!ort for integrated file and storage services sucas remova(le and ierarc ical storage management, dynamic volumemanagement, file re!lication and distri(uted file system @DFSA'

C /reater availa(ility wit su!!ort for integrated ig availa(ility services suc asclustering, load (alancing and file re!lication services for file servers

Assessing t$e Current .usiness Situation)ou must identify t e ga!s (etween t e current and desired states of your (usiness tocreate a solution t at fulfills t e (usiness goals' Performing a ga! analysis el!s youidentify !ro(lems in t e current (usiness environment and develo! a !at to t e desiredstate of t e (usiness' Different ty!es of (usiness issues t at you need to assess mayinclude#

C ?usiness !olicies

C ?usiness o!erations

C 19isting system !erformance, including downtime im!act

3ision Statement E5am les?ased on t e (usiness !ro(lem e9am!les at t e (eginning of t is section, ere are somesam!le vision statements#

C To ave file, !rint, and directory services running smoot ly and efficiently in aWindows environment'

C To ave file, !rint, and directory services running smoot ly and efficiently in acom(ined Novell and Windows environment'

T e vision statement s ould always address 7ey (usiness !ro(lems in t e organiee! in mind t at t e vision statement

covers w at t e system will loo7 li7e w en you com!lete t e !ro"ect, not ow you get tot at end state'

Creating t$e Solution Conce tT e solution conce!t descri(es at a ig level ow t e solution will solve t e (usiness!ro(lem in terms of a!!roac es it will ta7e to (uild and deliver solutions' T is is t eearliest version of t e functional s!ecification and !lans t at you will develo! in t ePlanning P ase'

T e !ur!ose of t e solution conce!t is to !rovide teams wit limited (ut sufficient detailto#

C Prove t e solution to (e com!lete and correct

C Perform several ty!es of analyses, including feasi(ility studies, ris7 analysis,usa(ility studies, and !erformance analysis t at will el! t e team develo! t e

solution in more detail during t e Planning P ase'C ommunicate t e !ro!osed solution to t e customer and ot er 7ey sta7e olders'

T e foremost Huestion to answer at t is stage is w et er you s ould migrate over time@! ased migrationA or all at once @direct migrationA'

*5


19/69

P$ased vs- /irect Migration)ou need to evaluate t e different levels of im!act a ! ased or a direct migration mig t

ave on your organi


20/69

T is !rocess can only (e !erformed if t ere are no reHuirements to maintain legacyNovell systems and your environment is small enoug or you ave enoug resources tomigrate all of t e wor7stations in t e environment' n addition, all a!!lications must (efully tested (efore migration to verify t at t ere is no longer a reHuirement for a Novellserver'

+etwor) S*stems and Services MigrationW en you reac t e Planning P ase, you will (e a(le to !lan more effectively if you 7noww ic services can (e easily migrated from a given NetWare environment toWindows Server 2003 and w ic tools you can use to !erform a given migration tas7'

Part of your solution conce!t will (e w at version you are currently using and w at yourend environment will (e# a Windows environment or a mi9ed Windows and Novellenvironment' T is section summari


21/69

+/S +ames ace Ma ing

)ou can ma! t e NDS ierarc ical directory names!ace to t e names!ace used inWindows Server 2003 &ctive Directory' -owever, in most circumstances, t e o!timum

&ctive Directory names!ace will not (e t e one used (y NDS' T is dis"ointed ma!!ing is(ecause of differences (etween t e (asic met ods of !artitioning and re!lication'

NDS names!ace ma!!ings t at are similar to an o!timal &ctive Directory names!acemig t occur if a geogra! ic names!ace model is used for &ctive Directory' t is commonfor NDS im!lementations to follow t is model to accommodate !artitioning at t eorgani


22/69

: +etwor) Securit* ' From a ig level, NetWare '9 and later versions !rovide a setof networ7 services t at is similar to &ctive Directory' T ese include su!!ort forsecure soc7ets layer @SS;A, ' 0 digital certificates, and security !olicies' fintero!era(ility (etween security im!lementations is desired, you s ould focus ont e use of SS; and !u(lic 7ey infrastructure @P> A to ensure a good level ofintero!era(ility' ?ot !latforms su!!ort many similar security !olicies suc as

account loc7out, access control, !assword !olicies, etc': +etwor) Partitions ' Wit very few e9ce!tions, do not attem!t to ma7e a direct

correlation (etween NDS !artitions @w ic are disassociated wit names!aceA and!artitions in &ctive Directory t at ma! to DNS domains and names!ace'

/e'ining t$e Sco e o' t$e ProjectT e sco!e of t e !ro"ect starts to ta7e s a!e after t e (usiness goals ave (een defined'For e9am!le, many organi


23/69

Project #imeline & final tas7 to accom!lis (efore t e end of t e 1nvisioning P ase is to !re!are anestimate of t e time frame for t e !ro"ect' t is common for t e goals of t e !ro"ect todictate t e timeline, as a migration can affect ot er critical (usiness !ro"ectde!endencies' &ll timeline decisions are !reliminary at t is !oint, (ut t is early timelinewill (e im!ortant as a (asis for t e !ro"ect sc edule you will !re!are during t e PlanningP ase'

+ne a!!roac to s7etc ing out t e timeline is to start (y setting a com!letion date andt en wor7ing (ac7ward' T is el!s to develo! a range of time t at is availa(le for eac! ase of t e !rocess' 1ven w en t e deadline for t e com!letion of t e !ro"ect is t einfamous (y yesterday, time s ould (e allocated for t e Planning and Sta(ili


24/69

C ?udget constraints

C ;ac7 of in8 ouse e9!ertise and resources for t e !ro"ect

C JPoliticalK issues

C ;ac7 of ardware and software availa(ility

22


25/69

3Planning )our Novell8to8Windows Migration Pro"ect

Introduction and %oalsT e Planning P ase of a !ro"ect is t e time w en t e initial vision is translated into!ractical !lans for ow to ac ieve it' Most of t e activity during t e Planning P aseinvolves ma7ing decisions and documenting t em' T e full !ro"ect team s ould (eengaged at t is !oint' 6eaders s ould consult t e .MP/ for guidance on organi


26/69

C Features and services t at define t e functionality of t e solution

C om!onent s!ecifications t at define t e !roducts t at will (e used to deliverreHuired features and services

C De!endencies on ot er !ro"ects or resources outside t e !ro"ect teamGs control

C T e master !ro"ect !lan and sc edule, w ic descri(es w en eac !iece of t ewor7 will (e done and s ows ow t e wor7 will (e coordinated, ta7ingde!endencies into account'

C &n u!dated ris7 assessment wit management !lans for to! ris7s'

Planning P$ase Major Milestone, Project Plans A rovedT e ! ase concludes w en t e !ro"ect team agrees t at t e !lans are sufficiently well8defined to !roceed wit develo!ment and testing, and t e team, (usiness s!onsor, and7ey sta7e olders a!!rove t e design and t e master !ro"ect !lan and sc edule, usuallyat a milestone meeting' T e formal conclusion is mar7ed (y t e second ma"or !ro"ectmilestone, Pro"ect Plans &!!roved'

Evaluating t$e E5isting Environmentt is critical to fully understand t e current environment (efore designing t e environment

to w ic you !lan to u!grade' &llow time in t e Planning P ase to continue t eassessment wor7 t at you did in t e 1nvisioning P ase (y collecting more detailedinformation a(out t e e9isting environment and evaluating t at information to determinet e a!!ro!riate ne9t ste!s'

T e evaluation !rocess can s ed lig t on constraints to t e im!lementation !rocess t atwerenGt considered !reviously, suc as time restrictions t at would affect t e window ofo!!ortunity for c ange' T ese restrictions can include seasonal (usinesses, com!any(udgeting cycles, or even vacation sc edules'

.ltimately, w ile t e amount of time s!ent in t e assessment and evaluation !rocess will

vary greatly, t e goals are t e same# to understand t e tec nology infrastructure in !laceand t e ris7s involved in t e !ro"ect to limit t e sur!rises t at may occur during t eMigrating and De!loying ! ases'

n !re!aration for develo!ment of t e functional s!ecifications document, t e followingassessment tas7s s ould (e !erformed#

: /iagram t$e networ) including $ardware and so'tware- reate a diagram oft e NetWare networ7 and all of its com!onents' dentify w ic servers are file and!rint servers, We( servers, mail servers, and data(ase servers' T oroug lydocument all servers, including NetWare versions, trans!ort !rotocols, NDS!artitioning, and directory versions @?indery or NDSA'

C /ocument an* rinters t$at need to be re laced ' ec7 !rinters to ensure t att ey can (e !rinted to using !rotocols ot er t an P @ideally T PE PA' nclude any

!rinters t at need to (e re!laced in (udget and timeline estimates': Identi'* all t* es o' in'ormation stored on t$e networ)- dentify all ty!es of

information stored on t e NetWare networ7 @not "ust NDS or ?indery informationA,w ere it is stored, w o is res!onsi(le for w ic information, w ic su(sets of users

ave access to w ic data, and w at t e associated security reHuirements are'

: Identi'* all +ovell;de endent so'tware- &mong t e software in t e diagram,identify all software t at is de!endent on Novell'

24


27/69

: Review WA+4(A+ lin)s7 and t$eir available bandwidt$- Determine t e availa(le(andwidt for W&N and ;&N lin7s' T is will el! you decide ow you caneffectively design t e &ctive Directory to!ology in res!ect to t e current Novell!ortioning on t e e9isting networ7'

: Anal*&e t$e current names ace design- Familiari


28/69

: Plan 'or 'uture $ardware7 so'tware7 and networ) bandwidt$ needs- 6esearcw at additional functionality your organiit# Designing and De!loying Directory and Security Services

tt!#EEwww'microsoft'comEdownloadsEdetails'as!9QFamily DR5 D1511:8 DF*843 4821D82*4: 3& 1??1Vdis!laylangRenUfilelist' ?efore reading t is document, you may

want to familiari


29/69

Windows Server 0112 /esignDetermine t e software version and t e ardware configuration t at will (e used' naddition, (efore de!loying t e servers in a test environment, consider t e use of t ird8!arty a!!lications to !rotect data on t e servers and ma7e a!!ro!riate decisions' T edesign of t e system and t e servers s ould ta7e into account any data !rotectionsoftware @(ac7u!, antivirus, etc'A t at you decide to use'

Active /irector* /esign &ctive Directory is a necessary and fundamental com!onent of anyWindows Server 2003 im!lementation' )ou can use (uilt8in tools to set u! &ctiveDirectory, in addition to Windows Server 2003, as long as you consider a fewstraig tforward design !arameters (efore de!loyment#

Arc$itectureC


30/69

: /!CP ' D- P can (e configured to allow for t e Server service to u!date t eDynamic DNS record for t e client if t at client is una(le to !erform t e u!dateitself' T is o!tion can (e turned on and off at t e server level, t roug t e D- PManager MM ' &dditional design considerations regarding D- P include#

C Migrating e9isting D- P sco!es or recreating t e sco!es

C Placement of D- P servicesCon'iguration

C Active /irector* Site and Re lication #o olog* (a*out ' For !ur!oses ofre!lication, &ctive Directory logically organi


31/69

ManagementC %rou Policies ' W ile /rou! Policy +("ects @/P+sA are a system introduced wit

&ctive Directory, !redecessors to /P+s and com!onents of /P+s are availa(lewit out t e use of &ctive Directory' System !olicies were introduced wit Windows

and Windows NT 4'0 and were used to manage various as!ects of t oseo!erating systems in a Wor7grou! or Domain environment' ;ocal !olicies areavaila(le for Windows 2000, Windows Server 2003, and Windows P com!uterst at are not mem(ers of an &ctive Directory forest'?ecause of t e !otential !resence of ot er !olicy (ased system for systemsmanagement, it is im!ortant to review t e current use of !olicies in yourorganiit Tools!rovide a !owerful toolset for t e creation of login scri!ts'

: Securit* ' Determine t e security reHuirements t at must (e re!licated in t e newenvironment and t e tools or features necessary to accom!lis t e reHuired levelof security'

Wor)stationsT ere are (asically four different o!tions for configuring t e clients#

C P ysically wal7 to every single des7to!, uninstall t e Novell lient32, andrema! to t e Windows client' T is is a manual !rocess t at ta7esa!!ro9imately *08* minutes !er wor7station' f you don t ave a lot ofcom!uters in t e environment, t is may (e t e easiest a!!roac '

C reate a scri!t' T e scri!t uninstalls and t en installs in one !rocess' t can (eim!lemented manually t roug a (atc file or a login scri!t'

C ;aunc a scri!t t roug /rou! Policy' )ou can create a scri!t t at will uninstallt e lient32 and install Windows remotely'

C 6etire lient32 during a ! ased des7to! refres ' ?efore t e client is removed,t e lient32 software remains on t e des7to!, (ut all of t e ma!!ings areremoved' ?asically you remove t e login scri!t from t e Novell system and youuse /rou! Policy and &ctive Directory to do all of t e drive ma!!ings' &t t is!oint t e lient32 is effectively unused, (ut is still !resent' W ile t e refres is

in !rogress, you will still need to maintain a NetWare aut enticationmec anism in !lace so t e user can login, (ut ot erwise &ctive Directory willta7e over t e networ7 login functions'

Many organi


32/69

Migration Planning &fter you ave determined w at your new environment will loo7 li7e, you are ready todetermine ow you will migrate your e9isting environment to t e new environment' T ereare t ree com!onents to !lanning t e migration from Netware to Windows Server 2003#(uilding t e new environment, determining your migration strategy, and determining yourmigration !rocess for moving your e9isting users and data to t e new environment'

.uilding Active /irector*?efore you can migrate you must first (uild t e new Windows &ctive Directoryenvironment' T is section !rovides an overview of t e o!tions for (uilding &ctiveDirectory' For detailed information regarding (uilding &ctive Directory, see t eWindows Server 2003 De!loyment >it# Designing and De!loying Directory and SecurityServices @tt!#EEwww'microsoft'comEdownloadsEdetails'as!9QFamily DR5 D1511:8 DF*843 48 21D82*4: 3& 1??1Vdis!laylangRenUfilelist A'

T e &ctive Directory de!loyment strategy t at you a!!ly will vary according to youre9isting networ7 configuration' For e9am!le, if your organi


33/69

e9isting Windows NT 4'0 domains, see .!grading Windows NT 4'0 Domains toWindows Server 2003 &ctive Directory@tt!#EEwww'microsoft'comEresourcesEdocumentationEWindowsServE2003EallEde!loyguideEen8usEDefault'as!QurlREresourcesEdocumentationEWindowsServE2003EallEde!loyguideEen8usEdss(( over dnrr'as! A'

.!grading your Windows 2000 domains to Windows Server 2003 domains is an efficient,straig tforward way to ta7e advantage of additional Windows Server 2003 features andfunctionality' .!grading from Windows 2000 to Windows Server 2003 reHuires minimalnetwor7 configuration and as little im!act on user o!erations' For more information onu!grading e9isting Windows 2000 domains, see Windows Server 2003.!gradingWindows 2000 Domains to Windows Server 2003 Domains@tt!#EEwww'microsoft'comEresourcesEdocumentationEWindowsServE2003EallEde!loyguideEen8usEDefault'as!QurlREresourcesEdocumentationEWindowsServE2003EallEde!loyguideEen8usEdss(( over dnrr'as! A'

/etermining ?our Migration Strateg*W en develo!ing a migration strategy t ere are a num(er of decisions t at you mustma7e#

C Plan a direct or $ased migration ' Plan an immediate, one8time migration, or a! ased migration over time @sync roni


34/69

A P$ased or /irect Migration@n t e 1nvisioning P ase, you determined w ic ty!e of migration will wor7 (est for your

organi


35/69

W en you introduce Windows Server 2003 and &ctive Directory into an e9isting Novellnetwor7, you can facilitate directory management and im!rove data availa(ility (yesta(lis ing directory intero!era(ility' entral to intero!era(ility is t e ca!a(ility tosync roni


36/69

Migration tools !rovide t e ca!a(ility to automate t e migration of information (y usinge9isting NetWare settings to decrease t e time s!ent on t e migration' .sing migrationtools, owever, and factoring in t eir sometimes significant cost, may not always (enecessary, !articularly in situations w ere#

C T ere is little configuration investment in access control lists @& ;sA or useraccount information in t e Novell environment

C T e information stored in t e Novell environment is not accurate or current

C T e num(er of o("ects or files is so small t at it is not wort t e time to install,learn, and use t e migration tools

f one of more of t ese situations descri(es your networ7 environment, consider a manualmigration'

-owever, if you ave a significant configuration investment, your Novell environment isu!8to8date, and you ave a large num(er of o("ects and files to migrate, migration toolsmay (e el!ful in t e migration !rocess'

Manual Migration

f you c oose manual migration, you will need to re8enter user account information andEor reset file !ermissions manually'

Automated MigrationT is guide focuses on two migration tools# Services for NetWare '03 and Ouest NDSMigrator' For many organi


37/69

C Microso't /irector* S*nc$roni&ation Services ' Microsoft DirectorySync roni


38/69

#able -1, Summar* o' Services 'or +etWare Migration Services

NetWareElement

NetWareVersions

MicrosoftMigration ToolAvailable?

Tool Name

Files NetWare 3.x Yes FMU

NetWare 4.x Yes FMU

NetWare 5.x Yes FMU

Directories NetWare 3.x Yes MSDSS

NetWare 4.x Yes MSDSS

NetWare 5.x Yes MSDSS

NDS 8 Yes MSDSS

n addition to t e tools outlined, Services for NetWare '03 !rovides trou(les ootingsu!!ort t at ena(les you to trou(les oot connectivity !ro(lems, login scri!ts, and!assword sync roni


39/69

Creating t$e


40/69

)our test !lan s ould include#

C Testing sco!e and o("ectives

C Testing met odology

C 6eHuired resources

C dentification of t e features and functions t at are to (e tested

C Testing sc edule

For detailed information on develo!ing a test !lan, see t e reating a Test Plan section of t e Windows Server 2003 De!loyment >it@tt!#EEwww'microsoft'comEresourcesEdocumentationEWindowsServE2003EallEde!loyguideEen8usEDefault'as!QurlREresourcesEdocumentationEwindowsservE2003EallEde!loyguideEen8usE!d!(c test atds'as! A'

Setting " t$e #est EnvironmentSet u! a test la( t at includes a restored co!y of t e ?indery or NDS Server and aWindows Server 2003 domain controller wit t e Novell lient for Windows and t e latestversion of MSDSS'

C nclude e9am!les of current and !lanned client wor7stations in t e la('

C nclude a co!y of t e !roduction NDS structure in t e la('

C nclude co!ies of as many source Novell fileE!rint servers as !ossi(le' ?e sure to!reserve security settings'

C nclude any ot er com!onents t at affect user e9!erience in t e la(, for e9am!le,system !olicies'

C nstall any Novell8de!endent a!!lications in t e test la( and test t eir com!ati(ilitywit your migration !lans'

/evelo ing #est (ab %uidelines and Procedures

.sers of t e test la( need to 7now w en t ey can !erform t eir tests, w et er t eirtesting will disru!t ot er tests, and w at t e current state of t e la( is' )our la( manageror an assigned team mem(er s ould esta(lis a communication system to disseminateinformation a(out t e availa(ility and state of t e test la( and s ould esta(lis guidelinesfor la( use'

/uidelines s ould (e easy to follow and s ould address#

: Roles and res onsibilities ' dentify w o is res!onsi(le for tas7s suc assc eduling test la( use and !erforming (ac7u!s'

:


41/69

: Server initiali&ation rocedures ' Document t e ste!s for installing, configuring,and !o!ulating domain controllers and mem(er servers' nclude DNS settings ifyou do not !lan to use t e DNS Server service in Windows Server 2003'

: #est lab restore rocedures 'or testing t$e rollout ' Document t e ste!s forrestoring domain controllers to t eir original state and for refres ing user accountdata' Document all server configurations' Test t e refres !rocess (efore you(egin migration testing'

: Client com uter restore rocedures- f you !lan to re(uild client com!utersfreHuently to test various configurations, document t e tools reHuired to Huic7lyrestore t e com!uters to a 7nown state' For e9am!le, if you use 6 S, note t is inyour guidelines'

&s !art of t e la( guidelines and !rocedures, t e la( manager or an a!!ointed teammem(er also s ould develo! an escalation !lan and an incident8trac7ing system'

3


42/69

Part 2# ?. ;D

4*


43/69

4Migrating# Prototy!ing t eMigration toWindows Server 2003

Introduction and %oalsT e !ur!ose of t e Develo!ing P ase @or Migrating P ase in t is documentA is to (uild,validate, and test t e design and migration !rocess in an isolated non!roductionenvironment' T is ! ase is a critical ste! in an effective migration strategy, as t ema"ority of !ro(lems can (e uncovered w en testing t e migration !rocess' t is muc(etter to uncover issues in t is ! ase t an w en t ey affect !roduction users and(usiness !rocesses'

Major #as)s and /eliverablesT e Develo!ing P ase tas7s t at are relevant to migration !ro"ects are#

C Testing t e design and migration !rocess

C 6esolving issues t at are identified during t e testing !rocess

T e content of t is section !rovides t e tec nical information needed to ena(le teams toaccom!lis t ese tas7s' 6efer to t e .MP/ for general !ro"ect guidance on ow teammem(ers and wor7 !rocesses s ould (e organi


44/69

#esting t$e /esign and Migration Processn t e Planning P ase, t e team develo!ed a design, migration strategy, and a test !lan'

T e Migrating P ase uses t e !arameters outlined t e Test Plan to test and validate t edesign configuration and migration !rocesses in t e isolated test environment'

alidation testing s ould include t e following ste!s#

C Sync roni


45/69

For environments w ic will (e u!grading from an e9isting Windows NT 4'0 domainstructure or Windows 2000 &ctive Directory forest, t e !rocess is more involved and!otentially im!actful to end users' T is ty!e of migration !rocess s ould (e carefullydesigned, documented, !rototy!ed, !iloted, and im!lemented on its own (efore it will (ea fully develo!ed Windows Server 2003 &ctive Directory environment' For moreinformation on u!grading to &ctive Directory see Windows Server 2003 De!loyment >it#Designing and De!loying Directory and Security Services@tt!#EEwww'microsoft'comEdownloadsEdetails'as!9QFamily DR5 D1511:8 DF*843 48

21D82*4: 3& 1??1Vdis!laylangRenUfilelist A'

/irect MigrationNow t at you ave esta(lis ed t e new !latform, you can test t e migration !rocess tot e new environment' T e ste!s for t e direct migration !rocess are#

*' ?uild new Windows 2003 Server infrastructure

2' ?uild &ctive Directory

3' nstall MSDSS

4' Migrate users, grou!s, and files

' Migrate !rinters

5' Migrate wor7stations'

P$ased Migration

Manual Migrationf your team selected a manual migration !rocess during t e Planning P ase, you ave

removed a certain degree of com!le9ity from t e !rocess, (ecause a manual a!!roacdoes not migrate e9isting users, grou!s, and file !ermission structures'

Setting u! a !rototy!e using t e manual migration !rocess consists of t e following 7eyste!s#

C dentify t e sam!le data t at will (e migrated' T is may consist of a server or asingle NetWare volume'

C reate test users and necessary accounts'

C reate eHuivalent users and grou!s in &ctive Directory to matc t e old .sers and/rou!s in NetWare'

C Migrate a s!ecific set of File data from NetWare file servers to &ctive Directory fileservers, using sim!le co!y tec niHues'

C &!!ly NTFS security to t e migrated data, eit er manually or wit a utility suc as& ;S, w ic will allow for a scri!ted a!!lication of file !ermissions'

C Migrate client functionality for t e test users, eit er t roug a manual removal oft e lient32 software, or a modification of t e e9isting login scri!ts to ma! t e

migrated volume or server to its new location in &ctive Directory' n addition, t eclients must (e configured to login using t eir new &ctive Directory user names'

4
http://www.microsoft.com/downloads/details.aspx?FamilyID=6CDE6EE7-5DF1-4394-92ED-2147C3A9EBBE&displaylang=en#filelisthttp://www.microsoft.com/downloads/details.aspx?FamilyID=6CDE6EE7-5DF1-4394-92ED-2147C3A9EBBE&displaylang=en#filelisthttp://www.microsoft.com/downloads/details.aspx?FamilyID=6CDE6EE7-5DF1-4394-92ED-2147C3A9EBBE&displaylang=en#filelisthttp://www.microsoft.com/downloads/details.aspx?FamilyID=6CDE6EE7-5DF1-4394-92ED-2147C3A9EBBE&displaylang=en#filelist


46/69

Automated Migration b* "sing Services 'or +etWare 8-12f your organi


47/69

' +n t e &ctive Directory ontainer and Domain ontroller !age, ty!e t e !at to t e &ctive Directory container in w ic you want to co!y items, or (rowse to it'

Ty!e t e !at , using t e synta9 in t e following e9am!le#

;D&P#EE+.RSales,D RServer*,D RWingti!,D Rcom

&ll su(containers in t e selected containers will (e co!ied'

5' .nder Domain ontroller, acce!t t e default domain controller in w ic you want tostore t e migration log, or clic7


48/69

' Select t e source volume and target location'

5' 1na(le logging'

:' lic7 Scan to c ec7 w et er t e target source and roots are valid'

=' +n t e last screen, clic7 Migrate ' T e logs will (e dis!layed as t e file data and!ermissions are migrated'

Automated Migration b* "sing BuestT e Ouest NDS Migrator tools allow for t e same ty!e of directory sync roni


49/69

4' Detect NDS to &ctive Directory collisions' Ouest NDS Migrator can determine ifaccounts t at are to (e migrated will collide wit an &ctive Directory account'

' Migrate o("ects'

+ote, T e ste!s to migrate from a !ure Novell environment versus a mi9ed Novell andWindows environment are t e same' -owever, configuration settings will differ' See t eOuest NDS Migrator .serGs /uide for configuration settings'

Password S*nc$roni&ation &fter t e test users ave (een migrated, t eir !asswords need to (e sync roni


50/69

Sta(ili


51/69

Conducting t$e PilotW en t e design com!onents and migration !rocess ave (een fully tested in t eisolated environment, it is time to introduce t em in t e !roduction environment as !art of a !ilot' T ere are t ree ma"or ste!s to conducting t e !ilot# (uilding t e new serverstructure, setting u! sync roni


52/69

Automated Migration "sing BuestFollow t e !rototy!e ste!s wit t e !ilot users and !ilot data'

C nstalling Ouest NDS Migrator

C .sing Ouest NDS Migrator

Password S*nc$roni&ationFollow t e !rototy!e ste!s wit t e !ilot users and !ilot data'


53/69

Part 3# D1P;+)


54/69

5De!loying t e Novell toWindows Server 2003Migration Solution

Introduction and %oalsDuring t is final ! ase of your Novell to Windows Server 2003 migration, t e goal is tode!loy t e solution to all of t e remaining file data and users t at were not included in t e!ilot' T e team will (e following t e !lan t at was develo!ed during t e Planning P aseand tested during t e !rototy!e and !ilot' T is !lan may ave (een u!dated as t e!ro"ect !rogressed'

n certain cases, t e final ! ase of t e !ro"ect will (e s!read over a !eriod of time, w eret e migration of a single server as !art of t e !ilot rolls into t e migration of a secondserver, and t en a t ird, and so on until t e entire set of data is migrated into t e!roduction environment' n ot er cases, a !ilot migration of data will (e followed (y aone8time full de!loyment and t e removal of t e lient32 from user des7to!s over a longwee7end' W ic ever met od you c oose, t e !rocess is effectively t e same' T emigration met od, eit er wit tools or manually, involves moving t e file data from t eNovell NetWare volumes to Windows s ares and rema!!ing clients to !oint to t e newdata location'

Major #as)s and /eliverablesTas7s in t e De!loying P ase include#

C om!leting de!loyment !re!arations

C De!loying t e solution in t e !roduction environment

C Sta(ili


55/69

&fter t e de!loyment, t e team conducts a !ro"ect review and a customer satisfactionsurvey' T e team may continue wit sta(ili


56/69

ust as you did during t e Pilot ! ase, t e file migration !rocess can (egin for t eremainder of t e data in t e server to!ology' ?e sure to allow enoug time for t emigration !rocess to ta7e !lace, eit er ! ased over a !eriod of time or over a longwee7end' +nce again, t e ig 8level migration ste!s are as follows#

*' 1sta(lis volume ma!!ings

2' Set t e Files Migration +!tions3' Migrate files

4' ec7 logs for file migration errors

' 6esolve migration errors

&fter all file data as (een migrated, t e sync roni


57/69

Part 4# +P16&T1


58/69

:+!erating )ourWindows Server 20031nvironment

Introduction and %oalsT is section addresses t e need to o!erate a Windows Server 2003 environment aftert e migration !ro"ect as (een com!leted' Muc of t e detailed guidance can (e found ine9isting documentation @see Windows Server 2003 +!erations

tt!#EEwww'microsoft'comEtec netE!rodtec nolEwindowsserver2003Eo!erationsEdefault'ms!9 A' 6eference to s!ecific sources are made t roug out t is section' T e guidance!rovided in t is c a!ter su!!lements t is documentation and addresses t e areas ofWindows Server 2003 management and maintenance'

Managing Windows Server 0112Windows Server 2003 systems are now t e eart of your T infrastructure' T ese serversneed to (e managed and maintained to 7ee! t e (usiness running o!timally' Servermanagement and maintenance el! ma9imi


59/69

Managing .ased on Server RolesWindows Server 2003 systems can !artici!ate in various res!onsi(ilities in a givennetwor7 environment' Some of t ese res!onsi(ilities may (e intertwined (ecause of(udget constraints, (usiness reHuirements, or tec nical "ustifications' No matter ow t eroles and res!onsi(ilities are defined in t e environment, it is im!ortant to manage t ema!!ro!riately (ased on t e roles of t e server' T e management as!ects for some of t eroles t at Windows Server 2003 can underta7e are defined as follows#

C


60/69

auditing could !otentially slow server !erformance' &lso, collecting lots of information isonly as useful as t e evaluation of t e audit logs' n ot er words, if a lot of information isca!tured and a significant amount of effort is reHuired to evaluate t ose audit logs, t ew ole outcome of auditing is not as effective' &s a result, itGs im!ortant to ta7e t e time to!ro!erly !lan ow t e system will (e audited' T is allows t e administrator to determinew at needs to (e audited, and w y, wit out creating an a(undance of over ead'

&udit !olicies can trac7 successful or unsuccessful event activity in aWindows Server 2003 environment' T e ty!es of events t at can (e monitored include#

C Account logon events ' 1ac time a user attem!ts to log on, t e successful orunsuccessful event can (e recorded' Failed logon attem!ts can include logonfailures for un7nown user accounts, time restriction violations, e9!ired useraccounts, insufficient rig ts for t e user to log on locally, e9!ired account!asswords, and loc7ed8out accounts'

C Account management ' W en an account is c anged, an event can (e logged andlater e9amined'

C /irector* service access ' &ny time a user attem!ts to access an &ctive Directoryo("ect t at as its own system access control list @S& ;A, t e event is logged'

C (ogon events ' ;ogons over t e networ7 or (y services are logged'C Object access ' T e o("ect access !olicy logs an event w en a user attem!ts to

access a resource @for e9am!le, a !rinter or s ared folderA'

C Polic* c$ange ' 1ac time an attem!t to c ange a !olicy @user rig ts, accountaudit !olicies, trust !oliciesA is made, t e event is recorded'

C Privileged use ' Privileged use is a security setting and can include a userem!loying a user rig t, c anging t e system time, and more' Successful orunsuccessful attem!ts can (e logged'

C Process trac)ing ' &n event can (e logged for eac !rogram or !rocess t at auser launc es w ile accessing a system' T is information can (e very detailed andta7e a significant amount of resources'

C S*stem events ' T e system events !olicy logs s!ecific system events, suc as acom!uter restart or s utdown'

T e audit !olicies can (e ena(led or disa(led t roug t e local system !olicy, domaincontroller security !olicy, or /rou! Policy o("ects' &udit !olicies are located wit in t e

om!uter onfigurationXWindows SettingsXSecurity SettingsX;ocal PoliciesX&udit Policyfolder'

"sing Microso't O erations Manager to Sim li'*ManagementMicrosoft +!erations Manager @M+MA is an enter!rise8class monitoring and managementsolution for Windows environments' t is designed to sim!lify Windows management (yconsolidating events, !erformance data, alerts, and more into a centrali


61/69

Kee ing u wit$ Service Pac)s and " datesService !ac7s and u!dates for (ot t e o!erating system and a!!lications are vital !artsof maintaining availa(ility, relia(ility, !erformance, and security' Microsoft !ac7ages t eseu!dates into service !ac7s or individually' T ere are several ways an administrator canu!date a system wit t e latest service !ac7 or u!date# D86+M, manually enteredcommands, Windows .!date, or Microsoft Software .!date Server @S.SA'

+ote, T oroug ly test and evaluate service !ac7s and u!dates in a la( environment(efore installing t em on !roduction servers and client com!uters' &lso, install t ea!!ro!riate service !ac7s and u!dates on eac !roduction server and client com!uterto 7ee! all systems consistent'

Windows " dateWindows .!date is a We( site t at scans a local system and determines w et er t ereare u!dates to a!!ly to t at system' Windows .!date is a great way to u!date individual

systems, (ut t is met od is sufficient for only a small num(er of systems' fadministrators c ose t is met od to u!date an entire organi


62/69

C 3eri'*ing t$at .ac)u s are Success'ul- To !rovide a more secure and fault8tolerant organi


63/69

Wee)l* MaintenanceMaintenance !rocedures t at reHuire slig tly less attention t an daily c ec7ing arecategori


64/69

Mont$l* Maintenancet is recommended t at you !erform t e tas7s outlined in t e section on a mont ly (asis'

C Maintaining DS> automatically at startu!' &dministrators canmaintain F&T, F&T32, and NTFS file system integrity (y running ->DS> once amont or during regular server maintenance cycles' For more information on t e

->DS> utility, see 7ds7@tt!#EEwww'microsoft'comEresourcesEdocumentationEWindowsServE2003EstandardE!roddocsEen8usEDefault'as!QurlREresourcesEdocumentationEWindowsServE2003EstandardE!roddocsEen8usEc 7ds7'as! A'

C #esting t$e "PS ' &n uninterru!ti(le !ower su!!ly @.PSA s ould (e used to !rotectt e system or grou! of systems from !ower failures @suc as s!i7es and surgesAand 7ee! t e system running long enoug after a !ower outage so t at anadministrator can gracefully s ut down t e system' t is recommended t at anadministrator follow t e .PS guidelines !rovided (y t e manufacturer at least once

a mont ' &lso, mont ly sc eduled (attery tests s ould (e !erformed' Many t ird8!arty .PS !roducts automate t is ty!e of functionality, or you can develo! scri!tsto run t is as well'

C 3alidating .ac)u s ' +nce a mont , an administrator s ould validate (ac7u!s (yrestoring t e (ac7u!s to a server located in a la( environment' T is is in addition toverifying t at (ac7u!s were successful from log files or t e (ac7u! !rogramGsmanagement interface' & restore gives t e administrator t e o!!ortunity to verifyt e (ac7u!s and to !ractice t e restore !rocedures t at would (e used w enrecovering t e server during a real disaster' n addition, t is !rocedure tests t estate of t e (ac7u! media to ensure t at t ey are in wor7ing order and (uildsadministrator confidence for recovering from a true disaster'

C " dating Automated S*stem Recover* Sets ' &utomated System 6ecovery@&S6A is a recovery tool t at s ould (e im!lemented in all Windows Server 2003

environments' t (ac7s u! t e system state data, system services, and all volumescontaining Windows Server 2003 system com!onents' &S6 re!laces t e1mergency 6e!air Dis7s @16DsA used to recover systems in earlier versions ofWindows Server'

&fter (uilding a server and any time a ma"or system c ange occurs, t e &S6 sets@t at is, t e (ac7u! and flo!!y dis7A s ould (e u!dated' &not er (est !ractice is tou!date &S6 sets at least once a mont ' T is 7ee!s content in t e &S6 setsconsistent wit t e current state of t e system' +t erwise, valua(le systemconfiguration information may (e lost if a system e9!eriences a !ro(lem or failure'

For more information on &S6, see -ow &S6 Wor7s@tt!#EEwww'microsoft'comEresourcesEdocumentationEWindowsServE2003EallEde!loyguideEen8usEDefault'as!QurlREresourcesEdocumentationEwindowsservE2003EallEde!loyguideEen8usEsdc(c sto a9 o'as! A'

C " dating /ocumentation ' &n integral !art of managing and maintaining any Tenvironment is to document t e networ7 infrastructure and !rocedures' Forassistance in u!dating documentation see t e o( &id, Wor7s eet &'*2 .!datingNetwor7 Documentation in t e Windows Server 2003 De!loyment >it@tt!#EEgo'microsoft'comEfwlin7EQ;in7 dR*44:* A'
http://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/chkdsk.asphttp://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/chkdsk.asphttp://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/chkdsk.asphttp://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/chkdsk.asphttp://www.microsoft.com/resources/documentation/WindowsServ/2003/all/deployguide/en-us/Default.asp?url=/resources/documentation/windowsserv/2003/all/deployguide/en-us/sdcbc_sto_axho.asphttp://www.microsoft.com/resources/documentation/WindowsServ/2003/all/deployguide/en-us/Default.asp?url=/resources/documentation/windowsserv/2003/all/deployguide/en-us/sdcbc_sto_axho.asphttp://www.microsoft.com/resources/documentation/WindowsServ/2003/all/deployguide/en-us/Default.asp?url=/resources/documentation/windowsserv/2003/all/deployguide/en-us/sdcbc_sto_axho.asphttp://www.microsoft.com/resources/documentation/WindowsServ/2003/all/deployguide/en-us/Default.asp?url=/resources/documentation/windowsserv/2003/all/deployguide/en-us/sdcbc_sto_axho.asphttp://go.microsoft.com/fwlink/?LinkId=14471http://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/chkdsk.asphttp://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/chkdsk.asphttp://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/chkdsk.asphttp://www.microsoft.com/resources/documentation/WindowsServ/2003/all/deployguide/en-us/Default.asp?url=/resources/documentation/windowsserv/2003/all/deployguide/en-us/sdcbc_sto_axho.asphttp://www.microsoft.com/resources/documentation/WindowsServ/2003/all/deployguide/en-us/Default.asp?url=/resources/documentation/windowsserv/2003/all/deployguide/en-us/sdcbc_sto_axho.asphttp://www.microsoft.com/resources/documentation/WindowsServ/2003/all/deployguide/en-us/Default.asp?url=/resources/documentation/windowsserv/2003/all/deployguide/en-us/sdcbc_sto_axho.asphttp://go.microsoft.com/fwlink/?LinkId=14471


65/69

Buarterl* Maintenance &s t e name im!lies, Huarterly maintenance is !erformed four times a year' &reas tomaintain and manage on a Huarterly (asis are ty!ically self8sufficient and self8sustaining'

nfreHuent maintenance is reHuired to 7ee! t e system ealt y' T is doesnGt mean,owever, t at t e tas7s are sim!le or t at t ey arenGt as critical as t ose tas7s t at reHuire

more freHuent maintenance'

C C$ec)ing Storage (imits ' Storage ca!acity on all volumes s ould (e c ec7ed toensure t at all volumes ave am!le free s!ace' >ee! a!!ro9imately 2 !ercentfree s!ace on all volumes'

C C$anging Administrator Passwords ' &dministrator !asswords s ould, at aminimum, (e c anged every Huarter @ 0 daysA' anging t ese !asswordsstrengt ens security measures so t at systems canGt easily (e com!romised' naddition to c anging !asswords, ot er !assword reHuirements suc as !asswordage, istory, lengt , and strengt s ould (e reviewed'

C Maintaining t$e Active /irector* /atabase ' &ctive Directory is t e eart of t eWindows Server 2003 environment' +("ects suc as users, grou!s, +.s, andmore can (e added, modified, or deleted from t e &ctive Directory data(ase' T isinteraction wit t e data(ase can cause fragmentation' Windows Server 2003!erforms online defragmentation nig tly to reclaim s!ace in t e &ctive Directorydata(ase owever, t e data(ase si


66/69

&6eferences and ?i(liogra! yC Windows Server 2003 De!loyment >it# Designing and De!loying Directory and

Security Services tt!#EEwww'microsoft'comEdownloadsEdetails'as!9QFamily DR5 D1511:8 DF*843 48 21D82*4: 3& 1??1Vdis!laylangRenUfilelist

C NetWare to Windows Server 2003 Migration Planning /uide

tt!#EEwww'microsoft'comEwindowsserver2003Etec infoEoverviewEsfnmig'ms!9C Microsoft Windows Storage Server 2003

tt!#EEwww'microsoft'comEwindowsserversystemEwss2003Edefault'ms!9

C Windows Servers in a Storage &rea Networ7 1nvironmenttt!#EEwww'microsoft'comEwindowsserversystemEwss2003Etec infoE!lande!loyEmss

ans'ms!9

C Microsoft Windows Services for NetWare Tec nology entertt!#EEwww'microsoft'comEwindowsserver2003EsfnEdefault'ms!9

C Microsoft Windows Services for NetWare '03 +verview

tt!#EEwww'microsoft'comEwindowsserver2003Etec infoEoverviewEsfncd'ms!9

C MSDSS Tec nical +verview

tt!#EEwww'microsoft'comEwindows2000EsfnEmsdss'as!C -ow to Migrate or De!loy a Novell NetWare 1nvironment to Windows

tt!#EEsu!!ort'microsoft'comE7(EH2:42: E

C NetWare &dd8on Servicestt!#EEwww'microsoft'comEntserverEtec resourcesEintero!EnetwareE&ddonServices'a

s!

C Microsoft +!erations Manager 200tt!#EEwww'microsoft'comEtec netE!rodtec nolEmomEmom200 Edefault'ms!9

C DcDiag'e9e# Domain ontroller Diagnostic Tooltt!#EEwww'microsoft'comEwindows2000Etec infoEres7itEtoolsEnewEdcdiag8o'as!

C 7ds7tt!#EEwww'microsoft'comEresourcesEdocumentationEWindowsServE2003EstandardE!

roddocsEen8usEDefault'as!QurlREresourcesEdocumentationEWindowsServE2003EstandardE!roddocsEen8usEc 7ds7'as!

C -ow &S6 Wor7stt!#EEwww'microsoft'comEresourcesEdocumentationEWindowsServE2003EallEde!loyg

uideEen8usEDefault'as!QurlREresourcesEdocumentationEwindowsservE2003EallEde!loyguideEen8usEsdc(c sto a9 o'as!
http://www.microsoft.com/downloads/details.aspx?FamilyID=6CDE6EE7-5DF1-4394-92ED-2147C3A9EBBE&displaylang=en#filelisthttp://www.microsoft.com/downloads/details.aspx?FamilyID=6CDE6EE7-5DF1-4394-92ED-2147C3A9EBBE&displaylang=en#filelisthttp://www.microsoft.com/windowsserver2003/techinfo/overview/sfnmig.mspxhttp://www.microsoft.com/windowsserversystem/wss2003/default.mspxhttp://www.microsoft.com/windowsserversystem/wss2003/techinfo/plandeploy/mssans.mspxhttp://www.microsoft.com/windowsserversystem/wss2003/techinfo/plandeploy/mssans.mspxhttp://www.microsoft.com/windowsserver2003/sfn/default.mspxhttp://www.microsoft.com/windows2000/sfn/msdss.asphttp://support.microsoft.com/kb/q274279/http://www.microsoft.com/ntserver/techresources/interop/netware/AddonServices.asphttp://www.microsoft.com/ntserver/techresources/interop/netware/AddonServices.asphttp://www.microsoft.com/technet/prodtechnol/mom/mom2005/default.mspxhttp://www.microsoft.com/windows2000/techinfo/reskit/tools/new/dcdiag-o.asphttp://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/chkdsk.asphttp://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/chkdsk.asphttp://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/chkdsk.asphttp://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/chkdsk.asphttp://www.microsoft.com/resources/documentation/WindowsServ/2003/all/deployguide/en-us/Default.asp?url=/resources/documentation/windowsserv/2003/all/deployguide/en-us/sdcbc_sto_axho.asphttp://www.microsoft.com/resources/documentation/WindowsServ/2003/all/deployguide/en-us/Default.asp?url=/resources/documentation/windowsserv/2003/all/deployguide/en-us/sdcbc_sto_axho.asphttp://www.microsoft.com/resources/documentation/WindowsServ/2003/all/deployguide/en-us/Default.asp?url=/resources/documentation/windowsserv/2003/all/deployguide/en-us/sdcbc_sto_axho.asphttp://www.microsoft.com/resources/documentation/WindowsServ/2003/all/deployguide/en-us/Default.asp?url=/resources/documentation/windowsserv/2003/all/deployguide/en-us/sdcbc_sto_axho.asphttp://www.microsoft.com/downloads/details.aspx?FamilyID=6CDE6EE7-5DF1-4394-92ED-2147C3A9EBBE&displaylang=en#filelisthttp://www.microsoft.com/downloads/details.aspx?FamilyID=6CDE6EE7-5DF1-4394-92ED-2147C3A9EBBE&displaylang=en#filelisthttp://www.microsoft.com/windowsserver2003/techinfo/overview/sfnmig.mspxhttp://www.microsoft.com/windowsserversystem/wss2003/default.mspxhttp://www.microsoft.com/windowsserversystem/wss2003/techinfo/plandeploy/mssans.mspxhttp://www.microsoft.com/windowsserversystem/wss2003/techinfo/plandeploy/mssans.mspxhttp://www.microsoft.com/windowsserver2003/sfn/default.mspxhttp://www.microsoft.com/windows2000/sfn/msdss.asphttp://support.microsoft.com/kb/q274279/http://www.microsoft.com/ntserver/techresources/interop/netware/AddonServices.asphttp://www.microsoft.com/ntserver/techresources/interop/netware/AddonServices.asphttp://www.microsoft.com/technet/prodtechnol/mom/mom2005/default.mspxhttp://www.microsoft.com/windows2000/techinfo/reskit/tools/new/dcdiag-o.asphttp://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/chkdsk.asphttp://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/chkdsk.asphttp://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/chkdsk.asphttp://www.microsoft.com/resources/documentation/WindowsServ/2003/all/deployguide/en-us/Default.asp?url=/resources/documentation/windowsserv/2003/all/deployguide/en-us/sdcbc_sto_axho.asphttp://www.microsoft.com/resources/documentation/WindowsServ/2003/all/deployguide/en-us/Default.asp?url=/resources/documentation/windowsserv/2003/all/deployguide/en-us/sdcbc_sto_axho.asphttp://www.microsoft.com/resources/documentation/WindowsServ/2003/all/deployguide/en-us/Default.asp?url=/resources/documentation/windowsserv/2003/all/deployguide/en-us/sdcbc_sto_axho.asp


67/69

C Windows Server 2003 +!erationstt!#EEwww'microsoft'comEtec netE!rodtec nolEwindowsserver2003Eo!erationsEdefa

ult'ms!9

C Ouest NDS Migrator For more information on Ouest NDS Migrator, visit us at

tt!#EEwm'Huest'comE!roductsEndsmigrator or contact your local sales office (yaccessing tt!#EEwww'Huest'comEa(outEa(out us'as! '

Ouest Windows Management delivers software !roducts in t ree areas# &ctiveDirectory, 19c ange, and Windows' n eac of t ese areas, Ouest !rovidescom!re ensive ca!a(ilities to el! you administer, migrate, re!ort, recover andaudit using secure !rocesses' To read more, access t e Ouest Solutions forWindows Management data s eet for more information'

oose w at you are interested in#

C &ctive Directory

C 19c ange

C Windows

C Migration

+r, go to &ll Products to (rowse t e com!lete list of Ouest Windows Management!roducts and t eir descri!tions'
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/operations/default.mspxhttp://www.microsoft.com/technet/prodtechnol/windowsserver2003/operations/default.mspxhttp://wm.quest.com/products/ndsmigratorhttp://www.quest.com/about/about_us.asphttp://wm.quest.com/library/getdocument.asp?target=qswmhttp://wm.quest.com/library/getdocument.asp?target=qswmhttp://wm.quest.com/products/activedirectory/http://wm.quest.com/products/exchange/http://wm.quest.com/products/windows/http://wm.quest.com/products/migration/http://wm.quest.com/products/allproducts/http://wm.quest.com/products/allproducts/http://www.microsoft.com/technet/prodtechnol/windowsserver2003/operations/default.mspxhttp://www.microsoft.com/technet/prodtechnol/windowsserver2003/operations/default.mspxhttp://wm.quest.com/products/ndsmigratorhttp://www.quest.com/about/about_us.asphttp://wm.quest.com/library/getdocument.asp?target=qswmhttp://wm.quest.com/library/getdocument.asp?target=qswmhttp://wm.quest.com/products/activedirectory/http://wm.quest.com/products/exchange/http://wm.quest.com/products/windows/http://wm.quest.com/products/migration/http://wm.quest.com/products/allproducts/


68/69

&((reviations#able 0-1, Abbreviation /e'initions

Abbreviation /e'inition

& ; &ccess ontrol ;og

&S6 &utomated System 6ecovery

? +S ?asic n!utE+ut!ut System

D Domain ontroller

DFS Distri(uted File System

D- P Dynamic -ost onfiguration Protocol

DNS *' Domain Name System

2' Domain Name Service

16D 1mergency 6e!air Dis7

F&T File &llocation Ta(le

FM. File Migration .tility

FTP File Transfer Protocol

/P+ /rou! Policy +("ect

/. /ra! ic .ser nterface

-TTP -y!erte9t Transfer Protocol

P nternet Protocol

P nternetwor7 Pac7et e c ange

T nformation Tec nology

;&N ;ocal &rea Networ7

;D&P ;ig tweig t Directory &ccess Protocol

M+M Microsoft +!erations Manager

MSF Microsoft Solutions Framewor7

MSDSS Microsoft Directory Sync roniey nfrastructure

6+ 6eturn on nvestment


69/69

S&N Storage &rea Networ7

SfN Services for NetWare

S;& Service ;evel &greement

SMTP Sim!le Mail Transfer Protocol

SS; Secure Soc7et ;ayer

S.S Software .!date Service

T + Total ost of +wners i!

T PE P Transmission ontrol ProtocolE nternet Protocol

.N .niversal Naming onvention

.PS .ninterru!ti(le Power Su!!ly

.MP/ .N Migration Pro"ect /uide

PN irtual Private Networ7

W&N Wide &rea Networ7

W NS Windows nternet Naming Service

Documents

Solution for Migrating From Novell Netware to Windows Server 2003