Windows Server 2008 as a Workstation OS

Windows Server 2008 comes in both x86 (32-bit) and x64 (64-bit) versions. It has received two service packs up to this time. It is heavily supported and Microsoft does an amazing job of handing out security patches and updates frequently. The second release of Windows Server 2008, called as R2 comes only in a 64-bit version. It might not be the best choice for some workstation setups; it depends on the user.

We recently featured an article here on ASP Free that gave a brief overview of the additions and enhancements that R2 brought to the table. Since we aren’t focused on enterprise usage here, but rock-solid and performance-oriented workstation usage, we can fortunately state that opting for the original Windows Server 2008 (R1) instead of R2 is not much of a deal-breaker. But if you don’t mind going 64-bit, do so.

Most people probably wonder, "What’s with the hype for using a server operating system for a main workstation OS, especially if it’s based on Vista?" Intuition tells us that there should be no significant difference. Now that Windows 7 is around the corner (or may even officially be out by the time you’re reading this!), why the hell would anyone want to use Windows Server 2008 at home?

The answer might be complex, if you’re looking for benchmark numbers comparing integer and floating-point mathematical equation crunching algorithms and their results organized in fancy charts and graphs. However, the real reason why some enthusiasts opt for server operating systems is because they are highly modular.

Windows Server 2008 is role-based. You can configure almost everything on it. It is not bloated at all. It does not come with “unnecessary” multimedia software packs that you aren’t asked about during the install process, and many other apps are also left out. The number of running services is also stripped-down, big time. It offers more scalable environments, a secure network infrastructure and management tools to save time.

In the following pages we will explore some of the tweaks necessary to make the workstation experience under Windows Server 2008 possible.

First of all, we will assume that you got your hands on a license for Windows Server 2008. This is the only tricky hindrance to running a server operating system as a workstation. As expected, the price of a server OS license is much higher than a desktop OS. However, you can always beta-test or evaluate RTM releases—being able to extend to 240 days, the trial period is truly beautiful—and if you have a MSDN and/or TechNet account, then you’ll end up spoiled by Microsoft.

All right, let’s get down to work. You’ve got your WSS2008 up and running. If you’re like most people, you have already ticked the checkbox for not showing the Server Manager interface at each logon. Another obvious step that you might have already taken is grabbing the latest drivers for your components, such as video, audio, and who knows what else. You need up to par video drivers to enable the Aero experience.

During the process of installing drivers and applications, the operating system asks for a reboot numerous times. You might notice the Shutdown Event Tracker. It’s pretty annoying; let’s disable that. Chances are you do not want to log your reboots and to specify a reason each time you shut down your workstation PC.

Run -> “gpedit.msc” without quotes, look inside Computer Configuration -> Administrative Templates -> System. You will find there an entry called something like “Display Shutdown Event Tracker.” Set "disable" there.

In order to enable the full Internet Explorer browsing experience without that Enhanced Security feature, visit the Control Panel, and within the Add/Remove Programs window, look inside Windows Components. There you will find listed “Internet Explorer Enhanced Security Configuration.” You can uninstall that. If you don’t want to totally remove this feature, then you can temporarily disable it from Server Manager -> Configure IE ESC.

Moving on, despite having installed your audio drivers, you may wonder why it just doesn’t seem to work. Windows Server 2008 does not start the Windows Audio service by default on boot-up. It’s understandable; you don’t need  unnecessary processes/services such as audio in the case of servers. To enable it, run “services.msc” and look for the “Windows Audio” service. Start it. But also set its Startup Mode to "Automatic."

Now that you’re inside the services management snap-in, don’t close that window. Also search for the service called “Themes.” Set its startup mode to Automatic as well. This process provides the theme management for the user interface. Your OS is pretty much XP-like by now. We will get into hooking it up with the Aero Experience right now...

Start the Server Manager, select Features Summary, and obviously Add Features. From the list that pops up, select “Desktop Experience.” While you’re there, do select other features you prefer, such as .NET 3.0 if you need it, or BitLocker Encryption, etc. After this step, just browse to the Control Panel, Personalization – Themes – and Aero.

The Desktop Experience feature not only installs Aero-related components, but also Windows Media Player. That should suffice for most people. But if you want a complete codec pack (such as K-Lite Mega Codec Pack) then don’t neglect to install your favorite. The same goes for media players. You might prefer something like VLC, KMPlayer, etc.

By now your Windows Server 2008 operating system is pretty much configured to serve as a power-horse workstation. We still have a few more tweaks to present, however, which can enhance your all-around experience.

Everyone knows that server operating systems prioritize server applications and services that are running in the background. The OS cannot allow these to become unresponsive or lag. But in the case of a workstation OS, you aren’t running power-hungry daemons; you want priority on the software you’re running in the foreground—the ones with which you are working. Let’s change that prioritizing setting now. Look below.

Control Panel -> System and Maintenance -> System -> Advanced -> Advanced / Performance -> Settings, Advanced -> Processor Scheduling

As you can guess, we want to select the "Programs" checkbox. Moving on, you also have the settings for Visual Effects. Tune these according to your preference.

There is another feature that is called SuperFetch. It’s a new technology that was introduced with Windows Vista. It “intelligently” caches your most frequently used applications so they load up much faster. Windows attempts to guess which apps you are going to use and when. It sounds weird, but it helps—more often than not, at least.

Fire up your Registry Editor (Run -> “regedit”) and find the following registry path.

HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlSession ManagerMemory ManagementPrefetchParameters

Once you’ve found the above key, you need to create two new DWORD entries: EnablePrefetcher and EnableSuperfetch. Set both of them to value 3. Once this step is done, you can find the SuperFetch service within the “services.msc” snap-in.

In the case of workstation machines, you may want multiple profiles or to enable auto-logon functions as well. Should you want to add another user profile, Start -> Run -> “control userpasswords2” and set up your new user. We recommend placing the users within the Administrators group so that you don’t need to mess with the policies later on. If you choose Standard, the user cannot reboot/shutdown the machine.

Of course, that can be modified within the policy management snap-in, or the user can later be placed within the Administrators group as well. Enabling auto-logon isn’t that tough either—at the same window where you’ve added the other user profile you can "uncheck" the “Users must enter a user name and password to use this computer” function. After this, select one of the users, and auto-logon is enabled on it.

Wireless Networking is hardly ever required in the case of servers, but that changes when you’re using a server OS for a workstation. For example, the author of this article set up Windows Server 2008 R2 on a laptop. Wireless networking is required in some cases. Fire up the Server Manager, Add Features, and pick “Wireless LAN Service.” Once you’re there, you might also want to set up Windows Search as a new server role.

Universal Plug ‘n’ Play (UPnP) can be found within the “services.msc” as well. If you need this service, set its start up mode to Automatic. Actually, there are two instances; these are called: “SSDP Discovery” and “UPnP Device Host.”

As a final step we suggest messing with group policies (local policies in our case) to further customize specific aspects of your operating system. Launch this snap-in with the command Run -> “gpedit.msc.” For example, this is the place where you can disable the strong password enforcement policy (Computer Configuration -> Windows Settings -> Security Settings -> Account Policies). Aside from this, there are hundreds of others.

Should you want to install the Vista Sidebar look here. The same goes for custom gadgets.

As you can see, we’ve slowly but surely reached the end of this article. We have thoroughly described most of the steps that are necessary to enable a Vista-like experience and XP-like workstation capability. Chances are you’re already amazed at how responsive and reliable the operating system seems.

However, please do remember that this is a server operating system, and some of your favorite applications and software suites might refuse to install. In the case of other software, you will be asked for Server Edition versions, and desktop suites won’t work anymore. This applies to some antivirus software (e.g.; Kaspersky and others) but also hundreds of other program. Compatibility Mode for XP does not suffice.

From a drivers perspective, Vista drivers ought to work without any trouble on Server 2008. This is true, and indeed we haven’t encountered any problems. All in all, we want to stress the fact that maintaining a server operating system is not for everyone. It comes with higher costs (i.e. licensing for the OS, but also for additional applications that require a server license) and sometimes requires additional administration (which takes time).

That is mainly the reason why almost always IT professionals, enthusiasts, and development professionals end up with this kind of workstation setup. It's simply because they can afford the extra time and costs to have a rock-solid, robust, and fully modular (role-based) and customizable operating system with server functionalities! And these experts also appreciate the simple fact that server OSes aren’t bloated.

In closing, I’d like to invite you to join our experienced community of technology professionals on all areas of IT&C starting from software and hardware up to consumer electronics at Dev Hardware Forums. As well, be sure to check out the community of our sister site at Dev Shed Forums. We are friendly and we’ll do our best to help you.