Merging & Migrating Users From Site B to Site A

July 16, 2020, 11:20 pm

≪ Previous: Configuring Exchange 2010 and Exchange 2013 virtual directories for coexistence.

Hi,

I am looking for solution or document to fulfill our exchange email IDs merging. We have to different independent sites Site A & Site B.
Site A scenario - In Site A we are having active directory domain abc.com & Exchange server 2013 with multiple Internal Relay domain. Internal Relay domains are abc.com, def.com,ghi.com & more. All domain systems & exchange users login to abc.com for access as no any subdomains to active directory (like user1@abc.com login using abc\user1, user2@def.com login using abc\user2, user3@ghi.com login using abc\user3 for accessing exchange emails).
Site B scenario - mno.com as active directory domain & multiple email domains mno.com, pqr.com, stu.com & more. At site B all emails are hosted to Exchange Online cloud (Office 365 E1 or Office 365 E3).
There is no any communication or trust relationship between Site A & Site B.
Now we are merging Site A & Site B. In merging we are planning to create new exchange domain xyz.com. To xyz.com we want to migrate users from abc.com of Site A & mno.com of Site B. This will create new mailbox newuser1@xyz.com, newuser2@xyz.com. Here as per our requirement we want to migrate/ create new user to Exchange server of Site A. From Site B dont want to migrate or merge other domain users except mno.com.
We are thinking to create new mailboxes on Exchange server for Site A (abc.com) & Site B (mno.com) users as xyz.com. For Site A users dont think much challenge, but for Site B users looking for smooth migration. When we create new email IDs for Site B users as xyz.com we are not discontinuing mno.com email IDs. These users requires emails for both domains (xyz.com on Exchange 2013 & mno.com to cloud). If we create new mailbox for Site B users how they will login to Exchange email ID using xyz\newuser. This is required for both sites users (Site A & Site B) for xyz.com users. Also how user1@mno.com emails we can forward or redirect to newuser1@xyz.com of Site B user.

Here we want to clear that we are going to use Exchange 2013 on premise setup only.

Looking for proper document for merger.

Thanks,
Sachin

↧

remote migration to o365

July 17, 2020, 11:25 am

≫ Next: Issue while trying to install Security update on Exchange 2013 CU 23

≪ Previous: Merging & Migrating Users From Site B to Site A

dears,

i configured my 2013 exchange for hybrid. however i recieved this warning in the end

the migration endpoint is not created. however mrs proxy is enabled tried to disable/enable more than once same issue

webmail and autodiscover are externally published

my certificate is valid and public

test using remote analyzer is successful

however, testing the remote migration move is failing with the call to ews.

if i try https://webmail.domain.com/ews/proxy.svc this is not working. the issue is here somewhere and i tried all the fixes with no luck. changed the authentication from iis and tested, same issue

your help is appreciated

↧

Issue while trying to install Security update on Exchange 2013 CU 23

July 20, 2020, 4:51 pm

≫ Next: Failed logon attempts for Alternate Service Account

≪ Previous: remote migration to o365

Hello Everyone.

I am trying security update KB4536988 in order to mitigate cve-2020-0688. We have total 10 servers out of which 4 are Exchange 2010 sp3 on which I was able to install RU 30. We also have 6 Exchange 2013 servers all with CU 23 installed 3 of which are CAS servers and rest 3 are Mailbox Servers. I was able to install this security update on other 5 servers but when I wanted to install this patch on the sixth server, I started facing the problem.

The installation exits abruptly few seconds after initiation prompting me to select msi file and gives me a message "The installed product does not match the installation source." In use source I can see it is looking for "Exchange 2013 CU 18 msi file". As it has CU23 installed, I tried to point it to CU 23 msi file but it ended up with another error "The file "C:\cu23\exchangeserver.msi" is not a valid installation package for the product microsoft Exchange Server. Try to find the installation package "exchangeserver.msi" in a folder from which you can install Microsoft Exchange Server" even though I was not prompted for anything as such on any of the other servers.

I also tried by copying Exchange 2013 CU18 files on this server but that did not help either.

If anyone has come accross this error. Please help me understand the underlying problem and fix it for once.

Basheer Syed

↧

Failed logon attempts for Alternate Service Account

July 22, 2020, 10:54 am

≫ Next: Unable to install exchange server 2013 using pypsrp client remotely.

≪ Previous: Issue while trying to install Security update on Exchange 2013 CU 23

Hello team. I've got an interesting problem where I see event 4625 in the Security Log for my ASA. The failure reason says "Unknown user name or bad password"

Environment: Exchange 2013 CU 23, Windows Server 2012 R2, Forest + Domain functional level - 2012 R2, Load Balancers, Kerberos Authentication, No forest-to-forest trusts. Many child domains.

Issue: ASA account shows failed logon attempts in Event Viewer on the Exchange server, but not on the domain controller. It shows successful attempts on the DC, but failed attempts on the Exchange Server. NOTE: This is only happening at one site as far as I know. There are multiple ASAs. I think this is because they are using site-based namespaces and so they delegate site-specific SPNs to the site specific ASA.

Troubleshooting done so far: Re-rolled out ASA credentials to the site Exchange Client Access Servers. Interestingly enough, once this was done, the error being reported changed from “…using a bad password” to “…using an old password.” Found and removed stored credentials by running “rundll32 keymgr.dll,KRShowKeyMgr” as the local system account (done by using PSExec).

Other info: Looking at the event log, it logs event ID 4625 for this ASA with a logon type of 8, which is supposedly “NetworkCleartext,” which implies that it is having issues with IIS logins using Basic Authentication. The Authentication Package in the event log info mentions using “Negotiate” and the Logon Process is “Advapi,” so I don’t see how it would be an issue with trying to use Basic Authentication. The caller process seems to be the Exchange svchost process ($env:ExchangeInstallPath\Bin\Microsoft.Exchange.ServiceHost.exe)

↧

Unable to install exchange server 2013 using pypsrp client remotely.

July 26, 2020, 7:44 am

≫ Next: Delete System and Arbitration Mailboxes after Office 365 Migration

≪ Previous: Failed logon attempts for Alternate Service Account

Hi Techies,

I am trying to install exchange 2013 on windows 2012 R2 using pypsrp client remotely but getting some role permission errors. Though I am able to install exchange 2013 using powershell on windows 2012 directly.

Command = Setup.exe /PrepareAD /OrganizationName:"Automation" /IAcceptExchangeServerLicenseTerms

Error:

Microsoft Exchange Server 2013 Cumulative Update 23 Unattended Setup

Copying Files...
File copy complete. Setup will now collect additional information needed for installation.

Performing Microsoft Exchange Server Prerequisite Check

Prerequisite AnalysisSetup 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.
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.
... FAILED

The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.

Global updates need to be made to Active Directory, and this user account isn't a member of the 'Enterprise Admins' group.
The local domain needs to be updated. You must be a member of the 'Domain Admins' group and 'Organization Management' role group, or 'Enterprise Admins' group to continue.
Setup encountered a problem while validating the state of Active Directory: Active Directory operation failed on . The supplied credential for 'AUTOMATION\Administrator' is invalid. See the Exchange setup log for more information on this 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.
Either Active Directory doesn't exist, or it can't be contacted.

Any help would be appreciable.

Thanks in advance.

↧

Delete System and Arbitration Mailboxes after Office 365 Migration

September 10, 2015, 8:07 am

≫ Next: Arbitration mailboxes in a hybrid deployment

≪ Previous: Unable to install exchange server 2013 using pypsrp client remotely.

Hey all,

We successfully completed our migration of all user mailboxes from our on-premise Exchange 2010 server to Office 365, and would now like to decommission the on-premise Exchange 2010 server. We have a separate server that we are leaving on-premises for management, which only has the EMC and no mailbox role. But the old mailbox server should be decommissioned now. It has been turned off for weeks with no impact. We have removed the hybrid configuration. MX records and autodiscover are all moved. DirSync is in place and working.

When attempting to uninstall Exchange 2010 from the old mailbox server, we are getting the error "This mailbox database contains one or more mailboxes, mailbox plans, archive mailboxes, or arbitration mailboxes." and cannot continue. The error suggests either moving the arbitration mailbox or disabling the mailbox if this is the last server in the organization. Since we don't have any other mailbox servers, there is nowhere to move it. And disabling the mailbox makes me nervous because though this is the last on-premise server, I don't want this to affect our cloud services by assuming we are decommissioning the organization. What do we do with the system and arbitration mailboxes?

We have read the article here but it does not fulfill our specific need: http://blogs.technet.com/b/exchange/archive/2012/12/05/decommissioning-your-exchange-2010-servers-in-a-hybrid-deployment.aspx

Also, and I'm not sure if this is a separate topic, how can we make sure that removing this on-premise mailbox server will not remove mail attributes from our user objects?

Thanks!

↧

Arbitration mailboxes in a hybrid deployment

January 24, 2018, 8:33 am

≫ Next: Migration Stuck at syncing when migrating to O365

≪ Previous: Delete System and Arbitration Mailboxes after Office 365 Migration

Hi,

We've migrated all user mailboxes to Office 365. I would like to retain our on-premise Exchange 2013 server to manage active directory objects (as recommended). However, I would like to delete the mailbox database in order to free disk space, and if possible remove the mailbox server role. What should I do with the arbitration and Discover Search mailboxes? Can they be migrated to Office 365? I haven't been able to find instructions on how to do that. I could move them to a new database on-premise, but would prefer to keep our local environment as lean as possible.

Thanks!

Dave

↧

Migration Stuck at syncing when migrating to O365

December 18, 2019, 4:05 am

≪ Previous: Arbitration mailboxes in a hybrid deployment

I have started migrating a batch of single user(35GB) of size, after the migration reached 8 GB, i was stuck in Syncing state for almost 4 hours now.

Provide a solution.

↧