Difficulty setting up a new 365 account manual migration (Autodiscover issue)

Run Microsoft Support and Recovery Assistant to diagnose the issue.

1.Start Registry Editor.

In Windows 10 and Windows 8, press the Windows Key + R to open a Run dialog box. Type regedit.exe and then press OK.

In Windows 7, click Start , type regedit in the Search programs and files box, and then press Enter.

2.Locate and then select the following registry subkey:


Notex.0 in this registry path corresponds to the Outlook version (16.0 = Outlook 2016, 15.0 = Outlook 2013, 14.0 = Outlook 2010, 12.0 = Outlook 2007).

3.Review the following possible DWORD values that may be located under the \Autodiscover subkey.

•ExcludeHttpsRootDomain – ignores Autodiscover.XML on domain website
•ExcludeScpLookup – Ignores local hosted exchange settings

Full Article link

Windows 10 update loop

In an elevated CMD type
Net stop bit
Net stop wuauserv
Net stop cryptsvc

Rename systemroot\softwaredistribution to softwaredistribution.old
And systemroot\system32\catroot2 to catroot2.old

Net start bit
Net start wuauserv
Net start cryptsvc

And restart pc

Migrate Windows DHCP server

A few weeks ago at work, I was tasked with the project of decommissioning one of our older Windows Server 2008 machines and upgrading it to Windows 2012. I was initially a little worried, seeing as this server ran a lot of key roles, such as DHCP, DNS, was a Domain Controller, and also acted as a print server as well as a few other services. As I was migrating the DHCP role, I wondered if there was a simple way of exporting all of the settings, such as DHCP scope and reserved IP addresses. Turns out there was, and it went off without a hitch!

Here’s how I did it:

Log on to the old/existing DHCP server.

Click Start, click Run, type cmd in the Open box, right-click, and then “Run as Administrator”.

On the Action menu, click Backup.

Type netsh dhcp server export C:\Users\\Desktop\dhcp.txt all, and then press ENTER.

Install the DHCP role on the new (2012) DHCP server using Server Manager.

Copy the exported DHCP text file to the desktop of the new DHCP server.

Verify that the DHCP service is installed and started on the new DHCP server.

Click Start, click Run, type cmd in the Open box, right-click, and then “Run as Administrator”.

Type netsh dhcp server import C:\Users\\Desktop\dhcp.txt all, and then press ENTER

Open DHCP console on the new server.

In the console tree, right-click DHCP.

Select “Authorize”.
If your old DHCP server is in the same network/subnet as the new DHCP server, you’ll notice that the old DHCP server has been de-authorized automatically. This is to prevent two DHCP servers from handing out conflicting addresses.

Check to make sure that your new DHCP has all of the same settings, options, scopes, and reservations set as the current one. If done correctly, everything should have been brought over. I was pretty impressed as to how well this worked and just how seamless it truly was.