How do I enroll to get a new certificate?

I did not get an e-mail confirmation containing a token from the enrollment process. What should I do?

I already have a token from the enrollment process for one of my computers. How do I install a second license server on another computer?

How do I check to see when my certificates will expire?

Do I have to enroll again after the Windows Media License Service certificate expires? If so, what is the cost?

Can I automate the enrollment process?

I tried to enroll my license server running Windows Media Rights Manager SDK on http://licenseserver.windowsmedia.com. I get an error: NS_E_DRM_LICENSE_SERVER_INFO_MISSING. What should I do?

How do I update my license server information?

Is there a way to update license server information without connecting to the Internet?

I upgraded from Windows Media Rights Manager 9 SDK to Windows Media Rights Manager 10.1.2 SDK. Do I need to repackage my content?

What is the difference between Cert1 and Cert2?

What is license revocation?

I tried to use the sample package.asp script, but I got the error code Status: 0xC0042918. What does this mean?

I am using the sample package.asp script and I am unable to package a file located on a remote machine. What can I do?

I am still having problems, how to I get support?

When my application calls the GetLicenseToDeliver method to generate a license, I get error 1073469151 (0xC0042921L). What does this mean?

What are drmv2lic.bak, drmv2key.bak, and drmv1lic.bak used for?

What is the difference between individualization for Windows Media Rights Manager SDK and for Windows Media Player?

Resources

--------------------------------------------------------------------------------
top of page
Q. How do I enroll to get a new certificate?

A. As a content provider distributing licenses, you must enroll with the Windows Media License Service and get a certificate and revocation list for each computer that runs Windows Media License Service. Before you enroll, ensure that your license server — the computer from which you will issue licenses, is configured as follows:
The license server must run on a clean installation of Windows? Server 2003.
Internet Information Services (IIS) and Active Server Pages (ASP) must be enabled.
A legacy version of Windows Media Rights Manager is not installed.
The current version of the Windows Media Rights Manager 10.1.2 SDK is installed.
For more information about the requirements to deliver licenses, see http://msdn2.microsoft.com/en-us/library/bb614754.aspx. For additional information regarding Windows Media Rights Manager 10.1.2 SDK setup see http://msdn2.microsoft.com/en-us/library/bb649407.aspx Content providers must obtain a Windows Media License Service certificate periodically because certificates expire after a year.

To get certificates from Microsoft:

Go to the Microsoft Web site http://licenseserver.windowsmedia.com/, click Enroll to get a new certificate, and then follow the instructions to begin the enrollment process. You will receive an e-mail message containing the token that you need to complete the enrollment. The tokens cannot be used more than once. If you are running multiple licensing servers, you must either perform this process separately on each computer or you can share the certificates between multiple computers.
On your computer running Windows Media License Service, go to http://licenseserver.windowsmedia.com/. Click Complete the enrollment with your e-mail confirmation, and then follow the instructions to complete the enrollment.
The enrollment procedure obtains the required certificates required to run Windows Media License Service and also updates the server with the latest configuration data. This configuration data includes the appropriate client keys so that users can interact with the license server and the Windows Media revocation data. After the enrollment process completes you can perform tasks such as packaging your content and issuing DRM licenses. To maintain server functionality, you must enroll at least once a year by accessing the enrollment page from http://licenseserver.windowsmedia.com/registration.asp?v2=true. You must also update the server configuration every week by downloading the latest License Service Information from http://licenseserver.windowsmedia.com/v2revocation.asp. If you do not update the server configuration every week and enroll at least once a year, your License Server will not function. For more information on how Windows Media Rights Manager works with licenses, see http://msdn2.microsoft.com/en-us/library/bb614609.aspx For information about the differences between the Windows Media Rights Manager SDK version 10.1.2 Evaluation Agreement and Windows Media Rights Manager SDK version 10.1.2 Agreement, see http://www.microsoft.com/windows/windowsmedia/licensing/Licensing_DRM_Content.aspx

--------------------------------------------------------------------------------
top of page
Q. I did not get an e-mail confirmation containing a token from the enrollment process. What should I do?

A. If you are enrolling to get the certificate through http://licenseserver.windowsmedia.com, you should receive an automated e-mail containing a token. Due to delays in e-mail gateways it is not possible to predict how long it may take. If you are not receiving the e-mail then:
Try enrolling again from the license server that is running Windows Media Rights Manager SDK by using a different e-mail address.
Confirm that Internet Explorer security settings allow signed ActiveX components.
Confirm that enrollment is done from a Windows Server 2003-based computer that has Windows Media Rights Manager SDK installed.

--------------------------------------------------------------------------------
top of page
Q. I already have a token from the enrollment process for one of my computers. How do I install a second license server on another computer?

A. You can request a new certificate to run Windows Media License Service on the new license server. This will give you a new token. Alternately, you can share the existing certificate and configuration data among multiple computers. For example, if you have a server farm and a test server that share certificates, you can first install the updates on the test server. If successful, you can then export the related registry keys from the test server and import them on the servers in the server farm. For more information, see: http://msdn2.microsoft.com/en-us/library/bb649420.aspx.

--------------------------------------------------------------------------------
top of page
Q. How do I check to see when my certificates will expire?

A. The Windows Media License Service certificates expire periodically and at different times from each other. As a license distributor, you are responsible for monitoring when the certificate expires. The Windows Media Rights Manager SDK documentation provides a sample VBScript, which will tell you the number of days remaining on your certificates. To ensure that your certificates are still valid, you can periodically run this script. For more information, see http://msdn2.microsoft.com/en-us/library/bb614564.aspx.

--------------------------------------------------------------------------------
top of page
Q. Do I have to enroll again after the Windows Media License Service certificate expires? If so, what is the cost?

A. Windows Media License Service certificates expire after a year. Before expiration, you must enroll again to get a new certificate. If you do not, the license server will stop working until it is updated. There is no cost involved to renew an existing certificate.
--------------------------------------------------------------------------------
top of page
Q. Can I automate the enrollment process?

A. At this time, there is no Microsoft-prescribed method of automating the enrollment process. The automation implementation depends on your production environment. For example the automation process can invoke the Task Scheduler and run a script that launches Internet Explorer , navigates to the Windows Media License Service http://licenseserver.windowsmedia.com/, and ends when the enrollment is complete. Microsoft recommends that you run the process in a test environment. If the process is successful, you can export it to the live server farm.

--------------------------------------------------------------------------------
top of page
Q. I tried to enroll my license server running Windows Media Rights Manager SDK on http://licenseserver.windowsmedia.com. I get an error: NS_E_DRM_LICENSE_SERVER_INFO_MISSING. What should I do?

A. The following steps may be followed to resolve your issue.
Verify that registry key values at HKLM\Software\Microsoft\WM Rights Manager exist. If the values do not exist, you should try reinstalling the SDK and then enrolling.
Verify the account used for enrollment has permission to edit the registry key. If the account does not have permissions, change these permissions and then try to enroll again.
If you still cannot enroll, this issue may be resolved by updating license server information as described in the answer below.

--------------------------------------------------------------------------------
top of page
Q. How do I update my license server information?

A. To update your license server:
On the computer that is running Windows Server 2003 and the Windows Media License Service, go to http://licenseserver.windowsmedia.com.
Click Download the latest License Server information to update the registry entries. For more information about these registry settings, see http://msdn2.microsoft.com/en-us/library/bb614656.aspx

--------------------------------------------------------------------------------
top of page
Q. Is there a way to update license server information without connecting to the Internet?

A. At this time, Microsoft does not offer an alternative way to update the license server information without connecting to the Internet at http://licenseserver.windowsmedia.com.

--------------------------------------------------------------------------------
top of page
Q. I upgraded from Windows Media Rights Manager 9 SDK to Windows Media Rights Manager 10.1.2 SDK. Do I need to repackage my content?

A. If you upgrade to Windows Media Rights Manager 10.1.2 SDK your packaged content does not have to be repackaged and does not need to be re-encrypted. Headers for the packaged content do not need to be recreated for license chaining to continue working. Microsoft recommends that you update content headers to contain the current Uplink ID so that Windows Media Rights Manager 10.1.2 SDK clients can send the license state of the chained licenses to the license server. Legacy clients will ignore the new state information. Newer clients will identify the cause of what triggered the license request to the license server. By using the license state information, the license server will send only the license(s) (root, leaf, or both) that the client needs.

--------------------------------------------------------------------------------
top of page
Q. What is the difference between Cert1 and Cert2?

A. Cert1 is used to validate the identity of the license server. Cert2 is the Microsoft Root License certificate, which is the trusted party that makes that validation possible. This is similar to SSL. For example, if Cert1 were a hotmail.com certificate, Cert2 would be the VeriSign root certificate.

--------------------------------------------------------------------------------
top of page
Q. What is License Revocation?

A. License Revocation refers to the process in which the license issuer revokes licenses that have problems. Only the license issuer can revoke licenses. This is not a Microsoft process. Windows Media Rights Manager 10.1.2 SDK provides programming elements that you can use to write an application that revokes licenses. For more information, see http://msdn2.microsoft.com/en-us/library/bb614770.aspx
Note The License Revocation process is not related to your certificates that allow you to run Windows Media License Service. These certificates expire yearly and can be renewed at anytime by enrolling again. The new certificate replaces the old one.

--------------------------------------------------------------------------------
top of page
Q. I tried to use the sample package.asp script, but I got the error code Status: 0xC0042918. What does this mean?

A. The error code 0xC0042918 indicates that the input file is not a Windows Media file. The Windows Media Rights Manager 10.1.2 SDK can only package Windows Media files.

--------------------------------------------------------------------------------
top of page
Q. I am using the sample package.asp script and I am unable to package a file located on a remote machine. What can I do?

A. The package.asp script runs under the IIS credentials. Check your permissions and ensure that the IIS process is allowed to access remote shares and files.

--------------------------------------------------------------------------------
top of page
Q. I am still having problems, how do I get support?

A. Twenty-four-hour support is available at http://www.microsoft.com/support/. If you need support with certificate acquisition or installation, e-mail askdrm@microsoft.com or call 800-936-4900.

--------------------------------------------------------------------------------
top of page
Q. When my application calls the GetLicenseToDeliver method to generate a license, I get error 1073469151 (0xC0042921L). What does this mean?

A. The error 1073469151 (0xC0042921L) is DRM_E_BINDTOPUBKEY_NOT_SET. This indicates the BindToPubKey property was not set before calling this method.

--------------------------------------------------------------------------------
top of page
Q. What are drmv2lic.bak, drmv1key.bak, drmv2key.bak, and drmv1lic.bak used for?

A. These .bak files contain encrypted information about the computer and license data. They are all required for license restoration. Information regarding Microsoft's privacy policies may be found at http://www.microsoft.com/windows/windowsmedia/player/10/privacy.aspx

--------------------------------------------------------------------------------
top of page
Q. What is the difference between individualization for Windows Media Rights Manager SDK and individualization for Windows Media Player?

A. Individualization is a feature that reduces the security risk in a digital rights management (DRM) system by providing security upgrades to DRM components. Windows Media Rights Manager SDK runs on Windows Server 2003 and is designed for developers who want to deliver licenses for digital media, such as songs and videos, over the Internet in a protected and secure manner. For more information about Windows Media Rights Manager SDK, see http://msdn2.microsoft.com/en-us/library/bb649422.aspx. Individualization for the Windows Media Rights Manager SDK updates components on the license issuing end of the DRM system. Individualization for Windows Media Player updates components on the content playback end of the DRM system. Windows Media Player uses DRM technology to preserve the rights of content owners who protect their content. You must have a license in order to play protected content. For more information on DRM technology in Windows Media Player, see http://www.microsoft.com/windows/windowsmedia/mp10/privacy.aspx#MicrosoftDigitalRightsManagement.