locked
Deploy address book when the client is installed RRS feed

  • Question

  • For a large role out it would be quite a strain on the system if 80,000 clients all signed in on the go live day and downloaded a 20mb address book.

    Is it possible\supported to "pre-populate" the clients with the address book by copying the GalContacts.db (?) etc to the correct  Local Settings folder?

     

    I understand that any point in time copy of GalContacts.db is only valid for 30 days and a number of deltas would need to be donwloaded etc.

     

    Thanks for any thoughts.

     

    Monday, September 1, 2008 1:15 PM

Answers

  • This suggestion is probably your best bet for the initial deployment, assuming you have enough local DCs to assist in a distributed file deployment.

     

    The AbsInsideURL registry setting, which is configurable via the communicator.adm GPO template is what you would use to configure local distrubtion points, would be easy to setup if you already have user or computer accounts organizaed by location OUs.

     

    The bandwidth throttling may also work but might cause very slow initial logins of OC and possible timeouts depending ont the load.

    Wednesday, September 3, 2008 10:58 PM
    Moderator

All replies

  •  

    Addressbook is downloaded via the Webcomponents server that is hosted on IIS

    So you could actually throttle IIS so that you do not strain the network but downloads will be slower

     

    Not sure if the local copy up front will work but if you try it out let us know how it went

     

    Monday, September 1, 2008 4:06 PM
  • Thanks _ excellent idea about throttling IIS.

     

    I will do some more testing on pre-populating address book.

    In intial tests the client doesn't throw up any errors but I need to carefully monitor how much data it downloads.

     

    Regards

    Alistair

     

     

    Wednesday, September 3, 2008 9:09 AM
  •  

    You can also set the clients to look in the sysvol folder on the dc's.  This will spread it out over all of your DC's instead of one server.  This can be done through the GPO.  You will also need to setup a routine to copy the files over to the sysvol location after the address book sync occurs every nite.
    Wednesday, September 3, 2008 6:07 PM
  • This suggestion is probably your best bet for the initial deployment, assuming you have enough local DCs to assist in a distributed file deployment.

     

    The AbsInsideURL registry setting, which is configurable via the communicator.adm GPO template is what you would use to configure local distrubtion points, would be easy to setup if you already have user or computer accounts organizaed by location OUs.

     

    The bandwidth throttling may also work but might cause very slow initial logins of OC and possible timeouts depending ont the load.

    Wednesday, September 3, 2008 10:58 PM
    Moderator