You need to recommend changes to the network to ensure that you can deploy the planned Exchange Server 2013 infrastructure.
What should you recommend?
A. Transfer of the FSMO roles to a domain controller in the Chicago office.
B. Change the forest functional level.
C. Change the domain functional level.
D. Change the operating system on one of the domain controllers in the Chicago office
Correct Answer: D
Explanation/Reference:
Explanation:
DIFFICULT QUESTION
FSMO ( Flexible Single Master Operations )
In a forest, there are five FSMO roles that are assigned to one or more domain controllers. The five FSMO roles are:
Schema Master:
The schema master domain controller controls all updates and modifications to the schema. Once the Schema update is complete, it is replicated from the schema master to all other DCs in the directory. To update the schema of a forest, you must have access to the schema master. There can be only one schema master in the whole forest.
Domain naming master:
The domain naming master domain controller controls the addition or removal of domains in the forest. This DC is the only one that can add or remove a domain from the directory. It can also add or remove cross references to domains in external directories. There can be only one domain naming master in the whole forest.
Infrastructure Master:
When an object in one domain is referenced by another object in another domain, it represents the reference by the GUID, the SID (for references to security principals), and the DN of the object being referenced. The infrastructure FSMO role holder is the DC responsible for updating an object’s SID and distinguished name in a cross-domain object reference. At any one time, there can be only one domain controller acting as the infrastructure master in each domain.
Note: The Infrastructure Master (IM) role should be held by a domain controller that is not a Global Catalog server (GC). If the Infrastructure Master runs on a Global Catalog server it will stop updating object information because it does not contain any references to objects that it does not hold. This is because a Global
Catalog server holds a partial replica of every object in the forest. As a result, cross-domain object references in that domain will not be updated and a warning to that effect will be logged on that DC’s event log. If all the domain controllers in a domain also host the global catalog, all the domain controllers have the current data, and it is not important which domain controller holds the infrastructure master role.
Relative ID (RID) Master:
The RID master is responsible for processing RID pool requests from all domain controllers in a particular domain. When a DC creates a security principal object such as a user or group, it attaches a unique Security ID (SID) to the object. This SID consists of a domain SID (the same for all SIDs created in a domain), and a relative ID (RID) that is unique for each security principal SID created in a domain. Each DC in a domain is allocated a pool of RIDs that it is allowed to assign to the security principals it creates. When a DC’s allocated RID pool falls below a threshold, that DC issues a request for additional RIDs to the domain’s RID master. The domain RID master responds to the request by retrieving RIDs from the domain’s unallocated RID pool and assigns them to the pool of the requesting DC. At any one time, there can be only one domain controller acting as the RID master in the domain.
PDC Emulator:
The PDC emulator is necessary to synchronize time in an enterprise.
The PDC emulator of a domain is authoritative for the domain. The PDC emulator at the root of the forest becomes authoritative for the enterprise, and should be configured to gather the time from an external source.
All PDC FSMO role holders follow the hierarchy of domains in the selection of their in-bound time partner.
NOT A
All of the FSMO roles are located on a domain controller in the Baltimore Office. All of the domain controllers are configured as a global catalog server
No need to transfer all of these roles to the chicago domain controller as the question suggests.
NOT B
Apparently no need to change the forest functional level
http://technet.microsoft.com/en-us/library/cc771294.aspx
Forest functional levels enable features across all the domains in your forest. The following table lists the forest functional levels and their corresponding supported domain controllers.
NOT C
Apparently no need to change the domain functional level
http://technet.microsoft.com/en-us/library/cc771294.aspx
For all domain controllers to function accordingly in the domain the domain functional level would have to be set to Windows Server 2003
All domain controllers in the Chicago office run Windows Server 2003 Service Pack 1. (SP1)
All domain controllers in the Los Angeles office run Windows Server 2008 R2.
All domain controllers in the Baltimore office run Windows Server 2012
Domain functional levels
Domain functionality enables features that affect the entire domain and that domain only. The following table lists the domain functional levels and their corresponding supported domain controllers:
D
http://technet.microsoft.com/en-us/library/ff728623(v=exchg.150).aspx
Mixture of exchange 2007,2010 and 2013 environment
Exchange 2007/2010/2013 can operate in a Windows Server 2003/2008/2012 domain functional level Exchange 2007/2010/2013 can operate in a Windows Server 2003/2008/2012 forest functional level However to operate appropriately the min spec for Exchange 2013 is for an AD environment of Server 2003 SP2
Currently all of the chicago domain controllers are 2003 SP1
Need to upgrade a chicago domain controller which will house Exchange 2013
Exchange 2013 System Requirements: Exchange 2013 Help
Explanation/Reference:
Explanation:
DIFFICULT QUESTION
FSMO ( Flexible Single Master Operations )
In a forest, there are five FSMO roles that are assigned to one or more domain controllers. The five FSMO roles are:
Schema Master:
The schema master domain controller controls all updates and modifications to the schema. Once the Schema update is complete, it is replicated from the schema master to all other DCs in the directory. To update the schema of a forest, you must have access to the schema master. There can be only one schema master in the whole forest.
Domain naming master:
The domain naming master domain controller controls the addition or removal of domains in the forest. This DC is the only one that can add or remove a domain from the directory. It can also add or remove cross references to domains in external directories. There can be only one domain naming master in the whole forest.
Infrastructure Master:
When an object in one domain is referenced by another object in another domain, it represents the reference by the GUID, the SID (for references to security principals), and the DN of the object being referenced. The infrastructure FSMO role holder is the DC responsible for updating an object’s SID and distinguished name in a cross-domain object reference. At any one time, there can be only one domain controller acting as the infrastructure master in each domain.
Note: The Infrastructure Master (IM) role should be held by a domain controller that is not a Global Catalog server (GC). If the Infrastructure Master runs on a Global Catalog server it will stop updating object information because it does not contain any references to objects that it does not hold. This is because a Global
Catalog server holds a partial replica of every object in the forest. As a result, cross-domain object references in that domain will not be updated and a warning to that effect will be logged on that DC’s event log. If all the domain controllers in a domain also host the global catalog, all the domain controllers have the current data, and it is not important which domain controller holds the infrastructure master role.
Relative ID (RID) Master:
The RID master is responsible for processing RID pool requests from all domain controllers in a particular domain. When a DC creates a security principal object such as a user or group, it attaches a unique Security ID (SID) to the object. This SID consists of a domain SID (the same for all SIDs created in a domain), and a relative ID (RID) that is unique for each security principal SID created in a domain. Each DC in a domain is allocated a pool of RIDs that it is allowed to assign to the security principals it creates. When a DC’s allocated RID pool falls below a threshold, that DC issues a request for additional RIDs to the domain’s RID master. The domain RID master responds to the request by retrieving RIDs from the domain’s unallocated RID pool and assigns them to the pool of the requesting DC. At any one time, there can be only one domain controller acting as the RID master in the domain.
PDC Emulator:
The PDC emulator is necessary to synchronize time in an enterprise.
The PDC emulator of a domain is authoritative for the domain. The PDC emulator at the root of the forest becomes authoritative for the enterprise, and should be configured to gather the time from an external source.
All PDC FSMO role holders follow the hierarchy of domains in the selection of their in-bound time partner.
NOT A
All of the FSMO roles are located on a domain controller in the Baltimore Office. All of the domain controllers are configured as a global catalog server
No need to transfer all of these roles to the chicago domain controller as the question suggests.
NOT B
Apparently no need to change the forest functional level
http://technet.microsoft.com/en-us/library/cc771294.aspx
Forest functional levels enable features across all the domains in your forest. The following table lists the forest functional levels and their corresponding supported domain controllers.
NOT C
Apparently no need to change the domain functional level
http://technet.microsoft.com/en-us/library/cc771294.aspx
For all domain controllers to function accordingly in the domain the domain functional level would have to be set to Windows Server 2003
All domain controllers in the Chicago office run Windows Server 2003 Service Pack 1. (SP1)
All domain controllers in the Los Angeles office run Windows Server 2008 R2.
All domain controllers in the Baltimore office run Windows Server 2012
Domain functional levels
Domain functionality enables features that affect the entire domain and that domain only. The following table lists the domain functional levels and their corresponding supported domain controllers:
D
http://technet.microsoft.com/en-us/library/ff728623(v=exchg.150).aspx
Mixture of exchange 2007,2010 and 2013 environment
Exchange 2007/2010/2013 can operate in a Windows Server 2003/2008/2012 domain functional level Exchange 2007/2010/2013 can operate in a Windows Server 2003/2008/2012 forest functional level However to operate appropriately the min spec for Exchange 2013 is for an AD environment of Server 2003 SP2
Currently all of the chicago domain controllers are 2003 SP1
Need to upgrade a chicago domain controller which will house Exchange 2013
Exchange 2013 System Requirements: Exchange 2013 Help
