Aces High Bulletin Board

General Forums => The O' Club => Topic started by: rabbidrabbit on March 07, 2007, 05:05:53 PM

Title: building a win2k3 domain..
Post by: rabbidrabbit on March 07, 2007, 05:05:53 PM

Any good pointers on what I should be aware of?  I'm building one from scratch for a small company but its been about 5 years since I built one and that was win2k.  It will be for internal use of about 15 users.  Remote access is operational now via a sonicwall device.  They are now simply sitting on a workgroup.

Title: Re: building a win2k3 domain..
Post by: Vulcan on March 07, 2007, 07:58:53 PM

Quote

Originally posted by rabbidrabbit
Remote access is operational now via a sonicwall device.

Good fella. Hope ya got it all licensed up with the extra services :P

Title: building a win2k3 domain..
Post by: rabbidrabbit on March 07, 2007, 09:05:20 PM

You work for them?

Title: building a win2k3 domain..
Post by: Auger on March 07, 2007, 09:05:25 PM

A domain that small shouldn't be a problem.  There aren't any interdomain trusts to worry about or bushy forests or any of that multi server stuff.  It should be fine setting it up with the defaults as the 1st controller in the domain.

Are you using straight W2K3, or SBS?

Also, you may want to have multiple partitions, just to separate the system drive from all of the shares that will eventually grow on it.

Title: building a win2k3 domain..
Post by: rabbidrabbit on March 07, 2007, 09:10:51 PM

win2k3r2 standard edition.

With win2k you had to set up the DNS first.   Is it simply a matter of setting the defaults?

I forget on this one but once I promote up the server to a domain controller can machines still on the workgroup still see it and mapped drives?  I don't want to break connectivity to mapped drive during the day.

Title: building a win2k3 domain..
Post by: Vulcan on March 07, 2007, 09:32:58 PM

Quote

Originally posted by rabbidrabbit
You work for them?

No, but I work in a kinda pre-sales role with them (and other stuff). And know a tad about the beasties.

Title: building a win2k3 domain..
Post by: lukster on March 07, 2007, 10:41:31 PM

You mentioned DNS. Active Directory relies on it more than before. While WINS is still available I wouldn't use it. Be sure to point all of your workstations to the DNS server running on the AD server or you'll experience very long login times.

Title: Re: building a win2k3 domain..
Post by: Heater on March 08, 2007, 03:13:17 AM

Quote

Originally posted by rabbidrabbit
Any good pointers on what I should be aware of?  I'm building one from scratch for a small company but its been about 5 years since I built one and that was win2k.  It will be for internal use of about 15 users.  Remote access is operational now via a sonicwall device.  They are now simply sitting on a workgroup.

Well yes,

Can you Say LINUX  



:D:D