Month: May 2012

Configuring Cisco Unity Connection 8.6(2) and later and Microsoft Office 365 for Unified Messaging

Posted on Updated on

 

 

 

For those Office 365 Administrators who have Cisco Unity devices and want/need to integrate this service with Exchange Online Unified Messaging, that time has finally come.  Cisco has a great write up on how to accomplish this task of integrating your on-premises Cisco Unity with Exchange Online Unified Messaging (Exchange Mailbox used for Voice Mail).  To learn more, please refer to:  http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/unified_messaging/guide/85xcucumg025.html

Exchange Online & eDiscovery Mailbox Search Increases

Posted on Updated on

For those Exchange Online administrators out there, you will be happy to hear that Exchange Online has updated its maximum mailbox search capabilities from 50 to 5,000.  As described below Exchange Online Administrators can now search against a maximum of 5,000 mailboxes but with a few caveats:

DiscoveryMaxMailboxes: 50 DiscoveryMaxMailboxesResultsOnly: 5000
The maximum number of mailboxes you can search and get bothsearch results and keyword statistics.  The maximum number of mailboxes you can search for which you will get search result but no statistics.


Office 365 Directory Synchronization Error Messages & Resolutions

Posted on

For those Office 365 Administrators who are responsible for the installation, configuration and usage of the Office 365 Directory Synchronization application, which provides synchronization of on-premises Active Directory users, contacts and groups, this table will help explain all known DirSync errors along with suggested workarounds, fixes, configuration and/or updates to resolve your issue:

Error Name Error Details Source Resolution
AdminRequired Local Administrator permissions are required to install Directory Synchronization. Event Viewer/ Error Prompt
DirSyncAlreadyInstalled The Directory Synchronization tool is already installed. Version {0} Event Viewer Instruct the customer to uninstall all previous versions of DirSync before attempting the install the latest version.
DirSyncInstallKeyNotRemoved Windows Installer could not remove the uninstall registry key from the Microsoft Online Services Directory Synchronization MSI. Retry un-install or contact Microsoft Online Support. Event Viewer Instruct the customer to manually remove the registry keys to complete the installation.
DirSyncNotInstalledError A complete installation of the Microsoft Online Services Directory Synchronization tool was not detected on this machine. Please uninstall any versions of this tool and then reinstall the most recent version. Event Viewer Instruct the customer to uninstall all previous versions of DirSync before attempting the install the latest version.
ErrorReRunConfigWizard Unable to start synchronization due to configuration issues. To fix the issues, try running the Configuration Wizard. If you continue to see this error please contact Microsoft Online Support. Event Viewer Instruct the customer to run the DirSync configuration wizard.
WindowsInstaller45Required Microsoft Windows Installer 4.5 is required for installation. Please install Microsoft Windows Installer 4.5 and try again. Event Viewer Instruct the customer to ensure that the server DirSync is being installed on meets the minimum requirements.
ErrorClearRunHistory Could not clear the run history on the MIIS Server. Error returned is ‘{0}’. Contact Microsoft Online support. Event Viewer
ErrorNoStartConnection Synchronization failed to start because of connection issues or domain controllers could not be contacted by the server. Verify that you are connected to the server and all the configured domain controllers are connected to the network. If you have recently deleted domain or naming context, please rerun the Configuration Wizard. Event Viewer Instruct the customer to confirm that the local Active Directory Domain Controllers are accessible from the server running DirSync.
ErrorNoStartCredentials Synchronization failed to start because of credential problems. Rerun Configuration Wizard to update credentials for Synchronization. Event Viewer Instruct the customer to run the DirSync Configuration wizard and re-enter credentials. The customer should also confirm that the credentials have Admin access to MOAC.
ErrorNoStartNoDomainController Synchronization failed to start because the domain controller could not be contacted by the server. Verify that the domain controller is connected to the network. Event Viewer Instruct the customer to confirm that the local Active Directory Domain Controllers are accessible from the server running DirSync.
ErrorStoppedConnectivity Synchronization stopped because of connectivity loss. Restore connectivity to the server. Event Viewer Instruct the customer to confirm that the local workstation can access the Internet. Have the user attempt to ping provisioning.microsoftonline.com to verify that it can reach the DirSync Service on Microsoft Online.
ErrorStoppedDatabaseDiskFull Synchronization stopped because the SQL Server database used by the Synchronization server is full. Create some space in the SQL Server database. Event Viewer Instruct the customer to free up space on the storage used to hold the DirSync SQL Database. If the issue is not resolved DirSync will not be able to run successfully and the SQL database may be permanently damaged.
InstallNotAllowedOnDomainController Microsoft Online Services Coexistence can not be installed on a domain controller. Event Viewer Instruct the customer that DirSync can only be installed on domain joined computers that do act as Domain Controllers
InstallPathLengthTooLong The installation path is too long. Provide a path of 116 characters or fewer and then try again. Event Viewer Instruct the customer that if they choose to use a customer path for the installation of DirSync that the total path length has to be less than 116 characters.
InsufficentDiskSpace Insufficent Disk Space Event Viewer Instruct the customer that there is not enough space to install DirSync on the local workstation.
InvalidPlatform The Microsoft Online Services Directory Synchronization tool must be installed on a computer running Windows Server 2003 Service Pack 2 or later. Event Viewer Instruct the customer to ensure that the server DirSync is being installed on meets the minimum requirements.
InvalidUPNFormat User Principal Name (UPN) is your logon name. This error is displayed when the user enters credentials for Microsoft Online that do not contain an ‘@’ character. Event Viewer Instruct the customer to enter a valid credentials for Microsoft Online Services and to continue.
ADCredsNotValid The Enterprise Administrator credentials that you supplied are not valid. Supply valid credentials and try again. Event Viewer The installation wizard was unable to verify that the user account being used to install (No Suggestions) is an Enterprise Administrator.
MachineIsDomainJoinedUserIsNot The computer is joined to a domain, but the current user credentials do not have access permissions on the domain. Event Viewer Instruct the customer to log in as a domain user with an account that meets the minimum requirements before attempting to install DirSync.
MachineIsNotDomainJoined The computer is not joined to any domain. Event Viewer Instruct the customer to ensure that the server DirSync is being installed on meets the minimum requirements.
MachineNotDomainJoined The computer must be joined to a domain. Event Viewer Instruct the customer to ensure that the server DirSync is being installed on meets the minimum requirements.
MIISSyncIsInProgressError The synchronization engine is busy. Retry this operation after this synchronization session is complete. Event Viewer Inform the customer that this means there is an existing operations being completed by the MIIS and that any new operations for (No Suggestions) can only be completed once the current operation is completed.
MIISUserAddRight_AccountNotFound Account name:'{0}’ could not be found. Error Code:{1} Event Viewer Inform the customer the DirSync was not able to add the local account being used to complete the installation to the MIIS Admin Group. The user should be manually added to the group to continue with the installation.
MIISUserAddRight_AddFailed ‘{0}’ could not be added to the account rights for ‘{1}’. Error code:{2} Event Viewer Inform the customer the DirSync was not able to add the local account being used to complete the installation to the MIIS Admin Group. The user should be manually added to the group to continue with the installation.
MIISUserAddRight_PolicyHandleNotFound Failed to obtain the policy handle. Error Code:{0} Event Viewer Inform the customer the DirSync was not able to add the local account being used to complete the installation to the MIIS Admin Group. The user should be manually added to the group to continue with the installation.
PowerShellRequired PowerShell must be installed. Event Viewer Instruct the customer to ensure that the server DirSync is being installed on meets the minimum requirements.
UnsupportedNameFormat The name format is not supported. Two examples of the supported user name formats are: someone@example.com or example\someone. Event Viewer Instruct the customer to enter a valid credentials for Microsoft Online Services and to continue.
UserNotAMemberOfMIISAdmins The current user is not a member of the Microsoft Identity Integration Server (MIIS) Admin group. If you have recently installed the Microsoft Online Services Directory Synchronization tool, you may need to log off and then log on. Event Viewer Instruct the customer to manually add the local Active Directory user account used to run DirSync to the MIIS Admin Group.
UserNotAnEnterpriseAdmin User ‘{0}’ is not a member of the Enterprise Admins group. Event Viewer Instruct the customer to manually add the local Active Directory user account used to run DirSync to the Active Directory Enterprise Admin Group.
UnsupportedClientVersion This version of the Directory Synchronization tool is no longer supported. Remove this version and then install the latest version from the Directory Synchronization page of the Migration tab in the Microsoft Online Services Administration Center. Event Viewer Instruct the customer to download the latest version of the DirSync Tool from the Office 365 portal.
InternetQueryOptionError Internet Explorer proxy settings were not read. Initial configuration using setup wizard may not be able to access online help. WinInet Error {0} Event Viewer Instruct the customer verify that they proxy settings entered into Internet Explorer are correctly formated because the Installation Wizard was not able to read/modify these settings correctly.
InternetSetOptionError Internet Explorer proxy settings were not set. Initial configuration using setup wizard may not be able to access online help. WinInet Error {0} Event Viewer Instruct the customer verify that they proxy settings entered into Internet Explorer are correctly formated because the Installation Wizard was not able to read/modify these settings correctly.
RichCoexistenceNotAllowed Current local directory does not have Exchange 2010 installed. Rich coexistence is not allowed. Event Viewer Instruct the customer to install all of the required prerequisites for Rich Coexistence before attempting to install DirSync

Maintaining Email Connectivity for BES Devices Over the BPOS Transition Weekend

Posted on Updated on

Many BES users have asked how they can maintain email connectivity over the BPOS Transition Weekend, which moves BPOS tenants into Office 365.  Due to users Mailbox, at some point during the weekend, moving out of BPOS and into Office 365 the BES device mail configuration will stop working, in the same way ActiveSync devices will.  This is because the BPOS mailbox is no longer available and mobile devices cannot automatically pick up this move, which requires ActiveSync and BES devices to reconfigure their devices to point to Exchange Online 365 messaging services.

However BES devices, typically, will use RIMs Onboarding Wizard, which is an automated approach to backup the device, wipe, restore content and configure the device for use in RIMs BlackBerry Business Cloud Services (BBCS).  To learn more about RIMs Onboarding Wizard and how this should be used during your phone configuration to use BBCS, please click here:

Office 365 Help & RIMs Web Desktop Managerhttp://onlinehelp.microsoft.com/en-us/office365-enterprises/ff637599.aspx

To keep your BES device up and running with email over the Transition Weekend, you can use these steps to keep your phone connected.  Note that once you as an Office 365 user are created and activated with RIMs BBCS environment, your RIM user will be transitioned from the BlackBerry Internet Service (BIS) to full BBCS, so there is no need to reconfigure your device manually, as you will use the Onboarding Wizard to backup, wipe, restore and reconfigure the device.

Steps to use BlackBerry Internet Service BIS Over Transition Weekend

  1. Make sure you have changed your BPOS password using either the Company Portal or Sign-In Client (SIC)
  2. Once changed attempt to login to the Office 365 Portal to verify you can login with your BPOS credentials, using your newly changed password
    1. Login to: https://portal.microsoftonline.com
      1. Username:  BPOS account
      2. Password:  Newly changed password
      3. Note the Outlook link at the top of the Microsoft Online Portal
        1. Click this link to determine whether your mailbox is not accessible within Office 365
          1. During the Transition weekend your mailbox and others will be moved from BPOS into Office 365.  There is no way to know exactly when this will occur, so you should check the Microsoft Online Portal from time to time, starting sometime ~Saturday afternoon of your Transition Weekend.  Once your mailbox is accessible via OWA, you can proceed with configuring your BES device to connect and use RIMs BlackBerry Internet Service (BIS).  BIS provides connectivity between your BES device and your Office 365 mailbox.
            1. Once your online administrator configures you for the BlackBerry Business Cloud Service (BBCS), your BIS device configuration can be left as you will use RIMs Onboarding Wizard, which will backup, wipe, restore and reconfigure your phone.
            2. Once you are connected and logged into your Office 365 Mailbox via Outlook Web Access (OWA), you can proceed with the following steps.

Integrate a Microsoft® Outlook® Web Access Email Address Using the Email Setup Application from the BlackBerry® Smartphone:

  1. Open Email Settings on the BlackBerry smartphone (for BlackBerry Device Software 6.0 and higher open Setup and choose Email Accounts
  2. Click Set up Internet email account. (not Enterprise email account) Any existing email accounts will remain active
  3. Choose Other from the list of options
  4. Enter the O365 Email Address and Email Password, then click Continue

Integrate a Microsoft Outlook Web Access Email Address Using the Web Login for BlackBerry Internet Service:

  1. Go to the wireless service provider’s BlackBerry Internet Service website and log in to the BlackBerry Internet Service account
  2. Click Set Up Email
  3. Complete the Email address and Email Password, and select Next
  4. Select provide additional settings
  5. Select Microsoft Exchange (using Microsoft ® Outlook Web Access), complete the required fields, and select Next

Additional Information

During advanced integration of a Microsoft Exchange Server 2010 account with BlackBerry Internet Service, any mailbox name can be typed in the Mailbox Name field and the account will associate successfully.

The Exchange Web Services (EWS) protocol introduced in Microsoft Exchange Server 2007 does not use the mailbox name. The EWS protocol uses the HTTP authenticated user. The BlackBerry Internet Service user interface does not currently differentiate between different versions of Outlook Web Access (OWA), so the Mailbox Name field is still displayed even though it is not used for Microsoft Exchange Server 2007 or Microsoft Exchange Server 2010 accounts.

BlackBerry Internet Service will still function correctly with Microsoft Exchange Server 2007 or Microsoft Exchange Server 2010 accounts, even if an incorrect mailbox name is used.

Support for Lotus Notes to Office 365 Mailbox Migrations

Posted on Updated on

Great write up on the new Lotus Notes (MONTI – Microsoft Online Notes Inspector) Tool, providing mailbox migrations from Lotus Notes into Office 365

http://360on365.com/2012/05/06/support-for-lotusnotes-to-office365-migrations/ 

Outlook Password Notifications & Exchange Online 365 – Password Expiration Notifications are Coming!!!

Posted on

Problem:  Office 365 Customers using managed (OrgID Based) accounts will not know when passwords will expire (if enabled for expiration). Further, Outlook’s behavior when the password expires is to go into a disconnected state, without notifying the user of what the problem is or what is required to resolve it. Opening Outlook and providing an expired password will continually prompt the user just as if they had mistyped the password.

Solution OverviewOnce customers deploy an upcoming Outlook update, they will receive a notification 14 days before their password will expire for managed accounts. The notification will include a link to a password change page hosted by OrgID. If they try to logon after the password has already expired (when returning from vacation for example), they will also receive notification that their password has expired and will be provided a link to use to change it.

Forecasted Resolution Date: With the Outlook August 2012 Cumulative Update.

Understanding When to Start Using Directory Synchronization into Office 365 After BPOS Transition

Posted on Updated on

   As many of you are in the BPOS Transition into Office 365, the questions comes up around “…when can I start using the new Directory Synchronization against Office 365?”.  Below is an excerpt from the Enterprise Transition Guide, which discusses among other things, what, why, when and where to start your Office 365 Directory Synchronization administrative tasks:

Validate the configuration of Directory Synchronization Tool for BPOS–S and continue to perform synchronization

Directory synchronization enables you to synchronize objects from your Active Directory to the BPOS–S environment. There is an updated version of the Directory Synchronization Tool for Office 365, and the BPOS–S version of the Directory Synchronization Tool for BPOS–S will not work with Office 365. The BPOS–S synchronization will continue to work up until the start of the transition weekend. Microsoft recommends scheduling for the suspension of all technical and business identity change processes, including directory synchronization, approximately 12 hours before the start of the Transition Window. However you choose to manage your organizations identity processes during transition, it is a requirement that directory synchronization is suspended 12 hours before the transition begins.

Upon completion of the transition process, the Office 365 portal will not permit changes to user properties because the tenant is not yet authoritative for the user directory. Becoming authoritative can take between 24 and 72 hours (worst case) after transition completes. When you see that you can make changes to user attributes via the Office 365 tenant portal (not the BPOS–S Microsoft Online Admin Center which will be unavailable after transition), then your tenant has directory authority and you can re-establish directory synchronization with the Office 365 environment using the Office 365 version of the Directory Synchronization Tool. For more information about key work items you must complete before you start the Office 365 Directory Synchronization Tool, see Deploy Directory Synchronization Tool for Office 365 Post Transition in Section 3.

If you were using DirSync before the transition, you are required to continue to use the new Directory Synchronization V2 Tool in Office 365.

Deploy Directory Synchronization for Office 365 Post Transition

Once the transition process has been completed, and all services have been validated as part of the solution, one of the final remaining tasks is to complete the upgrade to the Directory Synchronization Tool for Office 365. The BPOS–S version of the Directory Synchronization Tool (DirSync) will become non-functional during the transition weekend, and will need to be re-established once the post-transition validations have been completed and after you have captured the ‘public delegates’ configuration described below.

The new version of the Directory Synchronization Tool now supports the x86 and x64 platforms, which gives customers additional flexibility in regards to their deployment. The configuration of the Office 365 directory synchronization service is broken down into the following tasks:

  • Removal/uninstallation of the existing BPOS DirSync Service.
  • Download of the updated Office 365 Directory Synchronization Tool code (32-bit or 64-bit).
  • Installation of any new hardware that may be intended for the DirSync Service.
  • Installation and upgrade of Office 365 Directory Synchronization Tool.
  • Validation that the Directory Synchronization service is working and synchronizing correctly.

The installation of the Directory Synchronization Tool post-transition will require a full synchronization of the directory and this cannot be performed until between 24 and 72 hours after transition is complete, as described earlier in Post Transition in Section 2.

A full list of upgraded features of the Office 365 Directory Synchronization Tool can be found in the documentation that is downloaded with the tool. The most up-to-date version of this guidance can be found in the help topic Install and Upgrade the Microsoft Online Services Directory Synchronization Tool at http://onlinehelp.microsoft.com/en-us/office365-enterprises/ff652545.aspx.

If you are going to be using directory synchronization between your on-premises Active Directory and Office 365, it is crucial your directory meets the directory requirements for Office 365. These requirements are documented in the Office 365 Identity Service Description, which can be downloaded from http://www.microsoft.com/download/en/details.aspx?id=13602. Review the “Active Directory Considerations” section in this Service Description, and include project activity during your pre-transition phase to confirm your Active Directory content is compliant with Office 365.

Note that unlike BPOS–S, Office 365 requires the User Principal Name (UPN) configured in your directory to precisely match at least one SMTP address configured for that user. If this is not the case, your transition may be delayed until your directory meets this and the other above requirements. The SMTP address selected to match the UPN does not need to be the primary SMTP address for that user. However it is critically important that a user’s UPN is not the SMTP address of a different user in BPOS –S. This could delay your transition or result in the loss of mail for one or the other user during transition unless corrected.