Home ›
ASP.NET Forums » Data Access » Active Directory and LDAP » 911**Urgent**911

911**Urgent**911

Last post 11-05-2009 5:12 PM by N_EvilScott. 1 replies.

Sort Posts:

  • 911**Urgent**911

    05-05-2009, 9:39 PM
    • Member
      point Member
    • clos_man
    • Member since 05-06-2009, 1:31 AM
    • Posts 1

    Can anybody help me? I am having trouble finding a solution to the following scenario:

    You are an independent contractor who specializes in Microsoft’s Active Directory.  You have taken on as a client a local hospital.  The hospital has 25 domain controllers located in 9 departments around the hospital.  All domain controllers are connected through the LAN.  Three departments are using older, 10-Mbps hubs, while the other departments are using 10/100-Mbps switches.  Between the hours of 8:00 AM and 6 PM, the network bandwidth utilization averages 95%.  A research team just leased office space in a building located across town to house 20 researchers.  The new office currently has a 56-Kbps ISDN connection to the hospital that needs to be upgraded to a T1 within the next six months.The hospital’s IT manager is concerned that there is too much Active Directory replication occurring during the day, consuming the bulk of the available bandwidth in the hospital.  You just found out that the researchers will be using Active Directory to store research subject data that will be constantly updated and modified.  Senior researchers at the hospital will review this data.  You are concerned this will cause network slowdown at the hospital.  How should you design the hospital’s replication topology to minimize the amount and frequency of replication during the day?  Feel free to create a network map to help explain your solution.You received a call from a researcher in the new facility informing you that changes made by network administrative staff located at the hospital do not seem to take effect at the new facility.  Similarly, research subject data is not being replicated from the new facility to the hospital.  What tool(s) could you use to troubleshoot the issue?  What are some possible causes of, and solutions to, this problem?                                                                                                                                 

     

  • Re: 911**Urgent**911

    11-05-2009, 5:12 PM
    • Participant
      899 point Participant
    • N_EvilScott
    • Member since 07-22-2008, 7:28 PM
    • Oregon
    • Posts 203

    First of all who created this weird solution? There is a reason hospitals are supposed to have well suited data rooms or data centers. I used to work at a hospital and we built a brand new data center in the basement just for this purpose. Why are the domain controllers stacked around all over the place and not centralized? Why do you want a T1? Get a T3 bracket and start porting phones off of it and cut costs accross the board.

    Use DCDIAG and NETDIAG to study basic replication issues, most likely domain controller errors or conflicts in catalog servers.

    Change out the HUBS and drop in switches, very inexpensive and better network usage. I would recommend using HP 1800 series switches as you can from a Layer2 aspect handle all traffic bandwidth.

    Next in Active directory sites and services, make sure that all sites are set to replicate no more than every 2 hours due to bandwidth needs. Would also be cost justifiable to insert a couple load balancers at key places to make sure the data is streamed correctly, and give priority in the right places....

    And if the network administration people cant' figure out whats wrong then they suck and need to be fired :P

    I know this post is old, but heck why not?

    Scott was here...
    http://www.orionmedicalservices.com
    http://www.seideleyecare.com
    http://www.freytagdesigns.com
Page 1 of 1 (2 items)
RSS Available

Contact | Advertise | Issue Management by Axosoft's OnTime | Running IIS7
All Rights Reserved. | Terms of Use | Trademarks | Privacy Statement
© 2009 Microsoft Corporation.