Browsing "Exchange"
Jul 19, 2014 - Exchange    No Comments

Generate HTML Mailbox Size and Usage Report using PowerShell for Exchange 2010 / 2013

Here is a nice way to see who is using up the most space on your mailbox servers.

 

Get-Mailbox -ResultSize Unlimited | Get-MailboxStatistics | Select DisplayName,TotalItemSize,ItemCount,
Database,LastLogonTime,LastLoggedOnUserAccount |
SortTotalItemSize -Descending |
ConvertTo-Html -Title "Mailbox Stats"|Out-file "C:\MailboxStatistics.html

Apr 11, 2014 - Exchange, General    No Comments

How to reset the Search Index in Exchange 2010 Search

Exchange 2010 has a built in search feature which allows you to quickly search for emails in your mailbox using Outlook (when Online), OWA, Exchange ActiveSync etc. Exchange 2010 search indexes items as soon as they are received by the Mailbox Database. So if you’ve just transitioned from Exchange 2003 to 2010, Exchange may not index items brought over from the Exchange 2003 server to the Exchange 2010 server. You may find that users using Exchange search may have issues searching for items that were in their mailbox before the transition. For example, you will not be able to find a pre-transition item using instant search but will be able to find them using ‘Advanced Find’ in Outlook.

To fix this issue, you will have to reset the search index to force the Exchange Search service to index all items in the Mailbox Database including items that were moved to the database from Exchange 2003.

To reset the search index, open up the Exchange Management Shell navigate to %PROGRAMFILES%\Microsoft\Exchange Server\V14\Scripts and then run the following command:

.\ResetSearchIndex.ps1 -force -all

You should see output that resembles the following:

WARNING: Waiting for service 'Microsoft Exchange Search Indexer (MSExchangeSearch)' to finish stopping...
MSExchangeSearch service stopped
Deleting catalog for Mailbox Database
removing: <location of catalogue>

MSExchangeSearch service Started

To verify that the rebuilding of the index has completed do the following:

  1. Add this counter to Perfmon: MSExchange Search Indices\Full Crawl Mode Status. This counter will be 0 before running ResetSearchIndex, go to 1 during the full crawl and then back to 0 after ResetSearchIndex completes.
  2. You will receive MSExchange Search Indexer Event ID 109 when the full crawl begins.
  3. You will receive MSExchange Search Indexer Event ID 110 when the full crawl ends.

You should now be able to search for pre-transition items using Exchange searc

 

Jul 1, 2013 - Exchange, General    No Comments

How can I stop Outlook 2010 from automatically mapping all my full-access mailboxes ?

In Exchange 2010 Service Pack 1 (SP1) Exchange introduced a feature that allows Outlook 2007 and Outlook 2010 clients to automatically map to any mailbox to which a user has Full Access permissions. If a user is granted Full Access permissions to another user’s mailbox or to a shared mailbox, Outlook automatically loads all mailboxes to which the user has full access.

This is a great time saver for help-desks, as in the past they had to constantly advise users how to add additional mailboxes to their profiles.

However, if you do have full access to a large number of shared / team mailboxes, this can cause performance issues with Outlook, especially during boot up.

In Exchange 2010 SP1, there was no way to turn this feature off. However, in Exchange 2010 SP2, you can use the Shell to disable this feature:

Add-MailboxPermission -Identity BillG -User ‘Ali Butt’ -AccessRight FullAccess -InheritanceType All -Automapping $false


This example grants me full access permission to BillG mailbox and disables the auto-mapping feature.




Jun 22, 2013 - Exchange    No Comments

Exchange 2010 servers constantly showing Event ID 1069 and 1558.

If you are getting events 1558 and 1069 stating “The cluster service detected a problem with the witness resource” every 15 minutes, there is now an official fix from Microsoft. I noticed an issue like this at a previous client who had a 6 node Exchange 2010 fail over cluster with 1 file share witness.

Log Name: System

Source: Microsoft-Windows-FailoverClustering

Event ID: 1069

Task Category: Resource Control Manager

Level: Error

User: SYSTEM

Computer: node01.ali-lab.com

Description: Cluster resource ‘File Share Witness (\\node02.ali-lab.com\DAG.ali-lab.com)’ in clustered service or application ‘Cluster Group’ failed. Read more »

May 9, 2013 - Exchange    No Comments

Top 5 admin tools for Exchange Deployments and Migrations

Time to dig out some favourites from my browser and share the top Exchange admin tools / sites …

Mailbox Server Role Requirements Calculator – Helps you properly design Mailbox servers for your environment,
http://blogs.technet.com/b/exchange/archive/2009/11/09/3408737.aspx

Exchange Remote Connectivity Analyzer (ExRCA) – Provides a test system for administrators to use to validate external connectivity to Exchange. Essential for testing your activesync / autodiscover deployments !
https://www.TestExchangeConnectivity.com

Microsoft Active Directory Topology Mapper – Reads Active Directory configuration using LDAP, and automatically generates a Visio diagram of your Active Directory and/or Exchange topology,
http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=13380

Exchange Server Deployment Assistant (ExDeploy) – Generates custom instructions for moving your organization to Exchange 2010 or Office 365,
http://technet.microsoft.com/en-us/exchange/jj657516

Exchange Client Network Bandwidth Calculator – Helps you predict network bandwidth requirements for a specific set of clients,
http://gallery.technet.microsoft.com/Exchange-Client-Network-8af1bf00

 

I know I said 5, but this one is too good to ignore !…

Microsoft Active Directory Topology Mapper – Reads Active Directory configuration using LDAP, and automatically generates a Visio diagram of your Active Directory and/or Exchange topology,
http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=13380

Mar 13, 2008 - Exchange    No Comments

How do I disable Exchange Server 2003 minor link-state changes?

Exchange 2003 can detect link state changes, notify other Exchange servers about the changes, and advise them to use other routes. A minor state change is when a link is detected as either available or unavailable. The notification actually sends the entire state table. A major state change is an administrator-made manual routing change, such as adding a new connector or changing an existing connector’s attributes.

Sometimes, minor state change notifications are undesirable, such as when the notification sending of the entire state table could flood a network. This could happen in a large Exchange environment. It could also happen in a combined Exchange Server 2007and Exchange 2003 environment with multiple routing group connectors between routing groups and different Exchange 2003 bridgeheads in different routing groups.

To disable minor link state changes, use the following commands on each Exchange 2003 server:

1. Start the registry editor (regedit.exe).
2. Navigate to HKEY_LOCAL_MACHINESystemCurrentControlSetServicesRESvcParameters.
3. From the Edit menu, select New – DWORD value.
4. Enter as a name SuppressStateChanges and press Enter.
5. Double click the new value and set the value to 1, then click OK.
6. Close the registry editor and restart the SMTP, Microsoft Exchange Routing Engine, and the Microsoft Exchange MTA Stacks services.

Windows Update Error 0xC80003FB

Click Start, select Run, type in: services.msc
then press enter
Now look for the Automatic Updates Service, right click it and choose to stop

Click Start, select Run, type in: %windir%SoftwareDistribution
then press enter
Open the Datastore folder and delete its contents.

Click Start, select Run, type in: type services.msc
then press enter
Now look again for the Automatic Update Service and choose to start

Try running the Updates again.

Can I still use Microsoft Virtual Server or Microsoft Virtual PC to test Windows Server 2008 clustering?

Virtual Server has commonly created a shared disk over the emulated SCSI controller to use for clustered storage. However, Server 2008 clustering doesn’t support parallel SCSI.

But there is light at the end of the tunnel. Server 2008 clustering supports the majority node set model, which means a cluster doesn’t need shared storage. Server 2008 can use node-voting with three nodes or more, or a file-share witness instead of the quorum disk for two-node clusters.

If you want shared storage, the easiest option is probably iSCSI because the iSCSI initiator is built into both Server 2008 and Windows Vista. For the iSCSI target, you may have access to an iSCSI SAN/device, a software solution such as Windows Storage Server, or an add-on iSCSI

Aug 20, 2007 - Exchange, General, Windows 2003    1 Comment

I changed the IP address of a server running the SMTP service, but I can’t send mail to it locally. What’s the problem?

t’s common to install the SMTP service on servers that require limited mail-sending capabilities–for example, on a Microsoft SharePoint server. I recently had a problem in which the box got a new IP address, and at that point the services that used the SMTP service could no longer send email. The problem was that the server had a relay restriction list in place, and the list didn’t have the new IP address listed.

To resolve the problem, you need to update the relay list. Start the Microsoft Management Console (MMC) Internet Information Services Manager snap-in by accessing Start, Programs, Administrative Tools, Internet Information Services (IIS) Manager. Right-click the SMTP virtual server and select Properties, then select the Access tab. Click the Relay button. Be sure to add the IP address of the server trying to connect or a subnet containing the servers trying to send via the server by clicking the Add button. When you’re finished, click OK on all dialog boxes.

Jul 20, 2007 - Exchange, Windows 2003    No Comments

What’s the new transaction log size in Microsoft Exchange Server 2007?

The transaction log size in Exchange 2007 is now 1MB instead of 5MB, which was the transaction log size for Exchange 2003. The reason for the size reduction is related to the new log shipping clustering technologies in Exchange 2007. The smaller the log file means a smaller amount of data loss because you can’t ship a transaction log until it’s closed and it needs 5MB of data written before you can close. With Exchange 2007, you only need 1MB of data written. In addition to the reduction of size of the transaction logs the naming scheme has been changed from E<2 digit storage group identifer><5 hexidecimal digits> to E<2 digit storage group identifer><8 hexidecimal digits> which means even though there will be five times the number of transaction logs the number of transaction logs you can have in total is over two thousand times the number of transaction logs you could previously have under Exchange 2003 (you don’t go all the way up to ffffffff, rather 7fffffec).

Related Posts Plugin for WordPress, Blogger...
Pages:1234»