Exchange 2013 Shared Mailbox Get-MailboxSentItemsConfiguration SP1 Help

Hello
My Setup
Server1: Server 2012 Standard + Exchange 2013 CU2 Standard (MBX+CAS)
Server2: Server 2012 Standard + Exchange 2013 CU2 Standard (MBX+CAS)
DAG Enable
I am having problems with Shared mailboxes, when sending E-mail from the Shared mailbox the sent E-mail will show up in the recipients Sent Items insted of the Shared mailbox sent Items.
I know that in Exchange 2010 Later SP and RU there where a PowerShell command that could send a copy to the Shared mailbox Sent Items (Get-MailboxSentItemsConfiguration)
but it doesn't seem to be there anymore, does anyone know if the cmdlet is back in CU3 or SP1? will it come back?
there is a workaround (Registry) but it doesn't help us, not for our environment.
Can I set this up by Outlook rules or maybe some kind of forwarding?
If you have any experience with this, feel free to give some advice.
Thank You very much!

Hi,
*.MailboxSentItemsConfiguration has not been brought back in CU3 or CU4/SP1 and I don't know if it ever will be.
If DelegateSentItemsStyle configured in the registry is not an option for you, then using multiple Exchange accounts in the same Outlook Profile might be. The support for that was added in Outlook 2010 and personally, I like that option a lot.
Martina Miskovic

Similar Messages

Outlook 2013 / Exchange 2013 : Shared mailboxes - Mail stuck in outbox (non-cached), Mail sends but doesn't get received (cached).

Hello,
We are currently experiencing some weird behaviour in Outlook 2013 since we added Shared Mailboxes.
When we run Outlook 2013 with cached mode
enabled:
- I create a new e-mail and send it.
- The e-mail goes to the outbox, and get's 'send'.
- None of the recipients receives the e-mail.
When we run Outlook 2013 with cached mode
disabled:
- I create a new e-mail and send it.
- The e-mail goes to the outbox, but remains there.
Now to make things even more bizarre:
When I switch from 'cached'-mode to 'non cached'-mode, I see all the e-mail that were 'send' in cached-mode stuck in the outbox.
Note: The DNS server configuration in Exchange is correct.

Hi,
How about sending on OWA? Does the issue exist?
To troubleshoot the issue, let's run Outlook in Safe Mode to determine if 3rd-party add-ins are related:
Press Win + R and type “outlook.exe /safe” in the blank box, then press Enter.
If there’s no problem sending emails in Safe Mode, disable the suspicious add-ins to verify which add-ins caused this issue.
Please also disable the firewall and anti-virus program to send the emails again, in many scenarios the protection may cause the issue.
Please also keep Exchange and Outlook patched to the latest.
Regards,
Melon Chen
TechNet Community Support

Exchange 2013 - Shared Mailbox Permissions

Here is what I am trying to do. I would like to create a shared mailbox in exchange 2013 for time off requests for my employees. I will have the mailbox to be something like
[email protected] If an employee is sick or requesting time off, they can email this shared mailbox or send a meeting request.
I would then like the ability for ALL employees to be able to have read access to the mailbox and Calendar associated with it, and I would like to have managers have Full access to it and to be able to approve calendar requests so that they are entered into
the calendar.
Is this possible? How can I set read only to the inbox and calendar for a shared mailbox? I would also like to be able to have the shared mailboxes automatically added to all user's Outlook.
Thanks!

Simply grant Full Access to the managers. Then for everyone else you can grant read only access to just the Calendar.
Here is an example on how to do this -
http://exchangeshare.wordpress.com/2009/07/07/how-to-setup-read-only-mailbox-in-exchange-20032007/.
Let me know if that works.
JAUCG - Please remeber to mark replies as helpful if they were or as answered if I provided a solution.

Exchange 2010 users cannot open Exchange 2013 shared mailbox

Title says it all.
We're in the process of migrating 1000+ mailboxes to Exchange 2013. A number of shared mailboxes have been migrated, but those users still on 2010 cannot open them.
Is this just how it is, or is there a way around it?

Hi,
I tested in my lab, if the shared mailbox is on Exchange 2010, I could open this shared mailbox successfully. Then I moved this shared mailbox to Exchange 2013, after that, I couldn’t open it anymore, I got the following error:
Besides, I tried to open a shared mailbox on Exchange 2013 which was not moved from Exchange 2010, it is the same error message.
Based on the test, it seems that Exchange 2010 users can’t open shared mailbox on Exchange 2013. So I recommend you move those users to Exchange 2013.
Best regards,
Belinda Ma
TechNet Community Support

Exchange 2013 Health Mailbox filling up security logs

I'm doing security audits and having the Exchange 2013 Health Mailbox fill up my security logs. I've read that if I delete the mailboxes and re-create them and restart the service the errors will go away. My question is how do I delete them?
I found the full mailbox name with this command.
get-mailbox -monitoring | select-object -expandproperty name
Do I use this method?
Remove-Mailbox -Identity contoso\johnor this one?Remove-Mailbox -Identity contoso\john -Permanent $trueOr something else?
Thanks!
Fernando

I did help on the setup in Exchange server folder. Looks like prepares Active Directory forest for Exchange Install. /PrepareAD, /p So this is what I'm supposed to run?
C:\Program Files\Microsoft\Exchange Server\V15\Bin>setup /?
Welcome to Microsoft Exchange Server 2013 Cumulative Update 3 Unattended Setup
For detailed help, type one of the following options:
Setup /help:Install - Install Exchange server roles.
Setup /help:Upgrade - Upgrade an existing Exchange server.
Setup /help:Uninstall - Uninstall Exchange server roles.
Setup /help:RecoverServer - Recover an existing Exchange server.
Setup /help:PrepareTopology - Prepare your topology for Exchange.
Setup /help:Delegation - Delegate server installations.
Setup /help:UmLanguagePacks - Add or remove Unified Messaging
language packs.
C:\Program Files\Microsoft\Exchange Server\V15\Bin>Setup /help:PrepareTopology
Welcome to Microsoft Exchange Server 2013 Cumulative Update 3 Unattended Setup
Microsoft Exchange Server 2013 Setup Parameter Help
Prepare Topology Usage:
Setup /PrepareAD [<OptionalParameters>]
/IAcceptExchangeServerLicenseTerms
Setup /PrepareSchema [<OptionalParameters>]
/IAcceptExchangeServerLicenseTerms
Setup /PrepareDomain [<OptionalParameters>]
/IAcceptExchangeServerLicenseTerms
Setup /PrepareDomain:<domainA, domainB> [<OptionalParameters>]
/IAcceptExchangeServerLicenseTerms
Setup /PrepareAllDomains [<OptionalParameters>]
/IAcceptExchangeServerLicenseTerms
--Prepare Topology Required Parameters--
/PrepareAD, /p
Prepares the Active Directory forest for the Exchange
installation.
Fernando

Exchange 2007 shared mailbox

How do you connect an exchange 2007 shared mailbox to your iphone? Normal "user" mailboxes work just fine. Is this supported by Apple and or Microsoft?

Hi
You can not control this behaviour from Exchange. This is controlled by Outlook.
Outlook chooses the from address from what additional mailbox you are replying from (just as you see :-))
There are a lot of registry tweaks for Outlook, but I don't think there are one to control this.
I see 3 possible sollutions.
1. The users can choose them self
2. You give the users "Send As" permissions on the mailbox
3. you use this tool
http://www.ivasoft.biz/setfrom2013.shtml
BR
Steen

Exchange 2010 Mailbox Users Cannot Access 2013 Shared Mailboxes

Hi Guys & Girls,
I've a painful issue with my environment which is made up of 1 x 2010 CAS server with 1x 2010 Mailbox server and 1x 2013 CAS server with 1 x 2013 mailbox server.
The users who've yet to be migrated to 2013 and are still on the 2010 server are unable to open shared mailboxes which have already been migrated to 2013.
When trying to access shared mailboxes on the 2013 servers they received the following error:
The configuration of OutlookAnywhere on my two CAS servers is as follows:
RunspaceId : aed28f13-cdd2-4dcf-a0a8-96b8e2518171
ServerName : THCAS1
SSLOffloading : True
ExternalHostname : mail.resourcegroup.co.uk
InternalHostname : mail.resourcegroup.co.uk
ExternalClientAuthenticationMethod : Ntlm
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods : {Ntlm}
XropUrl :
ExternalClientsRequireSsl : True
InternalClientsRequireSsl : False
MetabasePath : IIS://THCAS1.ResourceGroup.co.uk/W3SVC/1/ROOT/Rpc
Path : C:\Windows\System32\RpcProxy
ExtendedProtectionTokenChecking : None
ExtendedProtectionFlags : {}
ExtendedProtectionSPNList : {}
AdminDisplayVersion : Version 14.3 (Build 123.4)
Server : THCAS1
AdminDisplayName :
ExchangeVersion : 0.10 (14.0.100.0)
Name : Rpc (Default Web Site)
DistinguishedName : CN=Rpc (Default Web Site),CN=HTTP,CN=Protocols,CN=THCAS1,CN=Servers,CN=Exchange
Administrative Group (FYDIBOHF23SPDLT),CN=Administrative
Groups,CN=ResourceGroup,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=ResourceGroup,DC=co,DC=uk
Identity : THCAS1\Rpc (Default Web Site)
Guid : 71f76f2a-4ee1-4a9a-b2da-06d79e975403
ObjectCategory : ResourceGroup.co.uk/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
ObjectClass : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
WhenChanged : 26/11/2013 16:23:13
WhenCreated : 25/11/2013 16:33:45
WhenChangedUTC : 26/11/2013 16:23:13
WhenCreatedUTC : 25/11/2013 16:33:45
OrganizationId :
OriginatingServer : thdc1.ResourceGroup.co.uk
IsValid : True
ObjectState : Changed
RunspaceId : aed28f13-cdd2-4dcf-a0a8-96b8e2518171
ServerName : THCAS2
SSLOffloading : True
ExternalHostname : thcas2.resourcegroup.co.uk
InternalHostname : thcas2.resourcegroup.co.uk
ExternalClientAuthenticationMethod : Ntlm
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods : {Basic, Ntlm, Negotiate}
XropUrl :
ExternalClientsRequireSsl : True
InternalClientsRequireSsl : False
MetabasePath : IIS://THCAS2.ResourceGroup.co.uk/W3SVC/1/ROOT/Rpc
Path : C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\rpc
ExtendedProtectionTokenChecking : None
ExtendedProtectionFlags : {}
ExtendedProtectionSPNList : {}
AdminDisplayVersion : Version 15.0 (Build 712.24)
Server : THCAS2
AdminDisplayName :
ExchangeVersion : 0.20 (15.0.0.0)
Name : Rpc (Default Web Site)
DistinguishedName : CN=Rpc (Default Web Site),CN=HTTP,CN=Protocols,CN=THCAS2,CN=Servers,CN=Exchange
Administrative Group (FYDIBOHF23SPDLT),CN=Administrative
Groups,CN=ResourceGroup,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=ResourceGroup,DC=co,DC=uk
Identity : THCAS2\Rpc (Default Web Site)
Guid : 39c5133f-14cb-4d44-ae9c-69f7fb0fc432
ObjectCategory : ResourceGroup.co.uk/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
ObjectClass : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
WhenChanged : 26/11/2013 16:23:05
WhenCreated : 26/11/2013 12:49:17
WhenChangedUTC : 26/11/2013 16:23:05
WhenCreatedUTC : 26/11/2013 12:49:17
OrganizationId :
OriginatingServer : thdc1.ResourceGroup.co.uk
IsValid : True
ObjectState : Changed
If anyone could offer any help it'd be much appreciated, it's going to take several days to migrate my remaining 2010 users to 2013 which is causing a lot of use complaints.

Hi Seb,
Try the following please.
1- Remove the existing assigned mailbox permission from the mailbox.
2- Assign the permission (Add-MailboxPermission) with -AutoMapping value set to $false.
3- Launch Outlook. Then add the mailbox manually as an additional mailbox from the Account Settings. (Access to the mailbox by only following this step would also work but your user's then will have the same mailbox displayed twice hence
step 1 & 2)
ecsword

Exchange Server 2013 - Shared mailbox audit

Is shared mailbox auditing possible in exchange 2013? I want to see which users deleted/moved.. specific mails. I turned on mailbox auditing but when I want to access the data I receive:
There is no audit log of the mailbox associated with this user. The log is removed.

Hi Nick,
The
Mailbox audit logging is available in Exchange 2013. By using mailbox audit logging, you can log mailbox access by mailbox owners, delegates (including administrators with full access permissions to mailboxes), and administrators.
Please run the following command to check the Audit logging settings for the problematic user:
Get-Mailbox -Identity Shared1 | FL Identity,*Audit*
We can run the following command to enable and set Audit Logging for a mailbox:
Set-Mailbox -Identity Shared1 -AuditEnabled $True -AuditDelegate Update,Move,MoveToDeletedItems,SoftDelete,HardDelete,FolderBind,SendAs,SendOnBehalf,Create -AuditOwner Update,Move,MoveToDeletedItems,SoftDelete,HardDelete
Then we can do some operation in Shared mailbox, and use the
Search-MailboxAuditLog cmdlet to synchronously search mailbox audit log entries for a single mailbox. Additionally, we can use the
Auditing tab in the EAC to run a non-owner mailbox access report or export entries from the mailbox audit log.
Regards,
Winnie Liang
TechNet Community Support

Exchange 2013: Correcting mailbox delegation - Full Access

Not sure how to correct this issue. I have an Admin that setup the Exchange 2013. The admins account is now added to every new account (Resources, shared mailboxes etc.) I know how to remove the auto mapping so it does not show in the admin
OWA and outlook.
I would like to just correct the setting so the account is not automatically added. (Tester is not the real name of the account.)

Hi Friday77,
Check the AdminAuditLogs to see by who and when it is getting added.
View the administrator audit log
Search the role group changes or administrator audit logs
Search-AdminAuditLog -StartDate 05/04/2015 -EndDate 10/04/2015 -ObjectID contoso.com/Users/NewUSerName1
Search-AdminAuditLog -Cmdlets Add-MailboxPermission -Parameters AccessRights -StartDate 05/04/2015 -EndDate 10/04/2015
Normally this wouldn't be the case, however you might want to have a look at this as well.
Get-CmdletExtensionAgent "Mailbox Permissions Agent"
Cmdlet extension agents are components in Microsoft Exchange Server 2013 invoked by Exchange 2013 cmdlets when the cmdlets run.
Agents can modify, replace, or extend functionality of Exchange Management Shell cmdlets. An agent can provide a value for a required parameter that isn't provided on a command, override a value provided by a user, perform other actions outside of the cmdlet
workflow while a cmdlet runs, and more.
You can use the Scripting agent cmdlet extension agent in Exchange 2013 to insert your own scripting logic into the execution of Exchange cmdlets. Using the
Scripting agent, you can add conditions, override values, and set up reporting.
Every Exchange 2013 server includes the file ScriptingAgentConfig.xml.sample in the <installation path>\V15\Bin\CmdletExtensionAgents folder. This file must be renamed to ScriptingAgentConfig.xml on every Exchange 2013 server if you enable
the Scripting Agent cmdlet extension agent.
If its still .xml.sample, no need to worry about it.
Regards,
Satyajit
Please“Vote As Helpful”
if you find my contribution useful or “MarkAs Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

Exchange 2013 shell mailbox move requests showing up on 2010 hub server

We're in the process of migrating from exchange 2010 to 2013. All servers are patched and up to date. We have two 2010 CASs (one for external OWA use only) and a mailbox cluster. Our exchange 2013 setup is almost a mirror with the exceptions of how the exchange
server roles have changed.
Any new-moverequest commands entered from the either of our exchange 2013 CAS servers fail to show up in the EAC/recipients/migration page.
If the local move request is done in the EAC the batch(es) show up just fine.
The more perplexing part is: while I was going through a 2010 hub (looking for a different issue) I noticed ALL the batches/mailbox moves that weren't showing up in the 2013 EAC were listed in the 2010 move request section.
I can't get any info on the moves in the 2010 console (because they're 2013 jobs) but i can get statistics and such from a 2013 shell.
any ideas?

Are you running ex2013SP1 CU6? Can you try to update n check?
Thanks, MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Outlook 2007 - single profile connecting to Exchange 2013 / 2007 mailboxes

Hi,
I am in the early part of a migration from Exchange 2007 to Exchange 2013. So far I have 2013 installed and running in a DAG and just moved my own mailbox to the new server.
I set up a new profile in Outlook 2007 which connects to my mailbox on Exchange 2013. The problem is that I need to add additional mailboxes to my profile which are still hosted on Exchange 2007, however this is not working.
I thought at one stage I tested this and was able to get it work with a test mailbox also hosted on Exchange 2013.. but maybe I never did.
Does anyone know if this is possible at all (single Outlook profile, primary mailbox hosted on Exchange 2013 and other mailboxes on Exchange 2007). Most of our users have an additional mailbox mapped in their profile so I hope there is some way around this.
Thank you!

Hi,
It is possible to open a shared mailboxes on a legacy server.
Your problem could be caused by:
Not having one of the later CU installed (read CU4 or CU5)
Incorrect authentication methods configured (see link below)
Outlook is not at the latest patch level
Users of Exchange Server 2013 can't open public folders or shared mailboxes on an Exchange 2010 or Exchange 2007 server
http://support.microsoft.com/kb/2834139
Martina Miskovic

Exchange 2010 mailbox not able to access auto-mapped Exchange 2013 CU3 mailbox

Hi,
We are in co-existence with Exchange 2010 SP3 and Exchange 2013 CU3.
Outlook Anywhere and Autodiscover pointed towards Exchange 2013 CAS servers. Everything works fine irrespective where is mailbox is located Exchange 2010 or 2013.
When I tried to access auto-mapped mailbox from Exchange 2010 as primary mailbox accessing auto-mapped Exchange 2013 mailbox "Cannot expand the folder. The set of folders cannot be opened. Microsoft Exchange is not available. Either there are network
problems or the Exchange server is down for maintenance".
Exchange 2013 OutlookAnywhere "Externalclientauthenticationmethod" is Basic and "Internalclientauthencitcationmethod" is NTLM. Everything is setup as per the Tech-net recommendations.
Checked both these articles but still it is not working:
http://support.microsoft.com/kb/2839517
http://support.microsoft.com/kb/2834139
Please let me know if there are any other ideas.
Raman

Hi,
I recommend you refer to the following articles to troubleshoot the issue:
Troubleshooting Mailbox Auto-Mapping : Autodiscover
Details about the shared mailbox that is to be accessed will be returned to the Outlook client by the autodiscover process. This is really handy to know if you are ever in the position where you need to troubleshoot why the auto-mapping feature isn’t working
correctly
Troubleshooting Mailbox Auto-Mapping : Permissions
When you use either the Exchange Management Console or the Exchange Management Shell to grant a user with full access permission against another mailbox, permissions changes are made to allow this as you might expect. Certain Active Directory attributes
are also updated to reflect both the Active Directory account of the mailbox being accessed as well as the Active Directory account of the accessing mailbox. Specifically, you can check the contents of the msExchDelegateListLink and msExchDelegateListBL Active
Directory attributes to see these details and it is worth checking these if you have any suspicions that things aren’t working correctly.
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support

Office 365/Outlook 2013 Shared Mailbox Sent Items Problem

I've only been able to find an answer for this problem for Outlook 2010, and that doesn't work for 2013.
I'm trying to make the sent items for a shared mailbox save to the sent items of that mailbox, not my mailbox. I got the deleted items to finally work, I just need to get the sent items to work now.
I've read about this key:
HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Outlook\Options\Conversations
But I don't have the conversations folder, should I make it?
I've also seen this:
HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\Preferences\DelegateSentItemsStyle
But that doesn't seem to work with Office 2013.
Any ideas?
Thanks

We have the same problem with a client. We are using Office 365 with Outlook 2013 on a RDS Windows Server 2012 R2. I can't find the HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Outlook\Preferences
folder in the registry. HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\ is as far as it gets.
Even when we sent from the Office 365 online mailbox and fill in the from address, the sent mail is stored in the sent items folder from the user instead of the shared mailbox.
I've searched everywhere for a solution, but I haven't found one yet.
Regards,
Steve
If a key does not exist, you need to add it - Outlook doesn't create keys it's not using. :)
Diane Poremsky [MVP - Outlook]
Outlook & Exchange Solutions Center
Outlook Tips
Subscribe to Exchange Messaging Outlook weekly newsletter

Exchange 2013 Monitoring Mailboxes

I'm running exchange 2013 and it seems to have problems with health mailboxes (monitoring mailboxes). I have 5 mailbox databases on this server, DB1, DB2, DB3, DB4 and DB5.
I know there are 2 health mailboxes per mailbox database.
The command `Get-Mailbox -monitoring | Get-MailBoxStatistics` shows that several of these have not been accessed since December, even though they are in mounted Databases and powershell shows they are healthy.
There is also 2 health mailboxes that are missing from the below output because I got warninings saying these mailboxes have not been logged into yet.
[PS] C:\windows\system32> Get-Mailbox -monitoring | Get-MailBoxStatistics
DisplayName : HealthMailbox98fb2dc7692341ad8a3325ea2b14bbcc
ItemCount : 17426
LastLogonTime : 12/8/2012 3:28:04 PM
Database : DB1
DisplayName : HealthMailboxe27d88df28ae4d53af620604a83aca4d
ItemCount : 12386
LastLogonTime : 2/4/2013 3:29:46 PM
Database : DB1
DisplayName : HealthMailbox815f0ff077a342f7889a53ef38e40256
ItemCount : 291
LastLogonTime : 12/8/2012 3:26:43 PM
Database : DB3
DisplayName : HealthMailboxbca2f3409f1d4ae99098f48b574fc36d
ItemCount : 579
LastLogonTime : 12/8/2012 3:26:05 PM
Database : DB2
DisplayName : HealthMailbox2412e1a0e5d9415b8328f653b2e42efe
ItemCount : 209
LastLogonTime : 2/3/2013 6:08:41 PM
Database : DB3
DisplayName : HealthMailbox594b739a129941e688eafee6bbdfece6
ItemCount : 209
LastLogonTime : 2/3/2013 6:09:52 PM
Database : DB2
DisplayName : HealthMailboxc401cae2a70d4d659f5758908582406e
ItemCount : 210
LastLogonTime : 2/4/2013 3:28:59 PM
Database : DB4
DisplayName : HealthMailbox4b81211d555c4accad1f61a98700382e
ItemCount : 212
LastLogonTime : 2/3/2013 6:09:46 PM
Database : DB5
Warning: The user hasn't logged onto mailbox `<AD Domain>/users/HealthMailbox2c62876ca1bb45849c0daf2ecee6d715`, so there is no data to return. After the user logs on, this warning will no longer appear.
Warning: The user hasn't logged onto mailbox `<AD Domain>/users/HealthMailbox4399c592609a464d95c993ecee46f671`, so there is no data to return. After the user logs on, this warning will no longer appear.
I am also getting a lot of queued messages in the inboundproxy.com queue that have the subject line "Undelieverable: Inbound Proxy Probe". I dont know how to get these to stop. I just have to clean out the queue once a day to prevent it from getting
to large.
The last thing I notice is that I get a lot of audit errors in the event log when the system is trying to login to these mailboxes. That might be what is causing the issue. Here is one of the messages:
An account failed to log on.
Subject:
Security ID:
SYSTEM
Account Name:
<computer name here>$
Account Domain:
<AD DOMAIN>
Logon ID:
0x3E7
Logon Type: 8
Account For Which Logon Failed:
Security ID:
NULL SID
Account Name:
HealthMailboxbca2f3409f1d4ae99098f48b574fc36d@<domain.tld>
Account Domain:
Failure Information:
Failure Reason:
Unknown user name or bad password.
Status:
0xC000006D
Sub Status:
0xC0000064
Process Information:
Caller Process ID:
0x1265c
Caller Process Name:
C:\Windows\System32\inetsrv\w3wp.exe
Network Information:
Workstation Name:
<computer name here>
Source Network Address:
::1
Source Port:
34602
Detailed Authentication Information:
Logon Process:
Advapi
Authentication Package:
Negotiate
Transited Services:
Package Name (NTLM only):
Key Length:
0
This event is generated when a logon request fails. It is generated on the computer where access was attempted.
The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).
The Process Information fields indicate which account and process on the system requested the logon.
The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
The authentication information fields provide detailed information about this specific logon request.
- Transited services indicate which intermediate services have participated in this logon request.
- Package name indicates which sub-protocol was used among the NTLM protocols.
- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
As you can see, the system can not login to to this health mailbox account. The one in my example one of the mailboxes that has not been logged into since december.
Is there anywhere to troubleshoot these? or possibly rebuild them? The is a huge lack of documentation on these mailboxes from microsoft, I can not find any commands to interact with these other then 'get-mailbox -monitoring'

Because I KNOW it can lead to problems and do NOT know whether it can ever help me or not.
Here is one example of why I don't want it enabled:
http://social.technet.microsoft.com/Forums/exchange/en-US/7ed96489-92dd-441a-93e0-3d805b807dc3/maildeliveryprobemaildeliveryprobecom-and-inboundproxyinboundproxycom-in-the-logs
In my opinion there's one more strangeness about Managed Availability in Exchange 2013:
http://blogs.technet.com/b/exchange/archive/2012/09/21/lessons-from-the-datacenter-managed-availability.aspx
"When something is unhealthy its first action is to attempt to recover that component. Managed Availability provides multi-stage recovery actions – the first attempt might be to restart the application pool, the second attempt might
be to restart service, the third attempt might be to restart the server, and
the final attempt may be to offline the server so that it no longer accepts traffic.
If these attempts fail, managed availability
then escalates the issue to a human through event log notification."
...am I getting it right that Managed Availability is not going to alert an administrator BEFORE restarting/taking the server offline...just AFTER and in case it was unable to fix the issue??????!!!!!

Exchange 2013 - Shared Calendar problems

Since we put in Exchange 2013 in July 2013 we have had a problem with Shared Calendars. Even though a User has Owner Permission on another Calendar, New Appointment is Grayed Out and the User cannot add or amend and occasionally Outlook will hang.
We have tried Outlook 2010 and 2013 Clients as well as Cached Mode and Online Access. Exchange Server Standard 2013 CU2 was installed and this seemed to stop the problem for a while and now it has returned.
Permissions have been removed and reapplied both through the Exchange Powershell Interface and on the Mailbox. All other aspects of the system seem fine.
Any advice would be welcome.

Hi,
Please check your application logs in your Exchange server. Confirm whether there are some error logs such as Event 9646.
It may because there are too many users connect to shared calendar at the same time that cause this issue. And there is a limit on the number of items that clients can open.
If so, we can change regedit
on the Exchange computer to resolve this issue. For more information, please click the following KB:
http://support.microsoft.com/kb/830836/en-us
Thanks,
Winnie
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Exchange 2013 Shared Mailbox Get-MailboxSentItemsConfiguration SP1 Help

Similar Messages

Maybe you are looking for