|
web
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Win2000 server tutorial?I'm going to set up a win2k server soon, and it will be a very lowtech
little network with just 2 or 3 workstations. Is there some online tutorial material I could read up on, just for planning how the workstations/users will log on, workgroup vs domain, that sort of stuff? Is that sort of thing on the CD itself? Thanks With only 3 w/s you'd probably want to use a workgroup. Just understand that
security is NOT centralized in that environment. The user ID and password on the w/s MUST match the one on the server. Also, they need to be in the same workgroup. Anyway, the install is pretty much helpful during the process. Just make sure you have all the device drivers beforehand (network card, video, etc.). The server install (not including all the service packs and other security patches) takes less than 60 minutes (IF you have all the drivers). Regarding the service packs, try to get a newer 2000 CD that includes the latest service pack. That'll reduce the post-install updates a lot. To tell you the truth, it's so easy you may want to try it several times just for the experience. jwkh Show quoteHide quote "bill allemann" wrote: > I'm going to set up a win2k server soon, and it will be a very lowtech > little network with just 2 or 3 workstations. > Is there some online tutorial material I could read up on, just for planning > how the workstations/users will log on, workgroup vs domain, that sort of > stuff? Is that sort of thing on the CD itself? > > Thanks > > > thanks, that doesn't sound too bad.
Bill Show quoteHide quote "jwkh" <j***@discussions.microsoft.com> wrote in message news:E408492E-B2E1-4AE7-BBE7-3703DD295AAC@microsoft.com... > With only 3 w/s you'd probably want to use a workgroup. Just understand > that > security is NOT centralized in that environment. The user ID and password > on > the w/s MUST match the one on the server. Also, they need to be in the > same > workgroup. > > Anyway, the install is pretty much helpful during the process. Just make > sure you have all the device drivers beforehand (network card, video, > etc.). > > The server install (not including all the service packs and other security > patches) takes less than 60 minutes (IF you have all the drivers). > Regarding > the service packs, try to get a newer 2000 CD that includes the latest > service pack. That'll reduce the post-install updates a lot. > > To tell you the truth, it's so easy you may want to try it several times > just for the experience. > > jwkh It really isn't. Let me know how it's going.
jwkh Show quoteHide quote "bill allemann" wrote: > thanks, that doesn't sound too bad. > > Bill > > > "jwkh" <j***@discussions.microsoft.com> wrote in message > news:E408492E-B2E1-4AE7-BBE7-3703DD295AAC@microsoft.com... > > With only 3 w/s you'd probably want to use a workgroup. Just understand > > that > > security is NOT centralized in that environment. The user ID and password > > on > > the w/s MUST match the one on the server. Also, they need to be in the > > same > > workgroup. > > > > Anyway, the install is pretty much helpful during the process. Just make > > sure you have all the device drivers beforehand (network card, video, > > etc.). > > > > The server install (not including all the service packs and other security > > patches) takes less than 60 minutes (IF you have all the drivers). > > Regarding > > the service packs, try to get a newer 2000 CD that includes the latest > > service pack. That'll reduce the post-install updates a lot. > > > > To tell you the truth, it's so easy you may want to try it several times > > just for the experience. > > > > jwkh > > >
Boot problem
win 2000 Can't delete old documents How to change regional settings (date format) from command line ? win2k --- Blue Screen of death Event ID:222 source:SWS Spooled print job size much larger than actual file Blank Blue Desktop Windows installer launching whenever I try to open a file Unplug or Eject Hardware Icon missing |
|||||||||||||||||||||||