Search by tag «transition»

Entries found: 4

BPOS to Office 365 Transition Issues: Outlook Shared Calendars

This is the fourth post about issues that one of our client's found recently when they transitioned from BPOS to Office. You can see all of these issues in Support Stories. This time, we're talking about vanishing Outlook shared calendars.
Disappearing Shared Calendars in Outlook

After transitioning from BPOS to Office 365, a shared calendar that I had created vanished from my copy of Outlook but was still available to everyone who had been invited to the calendar. This posed a bit of a challenge, because as the owner of the calendar I could not be invited to the calendar - no one could invite other users to the calendar. The solution was very, very simple. Here are the steps you need to take:

  1. Log in to your Office 365 account.
  2. Click 'Outlook' at the top of the screen.
  3. On the left-hand side, click 'Calendar'.
  4. Right-click on the calendar you want access to again (look, it's still here!) and select 'Share' then 'Share This Calendar...'.
  5. Enter your own email address and change the share permission to 'All information with permission to add, edit, and delete', then hit 'Send' at the top.
  6. Open up the Outlook desktop application, then accept your own sharing invitation.
  7. Your shared calendar will now be available in the 'Calendar' section of Outlook.
  8. All done!

Office 365 - Outlook Web Access Shared Calendar

BPOS to Office 365 Transition Issues: Lync on Mobile Devices

This is the third post about issues that one of our client's found recently when they transitioned from BPOS to Office. You can see all of these issues in Support Stories. This time, we're talking about getting Lync working on mobile devices like Android phones, iPhones, iPad and Windows Phone 7 phones.

DNS Record for Lync for Mobile
Lync Online for Mobile Devices

After transitioning from BPOS to Office 365, no users were able to use the Lync mobile app. Whenever a user tried, they receive a server error. Trying the same device with an Office 365 (non-transitioned) account was fine, so this seemed more like a transition issue. This was a very easy fix of adding a new DNS record for the domain. Here are the steps you need to take:

  1. Log in to your Office 365 account (you must be an administrator for these steps).
  2. Under the 'Admin' panel, click 'Domains' on the left-hand side navigation bar.
  3. Click on the radio button next to your primary domain name and click 'View DNS Settings'. (You may need to edit domain intent to allow Exchange Online and Lync Online)
  4. Look at the bottom of this page for the lyncdiscover DNS record.
  5. Log in to your domain registrar's control panel and add a new CNAME record with these details.
  6. Wait for roughly half an hour.
  7. Try the mobile device again.
  8. Congratulations, you have won. If this still doesn't work, submit a support request through Office 365's admin panel.

BPOS to Office 365 Transition Issues: Can’t Access SharePoint Site Collections

This is the second post about issues that one of our client's found recently when they transitioned from BPOS to Office. You can see all of these issues in Support Stories. This time, we're talking about an issue that lead to a significant number of users being unable to access the transitioned site collections. Just to be clear, all users could access the default SharePoint Online site collection (the Team Site found at companyname.sharepoint.com).
TaskLight - Can't Access Transitioned SharePoint Site Collections
Users Can't Access Transitioned SharePoint Site Collections

So, this was a strange issue for us. After transition to Office 365, whenever quite a few users tried to open up one of the transitioned SharePoint site collections, the connection would just time out and give one of the very useful 'Microsoft Online Services is unavailable from this site...' messages. I contacted Microsoft's transition support team and they gave a terribly simply solution, outlined below.

  1. In Internet Explorer, on the Tools menu, click Internet options.
  2. Click the Security tab, click the Trusted sites zone, and then click Sites.
  3. Verify that the following entries are listed in the Websites list:
    • https://*.outlook.com
    • https://*.sharepoint.com
    • https://*.microsoftonline.com
    • https://*.lync.com
  4. If these entries are not present, add them to the Trusted sites list of websites.
  5. Now, go back to the Security tab and click Local intranet zone, click Sites, and then click Advanced.
  6. Add the following entries are listed in the Websites list:
    • .microsoftonline.com
    • .sharepoint.com
    • .outlook.com
    • .lync.com

BPOS to Office 365 Transition Issues: Workflows

One of our clients was recently transitioned from Microsoft's BPOS (Business Productivity Online Suite) to Office 365 as part of the upgrade cycle for Microsoft's Online Services. We encountered a few issues which we resolved, occasionally with (excellent, as always) support by Microsoft's support team. We're going to take the time to highlight a few of the issues that we encountered, in the hope that this will help other BPOS administrators in the future. You can see all of these issues in Support Stories. We'll start with an issue related to workflows, which was easily solved.

TaskLight - Office 365 Workflow Issues after transition to BPOS

Workflows

We encountered two issues with workflows post-transition to Office 365. The first was that none of the workflows would start at all, the error given in the workflow status being "[Workflow name] failed on Start". This happened for all of the workflows that we had created on the SharePoint site collections that transitioned. The (admittedly very simple) solution for this was to open up SharePoint Designer 2010 (remember, once you've transition to Office 365 you need to use the 2010 version of the programme, not 2007), then open the workflow and press the 'Publish' button on the taskbar - simple!

The second issue was that any issues in-progress during the transition failed when they tried to continue. For this client, this meant that there were a number of workflows which, before transition, had paused for a short amount of time. After transition, these workflows did not restart and the workflows failed. There was no way to directly fix this issue, the only thing to do was to start the workflows again.

Here's hoping this helps to indicate any potential issues that you might have with transitioning from BPOS to Office 365. We'll have more coming over the next few weeks under the category Support Stories, come back then, sign up to the RSS feed or join our newsletter.