Booking room calendars over 180 days out on Exchange 2010 (affects Exchange 2007 also).

While booking a recurring event with a room calendar, I receive the message "This resource can only be scheduled up to 180 days in advance". Actual e-mail below. I was booking a biweekly event for a year.

-----Original Appointment-----
From: Training Room
Sent: Friday, November 21, 2014 5:16 PM
To: removed
Subject: Declined: Sales Meeting
When: Tuesday, June 09, 2015 8:30 AM-10:00 AM (UTC-05:00) Eastern Time (US & Canada).
Where: Training Room

Your meeting request was declined.

This resource can only be scheduled up to 180 days in advance. The end time should fall before 5/21/2015.

All times listed are in the following time zone: Eastern Standard Time

Come to find out that this is the default setting.

Execute Get-MailboxCalendarSettings "<mailbox alias>" | fl

Look at settings for BookingWindowInDays and EnforceSchedulingHorizon.

Change the setting with:

Set-MailboxCalendarSettings <mailbox alias> -BookingWindowInDays <Days>
OR
Set-MailboxCalendarSettings <mailbox alias> -EnforceSchedulingHorizon  $False

No need to do both.

Error trying to delegate (grant) access to my Outlook Contacts - "The Delegates settings were not saved correctly. Unable to activate send-on-behalf-of list. You do not have sufficient permission to perform this operation on this object".

I was attempting to add a user with access to ONLY my contacts. I have a few thousand contacts and I have a temp user that was helping to categorize the contacts. I was trying to get organized.

Received the error "The Delegates settings were not saved correctly...".

If you go back in to TOOLS > Options > Delegates, nothing is saved/changed. For me this is happening on both Outlook 2007 and Outlook 2010 (I have multiple computers available) w/ Windows 7, 64 bit.

Per http://support.microsoft.com/kb/2593557 :

When you add a delegate, Outlook also tries to grant "send on behalf of" permission to the delegate by default. This permission is written to the publicDelegates attribute of your user object in Active Directory.

The issue that is described in "Symptoms" can occur for either (or both) of the following reasons.

• The global catalog (GC) server to which your Outlook client is connected is not local to your domain.
  
  If your Outlook client is connected to a GC that is not local to your domain, the publicDelegates attribute cannot be written to your user object in Active Directory.
• The SELF object does not have the Write Personal Information right on your Active Directory user object.

I checked that:
[1] the GC is definitely local to my domain - I only have one domain. I have 2 GCs, both are logically local and physically local.
[2] the self object does not have the Write Personal Information right on your Active Directory account

The latter was in fact true, in ADUC (advanced view) I did not have "Write Exchange Personal Information" (image below - In the image I already checked the box, originally is was not checked).
*edit - this is not correct, I was looking at the wrong attribute

**EDIT - this is incorrect
Unfortunately, Adding SELF to "Write Exchange Personal Information" did not fix the issue. Yes, I logged out and in. I also rebooted for good measure. Maybe I didn't wait long enough for AD replication. Regardless, I went ahead with the "Fix it for me..." from M$ http://go.microsoft.com/?linkid=9830127 and I was off to the races.

**EDIT
The attribute in question is "Write Personal information",  NOT "write Exchange Personal Information".

*adding the proper security DOES fix the problem.

*DO NOT run the Microsoft Fix it because, upon further investigation, this does not fix the problem, it only suppresses the error message.

This can be run/scripted via powershell

Add-ADPermission -Identity 'MailboxCanonicalName' -User 'NT Authority\self' -AccessRights ReadProperty, WriteProperty -Properties 'Personal Information'

to get the mailbox canonicalname use:
get-mailbox
or
get-mailbox | select name,alias

Good Luck

e-mail missing and automatically deleted

e-mail automatically deleted - Outlook 2010

Outlook 2010, Exchange 2007 SP3, Samsung S3 Andriod KitKat (4.4)


Today a strange scenario happened. I was on my way into the office and checking my e-mail while driving (not preferred). I noticed a few important e-mails from a particular sender that I need to address. The e-mail in question were mixed in with other lesser important e-mails. I will reply to the e-mail from my desk PC.

 

I get to my desk and open Outlook. NONE of the e-mail, all from one sender, are in the Inbox. Weird. I look down at my phone and POOF - the e-mail are gone from the Inbox on my phone. Again all of the e-mail in question is from one particular sender, no other e-mail is affected.

 

I search the junk e-mail, find nothing. I look in the "Deleted Items" and whamo my missing e-mail is there.

 

• I suspected rules in Outlook. I disabled all the rules in outlook, had the sender re-send the e-mail. Straight to deleted again.
• Next I suspected rules in OWA - disabled, same result
• Junk mail filter? This was not even a possibility for me because the sender was internal to my organization (and in the same domain). Additionally my junk e-mail options were not set to "permanently delete...instead of moving to the junk e-mail folder". See image 1.

Permanently delete suspected - NOT CHECKED. Doesn't matter because internal
senders are not processed by the junk e-mail filter.



• Spam filter? Again, not possible because the sender is internal. My spam filtering is done at the gateway therefore internal messages don't hit the spam filter. BTW, I am using SpamTitan - not the best, but it works.

I was just about to delve in to the transport logs and message tracking logs but I know that this will not be fruitful because, remember, I received the e-mail on my phone, and subsequently to my "deleted items", which means the e-mail was delivered. The e-mail in question only moved to deleted AFTER I opened Outlook. Something on the client, other than Junk E-mail filter and "rules" was processing the message.


After reviewing the e-mail in my deleted items, I found this gem "Ignore Conversation".





I never ever use the Ignore feature. I get it but I just don't have a need for it. Somehow this got enabled for this message. I probably pulled an end user maneuver and clicked on it instead of clicking delete. Here comes the big punch line. I never clicked on Ignore on this e-mail. Outlook thinks all messages with the SAME SENDER and the SAME SUBJECT LINE are part of the SAME CONVERSATION - even though we know this not the case. For example, if your co-worker Bill sends you a weekly e-mail, with the subject line "For your review", Outlook treats ALL of the messages as one conversation.

• Unchecking Ignore move ALL of the messages from that sender w/ the same subject line back to the Inbox.

Thanks for listening.