Home > Active Directory, Microsoft, Security, Windows > ESET Smart Security makes problems when migrating computers between domains

ESET Smart Security makes problems when migrating computers between domains

I was facing weird problem with computers when I was trying to migrate computer accounts between two active directory domains. When you use ADMT to migrate computer accounts, ADMT installs ADMT Agent on computer and this ADMT Agent makes all changes during computer account migration.


When there was computer with ESET Smart Security installed I had following problems. First problem was that migration failed and in ADMT log file I received following error:

2013-04-12 16:29:54 The Active Directory Migration Tool Agent will be installed on CENTRALA.DOMAIN.LOCAL
2013-04-12 16:29:59 WRN1:0000 Could not open SCManager on \\CENTRALA.DOMAIN.LOCAL : GetLastError() returned 5
2013-04-12 16:29:59 WRN1:7015 Failed to connect to the service control manager on \\CENTRALA.DOMAIN.LOCAL, rc=5   Access is denied.
2013-04-12 16:29:59 ERR2:7006 Failed to install agent on \\CENTRALA.DOMAIN.LOCAL, rc=5   Access is denied.

 So error number 5 means I have no rights somewhere. After reading couple pages of ADMT documentation I found out that ADMT installs ADMT Agent using Admin share called ADMIN$. So I tried to access ADMIN$ share on computer CENTRALA.DOMAIN.LOCAL. I received following error:

Problem with NETLOGON service

I have never seen such an error:”An attempt was made to logon, but the network logon service was not started.”. I checked services on computer CENTRALA.DOMAIN.LOCAL and Windows was right. Service NETLOGON was Disabled!


I had to temporary turn off ESET Smart Security (I would preffer not use this software at all 🙂 ) and also enable and start service NETLOGON.


Every computer I migrated and had installed ESET Smart Security had the same problems. So IMHO ESET Smart Security has changed service NETLOGON to Disabled. I really don’t understand why this is necessary, but I think it’s not right way “smart security product” should protect your computer.

I found one article about disabling NETLOGON service as security practice. It’s maybe good security practice, but there is also pitfall stated on websie:

If you disable the NetLogon service, a workstation no longer functions reliably as a domain member. This setting may be appropriate for some computers that do not participate in domains. However, it should be carefully evaluated before deployment.

I’m wondering what other functions are not available when NETLOGON disabled (besides not accessible ADMIN$ share) on domain member computer.

I hope this helps someone 🙂

  1. Andrew
    October 20th, 2014 at 22:56 | #1

    This resolved the issue that I had. I had the exact same issue/error message when using a Quest Migration tool for Active Directory and was not able to ping the machine or reach the admin share. The machine was located outside the country and they were using ESET and once it was disabled we were able to successfully migrate the machine.

    Thanks for the post!

  2. October 24th, 2014 at 07:28 | #2

    Yes, ESET gave me a lots of headaches 🙂

  3. May 17th, 2015 at 00:43 | #3

    Ondro, tak prave sme nato prisli aj my – a ze preco nam nechdoi ADcko 🙂 fck! Nechapem preco tuto funkciu nechavaju zapnutu ako “default”… a katastrofa je, ze ty si to pisal 2013 a doteraz 2015 to NEOPRAVILI! hamba-.-

  4. May 18th, 2015 at 11:15 | #4

    Vies ako 🙂 Eset je Eset a Esetom ostane…

  5. KERR
    January 20th, 2017 at 04:31 | #5

    I’m getting the same errors (ADMT) but NETLOGON is running OK, and not using ESET, any thoughts?

  6. January 24th, 2017 at 13:57 | #6

    If you cannot access admin shares (for example ADMIN$) you can look if you have enabled/disabled admin shares (more at https://support.microsoft.com/en-us/help/954422/how-to-remove-administrative-shares-in-windows-server-2008)

  1. No trackbacks yet.