0% found this document useful (0 votes)
271 views7 pages

Gap Analysis v1.2

Download as pdf or txt
Download as pdf or txt
Download as pdf or txt
You are on page 1/ 7

Gap Analysis

September 15, 2011


1

Our Understanding & Objective


Our Understanding
Novell eDirectory 8.8 is being used as the directory services for both intranet and internet users, Novell Zenworks for application packaging and deployment services and Novell iPrint solution for printing services Two Microsoft Active Directory forests exist in the current environment for a subset of GenRe users Infoblox appliance based DHCP and DNS services are implemented across the enterprise and these are used by all the 3 directories There are around 45 sites that are serviced by these directories Objective GenRe is making a planning to standardise the directory services to Microsoft Windows 2008 based Active Directory from the existing Novell environment.

Solution Scope
The current scope for Directory services migration includes Jointly validate the Windows 2008 Active Directory design proposed by Quest Deploy & Test the AD Infrastructure within a Lab environment with set of selected pilot users Build AD infrastructure in development, QA and production environment AD Migration of all the selected resources from Novell Users, Computers, Printers, Member servers

Out of scope Design of Windows 2008 AD DS Migration of Applications & LDAP credentials from Novell to AD DS

Quest Proposed Design


Domain Name: GRN.GENRE.COM
Root OU: Top Level OU in the domain, does not contain built in accounts, default AD containers Sub OU Hierarchy: Starting from Country level ,the hierarchy contains Users, Groups, Servers etc,. All servers will be listed under Servers OU.

This design indicating only OU level structure No service accounts defined No other information related to group policies ,computer account naming convection, user log on type ,etc have not provided
4

Requirements
o Detailed Level architecture diagram, including: o Logical and Physical Network topology diagram o Site level Replication diagram o Sub Nets design o DCs and ADCs placement o FSMO roles placement o AD Security groups design o Group Policies design o Print servers placement o Lab Documentation and PoC result for Quest tools like RMAD,NDS migrator o No information about Logon scripts and drive mappings

Requirements
o o o o o o o o o o o Functional Level Discussions DDNS and WINs Discussions RODC & Core Installation Discussions DFS/DFS-R Discussions Delegation of Authority Discussions & Best Practices Load balance and failover model DR Concerns Systems Management Tools and Best Practices Discussions around SCCM Requirements and how they will impact AD Discussions on Next steps Scalabilty of the current proposed setup

THANK YOU

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy