Active Directory Questions

  • Thread starter Thread starter BG250
  • Start date Start date
B

BG250

I'm replacing our NT4 PDC with Windows 2003 server (standard ed.) on a 65
user network.

Because there are file linkages in databases and such, the server MUST
retain the same name and UNC path as the old server. The new server will be
file, print, DHCP and WINS. I'm debating whether AD is even necessary.

Other than DHCP providing IPs to the ISPs DNS, the server will not have any
Internet users. I may install IIS to serve a little help page to the local
lan. I understand that AD uses DNS for name resolution. So my questions are:

Can the UNC be the same (Ex: \\myserver\shareddrive)?
How do I generate a domain name? Our company has a registered domain on the
Internet. Can I make it a sub domain just for consistency with our
registered name?
Do the local computers see the server as the DNS name or its computer name
(as they do now)?
If I don't install AD now, can I do it later with minimal downtime?

Thanks for your help, BG
 
I'm replacing our NT4 PDC with Windows 2003 server (standard ed.) on a 65
user network.
Because there are file linkages in databases and such, the server MUST
retain the same name and UNC path as the old server. The new server will be
file, print, DHCP and WINS. I'm debating whether AD is even necessary.
Click to expand...

AD is an accounts database with various improvements most for
large companies OR in "user/machine central management": Group
Policy (including centralized software installs), better scripting (logoff/
startup/shutdown), better security, and all the "server" features of
Win2000-2003 that are in addition to AD.

Also to consider, NT is becoming obsolete.

You can ONLY do the above and keep you current accounts and
resource ownship if you upgrade the PDC to Win2000 or Win2003.
This is the ONLY way to upgrade the domain and usually the best
choice for such small, single domains.
Other than DHCP providing IPs to the ISPs DNS, the server will not have
Click to expand...
any

You DHCP should never be providing ANYTHING to the ISP,
especially their DNS so I must assume you meant something else
with the above.
Internet users. I may install IIS to serve a little help page to the local
lan. I understand that AD uses DNS for name resolution. So my questions are:

Yes.

Can the UNC be the same (Ex: \\myserver\shareddrive)?
Click to expand...

Yes, especially if you just upgrade the current PDC.
How do I generate a domain name? Our company has a registered domain on the
Internet.
Click to expand...

When you upgrade your WinNT domain you will (permanently) pick
a name -- it is usually SIMILAR to the NetBIOS name you are now
using.

If you wish to change this; do it now under NT.
Can I make it a sub domain just for consistency with our
registered name?
Click to expand...

Good choice (no one can tell you the "perfect" choice) but this is
a good one.
Do the local computers see the server as the DNS name or its computer name
(as they do now)?
Click to expand...

It's best to make these names similar: My old NT "LEARNQUICK"
became "LEARNQUICK.COM" (learnquick.local or .net would work too)
and the machines are known under NetBIOS by the "simple machine name",
e.g., Hamachi, and under DNS by the full DNS name Hamachi.LearnQuick.Com.
If I don't install AD now, can I do it later with minimal downtime?
Click to expand...

? You are going to spend the same effort/time whether you do it now or
later.
What alternative are you implying?
 
Herb Martin said:
AD is an accounts database with various improvements most for
large companies OR in "user/machine central management": Group
Policy (including centralized software installs), better scripting (logoff/
startup/shutdown), better security, and all the "server" features of
Win2000-2003 that are in addition to AD.

Also to consider, NT is becoming obsolete.

You can ONLY do the above and keep you current accounts and
resource ownship if you upgrade the PDC to Win2000 or Win2003.
This is the ONLY way to upgrade the domain and usually the best
choice for such small, single domains.

any

You DHCP should never be providing ANYTHING to the ISP,
especially their DNS so I must assume you meant something else
with the above.
Click to expand...

Yes, I meant *of the ISPs*, not *to the ISPs*
Yes, especially if you just upgrade the current PDC.


When you upgrade your WinNT domain you will (permanently) pick
a name -- it is usually SIMILAR to the NetBIOS name you are now
using.

If you wish to change this; do it now under NT.


Good choice (no one can tell you the "perfect" choice) but this is
a good one.


It's best to make these names similar: My old NT "LEARNQUICK"
became "LEARNQUICK.COM" (learnquick.local or .net would work too)
and the machines are known under NetBIOS by the "simple machine name",
e.g., Hamachi, and under DNS by the full DNS name Hamachi.LearnQuick.Com.


? You are going to spend the same effort/time whether you do it now or
later.
What alternative are you implying?
Click to expand...

I am setting the new server up isolated from the lan. When it is ready, it
gets connected to the lan after the old one is removed. Eventhough the old
machine is a PDC. We never used any of the PDC features, such as having a
BDC. It just shared files and printers as any other machine on the lan
could. In a sense, I'm setting up the new server as if there was no server
on the lan except that I need the computer name the same for the data links
in existing files. The alternate I was implying was not using AD.

Thank you for the great responses, bg
 
You DHCP should never be providing ANYTHING to the ISP,
Yes, I meant *of the ISPs*, not *to the ISPs*
Click to expand...

It's no simple typo because even then it should be the other way
around: "Obtaining IP configuration FROM THE ISP DHCP...."
I am setting the new server up isolated from the lan. When it is ready, it
gets connected to the lan after the old one is removed. Eventhough the old
machine is a PDC. We never used any of the PDC features, such as having a
BDC.
Click to expand...

You mean like USER ACCOUNTS? Or authentication?

You never use these to control and grant access to resources?
It just shared files and printers as any other machine on the lan
could. In a sense, I'm setting up the new server as if there was no server
on the lan except that I need the computer name the same for the data links
in existing files. The alternate I was implying was not using AD.
Click to expand...

Are you or are you not using your domain? If so, you will be better
served in many instances by AD.

The purpose of a domain is to make sharing of resources among users
easy to control and the administration of those users easier.
 
Back
Top