Run SFC from Windows repair console
sfc /scannow /offbootdir=d:\ /offwindir=d:\windows
If users who are using Office 2007 or above to connect to Office 365 suddenly cant connect and it prompts for password continually, try the following link:
A very useful tool to reset Windows Update
Also with Hyper-V, dont mount the virtual hard drives in the parent OS if you have snapshots in use.
You can do a repair install of a server OS by inserting the disc and running the “upgrade” on top of itself.
Before we begin we need to gather a bit of information.
1. Go to testexchangeconnectivity.com
2. Select the Office 365 tab
3. Under Microsoft Office Outlook Connectivity Tests. click on Outlook Autodiscover
4. Fill in the information: Email address and Microsoft Account are your same Office 365 Username
5. Password, is your Office 365 password.
6. Check “I understand…” and continue.
7. When the test is done hit Expand All
8. If you are on google chrome, hit ctrl+F and type “
The lcnsregs.dat file on the server cannot be accessed.
Locate and rename this file in the Timeslips Installation folder.
Note: This file is HIDDEN and always resides in the same folder that the Timeslip.cfg file resides. Be sure to view hidden files to find this file. This solution should almost always be the resolution when you receive this error opening the Timeslips program.
Once the lcnsregs.dat file is deleted, clear the licenses from the station administrator by following this article on how to clear licenses
I respond to a lot of questions answered on an internal alias for Windows Installer support, some of which inspire posts on my blog. That alias is also archived in a public folder on our corporate Exchange server so there is a vast treasure trove of information for reading – far too much to use Outlook‘s built-in search.
For those also in an environment where public folders exist in Exchange full of information, there are many ways to find information quickly. I prefer to use Windows Desktop Search. To set this up, follow these instructions:
This guide is intended to provide step by step instructions on how to migrate from Small Business Server 2003 to Windows 2008 R2 with Exchange 2010.
For this migration to work you will need the following software:
When doing a Office 365 migration, depending on the migration the ability to respond to or forward emails pre-migration can become broken! This is because the user X500 addresses from the source email system are invalid on the target system. You can manually add the X500 address on the target system using the information from the source system. Here is a brief run down of how to accomplish this with powershell:
1) Run powershell as an admin
2) $LiveCred = Get-Credential
3) $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell/ -Credential $LiveCred -Authentication Basic –AllowRedirection
4) Set-ExecutionPolicy Unrestricted -Force
5) Import-PSSession $Session