During a cloud migration from a on-premise Exchange server behind a commercial firewall to a full Office365 Exchange we noticed the amount of spam that was getting through. Here is an example of the email.
The phishing email looks very genuine, but isn’t. We hope you find this information prior to an incident at your facility and it helps you thwart any attempt at gaining access to your facilities network.
Let us know if this helped you…
We noticed users were having issues opening Office documents like a Word or Excel file that was sent to them via email. Everything looks normal, but when they click on the file to open it they get the following error.
The fix is really easy.
Let us know if this helped you.
We needed to have an Excel spreadsheet of the email addresses we had in global address book group. Here is the best method we found so far.
Let us know if this helped you…
We had an employee who needed to find an email from a few months ago, but when he searched in Outlook the results only went back
The following article from Microsoft did not work. We changed the “Option” to allow more search results, but this didn’t fix the issue.
https://support.microsoft.com/en-us/help/2185146
We ended up creating a new profile and this totally fixed the issue. It took and hour for the mailbox to be completely rebuilt.
Let us know if this helped you…
Got a call from a user who recently changed her print option to landscape and couldn’t get it back to portrait. Going through the regular print options didn’t get back to portrait. Looked on the web for another solution and this following YouTube post had the right answer.
Let us know if this helped you…
We upgraded a Windows 7 machine to Windows 10 via the Media Creation Tool. Once the upgrade was finished Outlook wouldn’t run. We got the following error.
We uninstalled and re-installed the Office program but this didn’t solve the issue. We ran a repair from the “uninstall Program” but choosing “repair”. This time I start to check Office by opening Word and not Outlook. Word opened fine and so did all the rest of the Office suite. Outlook opened like it should.
Let us know if this helps you…
We got a call from a customer who got the following popup.
A quick search on the web lead me to this article from Microsoft.
I looked on the server and in the Vipre console I couldn’t push updates or definitions. We restarted the users machine to see if Vipre still shows it needs to be updated. We opened Outlook and didn’t get another warning. We saw the Vipre Add-in start up. We opened the Vipre agent and it asked to be updated. We pushed the button to update, but nothing happened.
In the console we “Forced Updates” instead of “Checking for updates” and this worked. We haven’t seen the warning come back yet.
Let us know if this helped you…
We got a call from a customer who had sent themselves an email as a test and the profile picture was someone else’s photo. This would happen as soon as the user typed in there email address and Outlook recognized it the photo of the other person would show up. We changed his profile picture in Outlook to be a white blank, but we still had the issue.
The problem was in the person’s contacts. They had a person in their contacts who picture was showing as the unwanted profile picture. We discovered the user had somehow had our customer’s email address not as the email address, but as the second email address. So when our user went to type in their email address it was associated with the person in their contacts.
Let us know if this helped you…
We got a call from a user that just got their laptop upgraded to Windows 10 using Office 2013. When the user tried to create their signature Outlook would freeze. Found a couple of links with suggestions, but this one did the trick.
The trick was to Settings >> Search for Apps. Click on “Apps and Features”, and uninstall “Microsoft Office Desktop Apps” and uninstall it. It did require a reboot, but everything was working after that.
Let us know if this helped you…
Had a user who started to get this message. “Your message couldn’t be delivered because you weren’t recognized as a valid sender”. Logged into their Office 365 Admin account and went to Protection >> Action Center. Saw the user there and clicked “unblock” them. It took a minute, and came back with the user still in the list. I tried to send an email at the user and got the same error. In the Admin panel >> Action Center the user was still listed. I clicked “unblock” again and this time the user wasn’t listed. I tried to send another email, and got the same error again. I see a alert on the Action Center page to go to the new “Restricted Users page“. This page didn’t show the user being blocked.
I looked at the error in the Non-Deliverable Report in the returned email. The error in the message is “550 5.1.8 Access denied, bad outbound sender“.
This page was a help to let me know it could take a few hours for the email to resume.
Let us know if this helped you…
