Tag: Active Directory
And the hole never ends…
by Michael Kavka on Feb.19, 2009, under Computers
You know, I love my job. I love being able to work on things and learn new thoughts and ideas as I work. It is so fulfilling to see a project finished and working right. The only problem is they never are really finished.
So after the big file migration, and the corrections to the AD Users/OUs/Groups was down to a tweak here or there, I decided to see if I could figure out why some things with Exchange and DNS seemed to be so damn slow. They say that curiosity killed the cat and satisfaction brought him back, well we shall see how this ends.
Between finding that AD/DNS integration was set to a legacy standard, even though we use Server 2003, to find that we had only 1 Global Catalog, even though we have 5 DCs 4 of them at other sites, only one DC as a Global Catalog. Replication for AD was set to 4 hours, and all other sorts of small errors in the DNS server have been found. Its the sort of stuff that should have been thought through when the original migration from 2000 to 2003 happened.
Well, at least its keeping me busy, and who knows when any of this stuff will come in handy, but I know it will at some point.
So here we go…
by Michael Kavka on Feb.12, 2009, under Computers
I can’t express how important it is to make sure you not only document your network, but what a pain it is when you don’t.
6 weeks of planning and having to map out Active Directory comes to a head for myself this week as I take care of the last parts of the redesign. Of course a lot fo this time could have been prevented with the proper documentation.
And I don’t mean just listing out what harware you have and how its connected. Active Directory, Network Shares, Security on the shares, all of it should be documented. Not just in case you need to change things, but to show what work has been done, so others can understand what has been done, how things are set up, and more importantly why they are done that way.
It also help out when trying to track down potential causes of issues. It doesn’t matter if its SBS or not, it should be done. Use Visio, make a network notebook, whatever floats your boat, but just do it
