Yeah.. I believe all that we really did was copy it[1] to the proper location and uncheck the read-only attribute. New CDs were burned every 2 weeks I believe, which was necessary as they were migrating users over from another mail system at the same time they were doing the deployment.
[1] "it" being the 5(?) *.oab files. On 3/11/03 14:10, "Tony Hlabse" <[EMAIL PROTECTED]> wrote: > Your first few sentences describes exactly what we would like to do. Send a > CD to all/most users with Outloo2002 deployment and a starting point OAB. > > > > > > > From: Chris Scharff <[EMAIL PROTECTED]> > Reply-To: "Exchange Discussions" <[EMAIL PROTECTED]> > To: "Exchange Discussions" <[EMAIL PROTECTED]> > Subject: Re: Pushing OAB out to end users. > Date: Tue, 11 Mar 2003 14:07:01 -0600 > > It can be done.[1] I worked through the logistics of doing so for a large > customer a couple of years ago. I believe they wound up writing a script to > wrap around the Outlook installation and configuration process which copied > the OAB files from a network share or possibly a CD. OL2003 might have some > other mechanisms for handling this... But I haven't seen the deployment > tools yet to be sure. > > [1] At least through OL2K. > > On 3/11/03 11:22, "Tony Hlabse" <[EMAIL PROTECTED]> wrote: > >> Has anyone pushed out an OAB to end users to preload that file during >> Outlook deployment for a new email system. This way when they go online > only >> the updates will be pulled down. With over 50K users in the GAL we are >> trying to minimize traffic when the Exchange system goes live. We think > it >> can be done just never done it and was wondering if anyone here has done >> this. If so how did you do it. > _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED]
