DRM Requirements
Other versions of this page are also available for the following:
8/27/2008
This topic describes the support that your application must provide in order to use Microsoft Windows Media Digital Rights Management (WMDRM) for Networked Media Devices.
Server Certificates and Client Certificates
You will need server certificates and client certificates to test WMDRM in your application. These server certificates and client certificates will be provided once your WMDRM agreements are signed and approved.
Persistent Storage for the UDN
UPnP requires every device to use a specific unique device name (UDN) to identify the device. For a networked media device, a UDN is created when the networked media device boots for the first time.
WMDRM-ND requires that the UDN for each device be stored in a persistent registry so that it can be retrieved and used whenever the device is re-started. If there is no persistent registry for the UDN, the UDN will be lost and the device will not be able to validate itself with the WMDRM-enabled media server the next time you try to connect by using the device.
To make the UDN persistent, the hive-based registry must be enabled.
For more information about the hive-based registry, see Using the Hive-Based Registry.
Note
Once a serial number for a device is registered with a media server such as Windows Media Connect (WMC), the device is not allowed to use another serial number. Using a new serial number, or different serial number, with the same device causes the playback of protected content on that device to fail, even if WMC indicates that the device is able to play WMDRM-protected content. This happens because WMC and WMDRM use different ways to judge whether a device is registered.
PlaysForSure Compliance
If you are building a Microsoft PlaysForSure compliant device, you are required to include both WMDRM and a UPnP renderer.
Notes for Platform Builder Users
When you use Microsoft Platform Builder to include the WMDRM component in your device, the necessary UPnP media renderer component is automatically added to your image.
Before you build the image you must manually update your .bib files and your .dat files. A sample .bib file, Fp_nmd.bib, and a sample .dat file, Fp_nmd.dat, are included with the NMD_UI application. You will need to update these files with the specific company filename entry for your server certificates and your client certificates.