SPS 2010 Install – Windows Server 2008 and ADDS

You guys know I’m no Windows expert; I’m way too easily frustrated. It’s great to have experts to lead us. I’m going to try this item from CodeProject.com to create a domain conttoller with the hopes of mapping the whole SPS 2010 instsall.

There’s alot of material to cover so this may take a few tries. I’m using the Server 2008 R2 x64 on a the Dell host I’ve talked about earlier.

Creating a new virtual machine is pretty easy in the Hyper-V manager. I told it to  give it 4gb RAM, give it a LAN connection and install an OS from the host CD drive when it starts up. The Windows Server install starts up and asks some rudimentaty setup questions. Click, click, click and you get a cool little status bar that says  2. Installing Windows.

This looks like it may take a little while. 5% in five minutes; makes the math easy.

brb… I’m expanding files…

Expanding files is a non-linear process since it finished in less than 20 minutes, The VM reboots and it comes up with an OK\Cancel screen that says I have to change my password. I click OK. My user name is Administrator and I have to enter a password twice.

It prepares my desktop and gives me a set of configuration tasks.

  • Activate Windows
  • Set Time Zone
  • Configure Networking – It already read the DHCP since I told the VM to attach to the LAN.
  • Provide computer name and domain – I don’t have a domain yet but I’ll name it MyDomainController and leave it in the default workgroup.

Reboot.

I check for and install 15 updates. This takes about 20 minutes and requries another reboot.

I get to Add Roles.

The Select Server Roles dialog wizard opens up. On the Server Roles tab, I check Active Directory Domain Services (ADDS). A second dialog box pops up asking to add the .Net Fx 3.5 features required for ADDS. I click Add Required Features button.

When I try to add any other roles, I get an error that says ADDS has to be added alone.

So, I uncheck ADDS and check the application server and the Web Server instead. When I click through the rest of the dialogs, these roles install and then I need to reboot.

After the reboot, I go back to add the ADDS role and click Next.

I get a page of information including that I have to run DNS and DCPromo.exe to complete my setup. I click Next and then Install. The progress bar takes a minute and I get the results page that indicates success.

I open a command window and run DCPromo.exe

I get the ADDS Installation Wizard. I check Advanced mode for good measure and click Next.

I get this schpeil about OS Compatibility. This is way complicated so I ignore it and click Next promising myself I’d go look at the KB article to which it refers.

I dot the Create a new domain in a new forest option and click Next.

It wants the fully qualified domain name of this new forest. I enter MyNewDomain.com and click Next.

The wizard checks for naming conflicts and gives me a NetBiosName: MYNEWDOMAIN. I click Next.

It asks me for a functional level. I choose Windows Server 2008 R2. Again, I’m flying blind here.

It tells me it needs a DNS server. It told me it would do this earlier so I leave the box checked and click Next.

Here it barfs on dynamic IP address. I never gave this box a static IP so I have to tell it I will by clicking on the No, I will assign.. option and it takes me back to the Installation Wizard.

I go to the Network and Sharing Center and click on the Local Area Connection and then on the Properties button. Click on IPv4 and then Properties. Here I claim a static IP address suitable to my router and add in the DNS servers that my host server uses.

I go back and click the No, I will assign.. button again.

Here, it warns me that the DNS servers I just picked do not recognize my new domain name. This is not surprising as I will have to update the internet using my registrar’s software.  I tell it I want to continue all the same.

I’ve only got the one hard drive so all my DNS files go on there. I click Next. I enter my new domain Restore Mode Admin’s password. I enter it twice and click Next here  and again on the Summary page.

Then I get a Finish page and I click Finish and reboot.

When the machine restarts, it prompts me for the MyNewDomain\Administrator password. I enter it and everything is good. Since this is a virtual machine, I go back to the Hyper-V manager on my host and take a snapshot. At this point, I think I can revet to this state at any time in the Hyper-V manager. This is good, because in the past, I have always screwed something up in the subsequent steps and wanted to start over. It’s good to know I can spin up a fresh domain controller any time I want. 

– robot


Tags:

 
 
 

Comments are closed.