Hi,

We are a hosting exchange provider company. We recently migrated a company from rackspace to our hosted Exchange. All users are successfully migrated and are sending and receiving emails.

The issue is that external users have autocomplete email addresses of rackspace's users in their outlook. Now that users are migrated to our exchanage, if someone tries to send an email using autocomplete address from outlook then email bounced back.

I also tried to send an email using autocomplete and email bounced. Bounced email shows rackspace's server name in the rejection message.

Is there any permanent solution to this issue? I have read about X500, but we migrated 5000 users. How can we create x500 for 5000 users?

 Any help will be highly appreciated.

Regards,

Anees

Hi Guys,

Most probably I am going to deliver one project in nearest future, which included to move Mailboxes and mail data from Novel Group-wise to Exchange 2013. i want to know what should be the approach and what are the per-requisites that need to be consider to perform Migration steps in above scenario? please let me know how the mail-flow work to/from Group-wise to exchange 2013 and vice-verse. please suggest me some initial steps and URLs for this requirement. i want to be clarified logically before i suggest any solution on this to my customer.

step by step docs will be more helpful to achieve this goal..

Regards,

Aanand Singh

Hi Guys,

Most probably I am going to deliver one project in nearest future, which included to move Mailboxes and mail data from Novel Group-wise to Exchange 2013. i want to know what should be the approach and what are the per-requisites that need to be consider to perform Migration steps in above scenario? please let me know how the mail-flow work to/from Group-wise to exchange 2013 and vice-verse. please suggest me some initial steps and URLs for this requirement. i want to be clarified logically before i suggest any solution on this to my customer.

step by step docs will be more helpful to achieve this goal..

Regards,

Aanand Singh

Hello all,

     This is my first post here. I fear our organization may have made a grave error. Here is our basic setup:

1. Location 1 - 3 2008 R2 standard servers in a domain. 1 Exchange 2010 sp3 server.
2. Location 2 - 3 2008 R2 standard servers in the same domain connected over CISCO VPN. 1 Exchange 2010 sp3 server

Our objective was to replicate the first site at the second site. We have setup DFS and made a BDC at the second site, no issues. However, I have been doing some reading on Exchange replication, and it looks like we are in trouble. I had read that Exchange 2010 could be fully replicated over two servers (unlike 2007). However, I now have read that this requires the Enterprise edition of Windows server 2008 R2. So, I guess I have three questions to start:

1. Is there ANY way we can replicate site 1 to site 2 with the current setup? Even if it means site 2 is "inactive" unless we need it for a failure at site 1?
2. If not, can we upgrade to the enterprise edition for the servers? Any idea on cost?
3. If we upgrade to Enterprise, is there a decent place to go to read on how to setup the second site?

Thanks very much.

When running PST Capture, I have entered the Online connection settings and specified the server: smtp.office365.com. That seems to work ok. I run the PST discovery and that works ok and I can then create an import list. However, when I go to specify a mailbox I am not seeing all of the mailboxes. There are a lot missing from the list, even though all are in Office 365?

Any help would be much appreciated.

Many Thanks

Paul.

I was unable to access Exchange via Exchange Management Shell.
Below is the error message:
VERBOSE: Connecting to exchange.domain.com.
New-PSSession : [exchange.domain.com] Processing data from remote server exchange.domain.com failed with the following error message: The WinRM Shell client cannot process the request. The shell handle passed to the WSMan Shell function is not valid. The shell handle is valid only when WSManCreateShell function completes successfully. Change the request including a valid shell handle and try again. For more information, see the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : -2144108212,PSSessionOpenFailed
VERBOSE: Connecting to exchange.domain.com.
New-PSSession : [exchange.domain.com] Processing data from remote server exchange.domain.com failed with the following error message: The WinRM Shell client cannot process the request. The shell handle passed to the WSMan Shell function is not valid. The shell handle is valid only when WSManCreateShell function completes successfully. Change the request including a valid shell handle and try again. For more information, see the about_Remote_Troubleshooting Help topic.
.
.
.

-    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : -2144108212,PSSessionOpenFailed
Failed to connect to an Exchange server in the current site.
Enter the server FQDN where you want to connect.:

I tried to access the Exchange using browser, https://localhost/ecp or https://192.168.1.10/ecp, i able to login. But after login the browser displays blank.

The last thing i did was re-create a self-sign certificate.

Anyone can help?

I have a 2010/2013 environment.

I'm trying to create a DAG in 2013 but when i try to specify the fileshare witness directory(or leave it blank) i see this error in the 2013 mailbox server.

i currently only have 1 2013 cas server and 1 2013 mbx server.

i tried to point the witness directory to be the 2013 cas server.

Below is the event

Also should I be able to ping the DAG ip address?

thanks in advance

Good morning...

We have a multi-tenancy Exchange environment where we need to move one of the tenants onto their own dedicated server (AD and Exchange).

I've seen a good amount of documentation on migrating the entire setup to a new server, but not much on just doing it for one tenant in a multi-tenant environment.

Is there a way of doing this and minimizing downtime?  It seems like using the new server for a backup/secondary AD and Exchange and then promoting and forgetting the old would work for a live setting.  However not having done that before, nor am I seeing anything about doing it for one single tenant in a multi-tenant environment.  I'd like to know if I'm trying the impossible to start with.

Thank you for your time.

-Erick

Hi All-

I just completed the installation of Exchange 2013, co-existing with Exchange 2007.  I have 2013 CU1 and 2007 SP3 RU10.  The issue I have is that I cannot access mailboxes existing in the 2007 mailbox servers through my 2013 OWA server.  Is there some advanced configuration that I need to do, on either 2007 or 2013? The documentation I have read seems to indicated that I should be able to use OWA 2013 to access 2007 mailbox.

TIA,

Chris

Hello,  Currently trying to migrate to Exchange 2013 and having issues.  The initial test rollover did not go well on Saturday so I failed the DNS entries back.

Current environment is Exchange 2007 and Lync 2013.  Clients are Office 2010 / 2013, and active sync users.

In adding the 2013 server, I did also create a legacy.domain.com DNS entry to point to the IP address of the existing 2007 server.

Everyone's mailboxes (and public folders) are on the 2007 server.  I migrated one test account to the 2013 server for testing purposes only.  That test account also has a Lync account.

So before rolling out the changes, I update the HOSTS file on my PC to try to simulate a real switch.  Its internal on the network so I added the new 2013's IP address with mail.domain.com and webmail.domain.com.

In DNS autodiscover.domain.com has a CNAME to mail.domain.com so I don't think I need to put that in my hosts file.  Anyway my account does appear to load in Outlook 2013.  However Lync 2013 has a yellow banner under the 4 main icons that says Exchange credentials required.  If I put them in, it keeps prompting.  I just close out of it and Lync still works.  So this is one thing that needs to be fixed.

If I try to access our webmail at https://webmail.domain.com, I put in my 2007 mail account username and password, but then it redirects to https://www.webmail.domain.com/owa/auth/owaauth.dll which cannot be displayed because there is no host called www.webmail.  I would imagine it should redirect to legacy.domain.com right?  I'm not sure where it is adding the www. in front because in the 2013 Exchange Admin Center under servers > Virtual Directories, the internal URL is https://mail.domain.com/owa and the external URL is https://webmail.domain.com/owa.

So this needs to be fixed as well.

Lastly, if I try to login with the test account that has the 2013 mailbox, Outlook and Lync both repeatedly prompt for credentials.  It doesn't appear to accept the credentials at all.  I can log into OWA at https://webmail.domain.com and that loads nice  Even setting automatic replies or changing themes works, which is a function of /ecp.

So another piece of the puzzle is that the existing environment has https in the firewall pointed directly to exchange 2007.  Whereas the new deployment has new outside IP pointed to a system on our DMZ.  This system is running IIS ARR and works great for all the LYNC 2013 features like external LYNC access through mobile apps, off site PC's, hosting meetings, etc.  And I seem to be able to go through this to get to the new Exchange 2013 OWA as well.  But when I changed external DNS on Saturday, ActiveSync still worked, but if I tried to log onto OWA with my account from the outside, I got "too many redirects" on my mobile browser.

I am at a loss here of what could the issue be.  Its a few problems here and I'm trying to get everything working fine using modified HOST file on my PC before spending downtime off hours changing internal and external DNS and the client access URL's on the 2007 server for both Internal and External.

Your help is greatly appreciated! 

I thought I was at the point of migrating our mailboxes from 2007 to 2013.  I had created a new test mailbox on the 2013 server and changed all the DNS and virtual directories for the legacy on the 2007 server and was able to successfully send mail to the test mailbox out and in both internally and externally.  Then I migrated my first mailbox from 2007 to 2013 and things went south.

I CAN NOT:
Send e-mail from a mailbox on the 2007 server to the migrated mailbox on the 2013 server.
Send e-mail from migrated mailbox to external e-mail address.

I CAN:
Send e-mail from the migrated mailbox to a 2007 mailbox and the test mailbox on the 2013 server.
Send e-mail from the internet to the migrated mailbox and the 2013 test mailbox.

I unfortunately am running Exchange 2013 with CU6 (I am already aware of the activesync issue and delegation crash issue but saw the info too late).

Suggestions please!!

I am mid way through migrating from Exchange 2007 to 2013. I have been following the instructions on Step-by-Step Exchange 2007 to 2013 Migration (it would not let me link it unverified). I have had to undo some of it in order to keep email flowing for the organization.

From the 2013 ECP, I cannot see the Mailbox Databases residing on the 2007 server. I successfully migrated a single mailbox to the 2013 server. If I have the 2013 server as the internet facing server as per the instructions, I can access the migrated mailbox without any issue via OWA and Outlook. I cannot access any mailboxes on the 2007 server in any way though.

With the 2007 server as internet facing, I can access every mailbox except for the migrated one. There appears to be a disconnect between the servers that is blocking communication.

From my understanding, I should be able to have the 2013 server set up to take over and all mailboxes should be accessible through that server. I have already tried checking some of the answers regarding the public folders (I have not even started to tackle that yet), but none of it seems to apply. I can see the databases from both servers through the management shell with no errors. Other than being unable to access mailboxes on the secondary server regardless of which is primary, I have not seen any errors.

Any help or suggestions would be appreciated.

Hello,

I have problem with Exchange 2010 management console. I open the console ok, but when click the Microsoft Exchange On-Premise the I got Initialization Failed and with following message :

the attempt to connect to http://mailbox.xxx.com/powershell using "kerberos" authentication failed : connecting to remote server failed with following error message : access denied. For more information, please see the about_Remote_Troubleshooting Help topic.

I already read many threads with same Error and follow the tips but the problem still remains. Does anyone can help?

Thanks

I am working on performing a migration from Exchange 2007 to Exchange 2013. I ran setup and prepared the schema, then when I got to trying to /prepareAD I received the error below.

I have tried a few suggestions found in the forum linked below but none of them resolved the issue. Any help is appreciated, thanks!

INSUFF_ACCESS_RIGHTS on Exchange 2013 SP1

From ExchangeSetup log file:

[09-23-2014 22:32:02.0672] [2] Adding access control entries to the security descriptor for the object CN=Configuration,DC=apptius,DC=com.
[09-23-2014 22:32:02.0672] [2] The appropriate access control entry is already present on the object "CN=Configuration,DC=apptius,DC=com" for account "APPTIUS\Exchange Servers".
[09-23-2014 22:32:02.0688] [2] Taking ownership of CN=Deleted Objects,CN=Configuration,DC=apptius,DC=com.
[09-23-2014 22:32:02.0703] [2] [ERROR] Active Directory operation failed on DC121.apptius.com. This error is not retriable. Additional information: Access is denied.
Active directory response: 00000005: SecErr: DSID-031521E1, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0

[09-23-2014 22:32:02.0703] [2] [ERROR] The user has insufficient access rights.
[09-23-2014 22:32:02.0719] [2] Ending processing initialize-ExchangeConfigurationPermissions
[09-23-2014 22:32:02.0719] [1] The following 1 error(s) occurred during task execution:
[09-23-2014 22:32:02.0719] [1] 0.  ErrorRecord: Active Directory operation failed on DC121.apptius.com. This error is not retriable. Additional information: Access is denied.
Active directory response: 00000005: SecErr: DSID-031521E1, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0

[09-23-2014 22:32:02.0719] [1] 0.  ErrorRecord: Microsoft.Exchange.Data.Directory.ADOperationException: Active Directory operation failed on DC121.apptius.com. This error is not retriable. Additional information: Access is denied.
Active directory response: 00000005: SecErr: DSID-031521E1, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0
 ---> System.DirectoryServices.Protocols.DirectoryOperationException: The user has insufficient access rights.
   at System.DirectoryServices.Protocols.LdapConnection.ConstructResponse(Int32 messageId, LdapOperation operation, ResultAll resultType, TimeSpan requestTimeOut, Boolean exceptionOnTimeOut)
   at System.DirectoryServices.Protocols.LdapConnection.SendRequest(DirectoryRequest request, TimeSpan requestTimeout)
   at Microsoft.Exchange.Data.Directory.PooledLdapConnection.SendRequest(DirectoryRequest request, LdapOperation ldapOperation, Nullable`1 clientSideSearchTimeout, IActivityScope activityScope, String callerInfo)
   at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException, Boolean isSync)
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Data.Directory.ADDataSession.AnalyzeDirectoryError(PooledLdapConnection connection, DirectoryRequest request, DirectoryException de, Int32 totalRetries, Int32 retriesOnServer)
   at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException, Boolean isSync)
   at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException)
   at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId)
   at Microsoft.Exchange.Management.Tasks.InitializeConfigPermissions.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)
[09-23-2014 22:32:02.0719] [1] [ERROR] The following error was generated when "$error.Clear();
    initialize-ExchangeConfigurationPermissions -DomainController $RoleDomainController

" was run: "Microsoft.Exchange.Data.Directory.ADOperationException: Active Directory operation failed on DC121.apptius.com. This error is not retriable. Additional information: Access is denied.
Active directory response: 00000005: SecErr: DSID-031521E1, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0
 ---> System.DirectoryServices.Protocols.DirectoryOperationException: The user has insufficient access rights.
   at System.DirectoryServices.Protocols.LdapConnection.ConstructResponse(Int32 messageId, LdapOperation operation, ResultAll resultType, TimeSpan requestTimeOut, Boolean exceptionOnTimeOut)
   at System.DirectoryServices.Protocols.LdapConnection.SendRequest(DirectoryRequest request, TimeSpan requestTimeout)
   at Microsoft.Exchange.Data.Directory.PooledLdapConnection.SendRequest(DirectoryRequest request, LdapOperation ldapOperation, Nullable`1 clientSideSearchTimeout, IActivityScope activityScope, String callerInfo)
   at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException, Boolean isSync)
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Data.Directory.ADDataSession.AnalyzeDirectoryError(PooledLdapConnection connection, DirectoryRequest request, DirectoryException de, Int32 totalRetries, Int32 retriesOnServer)
   at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException, Boolean isSync)
   at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException)
   at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId)
   at Microsoft.Exchange.Management.Tasks.InitializeConfigPermissions.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
[09-23-2014 22:32:02.0719] [1] [ERROR] Active Directory operation failed on DC121.apptius.com. This error is not retriable. Additional information: Access is denied.
Active directory response: 00000005: SecErr: DSID-031521E1, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0

[09-23-2014 22:32:02.0719] [1] [ERROR] The user has insufficient access rights.
[09-23-2014 22:32:02.0719] [1] [ERROR-REFERENCE] Id=-790439948 Component=
[09-23-2014 22:32:02.0719] [1] Setup is stopping now because of one or more critical errors.
[09-23-2014 22:32:02.0719] [1] Finished executing component tasks.
[09-23-2014 22:32:02.0750] [1] Ending processing Install-ExchangeOrganization
[09-23-2014 22:34:13.0541] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\V15\Setup, wasn't found.
[09-23-2014 22:34:13.0541] [0] CurrentResult setupbase.maincore:396: 0
[09-23-2014 22:34:13.0541] [0] End of Setup
[09-23-2014 22:34:13.0541] [0] **********************************************

We have a corrupted installation of Exchange 2013 due to installating CU6

New Exchange server is already installed and mailboxes are migrated over, I am now in the process to uninstall the old exchange 2013 so we can decomission it but I get this error when I try to run uninstall

"This mailbox database is associated with one or more active mailbox import,To get a list of all Mailboximport request associated with this database, run Get MailboxImportRequest | ?{ $_.RequestQueue -eq "<Database ID>"}....

But when i run this command I get an error of" The Get-MailboxImportRequest is not recognized as a cmdlet...

Any advise is appreciated

Thanks.

I am in the process of moving all of our users from one DAG to a brand new DAG. This was done unexpectedly and the users in the old DAG cannot access email except for through Outlook (We have many OWA and Mac users). 

My issue is that some users in certain databases move very quickly (20 mins) and others move exceedingly slowly (1 day 10 hours for a 400mb mailbox). This has really been an issue since most of the slow moving users are administration.

The slow moving users show a status of StalledDueToWriteUnknown from time to time and I will often see a few hours in the state when looking at their full move request statistics. This is confusing as many of these databases are moving from the same source and destination server. Can anyone clarify why they would enter that state and if there is anything I can do to help the process?

Trying to download Hotfix KB2619234 which is pre-req for exchnage 2013 installation on Win 2008 R2.

After providing the e-mail address and request hotfix....received error...The system is currently unavialable, Please try back later r contact support if you want immediate assitance.Seems like the HF is not available for download now, Any other option to get this HF?

Thanks,

Praveen

Hi There

I'm troubleshooting an issue during a exchange 2010 to exchange 2013 migration where the OOF is not working for users homed on the exchange 2010 mailbox servers. This applies to users using outlook 2010 and outlook 2013 .OWA works perfectly and you can also enable OOF via exchange powershell.

Users homed on the exchange 2013 servers does not have any issues.

The exchange 2010 servers is on SP3 rollup 4 and the 2013 servers on SP1 only without any rollups installed.

So my question will be - have anyone experienced this issue during migration and will patching the exchange 2010 servers to rollup 5 or 6 and the exchange 2013 to sp1 rollup 5 fix the OOF issue then? If requested the client to patch to these levels, but in the meantime I'm checking if anyone else had similar issues.

Any pointers will be welcome.