You need to ensure that you can access the contents of the mounted snapshot

Your network contains an Active Directory domain named contoso.com. The domain
contains a domain controller named DC1.
You run ntdsutil as shown in the exhibit. (Click the Exhibit button.)

You need to ensure that you can access the contents of the mounted snapshot.
What should you do?

Your network contains an Active Directory domain named contoso.com. The domain
contains a domain controller named DC1.
You run ntdsutil as shown in the exhibit. (Click the Exhibit button.)

You need to ensure that you can access the contents of the mounted snapshot.
What should you do?

A.
From a command prompt, run dsamain.exe -dbpath
c:\$snap_201204131056_volumec$\windows\ntds\ntds.dit -Idapport 33389.

B.
From the snapshot context of ntdsutil, run mount {79f94f82-5926-4f44-8af0-
2f56d827a57d>.

C.
From the snapshot context of ntdsutil, run activate instance “NTDS”.

D.
From a command prompt, run dsamain.exe -dbpath
c:\$snap_201204131056_volumec$\windows\ntds\ntds.dit -Idapport 389.

Explanation:
A) Custom port needs to be defined when mounting to allow access from ADUC
B) 389 is used as the standard ldap port
C) Run prior to mount and after the mount run dsamain Sets NTDS or a specific AD LDS
instance as the active instance.
D) mounts a specific snap shot as specified by guid, using the snapshot mounted you needs
to run dsamain to start an instance of AD
http://technet.microsoft.com/en-us/library/cc753609(v=ws.10).aspx



Leave a Reply 2

Your email address will not be published. Required fields are marked *


Mitchell

Mitchell

Answer is A. You need to mount the snap on a port that does not clash with AD running on the server so 33389 will do meaning D is wrong. B and C are bogus.