I have had a few questions regarding a message “Office 365 authentication did not succeed” suddenly appearing both in the daily reports and the Alert Viewer of Server Essentials. The alert viewer suggests changing the admin account (or refresh it) in the Office 365 tab of the Essentials Dashboard, however doing so fails with a message stating you are using the wrong account or password.
In most cases if you log into the Office 365 site using the domain’s admin e-mail account you will find the password has expired and you are asked to update it. Do so and return to the Dashboard entering the new password which should now allow it to validate and eliminate the error.
Virtual Launch Event for the new Office 365
Date Wednesday, February 27th 8 am PDT and 5 pm PDT
• Learn how the new Office 365 can help people do
their best work in a world of devices and services
• Hear customers talk about how Office 365
is transforming the way they deliver productivity
tools across their organization
• See how Office 365 delivers new experiences
combining the power of social with collaboration,
email and unified communications
• Join in a live Q&A with Microsoft executives
and product experts
Just as a “heads up” to our clients; there have been a large number of phishing e-mails lately claiming to be a LinkedIn reminder advising there is a pending invitation to add a new contact. These look quite legitimate.
Always avoid clicking on links in e-mails, it is far better to visit the site in a normal fashion and check your messages and notifications on the site. However to confirm the message’s legitimacy, hover your mouse over the link and you will see the true site destination in a popup. Clicking on a masked link could be disastrous, a virus or an attempt to obtain user names and passwords.
I recently came across an instance of Outlook 2007 which would not open. A popup reported; “Cannot start Microsoft Office Outlook. Cannot open the Outlook window. Invalid XML, the view cannot be loaded”. This was only occurring on 1 PC, for one user, in an SBS 2008 environment. If the user ran Outlook on another PC, there was no problem so it was obviously a local problem. Doing a repair install of office did not resolve, nor did the diagnostics suggested when Googling the issue. Assuming it was a problem with the Xml file; I closed Outlook, renamed the Outlook.xml file (safer than deleting), and restarted Outlook to find the problem was resolved. Should you wish to try the same solution, the file path with Office 2007/2010, on Vista\Win 7 is C:\Users\<user name>\AppData\Roaming\Microsoft\Outlook\Outlook.xml You will need to enable “Show hidden files, folders, and drives” and “Hide extensions of known file types” to view.
When opening Office 2010 documents such as Word and Excel using a VPN client, you will receive a warning on the menu bar which reads; ” Protected View This file originated from an Internet location and might be unsafe. Click for more details. Enable Editing”.
Microsoft has provided options to add trusted network locations within the trust center in Word, Excel, and other Office 2010 applications, which also requires checking “allow trusted Locations on my network”. However it does not accept using IP addresses such as \\192.168.123.123\ShareName. You can use the UNC path but that also requires proper name resolution be set up for DNS.
The simple solution is to simply make sure DNS is configured for the remote domain by adding the DNS suffix to the VPN/PPP network adapter. This allows you to open the documents located on the remote domain without the warning error, and without configuring Trusted Locations. To do so, view properties of the VPN virtual network adapter and under the DNS tab of the advanced TCP/IPv4 properties, add your internal remote domain, in the “DNS suffix for this connection” box, such as MyDomain.local.
Then connect to the remote resource using the UNC name such as \\ServerName\ShareName. If the client computer is a member of the domain it will immediately connect, if not you will be prompted for credentials
the first time you connect. For the user name use the format MyDomain\UserName. So long as the local
session is active you will not be prompted for credentials again, even if the VPN connection is disconnected and reconnected.