Today, I helped a client migrate Exchange from 2010 to 2019. As you know, Exchange 2010 can’t migrate to 2019 directly. You need to migrate Exchange from 2010 to 2016 and then 2019.
When I tried to prepare the AD schema for installing Exchange 2016 CU23, and it happened the error message is below.
“One or more servers in the existing organization are running Exchange 2000 Server or Exchange Server 2003”.
The error is because they were not uninstalled Exchange 2000 or 2003 completed. Let’s fix it.
If you are trying to change mailbox delegation settings via Exchange Admin center and show the access control defines the ObjectType {xxx-xxxx-xxx-xxxx} that can’t be resolved tab mailbox delegation, don’t panic, today, I am going to how to fix it.
Today, we help our client to build a new S2D server as new Veeam Repository, now, we need to move the SOBR performance tier from the old repository server to this new server, I am going to show you how to move it.
As we know, you can easy to create VMs, Firewalls, Load Balancers on Microsoft Azure, you also can make routing path change but all of them will cost you lots of money, it depends on how many virtual devices or virtual machines that you created.
Today, I am going to show you how to build Hyper-V nested VM with multiple public IP address, you just need to pay Microsoft for one Hyper-V host with storage space and public IP addresses, you can install firewall, created lots of VMs, load balancer, control routing path, port forwarding and so on, we can use them for LAB test, POC, or even production.
There is no more legacy public folder database, public folder mailboxes also knows as modern public folders, if you still need public folders, migrate them to Exchange 2016.
Public folder migration is a one-way process, if something goes wrong, you can roll back but any changes made since the migration will be lost.
After you’ve completed your deployment of Exchange 2016, and test connectivity via Exchange Remote Connectivity tool, you can move mailboxes to your Exchange 2016 Mailbox server.
t’s time to demote existing Windows server 2003 and migrate all Windows server roles to new Windows server 2012 R2, there are no down time for Part1 steps and Part2 steps, but we need to schedule down time for Part3 steps to cut over all services.
After done for Active Directory Preparation, now we need to install a new Windows Server 2012 R2, export data from existing windows server 2003 and then import to new Windows… Read more »
As we know Windows Server 2003 was end support on July 14, 2015, but there are some customers still using it for some reasons. Today, my customer asked me to… Read more »
Do your Windows 2016 Servers have mysterious shutdown issues? Today, I tried to troubleshooting windows 2016 mysterious shutdown for my client, I found it was NT Authority\System that shutdown the… Read more »
As we know, Veeam Backup and Replication Software is a powerful and easy-to-use for backup and availability solution, I would like to share a troubleshooting tip with you today. You… Read more »
Today, let’s talking about how to step by step to update Mellanox NIC firmware and driver for non-RDMA Storage space direct servers. You can easy to do it via follow… Read more »
My customer asked me to upgrade their Windows 2003 web server last week, as we know, Windows Server 2003 extended support ended on July 14,2015, Microsoft will no longer issue… Read more »
Today, my customer asked me that is it possible to expand system volume disk space for their Windows Server 2003 virtual machine? The answer is Yes, we can do it without any 3rd party tools. You just need a Windows Server 2008 or up to help this. Let’s follow the step by step to do it.
