Skip to main content

Moving an Exchange 2007 Server to Another Domain

 Moving an Exchange 2007 Server to Another Domain

It is not supported to move an Exchange 2007 server from one domain to another domain. Additionally, it is not supported to run the setup /mode:recoverserver command against an Exchange computer object that previously existed in a different domain. If you must move an Exchange 2007 server to another domain, you must instead perform one of the following tasks:
  • If you want to move an Exchange server between domains within the same forest in a planned scenario (for example, due to a reorganization), we recommend that you install new servers in the new domain. You can then move the mailboxes from the server in the old domain to the server in the new domain. You can also replicate public folder content to the new server. For more information about how to move mailboxes in Exchange 2007, see How to Move a Mailbox Within a Single Forest. For more information about replicating public folder content, see Managing Public Folder Replication.
  • If you want to move an Exchange server between domains due to an unplanned failure or disaster, we recommend that you restore the Exchange 2007 databases and mailboxes to a new Exchange server that you install in the new domain. To move the current Exchange information to the new Exchange server, you must have a good backup copy of the databases that were on the failed server. For more information about restoring a database to a new server, see How to Restore a Mailbox Database to a New Server with Database Portability.




Moving Objects Between Administrative Groups


Topic Last Modified: 2005-04-21
You can move some of the objects in an administrative group to a different group. However, there are other objects that you cannot move.
Objects that you can move between administrative groups are as follows:
  • System policies
  • Public folders
  • Routing group member servers (native mode only)
  • Mailboxes in Exchange Server 2003 SP1 and later. It is best to move mailboxes across administrative groups in mixed mode under certain circumstances; for example, during site consolidation.
Objects that you cannot move between administrative groups are as follows:
  • Servers
  • Containers
You can move objects only between containers of the same type. For example, you can move a system policy from one system policy container to another system policy container in a different administrative group, but you cannot move a system policy into a public folder container. This type of action is blocked by default.
For detailed instructions, see How to Move Objects Between Administrative Groups.

Comments

Post a Comment

Popular posts from this blog

Calculate how much data can be transferred in 24 hours based on link speed in data center

  In case you are planning for migration via DIA or IPVPN link and as example you have 200Mb stable speed so you could calculate using the below formula. (( 200Mb /8)x60x60x24) /1024/1024 = 2TB /per day In case you have different speed you could replace the 200Mb by any rate to calculate as example below. (( 5 00Mb /8)x60x60x24) /1024/1024 =  5.15TB  /per day So approximate each 100Mb would allow around 1TB per day.
Post a Comment
Read more

Integration with vCloud Director failing after NSXT upgrade to 4.1.2.0 certificate expired

  Issue Clarification: after upgrade from 3.1.3 to 4.1.2.0 observed certificate to be expired related to various internal services.   Issue Verification: after Upgrade from 3.1.3 to 4.1.2.0 observed certificate to be expired related to various internal services.   Root Cause Identification: >>we confirmed the issue to be related to the below KB NSX alarms indicating certificates have expired or are expiring (94898)   Root Cause Justification:   There are two main factors that can contribute to this behaviour: NSX Managers have many certificates for internal services. In version NSX 3.2.1, Cluster Boot Manager (CBM) service certificates were incorrectly given a validity period of 825 days instead of 100 years. This was corrected to 100 years in NSX 3.2.3. However any environment originally installed on NSX 3.2.1 will have the internal CBM Corfu certs expire after 825 regardless of upgrade to the fixed version or not. On NSX-T 3.2.x interna...
Post a Comment
Read more

Recreating a VMFS-3 or VMFS-5 partition table in ESXi 5.x

For this kind of issues you need to engage VMware support on this, following any part of this article could lead to more complex situation if not ran by an expert.   Symptoms Datastore does not mount because of a lost or overwritten partition table.   Purpose When a VMFS partition is created in ESX 3.x or ESX 4.x, it has a Master Boot Record (MBR) partition map. The MBR is written to the first 512 B block (LBA0) and contains the information where the (VMFS) partition starts and ends. ESXi 5.0 introduced VMFS-5, which uses a GUID partition table (GPT) for new datastores. When a VMFS-3 partition is created in ESXi 5.x and is later updated to VMFS-5, the original partition map (MBR) is maintained. If the partition information of a VMFS datastore is deleted or overwritten (for example, by a Windows system with direct access to the same disks), it is impossible to determine if the partition map was GPT or MBR. The only time you can be sure that a GPT partition map was used is if th...
Post a Comment
Read more