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.

Using AdRestore to recover Tombstone items

What is a Tombstone? Well, when we delete an object in the Active Directory it is not deleted directly, if not, the attribute 'isDeleted' is checked’ as 'True’ and is hidden from the normal view of AD consoles in addition to moving to the 'Deleted Objets' container. Eye, almost all but the most important attributes like GUID and SID are deleted. These objects remain in the Active Directory as Tombstone's until after 90 days, once this time has elapsed they are eliminated by the 'Garbage collector'. What is the Garbage Collector? It is a process that runs the Active Directory by default every 12 hours, although this parameter is modifiable in the attribute 'garbageCollPeriod'’ in the configuration object (NTDS). This, apart from removing the Tombstone's, also defragments the Active Directory. All of this comes in handy when using the Sysinternals AdRestore tool, since this utility allows us to […]

File Server Resource Manager in Windows 2003 R2

The file server resource manager allows us a series of improvements in a file server. We can enable quotas at the directory level and if we are interested, By means of some directives we can filter which types of files are not going to be saved on the server by extension. And we can generate reports to show us the correct or incorrect use by users. It is necessary to update our Windows beforehand 2003 to Windows 2003 R2 – HERE.

Install an additional domain controller from a Windows backup, for low-bandwidth networks/delegations using IFM

This is technically called IFM (Install from Media), this is useful in case we have a domain and we want to expand it with more domain controllers and we do not want the Active Directory to copy us over the network to the new domain controller, For example, if what we are doing is a domain controller in a delegation that its Internet bandwidth to where the primary domain controller is is quite loose, copying the Active Directory database may take a couple of hours or more copying it. This is used for this purpose:, the system state of the primary domain controller is backed up and restored to the one we want to be an additional domain controller in a directory, and when joining it to the domain we use this restored data instead of replicating the AD.

Defragment or compact the Active Directory database in Windows 2003

In this document, we will learn how to compact and defragment the Active Directory database. This process must be carried out on each of the domain controllers that we have. With this we will achieve a higher performance, that the database takes up less space. Before starting with this wizard, it is advisable to make a backup of Active Directory. This document shows how to do this on a Microsoft Windows server 2003.

Using the Security Setup Wizard in Windows 2003

El SP1 de Microsoft Windows 2003 It brings a new tool that will help us when securing and configuring our server in security issues. It is a wizard that helps us secure our server by blocking certain parts of the registry, disabling unnecessary services, removing MS applications that are not used and of course it would enable Microsoft's firewall and close ports that are not needed.