Is that all there is to setting up an AD domain?

[SunnyD]

I took it upon myself last week to start setting up my home network. No, I don't mean the wiring or the router, etc., but actually setting up some sort of menial infrastructure, servers and all. I had originally planned to just move my web hosting to a box at home, and then figured I'd give email a shot too so I'm not paying anything out of pocket. At the same time, my wife and I both like the features of Exchange, so I figured why not go all out and set up an AD domain at home while I'm at it.

Since this is really a very small and very trivial network, I figured an old laptop running Win2k3 Server would do fine, along with Exchange 2007, IIS for web hosting and also have it be the one and only domain controller on the network.

Other than taking forever and a day to install and update Win2k3, I thought there would be a heck of a lot more to setting up an AD domain. Unless I'm missing something, all it is is setting up DNS, installing and configuring AD (in this example very rudimentary), and then installing additional services (IIS, File Serving, Printer Serving, etc which I'm still in the process of doing). I've worked with AD for some time from the admin side, but I've never actually set a domain up from scratch. Is this really all there is to it for a small network? I have to be missing something, otherwise why do people think AD is "da debil"?

 

[Bluestealth]

Originally posted by: SunnyDotherwise why do people think AD is "da debil"?

I am not sure, I have setup several test domains, fully configured, never had any issues. I have never used Small Business Server but apparently they make it easier to setup, which I am not sure how.... o well, maybe people just have low thresholds for challenge.

 

[RebateMonger]

Originally posted by: Bluestealth
I have never used Small Business Server but apparently they make it easier to setup, which I am not sure how.... o well, maybe people just have low thresholds for challenge.

SBS is able to do a one-step installation of a dedicated small business server. It creates a "standard" small business network: Single Domain, Exchange, SharePoint, and Remote Access. Installing and configuring all that stuff manually is a LOT of work, and it's easy to forget something. There are hundreds of configuration steps that are all performed automatically.

Once you've SBS a few times, the challenge in most SBS installs isn't the Server. It's the client PCs. Many SBS Servers are "first servers", which means that the networks and the client PCs are often "messed up". About 1/3 of all installs are migrations. The client has trashed their old server and want all the client PCs and email have to be migrated to a new Domain, taking care not to lose profiles, documents, or email. Finally, since all are existing networks, it has to be done with little or no disruption to the office.

And finally, as SunnyD notes, there's the "Updates". These often take as long as the entire initial Server install.

 

[netsysadmin]

SunnyD...Exchange 2007 is a 64 bit App and will need to be run on 64 bit hardware. There is a trial version of 32 bit Exchange 2007 out there for testing purposes, but it will time out in 120 days.

John

 

[Bluestealth]

Originally posted by: RebateMonger

Originally posted by: Bluestealth
I have never used Small Business Server but apparently they make it easier to setup, which I am not sure how.... o well, maybe people just have low thresholds for challenge.

SBS is able to do a one-step installation of a dedicated small business server. It creates a "standard" small business network: Single Domain, Exchange, SharePoint, and Remote Access. Installing and configuring all that stuff manually is a LOT of work, and it's easy to forget something. There are hundreds of configuration steps that are all performed automatically.

Once you've SBS a few times, the challenge in most SBS installs isn't the Server. It's the client PCs. Many SBS Servers are "first servers", which means that the networks and the client PCs are often "messed up". About 1/3 of all installs are migrations. The client has trashed their old server and want all the client PCs and email have to be migrated to a new Domain, taking care not to lose profiles, documents, or email. Finally, since all are existing networks, it has to be done with little or no disruption to the office.

And finally, as SunnyD notes, there's the "Updates". These often take as long as the entire initial Server install.

Hmmm I still probably wouldn't consider it for most of my tasks but that is cool, its limited to 1 server per domain right?

 

[RebateMonger]

Originally posted by: Bluestealth
...its limited to 1 server per domain right?

You can only have one SBS 2003 Server per Domain. And SBS can't Trust other Domains. You can have as many other Windows Servers as you want in your Domain as long as you don't exceed the 75 User/Computer limit.

 

[RebateMonger]

Originally posted by: netsysadmin
SunnyD...Exchange 2007 is a 64 bit App and will need to be run on 64 bit hardware. There is a trial version of 32 bit Exchange 2007 out there for testing purposes, but it will time out in 120 days.

I keep forgetting about that. You'll have to run Windows Server 64-bit Edition to run (non-Trial) Exchange 2007.

Also, note that running Exchange on a DC is not generally recommended. Microsoft's discussion of this. SBS 2003 preconfigures this for you. None of the listed issues should be a problem in a small home network.

 

[dphantom]

For a basic home or small business, yes it is fairly easy to set up an AD domain. SBS in particular walks one thru just about everything that needs to be done.

Where the complexity comes in is larger companies. Multi-domain, multi-site, integrating AD DNS and Linus/Unix Bind, multi-forest, AD root domain, child or peer domains all gets complicated pretty fast.

That's why I like SBS for smaller businesses. Quick to set up and fairly easy for the company to maintain on their own with minimal help from me.

 

[SunnyD]

Originally posted by: RebateMonger

Originally posted by: netsysadmin
SunnyD...Exchange 2007 is a 64 bit App and will need to be run on 64 bit hardware. There is a trial version of 32 bit Exchange 2007 out there for testing purposes, but it will time out in 120 days.

I keep forgetting about that. You'll have to run Windows Server 64-bit Edition to run (non-Trial) Exchange 2007.

Also, note that running Exchange on a DC is not generally recommended. Microsoft's discussion of this. SBS 2003 preconfigures this for you. None of the listed issues should be a problem in a small home network.

Hmm, bummer. Looks like I'm going to have to dig out Exchange 2003 then. As far as the system as a whole goes, I'm using Server 2003 Enterprise (Not SBS), with nothing more than a primary domain controller, DNS, File Server & Printer Server and IIS running on it. Per a different discussion, it looks like it will also resort to being the DHCP server too, though I'm not 100% sure on that yet.

This machine will be relatively light duty, with the most critical app being Exchange. I really have nothing that I can't afford to lose, and if I do, it won't be on this machine anyway.

 

[stash]

Exchange 2007 would probably have terrible perf on a laptop anyway. Not that Exchange 2003 and AD will be much better

 

[RebateMonger]

Originally posted by: SunnyD
This machine will be relatively light duty, with the most critical app being Exchange. I really have nothing that I can't afford to lose, and if I do, it won't be on this machine anyway.

Seriously, for a home server, you should be fine, even on the laptop. In a "busy" office, with tons of email coming in, Exchange hits the CPU and (especially) the hard drive pretty hard. But for a home situation, about ANY host PC should be adequate.

The other services, DNS, DHCP, and WINS, won't have any significant CPU or disk usage.

 

[nweaver]

Originally posted by: SunnyD

Originally posted by: RebateMonger

Originally posted by: netsysadmin
SunnyD...Exchange 2007 is a 64 bit App and will need to be run on 64 bit hardware. There is a trial version of 32 bit Exchange 2007 out there for testing purposes, but it will time out in 120 days.

I keep forgetting about that. You'll have to run Windows Server 64-bit Edition to run (non-Trial) Exchange 2007.

Also, note that running Exchange on a DC is not generally recommended. Microsoft's discussion of this. SBS 2003 preconfigures this for you. None of the listed issues should be a problem in a small home network.

Hmm, bummer. Looks like I'm going to have to dig out Exchange 2003 then. As far as the system as a whole goes, I'm using Server 2003 Enterprise (Not SBS), with nothing more than a primary domain controller, DNS, File Server & Printer Server and IIS running on it. Per a different discussion, it looks like it will also resort to being the DHCP server too, though I'm not 100% sure on that yet.

This machine will be relatively light duty, with the most critical app being Exchange. I really have nothing that I can't afford to lose, and if I do, it won't be on this machine anyway.

Wow, you just happen to have a several hundred doller OS (2k3 Enterprise) and mail servers (2007 and 2003) just laying around your house? Pretty sweet, wish I just had that kind of stuff "laying" around to "dig out"

 

[Genx87]

I believe if you sign up as a partner and pay the 300 dollar a year fee MS sends you not for resale versions of about 30 applications with CALs for each. I know Exchange 2003, SBS 2003, Server 2003, ISA 2004 were all part of it. I believe they also include SQL server, and a bunch of other things. The list was about 20-30 applications deep.

MS Action Pack overview

 

[SunnyD]

Originally posted by: nweaver
Wow, you just happen to have a several hundred doller OS (2k3 Enterprise) and mail servers (2007 and 2003) just laying around your house? Pretty sweet, wish I just had that kind of stuff "laying" around to "dig out"

Yep, pretty much. At least Genx87 knows not to judge.

Originally posted by: Genx87
I believe if you sign up as a partner and pay the 300 dollar a year fee MS sends you not for resale versions of about 30 applications with CALs for each. I know Exchange 2003, SBS 2003, Server 2003, ISA 2004 were all part of it. I believe they also include SQL server, and a bunch of other things. The list was about 20-30 applications deep.

https://partner.microsoft.com/US/40013779?PS=3">MS Action Pack overview</a>

 

[RebateMonger]

Originally posted by: nweaver
Wow, you just happen to have a several hundred doller OS (2k3 Enterprise) and mail servers (2007 and 2003) just laying around your house? Pretty sweet, wish I just had that kind of stuff "laying" around to "dig out"

I have four NFR copies of Windows Server 2003, Enterprise Edition, with 25 CALS, sitting on my shelf. Microsoft gave away a lot of these a year or two ago. I've run into quite a few folks using them as the host for Virtual Servers, since the license apparently lets you use four Virtual Servers inside the host Server for "free".

 

[nweaver]

Originally posted by: Genx87
I believe if you sign up as a partner and pay the 300 dollar a year fee MS sends you not for resale versions of about 30 applications with CALs for each. I know Exchange 2003, SBS 2003, Server 2003, ISA 2004 were all part of it. I believe they also include SQL server, and a bunch of other things. The list was about 20-30 applications deep.

https://partner.microsoft.com/US/40013779?PS=3">MS Action Pack overview</a>

I thought you had to have an MCSE on staff to do that. Most folks don't have an action pack laying around (I happen to, but it's rare). Most folks who have an action pack also know what they are doing with it, it's not just something someone randomly decides to order.

 

[Genx87]

Originally posted by: nweaver

Originally posted by: Genx87
I believe if you sign up as a partner and pay the 300 dollar a year fee MS sends you not for resale versions of about 30 applications with CALs for each. I know Exchange 2003, SBS 2003, Server 2003, ISA 2004 were all part of it. I believe they also include SQL server, and a bunch of other things. The list was about 20-30 applications deep.

https://partner.microsoft.com/US/40013779?PS=3">MS Action Pack overview</a>

I thought you had to have an MCSE on staff to do that. Most folks don't have an action pack laying around (I happen to, but it's rare). Most folks who have an action pack also know what they are doing with it, it's not just something someone randomly decides to order.

Nah just be a partner. They suggest having one on staff but it isnt a requirement. I am looking into it once I finally get off my duff and get my company going

 

[networkman]

Originally posted by: nweaver

Originally posted by: Genx87
I believe if you sign up as a partner and pay the 300 dollar a year fee MS sends you not for resale versions of about 30 applications with CALs for each. I know Exchange 2003, SBS 2003, Server 2003, ISA 2004 were all part of it. I believe they also include SQL server, and a bunch of other things. The list was about 20-30 applications deep.

https://partner.microsoft.com/US/40013779?PS=3">MS Action Pack overview</a>

I thought you had to have an MCSE on staff to do that. Most folks don't have an action pack laying around (I happen to, but it's rare). Most folks who have an action pack also know what they are doing with it, it's not just something someone randomly decides to order.

Nope, just need to be a Microsoft Partner. As for me, I'm working toward my MCP in XP.

Edit: Oh, and I also have a seperate Windows 2003 Enterprise NFR that I got as a door prize from the local Windows NT User Group.

 

[WobbleWobble]

Originally posted by: nweaver

Originally posted by: Genx87
I believe if you sign up as a partner and pay the 300 dollar a year fee MS sends you not for resale versions of about 30 applications with CALs for each. I know Exchange 2003, SBS 2003, Server 2003, ISA 2004 were all part of it. I believe they also include SQL server, and a bunch of other things. The list was about 20-30 applications deep.

https://partner.microsoft.com/US/40013779?PS=3">MS Action Pack overview</a>

I thought you had to have an MCSE on staff to do that. Most folks don't have an action pack laying around (I happen to, but it's rare). Most folks who have an action pack also know what they are doing with it, it's not just something someone randomly decides to order.

It's a great way to get software to learn as well. What better way to learn other than hands-on experience?