<< Ask and I shall receive! | Home | Seattle's BUZZ 100.7 attacks Child's Play >>

Windows Server 2003 as a Workstation OS

This topic comes up so often in so many places that I thought I’d compile a list of reasons why someone might run Windows Server 2003 on a workstation.  If you have anything to add, please comment. 

Reason 1)  The Developer.

I’ll use this example first since it’s the one that applies to me.  Developing applications that require Windows Server functions in many cases will require you to run Windows Server.  Yes, there are alternatives… You can have a development workstation and a full test server, or you can run Windows Server in Virtual PC.  But there are a great many cases where developing applications for ASP .NET, Windows Sharepoint Services, and other Server functions is made far, far easier by actually developing directly on that platform. 

Reason 2)  Workstation versions.

Windows XP “2002 Edition” is built on Windows NT 5.1.2600.

Windows Server 2003 is built on Windows NT 5.2.3790.

Windows XP “2003 Edition” for 64-bit Extended Systems is built on Windows NT 5.2.3790. 

That OS is very clearly targeted at workstations (as the “XP Professional” branding indicates).  It is, however, built upon the Windows Server 2003 codebase (in fact, it’s built on Windows Server 2003 SP1).

Reason 3)  Terminal Services.

As was pointed out to me by a reader, Windows Server 2003 is used in countless organizations for its Terminal Services functionality for their desktop and workstation computers.  In fact, one of the hospitals I work with uses Windows CE thin-clients for just that.  In these cases, a great deal of desktop functionality is required.

Reason 4)  Windows Server 2003 works wonderfully as a workstation OS.

            It uses the same driver model as Windows XP.  It includes DirectX 9 and all the desktop features of Windows XP Professional.  It even includes Windows Media Player 9, and even some games!  It includes the “Themes” service and the Windows XP “Luna” theme.  It runs any program that Windows XP does, except where an installer or application explicitly checks the OS version number.  And in those few cases, there are easy workarounds. 

 

Do most people need Windows Server 2003 on their computers?  Of course not.  Should anyone illegally obtain Server 2003 to replace XP on their home computer?  Again, of course not.

But are there valid reasons for users asking questions about non-server functions of Windows Server?  Yes.  In fact, there are several.

Please feel free to comment.  I’ll add any pertinent information if there’s something I left out.

posted @ Tuesday, December 07, 2004 4:59 PM

Feedback

# re: Windows Server 2003 as a Workstation OS

I've used W2003 in the past, but I was never able to use some tools (like VPN client), and I finally gave up on my laptop since the appropriate video drivers for wide screen did not exist. 12/7/2004 5:25 PM | Paul Wilson

# re: Windows Server 2003 as a Workstation OS

What do you mean?

Resolutions are independent of the driver file. And any driver installation that works on XP will also work on 2000 and 2003 (the driver model is the same for all three).

If you're referring to one of the wacky resolutions (like 1400x1050) that Toshiba and Dell sometimes use, those always require either original drivers from the manufacturer, or specially modified INF files for installing the Nvidia reference drivers.

If you stick to the drivers that your laptop manufacturer provides, they should install on Windows Server 2003 just as they would on 2000/XP. 12/7/2004 5:36 PM | Brandon Paddock

# re: Windows Server 2003 as a Workstation OS

Nice theory, but its not reality. Yes, I am talking about the "wacky" wide resolutions (1280 by 800 in my case). And unfortunately the XP drivers just do not work under 2003. I tried many times and many different variations, contacted support, and read others experiencing the same thing. 12/7/2004 6:22 PM | Paul Wilson

# re: Windows Server 2003 as a Workstation OS

What kind of video chip does your laptop have? And who makes it?
Were you using drivers from the laptop manufacturer or reference drivers from nvidia/ati/intel/etc.?

If the drivers you installed did not let you select the proper resolution, you could always add it manually to the registry or by using a program like PowerStrip (or half a dozen others).

"Nice theory, but its not reality"

It's not a theory. Please don't insult me when I'm trying to help you. The Windows 2000 driver model has not changed. All versions of Windows NT 5.x use the same drivers. The only difference between a driver labeled for 2000/XP and one labeled for 2003 is the different WHQL certification program (the 2003 drivers have different standards to live up to).
12/7/2004 7:41 PM | Brandon Paddock

# re: Windows Server 2003 as a Workstation OS

Also, I don't think 1280x800 is one of the "wacky" resolutions I was talking about, as that looks like a normal widescreen resolution. What I was talking about are not widescreen resolutions (at least 1400x1050 is not), but rather a resolution that requries a special INF in order to make it available... regardless of the OS. 12/7/2004 6:50 PM | Brandon Paddock

# re: Windows Server 2003 as a Workstation OS

Hi

I read your article about Windows Server 2003 being used as a workstation and it looks very interesting.

The only problems I think you might run into if you install it on your computer to replace Win XP are:

1-The software designed for Windows XP Pro doesn't run on Windows Server 2003 (e.g.: Norton AntiVirus, Norton Personal Firewall, SpyBot, Ad-Aware, MS Money, AOL IM, etc.)

2-The drivers specifically designed for Win XP Pro, like for example : ATI RADEON video-card drivers and Sound Blaster Audigy sound card won't run on Win Server 2003.

I could continue numbering more problems you may get into if you wipe out your hard drive contents (e.g. : Win XP Pro) and do a clean install of Win Server 2003 but I wouldn't be able to finish.
I'm talking about my own problems because I tried that before and it didn't work for me, so I went back to Win XP.

BTW my PC is an HP that I bought at Best Buy.

Take care
Robert 12/7/2004 11:18 PM | Robert Lombard

# re: Windows Server 2003 as a Workstation OS

Hey Brandon,

First, I'm using Windows 2003 Server right now. It's a development machine, but I've had no problems with software - unless the manufacturer specifically writes it to check the OS, but even then, you can get around that.

The main reason I use Server 2003? Multiple web sites. To get it to work in XP, it's a hack, and only one will run at a time. In 2003, I can have as many as I want, all running at the same time. Being a web developer, that's important to me.

----------------

Robert,

I also have an HP (although not from Best Buy), and use Norton Antivirus, SpyBot, Ad-Aware, AOL IM, and just about any software, and have no problems whatsoever. I've even played Halo for the PC on it! Oh - I use Cisco's VPN client, and have used Check Point's VPN client, both at the same time. And of course, the built-in PPTP VPN without issue.

----------------

As for the comments about monitor resolution, mine is set to 1400 x 1050, with no problems.

Joel 12/7/2004 10:35 PM | Joel Ross

# re: Windows Server 2003 as a Workstation OS

Good, I'm not crazy :P

I have never seen any of those apps cause problems on Windows Server 2003 (except of course really outdated Norton software, which won't work on XP either).

ATI Radeon and Creative Sound Blaster drivers work fine on Windows Server 2003.

The ONLY issue I know of there is that the DVD-Audio module for Creative's Audigy 2 line of cards does not work, at least not by default. But every other Creative app works perfectly (just don't let it install the DVD-Audio module, or you'll get a BSOD).

But that's the one exception I know of, in a sea of successful examples. And it's a fairly obscure issue as well. 12/7/2004 11:15 PM | Brandon Paddock

# re: Windows Server 2003 as a Workstation OS

Just to clarify, I have run both Windows Server 2003 (32-bit) and Windows Server 2003 x64 Edition on my home/development machine several times.

I am not, at the moment, because I've become very attached to the Media Center Edition 2005 functionality only available with XP.

But at work, my development machine runs Windows Server 2003, as that is my target platform for my current project. And when I need to work on it from home, I just remote desktop in.

12/8/2004 12:17 AM | Brandon Paddock

# re: Windows Server 2003 as a Workstation OS

Sorry if you think I was insulting you, as that was not my intent. I only meant to say that I have heard that said before, but my experience and that of many others (already another one here and search the net for more) suggests things are not so simple. Maybe I should feel insulted since I was not able to get it too work even though some assure me it will, but I don't think you meant to really insult me any more than I intended to insult you. I can even accept that some like yourself do know more and are able to get it to work, as I'm not anywhere near as good at such things as drivers as I am with other things -- I just know that I could not get it to work by myself, nor with the help of someone far better than myself that I respected, nor searching the net, nor through my laptop's customer support. So in the end it wasn't worth trying anymore, since I only wanted IIS6 and multiple sites, neither of which was really worth continuing the trouble, especially since there are other things that don't work the same also (like my VPN client, anti-virus software, etc.) 12/8/2004 10:20 AM | Paul Wilson

# re: Windows Server 2003 as a Workstation OS

I started using windows server 2003 as a desktop. I recently acquired a Dell dimension desktop. Initially the drivers did not install by saying there was no drivers available on the support CD. When i explicitly forced the XP drivers they installed just fine. I have to yet check for DVD writing! Ofcource i am using the 32 bit verion of windows server. I actually like the clean interface it provides. And it boots up faster than windows XP pro i used to use previously! 12/12/2004 4:13 AM | Murthy

# re: Windows Server 2003 as a Workstation OS

I use Windows Server 2003 as a Workstation too.
But WMP 10 does not give in :( 12/15/2004 3:07 PM | Konstantin

# re: Windows Server 2003 as a Workstation OS

how would we can play games on the server2003
12/21/2004 1:50 AM | koki

# re: Windows Server 2003 as a Workstation OS

plz i want the steps to make my windows 2003 as aworkstation any body know plz send me the steps by @mail
thax 12/21/2004 1:53 AM | koki

# re: Windows Server 2003 as a Workstation OS

how can I make win CE clients to accept the resolution that is set on win 2k3 server? 12/21/2004 2:46 PM | klair

# re: Windows Server 2003 as a Workstation OS

LINUX RULES! 12/26/2004 9:29 AM | winsux0r

# re: Windows Server 2003 as a Workstation OS

What are these workarounds that allow xp installers to run on server 2003??
where can i find more info as i have server 2003 and running it as a dev platform and require to install some xp programs but i'm getting the os incompatable. 12/27/2004 11:27 PM | Sam

# re: Windows Server 2003 as a Workstation OS

Depending on the type of installer, you can sometimes use the Windows XP/2003 compatability stuff to "trick" it into working.

This involves right-clicking on the setup.exe file, and going to the "compatability" tab. There you should be able to set the OS you want Windows to "pretend" to be.

For MSI files, that usually doesn't work.

The MSN Desktop Search Suite installs with the following method:
use setup.exe /c /t: to unpack
then run
msiexec /i MsnToolbarSuite.msi TBSDEVCODE=1

But that might not work either. In such a case, go here:

http://weblogs.asp.net/jhoward/archive/2004/12/13/281924.aspx

12/28/2004 12:05 AM | Brandon Paddock

# re: Windows Server 2003 as a Workstation OS

As an IT admin, I find it very worthwhile to run Server 2003 as a workstation. Helps me to have a better feel for the ins and outs of the system. That said, I wanted to give many thanks for the pointer about not installing the DVD-Audio module. I had installed it with the module initially and was getting a blue screen after boot-up. After removing that module, all is running beautifully.

By the way, anybody who says Server 2003 is just for Server type roles is clueless. One of the tremendous benefits of Server 2003 is how well it works as a Terminal Server. Most of our users are no longer on Desktops, but on thin clients which connect to one of our Terminal Servers. This means the servers are running just about anything we would have put on a desktop ranging from Flash to Visio.

Nice page - Ciao! 12/31/2004 1:23 AM | John

# re: Windows Server 2003 as a Workstation OS

That said I would add:

Reason 5) The Network Administrator. If you really want to know the ins and outs of your OS, run it as your workstation. Sure you'll probably crash and burn a few times, but wouldn't you rather crash your server at home over a system critical server at your office! 12/31/2004 1:25 AM | John

# re: Windows Server 2003 as a Workstation OS

I just bought a Toshiba Laptop with XP Home edition installed. I need Windows Server 2003 on it and did a clean install of 2003 Standard edition on it last night. It didn't go well.
I went to Toshiba's website and downloaded all the necessary drivers and put them on a CD. After reading all these threads something tells me to try the clean install again and try forcing the XP drivers I downloaded from Toshiba's website. We'll see how that goes.
Also, worse comes to worse I will have to put XP Pro on it. What are some of the major differences between XP Pro and Server 2003 Standard? I know one is not a server-based OS but from a development standpoint.
Thanks. 1/1/2005 10:44 AM | Ali Khan

# re: Windows Server 2003 as a Workstation OS

First of all, thanks to everyone posting about Server03 and forcing the drivers from XP to go. I recently installed it at work and found that Server03 does really "fly" and now that I was able to read about being able to use it as a workstation well, I'll be installing at the home pc and see how it goes. Hardware I'll be trying to install on to is:

P4/3GHz ~ 1 gig RAM ~ Raptor HD ~ ATi x800XT ~ MSI MoBo ~
BuiltIn Audio & NIC ~ DVD&CD Burner ~

Anyway, before I start I'll create an image of my existing XP OS just incase. :) Thanks again guys and I'll be keeping you posted on how it goes. Cya . . .

Rick
1/3/2005 10:56 PM | Rick Pianelli

# re: Windows Server 2003 as a Workstation OS

Hey Rick - Im about ready to try the same thing at home on a backup machine with a demo I was given just to check it out and see how it compares... My stats are:

P4 3.0E / 512MB Memory / BFG 6800OC

Let me know how things go for you...

Skids

1/7/2005 2:10 PM | Skids

# re: Windows Server 2003 as a Workstation OS

Running Server 2003 as a workstation is actually cost-effective compared to say XP Pro and new devices. I do that at home to keep my IT management headaches at work. Users have limited accounts and can't do much to damage the system.

Try this :-)

Buy a cheap server from Dell like the 420sc (check fatwallet for deals on these) either with no OS or with OEM SmallBusiness Server 2003. Note that it comes with 5 CALs, which legally enables up to 5 devices to access it. The cost would be about $499 for the software or less (we pay under $450 usually). Most should just order the software OEM from Dell. Comparatively, OEM cost for XP Pro is $170/license plus hardware. You can put any PC3200+ RAM into it, so don't worry about special memory.

Running 2 client devices with any Microsoft OS that supports RDP client or a linux box running rdesktop enables you to not have to spend on new hardware to have very snappy performance on those older machines. Microsoft legally allows up to two concurrent RDP sessions in addition to the console session. They don't need to have admin rights if you modify the policies enough.

So, for the price of XP licenses, you get to extend the life of your aging or downright obsolete equipment. Another tip, you can send audio to your RDP client if you turn off the restriction on mapping audio in the terminal services manager. It works pretty well. Just don't try to view windows media video content. It will actually work, but not at 30fps.

I am personally using Visual Studio 2005 and Netbeans 4.0 on a 266mhz Latitude that has a licensed w98se on it running just the mstsc client on it while my other users use my nice LCD screen directly on the server, if I have to :). No more fighting. My host server is a Dell poweredge 400SC with 2.8ghz and 1Gb of RAM running SBS 2003 Standard.

I see no need to buy a replacement box for a couple of these laptops since deploying this configuration, maybe I'll get a 2001fp monitor instead.

It is interesting to see reaction of people on how fast "XP" runs on that thing... ;-)

This is an excellent solution for aspiring MCSEs, as you get Exchange and SharePoint as well. The Premium version adds SQL 2000, but MSDE works good enough for our purposes.

Don't try this under 1gb of RAM. Really. RAM is cheap - $170 on average for 2x512Mb pc3200 ddr sdram these days.

BTW, my ATI 9600 AIW is fully functional.

There is an interesting article over on msfn.org on how to make your server very much like a workstation. Some of the tips aren't trivial.

Note: Server 2003 has a substantially reduced HCL for NICs, so you may need to hack drivers from XP. The Netgear FX310 is particularly affected.

Enjoy,

Leonid 1/14/2005 5:21 AM | Leonid S. Knyshov

# re: Windows Server 2003 as a Workstation OS

From all these, does it mean that I can install Windows Server 2003 on TOP of my WinXP Pro and use it as though they're the same Windows ? I understand about the driver and application issues. I'm a home user and I don't really need any server functionality in Windows Server 2003 at all, but I can just ignore them right ? I just have some reasons that I have to use Windows Server 2003 instead of my WinXP Pro, not that I really want to do it though.

Also, could I just install Windows Server 2003 and also continue using WinXP Pro on the same PC ? If I could, could I completely remove one of the windows later if I need ? And if I just upgrade to Windows Server 2003 (install it on top of WinXP), could I revert back to WinXP later ? Without backup my harddisk that is.

Please understand that I'm a bit new to all this. Thank you very much in advance for all your replies.

Warat. 1/16/2005 12:24 AM | Warat

# re: Windows Server 2003 as a Workstation OS

The server versions are the only ones that have the RAID mirroring. This is why I run server on my workstation... 1/18/2005 6:49 PM | nospam

# re: Windows Server 2003 as a Workstation OS

Before I read this column, I just got off the phone with HP business sales: "A workstation is a PC, a server is not a PC. You can't run a server OS on a workstation...period."

I wanted to buy one of their workstations with Server 2003 installed on it. The guy really copped an attitude when I tried to discuss my reasons.

So, what to do? I am leaning toward buying the HP workstation (they all have XP pre-installed), then buying and installing Server 2003 Standard Edition.

But, and here is my question, how do I install it?

When I boot up the S2k3 CD, will there be an option to "replace" my existing OS? Will there be an option to reformat the hard drive(s)?

Brandon, a couple of pointers from yourself or a fellow reader would be greatly appreciated.

Thanks,

Hank 1/20/2005 2:56 PM | Hank Morris

# re: Windows Server 2003 as a Workstation OS

We've purchased a server for our office with Windows Server 2003 on it, and would like to use the machine as a part-time additional workstation in addition to its server functionality.

Does anyone see a potential problem with security running Server and general office applications, like IE with all its security problems, Office 2003, Adobe Apps, etc.? I'm a bit concerned about creating security holes by having all of the security-issue plagued software running on a machine responsible for serving as an office gateway and web server.

Thanks for help!

-Alto

1/26/2005 1:36 PM | Alto Cumulus

# re: Windows Server 2003 as a Workstation OS

Well, that depends.

If it's done right, I see no problem doing that, so long as the server is powerful enough to handle the load (you wouldn't want its workstation functions to slow down its server jobs - no one in the office would appreciate that).

What I'd suggest is this:

1) Keep IE Hardening turned on for non-administrators.
2) Make sure the users who operate the machine as a workstation are NOT Administrators or power users. They must be regular user accounts with the same privileges they'd be using on any other workstation.
If your network is properly set up, it shouldn't matter whether someone is physicall at the computer or connecting remotely.... they should NEVER have access that would allow them to compromise the security of your network.
3) Your group policy should enforce a secure working environment. This means blocking unauthorized installations, activeX controls, file downloads, opening of e-mail attachments, etc. This is especially important on the server, though really you should practice this everywhere in a mission-critical work environment.
4) Learn how to leverage EFS to encrypt vital confidential information.
5) Enable strong security audits and either check the log often or set up a set of automated alerts so you know if someone is trying to do something they shouldn't.
6) Educate your users. Make sure they know not to share their passwords or let unauthorized users access the system. If an employee leaves the business, make sure their account is disabled immediately.
7) Give new employees a probation period during which their privileges are restricted even more. Especially if you plan to or are required to give your users potentially dangerous privileges.

A properly set up IE won't have any security issues. The Server 2003 hardening mode will pretty much cover that. Of course, your must ensure that the system is ALWAYS kept up-to-date. I recommend you employ IE's Security Zones feature to delegate access to sites where it is required. One of my client's relies on Hotmail and access to a hospital's Citrix browser-based client program. The "Internet Zone" settings enforced by group policy will not permit the installation of ActiveX controls or active scripting. However, hotmail.com, passport.com (and .net), and the hospital's website are all in the Trusted Zone at this office, which allows them to work properly. 1/26/2005 2:38 PM | Brandon Paddock

# re: Windows Server 2003 as a Workstation OS

Someone above requested a link to how to setup server 2003 as a workstation. The following URL is the link I used to make my home pc with 2003 more like a workstation and less like a server.

http://www.msfn.org/win2k3/index.htm

Hope this helps, I know it helped me.. 2/3/2005 7:13 PM | Shawn

# re: Windows Server 2003 as a Workstation OS

Hi,
I'm using Windows server 2003 Enterprise Edition on my PC
Everytihing runs fine.

But i don't have any sound.
I cant install my soud card: Soundblaster AWE32 ISA.

I've tried to install it manually by clicking "Add New hardware"
i used " CDROM.inf" found on the CD-ROM.

Now it will say: Class Installer has dinied requets to update driver.

What to do now?

Yoichi D. 2/4/2005 3:38 PM | Yoichi DeeJay

# re: Windows Server 2003 as a Workstation OS

Yoichi, try enabling windows audio in services, then install the driver.

Joe 2/10/2005 1:14 PM | joe

# re: Windows Server 2003 as a Workstation OS

I'm using Win2003 as a desktop OS too - because the 180-days trial is free. I need it for checking websites in IE (God, damn this crap and its creators, please...) and playing games, nothing more. Maybe, sometimes, to check something developed on Unix with Qt/Win. And that's all.
Sadly, there are some bigger problems with display drivers. Generally, everything works, but in some cases, it starts to crash all the time. The most extreme example is Breed game, nVidia display driver (for my GeForce 5200) crashes every 30 minutes when I play it. Hell knows why. And every fourth or third crash, I must do a hard reset. The fact is that those drivers are not designed for Win2k3. That's really annoying, but I don't have money to buy an operating system (quite expensive one...) just to play games.
On the other hand, I would NEVER use it as a server. Lack of a properly made, remotely accessible text console with Unix-like power and capabilities makes this OS completely ineffective when it comes to administration, especially in a case of intrusion or some bigger technical problems, when time is essential and I can't afford making everything with clicking, because it takes HOURS, instead of seconds...
Conclusion? It's really useful for office tasks. They're simple enough to not make system crash. I've heard that it's good for graphics editors and engineers using CAD programs too, maybe that's true.
But it's neither a good home desktop OS, nor a good server OS... 2/13/2005 5:35 AM | Enleth

# re: Windows Server 2003 as a Workstation OS

As strange as this may sound I sort of want to go the other way I.E. get Server 2003 functions out of my XP Desktop, reading this page I have found some ppl who know what they are talking about and recon this is a good starting point, let me explain.

At work (as a unix sys admin / Core ISP engineer) I use Linux for about 85% of my work (for ssh and telnet sessions ) but I must use my XP host for Outlook and our CRM tool Heat Call Logging, in the past I have just used a NT4 Terminal serever and a citrix client on my linux box and just just had two / three sessions open, I know I could just usr RDP but I do not want the whole desktop just a few apps also I have tried WINE etc but Heat Client craps out on the ODBC connections thus its better on a Windows host.

any ideas please email me alex@alexswift.net Thanks


Alex

so I need to know if we have a hack that allows you to 2/14/2005 2:31 PM | Alexander

# Can W2k3 Webserver act as WINS Server?

As part of my network testing, I'd like to implement a replacement for my current WINS on NT. Does this service exist in W2k3 Web Edition? 2/16/2005 10:47 AM | Will

# Windows Media Player 10 & Web Edition

I tried to load Windows Media Player 10, but I got an error message. Any way to work around this? 2/16/2005 3:41 PM | M. Jackson

# How to Get WMP 10 to work on 2003

All you gotta do is install Windows 2003 Service Pack 1. 2/17/2005 2:58 PM | Janet Jackson

# re: Windows Server 2003 as a Workstation OS

Another thing I noticed yesterday: the drivers for Mustek BearPaw 1200 scanner (http://www.mustek.com.tw/Download/driv_scanr/europe/b1200.html) are officially for Win98/ME/2000/XP and some stupid, brainless dumbass who made them did an OS lock in the installer - this piece of crap refuses to install just because it's Win2k3, no matter it would probably work. Compatibility mode doesn't help. What you would suggest to do? Bug Mustek? Try to hack the installer? Any suggestions welcome... 2/20/2005 5:54 PM | Enleth

# re: Windows Server 2003 as a Workstation OS

Use WinRAR. 2/25/2005 11:39 AM | god

# re: Windows Server 2003 as a Workstation OS

Is it an MSI file? There are override commands for most installers (and almost all MSIs) to ignore the OS version check. 3/4/2005 3:53 PM | Brandon Paddock

# re: Windows Server 2003 as a Workstation OS

Hi.

I am running Windows Server 2003 on my laptop. The Laptop is an HP Pavilion, and everything runs OK. The reason I had for installing the server version of Windows is that audio drivers doesn't work well on Windows XP... Yes, it's true. The laptop has a label indicating "Designed for Windows XP", and the audio doesn't work fine. Searching any version of windows that works fine, I found Windows Server 2003. All the devices are working, and all of them work better on Windows Server than in Windows XP. 3/15/2005 6:25 PM | Manu

# re: Windows Server 2003 as a Workstation OS

I have an older adaptec isa scsi card that I use with my hp scanner. XP recognizes it automatically with built-in drivers, but W2003 refuses to recognize it. The driver for that exact card is not built-in to 2003 but is in XP. Is there a way to force the driver from the XP cd into 2003? 3/19/2005 9:12 PM | Nick Hastings

# re: Windows Server 2003 as a Workstation OS

Any ideas on how to get Plus! Media Edition installed? I am running Windows Server 2003 as a Workstation and wanted to take advantage of the analog recorder to convert cassettes to digital media. I tried using the Application Compatibility toolkit on msiexec.exe but still couldn't get it to install. Thanks! 3/21/2005 1:47 AM | Mark Michaelis

# re: Windows Server 2003 as a Workstation OS

Brandon

you mentioned that there are override commands for MSI files to get over the OS check.

Can you let mer know what they are

Thanks

Paul. 3/23/2005 6:09 PM | Paul D

# re: Windows Server 2003 as a Workstation OS

I have w2k server and a brand new Canon 9950F Scanner. The scanner has USB2 and Firewire connections. Drivers work fine on my XP machine but fail to install and work on my W2K server. Same driver model??? 4/2/2005 12:31 PM | Robert

# re: Windows Server 2003 as a Workstation OS

Yes the driver model is the same. If it's using USB and/or FireWire it should have no problems.

Are you installing the driver using a Setup.exe program? Or are you installing it from Device Manager or the Add New Hardware Wizard? 4/2/2005 4:22 PM | Brandon Paddock

# re: Windows Server 2003 as a Workstation OS

I'm also interested in bypassing the OS check to run a workstation app on a win 2003 server. Do you have more details? Thanks 4/7/2005 8:15 AM | Tray

# re: Windows Server 2003 as a Workstation OS

Yes, I've installed Windows Server 2003 SP1 on my Acer Ferrari 3000 and Everything works ABSOLUTELY FINE! Even better than XP SP2 since I could use the Hotkeys again :) 4/14/2005 4:38 AM | Champagne Supernova

# re: Windows Server 2003 as a Workstation OS

overiding 2003 to install comes down to 2 ways editing the installer wit added commands or hex editing the instaler for certain programs

I've been using 2003 server for moere than a year now and i must say it' rock solid

For most applications adding " /a " after thr installer (shortcut ) wil do just fine

when that doesn't work you can also try this >>

------- copy here ----

Option Explicit

Const msiOpenDatabaseModeReadOnly = 0
Const msiOpenDatabaseModeTransact = 1

Dim argNum, argCount:argCount = Wscript.Arguments.Count
If (argCount < 1) Then
Wscript.Echo "Please supply the name of the msi file to be modified."
Wscript.Quit 1
End If

' Scan arguments for valid SQL keyword and to determine if any update operations
Dim openMode : openMode = msiOpenDatabaseModeReadOnly
openMode = msiOpenDatabaseModeTransact

' Connect to Windows installer object
Dim installer : Set installer = Nothing
Set installer = Wscript.CreateObject("WindowsInstaller.Installer") : CheckError

' Open database
Dim databasePath:databasePath = Wscript.Arguments(0)
Dim database : Set database = installer.OpenDatabase(databasePath, openMode) : CheckError

' Process SQL statements and delete the crap out of this installer!
Dim query, view, record, message, rowData, columnCount, delim, column
Set view = database.OpenView("Delete from LaunchCondition") : CheckError
view.Execute
wscript.echo "Launch Conditions Removed"
Set view = database.OpenView("Delete from InstallExecuteSequence where Action='OnCheckSilentInstall'")
view.Execute
wscript.echo "OnCheckSilentInstall step removed"
Set view = database.OpenView("Delete from Property where Property = 'ISSETUPDRIVEN'")
view.Execute
wscript.echo "Property ISSETUPDRIVEN removed"
Set view = database.OpenView("INSERT INTO Property (Property,Value) VALUES ('ISSETUPDRIVEN',1)")
view.Execute
wscript.echo "Property ISSETUPDRIVEN added"
database.Commit
Wscript.Quit 0

Sub CheckError
Dim message, errRec
If Err = 0 Then Exit Sub
message = Err.Source & " " & Hex(Err) & ": " & Err.Description
If Not installer Is Nothing Then
Set errRec = installer.LastErrorRecord
If Not errRec Is Nothing Then message = message & vbLf & errRec.FormatText
End If
Fail message
End Sub

Sub Fail(message)
Wscript.Echo message
Wscript.Quit 2
End Sub
----- end copy ---

save this in a file with extension *.vbs

now copy the installer *.exe or *.msi to your hard disk with the rest of the installer and drag it over the visual basic script this will remove all os checks in the installer

kinda neat huh :)

along the way it wil tell you exactly what it's doing

when finished run the application works for games to

like Vampire masquarade and Doom 3 Ressurection of Evil

Well enjoy one of m$oft best OS
by the way i got my version from the MSN beta cd so i guess it's legal

did some minor ***ching

Laters compadres 4/14/2005 1:27 PM | abraxu

# re: Windows Server 2003 as a Workstation OS

anyone have any idea why server 03 would not recognize my audio card ...on board nvidia audio. 4/21/2005 10:51 AM | Bobby

# re: Windows Server 2003 as a Workstation OS

abraxu, you are a god among geeks - thank you! ;-) 4/26/2005 5:18 PM | Trig

# re: Windows Server 2003 as a Workstation OS

I'm thinking of making the leap you propose. If I connect to my Windows Server 2003 "workstation" from another PC over the Remote Desktop Client (RDP) will sound pass to the other (remote) PC? 4/28/2005 8:43 PM | Tbo

# re: Windows Server 2003 as a Workstation OS

I have an HP nw800 mobile workstation that I run server 2003 on. As a developer this is an ideal platform. I recently had a hard drive crash and am rebuilding. When I did my initial setup months ago I ran into an issue with the video drivers (it has a ATI MOBILITY FIRE GL T2 card...cool card for a laptop with upto 1600x1200 resolution). I found an article online that described how to get the XP drivers working on 2003...it was a matter of enabling directX (turned off by default) and something else that I cant recall. Any ideas? 5/5/2005 11:13 AM | Scott

#  Windows Server 2003 as a Workstation OS-Dell NIC

Need help installing Dell Precision WS 470 NIC-
All other XP drivers from the Dell resource CD work fine accept for the Intel NIC. It says it installs but does not work in Device Manager under NICs-Thanks
5/17/2005 5:14 PM | The Bird IT

# re: Windows Server 2003 as a Workstation OS

I use Server 2003 as a desktop, and until sp1, had no problems at all. I liked everything sp1 did, but it somehow changed something that will not allow me to use my hotmail account. I have two Server 2003 boxes, and the problem exists on both.

I thought it was a passport issue, but I can use my passport to log into MSDN just fine. Also, I can switch to an XP Pro sp2 machine and hotmail works just fine.

Anyone else experiencing this?
Thanks,
Lc 5/20/2005 6:06 PM | Larry

# re: Windows Server 2003 as a Workstation OS

An important reason I did not read yet...
Windows Server editions support more than 2 processors. So if you want to run an OS on a quad processor computer, you can choose Linux or go with the flow... 5/31/2005 1:19 PM | T. vd Meer

# re: Windows Server 2003 as a Workstation OS

I'm looking to run Server 2003 on my Dell Inspiron 8600.

My essential programs are:

Visual Studio
Photoshop
Money 2005
Palm HotSync

Has anyone experience any proglems with any of these apps under 2003 Server? Specially Money 2005?

Thank you,
Anthony
6/9/2005 12:58 AM | Anthony

# re: Windows Server 2003 as a Workstation OS

I used Windows 2003 as desktop since the release and I agree is an excelent desktop OS, i work in development using .Net and I can't ask for more flexibility and reliability 6/22/2005 3:34 AM | Carlos

# re: Windows Server 2003 as a Workstation OS

Which PCI audio card do you recomend using to play sound on Win 2003 Server? I bought the Audigy 2 by Creative and it blue screened on me. Can I play DVDs with sound on Server 2003?

Please help!

Thanks 8/9/2005 8:52 AM | Adam

# re: Windows Server 2003 as a Workstation OS

abraxu, ur script learned me many things about MSIs. But my problem is that I can't run a particular MSI by itself, it says it should be run by setup.exe.
However, I used Orca and found out there's an entry in the MSI which if I could remove, every thing would go right. But removing that entry corrupted the MSI. could u (or anyone else) help me? 8/13/2005 7:04 PM | Sadeq

# re: Windows Server 2003 as a Workstation OS

Hi. It's quite a nice os but:

I own an ATI 9100 based chipset graphics card. Under WinXP Pro my drivers works just fine, actually I got amazed by it's power. Under 2k3 is just as having a display adapter with no directdraw or direct3d or opengl (thats what the dxdiag tells me) functionality. I don't have an answer to my problem.

On the other hand: no crashes until this very moment, no other problems. It's nice OS I believe.

Hi to u all. 8/27/2005 9:52 AM | Nick

# re: Windows Server 2003 as a Workstation OS

You need to go into Display Properties -> Settings -> Advanced -> Troubleshoot

Then move the slider all the way to the right "full accleration"

By default, Windows Server turns off all hardware acceleration. 8/27/2005 3:14 PM | Brandon Paddock

# re: Windows Server 2003 as a Workstation OS

How bout a list of Win2003 Server issues or potential issues when using as a home pc OS?

Looks like it isn't as smooth as some make it out to be..... 8/27/2005 9:10 PM | bourbon

# re: Windows Server 2003 as a Workstation OS

I still can't install kerio personal firewall using the compability technique. Anyone has other ideas? 9/17/2005 9:28 PM | Frans

# re: Windows Server 2003 as a Workstation OS

abraxu,

I'm loading dell laptop drivers on 2003 that have an OS check in place.

When I drop the setup.exe on your script I get the following error:

Script: C:\dell\drivers\R96945\Os Check.vbs
Line: 22
Char: 16
Error: OpenDatabase,DatabasePath,OpenMode
Code: 80004005
Source: Msi API Error

Any ideas? 9/28/2005 7:40 PM | Dingle

# re: Windows Server 2003 as a Workstation OS

@Adam

The Creative Audigy actually works fine with 2003 - however, I had the same "blue-screen" problem.
This blue-screen ist caused by a registration program from creative (Happens on the first reboot after driver installation).
Here´s the workaround:
-Boot 2003 in safe mode
-Delete the folder C:\program files\creative\registration (or similar)
-Restart and enjoy 9/30/2005 1:16 PM | Xenor

# re: Windows Server 2003 as a Workstation OS


I'm a Visual Studio / SharePoint developer. My notebook computer recently died before a presentation, so I was forced to walk into Circuit City and buy a new one, that I expected to be junk. But I got an Acer w/ 1GB of Ram, and an AMD Turion 64 bit chip for $1000 that's been surprisingly nice, so I'll keep it.

The first thing I did was replace XP home with Server 2003, but I couldn't get any sound devices to work. After reading the above posts, I think I probably can get that to work.

But the sound problem, and the expense of server anti-virus tools made me consider installing a fresh copy of XP Pro, then installing Server 2003 on the same machine with Microsoft Virtual PC 2004.
I thought that might work out well because it would let me use all of the extra programs that came from Acer (like DVD player, anti-virus, etc), and still do SharePoint development.
I also thought it might be easier to manage, because I could put all of my user apps like Office on the XP operating system, and still have the ability to reinstall a clean Server 2003 if I have to. In my experience, SharePoint and .net development can hose up a machine, so it will be nice to be able to reinstall the server operating system without having to reinstall all of my applications. There are several articles and blogs on the web that recommend this.

My question is - Do you guys agree that there are benefits for a developer to build a machine like this? Do you know of any good reason not to do this?

Thanks 10/6/2005 11:05 AM | Louis315

# re: Windows Server 2003 as a Workstation OS

Hey Louis.

I've never found VirtualPC to be performant enough for development work, but that's just me.

Server 2003 should be able to work with your sound card, if it worked under XP. You might have to start the "Windows Audio" service if it isn't already.

As for Anti-Virus - I'm not aware of any XP anti-virus software that doesn't work on 2003. I regularly use AVG Free Edition on at home and eTrust at work, and both work great on 2003 systems. 10/6/2005 11:20 AM | Brandon Paddock

# re: Windows Server 2003 as a Workstation OS

Brandon, I read earlier in this post that you were able to get the Cisco VPN Client to work with the 2K3 OS.

I installed the 2K3 last week after upgrading my hard drive. EVERYTHING seems to have configured just fine - EXCEPT - the VPN Client.

I've spoken with our server group and Cisco and the client specifically will not work for the 03 OS. According to Cisco they do not support server OS's with their clients.

The client install fails during the Virtual Adapter creation part. I've ready dozens of posts and fixes regarding this - but nothing specifically works with 03.

I'm very curious how you got it to work? My setup is a clean/virgin install - nothing fancy. I disabled Internet Security and the FW.

Thanks 10/15/2005 3:39 AM | Michael Hamilton

# re: Windows Server 2003 as a Workstation OS

i have a gateway laptop and the log-on system wont let me log-on
10/18/2005 8:12 AM | kayla

# re: Windows Server 2003 as a Workstation OS

Louis315, After 20+ years with C/C++ on Unix I find myself doing the same work you do, visual studio, sharepoint-x, SQL, etc. and I had the same thought you had about using Virtual PC and for the same reason. A good friend and UberAdmin says he has put quite a bit of time into trying to get it stable and never really did (and he's got real servers with lots of memory to play around with....)

I have used VMWare Workstation in the past and found it rock solid while doing lots of testing and refactoring. I can't say enough good things about that product once you get your head around it. If you have to test/demo an n-tier architecture, you can build the while thing on a modern laptop! As a developer, you'll find lots of cool things about it that go beyond just protecting your build.

Downside on all VM's is that they need memory too. We found that a really happy VMWare needed 512mb of it's own, but on a laptop I was running it about 256 just fine.

Good luck. 10/18/2005 1:16 PM | OldDev

# re: Windows Server 2003 as a Workstation OS

i just installed w 2k3 server and i must admit it works really well as workstation, i don't use server stuffs but i'm working in computer graphics and it speed the stuff...

i used to work on 2000 and went to xp some times ago but it didn't works well with me...

anyway it's sad about the antivirus and firewall we can't install, i'm with sygate personal firewall for the moment...

ay ideas about compatibility issue or other good softwares ?

Kaspersky zone alarm and mc afee doesn't work :(


10/24/2005 5:23 PM | sebastien

# re: Windows Server 2003 as a Workstation OS

I also use W2K3 as my desktop, but can't make Matrox Xtools install.It uses older setup.inx system, not msi. It issues a dialogue stating "needs W2K or XP"

Any ideas ? 10/26/2005 2:43 PM | Matrox RTX100

# re: Windows Server 2003 as a Workstation OS

Hey Guys I found a great thing today !

A lot of ppl are having trouble install directx with XP, Server 2003, 2000...

After 10 days of searching a solution i tried to change the compatibility parameter in the property file..and it worked...

So i'm on server 2003 and i made the change to NT compatibility...

Try it for the one having problem and talk about it in forums 10/27/2005 5:08 PM | Sebastien

# re: Windows Server 2003 as a Workstation OS

Win2003 is the most stable of all Windows series. I use it (Win2003 Enterprise SP1) on every machine I have from Celeron366 / 128Mb RAM to Athlon XP 2.2 / 1Gb RAM.

Yes, you have to tweak something like video acceleration and services, but after that everything runs fine.

If you really need some programs that don't want to run on server - switch Win2003 to workstation mode (it will tell something like "Windows XP version 2003") and they won't compain. 11/4/2005 6:12 PM | SEt

# re: Windows Server 2003 as a Workstation OS

Hmmmm. I run Win2k3 as a workstation mostly because it is the best hardware I have and use it for everything incuding games and Domain controller.

Why do I need a domain controller? I don't really. But I am a developer and have a nice little lan at home and wanted to have a server to client setup instead of peer to peer. Mostly a learning experience but some real advantages also.

Now I have run into issues with the Nvidia display driver. There is none for Windows Win2k3 !! (At least not for 32 bit). The XP version works mostly. But Windows Media Player will consistantly crash unless with it instaled. Nvidia says to use the microsft video driver and set the accelation to high. This worked with my geForce3 but not my new 6600. Knights of the Old Republic and I'm sure many other games won't run on the microsoft driver.

Nvidia recommends a dual boot with and run Windows XP for media. Could do that but prefer to have the server up. I've thought about running XP in a Virtual PC but am concerned with performance.

Ideally I find a suitable display driver for Win2k3. Thoughts? 11/18/2005 7:55 PM | Doc Hammoc

# re: Windows Server 2003 as a Workstation OS

Hi Michael!

Search for msi install version "vpnclient-win-msi-4.7.00.0533-k9.exe" of cisco vpn client.
also look for a "vpnclient-windows-4.7.00.0533-readme.txt".

Seems that will work for you... ;)

Has anyone tried it with xp prof. 64 bit? 11/27/2005 11:20 AM | Ano Nym

# re: Windows Server 2003 as a Workstation OS

Does anyone know if Windows Server 2003 can run mstsc, or something equivalent, to act as a terminal services client to another 2000 or 2003 server? 12/17/2005 7:03 PM | Kevin

# re: Windows Server 2003 as a Workstation OS

Is it safe to presume 2003 is stable enough for sound design and studio mixing? I've got a clean install, which has picked up my LIVE card. Anyone use studio software and have issues?

12/19/2005 4:05 AM | Lithium

# re: Windows Server 2003 as a Workstation OS

compared to everyone else my problem might be a little silly, but here it is... i'm running server 2003 i have no problems, everything works fine and i have it tuned to workstation type performance,.. the only thing that does not work is my Canon digital camera... the software installs fine... but nothing when i plug in the camera,... besides, normally it should just work as a USB drive without having to install any of the software. I know my way around server 2003 pretty well, so the problem is not something like assigning a drive letter in disk manager or something like that.... on XP Pro all i do is plug it in and the new drive appears perfectly as a Canon camera... any ideas? 12/19/2005 9:57 PM | Wa'el

# re: Windows Server 2003 as a Workstation OS

Well, I have been running Server 2003 as a workstation since Whistler Beta 1, and it never gave any trouble (except, of course, trying to run UMAX scanners) until it took a dislike to my 60G drive. It would hang up loading crcdisk.sys (which doesn't seem to appear in XP). I ran it for about a year on a speed-doubled Pentium I chip with 128MB RAM and 1MB shared video (any more shared video than that and the installer kept saying I needed more RAM). It was running ISA Server for my firewall, a domain controller, DNS, and DHCP server. ISA configuration was a little slow, but otherwise it ran great. It also has been running on a Pentium II 450 (for a long time it was 333) with 192MB as a web server and MP3 streaming server for over 2 years. I have no idea what drug that HP guy was on saying you couldn't use 2003 as a workstation. I'm sure glad it wasn't available in the 60's or I would be a basket case now. 1/7/2006 4:00 PM | Larry

# re: Windows Server 2003 as a Workstation OS

I was sure glad to find this page! I won an Opteron 246 cpu at a MS/AMD show and was debating what to do with it. I've now concluded I'll buy an ASUS K8N-DL mobo and build a server/ws based on what I've learned today. That way I can dispose of my current hodge-podge server and reduce the bedroom PC count by one. The wife will be pleased. That's what matters most, right?

Nice work, Brandon and company! 1/22/2006 12:14 PM | Texrat

# re: Windows Server 2003 as a Workstation OS

I have WS2K3 installed as a desktop OS and so far I love it.....
except when I try to plug in my external USB hard drive I experience a crash and a physcial dump of the memory.
Would the enlightened souls here have any ideas why this happens?
All ideas greatly appreciated !! 1/31/2006 9:33 AM | Localduke

# re: Windows Server 2003 as a Workstation OS

Hi. I have only recently installed windows server 2003 standard edition, legally, as a practice for me to familiarize with using the os as i will help my dad do server maintainence, etc. Regarding how xp drivers are not compatible with Server 2k3 edition. I had the exact same problem with my labtop, but i managed to get around that. All you gotta do is right click and click explore on the cd drive. Inside, find the folder for any individual driver you want to install, and it should have it's own installation. It worked perfectly for me. You can also go to the device manager panel and right click the drivers with the unknown sign next to them and click update/install with the cd inside your computer. It will auto detect the installation and install it for you, although i dont recommend it as it didn't work out very well. 2/2/2006 8:13 PM | Andy

# re: Windows Server 2003 as a Workstation OS

It has been about 2 years since this article was posted.

Anyway, Im not sure if ill ever get a reply, yet it seems like people still do comment here.

Moving on, today I have purchased a ATI Radeon x850 Pro. The drivers simply do not work for 2003. THey install, but they do not work. OpenGL and Direct3D and DirectDraw dont function. I can tell by going to Start->Run->dxdiag DirectX shows no signs of these components functioning. And everytime I boot windows, right on the desktop, i get prompted that new hardward has been installed and to install the drivers for the card.... it gets really annoying now knowing that I HAVE installed drivers but its not accepting it.

I do not know what to do, I spent a lot of money on this card and I do NOT want to switch back to my Nvidia fx5200.....

Any help is appreciated 2/5/2006 7:11 PM | Mike

# re: Windows Server 2003 as a Workstation OS

Extract the XP driver to a folder with WinRAR, search for the XP reg key and run it, then run setup.exe in compatibility mode for XP. Mine went in fine.
2/6/2006 8:28 PM | ATI

# re: Windows Server 2003 as a Workstation OS

When I installed the 9700 Pro, I overclocked it and it went well. This is what worked for me.

he person who asked mentioned that they were locked up and could not reboot. F8 and Safe Mode will allow for a successful boot and then ADD/REMOVE Programs to uninstall the failed Catalyst driver. Then follow the steps below.

Radeon 9700 Pro in Server 2003 Enterprise Edition

--------------------------------------------------------------------------------

OS: Server 2003 Enterprise Edition

HARDWARE: ATI Radeon 9700 Professional

FILE: wxpw2kcatalyst41.exe

DRIVER: wxp-w2k-catalyst-7-97-031212a-013118c

ADD-ON: Rage3D - Tweak

1. Installation:

Completely remove all other drivers that have been attempted.

Go into SAFE MODE by pressing F8 on reboot and remove the prior driver installation as Server 2003 will not boot after all other Catalyst installations

Use ADD/REMOVE Programs option in the Control Panel and reboot

When the standard VGA driver loads, double-click on "wxpw2kcatalyst41.exe" and it will unpack to this directory: C:\ATI\SUPPORT\wxp-w2k-catalyst-7-97-031212a-013118c

When the prompt arises to INSTALL the drivers, cancel the process immediately so that the drivers can be altered in the Server 2003 environment

Go to this directory: C:\ATI\SUPPORT\wxp-w2k-catalyst-7-97-031212a-013118c\CPanel

Add these files to the registry: 13118_XP.REG and CP_XP.REG

Do this by double-clicking them with the left mouse button and saying YES to add them to the registry; this prepares the OS for the installation of the driver and Control Panel for the 9700 Pro.

Go to this directory: C:\ATI\SUPPORT\wxp-w2k-catalyst-7-97-031212a-013118c

Start here and for every .exe file in every folder therein, right-click on the .exe and choose PROPERTIES at the bottom of the list.

When the window opens that is tabbed at the top, choose COMPATIBILITY and check the box at the top.

Choose Windows XP from the OS drop-down menu and then click the APPLY button at the bottom, and OK.

When you have done this to all .exe files in the "C:\ATI\SUPPORT\wxp-w2k-catalyst-7-97-031212a-013118c" directory: Setup.exe, issetup.exe, AtiCimUn.exe, CheckVer.exe

Move on to "C:\ATI\SUPPORT\wxp-w2k-catalyst-7-97-031212a-013118c\Driver" and "setup.exe" for XP compatibility mode

Then "C:\ATI\SUPPORT\wxp-w2k-catalyst-7-97-031212a-013118c\CPanel" and "setup.exe" for XP compatibility mode

Finally "C:\ATI\SUPPORT\wxp-w2k-catalyst-7-97-031212a-013118c\WDM" and "setup.exe"

Now that all execution files are set for XP Compat Mode, go back to the main directory and run the setup, it will be best as express install.

The XP driver will install and you should reboot and the ATI Control Panel will fail to load because the driver is not yet configured

2. Configuration:

Right-click on the desktop and choose properties or go to the control panel and choose "Display"

Click the "settings" tab and set both monitors to the same resolution if using a dual display

The second monitor will not load unless you choose "extend my Windows desktop onto this monitor" and then Apply

The second monitor will flicker and come on

Remember, both the same color qualith and resolution and then click the "advanced" button in the bottom right for each monitor.

Select the 'troubleshoot" tab in the new window and slide the acceleration to "full" on both moitors, hit "apply" and OK.

Now the driver will be ready but the Direct X overlay will need to be configured.

Go to the Start button/RUN command and type: dxdiag (hit enter)

Say Yes to allow Direct X to check all of the drivers and click the Display tab and ENABLE the Direct Draw Acceleration, Direct 3d Acceleration, and AGP Texture Acceleration. (Repeat for Monitor 2)

Test all of them, exit the Direct X config and reboot the machine. The driver will load

3. Advanced Configuration:

Go to Start/Run and type "services.msc" (Services of Mocrosoft Corporation)

The Imapi CD-Burning can be enabled, Microsoft Image Acquisition (Scanner Input), Windows Audio (Sound) to name three

Right-click on the My Computer icon and choose PROPERTIES from the drop-down menu.

Click the ADVANCED tab at the far right and then the SETTINGS button under the PERFORMANCE heading.

In the new window, click the ADVANCED tab and select PROGRAMS for both as this will divert more system resources to games rather than network management.(This will require a reboot)

If you have more than one HD and Windows XP or another OS is not on it, then the paging file can be moved to smooth gaming.

Do this by returning to the Performance Options Tab as you have just done above and beneath the Processor Scheduling and Memory Options, you will see Virtual Memory.

Click the CHANGE button beneath the Virtual Memory header and when the new window opens, highlight the drive that you want to move the paging file to and copy the values. Adding a paging file does not require a reboot but deleting an old one does, so add one to your extra drive first then return to the C.

When it is highlighted, choose "No Paging File" and click the SET button and OK.

This allows the C drive to read info while the D is being written(paged) to which averages a system increase in performance of around 33%.

*Now reboot and install Rage 3D Tweak and open the ATI Control Panel by choosing Display in the Control Panel, the Settings Tab, and Advanced button. A fully functional and tweakable panel will open.

**I have found that the newer drivers tend to lock up the machine but this one has worked well for me. If you have success with any other ATI Drivers, please post below mine.

2/6/2006 8:38 PM | ATI (older post of mine)

# re: Windows Server 2003 as a Workstation OS

The link that is attached is in response to the article above that I wrote, cut, and pasted here for you. They did post new ATI Drivers and had newer cards to work with.

http://www.ntcompatible.com/ATI_Catalyst_drivers_are_the_new_ones_any_good_t26389.html

2/6/2006 9:14 PM | ATI (Nt Compatible threat on new

# re: Windows Server 2003 as a Workstation OS

After all the comment of people i have decided to share some insights in the hardware vs. software issue

stop wining about incompatibility

some things are destined to change

hardeware is ever evolving into new stuff

learn to deal with it
be creative if something doesn't work try to find an alternative

most this that don't work are dependend on some key elements in the software that provided by microsoft (flaws icompatibility and other programming //developmet cockups)

for example yhere are other software that do antivirii

Bitdefender one of my favorites of all time

or miranda im
smaller tighter code room for development

be creative again if one thing doesn't work switch and mix till it does dont get hung up at little quirks and the whims of M$ dependency

to show you whati mean

Albatron PE865 Pro II
my setup is a p4 extreme 3.2 GHz watercooled ( i hate noise)
ATI XT1800XT
2 xs ata 200GB 4x1 60 gb

no chain and ball here

at the end of the day windows is just an operating system no more no less

Knowing how to find anything you want on the web, once you will have learned it, will give you power. As always, that power can be used for 'evil' deeds and/or for 'good' deeds (let's leave aside, for now, the rather complex question of what would be 'evil' and what 'good', just use your own parameters). A similar problem arised in my previous 'page of reverse engineering' (1995-2000), a site that dealt specifically with software reverse engineering techniques and tools. The idea was to convert young crackers (i.e. people interested almost only in breaking software protections) into software reverse engineers, something that the [world needs badly], especially given the many [malwares] practices around.The experiment worked only in part, hence the decision a couple of years ago to freeze that site
Spreading knowledge on the web is indeed a difficult act of balance.There is for instance a special section, ported from the previous site, called 'ideale.htm', that was indeed intended as a sort of small 'introduction' to various "lores of destruction" (yet purposedly not server-attack oriented). There are indeed enough informations (and 'angles') there to allow anyone with average searching skills to find out, on other parts of the web, everything he may need to wreak havoc on a server and then some. Not that anyone would really need help for that: a simple search like [+directory +indexing +bugtraq] will "turn some mighty big stones", as a contributor pointed out some time ago.

that a good seeker can be MUCH MORE DANGEROUS than a good cracker or a good hacker or a good viri writer or a good reverser, because HE CAN BE ALL OF THEM AT ONCE, lacking their in-depth understanding of their relative specific field, but easily compensating this with his evaluation and searching skills.That's one of the reasons of our insisting (through the [reality cracking] section and various ramblings) on the ETHICAL side of the coin: may the "dangerous" seekers we contribute to create endanger the enemies of poetry, knowledge, diversity and tolerance and annoy instead the apostles of compelled behaviour, consumistic slavery, monolithical thinking and religious fanaticism (be it under the forms of catholic, jewish or islamic intolerance).This said, I do believe also that seekers are and will be open-minded per definition, and thus pretty difficult to force into any pre-definite, pre-digested or 'obligatorial' way of thought. Therefore ethic should kiss their shoulders 'semi-authomatically' when they seek.Seekers will grow ethically for the simple fact they seek, this evolution into an ethical seeker being the "fourth optimistical law of seeking" :-) In fact, judging from the firewalls' loggings, most attacks seem to come from idiots that DO NOT KNOW how to search... hence they are using common exploits and can easily be stopped (and if necessary directly and immediately punished :-)
Anyway, first of all, read on and learn how to seek!

+Orc 2/7/2006 2:40 PM | abraxu

# re: Windows Server 2003 as a Workstation OS

I fixed my video card, i installed the new Omega drivers and all is working fine. Its purring like a kitten. I didnt have to change any incompatibility modes for ANY files whatsoever. The only thing im having trouble with now and possibly you guys could help me with is that everytime i minimize a game using OpenGL or D3D, my screensaver automatically comes on... i have no idea what would cause this.

Another issue im having is that everytime i restart my PC, i get the "New Hardware Found - Video Card device".

Even tho i have drivers installed, etc, etc, i still get this stupid prompt to install drivers for it. 2/7/2006 4:49 PM | Mike

# re: Windows Server 2003 as a Workstation OS

Have been running Server 2003 Enterprise as a workstation about a year now since the SP1 release and I've learnt a couple things that might help some people on here:

1) I tried installing Server 2003 before SP 1 released and I gave up, it crashed badly. However with SP1 it's very stable so ensure you have SP 1 on there vefore you do anything else.

2) This is a Server old hardware will most likely not be detected, just like some win9x hardware failed on XP similarly some hardware even XP compatible will fail on Server 2003. Be creative when you try to install stuff like Printers, some come bundled with XP software that can crash on Server 2003 you need just the drivers not the bundled stuff to get the printer to work.

3) Enable audio and video acceleration before installing drivers otherwise your drivers will fail. Audio means the audio service and video means the slider in the Advanced video control panel.

4) Ensure you know what 3rd party software you're dumping on the Server would be wise to test it. Not all XP drivers work, I had a nasty crash with XP LAN drivers recently it turned out that the drivers were buggy even under XP. Ensure that your Chipset Drivers are Server 2003 compatible both Intel and AMD have Server 2003 WHQL drivers so it should not be an issue even on a Notebook.

Just follow the basics and you'll see Server 2003 is better than XP as a workstation, it has none of the GUI lags like XP. 2/11/2006 4:52 PM | hylian lynk

# re: Windows Server 2003 as a Workstation OS

Does anyone know how to get a Palm Life Drive (Palm OS Version Garnet v 5.4.80) to hotsync Local USB with Server 2003 Enterprise R2 - set up as a workstation. The device -Life Drive - seemed to appear and dissapear in Device Manager at first. Reinstalled the Palm driver in Device Manager, and pulled the PCI USB 2 card out and back into the computer over several boots. The TYAN K8W S2885 motherboard with the latest BIOS has only USB 1 native connections. There is no firewall or anti virus yet while initially setting up the basic hardware. The Life Drive appears in Device Manager now continually and with what seems to be compatable status - enabled drivers and device - but still no HotSync response when activated from the Palm Hot Sync. I had used the Palm LD on an XP Pro previously - so I know there is no problem with the Life Drive. Hope someone has experience with this and a solution. - Thanks, - Brad 2/25/2006 8:25 PM | Brad P

# re: Windows Server 2003 as a Workstation OS

i use 2k3 server enterprise on a home network linking 2 pc's together in a p2p configuration. i dont do development or anything similar. there is always one pc on at all times. the spec of the pc is as below.
abit kg7r mobo
xp2000 cpu
768mb ram
2 * 80gb hdd's
1 * 250gb hdd
2 * 120gb hdd's (set as raid 0)
dvd writer
soundblaster 5:1 live
3com nic card
2 port usb 1 card
ntl cable modem
samsung ml1610 printer
hp 5550 printer
xerox 2400 scanner
aiptek webcam.
i had no trouble installing any drivers at all. in fact they went in better than on xp pro. my fuji finepix s5500 digicam and technika mp3 player are picked up with no problems. overall i find 2k3 a lot better to use the xp and i find it more stable and faster. i have had no trouble with software except for the following. symantec antivirus and firewall (unless you use the corporate version) and creative recorder. the only mod i have done is turn off the enhanched security for IE as it was doing my head in all the time and my wife did not have a clue what to do (she only wants a pc for msn messenger which also works great) i have even had old software running ok such as carlton card crafts from 1998 (supports win 95/98 and nt) 2/27/2006 4:47 PM | kevin cozens

#