What a Joke!: This is nothing more than screenshots of the software load process. This is not installing a system. The installation of a system involves the careful selection of options and configurations for the correct and careful integration of aproductivity tool within an environment.
If you think that by following this simple little article you will have successfully installed Windows 2000, then you are sadly mistaken. Windows 2000 is the most complex desktop operating system ever designed and built.
Discussion on:
View:
Show:
If you guys know nothing about Win2k, just say so. I'd be better off just winging it. The embarrasing thing is I showed this to my boss before I read it, now he thinks I'm an idiot.
Shouldn't we all be happy that this guide isn't a full and complete discription of how to set up a Windows 2000 domain for each and every company in America ? I mean, if there were a downloadable guide like that, would Network Admin's still be making 75k a year or would it be more like 25k a year ? I for one am worried enough about books like "Mastering Windows 2000 Server". This book is 1800+ pages of detailed info on 2k server. Many people will be able to start from scratch with no experience in the industry and go very far from just reading 1800 pages of high quality info !
Post Windows 2000 Setup Issues: Actually, most people can do the installation shown in this document without any guide at all. After the basic installation of a Windows 2000 server there are many decisions to be made that require a bit of planning. The server configuration tool will launch on the first login to help you through these steps, but they require knowledge of the software being configured.
Hopefully this installation is only being used to get a test server up and running. The actualinstallation for a production environment is much more complex. The issue of domains is only briefly discussed, when this is one of the critical aspects of installing Windows 2000 server in an existing Windows NT domain.
Hopefully this installation is only being used to get a test server up and running. The actualinstallation for a production environment is much more complex. The issue of domains is only briefly discussed, when this is one of the critical aspects of installing Windows 2000 server in an existing Windows NT domain.
Can someone help me out.
I want to build a win2000 server.
then connect 10 machines to it.
then put an image of win 2000 OS on
each machine.
i want to somewhat of a step-by-step process
on how to go about doing this.
The image will be ghosted to the server
using GHOST and then each system will run
the install from the server.
And then be personalized for each user.
What's the best way about doing this?
Thanks,
Trav
I want to build a win2000 server.
then connect 10 machines to it.
then put an image of win 2000 OS on
each machine.
i want to somewhat of a step-by-step process
on how to go about doing this.
The image will be ghosted to the server
using GHOST and then each system will run
the install from the server.
And then be personalized for each user.
What's the best way about doing this?
Thanks,
Trav
Since all of the client machines will be installed with Win2k why don't you use RIS intead. If you really want to use GHOST you should be using the latest version corporate edition which will allow you to take advantage of the NIC's PXE feature. Assuming all you stations have NICs that support this feature. The latest GHOST version can also be used to take advantage of using RIS.
Hope this helps.
Mike
Hope this helps.
Mike
- Keyboard Shortcuts:
- Prev
- Next
- Toggle
