Showing posts with label MS Exchange. Show all posts
Showing posts with label MS Exchange. Show all posts

Thursday, October 30, 2014

Exchange Server 2013 Backup and Restore 101 - Recovering individual items (Part 1)

Introduction

In this article series, we are going to go over the process to restore data using Exchange Server 2013 built-in capabilities. We are going to start from the simplest assumption when an administrator has to restore a single message and from that point on, we will move forward with the restore capabilities of Exchange Server 2013 for several items, such as individual items, disabled mailboxes, deleted mailboxes, mailbox databases and finally server recovery.
All articles of this series are based on Exchange Server 2013 Service Pack 1.
Advertisement

Recovering Deleted items – An Introduction

The first stop of this article series is how we can retrieve single messages from a mailbox using the built-in tools. The Mailbox Database is the main component where we define how long any deleted item will stay in the Database and from there an easy restore process can be initiated from either side: end-user or administrator.
In order to identify how many days a message will stay on any given mailbox is controlled by the attribute Keep deleted items for (days) and that can be found on the properties of a Mailbox Database and by default the value is 14 (fourteen) days.
The steps to get there are, open Exchange Admin Center (EAC), click on servers, click on databases, and double-click on the desired database. Then, click on limits (Figure 01).
Image
Figure 01
In previous versions of Exchange that was known as Dumpster however, since Exchange Server 2010, the feature has been called Recoverable Items folder and the structure can be seen in Figure 02.
Image
Figure 02
Another concept that must be clear for the administrator is to understand the differences between delete, soft deleteand hard delete.
Using either Outlook client or Outlook Web App a user can select a message and hit delete button on the keyboard, or right-click on the message and delete (Figure 03), and that message will be removed from the current location and it will end-up in the Deleted Items folder. This operation is called delete.
Image
Figure 03
If you are using ActiveSync (iOS in this example), the Trash option will be displayed when moving items from regular folders to the Deleted Items folder, as shown in Figure 04.
Image
Figure 04
So far we moved the items from wherever they are to the Deleted Items (delete operation), and from there we can right-click on the Deleted Items folder and then click on empty (Figure 05) to perform a soft-delete operation. A soft delete operation means that the message is not visible on the client side however, it can be restored easily because all the content is located in the Deletions folder of Recoverable Items folder.
Image
Figure 05
We can soft delete a message directly from its original folder by holding Shift and hit Delete button. When we do that, a dialog box asking for confirmation will be displayed (Figure 06), when we click ok the message will be removed without stopping by your Deleted Items folder.
Image
Figure 06
If we try to delete a message from the Trash folder on iOS device we will notice that the caption changed to Delete, as shown in Figure 07.
Image
Figure 07

End-user restoring process…

Time has come when a user lost a message and the user could not find the message on the Deleted Items. We can instruct the user to right-click on the Deleted Items folder and then click on recover deleted items… item, as shown in Figure 08.
Important note:
If the message was deleted longer than the number of days defined in the Mailbox Database of that specific mailbox, we will not be able to restore such item using the current procedure.
Image
Figure 08
In the new window (Figure 09), the end-user will have all deleted messages, and the end-user can select any given message and right-click and then recover and purge options will be available. The same options are available at the right bottom corner of the same page.
Image
Figure 09
When the end-user selects recover option of a message the following dialog box (Figure 10) informing where the restored message will appear is going to be displayed, just click OK.
Image
Figure 10
All items located in the Deletions folder of the Recoverable Items folder are moved to the Purges folder when their retention period is reached or when the end-user uses the option Purge and that is considered a hard deleteoperation. In the Figure 11, we can see the dialog box that will show up when we try to purge an item from recover deleted items window.
Image
Figure 11

The problem… hard delete operations

In the previous section, we look at the Recoverable Items folder and how we can use to restore items to our end-users but we will have the risk for a hard delete operation and if that occurs we will need a previous backup to bring that data back to a regular situation, but there is methods to overcome this challenge.
We can also have common situations where a user knows or has access to their mailbox before being fired, then the user removes all information from the mailbox and Recovery Deleted, and that will create a problem to restore the data afterwards.
To avoid these issues described above we can take advantage of a feature called Single Item Recovery, which enforces that the number of days defined on the database will be honored. When this Single Item Recovery feature is enabled, then all messages that are moved to the Purges folder will stay there for the time defined in the database.
In order to enable a user, we just need to run the following cmdlet Set-Mailbox <Mailbox> -SingleItemRecoveryEnabled $True, as shown in Figure 12.
Image
Figure 12
Using Single Item Recovery feature, we can have consistency among restore time for end-users and in some scenarios replace the current tapes/backup solutions. For instance, if you have Single Item Recovery enabled for all users and 30 days defined at the database, then we should never use tapes to restore for at least the last 30 days.

Conclusion

In this first article of our series, we saw the different types of deletions of an item from the restore perspective. In the last section, we also covered how we can enable Single Item Recovery feature on a user basis and we will take advantage of this feature in the next article of this series.

Wednesday, October 29, 2014

Managing Exchange Online using Server 2012 R2 Essentials Experience Role (Part 1)

Introduction

Microsoft announced Windows Server 2012 Essentials back in the summer of 2012 as the next version of what used to be called Small Business Server (SBS) Essentials. This was, in many ways, the end of an era.
SBS was very popular as it was without a doubt a great platform: it contained in one box all of the elements a business could need such as the server’s operating system and management tools, together with SharePoint Server and Exchange Server. However, the two main problems with SBS were its 25 licenses limit and the fact it did not provide an easy upgrade path for companies once their needs grew larger than what SBS could handle.
Since SBS 4.0 launched back in 1997, e-mail functionality was provided in all versions of SBS by having Exchange Server installed on the SBS box itself. Eventually, this changed when Microsoft divided SBS 2011 into Standard (with Exchange built-in) and Essentials (without Exchange built-in).
Windows Server 2012 Essentials has been designed to work with three different types of e-mail systems:
  • Office 365;
  • Hosted Exchange;
  • On-premises Exchange.
The first two are very much what SBS 2011 Essentials was also designed to do. Through add-ins in the Essentials console, administrators could manage a large part of the e-mail system even though it was hosted in the cloud. The last one, however, is different as on-premises Exchange is not Exchange built into the SBS server itself, but a separate Exchange server. This has been the biggest complaint about Windows Server 2012 Essentials: the lack of Exchange and SharePoint.
On the other hand, Windows Server 2012 Essentials running on the right hardware can provide small businesses with everything they need to continue managing most of their IT infrastructure from one box. It may not be as simple to set up, but it does offer greater flexibility for small businesses to choose on-premises or cloud-based solutions, migrate from one to the other, or rely on a hybrid of both.
But we are not here to talk about Windows Server 2012 Essentials, but instead explore the new Windows Server 2012 R2 Essentials Experience Role.
Advertisement

Windows Server 2012 R2 Essentials Experience Role

Windows Server 2012 R2 Essentials is an ideal first server for small businesses with up to 25 users and 50 devices. For organizations with up to 100 users and 200 devices, we can now use a Windows Server 2012 R2 server with theWindows Server Essentials Experience role installed.
This role, which can be installed on a “normal” Windows Server 2012 R2 Standard or Datacenter edition server, has the following limitations:
Windows Server 2012 R2 EssentialsEssentials Experience role in Windows Server 2012   R2
Must be the domain controller at the root of the forest and domain, and must hold all the FSMO roles.Does not have to be a domain controller if it is installed in an environment with a pre-existing Active Directory domain.
Cannot be installed in an environment with a pre-existing Active Directory domain.If an Active Directory domain does not exist, installing the role will create an Active Directory domain, and the server will become the domain controller at the root of the forest and domain, holding all the FSMO roles.
Can only be deployed into a single domain.Can only be deployed into a single domain.
A read-only domain controller cannot exist in the domain.A read-only domain controller cannot exist in the domain.
Table 1
Image A major disadvantage that existed   until very recently, was that the online services integration features of the Essentials Experience role, including Azure Active Directory and Office   365, were only supported in environments with a single domain controller...   In environments with more than one domain controller, integration of these   services was blocked due limitations in the user account and password   synchronization mechanism. This has finally been overcome with the release of   the Windows August Update, which added support for both Azure Active   Directory integration and Office 365 integration features in domain   environments consisting of a single domain controller, multiple domain   controllers, or Windows Server Essentials as a domain member server. For more   information, please refer to http://support.microsoft.com/kb/2974308.
When we install the Windows Server Essentials Experience role, we can take advantage of all the features that are available in Windows Server 2012 R2 Essentials without the locks and limits enforced in it. It enables organizations to:
  • Protect servers and clients’ data by backing up servers and client computers within the network using Windows Azure Backup;
  • Manage users and groups through the server’s Dashboard. In addition, integration with Windows Azure Active Directory enables easy data access for Microsoft online services users (such as Exchange Online and SharePoint Online users) through their domain credentials (password sync);
  • Store company’s data in a centralized location;
  • Integrate with Microsoft online services such as Exchange Online, SharePoint Online and Windows Intune:
    • Integration with Office 365 enables administrators to synchronize and manage Office 365 user accounts and access through the Dashboard;
    • Integration with SharePoint Online enables administrators to create and manage SharePoint libraries through the Dashboard.
  • Use the Anywhere Access functionalities on the server (such as Remote Web Access and virtual private networks) to access the server, network computers and data from remote locations in a highly secure manner;
  • Access data from any location and on any device by using the company’s customized web portal (through Remote Web Access);
  • Manage ActiveSync mobile devices that access company’s e-mail by using Office 365;
  • Monitor network health and obtain customized health reports.
As the title of this article suggests, we are going to explore how to manage Exchange Online using the Windows Server Essentials Experience role.

Essentials Experience Role and Office 365

Windows Server 2012 Essentials and the Essentials Experience role build on the previous Office 365 Integration Module for SBS 2011 Essentials. This option is now part of the core product (not a separate download) and provides a seamlessly integrated management experience on Essentials for customers who are using Exchange Online.
On top of the core feature set that was included in the Office 365 Integration Module for SBS 2011 Essentials, such as integrated user account management and automatic user password synchronization, Microsoft also made a few enhancements to make the experience better:
  • Support for multiple e-mail addresses. Having multiple domains and/or assigning multiple e-mail addresses to a single user are common scenarios even for small businesses. Now it is finally possible to easily do that from within the Essentials’ Dashboard;
  • Improved Office 365 domain configuration wizard. In the Office 365 Integration Module for SBS 2011 Essentials, administrators were required to configure Remote Web Access (RWA) when configuring a domain for Office 365, which caused a lot of confusion. For example, administrators had to provide an SSL certificate which was not actually needed by Office 365, but was required by RWA. Now these two have been de-coupled. Another improvement is the option to configure a different domain name for Office 365 and for RWA, allowing small businesses to continue to use the same free domain names like letsexchange.remotewebaccess.com for RWA on Essentials and a different domain name for e-mail in Office 365;
  • Display mailbox usage information. The Office 365 tab on the Essentials Dashboard now shows the mailbox usage information.
Now that we know what the Windows Server 2012 R2 Essentials Experience Role is, in the next article we will be installing it and integrating it with Office 365.

Conclusion

In the first part of this article series, we started by looking at Windows Server 2012 Essentials and the new Windows Server 2012 R2 Essentials Experience Role. In the next part, we will be installing it and integrating it with Office 365.

Tuesday, October 28, 2014

Managing Exchange Online using Server 2012 R2 Essentials Experience Role (Part 1)

Introduction

Microsoft announced Windows Server 2012 Essentials back in the summer of 2012 as the next version of what used to be called Small Business Server (SBS) Essentials. This was, in many ways, the end of an era.
SBS was very popular as it was without a doubt a great platform: it contained in one box all of the elements a business could need such as the server’s operating system and management tools, together with SharePoint Server and Exchange Server. However, the two main problems with SBS were its 25 licenses limit and the fact it did not provide an easy upgrade path for companies once their needs grew larger than what SBS could handle.
Since SBS 4.0 launched back in 1997, e-mail functionality was provided in all versions of SBS by having Exchange Server installed on the SBS box itself. Eventually, this changed when Microsoft divided SBS 2011 into Standard (with Exchange built-in) and Essentials (without Exchange built-in).
Windows Server 2012 Essentials has been designed to work with three different types of e-mail systems:
  • Office 365;
  • Hosted Exchange;
  • On-premises Exchange.
The first two are very much what SBS 2011 Essentials was also designed to do. Through add-ins in the Essentials console, administrators could manage a large part of the e-mail system even though it was hosted in the cloud. The last one, however, is different as on-premises Exchange is not Exchange built into the SBS server itself, but a separate Exchange server. This has been the biggest complaint about Windows Server 2012 Essentials: the lack of Exchange and SharePoint.
On the other hand, Windows Server 2012 Essentials running on the right hardware can provide small businesses with everything they need to continue managing most of their IT infrastructure from one box. It may not be as simple to set up, but it does offer greater flexibility for small businesses to choose on-premises or cloud-based solutions, migrate from one to the other, or rely on a hybrid of both.
But we are not here to talk about Windows Server 2012 Essentials, but instead explore the new Windows Server 2012 R2 Essentials Experience Role.
Advertisement

Windows Server 2012 R2 Essentials Experience Role

Windows Server 2012 R2 Essentials is an ideal first server for small businesses with up to 25 users and 50 devices. For organizations with up to 100 users and 200 devices, we can now use a Windows Server 2012 R2 server with theWindows Server Essentials Experience role installed.
This role, which can be installed on a “normal” Windows Server 2012 R2 Standard or Datacenter edition server, has the following limitations:
Windows Server 2012 R2 EssentialsEssentials Experience role in Windows Server 2012   R2
Must be the domain controller at the root of the forest and domain, and must hold all the FSMO roles.Does not have to be a domain controller if it is installed in an environment with a pre-existing Active Directory domain.
Cannot be installed in an environment with a pre-existing Active Directory domain.If an Active Directory domain does not exist, installing the role will create an Active Directory domain, and the server will become the domain controller at the root of the forest and domain, holding all the FSMO roles.
Can only be deployed into a single domain.Can only be deployed into a single domain.
A read-only domain controller cannot exist in the domain.A read-only domain controller cannot exist in the domain.
Table 1
Image A major disadvantage that existed   until very recently, was that the online services integration features of the Essentials Experience role, including Azure Active Directory and Office   365, were only supported in environments with a single domain controller...   In environments with more than one domain controller, integration of these   services was blocked due limitations in the user account and password   synchronization mechanism. This has finally been overcome with the release of   the Windows August Update, which added support for both Azure Active   Directory integration and Office 365 integration features in domain   environments consisting of a single domain controller, multiple domain   controllers, or Windows Server Essentials as a domain member server. For more   information, please refer to http://support.microsoft.com/kb/2974308.
When we install the Windows Server Essentials Experience role, we can take advantage of all the features that are available in Windows Server 2012 R2 Essentials without the locks and limits enforced in it. It enables organizations to:
  • Protect servers and clients’ data by backing up servers and client computers within the network using Windows Azure Backup;
  • Manage users and groups through the server’s Dashboard. In addition, integration with Windows Azure Active Directory enables easy data access for Microsoft online services users (such as Exchange Online and SharePoint Online users) through their domain credentials (password sync);
  • Store company’s data in a centralized location;
  • Integrate with Microsoft online services such as Exchange Online, SharePoint Online and Windows Intune:
    • Integration with Office 365 enables administrators to synchronize and manage Office 365 user accounts and access through the Dashboard;
    • Integration with SharePoint Online enables administrators to create and manage SharePoint libraries through the Dashboard.
  • Use the Anywhere Access functionalities on the server (such as Remote Web Access and virtual private networks) to access the server, network computers and data from remote locations in a highly secure manner;
  • Access data from any location and on any device by using the company’s customized web portal (through Remote Web Access);
  • Manage ActiveSync mobile devices that access company’s e-mail by using Office 365;
  • Monitor network health and obtain customized health reports.
As the title of this article suggests, we are going to explore how to manage Exchange Online using the Windows Server Essentials Experience role.

Essentials Experience Role and Office 365

Windows Server 2012 Essentials and the Essentials Experience role build on the previous Office 365 Integration Module for SBS 2011 Essentials. This option is now part of the core product (not a separate download) and provides a seamlessly integrated management experience on Essentials for customers who are using Exchange Online.
On top of the core feature set that was included in the Office 365 Integration Module for SBS 2011 Essentials, such as integrated user account management and automatic user password synchronization, Microsoft also made a few enhancements to make the experience better:
  • Support for multiple e-mail addresses. Having multiple domains and/or assigning multiple e-mail addresses to a single user are common scenarios even for small businesses. Now it is finally possible to easily do that from within the Essentials’ Dashboard;
  • Improved Office 365 domain configuration wizard. In the Office 365 Integration Module for SBS 2011 Essentials, administrators were required to configure Remote Web Access (RWA) when configuring a domain for Office 365, which caused a lot of confusion. For example, administrators had to provide an SSL certificate which was not actually needed by Office 365, but was required by RWA. Now these two have been de-coupled. Another improvement is the option to configure a different domain name for Office 365 and for RWA, allowing small businesses to continue to use the same free domain names like letsexchange.remotewebaccess.com for RWA on Essentials and a different domain name for e-mail in Office 365;
  • Display mailbox usage information. The Office 365 tab on the Essentials Dashboard now shows the mailbox usage information.
Now that we know what the Windows Server 2012 R2 Essentials Experience Role is, in the next article we will be installing it and integrating it with Office 365.

Conclusion

In the first part of this article series, we started by looking at Windows Server 2012 Essentials and the new Windows Server 2012 R2 Essentials Experience Role. In the next part, we will be installing it and integrating it with Office 365.

Tuesday, October 7, 2014

Exchange server has failed to heartbeat error after uninstalling Exchange

This tip explains how to overcome an error raised by a bug when uninstalling Exchange 2013.
When you uninstall Exchange 2013, you might encounter the following error in the Event Log regarding the Managed Availability’s monitoring agent complaining that the server you uninstalled is not available:
Log Name: Microsoft-Exchange-ManagedAvailability/Monitoring
Source: Microsoft-Exchange-ManagedAvailability
Event ID: 4
Task Category: Monitoring
Level: Error
Description: Machine “uninstalled_server” has failed to heartbeat since “unistalled_date_and_time”, as observed by machine “some_other_server”. Restarting the Exchange Health Manager service did not fix the problem.
The problem is that the old server continues to be present under the following registry key for all other Exchange Servers:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v15\ActiveMonitoring\Subjects
This causes the error above in the Event Log or SCOM alerts. If this happens, the workaround is to simply delete the old server(s) from the registry key mentioned above on the remaining servers.
Microsoft says that this bug was previously closed as Won’t Fix but that they have re-opened it for re-triage.

How to find out your Windows or Microsoft Office product key: Locate the licence code for Microsoft's software suites and operating systems

Having trouble with lost Microsoft product keys? Here's our guide on how to get them back

How to find out your Microsoft Office Product Key

Locating your product keys when installing Windows or software suites such as Microsoft Office can be an absolute pain. How many of us have thrown away the packaging for a piece of software, only to realise that we’ve discarded a vital code with it? Should you find yourself in this situation, however, never fear: we’ve compiled a handy how-to to solve your product-key problems. Also see: Windows 10 preview.

How to find out your Windows or Microsoft Office product key: Step One

Trying to locate a product key by yourself is a nightmare - even if you manage to hunt through your computer’s Registry to find it, the code itself is encrypted. Luckily, there are a plethora of third-party programs that will do all the legwork for you.
Our favourite of these is ProduKey, a small application that will delve into the Registry to fish out and decrypt your product key. The file size is tiny, meaning it won’t take long at all to download and run.
How to find out your Microsoft Office Product Key

How to find out your Windows or Microsoft Office product key: Step Two

Once downloaded, simply run it once and it will immediately display the product keys of any Microsoft Office software up to 2013, as well as the keys of operating systems such as Windows Vista, 7 and 8. Then you can either copy the keys for future use, or export them to a HTML file for digital storage.

Tuesday, September 2, 2014

Managing mailbox features with corporate profiles

Managing mailbox features with corporate profiles (Part 1)

by  [Published on 12 Aug. 2014 / Last Updated on 12 Aug. 2014]
In this new article series, the author goes over the process of creating corporate profiles, which will be then used to manage a larger number of mailboxes from a central location.
If you would like to read the next part in this article series please go to Managing mailbox features with corporate profiles (Part 2).

Introduction

When managing an Exchange Server environment with hundreds to thousands of mailboxes, the process to keep consistency among servers and mailboxes can be challenging.
If we look on the server side, Exchange Server 2013 is all about to scale out, which means if we need more horsepower to keep the business going we can add more servers to the current infrastructure and that will spread the load among more servers, improving resiliency and so forth.
Now, if we look on the operations side, the challenge is that we always have more mailboxes being added to the exchange organization and in some companies that process takes a lot of time in manual processes by the Service Desk team.
The business, as usual, wants to do more with less and that is going to be the goal for this series. We will focus on this requirement and in the first article - how we can create profiles that later on will be assigned to the mailboxes. The new profiles will enforce features and/or restrictions to the mailboxes from a central location and by doing that we can save time from the Service Desk team.
There are several ways and tools to do that, and we are going to focus on how using corporate profiles and a couple of simple PowerShell scripts will help us achieve our goals.
In order to understand this series better, we will use the following scenario: we have an Exchange Organization with 5000+ mailboxes and after having discussions with the Legal department and upper management we decided to apply certain features/restrictions based on profiles that we will defined in this first article. The ultimate goal is to reduce the work to manage several users to a simple task from a central location.
Advertisement

Profile definition…

The profile definition process is critical for any company that is looking to keep consistency of settings among several mailboxes. A profile is a logic classification that will be assigned to the mailboxes and based on the profile, features and/or restrictions will be applied to mailboxes.
The advantage of using profiles is that the exchange administrator is able to manage from a central location a larger number of objects without the need of manual intervention.
The profile definition is key to define the future naming convention for Exchange objects and to define features/limits values for the future users that will be associate to the profile.
In order to keep consistency make sure that you create enough profiles to accommodate all your short and long term requirements, or at least plan to have enough room to support any growth on the structure down the road.
Based on my experience, what will be our worst enemy are the exceptions and for that, my recommendation is always to keep within the existent profiles instead of creating exceptions on a specific feature. In addition, if you see an expressive number of users asking the same thing, then you should start planning to change an existent profile or create a new profile to accommodate the new requirements but keep the standard in place at all costs.
The name for the profiles is also important because ideally you will name all other objects with a name that allows you to match the profile with a feature. The decision about the profile names is up to you. We can provide some definitions being used out there, such as REG (Regular), MED (Medium) and VIP; you can use army hierarchy, perhaps regions based on George Orwell’s book 1984 (Eurasia, Eastasia and Oceania). Well, we are going to keep it simple in this series, and we will be using GoldSilver and Bronze.

Creating the Exchange objects and some research…

Now that we have the name for the corporate profiles, we need to start defining features/restrictions for each profile.
In a real-world scenario, this kind of definition should be done with Security, Legal and upper-management and that usually involves creating a corporate policy informing all users before the exchange administrator can do anything on the server side.
When Legal department is involved in the process, then we have a great opportunity to apply e-mail life cycle using retention policies to archive and purge items based on the profile and this kind of exercise with different departments helps a lot.
In our scenario, after several sessions with our imaginary legal and security teams, we defined the following key features to be applied to the users and their values will vary based on the type of profile:
  • Outlook client (MAPI feature)
  • Single Item Recovery
  • Retention Policy
  • OWA Policy
  • Maximum number of recipients
Important note:
Some features/restrictions may use different object limits instead at the mailbox level. A good example is the maximum number of recipients where Exchange offers global limits. If the decision was to keep a lower number for all users, then our recommendation is to change the Global setting.
The same applies for Mailbox Database limits. I personally recommend using the Mailbox Database limits and keeping all mailboxes in a mailbox database that matches the profile. A good example would be one or more databases for Gold profile and only mailboxes assigned to the Gold profile would be stored in such databases.

Finding out the information to change some attributes...

At this point, we have some research to do to find out which cmdlets and attributes are required to define the features that will be applied to the corporate profiles. Exchange Server 2013 Service Pack 1 introduced a feature called Show Command Logging (Figure 01) which will help us a lot to find out the specific settings that will be part of our future profiles.
Image
Figure 01
A new window (Figure 02) will be displayed and any changes that we perform in the EAC (Exchange Admin Center) will be listed in this new window, but that window must be opened at all times, for now we will minimize it and go back to the EAC.
Image
Figure 02
The next step is to use a dummy account and change a feature that is part of the policy. At this point we do not care about the value itself but we are interested in finding out the cmdlet and the attribute. In the example shown in Figure 03, we are changing the Maximum recipients to 30 for our test account. We must make sure to save the settings to have the information logged on the Show Command Logging window.
Image
Figure 03
After completing the change on the test account, we can go back to the Show Command Logging page and all cmdlets used in the EAC will be displayed there.
Note:
The Show Command Logging will show all cmdlets of the current session, since we are changing settings our best chances to find the information is looking for verbs in our cmdlets that produce changes, such as: set, add, new and so forth.
In the Figure 04, we can see the entry Set-Mailbox and if we select and look at the bottom, we will have the entire cmdlet and the parameters used. That was the cmdlet performed in the background when we updated our dummy account. Our task is to record that in order to change the recipient limit. For any given user we need to use the Set-Mailbox cmdlet and the attribute is RecipientLimits
Image
Figure 04

Conclusion

In this first article, we defined the corporate profiles and the initial features/restrictions that will be part of those profiles. We also started the research to find out the cmdlets and attributes required for each feature listed, and that will be important when we start centralizing such changes.
If you would like to read the next part in this article series please go to Managing mailbox features with corporate profiles (Part 2).