Project PHOENIXMoving to Microsoft Server 2008 R2 Active

DirectoryProgress report to the

IT Steering CommitteeJune 24, 2011

Agenda:

1. What is Project Phoenix2. Objectives3. What’s been done4. Next steps5. Questions

What is Project Phoenix?

It’s a feasibility study.

“Replace Novell Netware with

Microsoft Active Directory (AD)”

Objectives

• Identify campus needs• Articulate a mission/vision• Gain MS AD Technical proficiency• Define an AD structure• Test the structure and service delivery• Recommendations to the Executive

Director, I.T. Services

What is Project Phoenix?

• What it is: replace Novell Netware with Microsoft Active Directory (AD)

• Why are we doing this? Novell Netware – end of life cycle Active Directory is emerging as a

leader in Directory Services Most new products on the market

work in Active Directory

What is Project Phoenix?• What it is: replacing Novell Netware with Microsoft Active

Directory (AD)• Why are we doing this?

• NDS – end of life cycle• Active Directory is emerging standard• Most new products on the market work in Active Directory

Who is involved:• LAN team – Kelvin, Sylvia, Peter and Adrian• “ADPostles” – technicians across campus

who have, may, or are using Active Directory• I.T. Services staff – identity management,

dns services, virtual server admins, etc. – all have a role.

• Campus community

What is Project Phoenix?• What it is: replacing Novell Netware with Microsoft Active

Directory (AD)• Why are we doing this?

• NDS – end of life cycle• Active Directory is emerging standard• Most new products on the market work in Active Directory

• Who is involved:• LAN team – Kelvin, Sylvia, Peter and Adrian• ADPostles – technicians across campus who have, may, or are using

AD• Relevant I.T. Services staff• Campus Community

• TimeLine:Completed report to Executive Director by September, 2011.

What’s been done …• Staff training – CBT’s throughout 2011. Lab

experience.• Selection of a consultant – March 22, 2011• Review of existing I.T environment, physical

network, etc. – April 15, 2011• Consultant engagement – on-campus presence

– April to May, 2011 (9 days). Report received May 16, 2011

• Test lab setup – two phases– Phase 1 – individual Virtual Machines

Next steps• Test lab setup – two phases

– Phase 1 – individual Virtual Machines (end of June, 2011). Meeting with Metafore in early July.

– Phase 2 – testing our “final” structure throughout July, early August 2011. Final meeting with Metafore in early August.

• Poll campus to fine tune requirements – June to July, 2011

• Governance – meetings with “ADPostles” - fine tune policies/procedures – June to July, 2011

• Writing the report – August, 2011• Final report – September 1, 2011• And then …

Questions?