General discussion

Locked

Ed Bott's Microsoft Challenge--2/17/00

By ebott ·
I?m looking for your suggestions on the most cost-effective ways to upgrade an entire office to Windows 2000. Microsoft?s price list is terribly confusing, with all its upgrade and licensing options. Assuming you aren?t part of Microsoft?s Select program, what?s the best way to upgrade 10, 20, or more PCs to Windows 2000?

This conversation is currently closed to new comments.

21 total posts (Page 1 of 3)   01 | 02 | 03   Next
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Ed Bott's Microsoft Challenge--2/17/00

If in U.S. I would buy this one:

Version/Product Upgrade:
Microsoft? Windows? 2000 Professional English Version/Product Upgrade North America CD Encryption Coded Software
CD-ROM $219.00

For my servers I would buy the cheapest upgrade to Windows 2000 Server, no need for advanced server here.

Microsoft? Windows? 2000 Server English Version Upgrade North America CD Encryption Coded Software 5 Client CD-ROM $489.00

Only reason for buying Advanced Server is if I want to be able to cluster two new machines together, they should be identical though.

If I have 40+ machines I'd start looking at becoming a Select customer.

/Hasse

PS! Not too hard to sort out the prices.. D.S.

Collapse -

Ed Bott's Microsoft Challenge--2/17/00

by ebott In reply to Ed Bott's Microsoft Chall ...

The question was auto-closed by TechRepublic

Collapse -

Ed Bott's Microsoft Challenge--2/17/00

by dsullivan In reply to Ed Bott's Microsoft Chall ...

First I would go to www.microsoft.com/technet/win2000. There are many documents on deploying Windows 2000. Are you upgrading your servers to 2000 and your workstations to professional? I would recommend planning your Active Direcory First. Then deploy your servers. It sounds like with size of your network all you need is regular nt server and not advanced or the datacenter server. Once you get your servers deployed, you will want o implement the advanced management feature. Then you can start your desktop Upgrades. Planning..Planning...Planning is a must when planning an migration to 2000.

Collapse -

Ed Bott's Microsoft Challenge--2/17/00

by ebott In reply to Ed Bott's Microsoft Chall ...

The question was auto-closed by TechRepublic

Collapse -

Ed Bott's Microsoft Challenge--2/17/00

by schred In reply to Ed Bott's Microsoft Chall ...

If I were updating myslef, I would buy the HOT Kit off the Direct Access site which gives you a NFR Copy of Pro, Server and Advance server, some training and sales materials.

For quantity buying for 10 or more, I would buy a MOLP. The savings aren't great, but you can get a copy that doesn't have the pesky serial/cd-key and you have liscences for each station. Then as you add more, you just buy more liscences.

Collapse -

Ed Bott's Microsoft Challenge--2/17/00

by ebott In reply to Ed Bott's Microsoft Chall ...

The question was auto-closed by TechRepublic

Collapse -

Ed Bott's Microsoft Challenge--2/17/00

by thim In reply to Ed Bott's Microsoft Chall ...

The upgrade version should be based on
the needs of the various departments in the
office with a dedicated server installed with the appropriate Windows 2000 version including licensing for the respective department concerned.

Where there's a need to upgrade to a different option for future expansion, the
respective departmental server can be upgraded accordingly as the needs arise.


Conduct a survey among the users and then
list out the required upgrade version after
checking out at:
www.microsoft.com/technet/win2000

It would not be feasible and cost-effective
to upgrade to a higher version than is necessary using perhaps the criteria of the number of users and the sophistication of user demands.

Collapse -

Ed Bott's Microsoft Challenge--2/17/00

by ebott In reply to Ed Bott's Microsoft Chall ...

The question was auto-closed by TechRepublic

Collapse -

Ed Bott's Microsoft Challenge--2/17/00

by D^Man In reply to Ed Bott's Microsoft Chall ...

It.s Actualy quite Simple,

1) Planning - Plan the whole project from start to finish including a contingency plan for any unexpected ocurrences, no matter how big or small the network (Most projects fail due to bad or no planning)
2) Use Win2K utilities, setup a SOE and use intellimirror services in conjunction with your SOE.
3) Use disk network setup on legacy machines and boot prom on new machines.
4) Run your network very strictly ( Like a tyrant - as far as providing efficient services to clients using policies and profiles.) and you will have a low cost efficient and effective solution.
5) Remember, your user is your client, provide good service, make sure they can do what they need to easily, treat them like gold, BUT DONT LETTHEM DICTATE HOW YOUR NETWORK IS RUN.

Collapse -

Ed Bott's Microsoft Challenge--2/17/00

by ebott In reply to Ed Bott's Microsoft Chall ...

The question was auto-closed by TechRepublic

Back to Windows Forum
21 total posts (Page 1 of 3)   01 | 02 | 03   Next

Operating Systems Forums