Office 365 – Lync has stopped working
When trying to run the Lync 2013 client on Windows 7/8/8.1 you receive the error:
Lync has stopped working.
A couple of roaming staff received this error after rolling out Lync 2013 basic client onto their laptops.
The only thing in common was they were both roaming staff with laptops. After about 20 minutes or so working on one of the laptops I noticed that there was a laptop dock software installed so the laptop could connect to two monitors. I read on Google that the error may be down to the Graphics drivers so I uninstalled the dock software and it worked fine. The dock software installed its own graphics drivers for the dual monitor which were in compatible with Lync. Downloading the latest software from the manufactures website allowed the dock to work again with Lync as well. I checked the other laptop and they also had similar software installed removing and updating the software fixed the issue there also.
Read MoreSCCM 2012 – Manually install the SCCM client
We have been using SCCM 2012 (System Center Configuration Manager 2012) for a while and every time we add a workstation to the domain the SCCM client and endpoint protection is installed automatically. Recently there was an issue where the client would not automatically install. The only difference from all other workstations was that this was a MacBook Pro with a virtual instance of Windows 8.1 Pro (using VMware Fusions v7). The VM was on the domain and I could not find the reason why the client would not install. I ended up having to install the client manually.
To manually install the client open up the Windows run window (Windows button + r) then type the following command:
\\SCCMServerName\sms_XXX\client\ccmsetup.exe /mp:SCCMServerName SMSSITECODE=XXX
SCCMServerName – Replace this value with the hostname of you SCCM Server.
XXX – Replace this value with the three letter site code of the server
Example:
SCCMServerName = SCCM2012
XXX = ABC
\\SCCM2012\sms_abc\client\ccmsetup.exe /mp:SCCM2012 SMSSITECODE=ABC
Read MoreOffice 365 – Shared Mailboxes Pre-Migration Checks
We had a hybrid deployment of Exchange 2010 and office 365. During the testing phase I found that if you have shared mailboxes/calendars that need to be accessed by both on premise exchange users and the users that have been migrated to office 365 then you will need to leave the mailboxes on the on premise server as they can then be accessed by both on premise exchange users and office 365 users (as long as they are on the network where the on premise exchange is located).
The other issue I found was not just migrating shared mailboxes but ANY mailbox to office 365 is that if you have the emails forwarded to another email address the forward is removed so make sure that you make a note of any forwarding on the mailboxes before you start the migration!
Read MoreOffice 365 – Emails sent from iPhone not being received
While testing the migration to office 365 I found that once a test mailbox had been migrated and I set up an account on my iPhone 4s (firmware version 7.1) I could not send emails. It worked fine with our on premise Exchange server 2010 account. I was creating and sending the emails and it was no longer in the outbox. The emails were never received and they did not appear in the sent Items. It turned out that there was a bug in the firmware and once I upgraded to version 7.1.2 it worked fine. If you are on version 8 of the firmware it was working fine on version 8.02.
Read MoreOffice 365 – Error When Sending Emails as a Shared Mailbox
Setup
- Hybrid deployment using office 365 and Exchange 2010
Issue
After migrating a shared mail box to office 365 from an on premise exchange server I received the following bounce message in outlook when trying to send emails as the shared folder. i.e. send emails as sales@mydomain.com.
The following recipient(s) cannot be reached:
xxxxxxxxx.xxxxxxx@gmail.com on 05/12/2014 15:17
This message could not be sent. Try sending the message again later, or contact your network administrator. Error is [0x80070005-00000000-00000000].
Solution
I checked the following to resolve the issue:
- First of a checked permissions and the users permissions had copied over. They had full access and send as permissions to the shared mailbox.
- I deleted the cached “from” email address in outlook and the issue was still there
- I logged into the outlook portal and the email worked fine which made me think the issue was with the outlook profile. I re-created the profile and the issue still remained.
- I did a little googling and found a couple of possible solutions
- First was to update the address book (http://support.microsoft.com/kb/2918777)
- Second was to recreate the profile but I had already tried that and it did not work
- After setting up a test shared mailbox and migrating that to office 365. It worked fine. After checking the settings on both mailboxes I found the solution for me to be down to the shared mailbox being hidden from the exchange address list. To disable the setting you cannot just tick the box in the office 365 admin portal or in the exchange 2010 hybrid deployment’s office 365 server as you will receive the following error messages:
Office 365 admin centre error
Office 365 admin centre > Shared Mailboxes > (select mailbox) > select edit more properties > un-tick hide from address lists > save
error
The operation on mailbox “(Shared mailbox)” failed because it’s out of the current user’s write scope. The action ‘Set-Mailbox’, ‘HiddenFromAddressListsEnabled’, can’t be performed on the object ‘(Shared Mailbox)’ because the object is being synchronized from your on-premises organization. This action should be performed on the object in your on-premises organization.
Exchange On-Premise Error Message
EMC > Office 365 > Mailbox > right click shared mailbox > properties > general tab > Untick Hide from exchange address lists > Apply
——————————————————–
Microsoft Exchange Error
——————————————————–
The following error(s) occurred while saving changes:
Set-Mailbox
Failed
Error:
The operation on mailbox “Shared Mailbox” failed because it’s out of the current user’s write scope. The action ‘Set-Mailbox’, ‘HiddenFromAddressListsEnabled’, can’t be performed on the object ‘Client Accounts Support’ because the object is being synchronized from your on-premises organization. This action should be performed on the object in your on-premises organization.
The action ‘Set-Mailbox’, ‘HiddenFromAddressListsEnabled’, can’t be performed on the object ‘Shared mailbox’ because the object is being synchronized from your on-premises organization. This action should be performed on the object in your on-premises organization.
As the changes are synched from AD to disable the setting you need to log into your AD Users and Groups, enable the advanced feature and open up the properties of the shared mailbox. Then select the attribute editor and find the setting:
msExchHideFromAddressLists
Set the value to FALSE and sync the changes up using the DirSync tool. Once complete wait a few minutes then restart outlook (or download the address book changes) and it should work fine.
Read More
Recent Comments