jump to navigation

Exchange 2013 demo videos August 30, 2013

Posted by vbry21 in Exchange 2013, Microsoft Training.
Tags: , ,
add a comment

One of the courses I teach is the 20341B Core Solutions of Microsoft Exchange Server 2013.

As part of my teaching the course I like to produce demo videos, these videos have some advantages.

1)      My demos always work.

2)      The demos happen faster as we don’t have to wait for the software to install.

3)      I can’t type, so in the demo my typing appears a lot better.

4)      I can show them time and time again.

 

To view the demos go to my You Tube page and look for the 20341B playlist.

http://www.youtube.com/bryanqa

I hope the videos are useful.

 

 

Advertisements

Public Folders in Exchange 2013 June 28, 2013

Posted by vbry21 in Exchange 2013, Microsoft Training.
Tags: ,
add a comment

I was told many years ago that Public Folders in Exchange Server were dead, well they’re not, they still exist in Exchange 2013, but now they are improved.

In Microsoft Exchange Server 2013, the underlying architecture for public folders has changed entirely, without changing the user experience with public folders.

 

In Microsoft Exchange Server 2013:

• Public folders are stored in a special type of mailbox called a public folder mailbox. In previous versions of Exchange Server, public folders were stored in a separate public folder database. In Exchange Server 2013, the public folder mailboxes are stored in regular mailbox databases. The public folder mailbox stores the public folder hierarchy as well as the public folder contents.

• Public folder mailboxes can be stored in mailbox databases that are part of a DAG. In previous versions of Exchange Server, public folders used a public folder replication process to enable redundancy. By storing the public folder mailboxes in a mailbox database that is part of a DAG, you can provide high availability for the public folder deployment using the same mechanism as the one used for providing high availability for mailboxes.

• Public folders are spread across multiple public folder mailboxes. In previous versions of Exchange Server, you could replicate public folder contents to public folder databases located in different locations to enhance client access to public folder contents. In Exchange Server 2013, you can create public folders and store the public folders in different mailboxes, which can be located on Mailbox servers in different locations.

Now the downside.

Public folders are accessed by clients only for Outlook 2007 or later. Outlook Web App clients cannot access the public folders.

Self Service Distribution Groups in Exchange 2013 June 28, 2013

Posted by vbry21 in Exchange 2013, Microsoft Training.
Tags: ,
add a comment

Many years ago I used to work on an IT support desk and the company I worked for used to recruit graduates, when they started we had to guess which distribution groups to add them to.

Wouldn’t it be nice if I could just get the managers responsible for the graduates to sort out distribution groups?

Well I can with Self-Service Distribution Groups in Exchange 2013

Assign non-Exchange administrators as distribution group owners. With this option, Exchange administrators with the appropriate permissions create distribution groups, and then assign other users as the owners of the groups. The group owners can manage the group membership by accessing the group properties in Outlook or through the Outlook Web App.  You can only add individual mailboxes as owners of a distribution group. You cannot add groups as owners.

Enable open distribution group memberships. You can configure distribution groups to enable users to either automatically join groups or request to join groups. The configuration options vary depending on whether the distribution group is a security group or not.

For security distribution groups, you can configure the group to require owner approval to join groups. Only owners can remove members from security groups.

For distribution groups that are not security groups, you can configure the group membership as open, which means that anyone can automatically join or leave the group. You can also configure the group to require owner approval to join the group. In this scenario, users can request to join the group, and they will be joined to the group when the owner approves the request.

Enable users to create and manage their own distribution groups. You also can enable users to create distribution groups using the Outlook Web App Options page.

To enable users to create distribution groups, you must change the Default Role Assignment Policy or create a new role assignment policy and enable the MyDistributionGroups role. This option gives users permission to create mail-enabled distribution groups and to manage the groups that they own.

The recipient types in Exchange 2013 June 25, 2013

Posted by vbry21 in Exchange 2013, Microsoft Training.
Tags: ,
add a comment

I’ve been looking at Microsoft Exchange Server 2013 over the last couple of weeks and for my exam I’ve been reading up on the various recipient types. These are the Active Directory Objects that we can send email to.

Types of Exchange Server Recipients

• User mailboxes. A mailbox that you assign to an individual user in your Exchange Server organization. This is the most common type of recipient in Exchange Server 2013.

• Mail contacts. Contacts that contain information about people or organizations that exist outside an Exchange Server organization and that have an external email address. Exchange Server routes all messages sent to the mail contact to this external e-mail address.

• Mail users. Users who have an AD DS user account but have an external email address. All messages sent to the mail user are routed to this external email address. A mail user is similar to a mail contact, except that a mail user has an AD DS user account with a security identifier (SID). This allows the user account to access resources in the AD DS environment.

• Resource mailboxes (room mailboxes and equipment mailboxes). A resource mailbox is configured for objects such as meeting rooms, or resources such as a projector. You can include resource mailboxes as resources in meeting requests, which provides a simple and efficient way of scheduling resource usage.

• Shared mailboxes. A mailbox that is used by multiple users rather than one primary user. Organizations often use shared mailboxes to provide services such as sales, help desk, or general information requests.

• Mail-enabled security and distribution groups. You can use a mail-enabled AD DS security group object to grant access permissions to AD DS resources, and you also can use it to distribute messages. You can use a mail-enabled AD DS distribution group object to distribute messages to a group of recipients.

• Dynamic distribution groups. A distribution group that uses a Lightweight Directory Access Protocol (LDAP) query with recipient filters and conditions to derive its membership at the time messages are sent.

• Linked mailboxes. A regular mailbox that is associated with an individual user in a separate, trusted forest. When you create a linked mailbox, a disabled user account is created in the Exchange organization, and a user account from a trusted forest is given access to the mailbox.

• Remote mailboxes. Mailboxes that are located in the Exchange Online environment. In a hybrid Exchange Server 2013 deployment, you can create and manage remote mailboxes in the Exchange Online environment by using the Exchange Administration Center.

• Site mailboxes. Mailboxes that include both an Exchange Server mailbox and a SharePoint site. With site mailboxes, messages are stored in the mailbox, whereas documents are stored on the SharePoint site.

Configuring and Using the Import and Export Mailbox utility Exchange 2013 June 25, 2013

Posted by vbry21 in Exchange 2013, Microsoft Training.
Tags: , ,
add a comment

In some scenarios, you might want to export data from the user’s database or import data to the user’s database. For example, because of compliance or legal reasons, you may be required to export mailbox content from a specific user to a personal storage file (.pst) file. For other purposes, you might want to perform a snapshot of a specific mailbox.

In yet another scenario, you might want to import data from a .pst file from a legacy application to a user’s mailbox on the Exchange Server. For example, if a user was using a Windows Mail application, all of the user’s data was being stored in a .pst file. It is common to import data from the user’s .pst file to the user’s new mailbox on the Exchange Server, or to the user’s archive mailbox.

In Exchange 2013, you can use the New-MailboxImportRequest or New-MailboxExportRequest cmdlets to import or export data from the user’s mailbox. Requests for mailbox import or export must be executed from the Exchange Management Shell. After you run one of these cmdlets, the process is completed asynchronously by the Microsoft Exchange Mailbox Replication service. This service takes advantage of the queuing and throttling frameworks to optimize Exchange performance during import or export operations.

To use the New-MailboxImportRequest or New-MailboxExportRequest cmdlets, the “Mailbox Import Export” role must be assigned to you. By default, this role is unassigned.

The steps to configure Mailbox Import and Export are as follows

  1. Enter the Exchange Management Shell.
  2. Then to allow Administrator access to the Import and Export. Type the following.
  3. New-ManagementRoleAssignment –Role “Mailbox Import Export” –User Administrator then press Enter
  4. To export type the following.
  5. New-MailboxExportRequest –Mailbox username –Filepath  path to export location
  6. To import to the user Archive folder type the following.
  7. New-MailboxImportRequest –Mailbox username –IsArchieve –Filepath  path to file location

 

Disable Exchange Admin Center from the Internet June 25, 2013

Posted by vbry21 in Exchange 2013, Microsoft Training.
Tags: , ,
add a comment

This week I’ve been learning all about Microsoft Exchange 2013, as part of my job as a Microsoft Certified Trainer.

One of the statements on the Microsoft 20341 Exchange Server 2013, Core Solutions Course is that we now use a web based admin utility which replaces the good old Exchange Management Console found in Exchange 2007 and 2010.

The advantages are primarily speed and flexibility.

But this could also be accessed from the outside world, the course tells us that we can disable this access to the new Exchange Admin Centre found in Exchange 2013.

This procedure shows you how to turn off access to the EAC. This procedure doesn’t prevent users from accessing the Options in Outlook Web App.

 

The steps below have to be enable via the Exchange Management Shell.

 

This procedure disables EAC administrator access entirely on the CAS server where the steps are applied. If you to enable EAC administrator for internal users, you should install a separate CAS server and configure it to only handle internal requests using the following command: 

Set-ECPVirtualDirectory -Identity “InternalCAS\ecp (default web site)” –AdminEnabled

Use the Shell to turn off Internet access to the EAC. This example turns off the access to the EAC on server CAS01.

 

Set-ECPVirtualDirectory -Identity “CAS01\ecp (default web site)” -AdminEnabled $false

 

Exchange 2013 Review is now here July 27, 2012

Posted by vbry21 in Exchange 2013.
Tags: ,
add a comment

Exchange 2013 preview is upon us, I have just received an email asking me to download the preview edition. Which, I did.

I haven’t yet installed it, but I will soon on my RC 2012 Windows Server, and probably in a VM on my 2012 Hyper-V server. Also I’ll stick it on VMware vSphere as well, get a balanced view

However I did a bit reading and the first thing that struck me was that we lose the four server roles of Mailbox, Hub Transport, Client Access and Unified Messaging. This gets condensed to two roles, Mailbox and Client Access.

The Mailbox server role now incorporates the traditional Exchange 2010 components such as Hub Transport, Mailbox and Unified Messaging.

The above makes complete sense to me, I never understood having the Message Transport and Unified Messaging as single roles anyway. But it was all to do with CPU constraints when Exchange 2007 popped up.

Client Access as a single role, yes I get that, after all with Database Availability Groups the mailbox may move.

Oh another thing, I remember that Exchange 2007 was going to be the death of Public Folders, well, Exchange 2013 preview has still got them.

As I play and learn more, I’ll stick it in a Blog.