Discussion Locked

XP or w2000 if starting fom scratch

0 helpful
12 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

So, somehow I got lucky today and got a completely unexpected call that we had a fair amount of money that HAS to be gone by the end of the year and that our execs want all new workstations in the main office. They also want them to be up-to-date asmuch as possible with XP, fast processers, lot's of RAM etc. which sounded great with one caveat.... XP. I understand that they want the latest date stamped OS but keep hearing it's still a pain to support. We have only 2 XP machines currently, andthey do fine, but still..... Any love\hate comments between the two from those that use the OS everyday?

~thanks! :)

12 replies

by zlitocook

It is easyer to use less trouble and it is easyer for the user to find things. I am with a contracting group now installing all XP workstations. And was with a group installing 2000 last month. 2000 was easyer to deploy and support. There were less problems importing data from the old computers and it seems to run faster and have less hangups when accessing network shares.

by jaytmoon

In a perfect IT Environment running the same OS on all workstations is a Tech supports dream. If you have any experience with Win XP then you know it is the way to go in a Microsoft Network environment. It has far more PnP compatability and better stability than w98 or 2000. (Yea I know there's a LOT of w2000 Fans out there). I have run all of them and found XP to be more secure and configurable than 2000. I can make any system crash if I try but XP is by far the best that Mr Gates has put out to date. From a support stand point, you will have fewer lockups and (possibly) more productivity of your clients.(After the XP learning curve). The only "Pain" is running Old Apps and older peripherals (scanners, printers etc. If most of your equipment is current, go with XP. BTW, W2000 support WILL end in 2 years, right?

by when in doubt

I use XP Pro everyday, our users use a combination of Win200 and NT. We've found that the extensive list of applications that we run have no problems running in XP. Also don't forget the Application Compatibility feature, we've used on some of theother programs, withou any problems. 50% of our IT staff uses XP on their workstations. Most of the "problems" that occur have to do with permissions on the local box. With some testing before hand you'll find XP much easier to work with and userfriendly than
2000.

by djent

XP isnt ready yet, with plug-n-pray and the EULA its a liability rather then an asset. On W2k use SP2, SP3 is still infested with bugs and carries the same EULA bagage as XP.

by guruofdos

If I was starting from 'scratch' I'd give them the latest Macs!!! Obviously you are talking about 'Dyed in the wool' Wintel users.

If your users require video editing, streaming multimedia and all the places that Bill Gates would like us to go 'tomorrow' then opt for XP running on an Athlon CPU (XP performs real-world tasks 18% better on AMD chips than it does on 'equivalent' P4's and they are a third of the cost!!). If all you want are workhorses for email, word processing and spreadsheetsthen obviously 2000 (optimised for Intel) is the better choice. I personally still feel that neither of these OS's are stable (is anything from Microsoft ever?!!) and no matter how 'fresh out of the wrapper' your 'weapon of choice' expect to be continuously patching, tweaking and installing updates. We are still giving our users Windows98 SE with 156Mb of patches and updates (DirectX 8.1, IE6.0, security updates, etc) installed because a) no one has any use for new features in the newer OS's, b)It's as stable as any MS platform and c) You can pick up a full licence for a fraction of the cost of XP or 2K...and if you are only using Orifice and Winzip and an e-mail client, there ain't much point in shelling out for a top-heavy disk-hungry OSwith 'bells and whistles' you are never going to use!

Incidentally, my immediate boss is still perfectly happy with a DX4-100 running 98SE with Office 2k SBE...he doesn't need any more speed, power or features to write letters and balance the accounts; after all, he's 61 and he can only type so fast!!! There ARE still uses for 456Mb hard disks....his is still only 80% full!!! Now where did my 120Gb spare drive go....my MP3's are getting out of hand!!

Mike :-)

by james r linn

And if you were already on 2000, I wouldn't see much reason to switch.

But starting from scratch is a different issue.

If you are looking to reduce the churn of installing new OS (versus patching existing ones) in the future, then its clear that Microsoft will support XP for about 2 years longer than 2000, so go for XP and run it as long as you can.

I have noticed that XP appears to be faster and is at least as stable as my W2K sp2 was. Having to manually install the JVM was a pain, but you can add it to an image and ghost it.

And if you are worried about the new look and feel you can change the theme to classic and it looks just like W2K.

I would suggest that the age of your machines be looked at as a factor -if they are minimum 400 Mhz, no problem - if you have alot of them earlier than that, my experience with a 300 Mhz machine is that XP was too slow, and 2000 worked better. Mind on my new 1Ghz, XP seems faster.

James

by madroxxx

With Microsofts EULA backward compatibility you could purchase XP and install 2000. Then when you felt XP was ready you would be legally licensed to deploy it on all your machines.

by lordinfidel

Stick with 2K, here is why.

1. It is a proven OS and is still supported. It is fairly stable.

2. .Net is around the corner. Purchase the Upgrade advantage liscensing. Talk to your liscense vendor.

3. XP does have a learning curve to it.I personally tested 2K on my machine for about a year before opening it up to my users.

4. Unless you are a developer (for testing code), there is little that XP is going to offer the corporate end user.

Most of the features in it are geared towards the home user (firewall, remote connection, etc). I would not want my end users messing around with personal fwls or letting them remote into their machine.

5. If you have the cash to burn, go to a strict Native 2K AD. Don't throw XP intothe mix. Especially if you are just getting familiar with AD. Keep everything the same.

Like I said, a year or 2 from now .Net srvr will be released, and that is where the next generation of upgrades will come.

I personally feel that your client OS should be a generation above your servers. XP is like a 1/2 generation. It is like bridging the gap between 2K and .Net. Once .Net srvr is out, we will probably see a new release of XP that will fit in nicely with .Net domains.

by lordinfidel

I personally feel that your client OS should be a generation above your servers. XP is like a 1/2 generation. It is like bridging the gap between 2K and .Net.

This should be

"I personally feel that your client OS should 'NOT' be a generation above your servers..."

by mamont

If you are getting new machines, definetely XP, and definetely on athlon boxes, which are designed to run XP. It has better resource management, and more stable then win2K by a long shot. It will also be a better investment considering that it hasnot been out for a long time. And another point to ponder, Microsoft tends to work on the new stuff first, and the old stuff last, so it would be a safe bet that XP will be easier to secure, patch, and fix then win2K

by thechas

While I have no experiance with W2K, I suggest XP Pro for the following reasons;

It will be supported for at least 1 year longer than W2K will be.

It will become harder and harder to purchase new PCs with W2K installed.

Your support issues will be less involved for a pure XP install than a mixed NT, W2K, XP setup.

DO NOT purchase any system with XP Home on it.

Chas

by madmark

Both Windows2000 and XP Pro are excellent choices, provided your environment supports them. For best results, it would be wise to standardize all PC's on one operating system. This reduces support costs big time, and reduces the amount of trainingrequired.

Things to consider:
What is the predominant OS in use in your current environment? That may be the way to go.
If you are using Active Directory, it may be easier to rollout Win2K.
Watch out for the UPnP in XP. Major security issue.
Keep all of your systems up to date with SP's and patches.
XP has better security features overall, but there is a learning curve as things change.
XP does not run all of the apps that Win2K can run, but that gap is closing.

I use Win2K and XP in my home office LAN. I have fewer problems with XP, but more problems with APPS on XP than on 2K.

My 2?...

This discussion is closed to new replies.