Hi When a room mailbox declines a meeting request that exceeds the booking window in days a response like this is returned. The end date of this series of repeating meetings is too far in the future. This resource can only be scheduled up to 180 days in advance. The end date must be before 2/7/2011. The date returned appears to be hardcoded in US format (M/d/yyyy). I need this to be NZ date format (d/MM/yyyy). How can I accomplish this? Thanks Olli

Hi Olli, Which lanuage version exchange do you use? Per my known, all the date format shown as M/d/yyyy in english version exchange. It seems by design. Regards! Gavin

Hi Gavin We use the English version of Exchange 2010, with regional settings set to English (New Zealand) defaults for all user accounts and administrative settings. The response should format the date according to the NZ short date format, rather than hardcoding it to US format. How can I accomplish this? Thanks Olli

Hi Gavin Any more information re this issue? If the format was hardcoded to US, that would be a really stupid mistake. Honoring the configured locale and regional settings is development 101. Regards Olli

Hi Olli, Sorry for the last puzzling reply. I have make a test, use cmdlet "set-mailboxregionalconfigration -identity source -lanuage en-nz", and the result would set the dateformate as D/MM/YYYY. So it seems work well, and what about your operation. You could test it again, and confirm the room mailbox using "get-mailboxregionalconfigration -identity source" Regards! Gavin

Hi Gavin I ran Set-MailboxRegionalConfiguration RoomName -Language en-NZ and the correct date and time format is now showing when running Get-MailboxRegionalConfiguration Identity Language DateFormat TimeFormat TimeZone -------- -------- ---------- ---------- -------- en-NZ d/MM/yyyy h:mm tt but the replies sent by the room are still showing the date in US format, even after waiting a couple of hours. Is there something that needs to be restarted to pick up the change? Btw why does Get-MailboxRegionalConfiguration not return a value for the Identity column? Thanks again Olli

Hi Gavin The replies still show US date format. Is it indeed hardcoded, or should it honor the regional configuration of en-NZ that I configured for the room? Do I have to restart a service to pick up the change? Any idea why Get-MailboxRegionalConfiguration does not return a value for the Identity column? The mailbox regional configuration cmdlets appear to be pretty buggy.... Regards Olli

Hi Gavin Would you please be so kind to answer the questions in my last post? Thanks Olli

Hi Olli, Sorry for the delay reply, I have been doing more research regarding to your issue with other members in our team, and I would give you more information ASAP. Regards! Gavin

Hi Gavin It's now been another 10 days, any news on that? Thanks again Olli

Hi Gavin Would you please get back to me with your findings? Despite setting the mailbox regional configuration to en-NZ and upgrading all mailbox servers to Exchange 2010 SP1 the date is still formatted in US format (MM/dd/yyyy). I need a solution for this because it's very confusing to NZ users if day and month are both between 1 and 12, and day and month are reversed. Thanks Olli

Hi We are having the same problem in our environment (Exchange 2010 SP1) and from what I have read this was an issue in Exchange 2007 as well, will this be fixed in a future Roll up for Exchange 2010?? Thanks Chris

Hi Gavin, We have exactly same problem in our environment (Exchange 2010 SP1). Any solution Yet?

FWIW, we are also having the same problem despite the room being set to the correct regional settings. Our environment is Exchange 2010 SP2 [PS] C:>get-mailboxregionalconfiguration MeetingRoom | select * RunspaceId : 1657394a-5640-4d8b-9b3b-e061e03db69f DateFormat : d/MM/yyyy Language : en-AU DefaultFolderNameMatchingUserLanguage : False TimeFormat : h:mm tt TimeZone : AUS Eastern Standard Time Identity : IsValid : True The Declined message reads: Your meeting request was declined. The end date of this series of repeating meetings is too far in the future. This resource can only be scheduled up to 500 days in advance. The end date must be before 11/17/2013. All times listed are in the following time zone: Customized Time Zone I guess, given the lack of response from MS, that it is in fact hard coded and cannot be changed. C'mon MS, can you atleast confirm this is the case? Thanks guys Mick

Hi All, So, to resolve the problem, we need to let the sender to send the message in EN-NZ locale, To do so, we can add the following registry entry on the senders Outlook client. HKCU\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles\<current Outlook profile>\13dbb0c8aa05101a9bb000aa002fc45a Value: 000366a1 Type: REG_BINARY Data: 09 0C 00 00 NOTE: You may need to create this value. Please try this, and make some tests. Regards!Gavin TechNet Community Support

Hi All, So, to resolve the problem, we need to let the sender to send the message in EN-NZ locale, To do so, we can add the following registry entry on the senders Outlook client. HKCU\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles\<current Outlook profile>\13dbb0c8aa05101a9bb000aa002fc45a Value: 000366a1 Type: REG_BINARY Data: 09 0C 00 00 NOTE: You may need to create this value. Please try this, and make some tests. Regards!Gavin TechNet Community Support

Hi All, I have the same situation here. Has anyone tried Gavin's fix? Cheers Harry

Tried the above regfix. Can confirm that it worked successfully after entering it into reg and restarting outlook. Environment: Exchange 2010 SP1 RU4 Outlook 2k10 client FYI - also confirmed that when trying to send the meeting request via OWA, it comes through correctly. Obviously this is one of those wonderful Outlook 'features'

Tried the above regfix. Can confirm that it worked successfully after entering it into reg and restarting outlook. Environment: Exchange 2010 SP1 RU4 Outlook 2k10 client FYI - also confirmed that when trying to send the meeting request via OWA, it comes through correctly. Obviously this is one of those wonderful Outlook 'features'