I'm adding a third tool to my chest on recovering MS Word (or other Office documents).
You can access ASD files (autorecover files) here:
%userprofile%\AppData\Roaming\Microsoft\Word
Other places to look for missing files (per this post):
C:\Users\%username%\AppData\Local\Microsoft\Windows\Temporary Internet Files\Content.Outlook
Or via this method to recover unsaved Word docs:
http://t-solve.blogspot.com/2014/09/retrieving-document-from-office-2010.html
Friday, October 24, 2014
Wednesday, October 15, 2014
Firefox opens up with a black screen in all profiles
I had a Dell Latitude E6220 on 32 bit Windows 7 SP 1 and each time I'd open up Firefox in any profile, the screen was totally black. This did not happen in safe mode (hold down shift while starting Firefox) or when I RDP'd to the computer. I reset Firefox settings to no avail.
The solution was to disable hardware acceleration via Options -> Advanced. If your Firefox is opening up with the black screen, you can disable hardware acceleration in safe mode.
The solution was to disable hardware acceleration via Options -> Advanced. If your Firefox is opening up with the black screen, you can disable hardware acceleration in safe mode.
Saturday, October 4, 2014
SSL cert errors for old Exchange server after you've already moved to Office365
My users began getting SSL cert errors in Outlook after the SSL cert on my old mail server expired. This was weird because I had moved my company's email to Office365 more than a year earlier. It looked something like this:
Quick research led to the idea that Outlook was looking at the autodiscover for the internal server when connected to the LAN as opposed to the CNAME record that pointed to autodiscover.outlook.com
The fix . . .
First run this on your old mail server in an Exchange shell to see where your autodiscover is currently pointing:
Get-ClientAccessServer | fl AutoDiscoverServiceInternalUri
If it's pointing to your internal server with the expired certificate, that's a problem. To fix that, run this command in the Exchange shell (assuming your server is named server1):
Set-ClientAccessServer -Identity "server1" -AutoDiscoverServiceInternalUri "https://autodiscover.outlook.com" -AutoDiscoverSiteScope "Mail"
or I could disable internal autodiscover via this command (assuming your server is named server1):
Set-ClientAccessServer -Identity “server1″ -AutoDiscoverServiceInternalUri $NULL
Quick research led to the idea that Outlook was looking at the autodiscover for the internal server when connected to the LAN as opposed to the CNAME record that pointed to autodiscover.outlook.com
The fix . . .
First run this on your old mail server in an Exchange shell to see where your autodiscover is currently pointing:
Get-ClientAccessServer | fl AutoDiscoverServiceInternalUri
If it's pointing to your internal server with the expired certificate, that's a problem. To fix that, run this command in the Exchange shell (assuming your server is named server1):
Set-ClientAccessServer -Identity "server1" -AutoDiscoverServiceInternalUri "https://autodiscover.outlook.com" -AutoDiscoverSiteScope "Mail"
or I could disable internal autodiscover via this command (assuming your server is named server1):
Set-ClientAccessServer -Identity “server1″ -AutoDiscoverServiceInternalUri $NULL
Subscribe to:
Posts (Atom)