Exchange 2013

  • Home
  • Tag: Exchange 2013

Exchange 2013 – Delete all contents from mailbox

Using the following Exchange Management Shell command you can cleanup emails from a mailbox such as one used to catch spam emails:

You can also check the number of items in the mailbox by issues the following command:

 

By |How-To, Technical|0 Comments
Read More

Tech Short: Convert a Mailbox, Exchange 2013

Here are some steps that worked for me in converting a user mailbox to a shared mailbox.

Info: You can convert the following mailboxes from one type to another

  • User mailbox to resource mailbox
  • Shared mailbox to user mailbox
  • Shared mailbox to resource mailbox
  • Resource mailbox to user mailbox
  • Resource mailbox to shared mailbox

Example reason why you might wan’t to do this:

You have a mailbox account with the name of  bookclub and are looking make it a shared account because its consuming a license. To address this we will convert it to a shared mailbox account by issues the following commands in the Exchange Management Shell

 

If you have multiple accounts, the following steps may apply to you

 

Please note the following csv document formatting:

Ref: http://technet.microsoft.com/en-us/library/jj710164%28v=exchg.150%29.aspx

 

By |How-To|0 Comments
Read More

Tech Short: List Mailbox Type of Account, Exchange 2013

Quick an simple power shell line to list a mailbox type in the Exchange 2013 environment

 

Additional info on RecipientTypeDetails enumeration can be located here

By |How-To|0 Comments
Read More

Tech Short: List all shared mailboxes, Exchange 2013

Quick an simple power shell line to list all shared mailboxes in your Exchange 2013 environment.

 

What’s a Shared Mailbox

A shared mailbox is a mailbox that multiple users can use to read and send email messages. Shared mailboxes can also be used to provide a common calendar, allowing multiple users to schedule and view vacation time or work shifts. ref: http://technet.microsoft.com/en-us/library/jj150498%28v=exchg.150%29.aspx

By |How-To, Technical|0 Comments
Read More

Fixed POP3 Service after Exchange 2013 CU6

In a previous post I wrote about my Exchange 2013 CU6 Adventure and how it caused my Exchange Replication Services to crash.

That wasn’t the only issues faced after updating to CU6.  It seems that the CU6 upgrade had crippled my ability to use the POP3 service.

I have been waiting for a week now for Microsoft to get back to me regarding a solution.  But I was able to find one else ware thanks to Jason (Izzy) Sherry’s Blog Post: Exchange 2013 POP3 service drops connections fix

Symptoms:

  • Exchange 2013 POP3 request fail from remote hosts
  • Exchange 2013 POP3 request respond from localhost

Troubleshooting Steps:

  • Restart POP3 and POP3 Back-end Services
  • Reconfigure Exchange POP3 Local IP Address
  • Check server for firewall
  • Check if 3rd party antivirus may be intercepting POP3 requests
  • Inspect traffic using Wireshark

Solution Steps Followed:

In Exchange Powershell type:
Get-ServerComponentstate -Identity SERVERNAME

This will list the Server Component States

Server Component State
SERVERNAME ServerWideOffline Active
SERVERNAME HubTransport Active
SERVERNAME FrontendTransport Active
SERVERNAME Monitoring Active
SERVERNAME RecoveryActionsEnabled Active
SERVERNAME AutoDiscoverProxy Active
SERVERNAME ActiveSyncProxy Active
SERVERNAME EcpProxy Active
SERVERNAME EwsProxy Active
SERVERNAME ImapProxy Active
SERVERNAME OabProxy Active
SERVERNAME OwaProxy Active
SERVERNAME PopProxy Inactive
SERVERNAME PushNotificationsProxy Active
SERVERNAME RpsProxy Active
SERVERNAME RwsProxy Active
SERVERNAME RpcProxy Active
SERVERNAME UMCallRouter Active
SERVERNAME XropProxy Active
SERVERNAME HttpProxyAvailabilityGroup Active
SERVERNAME ForwardSyncDaemon Active
SERVERNAME ProvisioningRps Active
SERVERNAME MapiProxy Active
SERVERNAME EdgeTransport Active
SERVERNAME HighAvailability Active
SERVERNAME SharedCache Active

 

Now that you have identified the issue; as you can see POPProxy is set to Inactive we need to now set it back to Active

So we issue the following command:

Set-ServerComponentState -Identity SERVERNAME -Component PopProxy -Requester HealthAPI -State Active

As soon as you do this the POP3 Service start to respond again.

Problem now fixed, cause is still unknown. The only thing known in my case is that this occurred after installing Exchange 2013 CU6

By |News, Software, Technical|11 Comments
Read More