Creating a Member server

[Rich Schiavi]

How do I create a member server within an existing Active
Directory? The other question is do the user's login into
the member server or into the Domain controller?

Thanks

 

[Cary Shultz [A.D. MVP]]

Rich,

You create a member server just like you create a WIN2000 Professional or
WIN XP Professional client. You simply install the OS ( in this case,
WIN2000 Server ) and join it to the domain, just like a workstation /
client. You just need to make sure that it has a unique, static IP
Address - since it is a server. Just make sure that the server points to
your internal DNS and you will be good to go. Once WIN2000 Server has been
installed and you have rebooted you will be presented with the "Configure
Your Server" wizard. You can simply ignore this and click on the little
check box so that it does not pop up everytime you reboot.

You users will logon to / authenticate against a Domain Controller. They
simply access resources on the member server ( files and folders if it is a
File Server / Printers if it is a Print Server / Applications if it is an
Application Server, etc. ) once they have been authenticated. Naturally,
they need to have permissions to access these resources.

HTH,

Cary

 

[Herb Martin]

How do I create a member server within an existing Active
Directory?

Unless you upgraded all DCs from NT, you have already
done this.

If you install a Win2000+ Server you have created a plain
server -- usually it's only called a "member server" if it is
joined to a domain (versus a "stand-alone" server) but not
always because there has never been a really popular name
for BOTH "member and stand-alone server."

Just install Win2000 server and join it to a domain in a
similar manner to a workstation.

The other question is do the user's login into
the member server or into the Domain controller?

NORMALLY, users should not login to such servers but
should use them over the network using a domain account.

Users AUTHENTICATE using the AD accounts to access
server resources, but never really "login."

If you need them to actually login then you have to decide the
purpose: Terminal Service users should typically be domain
users. A SQL server admin, may use domain account (I
like this method) or possibly a "server account".

If in doubt, AD account -- and grant or deny custom privileges
on the machine.

 

[Hank Arnold]

We set up all our servers with Terminal Services in Administrator mode. This
allow us to log in using an RDP client to administer it remotely without
having to have TSCALs... You can have, IIRC, 2 logins. The only servers with
TS in Application mode are our two Citrix servers.

 

[Herb Martin]

We set up all our servers with Terminal Services in Administrator mode. This
allow us to log in using an RDP client to administer it remotely without
having to have TSCALs... You can have, IIRC, 2 logins. The only servers with
TS in Application mode are our two Citrix servers.

How is the above related to the OP's question or to the answers
given?