I would like to be able to book resource rooms for an unlimitted amount of days, using the set-mailboxcalendarsettings -bookingwindowindays maximum is 1080, is there a way to set this to unlimitted? I realize I can set the enforceeventhorizon to $False but that still only results in the room being book 1080 days out.

Is it rejecting recurring meeting also after settingEnforceSchedulingHorizon to $False? This parameter will allow you to book recurring mettings which have end date out of booking window... Set-MailboxCalendarSettings http://technet.microsoft.com/en-us/library/aa996340.aspx BookingWindowInDays option can be set between 0 to 1080 only.Amit Tank | MVP - Exchange | MCITP:EMA MCSA:M | http://ExchangeShare.WordPress.com

no it does not reject the meeting when I have EnforceSchedulingHorizon to $False; but the accepted message states the meeting was accepted until date with date being 1080 days out. When I check the calendar for the resource the meeting shows up until the specified date in the accepted message.

This is not an answer Amit!What we need to know is that if it is possible in Exchange 2007 to book a resource with a recurrence that has no end date i.e. beyond 1080 daysbookingWindowInDays is set to 1080EnforceSchedulingHorizon is set to $falsewe still cannot book resources beyond 1080 days.Thanks,Ben

I am having the same issue. My settings are:Get-MailboxCalendarSettings adminrooma | fl *window*, *sched* BookingWindowInDays : 400EnforceSchedulingHorizon : FalseScheduleOnlyDuringWorkHours : Falsebut when I book a meeting for longer than 400 days out I get a declined meeting saying:Your meeting request was declined. This resource can only be scheduled up toxx days in advance. The end time should fall before 10/xx/20xx.I thought it might be similiar to my other resource mailbox issue, but logging in doesn't fix this one. I think this whole resource mailbox thing want tested very well.

Well let me tell you Mike, you're not gonna find a fix. I took this issues as high up as you could take it with MS in Texas. I will try to summarize the issue and your options and what we as an orgnization have ended up doing in the interim:1. Exchange still uses a relational database to store all the insane amounts of transactions and data that go on for a communication platform to function, so that means that you cannot have an infinitely recurring event forevever without the database tables/recordsets or whatever it may be becoming corrupt eventually. Don't ask me "how come I can book an individual meeting forever and it will let me do it on my own exchange mailbox forever". I don't know.2. Apparently MS was seeing issues with resource calendar corruptions in previous versions of exchange that allowed infinite bookings of resources that for 2007 they've decided to implement hard limits for resource type mailboxes. 3. Max # of days that you can have a recurring appointment in Exchange 2007 is 1080days. What? That's an odd number, like a few days shy of3 years. Again, don't ask, I have no clue why? Probably some mathematical limit beyond which data corruption becomes more likely?4. Apparently in their testing the Exchange 2007 group determined that 80% of organizations only need recurring events with resources for abotu 180days. Really? the other 15% or so of organization would need it up to 365... and oh the odd 5% weirdo orgnizations that for some strange reason need to have a meeting room booked for a weekly meeting forever would not need it beyond 1080 days (just shy of 3 years of course to make it a bit more confusing). 5. So, choices are as follows: a) Pick a limit that your users can handle, i.e. 365 and remind them that every year they have to go into appointments and update the recurring events for another year. Of course the catch here is that Outlook 2007's default view for an appointment's recurring screen is 'no limit'. What the ____ man? Are they trying to make it harder intentionally? Why not have Outlook check the resource being used for the appointment, see that there is a hard limit and not allow the client to book beyond that number of days. Duh! b) change EnforceSchedulingHorizon to be True (this should return a decline if the user tries to book beyond the BookingWindowInDays limit. If you set it to false, it shoudl just book without issues but only books till the number of BookingWindowInDays limit. Test this out, I've confirmed that's how it works on our Exchange 2007 SP1 with Update rollup8. c) We decided to enable 'directbooking' for our meeting/conference rooms instead of using autoattendant. The weird thing is that you can book the same resources if you disable autoattendant and use directbooking - might result in resource corruption eventually, but we're a local governement organization, our public hearing meetings and strata council meetings are on the SAME days of the week, at the SAME dang times... forever... it doesn't change.Ok I've rambled on enough on this - I have more details that I'll omit but if you have more questions, post and I'll see if I can help.Cheers,Ben

The solution is to: set-mailboxcalendarsettings yourroom -EnforceSchedulingHorizon $false -bookingwindowindays 0 This will allow infinite recurring appointments.

Sorry - I didn't mean to propose this question as an answer! First time I have used this forum. I think the solution is: set-mailboxcalendarsettings yourroom -EnforceSchedulingHorizon $false -bookingwindowindays 0

Ben, thanks for your comments! I think this underlines the lack of documentation and testing around this subject. click the above link to see what other problems exist with this feature.Cubittech, this sounds very promising. I have since moved on to other tasks, but this is great knowledge. Are you sure it works? Seems frusturating, though not unbelievable, that PSS wouldn't know this after all of Ben's calls.

Thanks for trying to provide a solution cubittech, but been there done that - it doesn't work! In fact I think I know where you might have found that - it was an "outlook online" help page right? Ran that solution past MS Exchange support and it's not a resolution. Cheers

The solution set-mailboxcalendarsettings yourroom -EnforceSchedulingHorizon $false -bookingwindowindays 0 actually worked. After this when we send a meeting request with no end date, the meeting room accepts with an acceptance message as below. " Accepted through 3/8/2013: Meeting Name " . ( This date is calculated based on 1080 days count. ) Now the BIG question is how to extend the meeting without recreating the meeting : The answer is simple. When the meeting organizer update the meeting series after some time, let’s say after a month, the date in the acceptance message get extended for furtehr 1080days from the day it is updated. INITIAL ACCETPANCE MESSAGE : Accepted through 2/6/2013: TEST Meeting AFTER UPDATING THE SERIES : Accepted through 3/6/2013: TEST Meeting ( Please note that the end date is calculated for further 1080 days ) - This extension of meeting period will work only when updating the meeting series and NOT an individual occurrence. - Anyways people updates meeting series at least once before 3 years, I belive 3 years is big time. PS: We recently updated Exchange SP2 and I happened to create a meeting room today, I noticed that it worked without applying -EnforceSchedulingHorizon command. I am not sure it is because of SP2. Of course it still accepts for the period of 3 years only.

Being able to book an appointment for an umlimited amount of days means that with a single re-occurring appointment you could make a resource calendar have an infinite number of appointments on it, and consume an equally infinite amount of space to store it.

Of course that makes sense to someone who understands that Exchange's DB is ultimately a relational database and cannot have infinite records; but try convincing users who then respond with "But before [Exchange 2003], I could book the appointment forever". Anyway, we've moved past this and set a 1 year limit. Users just have to update their appointments every year. As for our resources, i.e. rooms that we wish to book forever, we have disabled autoattendant and enabled directbooking - problem solved (via a workaround).

Of course that makes sense to someone who understands that Exchange's DB is ultimately a relational database and cannot have infinite records; but try convincing users who then respond with "But before [Exchange 2003], I could book the appointment forever". Anyway, we've moved past this and set a 1 year limit. Users just have to update their appointments every year. As for our resources, i.e. rooms that we wish to book forever, we have disabled autoattendant and enabled directbooking - problem solved (via a workaround). That doesn't really make any sense, why can you still do infinite appointments for a User Mailbox but not a Room Mailbox? Workaround is all good though.