Ambrosian Scripture

Real-world answers to real-world problems.

Foray into Windows .NET Server 2003

Earlier this week I decided to take the plunge with Windows .NET Server 2003 RC2.  I loaded it onto my Compaq Presario notebook.  For the most part, all went well except for three things: it did not recognize my sound card, so I had to get the W2K drivers from Compaq for it, Diskeeper 7 Workstation won't run on it, and I'm having trouble setting up web projects in VS.NET. 

Other than that, I'm liking the new features of IIS 6 and, though it may be just my imagination, it does seem to run faster than XP Pro on that box.  I'm a bit wary of trying to use the Style XP uxtheme.dll patch to enable non-standard themes as I did with XP Pro.  Currently I'm just running Windows Classic theme, which may account somewhat for the perceived performance increase.  Another really nifty feature is the Manage Server program; it looks to be quite powerful and yet very easy to use and understand.

In any event, this is only the second day since I've installed, so we'll see how it turns out.  Unless you're just goofy like me and have a hankering to try out the latest OS from MS, I'd probably recommend sticking with XP for the time being as a workstation OS (duh!).  But if you do like playing around with server features and the latest tech, you might want to give it a try.

Update 03/13/2003 22:31 CST:  I found a resolution to the VS.NET setup.  You need to add a MIME type to the web for temp files (.tmp).  Apparently, VS.NET tries to write/read a .tmp file and won't let you create or load web projects if it cannot do that.  See Creating ASP.NET VS.NET Projects in Windows Server 2003 RC2 for more info.

Posted: Mar 12 2003, 11:57 AM by Ambrose | with 4 comment(s)
Filed under:

Comments

Robert McLaws said:

Forgive me for being a smart ass, but I believe the reason that Diskeeper Workstation will not run on it is because Windows Server 2003 is not a workstation OS. I'm a beta tester for Windows Server 2003 since RC1, and Diskeeper Server has always worked just fine. There are several tutorials for turning WS2K3 into a workstation OS, and I love developing on it with Everett. The only thing I dislike is the inability to uninstall .NET Framework 1.1.
# March 12, 2003 10:24 AM

Daniel Bright said:

I tracked down a more recent build 3771 and I must say that I am way impressed by this OS. As soon as it hits the MSDN downloads site as RTM it will be going on my main machine.

I also had a noticable performance improvement on 2003 vs XP (and I run windows classic anyway), but I'm thinking that server 2003 might have improved SMP code in it.

XP never really liked my dual Athlons, but no probs here.
# March 12, 2003 10:46 AM

Ambrose said:

I only comment that DK 7 Workstation didn't work because it was a disappointment. Many applications that are meant for workstations work on servers, so it's not a no-brainer that X app won't work on Windows .NET Server 2003. Since I don't feel like paying several hundred dollars to defrag my workstation, I'd think my disappointment is justified.

Now my turn to be a smart ass--maybe you could have posted something useful like links to all these tutorials you speak of??
# March 12, 2003 11:43 AM

Thyogo said:

how to convert 2003 server to workstation http://www.msfn.org/win2k3/

i´ve found this one.. i hope this help
# September 11, 2003 1:13 PM
Leave a Comment

(required) 

(required) 

(optional)

(required)