J
Jesper G. Dinesen
Running Exchange Server 2003 environment with Outlook 2003 and OWA clients,
no migrated accounts, clean new environment. Approx 1000 users and 50
resources created. Every day one or more users/resources have their free/busy
information messed up disabling other users to book/view their schedule.
Why do Microsoft add a parameter (/cleanfreebusy) to Outlook to fix a messed
up free/busy instance instead of fixing the error in Outlook itself. Our
users keep running into the problem that another user can't see their
free/busy information because it is messed up by Exchange/Outlook/Green
Goblins.
I don't want the users with the messed up Free/Busy informations constantly
to have to fix the problem as they are rarely aware of the problem. I want to
stop the problem emerging or alternatively be able to let the support staff
fix it (without having to start outlook with the /cleanfreebusy on behalf of
the user).
Could a server side script/fix/routine/clean up job take care of it?
no migrated accounts, clean new environment. Approx 1000 users and 50
resources created. Every day one or more users/resources have their free/busy
information messed up disabling other users to book/view their schedule.
Why do Microsoft add a parameter (/cleanfreebusy) to Outlook to fix a messed
up free/busy instance instead of fixing the error in Outlook itself. Our
users keep running into the problem that another user can't see their
free/busy information because it is messed up by Exchange/Outlook/Green
Goblins.
I don't want the users with the messed up Free/Busy informations constantly
to have to fix the problem as they are rarely aware of the problem. I want to
stop the problem emerging or alternatively be able to let the support staff
fix it (without having to start outlook with the /cleanfreebusy on behalf of
the user).
Could a server side script/fix/routine/clean up job take care of it?