Windows 2000 Presidents Office/Office of General Counsel Domain Server/Workstation upgrade and...

Windows 2000

President’s Office/Office of General Counsel

Domain Server/Workstation upgrade and implementation report

Date: 3-7-02

Presenter: Tom Merriam

Contact info: tmerriam@asu.edu

The Environment

6 printers

Presofcnt

NT Domain Popresofc

32 PCs

9x/NT/w2k

29 Users

The Environment

6 printers

Presofcnt

NT Domain Popresofc

32 PCs

9x/NT/w2k

29 Users

•Presofcnt = file/Print Server

The Environment

6 printers

Presofcnt

NT Domain Popresofc

32 PCs

9x/NT/w2k

29 Users

•Presofcnt = file/Print Server

•2 Depts: President’s Office and Office of General Counsel

The Environment

6 printers

Presofcnt

NT Domain Popresofc

32 PCs

9x/NT/w2k

29 Users

•Presofcnt = file/Print Server

•2 Depts: President’s Office and Office of General Counsel

•6 Network printers were shared from Presofcnt, 2 to the President’s Office and 4 to the Office of General Counsel

The Environment

6 printers

Presofcnt

NT Domain Popresofc

32 PCs

9x/NT/w2k

29 Users

•Presofcnt = file/Print Server

•2 Depts: President’s Office and Office of General Counsel

•6 Network printers were shared from Presofcnt, 2 to the President’s Office and 4 to the Office of the General Counsel

•Passwords in this NT domain were usually different than ASURITE passwords

Easy Migration

Easy Migration

1. Able to have both servers on network: moving shares and mapping drives was seamless

Presofcnt Presofc2000

Easy Migration

1. Able to have both servers on network: moving shares and mapping drives was seemless

2. No policies were set up

Presofcnt Presofc2000

Easy Migration

1. Able to have both servers on network: moving shares and mapping drives was seemless

2. No policies were set up

3. No logon scripts or profiles on presofcnt server

Presofcnt Presofc2000

Easy Migration

1. Able to have both servers on network: moving shares and mapping drives was seamless

2. No policies were set up

3. No logon scripts or profiles on presofcnt server

4. Only 1 local security group for each area

Presofcnt Presofc2000

The Objective

6 printers

Presofcnt

32 PCs

9x/NT/w2k

29 Users6 printers

Presofcnt

NT Domain Popresofc

32 PCs

9x/NT/w2k

29 Users

The Objective

6 printers

Presofcnt

NT Domain Popresofc

32 PCs

9x/NT/w2k

29 Users

Create ASURITE OU “ M.PRES “

The Objective

6 printers

Presofcnt

NT Domain Popresofc

32 PCs

9x/NT/w2k

29 Users

Create ASURITE OU “ M.PRES “

Create Sub OU Structure

The Objective

6 printers

Presofcnt

NT Domain Popresofc

32 PCs

9x/NT/w2k

29 Users

Create ASURITE OU “ M.PRES “

Create Sub OU Structure

Presofc2000

The Objective

6 printers

Presofcnt

NT Domain Popresofc

32 PCs

9x/NT/w2k

29 Users

Create ASURITE OU “ M.PRES “

Create Sub OU Structure

Presofc2000

Create Shares and move all files

The Objective

6 printers

Presofcnt

NT Domain Popresofc

32 PCs

9x/NT/w2k

29 Users

Create ASURITE OU “ M.PRES “

Create Sub OU Structure

Presofc2000

Share printers from new server

Create Shares and move all files

The Objective

6 printers

Presofcnt

NT Domain Popresofc

32 PCs

9x/NT/w2k

29 Users

Create ASURITE OU “ M.PRES “

Create Sub OU Structure

Touch every machine: Change workstation Name, join ASURITE, set consistent Admin passwords, local profiles, security, service packs etc.

Presofc2000

Share printers from new server

Create Shares and move all files

The Objective

6 printers

Presofcnt

NT Domain Popresofc

32 PCs

9x/NT/w2k

29 Users

Presofc2000

Create ASURITE OU “ M.PRES “

Create Sub OU Structure

Change users popresofc passwords to the same as ASURITE in order to map to both servers

Share printers from new server

Create Shares and move all files

Touch every machine: Change workstation Name, join ASURITE, set consistent Admin passwords, local profiles, security, service packs etc.

Steps to Success Create Share for all documentation

Steps to Success Create Project Plan Doc with Timeline and due dates

Steps to SuccessCreate Spreadsheet of usernames, shares, printers and

schedule of workstation configuration

Steps to SuccessCreate Step-by-Step Workstation Configuration Checklist,

this will vary for 9x/NT/W2K

Important Issues

• Workstation Configuration

Important Issues

• Workstation Configuration• Computer Names - PO2370052

• Computers should be loaded into AD before you add the workstation so that you don’t have to move them out of the default Computer container into their OUs later

• User profiles – Desktop, Outlook configuration, PrtScn

• Mapped drives to shares on either server

• Passwords to old server were changed to ASURITE passwords for ease of connection

• Set Admin passwords, Service packs, critical upgrades etc.

• Check AD for any errors

Important Issues

• Workstation Configuration

• Publishing Printers in the AD & DNS

Publishing Printers in AD

Publishing Printers in AD

FQDN must be the same as the DNS

record of the Server or the printers will be pruned from the AD

daily

Important Issues

• Workstation Configuration

• Publishing Printers in the AD & DNS

• Map drives to Access DBs

Important Issues

• Workstation Configuration

• Publishing Printers in the AD & DNS

• Map drives to Access DBs

• Scheduling Critical Steps

Windows 2000

President’s Office/Office of General Counsel

Domain Server/Workstation upgrade and implementation report

Date: 3-7-02

Presenter: Tom Merriam

Contact info: tmerriam@asu.edu