Bits & Layers

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, Ch...

First you need a DB of all of the timezones... thank you tzdata~ DROP TABLE tzds; CREATE TABLE tzds(   tzName VARCHAR(32) NOT NULL PRIMARY KEY , UTCoffset VARCHAR(6) , DSToffset VARCHAR(6) , dayLightSaving BIT  ); INSERT INTO tzds(tzName,UTCoffset,DSToffset,dayLightSaving) VALUES ('Africa/Harare','+02:00','+02:00',0); INSERT INTO tzds(tzName,UTCoffset,DSToffset,dayLightSaving) VALUES ('Africa/Lusaka','+02:00','+02:00',0); INSERT INTO tzds(tzName,UTCoffset,DSToffset,dayLightSaving) VALUES ('Africa/Johannesburg','+02:00','+02:00',0); INSERT INTO tzds(tzName,UTCoffset,DSToffset,dayLightSaving) VALUES ('Indian/Mayotte','+03:00','+03:00',0); INSERT INTO tzds(tzName,UTCoffset,DSToffset,dayLightSaving) VALUES ('Asia/Aden','+03:00','+03:00',0); INSERT INTO tzds(tzName,UTCoffset,DSToffset,dayLightSaving) VALUES ('Pacific/Apia','+13:00','+14:00...