You have an Active Directory Rights Management Services (AD RMS) server named RMS1.
Multiple documents are protected by using RMS1.
RMS1 fails and cannot be recovered.
You install the AD RMS server role on a new server named RMS2.
You restore the AD RMS database from RMS1 to RMS2.
Users report that they fail to open the protected documents and to protect new documents.
You need to ensure that the users can access the protected content.
What should you do?
A.
From Active Directory Rights Management, update the Service Connection Point (SCP) for RMS1.
B.
From DNS, create an alias (CNAME) record for RMS2.
C.
From DNS, modify the service location (SRV) record for RMS1.
D.
From RMS2, register a service principal name (SPN) in Active Directory.
Answer is B
4
11
For me the Answer is B
0
5
i don’t understand why the answer is not B
1
3
This took some investigating (who actually uses RMS?) but I’m inclined to agree with the others and pick B.
Mostly based on this page:
https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/ff660011(v%3dws.10)
To quote the important part:
CNAME records are important for several reasons. First, when you create a piece of content, the URL for the AD RMS server is embedded into the header of it. When a user attempts to consume this content, it is this URL that is used to obtain a use license. If you originally installed AD RMS using the FQDN of the physical AD RMS server as the URL and this were to ever change, documents with the old URL would be inaccessible.
For example, if we have an AD-RMS server with an FQDN of AD-RMS.fabrikam.com and we use a URL of https://AD-RMS.fabrikam.com, then all of our content will have https://AD-RMS.fabrikam.com embedded in the header of all rights protected content. Now say we decide to change the AD RMS servers name to AD-RMS2.fabrikam.com and our URL is now https://AD-RMS2.fabrikam.com. Now when a user attempts to consume older rights-protected content, they will look for a use license at https://AD-RMS.fabrikam.com, not our new URL of https://AD-RMS2.fabrikam.com. They will not be able to consume this content. Now suppose instead we had created a CNAME record called RMS. We can point this record at AD-RMS.fabrikam.com. This record will have an FQDN RMS.fabrikam.com. When we install AD RMS, we will specify https://RMS.fabrikam.com as the URL. So now if we decide to change the AD RMS servers name to AD-RMS2.fabrikam.com we can simply edit the CNAME record to point to AD-RMS2.fabrikam.com.
11
4
its all about DNS settings… because the db is in the new RMS server.
0
4