When you’ve configured mailbox quota’s within your Exchange 2010/2013 environment, you’ve to check the configuration sometimes. Using Microsoft PowerShell, you can watch the current configuration within a few second, so this is extremely powerfull!! But, when you have to query for some specific user or result, it’s not that easy.
There’s a very usefull command within PowerShell that I’m using almost for all my scripts….Out-GridView. When using the parameter Out-GridView, the results are not showing within the PowerShell screen, but in a separate window! Within this window, you can very easy add some search criteria….for example: specific user, quota or an overview per database.
One requirement is that the Windows Feature “Windows PowerShell Integrated Scripting Environment (ISE)” is installed on the Exchange servers or mangement server from where you’re running the commands.
1.) Open the Exchange Management Shell (EMS)
2.) For an overview of the current mailbox quota, use the following command.
Get-Mailbox -Identity mswinkels | ft Name, IssueWarningQuota, ProhibitSendQuota, ProhibitSendReceiveQuota
3.) The results of this command is shown within the PowerShell window
4.) Now we’re running the same command, but replace “ft” (format-table) with “select” and add the parameter “Out-GridView”
Get-Mailbox -Identity mswinkels | Select Name, IssueWarningQuota, ProhibitSendQuota, ProhibitSendReceiveQuota | Out-GridView
5.) Now the results are in a separate window! Extreme usefull when you’ve have to search for a specific result or results.
When you setup coexistence with Microsoft Exchange 2010 and 2013, you can manager you mailbox databases in different ways. Though the Exchange Management Console (EMC), Exchange Control Panel (ECP) or with Exchange Management Shell (EMS). Today I had to configure a new Microsoft Exchange 2013 environment in a existing Exchange 2010 environment, so this is a coexistence infrastructure.
When I had installed the new Exchange 2013 servers, and I had started the Exchange Management Shell (EMS) from the new Exchange 2013 server, I saw only the new Exchange 2013 database. But wait a minute, I had also a copple of mailbox databases configured on my existing Exchange 2010 environment. In the Exchange Control Panel (ECP), all the databases are visseble, but why not in the Exchange Management Shell?
The solution is pretty easy. Within Exchange 2013 there’s a new parameter that you can use with the Get-MailboxDatabase command. So the new parameter is -IncludePreExchange2013. The whole command should be: Get-Mailboxdatabase -IncludePreExchange2013.
Kemp announced Firmware release LoadMaster 7.0-4. Now Microsoft has announced that the support for Microsoft TMG will stop, we have to look further for an reverse proxy solution. Ofcource there is Microsoft UAG, but with the new Edge Security Pack for KEMP Load Master, it is now possible to configure reverse proxy within the load balancers! Here you can view the new announcement from KEMP Technologies!
New Features and Feature Enhancements:
•Edge Security Pack – A range of new security features has been added to the LoadMaster.
•Sub-VS Support – The LoadMaster now supports the creation and management of sub-VSs.
•Graphical Metrics – There is a new dashboard home screen with the capability to display graphical performance information.
•New License format – A new license format has been introduced
•Oracle VirtualBox VLM – A new VLM package, to support VLM installation within an Oracle VirtualBox environment is available
•MIBS files have been updated
•SID and revision information included in IPS logging
•VLAN Separation per Interface •Support for larger TCP window sizes
•‘Kill switch’ is now supported on all LoadMaster versions
•LM-R320 has its serial number visible on the WUI
•The Netconsole Host interface is configurable via the WUI
•Issue with SMTP STARTTLS when a client sends an EHLO is resolved
•Issue with ACL whitelist allowing other IPs is resolved
•Issue with switching VS types under load is resolved
•Some reboot issues have been resolved
•An issue with caching on Firefox has been resolved
•The “-“ character is now allowed in the DNS Search Domain field
•Issues with the MIBS have been resolved
•A circular routing problem has been resolved
•SNMP trap Source IP has been changed to pre 5.1-48 behaviour
•SSL renegotiation can be toggled on/off
•SSLv2 is no longer used for LoadMaster initiated SSL connections
•An issue with Not Available Redirection XSS has been resolved
•The Default IP is now displayed on the WUI when DHCP fails
•An issue with VS Specific insert X-Clientside header being overwritten by system default has been resolved
•The “-“ character is now allowed in the User Login field
•An issue with the Fail on Match functionality has been resolved
•An issue with Maximum Cache Size has been resolved
• Quick setup Help appears automatically if no IP address is configured on the LM if a VLAN is configured on eth0 and no IP address is assigned to the underlying interface (eth0)
LoadMaster version v7.0-4 supports the following hardware:
NOTE – ESP is supported on select LoadMaster models and new VLM installations.
Learn more about LoadMaster 7.0:
Full Release Notes
Yesterday, the Microsoft Exchange Team has released Cumulative Update 1 for Exchange 2013 RTM. CU1 is the minimum version of Exchange 2013 required for on-premises coexistence with supported legacy Exchange Server versions. The final build number for CU1 is 15.0.620.29.
This is the Exchange 2013 product level required for co-existence with previous versions of Exchange, being Exchange Server 2010 SP3 or Exchange Server 2007 SP3 Rollup 10.
The Exchange Team provided a description of the major changes in CU1. You will find the announcement here;
Here are some of the major changes in CU1:
- Includes Address Book Policy Routing Agent (info);
- Allows group memberships to be managed by groups (again, as it was possible in Exchange 2007 but not in Exchange 2010);
- Access to Public Folders you have added as favorites via your favorites menu either in Outlook or Outlook Web App (still no regular Public Folder tree access though);
- EAC has been enhanced and now includes Unified Messaging management and migration options;
- Many probes, monitors, and responders have been updated and improved over the RTM release;
- Get-HealthReport cmdlet has been streamlined and its performance has been optimized;
- Supports the Exchange Server 2013 Management Pack for SCOM 2007 R2 and SCOM 2012 (due at a later date);
- High Availability changes
You can download Cumulative Update 1 for Exchange 2013 here.
Be aware, this update requires some preparation first. So be carefull and read the release notes before hitting the install button 😉
Yesterday, Microsoft has released the new version of the Posterpedia App. This is very nice app, available in the Windows store. Server Posterpedia is an interactive app that uses technical posters as a reference for understanding Microsoft technologies.
There are posters available for Microsoft Hyper-V, Exchange, Server 2008, SharePoint, Windows Azure, SQL, etc.
You can download the app using the following URL: http://blogs.technet.com/b/windowsserver/archive/2012/11/20/server-posterpedia-v2-available-in-the-windows-store.aspx or in the App Store!
When you’ve moved an mailbox database, the old catalog data is still present on the old partition. This prevents deleting the specific partition. When you try to delete those files, you receive this error.
The Catalog data folder stays in place after a database move path action. The folder couldn’t be cleaned up because it is in use by the Microsoft Exchange Search Indexing service
First we have to temporarely disable the indexing on the particular mailbox database. Then we stop the indexing service of Exchange so we can delete the remaining files. The last step is to enable the indexing again.
You can follow the next steps.
– Open the Exchange Management Shell and run the following command:
Set-MailboxDatabase -Identity databasename -IndexEnabled $false
-Before moving / cleaning the catalog files, stop the service Microsoft Exchange Search Indexer
– Move the catalog files to the new database location or clean them up.
– Start the service Microsoft Exchange Search Indexer
– Open the Exchange Management Shell and run the following command:
Set-MailboxDatabase -Identity databasename -IndexEnabled $true
Today I need to configure Role Based Access Control (RBAC) within Exchange 2010. The people on the helpdesk department must be able to set Send-As permissions on the mailboxes. To configure RBAC within Exchange 2010, you can use the RBAC User Editor from the Exchange 2010 toolbox.
Default there are a few pre-configured management roles, each with his own rights and permissions. In my case I added the people from the Helpdesk department in the “Recipient Management” role group. But for setting Send-As permissions, they need some rights more to perform this action.
With the following command, you can extent the role group “Recipient Management” with the Send-As permissions, so they are able to configure Send-As permissions on a specific mailbox. The case in this one is that the Send-As permission is a Active Directory permission, so they also need the role “Active Directory Permissions”.
New-ManagementRoleAssignment -Name “ADPermissions Recipient Mgmt” -Role “Active Directory Permissions” -SecurityGroup “Recipient Management”
Get-ManagementRole “Active Directory Permissions” | fl
Get-RoleGroup -Identity “Recipient Management” | fl
Now the members of the role group “Recipient Management” have also the ability to change or configure Send-As permissions. You can also do this through the GUI by dubble-click on the group “Recipient Management” and add the specific management role. See the screenshots below.
To obtain an overview of the whitespace within a mailbox database in Exchange 2010, you can use the following command:
Get-MailboxDatabase -Status | Select-Object Server,Name,AvailableNewMailboxSpace
Whit this new option, it’s possible to see when you’ve to perform an offline defragmentation of your Exchange mailbox databases. To perform an defragmentation, it is still necessary to put the databases offline.