Category Archives: Uncategorized

Manually Run DirSync via the MIIS Client

If you want to manually run DirSync to force synchronization of your on-premise Active Directory with Windows Azure Active Directory (WAAD) you can use the following method to perform a sync via the MIIS Client…

  • Launch Windows Explorer and browse to the C:\Program Files\Windows Azure Active Directory Sync\SYNCBUS\Synchronization Service\UIShell directory.

 

  • Right-click on miisclient.exe and choose “Run as administrator” from the context menu.

  • Choose Yes to the security prompt.

 

  • Click on the Management Agents button on the top menu bar

 

  • Right-click on “Active Directory Connector” and choose Run from the context menu.

     

  • Highlight “Full Import Full Sync” and choose OK.

     

  • The State will change to Running. The bottom half the screen will give information on any changes that it makes during the run as well as any errors encountered.

Advertisements

Office 365 Administrators Can’t View Their FOPE Quarantine

By default, if you are an Office 365 Administrator you will not be able to view your User Quarantine in Forefront Online Protection for Exchange.  The following article discusses the problem and offers a workaround…

http://support.microsoft.com/kb/2587698

The basic premise is you will need to temporarily remove yourself from Administrator roles in Office 365, create the quarantine and then add yourself back to the Administrator Roles.

Important safety tip: Make sure you have another Office 365 Administrator account first…

Exchange 2010 Coexistence

An Exchange 2007 CAS Server/Exchange 2003 Front End Server can’t proxy requests to Exchange 2010 mailboxes. Nor can an Exchange 2010 CAS Server proxy requests to Exchange 2003/2007 mailboxes (the one exception is Exchange ActiveSync). While an Exchange 2010 CAS Server can’t proxy, it can transparently redirect clients to an Exchange 2007 CAS Server / Exchange 2003 Front End Server though. Typically we would do this as follows.

The current configuration looks like this…

clip_image002

We would then stand the new Exchange 2010 environment in parallel to the Exchange 2007 environment. Note that I drew the ASA and ISA Server as two icons for clarity but in both cases we’re just talking about a second IP address on the same device.

clip_image004

At this point everything would be published and testable but no redirection would be occurring. Here comes the first step were we actually impact users. We would change the External URL values for OWA, EWS and Offline Address book on the Exchange 2007 CAS Server to point to legacy.domain.com (for Exchange 2003 we would add the Exchange2003URL value to the Exchange 2010 CAS Server) so Exchange 2010 would know where to redirect traffic. We would then swap IP addresses between the Exchange 2007 and Exchange 2010 Servers…

clip_image006

Now, when clients type owa.domain.com they would hit the Exchange 2010 server. If their mailbox is here they would stay put however if their mailbox is still on Exchange 2007/2003 their browser would be redirected to legacy.domain.com which would send them into the Exchange 2007 Server. We can now move mailboxes at our leisure. Once they are all moved we can tear out the temporary legacy stuff and we’re left with this…

clip_image008