Friday, February 22, 2013

How to Move Mailboxes in Exchange Server 2010

Mailbox moves in previous versions of Exchange were interactive in nature, in that a wizard, script or shell command was used to move the mailbox and it occured in real time.
In Exchange Server 2010 mailbox moves are now handled using move requests.  In short, the move request is submitted into a queue and processed by the Mailbox Replication Service (MRS), which runs on Client Access servers.
Exchange 2010 mailbox move requests can be created using either the Exchange Management Console or the Exchange Management Shell.
There are only a few minor differences between the console and shell for performing mailbox moves, for the most part it comes down to which one you are most comfortable with.

Creating Move Requests using the Exchange Management Console

Launch the Exchange Management Console and navigate to Recipient Configuration/Mailbox.
Select a mailbox, or hold the CTRL key to select multiple mailboxes to move as a group.
Selecting mailboxes to move in the Exchange Management Console
Selecting mailboxes to move in the Exchange Management Console
In the Actions pane click on New Local Move Request.  Local Move Requests are for moves within the same Exchange organization.
Start a new Local Move Request
Start a new Local Move Request
All of the mailboxes selected for the New Local Move Request wizard will be moved to the same target mailbox database.  Click the Browse button to choose a target mailbox database.
Browse to select a target mailbox database
Browse to select a target mailbox database
Select the mailbox database to move the pilot group to and then click OK.  Click Next to continue.
Choose the target mailbox database
Choose the target mailbox database
Leave the Move Settings as the default settings and click Next to continue.  If you encounter issues with corrupt items you may need to create a new move request for those mailboxes and choose to skip corrupted messages.
Configure the settings for the mailbox move requests
Configure the settings for the mailbox move requests
Review the list of mailboxes that will be moved and then click New to create the move requests.
Review the mailboxes to be moved
Review the mailboxes to be moved
Click Finish to close the wizard.
The move requests are created and will be processed by the Exchange server.  You can view the status of the move requests in the Exchange Management Console under Recipient Configuration/Move Request.
View the status of the mailbox move requests
View the status of the mailbox move requests
Right-click a move request and choose Properties to see the status of that move request.
View the progress of a mailbox move request
View the progress of a mailbox move request

Using Filters to Choose Mailboxes for Move Requests

When performing mailbox migrations you can use filters to make the task of selecting mailboxes to be moved simpler.
Open the Exchange Management Console and navigate to Recipient Configuration/Mailbox.  Click on Create Filter at the top of the console.
Creating filters in the Exchange Management Console
Creating filters in the Exchange Management Console
Filters can be created for a number of different user attributes, such as department, the current server they are on, or by name.
Choosing filter criteria
Choosing filter criteria
For example, if you are batching mailbox migrations by surname you can create a filter to only show mailbox users whose surname starts with a given letter.
Applying filters in Exchange Management Console
Applying filters in Exchange Management Console
Click on Apply Filter to see the resulting view.
A filtered view of mailboxes in the Exchange Management Console
A filtered view of mailboxes in the Exchange Management Console
Filtering the views in this way can make it very easy to select the mailboxes that you wish to create move requests for.

Creating Mailbox Move Requests with the Exchange Management Shell

In a similar way to the Exchange Management Console the Exchange Management Shell allows filtering of mailboxes in the organization by various criteria.
For example to get the same filtered list of mailbox users with surnames starting with the letter A the following command is used:
[PS] C:\>Get-Recipient | Where {$_.LastName -like "A*"}

Name                                                        RecipientType
----                                                        -------------
Amanda.Agrawal                                              UserMailbox
David.Abbott                                                UserMailbox
Debbie.Abdillahi                                            UserMailbox
Debbie.Amissah                                              UserMailbox
Debbie.Ashong                                               UserMailbox
Debbie.Askew                                                UserMailbox
Denise.Ahadi                                                UserMailbox
Donna.A'Bear                                                UserMailbox
Ella.Amaral                                                 UserMailbox
Janis.Armoogum                                              UserMailbox
Jo.Allingham                                                UserMailbox
Kathy.Abdullahi                                             UserMailbox
Lesley.Ahmad                                                UserMailbox
Sue.Andress                                                 UserMailbox
Valerie.Andrews                                             UserMailbox
This output can then be piped into the New-MoveRequest command to create the move requests.
Get-Recipient | Where {$_.LastName -like "A*"} | New-MoveRequest -TargetDatabase MB-HO-01
In the above example the mailbox users whose surnames starting with the letter A have new move requests created to migrate them to the database MB-HO-01.
If the same command was used but without the –TargetDatabase parameter, the mailboxes being moved would be automatically distributed across the available databases within the same Active Directory site as the server that the command is being executed from. The exception to this is any mailbox databases that have beenexcluded from automatic mailbox provisioning.
As another example, this command when run on ESP-HO-EX2010B will create move requests for all mailbox users on the legacy server ESP-HO-EX2003 and automatically distribute the mailboxes across the Exchange 2010 mailbox databases in the site where ESP-HO-EX2010B is located.
Get-Recipient | where {$_.ServerName -eq "esp-ho-ex2003"} | New-MoveRequest
Automatic distribution of mailboxes across available databases is only possible when using the Exchange Management Shell to initiate the move requests. Using the Exchange Management Console requires you to specify a target database for the mailboxes being moved.
The Exchange Management Shell can also be used to monitor the progress of move requests. For example this command will list all move requests that have a target database of MB-HO-01.
[PS] C:\>Get-MoveRequest | where {$_.targetdatabase -eq "MB-HO-01"} | Get-MoveRequestStatistics

DisplayName               Status                    TotalMailboxSize          TotalArchiveSize         PercentComplete
-----------               ------                    ----------------          ----------------         ---------------
Joanna Hughes             Queued                    204 MB (213,900,039 by...                          0
Joy Singh                 Queued                    201.6 MB (211,394,039 ...                          0
Laoise Curtis             Queued                    203.4 MB (213,259,972 ...                          0
Maggie Hengist            Queued                    201.5 MB (211,268,161 ...                          0
Lydia Haines              Queued                    202.9 MB (212,717,146 ...                          0
Michael Phillips          Queued                    204.5 MB (214,421,891 ...                          0
Nancy Scott               Queued                    200.7 MB (210,499,528 ...                          0
Ravi Edmonds              Queued                    201.6 MB (211,396,972 ...                          0
Pakwei Dean               Queued                    201.9 MB (211,688,603 ...                          0
Rowena Khan               Queued                    203.9 MB (213,824,471 ...                          0
Prathee Dar               Queued                    201.9 MB (211,671,241 ...                          0
Sharmila Hafri            Queued                    203.1 MB (213,003,913 ...                          0
Stuart Beauchamp          Queued                    206.8 MB (216,879,621 ...                          0
Wendy Fyson               Queued                    202.3 MB (212,077,416 ...                          0
Tina Miller               Queued                    203.2 MB (213,039,339 ...                          0
Jas Dowden                InProgress                201.2 MB (210,950,587 ...                          79
Jagir Ward                InProgress                201.1 MB (210,838,575 ...                          79
Aisha Bhari               Completed                 0 B (0 bytes)                                      100
Andrew O'Grady            Completed                 204.2 MB (214,083,224 ...                          100
Denise Dartnell           Completed                 204.8 MB (214,717,706 ...                          100
Garth Gibbons             Completed                 203.4 MB (213,254,283 ...                          100
Harinder Rahman           Completed                 203.8 MB (213,746,554 ...         

Windows Server 2008 : Controlling Access to Web Services (p5) - Managing URL Authorization Rules

Managing URL Authorization Rules

Authorization is a method by which systems administrators can determine which resources and content are available to specific users. Authorization relies on authentication to validate the identity of a user. Once the identity has been proven, authorization rules determine which actions a user or computer can perform. IIS provides methods of securing different types of content using URL-based authorization. Because Web content is generally requested using a URL that includes a full path to the content being requested, you can configure authorization settings easily, using IIS Manager.

Creating URL Authorization Rules
To enable URL authorization, the UrlAuthorizationModule must be enabled. Authorization rules can be configured at the level of the Web server for specific Web sites, for specific Web applications, and for specific files (based on a complete URL path). URL authorization rules use inheritance so that lower-level objects inherit authorization settings from their parent objects (unless they are specifically overridden).
To configure authorization settings, select the appropriate object in the left pane of IIS Manager, and then select Authorization Rules in Features View. Figure 6 shows an example of multiple rules configured for a Web site.

Figure 6. Viewing authorization rules for a Web site

There are two types of rules: Allow and Deny. You can create new rules by using the Add Allow Rule and Add Deny Rule commands in the Actions pane. The available options for both types of rules are the same. (See Figure 7.) When creating a new rule, the main setting is to determine to which users the rule applies. The options are:
  • All Users
  • All Anonymous Users
  • Specific Roles Or User Groups
  • Specific Users

Figure 7. Creating a new Allow Rule for a Web application

When you choose to specify users or groups to which the rule applies, you can type the appropriate names in a command-separated list. The specific users and groups are defined using .NET role providers. This is a standard feature that is available to ASP.NET Web developers. Developers can create their own roles and user accounts and can define permissions within their applications. Generally, information about users and roles is stored in a relational database or relies on a directory service such as Active Directory.
In addition to user and role selections, you can further configure an authorization rule based on specific HTTP verbs. For example, if you want to apply a rule only for POST commands (which are typically used to send information from a Web browser to a Web server), add only the POST verb to the rule.

Managing Rule Inheritance
As mentioned earlier in this section, authorization rules are inherited automatically by lower-level objects. This is useful when your Web site and Web content is organized hierarchically based on intended users or groups. The Entry Type column shows whether a rule has been inherited from a higher level or whether it has been defined locally. IIS Manager automatically will prevent you from creating duplicate rules. You can remove rules at any level, including both Inherited and Local entry types.

Friday, February 15, 2013

when I click on a PDF hyperlink I get "no program is registered to open this file" all of the hyperlinks are set properly but when I view the presentation I get the error message that there is no program registered to open the file.

In my own experience, it's a profile issue. I tried creating new credential, I open the file with PDF hyperlink it was working fine. So, I backup my important files and deleted my profile. Then recreated the account ID, it works.

How to delete profile:
Note: Make sure you are using different user account with Administrative privilege. Otherwise, the profile cannot be deleted.

1. Right click 'Computer' then properties
2. Click 'Advanced system settings'
3. In 'User Profiles' section, click settings
4. Select the Profile and Delete