Re: Server & Client Setup
From: Phillip Windell (_at_.)
Date: 04/22/04
- Next message: Phillip Windell: "Re: I can't see other servers and workstations"
- Previous message: Sergio Moreno: "RE: XP machines lose "trust" to Windows Server 2003"
- In reply to: Lisa: "Re: Server & Client Setup"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 22 Apr 2004 10:31:06 -0500
"Lisa" <anonymous@discussions.microsoft.com> wrote in message
news:28de01c42818$7e78f940$a001280a@phx.gbl...
> tool needed for the workstations? I previously worked in
> an office on a Novell server, and I believe we had
> a "client" software. Was that only because we had
> Windows as the operating system on the PCs and Novell as
> our networking system? I just want to understand this
There is no "client" software with a Windows based system. The Windows OS
takes care of everything itself. Except for XP Home and Win9x (and older),
you need to make the machines members of the Domain after the Server has
been made a domain controller.
Win98 does log into the Domain but is not actually a member (don't worry
about what that means). XP Home can only be in a Workgroup so make the
Workgroup Name the same name as the Domain. Walter gave some good advice on
this and I don't want to rehash what he already wrote.
When you give your Domain a name during the "promotion" of the server there
are some things to consider. Active Directory domains are DNS based, yet
they keep backward compatibility to a point with the old Netbois way of
doing things, so it effectively has two versions of the name. For example:
mycompany.loc (DNS version, tyipically shown in lower case letters, two
words, with "dots")
MYCOMPANY (Netbios version, often shown in upper case letters, one
word, no "dots")
"Later in life" when things ask for the domain name, sometimes you use one,
sometimes you use the other, you'll have to deal with that on a case-by-case
basis. Myself, I usually use the shorter Netbios version unless I know the
other is required.
I usually recommend *not* using the same Domain name on the private side of
your network in Active Directory as what your company may be known by
"publicly". For example, publicly you might be known as "mycompany.com", so
in the Active Directory domain I would use something else like
"mycompany.loc" ("loc" for local, ...creative,.. huh?). Some people preach
to make them the same,..I do not. It creates some DNS nightmares,
particularly if proxys and firewalls get involved and is too indepth to get
involved with in this message.
> And secondly, if the boss doesn't want to pop the $200 to
> upgrade the last PC from XP Home to Pro, or maybe wants
> to wait a while for some reason known only to bosses, can
I usually endorse "Public Boss Beatings", but if you can't do that, then
just do the best you can with the situation until you can finally eliminate
the XP Home machines. What Walter suggested should handle that fine.
-- Phillip Windell [MCP, MVP, CCNA] www.wandtv.com
- Next message: Phillip Windell: "Re: I can't see other servers and workstations"
- Previous message: Sergio Moreno: "RE: XP machines lose "trust" to Windows Server 2003"
- In reply to: Lisa: "Re: Server & Client Setup"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
