Exchange

Tech Short: Use Dsquery tool to manage group memberships On-Prem to Office 365

 

I had mentioned in a previous post about the inability to self service groups.

Problem: on-premises distribution group is synced to a Microsoft Office 365 organization through Active Directory synchronization, migrated users who are owners of the distribution group can’t manage it in Microsoft Exchange Online

Solution: Use the Exchange Tools (But we no longer have exchange on prem?)

Solution: Use Active Directory Users and Computers

Solution: Dsquery.exe  – Press the Windows Key and R to open the run box and past in the following:

Owners of the group should be able to make changes when needed.

Note:  You will still need to wait for dirsync to complete.

kb2417592

Office 365: Self Service of Distribution Groups

The ability to self service the creation of distributions groups has been a feature for quite some time in my Exchange experiences.  Now that I am in Office 365 / Exchange Online this functionally is no longer available for synced groups. This now forces the enlistment of the support department to facilitate all mortification for the end user.

Looking into this to get an understanding as to why this is, I’ve learned that if you’re an Office 365 Exchange Online customer and currently utilizing Directory Synchronization (DirSync) between an on-premise Active Directory and Office 365’s Azure Active Directory you will face such incidents as the objects on the Office 365 are in read only mode and are updated via the synchronization that has been put in place

You are even given a a little message when you attempt to make modification to groups:  The action ‘Update-DistributionGroupMember’, ‘Identity,Members’, can’t be performed on the object ‘Group Name’ because the object is being synchronized from your on-premises organization. This action should be performed on the object in your on-premises organization.

Now aware of this limitation that exist around group modification due to them being read only how do I work like this? I have the following two ideas to work with.

One: 

One method is to go old school and use the Use the ‘Find Users, Contacts and Groups’ tool to allow group modification. However there is an issue regarding the fact that the computer used needs to be a member of the domain and at the time of change also connected to the on premise domain network (internal or via vpn).

Note: After changes have been made the condition of waiting for Directory Synchronization (DirSync) to complete its sync cycle must take place.  This can take up to 3 hours time.

 

Two:

The Second method is to change all Directory Synchronization (DirSync) Distribution Group Objects to the Azure Active Directory and make the On-Clound

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

 

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

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