Another way to approach Autodiscover during migration: change DNS server settings on the WS
Any mailbox migration these days should include some way of addressing Autodiscover to ensure seamless user’s transition from one AD / Exchange organization to another. The issues with Autodiscover arise because 2 mailboxes exist – one in Source and one in Target, and depending on how the environment is configured, Outlook can resolve to one of them. […]
How to migrate 3 TB of Public Folder data into Ex 2013 with QMM/DMM (Quest/Dell Migration Manager). Part 2: PF Move Requests
Part of PF migration challenge is that Exchange 2013 CU7 hierarchy mailboxes cannot exceed 100 GB as prescribed by Microsoft (https://technet.microsoft.com/en-us/library/dn594582(v=exchg.150).aspx) This is the absolute maximum, recommended size is actually half of that value: 50 GB. Here you need to learn how to perform PF Move Requests, PF Branch moves or PF Mailbox split. Whether you go […]
How to migrate 3 TB of Public Folder data into Ex 2013 with QMM/DMM (Quest/Dell Migration Manager). Part 1: Setting things up
It will not be easy so be prepared. It will be very tedious job requiring lots of “babysitting”. And it will be time consuming. The end result of how long it’s going to take to complete will of course vary and I am sure if you read the below outline of my experience, it will save you quite a bit […]
Time Sync on virtualized DCs: My experience
Here are the notes I came up with after researching and building VM DCs infrastructure for a customer. 1. Disable VM Host Time Provider on all DCs via the following registry fix: reg add HKLM\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\VMICTimeProvider /v Enabled /t reg_dword /d 0 2. Create GPO that only applies to the PDC emulator with the settings to sync time externally: WMI Filter: Select * […]
Network Settings on newly built 2012R2 DC
Wanted to share some of my quick notes on how to configure networking (IPV6, DNS) on the newly built 2012R2 DC 1. Leave IPV6 enabled. Microsoft does not recommend to remove it, it’s part of OS. 2. Unlink IPV6 from listening IPs on DNS server, only leave to listen on IPv4 address (questionable but works for me) […]
OWA issue: User cannot load OWA, fails to save Time Zone
Took me some time to figure out so hopefully this post will get indexed on the Web and will save someone their valuable time. Imagine User trying accessing OWA on Exchange 2013, entering his credentials and being presented with the regional settings dialogue. He picks language, language and Time Zone, hits next but nothing happens – selected […]
MAgE Calendar Sync: Mailbox Move Logic
In this post I wanted to highlight some changes in the mailbox move logic of QMM MAgE Calendar Sync compared to the legacy CSA (Calendar Sync Agent). In the legacy Calendar sync collections mailbox is only moved once – immediately after Directory Sync instantiates empty mailbox on the stub database. Calendar agent then moves, deletes and re-creates mailbox […]
DNS DNAME Record: Migration use case
Just came across a common post-migration scenario that often happens during old Source domain decommissioning: What do we do with Source Domain name? Particularly how to redirect all those old name references to already migrated SERVER.SOURCE.LOCAL which now lives at SERVER.TARGET.LOCAL. It has very easy and elegant solution actually and while I am sure it wouldn’t be anything new for DNS gurus, since I am not the one 🙂 I will write […]
Moving QMM SQL Project to a different server.
Today I had to assist with re-locating QMM SQL database to a different SQL server / instance in order to isolate performance issues and give it more room / resources. Here are the steps we took: 1. IMPORTANT: Stop all QMM for Exchange Agent Instances especially MAgE which talk to SQL database. Legacy agents are ok but still […]
More you should know about QMM MAgE agents…
Here I wanted to emphasize some important facts about the new QMM MAgE (Migration Agent for Exchange) agents… what one should know about them when starting migration project. 1. Don’t underestimate Agent Host hardware requirements. MAgE is quite hungry for computer resources, especially CPU. Below is official requirement which I cannot agree more based on my experience, certainly […]
