Discovery for non-domain joined servers not working

[lmundere]

Hi,

I would like to discover non-domain windows servers but looks like this is not working, i have an account with admin rights and i can log on with it to the selected server. However when I pass the credentials thru the MID server, it is returning error that Authentication failed, is there anything I need to do on the MID for this to work?

Please note that i have created the credentials in many ways such as

.\username or just username ad then provided the password, and still returning the same error.

Anyone has been successful with this? 

[User511834]

You can try also workgroup\admin name

Also when you say credentials error out, are you getting this message from running test credentials or are you running discovery and getting an authentication type error in the Discovery log? If so can you share that message in the discovery log?

If it fails the test credentials, still try to run discovery as we are noticing on occasion the test credential may give you an authentication error, but when you actually run discovery it runs fine.

[Elizabeth Johns]

It used to be that a non-domain joined status meant isolation. A non-domain joined computer was restricted to the status of being in a lowly workgroup in which every machine was an island unto itself.  Conduent Connect Login

[lmundere · Accepted solution]

Cant find the correct article I found here but for non domain servers, we had to add one parameter in the registry and then it started working. The parameter is as follow

UAC restrictions need to be disabled. The discovery couldnt work without addind the LocalAccountTokenPolicy set to 1.

How to do it: The parameter needs to be added to registry under

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System

parameter is DWORD (32-bit) with name LocalAccountTokenFilterPolicy set to 1