Jump to content


  • 0
AdinE

SCORCH 2012 SP1 in a LAB – Installation (Part C – Install Active Directory Domain Services)

Question

In our last post we installed the Operating System on our VM's. Now, we will install Active Directory.



Install Active Directory Domain Services


Now that we have the VMs created, and the OS installed on both, we need to first install/setup Active Directory (AD).



When you log into a new installation of Server 2012, Server Manager will auto launch. From Server Manager, click on Manage, and choose ‘Add Roles and Features’.



post-20464-0-09596400-1373732291.png



On the Add Roles and Features Wizard, read the information on the Before You Begin dialog, and then click Next.



post-20464-0-44417200-1373732170.png



On the Installation Type screen, select ‘Role-based on feature-based installation’ and then click Next.



post-20464-0-42379000-1373732171.png



On the ‘Server Selection’ screen, since we are installed Active Directory on this local system, ensure that it is selected, and click Next. Side note: Windows Server 2012 has a new feature that allows you to remotely install Roles and Features on other systems.



post-20464-0-43392700-1373732172.png



On the Server Roles screen, select ‘Active Directory Domain Services’.



post-20464-0-54576900-1373732174.png



When you select ‘Active Directory Domain Services’, immediately you will be presented with the following dialog. Click Add Features.



post-20464-0-40228600-1373732169.png



On the Features screen, accept what has already been selected by default, and click Next.



post-20464-0-21287600-1373732197.png



On the AD DS screen, read the information presented, and click Next.



post-20464-0-88553100-1373732198.png



On the Confirmation screen, check the ‘Restart the destination server automatically if required’ checkbox, and then click Install. Note: You are not required to check the ‘restart’ checkbox, however, you’re going to have to restart the system anyways after the installation, so you might as well let the system do it for you.



post-20464-0-54107700-1373732200.png



Note: When you check off the ‘Restart the destination server automatically if required’ checkbox, you will immediately be prompted with the following dialog. Click Yes.



post-20464-0-48329000-1373732202.png



On the Results screen, click Close.



post-20464-0-31477800-1373732203.png



After the system restarts, and Server Manager launches, you will have to promote the server as a domain controller. This is because Active Directory has been installed, but that process does not automatically promote the server. Click on the ‘Promote this server to a domain controller’ link.



post-20464-0-08914100-1373732292.png



On the Deployment Configuration screen, select ‘Add a new forest’ since this is the first domain controller in our lab. Then enter a root domain name, and click Next. In my example I am using “SC.LAB” for System Center Lab (since I will be installing all other System Center products in my lab eventually).



post-20464-0-22960600-1373732204.png



For the Domain Controller Options, select the appropriate Forest functional level, and Domain functional level. This is more applicable if you already have an existing domain and are adding a new domain controller. But since this is the first domain controller in our new domain, then we’ll use the highest level, that of Windows Server 2012. Also, don’t forget to create the Directory Service Restore Mode password. Then press Next.



post-20464-0-92866700-1373732223.png



On the DNS Options screen, you can ignore this warning message and click Next.



post-20464-0-90729000-1373732224.png



On the Additional Options screen, click Next.



post-20464-0-90543600-1373732225.png



On the Paths screen, normally you would change the location for the database, log files, and SYSVOL, but since we are just in a lab environment, we’ll leave it at the defaults and click Next.



post-20464-0-90653800-1373732226.png



On the Review Options scree, review what you have entered/selected, and click Next.



post-20464-0-92506000-1373732227.png



The Prerequisites Check screen will check and confirm that everything passes before promoting the system as a domain controller. You will notice in my screenshot, that I have 1 warning because I didn’t set a static IP for the server yet.



post-20464-0-38784000-1373732229.png



After installation completes, the system will automatically restart. You will then be presented with the login screen. Something to note here, that because we were originally logged in with a local account, the first time you want to log on using a domain account you will have to type the domain\username; in my example SC\Administrator.



post-20464-0-28616200-1373732233.png



When you login, you will then see in the Server Manager, that AD DS is now listed, along with DNS.



post-20464-0-04811500-1373732288.png



Now all that you need to do is assign a static IP to your domain controller.



To do this, in Server Manager, select Local Server from the panel on the left. From there, click on the Ethernet link labelled ‘IPv4 address assigned by DHCP, IPv6 enabled’.



post-20464-0-58572700-1373732163.png



This will cause the Networks Connections explorer to open.



From here, right click on the Ethernet network that is displayed. This is in fact the network connection that we configured when we first created the VM.



post-20464-0-26571800-1373732230.png



On the Ethernet Properties dialog, select ‘Internet Protocol Version 4 (TCP/IPv4)’ and click the Properties button.



post-20464-0-92107200-1373732282.png



Within the Internet Protocol Version 4 (TCP/IPv4) Properties dialog, enter a static IP, gateway, and DNS that is applicable to your network. Once all the items have been entered, click OK. You will also have to click Close on the Ethernet Properties dialog as well.



post-20464-0-29786200-1373732284.png



Congratulations, you now have a domain setup in your lab environment.



Add Systems to Your Domain


Now that you have your domain setup, you need to add your other VM (the one that we will use for Orchestrator) to the domain before being able to install Orchestrator.


Log into the system you want to add to the domain. To do this in Server 2012, launch Server Manager, and click on Local Server.



post-20464-0-94853900-1373732286.png



Then click on the computer name. This will launch the System Properties dialog. From this dialog, click the Change button.



post-20464-0-65883300-1373732293.png



From this dialog, select the Domain option for ‘Member of’, and enter the domain name you want to join and press OK.



post-20464-0-80329100-1373732294.png



After pressing OK, you are immediately presented with a Windows Security dialog, in which you need to enter the credentials of an account that has Domain Admin rights. Enter the credentials and click OK.



post-20464-0-18605600-1373732232.png



Once the system is successfully joined to the domain, you will receive the following Welcome message. Press OK.



post-20464-0-18504000-1373732282.png



After you press OK to the Welcome message, you will receive a second prompt, indicating that you need to restart the system for the changes to take effect.



post-20464-0-53828100-1373732303.png



You will be back on the System Properties dialog. Press Close.



post-20464-0-79242900-1373732305.png



When you press Close, you will receive yet another prompt about restarting the system. You can choose to Restart Now or Restart Later, but you won’t be able to install Orchestrator without the VM being added to the domain.



post-20464-0-59701400-1373732304.png



After the system restarts, you will then be presented with the login screen. Something to note here, that because we were originally logged in with a local account, the first time you want to log on using a domain account you will have to type the domain\username; in my example SC\Administrator.



post-20464-0-28616200-1373732233.png



Now we have our Active Directory server setup and ready, and the VM we will be installing Orchestrator on is joined to the domain.



Now we can move onto installing SQL Server.


Share this post


Link to post
Share on other sites

0 answers to this question

Recommended Posts

There have been no answers to this question yet

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.