Asia provides infrastructure as a service which essentially is virtualization in the cloud.
All the considerations for virtualization applications and servers in an on premises infrastructure
apply to deploying the same applications and servers in Asia I'm deploying 80 days on Asia I guess you
are installing the domain controller on a virtual machine.
So all the rules that are applied to virtualize and domain controller apply to deploying ADT s in Asia.
You can install 80 days on Asia virtual machines to support a variety of scenarios.
Let's list these scenarios.
The first scenario is disaster recovery in a scenario in which you're on premises.
Domain Controllers are destroyed or are otherwise unavailable.
Asia based which really chill machines that are running as a replica domain controllers will have a
complete copy of your edit is data base.
This can help speed recovery and as a low cost alternative for organizations that do not have a physical
disaster recovery site.
The next scenario is due or distributed domain controllers if your organization is highly decentralized
Asia based virtual machines that are running as a replica domain controllers can provide lower latency
connections for improved authentication performance you can achieve this by running domain controllers
in different Asia regions that correspond to the locations where it is not cost effective for your organization
to deploy physical infrastructure and others to mirror is user authentication for isolated applications.
If you need to deploy an application with an aide it is dependency but that application does not require
connectivity with the organizational aided devious environment.
You could deploy a separate forest on Asia with ritual machines also on premises member servers and
clans can communicate with Asia based domain controllers.
These domains controllers should never be the only domain controllers in a hybrid environment.
Lots of connectivity between an on premises environment and Asia prevents authentication and other domain
functions.
If you are not also running a tedious services in your on premises environment when you implement it
it is in Asia.
Consider the following.
You should consider network topology to meet 80 days is requirements.
You must create an Asia virtual network and attach your virtual machines to it.
If you intend to join an existing on premises 8 it is infrastructure.
You can opt to extend network connectivity to your on premises environment.
You can achieve this through a standard virtual private network connection or an Asia express route
circuit.
Depending on the speed or reliability and security that your organization requires.
Please note that an express road circuit is a method of connecting and on premises infrastructure to
Microsoft cloud services through a dedicated connectivity provider that does not use the public internet.
Another consideration is site topology as well as a physical side.
You should define and configure and edit the site that corresponds to the IP address space of your Asia
virtual network.
Because the use of an easier virtual network in cures additional gateways costs for all outbound traffic
to your on premises environment you should carefully plan your ADT at sites and site links to minimize
cost because ADT a site link transit Tivoli is enabled by default.
You should consider disabling the option to breach all site links if you have more than two sides.
If you leave site link by region enabled it it is assumed that all sides in your deployment have direct
connectivity with one another which might result in your Asia ADT a site having multiple replication
partners ensure that you do not enable change notification on site links that contain your Asia aided
in site.
This is because this will override any replication into walls that are configured on the site link resulting
in frequent and often unnecessary replication.
If a writer will copy of ADT s is not necessary you should consider deploying a read only domain controller
to further limit the amount of outbound traffic that aided the application creates.
We'll talk about sites a DDA sites and site links and replication in more detail in later lessons.
But now to another consideration when planning interacting with Asia it is service healing.
Also Asia does not provide rollback services directly to customers.
Asia servers might roll back as regular part of maintenance when recovering from a service failure.
Domain Controller replication depends on the update sequence number or USN run on aided system rolls
back.
Duplicate us can be created to prevent this.
Windows Server 2012 ADT has introduced a new identifier named the AMD generation I.D. VM generation
80 can detect a rollback and prevent a ritualized domain controller from replicating changes outbound
until the virtualize 80 days has converged with the other domain controllers in the domain.
Please know that Asia virtual machines that are run in the domain controller role should always be shut
down through the guest operating system and never through the Asia portal.
Initialize and a shutdown through the Asia portal.
D allocates the virtual machine causing the result of the VM generation I.D. identifier and we have
three more considerations IP address and all lazier virtual machines to receive DCP addresses by default.
But you can configure with static addresses through Asia power shell that will persist across restarts
or shutdowns and service heal in Asia virtual machines that are to host a domain controller role a DNS
rule or both should have the initial dynamic IP address configured as static.
By using the set Asia is static in our IP command land so that that IP never deal kids is a virtual
machine shot down.
You must first provision provision the easy or virtual network before your provision the H or Asia based
domain controllers.
Another consideration is DNS.
Asia was built in DNS does not meet the requirement of ADT as such as dynamic DNS and service resource
records or other as a real records before you can extend your on premises aided its environment to an
Asia where actual machine you must provision and configure the Asia ritual network to an on parameters
DNS server.
And the last consideration is disks.
Asia virtual machines use read write host cache and for operating system virtual hard disk.
Although this can improve virtual machine performance if it s components are installed on the operating
system disk data loss is possible in the end.
In the event of a disk failure.
Please remember that cache and can be turned off in additional Asia disk that are attached to a virtual
machine.
When you install active directory in Asia you should put the entity has the deed file and since file
folders on an additional data disk on the Asia virtual machine with the host cache reference set and
configure to mom.
However keep in mind that Asia of data disks are constrained to a maximum size of one terabyte.