A previous admin installed a trail edition of Exchange 2013 in our 2007 environment for testing.  When he tried to uninstall it there was an issue and it left some Exchange AD debris in the Active Directory structure.  

Surprise, but now he is nowhere to be found.........

Now the company is going to upgrade and we cannot install Exchange 2013 because of these mailbox errors.  The old server and database has been cleared out of ADSI and the one user that was in the old 2013 database has had all the Exchange attributes cleared from their AD profile.

We are still getting the "Database is mandatory on UserMailbox" error when I try to install Exch2013 on the new server.  I tend to think there is some other mail-enabled object in AD that is causing the conflict, but I cannot find it.\

Obviously I cannot nuke the entire ADSI Exchange folder, because I still need 2007 to work.  :-)

Any help would be appreciated......

I've configured MAPI over HTTP in my testing environment. It is working fine. But i'm unable to test this configuration using the Powershell Test-OutlookConnectivity CMDlet.

Outlook is working fine and is using MAPI over HTTP, so i'm pretty sure there are no configuration problems. But the CMD-let gives me the following output:

[PS] C:\Windows\system32>Test-OutlookConnectivity -RunFromServerId <myserver> -ProbeIdentity OutlookMapiHttpSelfTestProbe
WARNING: An unexpected error has occurred and a Watson dump is being generated: Failed to find the probe result for
invoke now request id 1ad0cb55e6cc45c791194b34641fe3c2 and probe workdefinition id 241.
Failed to find the probe result for invoke now request id 1ad0cb55e6cc45c791194b34641fe3c2 and probe workdefinition id
241.
    + CategoryInfo          : NotSpecified: (:) [Test-OutlookConnectivity], InvalidOperationException
    + FullyQualifiedErrorId : System.InvalidOperationException,Microsoft.Exchange.Management.Tasks.TestOutlookConnecti
   vity
    + PSComputerName        : <fqdn of my serer>

Does anyone have a sollution for this?

Hi All.

I went to Upgrade from exchange 2010 sp3 running on windows 2008 r2 to exchange 2013 running on windows 2012.

I have the following servers:

1- 2 server running windows 2008 r2 with exchange 2010 sp3 with HUB - CAS role.

2- 2 server running windows 2008 r2 with exchange 2010 sp3 with MBX role.

3- 2 server running windows 2008 r2 with exchange 2010 sp3 with Edg role.

4- storage holding mailbox databases. 

what is the best scenario and the upgrade step by step ?

I am currently moving a small charity (25 mailboxes) from ex2007 to 2013 sp1, they have a domain.local LAN domain although the exchange server receives mail for domain.org.uk via smtp

They require local network access only, as they access outlook via a remote desktop server and have no demand for outlook web access from the internet.

I have seen a number of articles on installing certificates for access from outside the LAN, but I wondered what the simplest way of getting Ex 2013 to work with the local network was with regard to certificates.

e.g. in this case could I use group policy to distribute the self signed certificate? Would this work both for domain.local & domain.org.uk?

How about Microsoft CA perhaps on one of our domain controllers?

Or is there a better solution?

regards

Roga

Hi,

after read the article 'http://technet.microsoft.com/en-us/library/dd638158.aspx', we already have MBX and CAS 2007 running the lastest spk version and the SSL on the CAS 2007 is already working as 'LEGACY.DOMAIN.COM.BR' + 'Autodiscover.domain.com.br'+ 'mail.domain.com.br'.

My question is regarding the SSL request for the new server:

>>> Can I start the REQUEST for the external Certification Authority using Windows Powershell or IIS console instead to use 'Exchange Management Shell'??

* I´m afraid about the time (days) to install CAS 2010 on the new server, start the request to the CA, do the internal steps to aprove, pay the tax, wait for generation and then install the new SSL on the new server...

Hello,

I have a new Exchange 2013 installation on a small corporate network. We us an external web and email hosting company.  We would like to continue receiving our incoming email through the external email host for SPAM, antivirus, and intrusion protection. In the past we have used the MAPI Labs mail connector to poll the external mail server for email and deliver it to our internal exchange system. Previously, outgoing email was sent via SMTP directly from the client PC. I would like it so the outgoing mail was routed through Exchange and ideally, only those with external email accounts count send outside the organization.

What I have done so far is have the external email host setup a secondary MX record on the external domain (ourserver.domain.com, which differs from their mail.domain.com). ourserver.domain.com points to our public network IP address.  I then had our internet ISP create a PTR for our IP that pointed back to ourserver.domain.com. In ECP I have send connector set to use MX records with a FQDN of ourserver.domain.com; however outgoing mail is slow to deliver and is identified as SPAM using my outlook.com personal mail.

How can I get my outgoing mail to stop getting flagged as spam?  I am still using a self signed certificate for testing and get certificate errors locally, but I do not think that is related. Am I going about this correctly?

Mike Orlando

Hello,

We are in the process of migrating users from Exchange 2010 to Exchange 2013, with this I would like to batch migrate users.

What is the correct CSV format/syntax to move users? Our Exchange 2010 users have a live/archive database.

From what i've read around it say it should be..

EmailAddress,TargetDatabase,TargetArchiveDatabase,BadItemLimit
user1@domain.com,livedb1,arcdb1,25
user1@domain.com,livedb2,arcdb2,25

Is this the correct format? For "user1" I would like the live database to go into livedb1 and the archive to arcdb2.

According to this.. http://technet.microsoft.com/en-us/library/dn170437(v=exchg.150).aspx

It says.. (this is a local move, same local domain just moving to new server).

Specifies the mailbox database that the user’s archive mailbox will be moved to. You can specify a different database in the different rows of the CSV file, which lets you move archive mailboxes in the same migration batch to different databases.

Note:
If you specify a specific archive database, the archive mailbox (if it exists) will be moved to the same database as the primary mailbox.

It says if you specify a specific database, the archive mailbox will be moved to the same database as the primary mailbox ?! I need to separate the two, this is why I am specifying an archive databaase?!

Should it be like this below...?

EmailAddress,TargetDatabase,TargetArchiveDatabase,BadItemLimit
user1@domain.com,livedb1,,25
user1@domain.com,,arcdb1,25
user2@domain.com,livedb2,25
user2@domain.com,,arcdb2,25

Thanks.

After migrating relatively successfully from Exchange 2007 to 2013, I am in the process of trying to decommission and uninstall 2007 from the servers. Through this process I have been following a guide found here. Our old 2007 servers have been off for over two weeks and it seems like a good time to remove them and reclaim some space. I removed the old OAB and Mailbox DB, however when I attempted to remove the Public Folders so I could take the PF DB out the following error appeared.

Get-PublicFolder : There is no existing PublicFolder that matches the following Identity: '\'.

I know that there are Public Folders existing as I can see them when I run Get-PublicFolderStatistics:

I've been back and forth across the forums and web and haven't been able to find a solution to this. Ultimately we never have and are not interested in using public folders but they were originally configured when we had a contractor move us from 2003 > 2007 several years ago. What I would like is to remove all traces of this garbage and just be able to uninstall/delete the old servers and move on with life.

Any help is greatly appreciated. Thank you in advance.

Jon Howard

having problems on new server so I followed instructions to remove Exchange Server 2013 Sp1 using ADSI edit p;er these instructions:

http://blog.dargel.at/2012/11/20/complete-remove-exchange-2013-using-adsiedit/

now when I re-run setup for exchange 2013 SP1 I get the error :    

"Error: The type initializer for 'Microsoft.Exchange.Configuration.Tasks.ThrottlingModule`1' threw an exception."

David Sheetz MCP

So first, before you flame me, this is in QA!

We installed 2013 into a 2007 environment, then due to shifting business demand, cleanly removed 2013. Now we are trying to install 2010 CAS servers and it goes in fine, reports no errors, but I do not have 'server configuration' on the left pane of EMC, but I can run any related EMS cmdlet (so not permissions).  On the org health page all the info is listed as 'unavailable'. I'm thinking something is left over in AD's config container, but I can't find it. Help?

We will be replacing an SBS 2003 server that runs Exchange 2003 withnew hardware. There only 12 mailboxes but some are over 2GB. We will have a new server that has Exchange 2013 installed and will also be a DC and it will have a different name and FQDN from the SBS. We will be manually creating the AD with same user names that are on the SBS.

How can we get the mail from 2003 to 2013?

I am getting very frustrated. It really shouldn't take over a week to install Exchange.

I have two domain controllers, Windows 2003 and Windows 2008 R2. The 2008 is now all Operations Masters for all roles.

I have a clean install of W2K8 R2 SP1 installed under Hyper-V on a separate physical W2K8 server. Before starting the install I used ADSIEdit to ensure there was nothing left in the AD of prior Exchange install attempts. This is the first and only installation of Exchange.

I am running the install as the Domain\Administrator and naturally that account is a member of all the appropriate security groups. RSAT are installed on the Exchange server and using them to access Users and Computers clearly shows this. The install fails with the errors below, all of which appear to be incorrect.

*** BEGIN ERROR ***

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 the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedCafeFirstInstall.aspx

Error:
You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedFrontendTransportFirstInstall.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:
Setup encountered a problem while validating the state of Active Directory: Couldn't find the Enterprise Organization container.  See the Exchange setup log for more information on this error.
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 Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit. Please install the software from http://go.microsoft.com/fwlink/?LinkId=260990.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.UcmaRedistMsi.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 2007 server roles have been detected in this topology. After this operation, you will not be able to install any Exchange 2007 servers.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE12ServerWarning.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

*** END ERROR

Why can't Exchange installation see the AD when everything else can?

Hi All,

I am currently in the process of finishing a migration from Exchange 2007 SP3 UR13 to Exchange 2013 CU3, and I've hit a wall when migrating public folders.

So far I've been following the guide here: Part 4: Step-by-Step Exchange 2007 to 2013 Migration

And verified everything mentioned in the technet article here: Migrate Public Folders to Exchange 2013 From Previous Versions

At present, I'm getting the following results:

Get-PublicFolderMigrationRequest | Get-PublicFolderMigrationRequestStatistics -IncludeReport | FL
...
 7/23/2014 12:21:02 PM [xxxmbox02] The Microsoft Exchange Mailbox Replication service 'xxxmbox02.internal.domain.com' (15.0.775.35
 caps:3F) is examining the request.
 7/23/2014 12:21:02 PM [xxxmbox02] Connected to target mailbox '3bcdb652-b936-4a9f-b043-06b9d24de69b', database 'XXXRESOURCE_MBX01', Mailbox
 server 'xxxmbox02.internal.domain.com' Version 15.0 (Build 775.0), proxy server 'xxxmbox02.internal.domain.com' 15.0.775.35
 caps:07FFCB07FFFF.
 7/23/2014 12:21:03 PM [xxxmbox02] Connected to source mailbox '', database 'e2007xx01\First Storage Group\Public Folder Database', Mailbox
 server 'e2007xx01.corporate.wesfarmers.com.au' Version 8.3 (Build 348.0).
 7/23/2014 12:21:03 PM [xxxmbox02] Request processing continued, stage CreatingFolderHierarchy.
 7/23/2014 12:21:05 PM [xxxmbox02] Initializing folder hierarchy from mailbox '': 150 folders total.
 7/23/2014 12:21:11 PM [xxxmbox02] Transient error MapiExceptionUnknownUser has occurred. The system will retry (7/60).

This Article:  Exchange 2007 to 2013: Public Folder Migration Issue describes the same error message, however I have verified that the system attendant mailbox is right where it should be and available.

Any assistance would be greatly appreciated as I'm quite stumped, and the related threads don't seem to describe quite the same issue I'm seeing.

Many Thanks,

James

Hello,

We have 2 Exchange 2013 (build 712) servers in a DAG with distinct subnets. Cisco ASA in between was set to have no filtering between servers in subnet.

We cannot add database copies nor move mailboxes.

Tes-Mapiconnectivty fails with

unspaceId  : e8a087f1-6197-48df-b094-d5c93a7b6070
Server      : CLI-SRV01
Database    : CLI-MDB01
Mailbox     : SystemMailbox{376e8d54-7154-484a-a0a3-58f22d73236f}
MailboxGuid :
IsArchive   :
Result      : *FAILURE*
Latency     : 00:00:00
Error       : [Microsoft.Exchange.Data.Storage.MailboxOfflineException]: Cannot open mailbox /o=First
              Organization/ou=Exchange Administrative Group
              (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=CLI-SRV01/cn=Microsoft System Attendant. Inner error
              [Microsoft.Mapi.MapiExceptionMdbOffline]: MapiExceptionMdbOffline: Unable to make connection to the
              server. (hr=0x80004005, ec=1142)

In event log:

Adding database copy fails with

The seeding operation failed. Error: An error occurred while performing the seed operation. Error: Failed to open a log truncation context to source server 'CLI-SRV02.CLI.ch'. Hresult: 0xc7ff07d7. Error: Failed to open a log truncation context because the Microsoft Exchange Information Store service is not running. [Database: CLI-PFDB02, Server: CLI-SRV01.CLI.ch]

How can I further verify communication from CLI-SRV02 to CLI-SRV01 ?

Any help welcome

/Patrice

I am starting my transition to Exchange 2013 and I have a few questions. 

First, I am installing my mailbox servers. The management want a phased rollout and install the CAS servers next month. Are the mailbox servers OK to run on their own until then?

Second, I have some new and old namespaces, and I want to know how I configure these.

Old names:

internal webmail : https://webmail.domain.com.owa

activesync: webmail.domain.com

internal autodiscover: autodiscover.domain.com

CAS Array name: mapi.domain.com (MXserver10 and MXserver11)

We also have a DR with:

DRactivesync: DRwebmail.domain.com

We want to use the following names in our environment. Is it still wise to have different names for our DR activesync?

We are not using a CAS Array. We will be running exchange.domain.com as a CNAME to both serverCAS01 and serverCAS02

EAS: email.domain.com

DR EAS DRemail.domain.com

Am I missing something? Please help! How do I go about setting these names so that all mail for my 2010 servers gets routed through Exchange 213, and so that there is no disruption when i set these things up.

I'm on one of my last steps in migrating from 2010 to 2013.  When I issue the command to  Resume the migration request after the Autosuspend happens, I get a StalledDueToMailBoxLock, and it retries but never completes.  I've removed the request and tried it again, but I get the same thing.  The requests were 24 hours apart.  I have no clients that are connecting to the 2010 server anymore, and all the user mailboxes have been migrated to 2013 successfully.  I haven't found much online about this status, so I'm at a loss.  By the way, this is during my Public Folder migration process.  Sorry for leaving that out.

Thank you.

mail client use ms.outlook 2007, everything ok when it's use first time after setup, next business day it's show error and status disconnect

"Task 'Microsoft Exchange Server' reported error (0x8004011d): 'The server is not available. Contact your administrator is this condition persists."

i've follow this instruction,but not works.

*support.microsoft.com/kb/923575

*forums.msexchange.org/Error_%280x8004011D%29_The_server_is_not_available/m_30795900/tm.htm

note.first time after setup mail client,there's no certificate required pop-up, now each time open it, it's show certificate alert

in security alert,show cross : the name on the security certificate is invalid or does not match the name of the site

Hi guys,

I'm hoping for a bit of assistance. I have stepped into an environment where there is one production Exchange 2010 server and one Exchange 2013 server. The Exchange 2013 server is in a unrecoverable state however it contains the domain administrators mailbox and therefore I cannot remove it manually. As it was a vm, I took it offline, created an identical server (name, os version(Windows 2008 R2 with latest updates), ip address etc.), installed all the prerequisite components and then ran setup /m:RecoverServer /IAcceptExchangeServerLicenseTerms. Everything runs through successfully until it gets to the Mailbox role: Transport service where it fails with "Unable to set shared config DC.". After some searching on Google, it suggests that ipv6 is disabled on the DC. We have two DC's in our environment and both have ipv6 enabled as does the exchange server. If I try to re-run the installation for the role alone, i.e. Setup /mode:install /IAcceptExchangeServerLicenseTerms /role:HubTransport, it fails with "The machine is not configured for installing "BridgeheadRole" Datacenter Role." 

Any help would be greatly appreciated. 

In Exchange 2013, the RPC client access service now runs exclusively on mailbox role and no longer on CAS servers.  THis has caused a rather unique issue wit ha client I'm at.

Said client uses a firewall to separate client machines from server VLAN.  While thye normally only expose RPC/HTTP to the CAS servers in 2010, in 2013 this causes problems.  WHat happens currently is if a client queries for an RPC CAS server he will get the current CAS 2010 servers and the 2013 MBX servers... which have no client ports open to them (nor do they want them).  Eventually the problem will be solved on it's own when clients are upgraded to 2013, things are defaulted to MAPI over HTTPS etc ... but for now what it means is if anyone tries to setup a new profile there is a chance the service will attempt to bind to a mailbox server to which the client has no port access to.

with the remove-rpcclientaccessserver cmdlet gone in 2013, is there any way to disable the the publishing of the mailbox clienta ccess service in 2013?  If I used the blockedclientversions option on just the 2013 servers ... would clients auto-attempt to connect to the 2010 CAS?  

The goal here is to get the clients to ignore the 2013 RPC service until all upgrades and migrations are ready rather than exposing the mailbox servers before they've been tested/cleared.