Saturday, April 14, 2012

New Infrastructure Systems

       This article contains the processes for New Infrastructure Systems.  The information contained within this document applies to sites that range from newly acquired sites to established sites.  These sites may range in size from small sites (0-300 PCs), medium (301-500 PCs), or Large (501-1000 PCs up).


Refer to this article if:

  • Your site is currently not on the planed, namespace, and you plan to install your company workstations or servers. (That entire process is described here.)
  • You need to perform a subset of a new infrastructure deployment, such as:
        • Installing a new subnet for a site
        • Setting up DHCP at a site
        • Setting up DNS at a site
        • Installing Organizational Unit (OU) structure at a site
        • Setting up AD (Sites and Services ) for a site
        • Installing an AD Domain Controller at a site
        • Installing a software management services server at a site
Site Services Definitions:  Subnets, DNS, DHCP, OU’s
Subnet Design

The network team, who makes updates to the router for all sites should plan/design as is required for the following:
  • IP readdressing
  • Subnet mask
Note:  This design is to plan minimum of 15 weeks before the infrastructure needs to be in place (your scheduled IP readdress date, or server/desktop deployment date). 

New sites
For those deploying newly acquired sites, the following steps will be required:
  • Design new IP Addresses
  • Design DNS Entries
  • Subnet Design
  • Work on site design
  • Procure hardware and installation – Routers, rack, servers, space, power requirements
Procure Hardware
       Determine Hardware Requirement Determine your site’s hardware requirements and place your order 15 weeks prior to Day 1 of deployments. Depending on your location and procurement processes, it can take anywhere between 2 weeks and 4 months to receive your hardware.

Server Builds
       The individual server teams can be taked control to finish the process, which takes 5-7 work days for each server.) for example
  • AD Server and DC Promo – DCs need 5-7 work days (assumes already racked, and turned  on “burning in the HW” for a  minimum of 48 hours, and ready to begin DC Promo by day 1) for servers to be built.  After building out the AD Server and promoting the DC, set up the trust between CT and the resource domain. 
  • Software Management Services Server - SMS needs 5-7 work days (assumes already racked, built to Brand and turned on “burning in the HW” for a minimum of 48 hrs by day 1).  Do not plan on deploying workstations until a minimum of 10 work days after the SMS server is complete to avoid workstation deployment delay. The SMS and Exchange servers must wait for the DC server to be completed.  Exchange is also dependent on SMS being available. 
  • DHCP/DNS Build (Create/Delegate DHCP Scope) – NS Servers need 5-7 work days for completion. 
  • Exchange Server - The Active Directory and SAN storage? will need to be in place prior to server installation. Mailboxes can be migrated as soon as servers and storage are in place.  Note that if Exchange will be at the site, then a DC must be at the site as well.
  • Print Server -  Build up to brand 8 weeks prior to PC Deployment

0 comments:

Post a Comment