That sounds kind of messy Brian, I especially don't like the delete all existing subnets and recreate them all. Do you mean you delete *ALL* the subnets or just the subnets for that one site? If all of them it isn't a good thing, you are really working your DCs as they have to refigure everything. I recall speaking to one of the better Alliance guys a few years back and he was saying that adding/removing subnets can hang up a DC for a little while as it recalculates the siting info internally that the KCC and site location services depend on. The more subnets the more concern there was to the point where once you had hundreds of subnets and sites you should consider doing subnet changes after hours (my question of what is after hours for a global organization was not well received nor answered...).
Anyway, I believe Jorge mentioned the idea of having some main top level subnets that are used by any clients that are not in a more specific subnet. These subnets are assigned to the hub sites. I started doing this about 4-5 years ago with the one Widget company I worked for at the time. It worked well especially when my primary mechanism of finding subnets and sites fell through. That primary mechanism was being in the loop for all new deployments of sites and subnets. When a new DC was put into place, it was obviously quite easy to know about something new as three of us were the only ones that put new DCs into place. Anyway, we had scripts that built the sites and site link objects, we had scripts that created the subnets and added them to the sites. We never used sites and services gui so that everything was always very consistent. The mechanism was smooth enough that adding 50 sites or hundreds of subnets was about as hard as adding a single site or subnet and only took a few seconds more. joe -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brian Desmond Sent: Tuesday, May 10, 2005 8:44 PM To: [email protected] Subject: [ActiveDir] Site/Subnet Management Hi all, Wondering what strategies you all use for managing sites & subnets in your AD environment. Mine is fluid in this regard. There are roughly 650 physical locations with 2 subnets per. The number of locations is fluctual in terms of add/drop. Currently we have just a small handful of AD sites, and save for a couple dozen subnets, they all go in one big happy site. We're moving towards putting DCs at remote locations and thus they're going to start getting their own sites. The current system is fairly manual - I start seeing netlogon warnings about # of no site connections, email the WAN guy and get his subnet/location spreadsheet, and then i mangle it a bit into a CSV. I delete all the existing subnets. Run my vbscript which recreates them all according to the CSV. This is all well and good I guess but it's an annoying system. Anybody got anything better? List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
