Category: Migrations

Data Migration between 2 Untrusted domains (Subinacl)

In some not very frequent cases we find domain migrations in which we do not have permissions to manage the current domain completely and only access to OUs where we manage only the users within them. In the event that we need “Becoming independent” and migrate the data to a new domain, we will not be able to use Microsoft's common tools such as FSMT since they require a trust relationship to be able to pass the permissions. The first thing we must have is to create the same users and groups on the new server. To do this, we have two options: Create them by hand or use a tool such as ldifde that will allow us to export them from the OUs we have permissions to a text file and import them into the new domain. As there is no trust relationship, we will not have the same SIDs in the users of the domain 1 and mastery 2 so when performing […]

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.

USMT Application (User State Migration Tool)

This application will help us to migrate user profiles, either from one computer to another or to migrate the machine from a Microsoft Windows XP operating system to Microsoft Windows Vista, or directly if we are going to migrate from a Workgroup to a domain, or from one domain to another. All the information will migrate to us, User profile settings and data, are certified or are files encrypted by him (EFS), as well as ACLs (Access Control List) of the files… We can also do this using variables or XML configuration files.

How to Migrate a Print Server to Windows Server 2008

Today, In this document, we'll look at how to migrate a print server from a Windows 2003 to a Windows Server 2008 or directly between Windows servers 2008. It's pretty simple, since the new printer server will allow us to export configurations and import them into the new server, carrying drivers if they are compatible and sharing print queues, it will configure the destination server as the source server was.

Migrating a File Server Between Any Windows Server Version

Very good, In this brief document we will see how to migrate a file server in the simplest way between any version of Microsoft Windows Server (Windows NT, Windows 2000, Windows 2003 o Windows Server 2008). It's just cool and fast, that will allow us a hot migration. In this document we saw how with the Microsoft FSMT utility (File Server Migration Toolkit) could help us with a file server migration (HTTP://www.bujarra.com/?p=961), but if what we want is to avoid installing software, The following will be interesting.

Renaming a Windows Server Domain Controller 2008

In this document, we will discuss the proper steps for renaming a Microsoft Windows Server-based domain controller 2008, I know it's something unusual, but we will have to take it into account for when it is time, since there are several reasons that come to mind ;). We can run this wizard through GUI or via command line, I will choose this last option since it will be valid for Windows Server servers 2008 Core. We will take into account that if the server has the role of Certificate Authority or Certificate Authority (AC) We will not be able to change the name.

Migrate a Microsoft Exchange organization 2003 o Exchange 2000 to Microsoft Exchange 2007

Well, In this document we will see what is the migration process of an environment with Microsoft Exchange mail service 2003 to Microsoft Exchange 2007. We must bear in mind that it is not possible to perform the migration on the Exchange server 2003 in situ, if not we must, first prepare the Active Directory schema to support an Exchange 2007, then we will perform the Exchange installation 2007 on another server, once the installation is complete, we will replicate the public folders and migrate the Exchange server mailboxes 2003 to the Exchange 2007. We will finally uninstall the Exchange 2003 of our organization.