ആദ്യം ISO ഇമേജ് ഉണ്ടാക്കേണ്ട സിഡി സിഡി ഡ്രൈവില് ഇടുക.Applications > Sound & Video > Brasero Disc Burning ടൂള് പ്രവര്ത്തിപ്പിക്കുക.ഇപ്പോള് വരുന്ന Brasero വിന്ഡോയില് Disc copy ബട്ടണ് ക്ലിക്ക് ചെയ്യുക.ഇപ്പോള് DC/DVD copy options എന്ന വിന്ഡോ പ്രത്യക്ഷപ്പെടും. ഇവിടെ Select a drive to write to എന്നിടത്തെ ഡ്രോപ് ഡൗണ് ലിസ്റ്റില് File image സെലക്ട് ചെയ്യുക.Properties ബട്ടണ് ക്ലിക്ക് ചെയ്യുക.ഇപ്പോള് പ്രത്യക്ഷപ്പെടുന്ന Disc image file properties വിന്ഡോയിലെ Name എന്നിടത്ത് ഡിസ്ക് ഇമേജ് നെയിം ടൈപ്പ് ചെയ്യാം. ഉദാഹരണം: ubuntu.iso.Apply ബട്ടണ് ക്ലിക്ക് ചെയ്യുക.വീണ്ടും CD/DVD copy options വിന്ഡോയില് എത്തും. അവിടെ Copy ബട്ടണ് ക്ലിക്ക് ചെയ്യുക. ഇപ്പോള് ISO ഇമേജ് നിര്മ്മിക്കാന് തുടങ്ങും.റൈറ്റിംഗ് തീര്ന്നാല് ubuntu.iso എന്ന ഇമേജ് ഫയല് Home ഫോള്ഡറില് കാണാം.
Windows 7 Remote Desktop Activation
Windows 7 Remote Desktop feature if you want to connect to this computer remotely from other computer. This is useful if you have several computers on your home network and you wish to remote access all other computers from only a computer.1) As usual, go to Start, right click Computer and then click onProperties.
2) The computer properties window will appear, proceed to click onRemote settings. If you don’t like this way, you can also open this window by going to Control Panel -> System and Security -> System.
3) Proceed to click on Remote tab in System Properties window, this is the location you could enable this Remote Desktop access feature. Click on Allow connections from computers running any version of Remote Desktop (less secure) option if your Remote Desktop client doesn’t support Network Level Authentication.
You are also required to click Select Users button to choose the users that can connect to this computer remotely. Continue to read more below before clicking Apply and OK button.
Note: I highly recommend you to choose that Allow connections only from computers running Remote Desktop with Network Level Authentication (more secure) option if your Remote Desktop client supports that Network Level Authentication. If you want to check, just open the client (Start->All Programs->Accessories->Remote Desktop Connection) and click on upper left corner icon to open the About window, you will then find out whether it’s supported.
Note: If you click Select Users button in system Properties window, you can add the users that can connect to this computer remotely. By default the current user id that you use to enable this Remote Desktop will be allowed to connect remotely (which is Ivan the current logged on user in this case). You can click Add... to add other users.
Note: Please note that the Remote Desktop must be enabled (in your respective network location type) as exception in Windows Firewall, so that this Remote Desktop traffic will be permitted by firewall! If not this Remote Desktop traffic will be dropped by this firewall.
Note: Please also make sure Block all incoming connections, including those in the list of allowed programs check box is not enabled in Windows firewall! If it’s check, then no remote connection can be made from other computers.
ഡൊമെയിന് നെയിമുകള് URL(യൂണിഫോം റിസോഴ്സ് ലൊക്കെറ്റര്) ( ഡൊമെയിന് നെയിമുകള് ഒന്നൊ അതിലധികമൊ ഐ പി അഡ്രസുകളെ തിരിച്ചറിയാനായി ചെയ്യാനായി ഉപയോഗിക്കുന്ന പേരുകളാണ്. ഉദാഹരണത്തിനു ഗൂഗിൾ എന്ന ഡൊമെയിന് നെയിമിനു ഒരു ഡസനോളം ഐ പി അഡ്രസുകള് ഉണ്ടായിരിക്കും. ) കളില് ഒരു പ്രത്യേക വെബ് സൈറ്റിനെ എളുപ്പത്തില് മനസ്സിലാക്കാനായി ഉപയോഗിക്കുന്നവയാണ്. ഈ ഡൊമെയിന് നെയിമുകളെ ഐ പി അഡ്രസുകളായി മാറ്റാന് ഉപയോഗിക്കുന്ന സര്വീസുകളെയാണ് ഡൊമെയിന് നെയിം സെര്വീസ് എന്നു പറയുന്നത്. ഉദാഹരണമായി ഒരു ബ്രൌസറിൽ www.google.com എന്നു ടൈപ്പ് ചെയ്യുമ്പോള് അതിനെ കണ്വെര്ട്ട് ചെയ്തു ഒരു ഐപി അഡ്രസായി കമ്പ്യൂട്ടറിനു മനസ്സിലാക്കി കൊടുക്കുവാനായിട്ടാണ് ഡൊമെയിൻ നെയിം സെര്വര്/സെര്വീസ് എന്ന സങ്കേതമുപയോഗിക്കുന്നത്. ഏല്ലാ ഡൊമെയിന് നെയിമുകള്ക്കും വ്യത്യസ്തങ്ങളായ ഐപി അഡ്രസുണ്ടായിരികും. ഓരൊ തവണയും ഒരു വെബ് അഡ്രസ്, ബ്രൌസറിലെ അഡ്രസ് ബാറില് ടൈപ്പ് ചെയ്യുമ്പോള് അതിനെ ഒരു ഐ പി അഡ്രസ്സായി കണ്വെര്ട്ട് ചെയ്യുക എന്നുള്ളതാണ് ഡൊമെയിന് നെയിം സെര്വീസിന്റെ ലക്ഷ്യം..
ഇന്റര്നെറ്റ്, ഐപി അഡ്രസിനെ അടിസ്ഥാനമാക്കിയുള്ളതാണ് അവ ഡൊമെയിന് നെയിമുകളെ അടിസ്ഥാനമാക്കിയല്ല നിലനില്ക്കുന്നത്. ഡൊമെയിന് നെയിമുകള് ഒരു ഐപി അഡ്രസിനെക്കാള് എളുപ്പത്തില് ഓര്മ്മിച്ചിരിക്കുവാന് കഴിയുന്നതു കൊണ്ടാണ് ഈ ഐ പി വിലാസങ്ങളെ മനസ്സിലാക്കുന്നതിനായി ഓരൊ ഐപി വിലാസങ്ങള്ക്കും ഒരു ഡൊമെയിന് നെയിമുകള് നിശ്ചയിച്ചിരിക്കുന്നത്. ഇന്റര്നെറ്റിലെ അഡ്രസ് ബുക്കുകളാണ് ഡി എന് എസ് സെര്വറുകള്. ഔദ്യോഗികമായി 13 ടോപ്പ് ലെവൽ ഡി എൻ എസ് സെർവറുകളാണുള്ളത്
What is DNS?
DNS stands for Domain Naming Server, it is a standard of naming domains in any operational environment (Windows,Linux,Solaris,Any environment). It is a server which contains a database of all the domains and all the servers which are associated with those domains.
Why it is Used?
Its a service dedicated to identify all the machines (domains & member servers) in a network. To make this possible, every machine has to be registered in the authoritative DNS server of that network. That means every operational network should have a dedicated DNS server to enable identification and communication between the machines.
How it works?
As i said, it is dedicatedly used for identification, in technical words for “name resolution”. Every machine in a network has a dedicated IP address & hostname as its identity.
Whenever a machine tries to communicate with another machine on the network it should first identify the second machine, that means it should know the ip address of that particular machine. After knowing the identity (i.e ip address), it will directly communicates with the second machine. So to speak, a machine should know the ip address of the another machine, with which its going to communicate before it starts. Another question… Why the hostnames are used, if the machine already have an identity in the terms of IP address? Hostname is an English word which is useful for Human remembrance. It is impossible for a human being to remember lots of IP addresses, but it is possible to remember English names of the same hosts (as we configure the hostnames generally with employee name or department name or location name etc). For example we can remember www.yahoo.com but not its ip address, because we are not having only one website on the internet. To sum up Hostnames and IP addresses both are used to identification and communication between two machines in a network. But machines are only able to communicate with the IP addresses and which are impossible to remember for Humans (Keep in mind machines never communicate with hostnames). To solve this situation DNS was implemented. It basically contains a database of host records in a network. A host record contains “Hostname : IP address”, see the image below for better under standing. Out Internet is purely depended on DNS, when we access a particular website we will give its English name, when we press ENTER immediately the machines starts finding the IP address of the website using the DNS server configured on it. I will explain the name resolution process in details. And one more thing about the DNS is, it is the only largest database on the internet which changes every second. If this database goes down by a chance, we must remember all the ip addresses to access the internet. hahaha it will not happen, why because we have so many backup solutions already implemented.
Whenever a machine tries to communicate with another machine on the network it should first identify the second machine, that means it should know the ip address of that particular machine. After knowing the identity (i.e ip address), it will directly communicates with the second machine. So to speak, a machine should know the ip address of the another machine, with which its going to communicate before it starts. Another question… Why the hostnames are used, if the machine already have an identity in the terms of IP address? Hostname is an English word which is useful for Human remembrance. It is impossible for a human being to remember lots of IP addresses, but it is possible to remember English names of the same hosts (as we configure the hostnames generally with employee name or department name or location name etc). For example we can remember www.yahoo.com but not its ip address, because we are not having only one website on the internet. To sum up Hostnames and IP addresses both are used to identification and communication between two machines in a network. But machines are only able to communicate with the IP addresses and which are impossible to remember for Humans (Keep in mind machines never communicate with hostnames). To solve this situation DNS was implemented. It basically contains a database of host records in a network. A host record contains “Hostname : IP address”, see the image below for better under standing. Out Internet is purely depended on DNS, when we access a particular website we will give its English name, when we press ENTER immediately the machines starts finding the IP address of the website using the DNS server configured on it. I will explain the name resolution process in details. And one more thing about the DNS is, it is the only largest database on the internet which changes every second. If this database goes down by a chance, we must remember all the ip addresses to access the internet. hahaha it will not happen, why because we have so many backup solutions already implemented.
How the name resolution takes place?
I will explain this concept with internet as an example. Before that i want you to check some settings on your machine. Check the TCP/IP properties and see whether DNS server is configured or not. If you are seeing obtain automatically option, open command prompt and type “ipconfig /all” and press Enter. You will get DNS servers information along with your machine’s IP address. Now lets talk about the scenario, When you try to open a website like www.google.com, what happens next? how your machine gets IP address of the www.google.com. Here it goes….
1. The request sent to the DNS server which is configured on your machine.
2. The DNS server checks for the host record of www.google.com in its database, if it contains a record for www.google.com, it will directly send response with the IP address of www.google.com. Otherwise it starts requesting another DNS server.
3. Before it goes to another DNS server, how it identifies which DNS server is responsible for this request ? It checks the entire hostname (it is called as FQDN : Fully Qualified Domain Name), i.e in google’s case www.google.com. (note the FQDN ends with a period, and this period is called as root domain).
4. Every DNS server contains a roothint file associated with it, and the same will be used to identify the responsible DNS server. Root hint file contains Master DNS servers information. Here you go it looks like this. These are the master DNS servers for .com, .net, .edu, .org domains etc.
5. So in your case, the domain is .com, DNS server sends request to .com master DNS server (for ex: assume it as 198.41.0.4), the .com master DNS server contains name server records for all machines ending with .com . That means it definitely contains DNS server IP address for google.com. In the same way it contains all .com servers yahoo.com, microsoft.com & so on.
6. It does not contain the IP address of google.com, it contains DNS server IP of google.com.
7. So then the request is forwarded to google.com DNS server, in that server you will have a host record with the name www and its IP address. Finally you reached it. With the found IP address the request comes back as a response in the same reverse way to the DNS server which is configured in your machine, that DNS server tells the IP address of www.google.comto your machine.
8. This process happens in milliseconds in the background. i.e by the time you will get “Website found waiting for reply” message in the status bar of your internet explorer.
The process of installing an Active Directory domain in Windows Server 2008 is quite simple, but some beginners or IT professionals that have never had a chance to get their hands on AD installations and that are not familiar with its requirements might stumble across a few pitfalls.
Here is a quick list of what you must have:
- An NTFS partition with enough free space
- An Administrator's username and password
- The correct operating system version
- A NIC
- Properly configured TCP/IP (IP address, subnet mask and - optional - default gateway)
- A network connection (to a hub or to another computer via a crossover cable)
- An operational DNS server (which can be installed on the DC itself)
- A Domain name that you want to use
An NTFS Partition
To successfully install AD you must have at least one NTFS formatted partition. Back in older operating systems this was something that you actually had to tell people about, because *some* administrators had servers that did not have their partitions formatted with NTFS. Nowadays, NTFS is the only way to go in Windows-based servers, but I will nevertheless put it on the writing, just to make sure.
This partition is where the SYSVOL folder is placed, and usually, that is the C:' partition, but for large AD deployments, this could very well be a different partition.
To convert a partition (C:) to NTFS type the following command in the command prompt window:
convert c:/fs:ntfs
Free space on your disk
You need at least 250mb of free space on the partition you plan to install AD on. Of course you'll need more than that if you plan to create more users, groups and various AD objects.
Local Administrator's username and password
Remember, only a local Administrator (or equivalent) can install the first domain and thus create the new forest. Other installation scenarios – such as adding additional (replica) DCs require either Domain Admin permissions, or, in case of new domains in the same tree or in new trees – Enterprise Admins permissions.
The right operating system version - Windows Server 2008 Standard, Enterprise or Data Center
IP ConfigurationWhile it is possible to install Active Directory on a server that has a dynamically-assigned IP address, it doesn't make much sense to do so. It's much better to configure the server with a manual and dedicated IP address. If you do not use a dedicated IP address, DNS registrations may not work and Active Directory functionality may be lost. If the computer is a multi-homed computer, the network adapter that is not connected to the Internet can host the dedicated IP address.
The Active Directory domain controller should point to its own IP address in the DNS server list to prevent possible DNS connectivity issues.
To configure your IP configuration, use the following steps:
Note: IP addresses can be also configured from the Command Prompt by using the NETSH command, but I will not describe that procedure here.
- Right-click Network, and then click Properties.
- In the Control Panel'Network and Sharing Center window, click on the manage Network Connections link on the left.
- In the Control Panel'Network Connections window, right-click Local Area Connection, and then click Properties.
- Click Internet Protocol version 4 (TCP/IPv4), and then click Properties.
- Make sure you have a static and dedicated IP address. If you don't need Internet connectivity through this specific NIC you can use a Private IP range such as 192.168.101.0 with a Subnet Mask of 255.255.255.0.
- The next step is not required, but I usually recommend checking that the correct configuration is in place. Click Advanced, and then click the DNS tab. The DNS information should be configured as follows:
If you do not have the Network icon visible on your desktop, use Control Panel.
Note: You can get to the same window by typing NCPA.cpl in the run command.
Note: You can also configure the TCP/IPv6 properties, but you do NOT have to, and frankly, unless you require TCP/IPv6 functionality, I'd simply ignore it or disable it. More on that, in a future article.
Configure the DNS server addresses to point to the DNS server. This should be the computer's own IP address if it is the first server or if you are not going to configure a dedicated DNS server.
- If the Append these DNS suffixes (in order) option is selected for the resolution of unqualified names, the Active Directory DNS domain name should be listed first, at the top of the list.
- Verify that the information in the DNS Suffix for this connection box is the same as the Active Directory domain name.
- Make sure that the Register this connection's addresses in DNS check box is selected.
Active Network Connection Required During Installation
The installation of Active Directory requires an active network connection. When you attempt to use DCPROMO.exe to promote a Windows Server 2008 computer to a domain controller that doesn't have a connected and active NIC, you will receive the following error message:
And after hitting Next, this error will appear:
Active Directory Domain Services Installation Wizard The TCP/IP networking protocol must be properly configured. Complete the configuration before you proceed.
This problem can occur if the network cable is not plugged into a hub or other network device. (Screenshot of a connected NIC) (Sample of a disconnected or un-plugged network cable)
To resolve this problem, plug the network cable into a hub or other network device. While highly improbable that the network connection status would be disconnected in a server that is about to be deployed in a production environment, this could be the case when building the server for testing purposes. If network connectivity is not available and this is the first domain controller in a new forest, you can finish DCPROMO.exe by installing Microsoft Loopback Adapter.
DNS Configuration
A DNS server that supports Active Directory DNS entries (SRV records) must be present for Active Directory to function properly. In my Windows 2000/2003 versions of the Active Directory installation tips I recommended to manually install and configure DNS prior to running DCPROMO. However, in Windows Server 2008, and when installing the FIRST Domain Controller in the Active Directory domain, I tend to recommend that you allow the DCPROMO wizard to automatically build the proper DNS services and configuration.
Client Connections
When considering Internet connectivity, it is recommended (and in most cases, this is the proper and most-used configuration) that the client computers connect to the Internet through a NAT device (i.e. a Router that translates private IP addresses to one public one, and allows connectivity through one ISP-assigned IP address). This prevents any issues that may arise if clients obtain an IP address from your Internet service provider (ISP). In Small Office or Home Office (SOHO) scenarios, this can be achieved by using a second network adapter on the server connected to a hub. You can use NAT and Routing on the server to isolate the clients on the local network. The clients should point to the domain's INTERNAL DNS server, and NOT to the ISP's DNS server, to ensure proper DNS connectivity. The internal DNS server's forwarder will then allow the clients to access DNS addresses on the Internet.
Do not use Single-Label domain names
As a general rule, Microsoft recommends that you register DNS domain names for internal and external namespaces with Internet authorities. This is true for Windows 2000/2003 and for Windows Server 2008. This includes the DNS names of Active Directory domains, unless such names are sub-domains of names that are registered by your organization name, for example, "corp.example.com" is a sub-domain of "example.com". When you register DNS names with Internet authorities, it prevents possible name collisions should registration for the same DNS domain be requested by another organization, or if your organization merges, acquires or is acquired by another organization that uses the same DNS names.
DNS names that don't include a period ("dot", ".") are said to be single-label (for example, com, net, org, bank, companyname) and cannot be registered on the Internet with most Internet authorities.
Microsoft Active Directory provides the structure to centralize the network management and store information about network resources across the entire domain. Active Directory uses Domain Controllers to keep this centralized storage available to network users. In order to configure a Windows Server 2008 machine to act as Domain Controller, several considerations and prerequisites should be taken into account, and several steps should be performed. In this article I will guide you through these prerequisites and steps of creating a new Windows Server 2008 Domain Controller for a new Active Directory domain in a new forest.
Considerations when Installing a new Windows Server 2008 forest
When you install AD to create the first domain controller in a new Windows Server 2008 forest, you must keep the following considerations in mind:
- You must make forest and domain functional level decisions that determine whether your forest and domain can contain domain controllers that run Windows 2000 Server, Windows Server 2003, or both. To read more about forest and domain functional levels please refer to the links below.
- Domain controllers running the Microsoft Windows NT Server 4.0 operating system are NOT supported with Windows Server 2008.
- Servers running Windows NT Server 4.0 are NOT supported by domain controllers that are running Windows Server 2008, meaning you MUST have additional DCs running Windows 2000/2003 to support older NT 4.0 servers.
nstalling Active Directory Domain Services (AD-DS)
In Windows Server 2008, unlike previous server operating Systems, there is an additional step that needs to be taken before running DCPROMO to promote the server to Domain Controller and installing Active Directory on it. This step is the installation of Active Directory Domain Services (AD-DS) role on the server. In fact, the AD-DS role is what enables the server to act as a Domain Controller, but you will still need to run DCPROMO the regular way.
AD-DS can be installed in one of 3 methods:
Method 1 – Server Manager/Initial Configuration Tasks
Roles can and should be added from Server Manager (but they can also be initiated from the Initial Configuration Tasks wizard that auto-opens the first time you log on to the server).
- Open Server Manager by clicking the icon in the Quick Launch toolbar, or from the Administrative Tools folder.
- Wait till it finishes loading, then click on Roles > Add Roles link.
- In the Before you begin window, click Next.
- In the Select Server Roles window, click to select Active Directory Domain Services, and then click Next.
- In the Active Directory Domain Services window read the provided information if you want to, and then click Next.
- In the Confirm Installation Selections, read the provided information if you want to, and then click Next.
- Wait till the process completes.
- When it ends, click Close.
- Going back to Server Manager, click on the Active Directory Domain Services link, and note that there's no information linked to it, because the DCPROMO command has not been run yet.
- Now you can click on the DCPROMO link, or read on.
- To run DCPROMO, enter the command in the Run command, or click on the DCPROMO link from Server Manager > Roles > Active Directory Domain Services.
- Depending upon the question if AD-DS was previously installed or not, the Active Directory Domain Services Installation Wizard will appear immediately or after a short while. Click Next.
- In the Before you begin window, click Next.
- In the Select Server Roles window, click to select Active Directory Domain Services, and then click Next.
- In the Active Directory Domain Services window read the provided information if you want to, and then click Next.
- In the Confirm Installation Selections, read the provided information if you want to, and then click Next.
- Wait till the process completes.
- When it ends, click Close.
- Going back to Server Manager, click on the Active Directory Domain Services link, and note that there's no information linked to it, because the DCPROMO command has not been run yet.
- Now you can click on the DCPROMO link, or read on.
- To run DCPROMO, enter the command in the Run command, or click on the DCPROMO link from Server Manager > Roles > Active Directory Domain Services.
- Depending upon the question if AD-DS was previously installed or not, the Active Directory Domain Services Installation Wizard will appear immediately or after a short while. Click Next.
- In the Operating System Compatibility window, read the provided information and click Next.
- In the Choosing Deployment Configuration window, click on "Create a new domain in a new forest" and click Next.
- Enter an appropriate name for the new domain. Make sure you pick the right domain name, as renaming domains is a task you will not wish to perform on a daily basis. Click Next.
- Pick the right forest function level. Windows 2000 mode is the default, and it allows the addition of Windows 2000, Windows Server 2003 and Windows Server 2008 Domain Controllers to the forest you're creating.
- Pick the right domain function level. Windows 2000 Native mode is the default, and it allows the addition of Windows 2000, Windows Server 2003 and Windows Server 2008 Domain Controllers to the domain you're creating.
- The wizard will perform checks to see if DNS is properly configured on the local network. In this case, no DNS server has been configured, therefore, the wizard will offer to automatically install DNS on this server.
- It's most likely that you'll get a warning telling you that the server has one or more dynamic IP Addresses. Running IPCONFIG /all will show that this is not the case, because as you can clearly see, I have given the server a static IP Address. So, where did this come from? The answer is IPv6. I did not manually configure the IPv6 Address, hence the warning. In a network where IPv6 is not used, you can safely ignore this warning.
- You'll probably get a warning about DNS delegation. Since no DNS has been configured yet, you can ignore the message and click Yes.
- Next, change the paths for the AD database, log files and SYSVOL folder. For large deployments, carefully plan your DC configuration to get the maximum performance. When satisfied, click Next.
- Enter the password for the Active Directory Recovery Mode. This password must be kept confidential, and because it stays constant while regular domain user passwords expire (based upon the password policy configured for the domain, the default is 42 days), it does not. This password should be complex and at least 7 characters long. I strongly suggest that you do NOT use the regular administrator's password, and that you write it down and securely store it. Click Next.
- In the Summary window review your selections, and if required, save them to an unattend answer file. When satisfied, click Next.
- The wizard will begin creating the Active Directory domain, and when finished, you will need to press Finish and reboot your computer.
Note: Do NOT use single label domain names such as "mydomain" or similar. You MUST pick a full domain name such as "mydomain.local" or "mydomain.com" and so on.The wizard will perform checks to see if the domain name is not already in use on the local network.Note: If you select "Windows Server 2008" for the forest function level, you will Not be prompted to pick a domain function level.Note: The first DCs must also be a Global Catalog. Also, the first DCs in a forest cannot be a Read Only Domain controller.Note: You can automate the rebooting process by checking the Reboot on Completion checkbox.To automate domain controller installations, you can use an answer file or you can specify unattended installation parameters at the command line configuring a Windows Server 2008 Server Core machine REQUIRES you to perform an automated installation of Active Directory on that server, as there is NOT DCPROMO GUI on Server Core.Your server now acts as a Domain Controller. Make sure you properly back it up. You can test functionality by using AD management tools such as Active Directory Users and Computers, examine the Event Logs, services and folders and shares that have been created.
Method 2 – Servermanagercmd.exe
Servermanagercmd.exe is the command prompt equivalent of the Add Roles and Add Features wizards in Server Manager. Through the use of various command line options, you can quickly and easily add or remove features and roles to or from your server, including the AD-DS role.To install AD-DS by using Servermanagercmd.exe, simply enter the following command in the Command Prompt window:Servermanagercmd.exe –I ADDS-Domain-Controller
Let the command run and when it finishes, AD-DS will be installed on the server.Method 3 – Letting DCPROMO do the job
Oh yes. If you forget to install AD-DS or simply want to skip clicking on some windows, you can run DCPROMO from the Run command and before it is executed, the server will check to see if the AD-DS binaries are installed. Since they are not, they will auto-install.After you complete the Add Roles Wizard, either click the link to start the Active Directory Domain Services Installation Wizard, or close Server Manager and manually run DCPROMO from the Run command.