Retention tags and retention policies

Applies to: Exchange Online, Exchange Server 2013

Topic Last Modified: 2016-02-01

In Microsoft Exchange Server 2013 and Exchange Online, Messaging records management (MRM) helps organizations to manage email lifecycle and reduce legal risks associated with e-mail and other communications. MRM makes it easier to keep messages needed to comply with company policy, government regulations, or legal needs, and to remove content that has no legal or business value.

Looking for management tasks related to MRM? See Messaging Records Management Procedures.

Contents

Messaging Records Management strategy

Retention tags

Retention policies

Managed Folder Assistant

Retention hold

Messaging Records Management strategy

MRM in Exchange 2013 and Exchange Online is accomplished by using retention tags and retention policies. Before discussing the details about each of these retention features, it's important to learn how the features are used in the overall MRM strategy. This strategy is based on:

• Assigning retention policy tags (RPTs) to default folders, such as the Inbox and Deleted Items.
• Applying default policy tags (DPTs) to mailboxes to manage the retention of all untagged items.
• Allowing the user to assign personal tags to custom folders and individual items.
• Separating MRM functionality from users' Inbox management and filing habits. Users aren't required to file messages in managed folders based on retention requirements. Individual messages can have a different retention tag than the one applied to the folder in which they're located.

The following figure illustrates the tasks involved in implementing this strategy.

Return to top

Retention tags

As illustrated in the preceding figure, retention tags are used to apply retention settings to folders and individual items such as e-mail messages and voice mail. These settings specify how long a message remains in a mailbox and the action to be taken when the message reaches the specified retention age. When a message reaches its retention age, it's moved to the user’s In-Place Archive or deleted.

Retention tags allow users to tag their own mailbox folders and individual items for retention. Users no longer have to file items in managed folders provisioned by an administrator based on message retention requirements.

Types of retention tags

Retention tags are classified into the following three types based on who can apply them and where in a mailbox they can be applied.

 

Type of retention tag	Applied...	Applied by...	Available actions…	Details
Default policy tag (DPT)	Automatically to entire mailbox A DPT applies to untagged items, which are mailbox items that don’t have a retention tag applied directly or by inheritance from the folder.	Administrator	Move to archive Delete and allow recovery Permanently delete	Users can’t change DPTs applied to a mailbox.
Retention policy tag (RPT)	Automatically to a default folder Default folders are folders created automatically in all mailboxes, for example: Inbox, Deleted Items, and Sent Items. See the list of supported default folders inDefault folders that support Retention Policy Tags.	Administrator	Delete and allow recovery Permanently delete	Users can’t change the RPT applied to a default folder.
Personal tag	Manually to items and folders Users can automate tagging by using Inbox rules to either move a message to a folder that has a particular tag or to apply a personal tag to the message.	Users	Move to archive Delete and allow recovery Permanently delete	Personal tags allow your users to determine how long an item should be retained. For example, the mailbox can have a DPT to delete items in seven years, but a user can create an exception for items such as newsletters and automated notifications by applying a personal tag to delete them in three days.

More about personal tags

Personal tags are available to Outlook 2010 and Outlook Web App users as part of their retention policy. In Outlook 2010 and Outlook Web App, personal tags with theMove to Archive action appear as Archive Policy, and personal tags with the Delete and Allow Recovery or Permanently Delete actions appear as Retention Policy, as shown in the following figure.

Users can apply personal tags to folders they create or to individual items. Messages that have a personal tag applied are always processed based on the personal tag's settings. Users can apply a personal tag to a message so that it's moved or deleted sooner or later than the settings specified in the DPT or RPTs applied to that user's mailbox. You can also create personal tags with retention disabled. This allows users to tag items so they're never moved to an archive or never expire.

Note:
Users can apply archive policies to default folders, user-created folders or subfolders, and individual items. Users can apply a retention policy to user-created folders or subfolders and individual items (including subfolders and items in a default folder), but not to default folders.

Users can also use the Exchange Administration Center (EAC) to select additional personal tags that aren't linked to their retention policy. The selected tags then become available in Outlook 2010 and Outlook Web App. To enable users to select additional tags from the EAC, you must add the MyRetentionPolicies role to the user's role assignment policy. To learn more about role assignment policies for users, see Understanding management role assignment policies. If you allow users to select additional personal tags, all personal tags in your Exchange organization become available to them.

Note:
Personal tags are a premium feature. Mailboxes with policies that contain these tags (or as a result of users adding the tags to their mailbox) require an Exchange Enterprise client access license (CAL).

Return to top

Retention age

When you enable a retention tag, you must specify a retention age for the tag. This age indicates the number of days to retain a message after it arrives in the user's mailbox.

The retention age for non-recurring items (such as email messages) is calculated differently than items that have an end date or recurring items (such as meetings and tasks). To learn how retention age is calculated for different types of items, see How retention age is calculated.

You can also create retention tags with retention disabled or disable tags after they're created. Because messages that have a disabled tag applied aren't processed, no retention action is taken. As a result, users can use a disabled personal tag as a Never Move tag or a Never Delete tag to override a DPT or RPT that would otherwise apply to the message.

Retention actions

When creating or configuring a retention tag, you can select one of the following retention actions to to be taken when an item reaches its retention age:

 

Retention action	Action taken…	Except…
Move to Archive 1	Moves the message to the user's archive mailbox Only available for DPTs and personal tags For details about archiving, see: In-Place Archiving in Exchange 2013 Archive mailboxes in Exchange Online	If the user doesn't have an archive mailbox, no action is taken.
Delete and Allow Recovery	Emulates the behavior when the user empties the Deleted Items folder. Items are moved to the Recoverable Items folder in the mailbox and preserved until the deleted item retention period. Provides the user a second chance to recover the item using the Recover Deleted Items dialog box in Outlook or Outlook Web App	If you’ve set the deleted item retention period to zero days, items are permanently deleted. For details, see Change the deleted item retention period for a mailbox in Exchange Online.
Permanently Delete	Permanently deletes messages. You can’t recover messages after they’re permanently deleted.	If mailbox is placed on In-Place Hold and Litigation Hold or Litigation Hold, items are preserved in the Recoverable Items folder based on hold parameters. In-Place eDiscoverywill still return these items in search results.
Mark as Past Retention Limit	Marks a message as expired. In Outlook 2010 or later, and Outlook Web App, expired items are displayed with the notification stating 'This item has expired' and 'This item will expire in 0 days'. In Outlook 2007, items marked as expired are displayed by using strikethrough text.	N. A.

Note:

1   In an Exchange hybrid deployment, you can enable a cloud-based archive mailbox for an on-premises primary mailbox. If you assign an archive policy to an on-premises mailbox, items are moved to the cloud-based archive. If an item is moved to the archive mailbox, a copy of it isn't retained in the on-premises mailbox. If the on-premises mailbox is placed on hold, an archive policy will still move items to the cloud-based archive mailbox where they are preserved for the duration specified by the hold.

For details about how to create retention tags, see Create a Retention Policy.

Return to top

Retention policies

To apply one or more retention tags to a mailbox, you must add them to a retention policy and then apply the policy to mailboxes. A mailbox can't have more than one retention policy. Retention tags can be linked to or unlinked from a retention policy at any time, and the changes automatically take effect for all mailboxes that have the policy applied.

A retention policy can have the following retention tags:

 

Retention tag type	Tags in a policy
Default policy tag (DPT)	One DPT with the Move to Archive action One DPT with the Delete and Allow Recovery or Permanently Delete actions One DPT for voice mail messages with the Delete and Allow Recovery or Permanently Delete action
Retention policy tags (RPTs)	One RPT for each supported default folder Note: You can't link more than one RPT for a particular default folder (such as Deleted Items) to the same retention policy.
Personal tags	Any number of personal tags Tip: Many personal tags in a policy can confuse users. We recommend adding no more than 10 personal tags to a retention policy.

Note:
Although a retention policy doesn't need to have any retention tags linked to it, we don't recommend using this scenario. If mailboxes with retention policies don't have retention tags linked to them, this may cause mailbox items to never expire.

A retention policy can contain both archive tags (tags that move items to the personal archive mailbox) and deletion tags (tags that delete items). A mailbox item can also have both types of tags applied. Archive mailboxes don't have a separate retention policy. The same retention policy is applied to the primary and archive mailbox.

When planning to create retention policies, you must consider whether they'll include both archive and deletion tags. As mentioned earlier, a retention policy can have one DPT that uses the Move to Archive action and one DPT that uses either the Delete and Allow Recovery or Permanently Delete action. The DPT with the Move to Archive action must have a lower retention age than the DPT with a deletion action. For example, you can use a DPT with the Move to Archive action to move items to the archive mailbox in two years, and a DPT with a deletion action to remove items from the mailbox in seven years. Items in both primary and archive mailboxes will be deleted after seven years.

For a list of management tasks related to retention policies, see Messaging Records Management Procedures.

Default retention policy

Exchange Setup creates the retention policy Default MRM Policy. The Default MRM Policy is applied automatically to new mailboxes in Exchange Online. In Exchange Server, the policy is applied automatically if you create an archive for the new user and don’t specify a retention policy

You can modify tags included in the Default MRM Policy, for example by changing the retention age or retention action, disable a tag or modify the policy by adding or removing tags from it. The updated policy is applied to mailboxes the next time they’re processed by the Managed Folder Assistant.

For more details, including a list of retention tags linked to the policy, see Default Retention Policy in Exchange Online and Exchange Server.

Return to top

Managed Folder Assistant

The Managed Folder Assistant, a mailbox assistant that runs on Mailbox servers, processes mailboxes that have a retention policy applied.

The Managed Folder Assistant applies the retention policy by inspecting items in the mailbox and determining whether they're subject to retention. It then stamps items subject to retention with the appropriate retention tags and takes the specified retention action on items past their retention age.

The Managed Folder Assistant is a throttle-based assistant. Throttle-based assistants are always running and don't need to be scheduled. The system resources they can consume are throttled. You can configure the Managed Folder Assistant to process all mailboxes on a Mailbox server within a certain period (known as a work cycle). Additionally, at a specified interval (known as the work cycle checkpoint), the assistant refreshes the list of mailboxes to be processed. During the refresh, the assistant adds newly created or moved mailboxes to the queue. It also reprioritizes existing mailboxes that haven't been processed successfully due to failures and moves them higher in the queue so they can be processed during the same work cycle.

You can also use the Start-ManagedFolderAssistant cmdlet to manually trigger the assistant to process a specified mailbox. To learn more, see Configure the Managed Folder Assistant.

Note:
The Managed Folder Assistant doesn't take any action on messages that aren't subject to retention, specified by disabling the retention tag. You can also disable a retention tag to temporarily suspend items with that tag from being processed.

Moving items between folders

A mailbox item moved from one folder to another inherits any tags applied to the folder to which it's moved. If an item is moved to a folder that doesn't have a tag assigned, the DPT is applied to it. If the item has a tag explicitly assigned to it, the tag always takes precedence over any folder-level tags or the default tag.

Applying a retention tag to a folder in the archive

When the user applies a personal tag to a folder in the archive, if a folder with the same name exists in the primary mailbox and has a different tag, the tag on that folder in the archive changes to match the one in the primary mailbox. This is by design to avoid any confusion about items in a folder in the archive having a different expiry behavior than the same folder in the user’s primary mailbox. For example, the user has a folder named Project Contoso in the primary mailbox with a Delete – 3 years tag and a Project Contoso folder also exists in the archive mailbox. If the user applies a Delete – 1 year personal tag to delete items in the folder after 1 year. When the mailbox is processed again, the folder reverts to the Delete – 3 Years tag.

Removing or deleting a retention tag from a retention policy

When a retention tag is removed from the retention policy applied to a mailbox, the tag is no longer available to the user and can't be applied to items in the mailbox.

Existing items that have been stamped with that tag continue to be processed by the Managed Folder Assistant based on those settings and any retention action specified in the tag is applied to those messages.

However, if you delete the tag, the tag definition stored in Active Directory is removed. This causes the Managed Folder Assistant to process all items in a mailbox and restamp the ones that have the removed tag applied. Depending on the number of mailboxes and messages, this process may significantly consume resources on all Mailbox servers that contain mailboxes with retention policies that include the removed tag.

Important:
If a retention tag is removed from a retention policy, any existing mailbox items with the tag applied will continue to expire based on the tag's settings. To prevent the tag's settings from being applied to any items, you should delete the tag. Deleting a tag removes it from any retention policies in which it's included.

Disabling a retention tag

If you disable a retention tag, the Managed Folder Assistant ignores items that have that tag applied. Items that have a retention tag for which retention is disabled are either never moved or never deleted, depending on the specified retention action. Because these items are still considered tagged items, the DPT doesn't apply to them. For example, if you want to troubleshoot retention tag settings, you can temporarily disable a retention tag to stop the Managed Folder Assistant from processing messages with that tag.

Note:
The retention period for a disabled retention tag is displayed to the user as Never. If a user tags an item believing it will never be deleted, enabling the tag later may result in unintentional deletion of items the user didn't want to delete. The same is true for tags with the Move to Archive action.

Return to top

Retention hold

When users are temporarily away from work and don't have access to their e-mail, retention settings can be applied to new messages before they return to work or access their e-mail. Depending on the retention policy, messages may be deleted or moved to the user's personal archive. You can temporarily suspend retention policies from processing a mailbox for a specified period by placing the mailbox on retention hold. When you place a mailbox on retention hold, you can also specify a retention comment that informs the mailbox user (or another user authorized to access the mailbox) about the retention hold, including when the hold is scheduled to begin and end. Retention comments are displayed in supported Outlook clients. You can also localize the retention hold comment in the user's preferred language.

Note:
Placing a mailbox on retention hold doesn't affect how mailbox storage quotas are processed. Depending on the mailbox usage and applicable mailbox quotas, consider temporarily increasing the mailbox storage quota for users when they're on vacation or don't have access to e-mail for an extended period. For more information about mailbox storage quotas, see Configure storage quotas for a mailbox.

During long absences from work, users may accrue a large amount of e-mail. Depending on the volume of e-mail and the length of absence, it may take these users several weeks to sort through their messages. In these cases, consider the additional time it may take the users to catch up on their mail before removing them from retention hold.

If your organization has never implemented MRM, and your users aren't familiar with its features, you can also use retention holds during the initial warm up and training phase of your MRM deployment. You can create and deploy retention policies and educate users about the policies without the risk of having items moved or deleted before users can tag them. A few days before the warm up and training period ends, you should remind users of the warm-up deadline. After the deadline, you can remove the retention hold from user mailboxes, allowing the Managed Folder Assistant to process mailbox items and take the specified retention action.

For details about how to place a mailbox on retention hold, see Place a mailbox on retention hold.

Video: Retention Policies

http://www.msexchange.org/articles-tutorials/exchange-server-2010/management-administration/video-retention-policies.html

Place a mailbox on Litigation Hold

How does Litigation Hold work? In the normal deleted item workflow, a mailbox item is moved to the Deletions subfolder in the Recoverable Items folder when a user permanently deletes it (Shift + Delete) or deletes it from the Deleted Items folder. A deletion policy (which is a retention tag configured with a Delete retention action) also moves items to the Deletions subfolder when the retention period expires. When a user purges an item in the Recoverable Items folder or when the deleted item retention period expires for an item, it's moved to the Purges subfolder in the Recoverable Items folder and marked for permanent deletion. It will be purged from Exchange the next time the mailbox is processed by the Managed Folder Assistant (MFA).

When a mailbox is placed on Litigation Hold, items in the Purges subfolder are preserved for the hold duration specified by the Litigation Hold. The hold duration is calculated from the original date an item was received or created, and defines how long items in the Purges subfolder are held. When the hold duration expires for an item in the Purges subfolder, the item is marked for permanent deletion and will be purged from Exchange the next time the mailbox is processed by the MFA. If an indefinite hold is placed on a mailbox, items will never be purged from the Purges subfolder.

The following illustration shows the subfolders in the Recoverable Items folders and the hold workflow process.

• Note:
  If an In-Place Hold is placed on a mailbox, purged items are moved from the Deletions subfolder to the DiscoveryHolds subfolder and are preserved for the hold duration for the In-Place Hold.

• If your organization requires that all mailbox data has to preserved for a specific period of time, consider the following before you place all mailboxes in an organization on Litigation Hold.
  • When you use the previous command to place a hold on all mailboxes in an organization (or a subset of mailboxes matching a specified recipient filter) only mailboxes that exist at the time that you run the command are placed on hold. If you create new mailboxes later, you have to run the command again to place the new mailboxes on hold. If you create new mailboxes often, you can run the command as a scheduled task as frequently as required.
  • Placing all mailboxes on Litigation Hold can significantly impact mailbox sizes. In an Exchange 2016 organization, plan for adequate storage to meet your organization’s preservation requirements.
  • The Recoverable Items folder has its own storage limit, so items in the folder don’t count towards the mailbox storage limit. As previously explained, preserving mailbox data for a long period of time will result in growth of the Recoverable Items folder in a user’s mailbox and archive. We recommend that you periodically monitor the size of this folder to ensure it doesn’t reach the limit. For more information, see Recoverable Items folder.

The following table provides an overview of the messaging policy and compliance features in Exchange 2013:

Feature	Description
Messaging Records   Management (MRM)	To meet legal or business requirements, organizations include e-mail lifecycle policies as part of their messaging policy. Exchange 2013 includes MRM features that allow administrators to implement organization’s e-mail lifecycle policies. MRM can be used to apply uniform retention settings to all messages, or to allow users to classify messages so that they can be retained for a specified duration.
In-Place Archiving	In-Place Archiving helps regain control of the organization's messaging data by eliminating the need for personal store (.pst) files and allowing users to store messages in an archive mailbox accessible in and Outlook Web App.
In-Place Hold	Organizations are required to preserve electronically stored information, including e-mail that is relevant to a litigation case. In-Place Hold allows the search and preservation of messages matching query parameters. Messages are protected from deletion, modification, and tampering and can be preserved indefinitely or for a specified period.
In-Place eDiscovery	In-Place eDiscovery allows the search of mailbox data across an Exchange organization, preview search results and copy them to a Discovery mailbox.
Journaling	Journaling can also help organizations respond to legal, regulatory and organizational compliance requirements by recording inbound and outbound e-mail communications.
Transport Rules	Transport rules can look for specific conditions for messages that pass through an organization and   then take action on them. Transport rules can also apply messaging policies to e-mail messages, secure messages, protect messaging systems and prevent information leakage.
Data Loss Prevention   (DLP)	DLP capabilities help protect sensitive data and inform users of policies and regulations. DLP can   also help prevent users from mistakenly sending sensitive information to unauthorized people.
Information Rights   Management (IRM)	IRM provides persistent online and offline protection for e-mail messages and attachments using Active Directory Rights Management Services (AD RMS).
Mailbox audit logging	Because mailboxes can potentially contain sensitive, high business impact information, it is important to keep track of who logs on to the mailboxes in an organization and what actions are taken. It is especially important to track access to mailboxes by users other than the mailbox owner (known as delegate users). Mailbox audit logging logs mailbox access by mailbox owners, delegates   (including administrators with full mailbox access permissions) and administrators.
Administrator audit logging	Administrator audit logging keeps a log of changes made by administrators to an Exchange environment. They can be used as part of a change control process or to track changes and access to configuration and recipients for compliance purposes.

Table 1

Immutability of data is another key feature of any messaging and archiving product and the way Exchange treats immutability is slightly different from other products. Traditionally, immutability was associated with WORM storage that would guarantee that the data could not be tampered with once it was written to disk. In Exchange, this is all done at the software level using the In-Place Archive feature, and is fully independent from the storage used.

How to perform a search:

http://msexchangeguru.com/2014/08/21/in-place-hold/

How to configure e discovery and hold permission to the user in exchange server 2013

Instalando Exchange 2013

Exchange 2010 SP3: UCMA requires the following missing Windows features

When installing Exchange 2010 SP3 on a server with Windows Server 2012 you need to install some prerequisites first. Each server with the Client Access role requires the Unified Communications Managed API 4.0 Runtime.

You may run into this error message when you try to install:

Microsoft Unified Communications Managed API 4.0, Runtime requires the following missing Windows features.

• Media Foundation

This error occurs when you followed the instructions on this page: Exchange 2010 Prerequisites (Install the Windows Server 2012 operating system prerequisites). For a server with the three basic roles Microsoft says you need to install the following operating system components:

Solution

Add Media Foundation via PowerShell

Run the following command;

Install-WindowsFeature Server-Media-Foundation

Add Media Foundation via Server Manager

1. Launch Server Manager (ServerManager.exe) > Manage > Add Roles and Features > Next > Next > Next > Scroll Down > Select Media Foundation > Next > Install.

Permisos:

Schema admin, enterprice admin:

Preparing Active Directory for Exchange Server 2013

When you are installing Exchange Server 2013 for the first time the Active Directory needs to be prepared.
There are a series of requirements for Active Directory preparation to be successful:

• Schema master running Windows Server 2003 with SP2, or a later version of Windows Server
• At least one Global catalog server per site that Exchange will be installed in that is running Windows Server 2003 SP2 or later
• At least one Domain controller per site that Exchange will be installed in that is running Windows Server 2003 SP2 or later
• Forest functional mode of Windows Server 2003 or higher
• An account with Schema Admins, Domain Admins, and Enterprise Admins permissions to run Exchange setup

Although Active Directory preparation can occur as part of the installation of the first Exchange Server 2013 server, you can also run the Active Directory preparation as a separate task beforehand on a 64-bit server running Windows Server 2008 or higher.
Because the Active Directory preparation requires the RSAT-ADDS tools I am running it on the domain controller in my test lab.
Alternatively, you can install the tools on a member server to run Exchange 2013 Active Directory preparation.

For Windows Server 2008 R2 (SP1 or later), in PowerShell run:

Import-Module ServerManager

Add-WindowsFeature RSAT-ADDS

For Windows Server 2012, in PowerShell run:

Install-WindowsFeature RSAT-ADDS

If you are installing Exchange Server in the AD forest for the first time run the following Exchange 2013 setup command to prepare Active Directory:

setup /PrepareAD /OrganizationName:"your organization name" /IAcceptExchangeServerLicenseTerms

Note: if your organization name contains spaces then it must be enclosed in quotes as shown above.
If an Exchange organization already exists you can omit the /OrganizationName parameter.

setup /PrepareAD /IAcceptExchangeServerLicenseTerms

For other Active Directory preparation scenarios, such as multiple forests or multiple domains, refer to this article on TechNet.

Prerequisitos de componentes sobre servers de correo

Con la propia instalación desde la UI se realiza automáticamente con solo elegir un seteo:

Tambien podemos instalarlo desde el Shell:

Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation, RSAT-Clustering-CmdInterface, RSAT-ADDS

The cmdlet action is shown in Figure 03.

Figure 03

No mas exch managment tool:

https://www.youtube.com/watch?v=GpH0jC_2-FQ#t=248

 Hi All :
       When you installing Exchange Server 2013 Mailbox High-available on Windows Server 2012 environment , you may encounter this error : An Active Manager operation failed with a transient error: Please retry the operation. Error: The fully qualified domain name for node 'XXXX' could not be found.

        Now , you need to assign the machine account of the first node added to the DAG with full control of the pre-staged object.
      1. Select the appropriate container in Active Directory Users and Computers snap-in console where you wish the account to be created.  Right click, select New –> Computer :

      2. In the Computer name box, type the name that was assigned to the database availability group :

        3. Click OK , the computer account created . Right-click this account and click Properties :

       4. Then click Security tab , and click Add... , add the first DAG member server computer account and assign the machine account Full control Allow permission :



   6. When presented with the disable dialog, select Yes :

     7. After the object has been successfully disabled,  press the OK button on the success confirmation :

    8. And now , you can start to creating DAG successfully !

Exchange 2013 DAG

Hi All :
       When you installing Exchange Server 2013 Mailbox High-available on Windows Server 2012 environment , you may encounter this error : An Active Manager operation failed with a transient error: Please retry the operation. Error: The fully qualified domain name for node 'XXXX' could not be found.

        Now , you need to assign the machine account of the first node added to the DAG with full control of the pre-staged object.
      1. Select the appropriate container in Active Directory Users and Computers snap-in console where you wish the account to be created.  Right click, select New –> Computer :

      2. In the Computer name box, type the name that was assigned to the database availability group :

        3. Click OK , the computer account created . Right-click this account and click Properties :

       4. Then click Security tab , and click Add... , add the first DAG member server computer account and assign the machine account Full control Allow permission :



   6. When presented with the disable dialog, select Yes :

     7. After the object has been successfully disabled,  press the OK button on the success confirmation :

    8. And now , you can start to creating DAG successfully !

Empower photographers to capture and recognize eye cancer in children