70-695 · Question #56
Your network contains one Active Directory forest named contoso.com that has two sites named Site1 and Site2. The contoso.com domain contains two servers named Server1 and Server2 that run Windows…
The correct answer is A. Bootstrap.ini. To ensure clients connecting to Server2's MDT deployment share are deployed from Server2 instead of Server1, the Bootstrap.ini file on Server2 must be modified.
Question
Your network contains one Active Directory forest named contoso.com that has two sites named Site1 and Site2. The contoso.com domain contains two servers named Server1 and Server2 that run Windows Server 2012 R2. The Microsoft Deployment Toolkit (MDT) is installed on both of the servers. Server1 is located in Site1 and Server2 is located in Site2. You perform the following actions on Server1:
- Import an operating system.
- Import drivers.
- Create a task sequence.
You copy the deployment share from Server1 to Server2 and you open the share on Server2 as MDTShare2. You discover that clients that connect to MDTShare2 are deployed from Server1. You need to ensure that the clients that connect to MDTShare2 are deployed from Server2. What should you modify on Server2?
Options
- ABootstrap.ini
- BCustomsettings.ini
- CThe Rules properties of MDTShare2
- Dthe General properties of MDTShare2
How the community answered
(53 responses)- A91% (48)
- B2% (1)
- C2% (1)
- D6% (3)
Why each option
To ensure clients connecting to Server2's MDT deployment share are deployed from Server2 instead of Server1, the Bootstrap.ini file on Server2 must be modified.
The Bootstrap.ini file contains the DeployRoot variable, which specifies the initial network path to the deployment share that MDT clients connect to. When the deployment share is copied from Server1 to Server2, the Bootstrap.ini on Server2 will still point to Server1. Modifying the DeployRoot in Server2's Bootstrap.ini to reflect Server2's share path and then regenerating boot images on Server2 will direct clients to the correct server for deployment.
Customsettings.ini controls task sequence logic and variable assignments during deployment but does not define the initial connection path for the client boot media.
Modifying the Rules properties of MDTShare2 would update the Customsettings.ini file, which is processed after the initial connection and thus would not resolve the issue of clients connecting to the wrong deployment share.
The General properties of MDTShare2 configure overall share settings, such as description or folder paths, but do not contain the DeployRoot variable used by clients for the initial deployment share connection.
Concept tested: MDT Bootstrap.ini configuration and DeployRoot
Source: https://learn.microsoft.com/en-us/windows/deployment/deploy-windows-mdt/reference-for-mdt-settings#deployroot
Topics
Community Discussion
No community discussion yet for this question.