Cannot schedule Meetings beyond 6 months

M

mmcginley

Our Exchange Environment is a mix of Exchange 2003 and Exchange 2007. It
appears that clients cannot schedule appointments beyond six months.

The following message is being returned by Exchange, "Your meeting request
was declined.

This resource can only be scheduled up to 180 days in advance. The end time
should fall before 3/31/2010.

All times listed are in the following time zone: (GMT-05:00) Time Zone.
Sent by Microsoft Exchange Server 2007"

To date this only seems to happen to clients using Microsoft Outlook 2007.

Is this a configuration setting? If so, how and where is it configured?
Is this an actual error? If so, does anyone know the fix?

Thanks for any help that can be provided.
 
M

mmcginley

Thanks Diane,

Is there anything you can think of that would prevent Office 2007 clients to
not schedule beyond 6 months and allow Office 2003 clients to schedule beyond
6 months?

Mark

Diane Poremsky said:
This is an Exchange configuration - you need to use the management shell
set-mailboxcalendarsettings "MailboxAlias" -BookingWindowInDays ###

### can equal up to something like 1080.

--

Diane Poremsky [MVP - Outlook]



Outlook Tips by email:
mailto:[email protected]

EMO - a weekly newsletter about Outlook and Exchange:
mailto:[email protected]

Let's Really Fix Outlook 2010
http://forums.slipstick.com/forumdisplay.php?f=34

mmcginley said:
Our Exchange Environment is a mix of Exchange 2003 and Exchange 2007. It
appears that clients cannot schedule appointments beyond six months.

The following message is being returned by Exchange, "Your meeting request
was declined.

This resource can only be scheduled up to 180 days in advance. The end
time
should fall before 3/31/2010.

All times listed are in the following time zone: (GMT-05:00) Time Zone.
Sent by Microsoft Exchange Server 2007"

To date this only seems to happen to clients using Microsoft Outlook 2007.

Is this a configuration setting? If so, how and where is it configured?
Is this an actual error? If so, does anyone know the fix?

Thanks for any help that can be provided.
 
D

Diane Poremsky [MVP]

Nope, I don't know why outlook 2007 would have a limit and 2003 doesn't,
provided they both hit the same server. If there are multiple servers and
outlook 2003 is hitting a different server with a different limit, then the
results will reflect the server setting.

You might want to try the exchange newsgroups on this server or access then
via the web -
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.exchange.misc

--

Diane Poremsky [MVP - Outlook]



Outlook Tips by email:
mailto:[email protected]

EMO - a weekly newsletter about Outlook and Exchange:
mailto:[email protected]

Let's Really Fix Outlook 2010
http://forums.slipstick.com/forumdisplay.php?f=34

mmcginley said:
Thanks Diane,

Is there anything you can think of that would prevent Office 2007 clients
to
not schedule beyond 6 months and allow Office 2003 clients to schedule
beyond
6 months?

Mark

Diane Poremsky said:
This is an Exchange configuration - you need to use the management shell
set-mailboxcalendarsettings "MailboxAlias" -BookingWindowInDays ###

### can equal up to something like 1080.

--

Diane Poremsky [MVP - Outlook]



Outlook Tips by email:
mailto:[email protected]

EMO - a weekly newsletter about Outlook and Exchange:
mailto:[email protected]

Let's Really Fix Outlook 2010
http://forums.slipstick.com/forumdisplay.php?f=34

mmcginley said:
Our Exchange Environment is a mix of Exchange 2003 and Exchange 2007.
It
appears that clients cannot schedule appointments beyond six months.

The following message is being returned by Exchange, "Your meeting
request
was declined.

This resource can only be scheduled up to 180 days in advance. The end
time
should fall before 3/31/2010.

All times listed are in the following time zone: (GMT-05:00) Time Zone.
Sent by Microsoft Exchange Server 2007"

To date this only seems to happen to clients using Microsoft Outlook
2007.

Is this a configuration setting? If so, how and where is it
configured?
Is this an actual error? If so, does anyone know the fix?

Thanks for any help that can be provided.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top