Creating and Deploying Active Directory Rights Management Services Rights Policy Templates Step-by-Step Guide

About this Guide

This step-by-step guide walks you through the process of creating and deploying Active Directory Rights Management Services (AD RMS) policy templates in a test environment. During this process you create a rights policy template, deploy this template to a client computer running Windows Vista® and Microsoft® Office Word 2007, and verify that the client computer can rights-protect a document by using the newly-created rights policy template.

Once complete, you can use the test lab environment to assess how AD RMS rights policy templates can be created with Windows Server® 2008 and deployed within your organization.

As you complete the steps in this guide, you will:

• Create an AD RMS rights policy template.

• Deploy the rights policy template.

• Verify AD RMS functionality after you complete the configuration.

The goal of an AD RMS deployment is to be able to protect information, no matter where it is moved. Once AD RMS protection is added to a digital file, the protection stays with the file. By default, only the content owner is able to remove the protection from the file. The owner can grant rights to other users to perform actions on the content, such as the ability to view, copy, or print the file.

What This Guide Does Not Provide

This guide does not provide the following:

• This guide assumes that AD RMS is already configured for a test environment. For more information about configuring AD RMS, see Windows Server Active Directory Rights Management Services Step-by-Step Guide.

• Complete technical reference for AD RMS or deploying AD RMS templates within your organization. In a large organization, Systems Management Server (SMS) or Group Policy can provide a way to deploy AD RMS rights policy templates to several workstations at a time.

Deploying AD RMS in a Test Environment

We recommend that you first use the steps provided in this guide in a test lab environment. Step-by-step guides are not necessarily meant to be used to deploy Microsoft products without accompanying documentation and should be used with discretion as a stand-alone document. Before you start the steps in this guide, you will need to use the steps provided in Windows Server Active Directory Rights Management Services Step-by-Step Guide also in a lab environment. That guide prepares the basic infrastructure for an AD RMS deployment, with an AD RMS cluster, AD RMS Logging database, and domain controller. This step-by-step guide builds on the previous guide, so it is important to complete it before starting this one. On completion of this step-by-step guide, you will have a working AD RMS rights policy template. You can then test and verify AD RMS rights policy template functionality through the simple task of restricting permissions on a Microsoft Office Word 2007 document with the rights policy template created in this guide.

The test environment described in this guide includes three computers connected to a private network and using the following operating systems, applications, and services:

Computer Name	Operating System	Applications and Services
ADRMS-SRV	Windows Server 2008	AD RMS, Internet Information Services (IIS) 7.0, World Wide Web Publishing Service, Message Queuing (also known as MSMQ), and Windows Internal Database
CPANDL-DC	Windows Server 2003 with Service Pack 1 (SP1)	Active Directory®, Domain Name System (DNS)
ADRMS-DB	Windows Server 2003 with SP1	Microsoft SQL Server™ 2005 Standard Edition
ADRMS-CLNT	Windows Vista	Microsoft Office Word 2007 Enterprise Edition

The computers form a private intranet and are connected through a common hub or Layer 2 switch. This configuration can be emulated in a virtual server environment if desired. This step-by-step exercise uses private addresses throughout the test lab configuration. The private network ID 10.0.0.0/24 is used for the intranet. The domain controller is named CPANDL-DC for the domain named cpandl.com.

The following figure shows the configuration of the test environment:

Read more »

Document Policy from Windows

This document supports a preliminary release of a software product that may be changed substantially prior to final commercial release, and is the confidential and proprietary information of Microsoft Corporation. It is disclosed pursuant to a non-disclosure agreement between the recipient and Microsoft. This document is provided for informational purposes only and Microsoft makes no warranties, either express or implied, in this document. Information in this document, including URL and other Internet Web site references, is subject to change without notice. The entire risk of the use or the results from the use of this document remains with the user. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.

© 2008 Microsoft Corporation. All rights reserved.

Active Directory, Microsoft, MS-DOS, Vista, Windows, Windows NT, and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

All other trademarks are property of their respective owners.

Read more »

Creating and Deploying Active Directory Rights Management Services Templates Step-by-Step Guide

Creating and Deploying Active Directory Rights Management Services Templates Step-by-Step Guide

Microsoft Corporation

Published: January 2008

Author: Brian Lich

Editor: Carolyn Eller

Abstract

This step-by-step guide provides instructions for setting up a test environment for creating and deploying Active Directory Rights Management Services (AD RMS) rights policy templates on the Windows Server® 2008 operating system.

Read more »

Sanket and Swapnil Barot

Read more »

Viruses

A virus is a program that gets on your hard drive and deletes programs. One will also lock up files. Some will delete your passwords. Every virus does something different. Some viruses have weird names such as groovier, Jack the Ripper and tequila. The way the viruses are made is through programming computer programs such as COBOL, basic, c, and, Java. You should be careful when you download something from the Internet because it may have a virus. Opening E-mail can also transfer viruses. You should have an antivirus program on your computer. One example of a network antivirus program is LANDesk. Two of the more popular personal programs are McAfee and Norton. One bad virus is Sunday-1 On Sundays; the virus displays the following message:

"Today is Sunday! Why do you work so hard?

All work and no play make you a dull boy!

Come on! Let's go out and have some fun!"

The virus increases infected files by 1636 bytes.

Another example of a virus is Friday The 13^th On Friday the 13th, Jerusalem loads into memory for 30 minutes, after which it deletes any file the user attempts to execute. On other days, Jerusalem slows down the computer system 30 minutes after each infection. It also wipes out an area of the screen, usually called the "black window," or "black box." A bug in the virus can cause .EXE files to be infected repeatedly until they become too large to execute.

So take care of your computer and always have a virus protection program. Always be careful when you open a floppy disk because it might have a virus. When you download anything from the internet always scan

- JMD Computer

Read more »