In this document we will be able to see all the requirements and steps that we must take to proceed with migrating a Microsoft Exchange environment 2010 to Exchange Server 2013. We must bear in mind that it is a long process and especially depending on the number of servers as well as mailboxes we have or their sizes, It will be a migration that will not require a service stop at any time.
In this document we will see a manual migration process of an organization with Citrix XenApp 6 or 6.5, we'll look at how to export both policies and apps from our old farms to a new community in Citrix XenApp 7.6, optionally we can also make an on-site upgrade of the XenApp 6.x servers themselves to VDA 7.6 to be able to reuse them!
One of the many new features that the version brought 5 VMware Mirage was Windows support 8 and Windows 8.1 as a centralizing desktop and at the same time gives us the possibility to migrate Windows systems 7 to Windows 8/8.1 in a very simple and very fast way. In this document we will see how to deploy a corporate OS layer with Windows 8.1 to a Windows 7 and upgrade your system while maintaining your user data layer!
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 […]
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.
In this document we have the explanation of each FSMO function or role that our domain controllers will have. We will also look at how to transfer these functions between domain controllers and the recommendations to consider.
This document describes the process of upgrading Symantec Backup Exec 11d to the Symantec Backup Exec version 12. It's a pretty simple process, but we must take precautions, lest disaster strike.
This procedure is like data migration, instead of moving data, Printers are moved with two other Microsoft tools, PRINTMIG (HERE) and FIXPRNSV (is on the MS Windows CD 2003, If you can't look for it, download it, but it's 14Mb! HERE). It does the same as the previous one, copies NT4-based server drivers (SERVERNT) to Windows-based server 2003 (SERVER02) and shares them with the same name they had before.
In this procedure we will migrate the printers from one server to another, it doesn't matter the operating system of the origin and the destination. This procedure copies the printers, your drivers and their configurations to the target with the Microsoft tool, PRINTMIG (HERE).
Do Tailor-made training
Windows Server – VMware vSphere – Citrix Virtual Apps & Desktops – Centreon
|
We are a consulting firm that cares and pampers
|
 |
|
With quality and added value
|
 |
|
¡Let's work together!
|
 |
