At a client there is a Exchange 2007 Server whic hosts a lot of shared mailboxes and legacy software. For about 200 mailboxes they run a scheduled acript which deletes mailitems from those mailboxes. The script uses the following Syntax:

$EndDate180=(Get-Date).Adddays(-184)
Export-Mailbox -Identity Mailbox -IncludeFolders “\Back-up”  -DeleteContent -confirm:$false -EndDate $Enddate180

In Exchange 2010 SP1 this is not supported anymore so there must be an alternative. I created the following script:

$EndDate180=(Get-Date).Adddays(-184)
Get-Mailbox [mailbox] | Search-Mailbox -searchquery {received<$EndDate180}–SearchDumpster –deletecontent –confirm:$false

The problem is, it deletes also items from folders outside "\Back-up".

How to fix this?

Hello!

I created a custom DSN message for the 5.1.1 code but Exchange still presents the default one:

???

Thank you in advance,

Michael

Hi

We have several SMTP domains that are accepted on our Exchange Edge MTA. For testing purposes I'd like the outgoing mails from one of these domains to flow through a different external host.

In other words, my default send-to-internet connector uses the * SMTP address space, and MX records to send out mail. So all my outgoing mail is send by my Edge server to whatever external SMTP server it located through MX lookups.
But I want outgoung mails from one of my internal SMTP accepted domains to not go to the SMTP server of the destination domain directly (using MX lookup), but to another external host instead. This host will then send to the destination SMTP using MX lookup.
I know how to do it for all my domains (change the send connector and make it use a Smart-host), but then all my outgoing mail will use this, and I just want to do it for one SMTP domain.

I actually need a check on source SMTP address in the Address space window of the send connector. But, it's not there ;)

Anyone ?

Greetings

After performing this update on our server, I noticed now users can no longer recover items from deleted items in OWA. The page always errors out now.

The KB installed was KB3011140

:-(
something went wrong
Sorry, we can't get that information right now. Please try again later. If the problem continues, contact your helpdesk.

X-OWA-Error: ClientError;exMsg=Sys.ArgumentException: Value does not fall within the expected range.Parameter name: Unknown type _d.$Vq was requested;file=$7CD@https://whatever.com/OWA/prem/15.0.847.34/scripts/boot.1.mouse.js:1:1170608_t.PopoutStartupViewModelFactory.prototype.$E/<@https://whatever.com/OWA/prem/15.0.847.34/scripts/boot.1.mouse.js:1:1171022_a.$Z0.prototype.$5V3/<@https://whatever.com/OWA/prem/15.0.847.34/scripts/boot.0.mouse.js:91:294125_a.$2r.$5e5@https://whatever.com/OWA/prem/15.0.847.34/scripts/boot.0.mouse.js:91:601482_a.$2r.$iS@https://whatever.com/OWA/prem/15.0.847.34/scripts/boot.0.mouse.js:91:600669_a.$Sd.$9lW@https://whatever.com/OWA/prem/15.0.847.34/scripts/boot.0.mouse.js:91:369272$1mX@https://whatever.com/OWA/prem/15.0.847.34/scripts/boot.0.mouse.js:91:27237$4pt@https://whatever.com/OWA/prem/15.0.847.34/scripts/boot.0.mouse.js:91:27789_js.$J.prototype.$6Kk@https://whatever.com/OWA/prem/15.0.847.34/scripts/boot.0.mouse.js:91:32733Function.createDelegate/<@https://whatever.com/OWA/prem/15.0.847.34/scripts/preboot.js:34:39109_a.$2r.$5e5@https://whatever.com/OWA/prem/15.0.847.34/scripts/boot.0.mouse.js:91:601482_a.$2r.$iS@https://whatever.com/OWA/prem/15.0.847.34/scripts/boot.0.mouse.js:91:600669_a.$Sd.$9lW@https://whatever.com/OWA/prem/15.0.847.34/scripts/boot.0.mouse.js:91:369272$1mX@https://whatever.com/OWA/prem/15.0.847.34/scripts/boot.0.mouse.js:91:27237$2gl/s@https://whatever.com/OWA/prem/15.0.847.34/scripts/boot.0.mouse.js:91:28216:1170608
X-OWA-Version: 15.0.847.34
X-FEServer: SERVERNAME
X-BEServer: null
Date: 1/2/1601 3:22:42 PM

Hello,

I'm running an Exchange 2013 CU6 environment.  I have two DAGs, and I was able to migrate users off my Exchange 2007 environment without an issue.  However, I have since created a couple more mailbox databases.  Whenever I do an inter-Exchange 2013 move, it creates new calendar, contacts, drafts, and junk email folders (Calendar1, Contacts1, etc).  Those folders become the default folders for those items.  The first two obviously being the biggest problem because users have their default calendars and contacts folders taken out of the picture, and it converts those folders to "mail item" folders.  They cannot be changed back.  This first started happening when I was at a CU3 patch level, and I read that it was a known issue that was solved in CU6.  My entire environment is CU6 now with plenty of reboots and service restarts since CU6 was installed.  

I just created a new mailbox DB, and I'm still experiencing the same issue.  I'd like to avoid a call with Microsoft if possible, but I'm stumped.  Has anybody successfully troubleshot similar behavior?  Thanks!

TAG

Hi

We have 2 CAS server and 2 MailBox servers in DAG, the problem began when I add a new user, the user is created in the ECP and appear there very well, but if I try to send a mail, returns an email: Remote Server returned '550 5.1.1 RESOLVER.ADR.RecipNotFound; not found', if I try to open an OWA sesion it ask me the languaje and the local hour, but after that it returns: X-OWA-Error: Microsoft.Exchange.Data.Storage.MailboxUnavailableException

This problem is for all the new users, the previous users does not have problems.

In the Event Viewer in Exchange Management, only appear the EventID1:

Cmdlet suceeded. Cmdlet New-Mailbox, parameters -ResetPasswordOnNextLogon "False" -LastName "Test 3" -UserPrincipalName "hse3@domain.com.mx" -Alias "hse3" -Password "System.Security.SecureString" -DisplayName "Hector Test 3" -Database "2013-USR01" -FirstName "Hector" -Name "Hector Test 3".

Even I ran a "New-MailboxRepairRequest", but it shows that the user has not logged on to mailbox...

Any idea or somewhere to dig?

If I open that user in the ECP, in MailBox characteristics send a Warning: "Can not open the mailbox /o=CPTMMEXEXC/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=EXCH-IL03/cn=Microsoft System Attendant"

Need help, we're growing and I can not give to the users their new mailbox

Doc MX

Exchange 2013 SP1

I use Comcast as a smart host. It needs to work on port 587. How do I change the default port to 587?

John Lenz

I have a user that when a calendar invite is sent to them it goes directly to their calendar as tentative which is fine but they never receive a message in their inbox. I am running Exchange 2013 CU7.

This is what I have tried so far but it has not helped. I disabled activesync and closed out of Outlook, but I see the same symptoms in OWA. I verified that the user has no rules or delegates. I changed the Mail Option so it does not Automatically process meeting requests and responses to meeting requests and polls. I did a couple of message traces and they look like any other message being processed.  I tried to set this command on the mailbox "Set-MailboxCalendarSettings –identity Mailbox  -AddNewRequestsTentatively  $false" but it would not let me since it is not a shared mailbox. The calendar repair assistant is turned on for all of our users. I am thinking about moving the users mailbox to another database to see if it makes a difference. If that does not work then I feel my only options is to export the users mailbox to as pst then import it into a new mailbox.

Is there anyway to get details on how a message is processed by the exchange server, so that maybe I can see why they are going straight to the calendar?

Hi,

We upgraded to Exchange 2013 last month and have recently encountered an issue setting permission on calendars.

In 2010 our guidance counselors gave contributor permissions to students. Students could see there free and busy time and could add an item. They could not edit, delete or see any details and this worked great.

Since upgrading to 2013 whenever any tries to grant contributor permissions in outlook it immediately changes to custom? The user who has been granted rights can't add any items to that calendar. Changing that users rights to any other predefined right such as say owner or editor works fine and shows as that appropriate right. Trying to change it back to contributor thought and it immediately shows as a custom right in outlook.

I have tried setting rights via power shell and in power shell it will report as contributor but shows as custom in outlook. I have also tried just setting the individual rights and not the predefined ones via both outlook and power shell and it makes on difference.

Has anyone else run across this?

We are running Exchange 2013 CU6 and our clients are Outlook 2013 as well.

Thanks!

Hello,
I'm trying to move users from one mailbox database to another. Most people are moved without errors, but the remaining 10 are not moved in error:

Error details: MapiExceptionNoAccess: Unable to query table rows. (hr=0x80070005, ec=-2147024891)
Diagnostic context:
    Lid: 55847   EMSMDBPOOL.EcPoolSessionDoRpc called [length=284]
    Lid: 43559   EMSMDBPOOL.EcPoolSessionDoRpc returned [ec=0x0][length=264][latency=0]
    Lid: 23226   --- ROP Parse Start ---
    Lid: 27962   ROP: ropGetContentsTable [5]
    Lid: 27962   ROP: ropSetColumns [18]
    Lid: 17082   ROP Error: 0x80070005
    Lid: 27489 
    Lid: 21921   StoreEc: 0x80070005
    Lid: 27962   ROP: ropExtendedError [250]
    Lid: 1494    ---- Remote Context Beg ----
    Lid: 26426   ROP: ropSetColumns [18]
    Lid: 28064 
    Lid: 13861   StoreEc: 0x80070005
    Lid: 27265   StoreEc: 0x80070005
    Lid: 1750    ---- Remote Context End ----
    Lid: 27962   ROP: ropQueryRows [21]
    Lid: 17082   ROP Error: 0x80070005
    Lid: 17153 
    Lid: 21921   StoreEc: 0x80070005
    Lid: 27962   ROP: ropExtendedError [250]
    Lid: 1494    ---- Remote Context Beg ----
    Lid: 26426   ROP: ropQueryRows [21]
    Lid: 40685   StoreEc: 0x80070005
    Lid: 28468 
    Lid: 13029   StoreEc: 0x80070005
    Lid: 26348 
    Lid: 22252   StoreEc: 0x80070005
    Lid: 1750    ---- Remote Context End ----
    Lid: 26849 
    Lid: 21817   ROP Failure: 0x80070005
    Lid: 28414 
    Lid: 32510   StoreEc: 0x80070005
   at Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message, Int32 hresult, SafeExInterfaceHandle iUnknown, Exception innerException)
   at Microsoft.Mapi.MapiTable.QueryRows(Int32 crows, QueryRowsFlags flags)
   at Microsoft.Exchange.MailboxReplicationService.LocalDestinationFolder.<>c__DisplayClass15.<SetExtendedProps>b__11()
   at Microsoft.Exchange.MailboxReplicationService.ExecutionContext.Execute(GenericCallDelegate operation)
   at Microsoft.Exchange.MailboxReplicationService.LocalDestinationFolder.SetExtendedProps(PropTag[] promotedProperties, RestrictionData[] restrictions, SortOrderData[] views)
   at Microsoft.Exchange.MailboxReplicationService.LocalDestinationMailbox.Microsoft.Exchange.MailboxReplicationService.IDestinationMailbox.CreateFolder(FolderRec sourceFolder, Boolean failIfExists, Byte[]& newFolderId)
   at Microsoft.Exchange.MailboxReplicationService.DestinationMailboxWrapper.<>c__DisplayClass6c.<Microsoft.Exchange.MailboxReplicationService.IDestinationMailbox.CreateFolder>b__6b()
   at Microsoft.Exchange.MailboxReplicationService.ExecutionContext.Execute(GenericCallDelegate operation)
   at Microsoft.Exchange.MailboxReplicationService.DestinationMailboxWrapper.Microsoft.Exchange.MailboxReplicationService.IDestinationMailbox.CreateFolder(FolderRec sourceFolder, Boolean failIfExists, Byte[]& newFolderId)
   at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.<>c__DisplayClass36.<>c__DisplayClass38.<CreateFolderHierarchy>b__31()
   at Microsoft.Exchange.MailboxReplicationService.ExecutionContext.Execute(GenericCallDelegate operation)
   at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.<>c__DisplayClass36.<CreateFolderHierarchy>b__30(FolderRecWrapper folderRec, EnumFolderContext context)
   at Microsoft.Exchange.MailboxReplicationService.FolderMap.EnumSingleFolder(FolderRecWrapper folderRec, EnumFolderContext ctx, EnumFolderCallback callback, EnumHierarchyFlags flags)
   at Microsoft.Exchange.MailboxReplicationService.FolderMap.EnumSingleFolder(FolderRecWrapper folderRec, EnumFolderContext ctx, EnumFolderCallback callback, EnumHierarchyFlags flags)
   at Microsoft.Exchange.MailboxReplicationService.FolderMap.EnumSingleFolder(FolderRecWrapper folderRec, EnumFolderContext ctx, EnumFolderCallback callback, EnumHierarchyFlags flags)
   at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.<CreateFolderHierarchy>b__2f(MailboxMover mbxCtx)
   at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.ForeachMailboxContext(MailboxMoverDelegate del)
   at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.CreateFolderHierarchy(Object[] wiParams)
   at Microsoft.Exchange.MailboxReplicationService.CommonUtils.CatchKnownExceptions(GenericCallDelegate del, FailureDelegate failureDelegate)
Error context: --------
Operation: LocalDestinationFolder.SetPromotedProps
PropTags: [ExpiryTime; ReplyTime; SentRepresentingName; MessageToMe; MessageCcMe; SentRepresentingEmailAddress; DisplayBcc; DisplayCc; DisplayTo; 237699075; 245497859; Body; 276824067; 277872643; 278200323; ItemTemporaryFlag; ContentCount; 921436163; 921567235; 1737359391; 1748172872; 1748238339; 1748631555; 1749090307; 1749156098; 1750401035; 1750466591; 1750532107; 1750663199; 1750990851; 1845559299; 1879441439; 1879506947; 0x80000102(NamedProp); 0x80010003(NamedProp); 0x8003101f(NamedProp); 0x80290003(NamedProp); 0x802b0003(NamedProp); 0x8031000b(NamedProp); 0x80320040(NamedProp); 0x8074000b(NamedProp); 0x80940040(NamedProp); 0x80950040(NamedProp); 0x80980003(NamedProp); 0x809e000b(NamedProp); 0x80d20003(NamedProp); 0x80d30102(NamedProp); 0x80d50003(NamedProp); 0x80d9000b(NamedProp); 0x80db0003(NamedProp); 0x80dc001f(NamedProp); 0x844c0003(NamedProp)]

I have tried to add the option to request:  -BadItemLimit '100' -LargeItemLimit 50 -AcceptLargeDataLoss -AllowLargeItems
I run New-MailboxRepairRequest for mailbox and database: -CorruptionType ProvisionedFolder, SearchFolder, AggregateCounts, FolderView
Open mailbox with MFCMapi and delete rules

Please help how to solve this problem?

I've had my Samsung S4 for several months and everything worked w/o issue until 12/13/2013 when Verizon did a software update "update_SCH-1545_MJ7_to_MK2". 

Prior to this update, my phone was synced to my work account without any issues. For several years before that, I had other phones synced as well, all without issue. Since this update, all of my contacts/tasks/calendar work just fine.

The problem is with the email, I cannot get email to sync past 12/10/2013. The phone syncs up and loads emails dating back to 2007, but it will not give me any email past 12/10/2013. I've tried uninstalling/reinstalling, changing push to every 5 minutes, resetting the phone. Nothing works. 

I've spoken with our IT department, they can't figure it out. They referred me to Verizon. I've taken it to Verizon, no one there seems to have a clue. I even asked them to revert my phone to the prior software version, but they claim it's not possible. 

One of the main issues I believe is the inability of the new software to allow me to access the port #'s being used. I recall the prior version of software to allow me to change these, the new version does not allow or even show what port it's using. 

Any help would be greatly appreciated.

I believe we are running Windows XP, unsure of the version of Outlook. We are a small city government, so newer software (2007/2010/2013) is highly unlikely anytime soon. 

TMMR03

Hello

We have 2 Exchange 2013 CU7 servers.

Sometime I get an error message on phones that says it cannot log in.

I can see from event log that

[Eas] The number of outstanding requests for guard TargetBackend("exch01.top.domain.no") has exceeded the max limit 150. Current request will be rejected.

Anyone know what limit its refering to? And should it be set higher?

Regards

Can I use a single DNS record for my SMTP and HTTPS services (OWA, ActiveSync)

eg. Mail.contoso.com points to public IP 212.1.1.1

I point my mx record to mail.contoso.com

I would also like to use mail.contoso.com for owa and activesync ...is this ok? IP points back to single exchange server anyway. (via firewall rule which I assume I enable for smtp and https)

also can I use same ip for autodiscover

also

After updating our Exchange servers to CU7 I noticed we had over 800 monitoring mailboxes while only having 50 active databases spread across two dags.  This resulted in a few of the health mailboxes having duplicate SMTP addresses causing unhealthy states for the HubTransport healthset.  To remedy the issue I was going to follow the procedure to delete the mailboxes and have Exchange recreate them.  Before I do this I'd like to get Exchange to correctly stamp the mailbox with the alias and default domain.

Currently we only have the default email address policy, which was changes to set the primary smtp address as <sir name>-<given name>@domain.com.  Monitoring mailboxes have neither when created.  

If I were to create another email address policy at priority 1 making the SMTP format <sir name>-<given name>@domain.com (%s-%g@domain.com) and changing the default policy to alias@domain.com would the recreation of the monitoring mailboxes use the alter default policy to stamp the SMTP addresses.

I apologize ahead as I don't have a lot of Exchange experience.  Just enough to be dangerous.

I just started with a new company and they asked me to work on setting up TLS between us and another company.  The other company has sent me the domain name(s) they want us to use.

We are using Office 365.  So my access to the Exchange server is via the Office 365 Portal (https://portal.office.com/Home).

HISTORY:  I was told that a former coworker changed some settings on the Send Connector and, in their words, "broke Exchange".  So, they changed everything back.

As I understand it, Exchange 2010 and above uses optimistic TLS.

I have used CheckTLS.com and verified that our server and the other company's server supports TLS.

QUESTION(s):

Should I set up a second Send Connector to communicate TLS only with the other company?

Do I have to set up a second Receive Connector?

Do I have to use a 3rd party CA?

What questions should I ask the other company in regards to their TLS settings?

Thanks for your help in advance.

Hi there,

Try as I might, I cannot get Exchange 2013 to install on a Server 2008 R2 domain.

Previously tried installing, but it repeatedly failed complaining about IPv6 being disabled. Re-enabled IPv6 and attempted to no avail (same error). However, the modifications have already been made to Active Directory.

Now trying in a fresh installation of Windows, and get these errors (below). The errors are wrong: the accountis a member of Enterprise Admins for example.

Please advise.

-----------------------------

Error:
Global updates need to be made to Active Directory, and this user account isn't a member of the 'Enterprise Admins' group.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.GlobalUpdateRequired.aspx

Error:
You must be a member of the 'Organization Management' role group or a member of the 'Enterprise Admins' group to continue.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.GlobalServerInstall.aspx

Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedBridgeheadFirstInstall.aspx

Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedMailboxFirstInstall.aspx

Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedClientAccessFirstInstall.aspx

Error:
You must use an account that's a member of the Organization Management role group to install the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedUnifiedMessagingFirstInstall.aspx

Error:
The NetBIOS name of the computer doesn't match the DNS host name. Ensure that the NetBIOS name isn't truncated due to the 15-character limit.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ComputerNameDiscrepancy.aspx

Error:
Setup encountered a problem while validating the state of Active Directory: Couldn't find the Enterprise Organization container.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.AdInitErrorRule.aspx

Error:
The forest functional level of the current Active Directory forest is not Windows Server 2003 native or later. To install Exchange Server 2013, the forest functional level must be at least Windows Server 2003 native.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ForestLevelNotWin2003Native.aspx

Error:
This computer requires the update described in Microsoft Knowledge Base article KB974405 (http://go.microsoft.com/fwlink/?LinkId=262357). Please install the update, and then restart Setup.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.Win7WindowsIdentityFoundationUpdateNotInstalled.aspx

Error:
Either Active Directory doesn't exist, or it can't be contacted.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.CannotAccessAD.aspx

Warning:
Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have been detected in this topology. After this operation, you will not be able to install any Exchange 2010 servers.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.aspx