Discussion Locked

Win2k Internetworking

0 helpful
4 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I am currently developing a Windows 2000 upgrade plan. I am being told that unless I place a Win2k DC in each remote location from the onset my bandwidth will be consumed by remote clients performing requests for services over the wan. Is this true?Would you point me in the direction of any documentation pertaining to this information. I was planing on upgrading one site at a time and not using the Active Directory Client in any site until a Win 2k DC is in place on that subnet.

4 replies

by ntoz

I would say this is not true. It wouldnt be logical to install a DC at a site with a couple of users. While that might not be the case, it just dispells this theory. You really have to be the one who answers this question though. Your the one who knows what type of traffic will come from these sites. To play this out in another way, lets say you did have a very small subnet, you placed a dc at this site and by nature, you did do many changes, additions and deletions in an ongoing fashion. If the site contained a DC that replicated with a much larger site, that small site, its smaller bandwidth would be disrupted with all that traffic. Its really a balancing act. The very most important part is to get your AD tree correct. I would put 80% of my effort into that and planning your AD and Windows 2000 effort. May I suggest a book, Building Enterprise Active Directory Services Notes from the field. By Microsoft Press. The great thing about this book is the number of case studies and bandwidth compairing they give. This is real world information that may help you better plan. The only thing in your design that is written in stone is your AD root. You can have a good plan, if you have issues with small sites after you have tried it initialy with out a dedicated DC, put in a DC. Please dont get me wrong, Im in no way saying have a half A@%* plan, but on the other hand, AD is flexable, its the point of AD. As far as your remote clients performing requests for services, most service requests are very small in size. In a mix mode enviroment, your legacy clients will still be using WINS to locate services and BDC's for logon authentication and Master Browsers for your brows list. Not much has changed. Your new Windows 2000 again, depending on how you set it up, will use DNS's service records to find these resouces. DNS look ups are not very big, they are done over 56K Dialup by most people surfing the web.

by ntoz

Take it all into perspective, dont panic, forget the hype. Put all that aside, draw it all out on paper, use a Microsoft Road map and you should be golden. There is no documents that say you have to put a DC in every remote location and if there are, they are wrong and you wont find it on the Microsoft site. Not one that at least says "YOU MUST HAVE A DC AT EVERY LOCATION". I can see it now, Ok Mike take home your laptop, your going to VPN in, oh and by the way, you need to take home this Domain Controler that Oh by the way will replicate with Corporate tons of stuff you wont need so at times you wont be able to do a thing, but your logons will be very fast in between and you will have a local server, just dont drop it on your foot when you travel. I hope I helped a little bit, get the book and good luck..

Pete

This discussion is closed to new replies.