<shameless pimping>
I'm running a story and survey about e-mail based calendaring solutions on
my website (www.mail-resources.com) to get an idea of what kinds of issues
people are having related to calendaring and what types of solutions people
are implementing. At our office we just use Outlook's direct booking
feature, but then I can "educate" users who don't understand it directly and
we only have 2 conference rooms....

So, register on the site (shame on you if you haven't already) and feel free
to moan mightily about how the world isn't fair. 

> -----Original Message-----
> From: Moore, David K [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, June 19, 2002 2:07 PM
> To: Exchange Discussions
> Subject: From nirvana to hell in one upgrade - the tail of direct booking
> in Outlook 2k+
> Importance: High
> 
> Here's the story -
> 
> Running Exchange 5.5 and users booking appointments using the AutoAccept
> script from ExchangeCode.com - and my life is great (except for those
> darn reoccurring meetings from time to time).  Now we make the big move
> to E2K and since the autoaccecpt script "doesn't" (some reports say it
> does, some it doesn't - my testing says it doesn't) work on E2K... so I
> need to come up with a new method.  The two methods are using the really
> old method of leaving an Outlook97 machine logged in with all the
> resource accounts setup to delegate their appointments to the one
> dedicated Outlook97 account -or- use the new fangled Outlook 2000/2002
> direct booking feature (Direct Booking of Resource Without a Delegate
> Acct. [Q196534]) where in the client directly books their own meetings
> using Outlook.
> 
> Ok, I test it (the new direct book method) and all seems ok.  But...
> when I roll it out into production I have random users (dozens out of
> 4,000 users) that can not book onto a room because Outlook first
> declines the meeting because it says it is "busy" and then follows that
> up with an error of "Unable to save Free/Busy".  So, in trouble shooting
> I have narrowed it down to the client by:
> 
> * Happens even if the user logs into another machine with their account
> (without roaming profiles)
> * Deleting the free/busy file of the calendar (using the GW-Client) and
> then re-setting it up fixes it from time to time
> * Granting Owner rights also "sometimes" fixes the problem but not
> always
> 
> Is there anyone out there that is using the new OL2000+ direct booking
> method and has it working correctly?  Is there some way to get the
> exchangecode.com script working on E2K?
> 
> david moore
> Chevron Phillips Chemical
> Messaging Group
> 
> _________________________________________________________________
> 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]

_________________________________________________________________
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]

Reply via email to