Network Redesign: Part 1

I work for 'Company' and when I got here there was no IT department, this allowed for a third party to make a mess of anything you could call a network design or plan.  I made it a goal to write a new design plan and execute it, These are some notes from my design process.

the Domain Forests

Existing design:
The WHY:
Single domain with awful ".local" post-fix.... not sure why they did it like this.

shorthandnameofcompany.local

New Design:
The WHY:
We work with systems that require clean active directory forests and their own domain so we created a series of domains to facilitate this.  All Users are found in the Parent "Internal" Domain.

in.companyname.com (Windows 2012, internal domain, Parent)
dev.in.companyname.com (Windows 2012, Developer Domain, Child)
qa.in.companyname.com (Windows 2012, Testing Domain, Child)
prod.in.companyname.com (Windows 2012, Demo Environment, Child)
lab.in.companyname.com (Windows 2012, Sandbox Environment, Child)

LDAP User Lookup:
To user LDAP Authentication against the parent domain with some of our systems I used the following string as my Active directory Filter....

(&(memberOf=CN=GroupName,CN=Users,DC=in,DC=companyname,DC=com)(sAMAccountName=*)(!(userAccountControl:1.2.840.113556.1.4.803:=2)))


This allows me to give access to a server/application by simply adding the user to a AD specific group.



Comments

Popular posts from this blog

Understanding & Constructing Dynamic CVP Elements with VFC: Part 1

Creating tar files for Cisco UCM with a Mac

PCCE 11.x Multi-Line Not Working