Tuesday, 30 November 2010

Real Admin Tips

01. After using 'Telnet' command to check server reponse, it's sometimes a pain to completly get out of the telnet terminal. I found a short cut key combination to quit from Telnet.

Use 'Ctrl plus [' key combination to exit from telnet and enter 'quit' or 'q' to get back to the pervious command lines.

Posted by: Khaleel M Ismail

02. .In order to run 'Restore' wizard in case of Computer Crash or failiure, you can reboot the computer and restart the computer by pressing 'F8' to go to advanced options. Select 'Safe Mode with Command prompt' option.
Once computer started on safe mode with command window open, enter the command as
C:\windows\system32\rstrui.exe to run 'Restore' wizard from command prompt.

Posted by: Khaleel M Ismail
Posted by at No comments:

AD LDS Getting Started Step-by-Step Guide

Updated: September 7, 2007
Applies To: Windows Server 2008
Active Directory® Lightweight Directory Services (AD LDS), formerly known as Active Directory Application Mode (ADAM), is a Lightweight Directory Access Protocol (LDAP) directory service that provides data storage and retrieval support for directory-enabled applications, without the dependencies that are required for the Active Directory Domain Services (AD DS). You can run multiple instances of AD LDS concurrently on a single computer, with an independently managed schema for each AD LDS instance.
For additional information about AD LDS, see Active Directory Lightweight Directory Services Overview (http://go.microsoft.com/fwlink/?LinkId=96084).
For more information about configuring ADAM, see Step-by-Step Guide to Deploying ADAM (http://go.microsoft.com/fwlink/?LinkId=96083).
noteNote
If you install security update 951746 on your Windows Server 2008 R2–based and Windows Server 2008–based computers, the Domain Name System (DNS) server’s method of port allocation changes, and this change might prevent AD LDS from obtaining the port that it requires to function correctly. For more information, see article 959215 in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkId=157712).

About this guide

This guide describes the processes for setting up AD LDS and getting it running. You can use the procedures in this guide to install AD LDS on servers that are running the Windows Server® 2008 operating system in a small test lab environment.
As you complete the steps in this guide, you will be able to:
  • Install the AD LDS server role and practice working with AD LDS instances.
  • Practice using AD LDS administration tools.
  • Practice creating and managing organizational units (OUs), groups, and users in AD LDS.
  • Practice creating and deleting AD LDS application directory partitions.
  • View, grant, and deny AD LDS user permissions.
  • Practice binding to an AD LDS instance in several ways.
  • Practice managing AD LDS configuration sets.
noteNote
To maximize your chances of successfully completing the objectives of this guide, it is important that you follow the steps in this guide in the order in which they are presented.

Requirements

Before you start using the procedures in this guide, do the following regarding your system requirements:
  • Have available at least one test computer on which you can install AD LDS. For the purposes of following the exercises in this guide, install AD LDS on computers running Windows Server 2008.
  • Log on to Windows Server 2008 with an administrator account.
  • For the purposes of this guide, you can install replica AD LDS instances on your first test computer or you can install them on a second computer, if you have a second computer available.

Steps for getting started with AD LDS

The following sections provide step-by-step instructions for setting up AD LDS. These sections provide both graphical user interface (GUI) and command-line methods for backing up and restoring AD LDS, where applicable.
Source: http://technet.microsoft.com/en-us/library/cc770639%28WS.10%29.aspx
Posted by at No comments:

Friday, 26 November 2010

All About AD RMS - Step By Step

About This Guide

This step-by-step walks you through the process of setting up a working Active Directory Rights Management Services (AD RMS) infrastructure in a test environment. During this process you create an Active Directory® domain, install a database server, install the AD RMS server role, configure the AD RMS cluster, and configure the AD RMS-enabled client computer.
Once complete, you can use the test lab environment to learn about AD RMS technology on Windows Server® 2008 and assess how it might be deployed in your organization.
As you complete the steps in this guide, you will:
  • Prepare the AD RMS infrastructure.
  • Install and configure AD RMS.
  • 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 goes. 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 grants rights to other users to perform actions on the content, such as the ability to view, copy, or print the file. For more information about the business reasons behind an AD RMS deployment, see the white paper "Windows Rights Management Services: Helping Organizations Safeguard Digital Information from Unauthorized Use" (http://go.microsoft.com/fwlink/?LinkId=64636).
noteNote
This guide is considered the basic AD RMS step-by-step guide. All other step-by-step guides developed for AD RMS will assume that this guide has been completed first.

What This Guide Does Not Provide

This guide does not provide the following:
  • An overview of AD RMS. For more information about the advantages that AD RMS can bring to your organization, see http://go.microsoft.com/fwlink/?LinkId=84726.
  • Guidance for setting up and configuring AD RMS in a production environment
  • Complete technical reference for AD RMS

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 Windows Server features without additional deployment documentation and should be used with discretion as a stand-alone document.
Upon completion of this step-by-step guide, you will have a working AD RMS infrastructure. You can then test and verify AD RMS functionality as follows:
  • Restrict permissions on a Microsoft Office Word 2007 document
  • Have an authorized user open and work with the document.
  • Have an unauthorized user attempt to open and work with the document.
The test environment described in this guide includes four 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, and Message Queuing
CPANDL-DC
 Windows Server 2008 or Windows Server 2003 with Service Pack 2 (SP2)
noteNote
Service Pack 2 for Windows Server 2003 is not required but will be used for the purposes of this guide.

Active Directory, Domain Name System (DNS)
ADRMS-DB
 Windows Server 2003 with SP2
noteNote
Service Pack 2 for Windows Server 2003 is not required but will be used for the purposes of this guide.

Microsoft SQL Server® 2005 Standard Edition with Service Pack 2 (SP2)
noteNote
Service Pack 2 for SQL Server 2005 Standard Edition is not required but will be used for the purposes of this guide.

ADRMS-CLNT
 Windows Vista®
 Microsoft Office Word 2007 Enterprise Edition
noteNote
For more information about the system requirements for installing AD RMS, see http://go.microsoft.com/fwlink/?LinkId=84733.

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:
Art Image 
 
 

Step 1: Setting up the Infrastructure

Applies To: Windows Server 2008
To prepare your AD RMS test environment in the CPANDL domain, you must complete the following tasks:
Use the following table as a reference when setting up the appropriate computer names, operating systems, and network settings that are required to complete the steps in this guide.
ImportantImportant
Before you configure your computers with static Internet Protocol (IP) addresses, we recommend that you first complete Windows product activation while each of your computers still has Internet connectivity. You should also install any available critical security updates from Windows Update (http://go.microsoft.com/fwlink/?LinkID=47370).

 

Computer name Operating system requirement IP settings DNS settings
CPANDL-DC
 Windows Server 2003 with Service Pack 2 (SP2) or Windows Server® 2008
 IP address:
10.0.0.1
Subnet mask:
255.255.255.0
 Configured by DNS server role.
ADRMS-SRV
 Windows Server 2008
IP address:
10.0.0.2
Subnet mask:
255.255.255.0
 Preferred:
10.0.0.1
ADRMS-DB
 Windows Server 2003 with SP2
 IP address:
10.0.0.3
Subnet mask:
255.255.255.0
 Preferred:
10.0.0.1
ADRMS-CLNT
 Windows Vista
IP address
10.0.0.4
Subnet mask:
255.255.255.0
 Preferred:
10.0.0.1

Configure the domain controller (CPANDL-DC)

Depending on your environment, you may evaluate AD RMS in Windows Server 2008 or Windows Server 2003 domain. Use the appropriate section to configure the domain controller, depending on the type of domain to be used, and then configure user accounts and groups.

Configure a Windows Server 2003–based domain controller

To configure the domain controller CPANDL-DC using Windows Server 2003, you must:
  • Install Windows Server 2003 with SP2.
  • Configure TCP/IP properties.
  • Install Active Directory.
  • Raise the Active Directory domain functional level to Windows Server 2003.
  • Create user accounts.
  • Create groups for the user accounts.
For each user account and group that you configure with AD RMS, you need to add an e-mail address and then assign the users to groups.
First, install Windows Server 2003 with SP2 on a stand-alone server.

To install Windows Server 2003 Standard Edition

  1. Start your computer by using the Windows Server 2003 product CD. (You can use any edition of Windows Server 2003 except the Web Edition to establish the domain.)
  2. Follow the instructions that appear on your computer screen, and when prompted for a computer name, type CPANDL-DC.
Next, configure TCP/IP properties so that CPANDL-DC has a static IP address of 10.0.0.1. In addition, configure 10.0.0.1 as the IP address for the DNS server.

To configure TCP/IP properties on CPANDL-DC

  1. Log on to CPANDL-DC as a member of the local Administrators group.
  2. Click Start, point to Control Panel, point to Network Connections, click Local Area Connection, and then click Properties.
  3. On the General tab, click Internet Protocol (TCP/IP), and then click Properties.
  4. Click the Use the following IP address option. In the IP address box, type 10.0.0.1. In the Subnet mask box, type 255.255.255.0.
  5. Click OK, and then click Close to close the Local Area Connection Properties dialog box.
Next, configure the computer as a domain controller.

To configure CPANDL-DC as a domain controller

  1. Click Start, and then click Run. In the Open box, type dcpromo, and then click OK.
  2. On the Welcome page of the Active Directory Installation Wizard, click Next.
  3. Click the Domain controller for a new domain option, and then click Next.
  4. Click the Domain in a new forest option, and then click Next.
  5. Click the No, just install and configure DNS on this computer option, and then click Next.
  6. In the Full DNS name for new domain box, type cpandl.com, and then click Next.
  7. In the Domain NetBIOS name box, type CPANDL, and then click Next three times.
  8. Select the Permissions compatible only with Windows 2000 or Windows Server 2003 operating systems option, and then click Next.
  9. In the Restore Mode Password and Confirm password boxes, type a strong password. Click Next.
  10. Click Next again.
  11. When the Active Directory Installation Wizard is done, click Finish.
  12. Click Restart Now.
noteNote
You must restart the computer after you complete this procedure.

Next, you must raise the domain functional level to Windows Server 2003 so that Active Directory Universal groups can be used.

To raise the domain functional level to Windows Server 2003

  1. Log on to CPANDL-DC with the CPANDL\Administrator account.
  2. Click Start, point to Administrative Tools, and then click Active Directory Users and Computers.
  3. Right-click cpandl.com, and then click Raise domain functional level.
  4. In the list under Select an available domain functional level, click Windows Server 2003, and then click Raise.
  5. Click OK to confirm the selection.
    noteNote
    You cannot change the domain functional level once you have raised it.

  6. Close the Active Directory Users and Computers console.

Configure a Windows Server 2008–based domain controller

To configure the domain controller CPANDL-DC using Windows Server 2008, you must:
  • Install Windows Server 2008.
  • Configure TCP/IP properties.
  • Install Active Directory Domain Services (AD DS).
First, install Windows Server 2008 on a stand-alone server.

To install Windows Server 2008

  1. Start your computer by using the Windows Server 2008 product CD.
  2. When prompted for a computer name, type CPANDL-DC.
  3. Follow the rest of the instructions that appear on your screen to finish the installation.
Next, configure TCP/IP properties so that CPANDL-DB has a IPv4 static IP address of 10.0.0.1 and a IPv6 static IP address of FEC0:0:0:1::.

To configure TCP/IP properties

  1. Log on to CPANDL-DC with the CPANDL-DC\Administrator account.
  2. Click Start, click Control Panel, click Network and Internet, click Network and Sharing Center, click Manage Network Connections, right-click Local Area Connection, and then click Properties.
  3. On the Networking tab, click Internet Protocol Version 4 (TCP/IPv4), and then click Properties.
  4. Click the Use the following IP address option. In the IP address box, type 10.0.0.1. In the Subnet mask box, type 255.255.255.0, and then click OK.
  5. On the Networking tab, clear the Internet Protocol Version 6 (TCP/IPv6) check box, and then click OK.
  6. Click OK to close the Local Area Connection Properties dialog box.
Next, configure the computer as a domain controller using Windows Server 2008.

To configure CPANDL-DC as a domain controller using Windows Server 2008

  1. Click Start, and then click Run. In the Open box, type dcpromo, and then click OK.
  2. On the Welcome to the Active Directory Domain Services Installation Wizard page, click Next.
  3. Click the Domain controller for a new domain option, and then click Next.
  4. Click the Create a new domain in anew forest option, and then click Next.
  5. In the FQDN of the forest root domain box, type cpandl.com, and then click Next.
  6. In the Forest functional level box, select Windows Server 2003, and then click Next.
  7. In the Domain functional level box, select Windows Server 2003, and then click Next.
  8. Ensure that the DNS server check box is selected, and then click Next.
  9. Click Yes, confirming that you want to create a delegation for this DNS server.
  10. On the Location for Database, Log Files, and SYSVOL page, click Next.
  11. In the Password and Confirm password boxes, type a strong password, and then click Next.
  12. On the Summary page, click Next to start the installation.
  13. When the installation is complete, click Finish, and then click Restart Now.
noteNote
You must restart the computer after you complete this procedure.

Configure user accounts and groups

In this section you create the user accounts and groups in the CPANDL domain.
First, add the user accounts shown in the following table to Active Directory or AD DS. Use the procedure following the table to create the user accounts.

 

Account Name User Logon Name E-mail address Group
ADRMSSRVC
 ADRMSSRVC

ADRMSADMIN
 ADRMSADMIN
Enterprise Admins
Nicole Holliday
 NHOLLIDA
 nhollida@cpandl.com
 Employees, Finance
Limor Henig
 LHENIG
 lhenig@cpandl.com
 Employees, Marketing
Stuart Railson
 SRAILSON
 srailson@cpandl.com
 Employees, Engineering

To add new user accounts

  1. Click Start, point to Administrative Tools, and then click Active Directory Users and Computers.
  2. In the console tree, expand cpandl.com.
  3. Right-click Users, point to New, and then click User.
  4. In the New Object – User dialog box, type ADRMSSRVC in the Full name and User logon name boxes, and then click Next.
  5. In the New Object – User dialog box, type a password of your choice in the Password and Confirm password boxes. Clear the User must change password at next logon check box, click Next, and then click Finish.
  6. Perform steps 3-6 for each of the following users: ADRMSADMIN, Nicole Holliday, Limor Henig, and Stuart Railson.
Next, add e-mail addresses to all user accounts.

To add e-mail addresses to user accounts

  1. In the Active Directory Users and Computers console, right-click Nicole Holliday, click Properties, type nhollida@cpandl.com in the E-mail box, and then click OK.
  2. Repeat step 1 for Limor Henig and Stuart Railson, using the e-mail addresses for each account from the table.
  3. Close the Active Directory Users and Computers console.
Once the user accounts have been created, Active Directory Universal groups should be created and these users added to them. The following table lists the Universal groups that should be added to Active Directory. Use the procedure following the table to create the Universal groups.

 

Group Name E-mail address
Finance
 finance@cpandl.com
Marketing
 marketing@cpandl.com
Engineering
 engineering@cpandl.com
Employees
 employees@cpandl.com

To add new group objects to Active Directory

  1. In the Active Directory Users and Computers console, right-click Users, point to New, and then click Group.
  2. In the New Object – Group dialog box, type Finance in Group name, select the Universal option for the Group Scope, and then click OK.
  3. Perform the above steps 1-2 for each of the remaining groups: Marketing, Engineering, and Employees.
Next, add e-mail addresses to group objects:

To add e-mail addresses to group objects

  1. In the Active Directory Users and Computers console, double-click Users, right-click Finance, and then click Properties.
  2. Type finance@cpandl.com in the E-mail box, and then click OK.
  3. Perform the above steps 1-2 for each of the remaining groups: Marketing, Engineering, and Employees.
Finally, add the user accounts to their appropriate groups. In this guide, we will add Nicole Holliday, Limor Henig, and Stuart Railson to the Employees group. Then, we will add Nicole Holliday to the Finance group, Limor Henig to the Marketing group, and finally add Stuart Railson to the Engineering group. To add the user accounts to their respective groups, you should follow these steps:

To add user accounts to groups

  1. In the Active Directory Users and Computers console, double-click Users, and then double-click Employees.
  2. Click Members, and then click Add.
  3. Type nhollida@cpandl.com;lhenig@cpandl.com;srailson@cpandl.com, and then click OK.
  4. Perform the above steps 2-4 to add one member to each of the remaining groups as follows:
    • Nicole Holliday—Finance
    • Limor Henig—Marketing
    • Stuart Railson—Engineering
  5. Double-click Enterprise Admins
  6. Click Members, and then click Add.
  7. Type adrmsadmin@cpandl.com, and then click OK.
  8. Close the Active Directory Users and Computers console.

Configure the AD RMS database computer (ADRMS-DB)

First, install Windows Server 2003 on the computer that will be hosting the AD RMS databases.

To install Windows Server 2003 Standard Edition

  1. Start your computer using the Windows Server 2003 product CD. (You can use any edition of Windows Server 2003 except the Web Edition to establish the domain.)
  2. Follow the instructions that appear on your computer screen, and when prompted for a computer name, type ADRMS-DB.
In this step, configure TCP/IP properties so that ADRMS-DB has a static IP address of 10.0.0.3.

To configure TCP/IP properties on ADRMS-DB

  1. Log on to ADRMS-DB with the ADRMS-DB\Administrator account or another user account in the local Administrators group.
  2. Click Start, point to Control Panel, point to Network Connections, click Local Area Connection, and then click Properties.
  3. On the General tab, click Internet Protocol (TCP/IP), and then click Properties.
  4. Click the Use the following IP address option. In the IP address box, type 10.0.0.3. In the Subnet mask box, type 255.255.255.0. In the Preferred DNS server box, type 10.0.0.1.
  5. Click OK, and then click Close to close the Local Area Connection Properties dialog box.
Next, join the AD RMS database server (ADRMS-DB) computer to the CPANDL domain:

To join ADRMS-DB to the CPANDL domain

  1. Click Start, right-click My Computer, and then click Properties.
  2. Click Computer Name tab, and then click Change.
  3. In the Computer Name Changes dialog box, select the Domain option, and then type cpandl.com.
  4. Click More, and then type cpandl.com in the Primary DNS suffix of this computer box.
  5. Click OK twice.
  6. When a Computer Name Changes dialog box appears prompting you for administrative credentials, provide the credentials for CPANDL\Administrator, and then click OK.
  7. When a Computer Name Changes dialog box appears welcoming you to the cpandl.com domain, click OK.
  8. When a Computer Name Changes dialog box appears telling you that the computer must be restarted, click OK, and then click OK again.
  9. Click Yes to restart the computer.
Next, install Microsoft SQL Server 2005 Standard Edition:

To install Microsoft SQL Server 2005

  1. Log on to ADRMS-DB with the CPANDL\Administrator account or another user account in the local Administrators group.
  2. Insert the Microsoft SQL Server 2005 product CD. The installation will start automatically.
  3. Click the I accept the licensing terms and conditions check box, and then click Next.
  4. On the Installing Prerequisites page, click Install.
  5. Click Next.
  6. On the Welcome to theMicrosoft SQL Server Installation Wizard page, click Next, and then click Next again.
  7. In the Name box, type your name. In the Company box, type the name of your organization, and then type in the appropriate product key. Click Next.
  8. Select the SQL Server Database Services, and Workstation components, Books Online, and development tools check boxes, and then click Next.
  9. Select the Default instance option, and then click Next.
  10. Click the Use the built-in System account option, and then click Next.
  11. Click the Windows Authentication Mode option, and then click Next.
  12. Click Next, accepting the default Collation Settings, and then click Next again.
  13. Click Install. When the status of all the selected components is finished, click Next.
  14. Click Finish.
Next, add ADRMSADMIN to the local Administrators group on ADRMS-DB. The AD RMS installing user account needs this membership in order to create the AD RMS databases. After AD RMS installed, ADRMSADMIN can be removed from this group.

To add ADRMSADMIN to local Administrators group

  1. Click Start, point to Administrative Tools, and then click Computer Management.
  2. Expand System Tools, expand Local Users and Groups, and then click Groups.
  3. Right-click Administrators, click Add to Group, click Add, type ADRMSADMIN in Enter the object names to select (examples) box, and then click OK.
  4. Click OK, and then close Computer Management.
Finally, create a shared folder on ADRMS-DB so that other users can find documents saved to the network.

To create a shared network folder that can be modified by CP&L employees

  1. Click Start, click MyComputer, and then double-click Local Disk (C:).
  2. Click File, point to New, and then click Folder.
  3. Type Public for the new folder, and then press ENTER.
  4. Right-click Public, and then click Sharing and Security.
  5. On the Sharing tab click the Share this folder option, and ensure that Public is in the Share name box.
  6. Click Permissions.
  7. In the Group or user name box click Everyone.
  8. Select the Full Control check box in the Allow column of the Permissions for Everyone box.
  9. Click OK.
  10. Click the Security tab, and then click Users (ADRMS-DB\Users) in the Group or user name box.
  11. In the Permissions for Users box select the Full Control check box in the Allow column.
  12. Click OK.

Configure the AD RMS root cluster computer (ADRMS-SRV)

To configure the member server, ADRMS-SRV, you must install Windows Server 2008, configure TCP/IP properties, and then join ADRMS-SRV to the domain cpandl.com. You must also add the account ADRMSADMIN as a member to the local administrators group. This is needed for ADRMSADMIN to install AD RMS on ADRMS-SRV.
Installing the AD RMS server role will also install Internet Information Services (IIS) 7.0 and Message Queuing.
First, install Windows Server 2008 as a stand-alone server.

To install Windows Server 2008

  1. Start your computer by using the Windows Server 2008 product CD.
  2. When prompted for a computer name, type ADRMS-SRV.
  3. Follow the rest of the instructions that appear on your screen to finish the installation.
Next, configure TCP/IP properties so that ADRMS-SRV has a static IP address of 10.0.0.2. In addition, configure the DNS server by using the IP address of CPANDL-DC (10.0.0.1).

To configure TCP/IP Properties

  1. Log on to ADRMS-SRV with the ADRMS-SRV\Administrator account or another user account in the local Administrators group.
  2. Click Start, click Control Panel, double-click Network and Sharing Center, click Manage Network Connections, right-click Local Area Connection, and then click Properties.
  3. On the Networking tab, click Internet Protocol Version 4 (TCP/IPv4), and then click Properties.
  4. Click the Use the following IP address option. In IP address, type 10.0.0.2, in Subnet mask, type 255.255.255.0.
  5. Click the Use the following DNS server addresses option. In Preferred DNS server, type 10.0.0.1.
  6. Click OK, and then click Close to close the Local Area Connection Properties dialog box.
Next, join ADRMS-SRV to the cpandl.com domain.

To join ADRMS-SRV to the cpandl.com domain

  1. Click Start, right-click Computer, and then click Properties.
  2. Click Change settings (at the right side under Computer name, domain, and workgroup settings), and then click Change.
  3. In the Computer Name/Domain Changes dialog box, select the Domain option, and then type cpandl.com.
  4. Click More, and type cpandl.com in Primary DNS suffix of this computer box.
  5. Click OK, and then click OK again.
  6. When a Computer Name/Domain Changes dialog box appears prompting you for administrative credentials, provide the credentials for CPANDL\Administrator, and then click OK.
  7. When a Computer Name/Domain Changes dialog box appears welcoming you to the cpandl.com domain, click OK.
  8. When a Computer Name/Domain Changes dialog box appears telling you that the computer must be restarted, click OK, and then click Close.
  9. Click Restart Now.
After the computer has restarted, add ADRMSADMIN to the local administrators group on ADRMS-SRV.

To add ADRMSADMIN to the local administrators group

  1. Log on to ADRMS-SRV with the CPANDL\Administrator account.
  2. Click Start, click Administrative Tools, and then click Computer Management.
  3. Expand System Tools, expand Local User and Groups, and then click Groups.
  4. Right-click Administrators, click Add to Group, click Add, type ADRMSADMIN in Enter the object names to select (examples) box, and then click OK.
  5. Click OK, and then close Computer Management.

Configure AD RMS client computer (ADRMS-CLNT)

To configure ADRMS-CLNT, you must install Windows Vista, configure TCP/IP properties, and then join ADRMS-CLNT to the domain cpandl.com. You must also install an AD RMS-enabled application. In this example, Microsoft Office Word 2007 Enterprise Edition is installed on ADRMS-CLNT.

To install Windows Vista

  1. Start your computer by using the Windows Vista product CD.
  2. Follow the instructions that appear on your screen, and when prompted for a computer name, type ADRMS-CLNT.
Next, configure TCP/IP properties so that ADRMS-CLNT has a static IP address of 10.0.0.4. In addition, configure the DNS server of CPANDL-DC (10.0.0.1).

To configure TCP/IP properties

  1. Log on to ADRMS-CLNT with the ADRMS-CLNT\Administrator account or another user account in the local Administrators group.
  2. Click Start, click Control Panel, click Network and Internet, and then click Network and Sharing Center.
  3. Click Manage Network Connections, right-click Local Area Connection, and then click Properties.
  4. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  5. On the Networking tab, click Internet Protocol Version 4 (TCP/IPv4), and then click Properties.
  6. Click the Use the following IP address option. In IP address, type 10.0.0.4, in Subnet mask, type 255.255.255.0.
  7. Click the Use the following DNS server addresses option. In Preferred DNS server, type 10.0.0.1.
  8. Click OK, and then click Close to close the Local Area Connection Properties dialog box.
Next, join ADRMS-CLNT to the cpandl.com domain.

To join ADRMS-CLNT to the cpandl.com domain

  1. Click Start, right-click Computer, and then click Properties.
  2. Under Computer name, domain, and workgroup settings, click Change settings.
  3. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  4. On the Computer Name tab, click Change.
  5. In the Computer Name/Domain Changes dialog box, select the Domain option, and then type cpandl.com.
  6. Click More, and in the Primary DNS suffix of this computer box, type cpandl.com.
  7. Click OK, and then click OK again.
  8. When a Computer Name/Domain Changes dialog box appears prompting you for administrative credentials, provide the credentials, and then click OK.
  9. When a Computer Name/Domain Changes dialog box appears welcoming you to the cpandl.com domain, click OK.
  10. When a Computer Name/Domain Changes dialog box appears telling you that the computer must be restarted, click OK, and then click Close.
  11. In the System Settings Change dialog box, click Yes to restart the computer.
Finally, install Microsoft Office Word 2007 Enterprise.

To install Microsoft Office Word 2007 Enterprise

  1. Log on to ADRMS-CLNT with the CPANDL\Administrator account or another user account in the local Administrators group.
  2. Double-click setup.exe from the Microsoft Office 2007 Enterprise product disc.
  3. Click Customize as the installation type, set the installation type to Not Available for all applications except Microsoft Office Word 2007 Enterprise, and then click Install Now. This might take several minutes to complete.
     

 

Step 2: Installing and Configuring AD RMS on ADRMS-SRV

Applies To: Windows Server 2008
To install and configure AD RMS, you must add the AD RMS server role.
Windows Server 2008 includes the option to install AD RMS as a server role through Server Manager. Both installation and configuration of AD RMS are handled through Server Manager. The first server in an AD RMS environment is the root cluster. An AD RMS root cluster is composed of one or more AD RMS servers configured in a load-balancing environment. This step-by-step guide will install and configure a single-server AD RMS root cluster.
Registering the AD RMS service connection point (SCP) requires that the installing user account be a member of the Active Directory Enterprise Admins group.
ImportantImportant
Access to the Enterprise Admins group should be granted only while AD RMS is being installed. After installation is complete, the cpandl\ADRMSADMIN account should be removed from this group.

To add ADRMSADMIN to the Enterprise Admins group

  1. Log on to CPANDL-DC with the cpandl\Administrator account or another user account in the Domain Admins group.
  2. Click Start, point to Administrative Tools, and then click Active Directory Users and Computers.
  3. In the console tree, expand cpandl.com, double-click Users, and then double-click Enterprise Admins.
  4. Click the Members tab, and then click Add.
  5. Type adrmsadmin@cpandl.com, and then click OK.
Install and configure AD RMS as a root cluster.

To add the AD RMS Server Role

  1. Log on to ADRMS-SRV as cpandl\ADRMSADMIN.
  2. Click Start, point to Administrative Tools, and then click Server Manager.
  3. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  4. In the Roles Summary box, click Add Roles. The Add Roles Wizard opens.
  5. Read the Before You Begin section, and then click Next.
  6. On the Select Server Roles page, select the Active Directory Rights Management Services check box.
  7. The Role Services page appears informing you of the AD RMS dependent role services and features. Make sure that Web Server (IIS), Windows Process Activation Service (WPAS), and Message Queuing are listed, and then click Add Required Role Services. Click Next.
  8. Read the AD RMS introduction page, and then click Next.
  9. On the Select Role Services page, verify that the Active Directory Rights Management Server check box is selected, and then click Next.
  10. Click the Create a new AD RMS cluster option, and then click Next.
  11. Click the Use a different database server option.
  12. Click Select, type ADRMS-DB in the Select Computer dialog box, and then click OK.
  13. In Database Instance, click Default, and then click Validate.
  14. Click Next.
  15. Click Specify, type CPANDL\ADRMSSRVC, type the password for the account, click OK, and then click Next.
  16. Ensure that the Use AD RMS centrally managed key storage option is selected, and then click Next.
  17. Type a strong password in the Password box and in the Confirm password box, and then click Next.
  18. Choose the Web site where AD RMS will be installed, and then click Next. In an installation that uses default settings, the only available Web site should be Default Web Site.
  19. Click the Use an SSL-encrypted connection (https://) option.
  20. In the Fully-Qualified Domain Name box, type adrms-srv.cpandl.com, and then click Validate. If validation succeeds, the Next button becomes available. Click Next.
  21. Click the Create a self-signed certificate for SSL encryption option, and then click Next.
  22. Type a name that will help you identify the AD RMS cluster in the Friendly name box, and then click Next.
  23. Ensure that the Register the AD RMS service connection point now option is selected, and then click Next to register the AD RMS service connection point (SCP) in Active Directory during installation.
  24. Read the Introduction to Web Server (IIS) page, and then click Next.
  25. Keep the Web server default check box selections, and then click Next.
  26. Click Install to provision AD RMS on the computer. It can take up to 60 minutes to complete the installation.
  27. Click Close.
  28. Log off the server, and then log on again to update the security token of the logged-on user account. The user account that is logged on when the AD RMS server role is installed is automatically made a member of the AD RMS Enterprise Administrators local group. A user must be a member of that group to administer AD RMS.
noteNote
At this point in the guide, you can remove cpandl\ADRMSADMIN from the local Administrators group on ADRMS-DB.

Your AD RMS root cluster is now installed and configured.
Further management of AD RMS is done by using the Active Directory Rights Management Services console.

To open the Active Directory Rights Management Services console

  1. Click Start, point to Administrative Tools, and then click Active Directory Rights Management Services.
  2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
From the console, you can configure trust policies, configure exclusion policies, and create rights policy templates.

Step 3: Verifying AD RMS Functionality on ADRMS-CLNT

Applies To: Windows Server 2008
The AD RMS client is included in the default installation of Windows Vista and Windows Server 2008. Previous versions of the client are available for download for some earlier versions of the Windows operating system. For more information, see the Windows Server 2003 Rights Management Services page on the Microsoft Windows Server TechCenter (http://go.microsoft.com/fwlink/?LinkId=68637).
Before you can consume rights-protected content, you must add the AD RMS cluster URL to the Local Intranet security zone.
Add the AD RMS cluster URL to the Local Intranet security zone for all users who will be consuming rights-protected content.

To add AD RMS cluster to Local Intranet security zone

  1. Log on to ADRMS-CLNT as Nicole Holliday (cpandl\NHOLLIDA).
  2. Click Start, click All Programs, and then click Internet Explorer.
  3. Click Tools, and then click Internet Options.
  4. Click the Security tab, click Local intranet, and then click Sites.
  5. Click Advanced.
  6. In the Add this website to the zone, type https://adrms-srv.cpandl.com, and then click Add.
  7. Click Close.
  8. Repeat steps 1–7 for Stuart Railson and Limor Henig.
To verify the functionality of the AD RMS deployment, you will log on as Nicole Holliday and then restrict permissions on a Microsoft Word 2007 document so that members of the CP&L Engineering group are able to read the document but unable to change, print, or copy. You will then log on as Stuart Railson, verifying that the proper permission to read the document has been granted, and nothing else. Then, you will log on as Limor Henig. Since Limor is not a member of the Engineering group, he should not be able to consume the rights-protected file.
noteNote
In this step-by-step guide, when a user restricts permissions on a document or attempts to open a restricted document, a warning appears that informs you that the certificate issuer for the AD RMS Web site is unknown or untrusted. This warning results from using a self-signed certificate instead of a certificate issued by a recognized certification authority. When you receive this warning, click Yes to continue.

To restrict permissions on a Microsoft Word document

  1. Log on to ADRMS-CLNT as Nicole Holliday (cpandl\NHOLLIDA).
  2. Click Start, point to All Programs, point to Microsoft Office, and then click Microsoft Office Word 2007.
  3. Type CP&L engineering employees can read this document, but they cannot change, print, or copy it on the blank document page.
  4. Click the Microsoft Office Button, click Prepare, click Restrict Permission, and then click Restricted Access.
  5. Click the Restrict permission to this document check box.
  6. In the Read box, type engineering@cpandl.com, and then click OK to close the Permission dialog box.
  7. Click the Microsoft Office Button, click Save As, and then save the file as \\ADRMS-DB\Public\ADRMS-TST.docx.
  8. Log off as Nicole Holliday.
Next, log on as Stuart Railson and open the document, ADRMS-TST.docx.

To view a rights-protected document

  1. Log on to ADRMS-CLNT as Stuart Railson (cpandl\SRAILSON).
  2. Click Start, point to All Programs, point to Microsoft Office, and then click Microsoft Office Word 2007.
  3. Click the Microsoft Office Button, and then click Open.
  4. In the File name box, type \\ADRMS-DB\Public\ADRMS-TST.docx, and then click Open.
    The following message appears: "Permission to this document is currently restricted. Microsoft Office must connect to https://adrms-srv.cpandl.com:443/_wmcs/licensing to verify your credentials and download your permission."
  5. Click OK.
    The following message appears: "Verifying your credentials for opening content with restricted permissions…".
  6. When the document opens, click the Microsoft Office Button. Notice that the Print option is not available.
  7. Close Microsoft Word.
  8. Log off as Stuart Railson.
Finally, log on as Limor Henig and verify that he is not able to consume the rights-protected file.

To attempt to view a rights-protected document

  1. Log on to ADRMS-CLNT as Limor Henig (cpandl\LHENIG).
  2. Click Start, point to All Programs, point to Microsoft Office, and then click Microsoft Office Word 2007.
  3. Click the Microsoft Office Button, click Open, and then double-click \\ADRMS-DB\Public\ADRMS-TST.docx.
    The following message appears: "Permission to this document is currently restricted. Microsoft Office must connect to https://adrms-srv.cpandl.com:443/_wmcs/licensing to verify your credentials and download your permission."
  4. Click OK.
  5. The following message appears: "You do not have credentials that allow you to open this document. You can request updated permission from nhollida@cpandl.com. Do you want to request updated permission?"
  6. Click No, and then close Microsoft Word.
You have successfully deployed and demonstrated the functionality of AD RMS, using the simple scenario of applying restricted permissions to a Microsoft Word 2007 document. You can also use this deployment to explore some of the additional capabilities of AD RMS through additional configuration and testing.

Source: http://technet.microsoft.com/en-us/library/cc753531%28v=WS.10%29.aspx

 

 


 

Posted by at 1 comment:

DNS - Useful Tips

How to create and apply a custom application directory partition on an Active Directory integrated DNS zone in Windows Server 2003

 Refer to : http://support.microsoft.com/kb/884116

 Common Tasks

You'll come to use nslookup for little chores almost every day: for example, finding out the IP address or MX records for a given domain name or querying a particular name server for data. We'll cover these common tasks before moving on to the more occasional stuff.

Looking Up Different Data Types

By default, nslookup looks up the address for a name or the name for an address. You can look up any data type by changing the querytype, as we show in this example:
C:\> nslookup  
Default Server:  terminator.movie.edu 
Address:  192.249.249.3 

> misery           Look up address. 
Server:  terminator.movie.edu 
Address:  192.249.249.3 

Name:    misery.movie.edu 
Address:  192.253.253.2 

> 192.253.253.2      Look up name. 
Server:  terminator.movie.edu 
Address:  192.249.249.3 

Name:    misery.movie.edu 
Address:  192.253.253.2 

> set type=mx          Look up MX data. 
> wormhole  
Server:  terminator.movie.edu 
Address:  192.249.249.3 
wormhole.movie.edu      MX preference = 10, mail exchanger = wormhole.movie.edu 
wormhole.movie.edu      internet address = 192.249.249.1 
wormhole.movie.edu      internet address = 192.253.253.1 

> set q=any          Look up data of any type. 
> diehard  
Server:  terminator.movie.edu 
Address:  192.249.249.3 

diehard.movie.edu       internet address = 192.249.249.4 
diehard.movie.edu       MX preference = 10, mail exchanger = diehard.movie.edu 
diehard.movie.edu       internet address = 192.249.249.4
These are only a few of the valid DNS data types, of course. For a more complete list, see Appendix A.

Authoritative Versus Nonauthoritative Answers

If you've used nslookup before, you might have noticed that it sometimes precedes its answers with the phrase "Non-authoritative answer":
C:\>nslookup
Default Server:  terminator.movie.edu
Address:  192.249.249.3

> slate.mines.colorado.edu.
Server:  terminator.movie.edu
Address:  192.249.249.3

Non-authoritative answer:
Name:    slate.mines.colorado.edu
Address:  138.67.1.38
This phrase indicates that the name server is not authoritative for the data in the answer. (Recall that a name server is authoritative for data when it's a primary or secondary for the zone containing the data.) You'll see a nonauthoritative response for one of two reasons. The first is that the name server you queried didn't have the data you were looking for and had to query a remote name server to get it. The remote name server is authoritative for the data (that's the reason it was queried!) and returns it with the "authoritative answer" bit set in the DNS message header. The Microsoft DNS Server you queried puts this data in its cache and returns it to you marked nonauthoritative. If you ask for the same data again, this time the name server can answer from its cache and will mark the data nonauthoritative: that's the second reason you'll see a nonauthoritative answer.
Authoritative answers are not announced by nslookup: the absence of the nonauthoritative message means the answer is authoritative.
Notice that we ended the domain name with a trailing dot. The response would have been the same had we left it off. Sometimes it is critical that you use the trailing dot while debugging, but not always. Rather than stopping to decide if this name needs a trailing dot, we always add one if we know the name is fully qualified (except, of course, for the example where we turn off the search list).

Switching Servers

Sometimes you want to query another name server directly—for example, if you think it is misbehaving. You can switch servers with nslookup by using the server or lserver commands. The difference between server and lserver is that lserver queries your "local" server—the one you started out with—to get the address of the server you want to switch to; server uses the default server instead of the local server. This difference is important because the server that you just switched to may not be responding, as we'll show in this example:
C:\> nslookup 
Default Server:  relay.hp.com 
Address:  15.255.152.2
When we start up, our first server, relay.hp.com, becomes our lserver (this will matter later on in this session):
> server galt.cs.purdue.edu. 
Default Server:  galt.cs.purdue.edu 
Address:  128.10.2.39 

> cs.purdue.edu. 
Server:  galt.cs.purdue.edu 
Address:  128.10.2.39 

*** galt.cs.purdue.edu can't find cs.purdue.edu: No response from server
At this point we try to switch back to our original name server. But there is no name server running on galt to look up relay's address:
> server relay.hp.com. 
*** Can't find address for server relay.hp.com: No response from server
Instead of being stuck, though, we use the lserver command to have our local server look up relay's address:
> lserver relay.hp.com. 
Default Server:  relay.hp.com 
Address:  15.255.152.2 

>
Since the server on galt did not respond—it's not even running a name server—it wasn't possible to look up the address of relay to switch back to using relay's name server. Here's where lserver comes to the rescue: the local name server, relay, was still responding, so we used it. Instead of using lserver, we could have recovered by using relay's IP address directly—server 15.255.152.2.
You can even change servers on a per-query basis. To specify that you'd like nslookup to query a particular server for information about a given domain name, you can specify the server as the second argument on the line, after the domain name to look up—like so:
C:\> nslookup 
Default Server:  relay.hp.com 
Address:  15.255.152.2 

> saturn.sun.com. ns.sun.com. 
Server:  ns.sun.com 
Address:  192.9.9.3 

Name:    saturn.sun.com 
Address:  192.9.25.2
And, of course, you can change servers from the command line. You can specify the server to query as the argument after the domain name to look up, like this:
C:\> nslookup -type=mx fisherking.movie.edu. terminator.movie.edu.
This instructs nslookup to query terminator.movie.edu for MX records for fisherking.movie.edu.
To specify an alternate default server and enter interactive mode, you can use a hyphen in place of the domain name to look up:
C:\> nslookup - terminator.movie.edu.
 
Source: http://fengnet.com/book/DNS.on.Windows.Server.2003/0596005628_dnswinsvr-chp-12-sect-5.html
Posted by at No comments:

Active Directory Services - Windows Server 2008

Active Directory Domain Services

Active Directory Domain Services (AD DS), formerly known as Active Directory Directory Services, is the central location for configuration information, authentication requests, and information about all of the objects that are stored within your forest. Using Active Directory, you can efficiently manage users, computers, groups, printers, applications, and other directory-enabled objects from one secure, centralized location.
  • Auditing. Changes made to Active Directory objects can be recorded so that you know what was changed on the object, as well as the previous and current values for the changed attributes.
  • Fine-Grained Passwords. Password policies can be configured for distinct groups within the domain. No longer does every account have to use the same password policy within the domain.
  • Read-Only Domain Controller. A domain controller with a read-only version of the Active Directory database can be deployed in environments where the security of the domain controller cannot be guaranteed, such as branch offices where the physical security of the domain controller is in question, or domain controllers that host additional roles, requiring other users to log on and maintain the server. The use of Read-Only Domain Controllers (RODCs) prevents changes made at branch locations from potentially polluting or corrupting your AD forest via replication. RODCs also eliminate the need to use a staging site for branch office domain controllers, or to send installation media and a domain administrator to the branch location.
  • Restartable Active Directory Domain Services. Active Directory Domain Services can be stopped and maintained. Rebooting the domain controller and restarting it in Directory Services Restore Mode is not required for most maintenance functions. Other services on the domain controller can continue functioning while the directory service is offline.
  • Database Mounting Tool. A snapshot of the Active Directory database can be mounted using this tool. This allows a domain administrator to view the objects within the snapshot to determine the restore requirements when necessary.

Active Directory Rights Management Services

Your organization’s intellectual property needs to be safe and highly secure. Active Directory Rights Management Services, a component of Windows Server 2008, is available to help make sure that only those individuals who need to view a file can do so. AD RMS can protect a file by identifying the rights that a user has to the file. Rights can be configured to allow a user to open, modify, print, forward, or take other actions with the rights-managed information. With AD RMS, you can now safeguard data when it is distributed outside of your network.
  • Application Support. Support for AD RMS is already included within Windows Vista. Internet Explorer 7 and the 2007 Microsoft Office system already have support for AD RMS. The AD RMS client can also be installed on other Windows operating systems.
  • Persistent Protection. Your content can be protected on the go. You specify who can open, modify, print, or manage the content, and the rights stay with the content—even after it has been transferred outside of your organization.
  • Usage Policy Templates. If you have a common set of rights that you use to control access to information, a Usage Policy Template can be created and applied to content. This alleviates the need to recreate the usage rights settings for every file you want to protect.
  • AD RMS Software Development Kit. The AD RMS Software Development Kit (SDK) can be used by independent software vendors (ISVs) to rights-enable their applications, meaning the application investments you’ve already made may be (or will become) compatible with AD RMS.

Active Directory Federation Services

Active Directory Federation Services is a highly secure, highly extensible, and Internet-scalable identity access solution that allows organizations to authenticate users from partner organizations. Using AD FS in Windows Server 2008, you can simply and very securely grant external users access to your organization’s domain resources. AD FS can also simplify integration between untrusted resources and domain resources within your own organization.
  • Availability As an Integrated Server Role. AD FS is a server role within Windows Server 2008 that can be easily deployed and managed using Server Manager, instead of handled as an added feature, as in Windows Server 2003 R2.
  • Integration with Microsoft Office SharePoint Server 2007. AD FS can be used to facilitate a single sign-on solution for Office SharePoint Server 2007.
  • Integration with Active Directory Rights ManagementServices (AD RMS). AD FS can integrate with AD RMS to support the sharing of rights-protected content between organizations without requiring AD RMS to be deployed in both organizations.
  • Improved Administration. Importing and exporting trust information has been enhanced so that each organization can quickly export or import XML files to facilitate the configuration of trust information.

Active Directory Certificate Services

Most organizations use certificates to prove the identity of users or computers, as well as to encrypt data during transmission across unsecured network connections. Active Directory Certificate Services (AD CS) enhances security by binding the identity of a person, device, or service to their own private key. Storing the certificate and private key within Active Directory helps securely protect the identity, and Active Directory becomes the centralized location for retrieving the appropriate information when an application places a request.
  • Enrollment Agent Templates. Delegated enrollment agents can be assigned on a per-template basis.
  • Integrated Simple Certificate Enrollment Protocol (SCEP). Certificates can be issued to network devices, such as routers.
  • Online Responder. Certificate Revocation List (CRL) entries can be returned to the requestor as a single certificate response instead of the entire CRL. This reduces the total amount of network traffic consumed when clients validate certificates.
  • Enterprise PKI (PKI View). A new management tool for AD CS, this tool allows a Certificate Services administrator to manage Certification Authority (CA) hierarchies to determine the overall health of the CAs and to easily troubleshoot errors.

Active Directory Lightweight Directory Services

Active Directory Lightweight Directory Service (AD LDS), formerly known as Active Directory Application Mode, can be used to provide directory services for directory-enabled applications. Instead of using your organization’s AD DS database to store the directory-enabled application data, AD LDS can be used to store the data. AD LDS can be used in conjunction with AD DS so that you can have a central location for security accounts (AD DS) and another location to support the application configuration and directory data (AD LDS). Using AD LDS, you can reduce the overhead associated with Active Directory replication, you do not have to extend the Active Directory schema to support the application, and you can partition the directory structure so that the AD LDS service is only deployed to the servers that need to support the directory-enabled application.
  • Install from Media Generation. The ability to create installation media for AD LDS by using Ntdsutil.exe or Dsdbutil.exe.
  • Auditing. Auditing of changed values within the directory service.
  • Database Mounting Tool. Gives you the ability to view data within snapshots of the database files.
  • Active Directory Sites and Services Support. Gives you the ability to use Active Directory Sites and Services to manage the replication of the AD LDS data changes.
  • Dynamic List of LDIF files. With this feature, you can associate custom LDIF files with the existing default LDIF files used for setup of AD LDS on a server.
  • Recursive Linked-Attribute Queries. LDAP queries can follow nested attribute links to determine additional attribute properties, such as group memberships.

Additional Active Directory Improvements

The Active Directory Installation Wizard includes several improvements over earlier versions. These improvements make it easier for an administrator to control the installation of domain controllers within the domain. Enhancements include:
  • New Forest Functional Level. Windows Server 2008 R2 includes a new Active Directory forest functional level. Many of the new features in the Active Directory server roles require the Active Directory forest to be configured with this new functional level.
  • Enhanced Command Line and Automated Management. Windows PowerShell cmdlets provide the ability to fully manage Active Directory server roles.
  • Improved Automated Monitoring and Notification. An updated System Center Manager 2007 Management Pack helps improve the monitoring and management of Active Directory server roles.
  • Better Management with Server Manager. Server Manager, the Windows Server 2008 R2 server management tool, allows an administrator to pre-stage domain controllers. When the domain controller role is added from the Server Manager console, the files that are needed to perform the installation of the directory service are copied to the server. When an administrator starts the Installation Wizard, dcpromo.exe, the files are already cached and available.
  • Improved Compliance with Established Standards and Best Practices. Windows Server 2008 R2 includes an integrated Best Practices Analyzer for each of the server roles. The Best Practices Analyzer creates a checklist within Server Manager for the role, which you can use to help perform all the configuration tasks.
  • Answer File Creation. If several domain controllers use the same settings when they are installed, the Summary page allows you to export the settings from the current installation into an answer file. The password used for your Directory Services Restore Mode administrator account is not exported with the answer file, and you can specify that the user who is installing the domain controller is always prompted for the administrator password. This way, passwords are not accessible to users who have access to the location where the answer files are stored.
  • Read-Only Domain Controller Installation The Read-Only Domain Controller role can be installed using the Installation Wizard. When installing a Read-Only Domain Controller, you can define who is allowed to install and manage the domain controller. In the first phase of the installation, a domain administrator can define the account that can install the Read-Only Domain Controller. Once defined, the user that is associated with the Read-Only Domain Controller will have the rights to install the directory service.

    Source: http://www.microsoft.com/windowsserver2008
Posted by at No comments:
Subscribe to: Posts (Atom)