Migrate the five roles between domain controllers and forcing in case of failure

To migrate roles between different domain controllers, for example from a Windows 2000 to a Windows 2003, or a Windows 2003 to another 2003… or simply to distribute the load among the DCs. It doesn't matter in which the process is carried out. It can be done in two ways, Mediate GUI, or by commands. And there is a third way that would be aggressive in case the Active Directory does not work correctly and we must force the transfer of the functions – HERE.

Installing and Configuring Microsoft SoftGrid – Application Virtualization for Terminal Services

GOOD, What is this? A new product from Microsoft? Of course not, Something bought, of course. How to describe it, It's something that distributes virtualized applications to whomever we want. Exactly, We have an app called “Softgrid Sequencer” which what it does is virtualize an application. This virtualized application is saved on and distributed from the Softgrid server, Who? to XP/Vista stations or terminal servers. For what? To avoid running around installing a post x post application or TS server x TS server. It is used to run an application that we do not have installed on our XP, for example Winrar, but we would have the direct access and when we open it that application comes from the Softgrid server to us and we execute it as if it were installed, but without being since it does not generate anything in Program Files or in the Registry… […]

Installing and configuring Microsoft Search Server 2008 Express

If what we are looking for is a product that allows us to carry out internal searches in our network, mainly about files and web addresses and what we are interested in is that it is easy to use for users, via browser, intuitive, how they regularly search the internet, Search for documents in your own network… this free tool is offered to us by Microsoft, Call Search Server 2008. In this document we will explain how MSS is installed and configured to allow users to search wherever we configure.

License a Terminal Server on Windows 2003

To be able to work with Terminal Services for more than 90 days you need to buy licenses and activate them. The part of buying them we leave to the Department. Commercial :), Here's how to install them on a server so that they don't expire and users can work perfectly. This procedure explains how to license a Windows 2000 Server, but it's exactly the same for a Windows server 2003.

Configuring iSCSI on Microsoft Windows

iSCSI is something like :P, is having a disk server (SCSI disks, SATA or IDE with the types of RAID we want to mount), That disk server connects to the network and tricks our other Windows server into accessing those disks as if they were physically connected, Here's a graph of the example you'll see in the document:

Securing our LAN using IPSec, between Microsoft Windows 2003 and Microsoft Windows XP

IPSec is a network traffic encryption protocol. In this procedure I do a test of how to encrypt communications between a client PC (XP) and a server (2003). The server 2003 has the IP 192.168.0.3 and has FTP server enabled, the thing is that the XP is connected to the FTP server to download some files, but between those two PCs there is a 'kapuyo'’ With a sniff, and since FTP traffic and almost everything on the network is unencrypted then the 'kapuyo’ has taken out the password with which the XP has been authenticated in the 2003, all this happens in the same network, in the same domain (XP and 2003 At least). In order for all traffic to the server to be encrypted I will enable the IPSec services and on the client also to talk to each other in 'IPSec'.

Upgrade to Microsoft Windows 2003 R2

This procedure explains how to update a Windows environment 2003 to Windows 2003 R2. If it were a Windows 2003 No roles in the active directory could be upgraded seamlessly, it just puts the Windows CD2 in 2003 R2 and install with the wizard. But things change if you have a role in the active directory or if you, we directly want to migrate our domain to an R2 version of 2003.

Automated installation of Microsoft Windows using response files – Unattended setup answer file

This is for, Even the administrators work less!! 😀 Or good, If not, that, our work is more comfortable, if you waste a lot of time installing PCs with MS Windows and it's always the same, with the same data, or similar, I mean the data from when you install Windows, The data you ask for, So much NAMEPC, DOMAIN, RED Configuration, Serial Number… to install a Windows CD and totally go from asking us and getting the answers from a floppy disk, prepare what's called a response file, or “Unattended Setup Answer File”. We can put it together with the RIS (HERE) and the use of distributed software (HERE) to make it even more convenient to install a PC in a domain and its respective applications/configurations.