Microsoft Azure Traffic Manager allows you to control the distribution of user traffic for service endpoints in different datacenters and region. Traffic Manager support distribution of traffic for Azure VMs, Web Apps, cloud services and non-Azure endpoints.
Traffic Manager uses the Azure DNS to direct client requests to the most appropriate endpoint based on a traffic-routing method and the health of the endpoints.
Traffic Manager uses vanity domain name to direct traffic to desired endpoints based on geographic location of the user and nearest Azure Datacentre where endpoint is located.
||Vanity Domain Name
||Public IP Address of endpoint
||Public IP Address of endpoint
Traffic Manager act like a DNS routing system to direct clients to specific service endpoints based on the rules of the traffic-routing method. Clients connect to the selected endpoint directly. Traffic Manager is not a proxy or a gateway. Traffic Manager does not see the traffic passing between the client and the service.
To Create Traffic Manager Profile,
- From a browser, sign in to the Azure portal.
- Click Create a resource > Networking > Traffic Manager profile > Create
- In the Create Traffic Manager profile, Select Geographic Routing Method, Resource Group Location and create profile.
- Select the Profile, Navigate to Settings -> Endpoints in Traffic Manager.
- Click Add to show the Add Endpoint.
- Click Add and in the Add endpoint, Type the Name and Source Type then Add geo-mapping to the endpoint.
- To test the Geo-mapping and Traffic routing, you can use any free VPN service or subscribe a VPN service and connect to region using the VPN service and access your endpoint. You will be directed to the nearest endpoint you have configured in step 5 & 6.
Forest Functional Prerequisites
- Check to ensure the Domain Functional Level is currently setup to at least Windows 2003 mode.
- Open the Active Directory Users and Computers console, select the domain via the right mouse button on it.
- Select Raise Domain Functional Level and review the Current domain functional level reported minimum Windows Server 2003.
Your account must be a member of Domain Admins, Schema Admins and Enterprise Admin.
|Free disk space requirements
||800 x 600 or higher
Prepare Windows Machine
- Download Windows Server 2012 R2.
- Build Windows Server 2012 R2
- Join the Server to Domain with a static IP
Prepare Forest and Domain
- Mount Windows Server 2012 R2 ISO on to the Windows Server 2008 R2 Domain Controller.
- Log on to Windows 2008 R2 Domain as an administrator.
- Open command prompt as an administrator, and type adprep /forestprep and press enter.
- Open command prompt as an administrator, and type adprep /domainprep and press enter.
Install AD DS Role
- Open the Server Manager console and click on Add roles and features
- Select Role-based of featured-based installation and select Next.
- Select the Active Directory Domain Services role.
- Accept the default features required by clicking the Add Features button.
- On the Features screen click the Next button.
- On the Confirm installation selections screen click the Install button. Check off the Restart the destination server automatically if required
- Click the Close button once the installation has been completed.
- Once completed, notification is made available on the dashboard highlighted by an exclamation mark. Select it and amidst the drop down menu select Promote this server to a domain controller.
- Select add a Domain Controller into existing domain
- Ensure the target domain is specified. If it is not, please either Select the proper domain or enter the proper domain in the field provided.
- Click Change, provide the required Enterprise Administrator credentials and click the Next button.
- Define if server should be a Domain Name System DNS server and Global Catalog (GC). Select the Site to which this DC belongs to and define Directory Services Restoration Mode (DSRM) password for this DC
- Click the Next button on the DNS options screen.
- Click the Next button once completed.
- Specify location for AD database and SYSVOL and Click the Next button.
- Next up is the Schema and Domain preparation. Alternately, one could run ADPrep prior to commencing these steps, if ADPrep is not detected, it will automatically be completed on your behalf.
- Finally, the Review Options screen provides a summary of all of the selected options for server promotion. As an added bonus, when clicking View Script button you are provided with the PowerShell script to automate future installations. To click the Next button to continue.
- Should all the prerequisites pass, click the Install button to start the installation.
- After it completes the required tasks and the server restarts, the new Windows Server 2012 R2 Domain Controller setup is completed.
Check New Domain Controller in AD Sites and Services
- Open Active Directory Users and Computers, expand <Your Domain> and click the Domain Controller OU to verify your server is listed.
- Open DNS Manager, right-click on <Your Domain>, select Properties and then click Name Servers Verify that your server is listed in Name Servers: lists.
- Open Active Directory Sites and Services; verify that your server is listed in Servers under Default-First-Site-Name.
Check New Domain Controller in DNS Manager
- Open DNS Manager in new Domain Controller
- Expand Forward Lookup Zone
- Select FQDN of domain> Double Click on Name Server (NS)>Properties>Check New Server in Name Server Tab.
Transfer FSMO Role
Now transfer all the FSMO roles from windows 2008 domain controller to windows 2012 R2 domain controller. Log on to windows 2008 domain controller as enterprise admin. Open command prompt type these command as follows:
connect to server WIN2012R2SERVERNAME
Transfer domain naming master
Transfer Schema Master
Transfer RID master
Transfer infrastructure master
Change DNS Properties of Servers and Workstation
On each server and workstation within the target domain require a NIC properties configuration update to point to the new Domain Controller. Open the DHCP management console, select Option no. 006 and under server scope options and add the IP address of your new Domain Controller as DNS server.
Removing the Windows 2008 R2 domain controller
- On the Windows 2008 R2 server click Start, Click Run, type dcpromo, then click
- After the Welcome to the Active Directory Installation Wizard page, be sure to leave the Delete the domain because this server is the last domain controller in the domain
- On the Administrator Password Page, enter your password and click Next.
- On the Summary page, click Next, wait for the process to end, then click
- On the Completing the Active Directory Domain Services Installation Wizard, click
- On the Active Directory Domain Services Installation Wizard page, click Restart Now to Restart the server.
- After the reboot is completed, delete the Windows Server 2008 R2 server from the domain to a workgroup and remove any unnecessary record from Active Directory Sites and Services.
Note: Wait for all schema object to be cleaned automatically. Do not rush to clean any schema object or DNS record in new Domain Controller.