Tag: Migrate

Migrating GPO's between different domains

If we need to carry policies from one Active Directory to another and we don't have a trust relationship, or there is no possible communication between them, we could make a backup of the GPO's that we are interested in in the source domain and import them through the migration tables in the destination domain. This document is valid for migrating GPO's between any version of Windows Server, since 2000, 2003, 2003 R2, 2008 or 2008 R2; In this document we will see how to perform these steps.

Upgrade VMware ESXi 4.0 a 4.1 manually

Algo típico de estos días es ir actualizando nuestros entornos virtuales a la versión 4.1 los que tengan VMware ESXi 4.0 y quieran migrarlos a VMware ESXi 4.1, en este documento vemos cómo actualizar los host que tengamos descentralizados de una forma rápida pero manual, lo realizaremos mediante VMware vSphere CLI (Command-Line Interface) y bajándonos el fichero a que nos permitirá dicha actualización.

Migrating to Citrix XenApp 6

The past 24 Citrix finally released its latest version of XenApp, in this document we will see how to bring our Citrix XenApp environment 4.5 o Citrix XenApp 5 to this new Citrix XenApp version 6. Of course,, as XenApp 6 only supports Windows 2008 R2 (x64) we will not be able to upgrade directly on our current XenApp servers, we will have to export all its configuration with a tool provided by Citrix called Citrix XenApp Migration Tool and import it into the new environment. So we will have to set up the new environment on another server beforehand, performing a clean/new installation, creating a new community and subsequently, We would have to reinstall the applications with the same configurations as in the previous environment. Apparently an unpleasant migration, But of course, all this is due to the need to mount it under Windows 2008 R2 that will provide us with greater performance.

Exchange Migration 2003 to Exchange 2010

In this document, we'll look at the steps to take when migrating a Microsoft Exchange Server organization 2003 to Microsoft Exchange Server 2010, we will note that in this document we will migrate an Exchange server 2003 with mailboxes, Public Folders, policies and OWA to an Exchange server 2010 With all the roles (Transport Hub, Client Access, Mailbox and Exchange Management Tools). If we want to get an Exchange organization 2010 With the separate functions we can use the document as a guide, since each migration is completely different from the rest.

Migrate VMware ESX 3.x to VMware ESX 4.0 manually

This document shows how to migrate an ESX host from the VMware ESX release 3.5 to VMware ESX 4.0, but it is valid for any ESX 3.x, It is designed for small environments, of one or two host's, but it would not make sense since it is a manual update process, without the ability to schedule the task or perform more than one simultaneous migration or by specifying a migration order for our hosts.

Update VMware Tools and Automatically Upgrade Virtual Machine Hardware with Update Manager

This would be the last step for a successful migration of our VMware vCenter virtual environment 2.5 a VMware vCenter Server 4.0, once we already have the VMware vCenter Server in the version 4.0, we have migrated the VMware Update Manager to VMware vCenter Update Manager 4.0 and all our ESX hosts are already with ESX 4.0, we will be able to upgrade the VMware Tools to the virtual machines as well as then upgrade the virtual hardware version of the version 4 to the version 7.

Upgrade ESX 3.x to ESX 4.0 con VMware vCenter Update Manager

We continue in the process of migrating the VMware Virtual Infrastructure environment 3 to VMware vSphere 4. We first upgraded the VMware VirtualCenter server to VMware vCenter Server, later we will have migrated the VMware Update Manager component to VMware vCenter Update Manager 4.0. After this, we will now be able to upgrade from ESX to the 4.0. All this, of course, taking into account whether our ESX hosts are fully compatible with the new version, to do this, check it in the VMware HCL.

Migrate VMware Converter Enterprise to VMware vCenter Converter 4

Like VMware vCenter Update Manager, if we were using VMware VirtualCenter in our environment 2.5 the VMware Converter Enterprise, we need to update it to the latest version in order to use it in our new VMware vCenter environment 4.0. If we update the, We may continue to retain existing configurations in the previous environment or logs… It will be a process that we can carry out at any time, once we already have our VMWare vCenter server in the 4.0, We can upgrade it when we need it, once we update the Update Manager or at the end of the migration process.

Migrate VMware Update Manager 1.0 a VMware vCenter Update Manager 4.0

After migrating our VMware vCenter server from the 2.5 to the version 4.0 (HTTP://www.bujarra.com/?p=2700) we have to update the other components that we have installed, in this case we will update the VMware Update Manager environment 1.0 that we had in VMware Virtual Center 2.5 to the new environment for use with VMware vCenter 4.0 (vSphere), called VMware vCenter Update Manager 4.0. This will be a process to be performed before proceeding with the migration of the environment 2.5 a 4.0, since after updating the Update Manager, we will update ESX hosts from version 3.x to the 4.0, and then the virtual machines (both the hardware version of the 4 to the 7 and VMware Tools to the latest version). All this in future documents.