This happens in our environment. I have found that I have to uninstall
KB2687623 more than once because it seems to re-appear after
uninstalling a different Outlook update. Triple check that that didn't
happen.
I do really wish they would fix this!
On 3/21/2013 3:43 PM, Miller Bonnie L.
Good luck with that. You'd probably be much better served by creating a
rule that just sent OOF messages to trash. In my ~12 years on the sunbelt
lists you aren't the first person to make such an observation or request.
On Fri, Mar 22, 2013 at 8:54 AM, Dean d...@ripperd.com wrote:
It seems
I didn't see it on the list, but now that you mention that, it makes me think
there could also be some patch supercedence going on here, as we are all
up-to-date through now. I'll have to look at our WSUS server on Monday (I'm
off today) and look for a chain--there could be another patch
You have days off? What's that like?
From: Miller Bonnie L. [mailto:mille...@mukilteo.wednet.edu]
Sent: Friday, March 22, 2013 7:29 AM
To: Heaton, Joseph@Wildlife; MS-Exchange Admin Issues
Subject: RE: Export-Mailbox issue
I didn't see it on the list, but now that you mention that, it makes me
LOL, and I'm checking my work e-mail still, so does it really count? Nice and
snowy today here in the WA mountains =)
From: Heaton, Joseph@Wildlife [joseph.hea...@wildlife.ca.gov]
Sent: Friday, March 22, 2013 8:00 AM
To: MS-Exchange Admin Issues
Subject: RE:
Can't say for sure, but this part looks suspicious:
System.InvalidOperationException: Operation is not valid due to the current
state of the object.
at
Microsoft.Exchange.Data.Storage.ExchangePrincipal.get_ServerFullyQualifiedDomainName()
at
I think I reported this during the E15 TAP but there was no backport. Try this:
Add-PSSnapin Microsoft.Exchange.Management.PowerShell.E2010
$error.clear()
$mb = get-mailbox xx
$mb | get-InboxRule | export-csv pete.csv
$mb | export-csv pete2.csv
The problem is that get-InboxRule can't figure
