Installing Windows Server Functions and Features 2008 Command Line

In this document, describes what parameters we can use with the Windows Server ServerManagerCmd command 2008 to add, Remove or view functions or features. Since it will always be more comfortable to use the command line to install some functions or features, or directly generate a response file with the parameters we need in case we are always mounting the same type of servers. All thanks to ServerManagerCmd.exe.

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.

Setting up Microsoft Exchange 2007 with SCC (Single Copy Cluster) on Windows Server 2008

In this document, we will see how to set up a high availability cluster for our Microsoft Exchange mail server 2007 Server with the Microsoft Windows Server operating system 2008, in this case we will set up a cluster system called SCC (Single Copy Cluster o Clúster de Copia Única). In this previous document the rest of the possibilities that we would have are described, we may be more interested in one system than another (HTTP://www.bujarra.com/?p=2362). As discussed above, SCC is the cluster that we can know from previous editions of Microsoft Exchange, is a shared storage failover cluster system, This is, we will have several nodes with the 'Mailbox function' one of them being active and the rest passive. Storage must be shared, Databases must be in an array or remote storage system, iSCSI, fibre... When the active node fails, One of the nodes in a passive state […]

Different types of Microsoft Exchange high availability 2007 (CCR, SCC, CSF & SCR)

Well, After a long time out, with a lot of work, I had time to look at myself and wrestle with the different types of high availability that Microsoft Exchange gives us 2007 to date. Unlike Microsoft Exchange 2003, This version, brings more possibilities to have a high availability of our mail server, having different methods, some cheaper than others and more or less complex. In principle, we have: CCR (Cluster Continuous Replication o Replicación Continua en Clúster) SCC (Single Copy Cluster o Clúster de Copia Única) CSF (Local Continuous Replication o Replicación Continua Local) SCR (Standby Continuous Replication o Replicación Continua en Espera)

Automated installation of Exchange prerequisites 2007 on Windows Server 2008

In this document, explains how to automate the installation of one or more Exchange servers 2007, basically the requirements of the installation. In this Technet article http://technet.microsoft.com/en-us/library/bb691354.aspx shows how to create scripts to install Exchange prerequisites 2007 and Windows Server 2008 to install the Exchange feature you're interested in 2007 via command line. With this website you can generate some response files (XML) to install whatever you need.

Upgrade the Windows Server Edition 2008

It's pretty simple, but necessary on certain occasions, When we should update our server edition, be Windows Server 2008 Standard a Windows Server 2008 Enterprise or Windows Server 2008 Datacenter, or Windows Server 2008 Enterprise to Windows Server 2008 Datacenter. Usually why we have expanded the RAM and our operating system does not support so much, or why we need to install a feature or function that is not in the current edition of our server.

Creating a High Availability Cluster on Microsoft Windows Server 2008

After viewing a document on how to create shared storage for a cluster, Why not create one? Well, the process is similar to Windows 2003, now we will do it for Windows 2008, A new cluster, and it will be for a file server, failover clustering, The process for another type of cluster is similar. With this we will achieve high availability, that if one of the servers falls (node) Don't worry., since there are other nodes that can take the resources and lift the services so that users can work practically without noticing the fall of the node they were working against. Also comment that maintaining a cluster is expensive, This is, We will always keep in mind that both servers will have the same applications installed, in the same way and with the same versions, all this to avoid future problems. It is also advisable to balance the cluster […]

Creating an iSCSI Target on Windows Unified Data Storage Server

In this document, we'll see how we can create an iSCSI Target with our Windows operating system, No third-party apps, we can create or assign virtual disks to the iSCSI Target to later use them in shared storage, To set up a cluster… What we will need is a compatible Operating System, or a Windows Unified Data Storage Server, It's an OS. OEM, This is, that are already pre-installed with the equipment when we purchase it from our manufacturer. If we have a Windows Server 2003 o Windows Server 2008, we should update it to these editions, I will comment on this in another document, to be able to have OEM operating systems on virtual machines (For example).

Using VMware View Composer

GOOD, this may be VMware View's most attractive product, the VMware View Composer, with this product, what we will achieve is to distribute Desktops to users from the same image for everyone. Without having to go around cloning a source VM, or have one full virtual machine per user, This is, the desktops we generate from this will not have a virtual hard drive, If not a link’ to a replica of the original virtual hard drive. With this we will achieve impressive storage savings, For example, if we design that our Desktops we want them to have 20Gb of disk, You don't need to allocate that amount to each VM, if, for example, we are going to distribute 50 Desks: 50MV x 20Gb = 1TB of space for VDI or VMware View environment only, as this does not make much sense, VMware View Composer is used to deploy Desktops from […]

Script to run when you're on Citrix or Terminal Server but not on-premises (or vice versa)

Although it may seem a bit simple, I'm forced to have to post this, since many people have asked me for it and to put it here… How is it free… 😉 Well, is as simple as a script that will be executed at the login login of the users of our Active Directory, through policies or GPOs. There are many times that we want users to run a certain script when they're on Citrix but not when they're on-premises, or the other way around 😉 when they are in the local that they execute a certain script, but when they are in Citrix or Terminal Services they are not.