Because there still is a huge lack of documentation about Microsoft AD RMS, here some hints and tricks to use!
- First thing: irmcheck! Go use it!
- Always check ntsf acl permissions on the server side files asmx-files.
- ConnectionString for SQL is located in registry
- MSIPC (RMS client 2.0 in windows 8 and office 2013) caches in registry and %localappdata%
- REGISTRY:\Software\Classes\Local Settings\Software\Microsoft\MSIPC\<Server Name> \Template (HKCU or HKLM)
Hint: you can delete huge file names with “rmdir MSIPC /s” in cmd (for some reason it doesn’t work in powershell)
- Advanced troubleshooting on OSI Layer 7: fiddler! (enable https decryption) Really, put it in between! You’ll get some far more usefull error messages then “cannot connect to the server”, or “cannot use this feature without credentials”…
Even better, go Wireshark (note: ssl mitm here…)!
- The older MSDRM (RMS Client 1) puts everything in your %localappdata%\Microsoft\DRM . There you can find your user- & machine certificates, and templates.
Regkeys under REGISTRY:\software\microsoft\msdrm
- always check the IIS certificates! If there’s something wrong, nothing will ever work!
Please, open them up, they’re just XML-based, and contain a lot of information! For example, in the GIC-file you can confirm your RMS-location. Don’t bother trying to modify them, they’re hashed… But you definitely should check them for having :443 in their url’s (check this article)
GIC (Group Identity Certificate) = RAC (Rights Account Certificate)
CLC (Client Licensor Certificate)
CERT-Machine = SPC (Security Processor Certificate)
More about those 3 files in here
- When you need to go deeper, use debugview (or something new: Trace Spy). This works for bot MSDRM and MSIPC
Server-side and Client-side
- Go and check Windows Event Logs. RMS Client doesn’t actually logs something there, but it can be a source of good information anyway!