dcpromo demoting Win2k3 Server Failed to configure the service NETLOGON

Failed to configure the service NETLOGON as requested.
“The wait operation timed out”

dcpromo demoting Win2k3 Server Failed to configure the service NETLOGON

dcpromo demoting Win2k3 Server Failed to configure the service NETLOGON

The error message seen above in the image can occure when demoting an Active Directory domain controller.

Error demoting domain controller: Failed to configure the service NETLOGON

Received this error while demoting an SBS 2003 Active Directory domain controller as a final part of a migration to SBS 2011.  After overcoming obstacles to get exchange removed, this error came up during the dcpromo process in which the domain control that was formally y the SBS 2003 server would be turned into a member server.

The solution to this problem was simple and hopefully it is for you too if you have come across this post looking for an answer should you be confronting this right now.

Change the DNS configuration on the server you are trying to demote and be sure it’s first DNS server configured in the TCP configuration is assigned to the SBS 2011 server or just another Active Directory DNS server if you are just demoting a non-sbs domain controller.


Share

Advertisements

Out-of-Office Not Working in Outlook 2007 or Outlook 2010

Outlook Out-of-Office Not working

Outlook Out-of-Office Not working

Out-of-Office Not Working in Outlook 2007

The Microsoft Exchange server version does not matter. It can be Exchange 2010 or exchange 2007, Outlook out-of-office functionality doesn’t work. The user profile for Outlook sets up fine without error but when the user tries to setup Out-of-office emails, they cannot. What can make this an even more peculiar case is that some users on the same network connected to the same exchange server and using the same version of Outlook out-of-office works fine. To make it even more interesting, setting up a different user on the same computer, meaning a user who has not signed in on that computer before, works fine too.

In such a case, the interesting fact to find out is if the user had used Microsoft BPOS or Microsoft Hosted Email services. This problem was found for users at an organization who had used Microsoft BPOS service in the past and not have migrated to their own exchange server.
The solution for my company was the following registry settings had to be changed back to their defaults. Microsoft BPOS changed service these values form their defaults.

[HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\AutoDiscover]
“PreferLocalXML”=dword:00000001
“ExcludeHttpRedirect”=dword:00000000
“ExcludeHttpsAutodiscoverDomain”=dword:00000001
“ExcludeHttpsRootDomain”=dword:00000001
“ExcludeScpLookup”=dword:00000001
“ExcludeSrvLookup”=dword:00000001
“ExcludeSrvRecord”=dword:00000001

The above registry settings are telling Outlook to NOT use Autodiscover and to instead use a local XML file to tell it how to connect to the Exchange server.

Change all the 00000001 to 00000000 . All the values should be zeros.

This worked perfectly. We were able to even do a remote regedit to remotely access the registry and to support it, didn’t even have to remote control the user’s computer desktop. Instead of even remote controlling users computers because there are multiple to many computers to do, you can use login scripts to accomplish the task.

Exchange 2010 ECP login The user name or password you entered isn’t correct.

Exchange 2010 ECP login The user name or password you entered isn't correct.

Exchange 2010 ECP login The user name or password you entered isn’t correct.

 A method used to resolve this problem was to change the authentication methods used by the ECP (exchange control panlel) virtual directory. The settings below worked. After they were applied, the user who had the correct permissions was able to login and manage their account and other user accounts. ECP-outlook-web-app-exchange-2010-user-name-password-entered-isn't-correct-authentication-setting

 Once the aauthentication settings for ecp were updated, the user was able to login through OWA by licking the options and see all options or directly using the ecp url.

Desktops, Servers, and Networks, oh MY!: Outlook Web App didnt initialize – Exchange 2010

Desktops, Servers, and Networks, oh MY!: Outlook Web App didnt initialize – Exchange 2010.

This is a useful post of how to correct a common authentication problem with outlook web app (OWA) on Microsoft exchange 2010 and IIS 7 . The server version is of course windows server 2008 R2.

The problem is that the login form for owa displays, a test user account is entered but then the next page instead of displayign the user mailbox, an error page is displayed stating that outlook web app did not initialize.