Deployment Error. Unknown Error

[Guest]

[Tim B.]

w-e-v, currently ESM Server uses the same deployment mechanism for both local and remote deployment types. So it's an expected behaviour.

[w-e-v]

Thank you Tim.

So what do I do now?
Should I type something else, instead of "admin$" (maybe the real Administrator username of each PC) in order to receive a prompt to enter the password?

If you read again the answers I get in the console, these are:
The network path was not found

[shan77]

So what do I do now?
Should I type something else, instead of "admin$" (maybe the real Administrator username of each PC) in order to receive a prompt to enter the password?

If you read again the answers I get in the console, these are:
The network path was not found

My 2nd problem is exactly the same...but the ping cmd is working...

[shan77]

w-e-v:
the query: \\IPadress\admin$ isn't working, when you run it from command prompt.
it works only from windows explorer (windows key+E)
on the remote pc, it must have an administrator user (f.e: WEV)
So, I already can reach the pcs.

I think under deployment menu--->credentials, you must provide that administrator user and its password.

greetings

[w-e-v]

Shan77:

Thank you for your message.
I run the query in Windows Explorer.
And the PCs are reached. We input the Admin User and Admin Password and everything works fine.

However, the Deployment Error (1222) its always there with ESM 2.0


How did you fix it?
Maybe Tim from COMODO can recommend something else?

[shan77]

Not at all!
Unfortunately I couldn't fix it. Yet...
I think the problem of ours is, that on our PCs the users log in as Guest. I found clues, that ESM is trying to install as guest user, because there are a deployment folder in document and settings -> Guest -> Temp directory.
But i will not give up, the problem must be solved. 

Shan77:

Thank you for your message.
I run the query in Windows Explorer.
And the PCs are reached. We input the Admin User and Admin Password and everything works fine.

However, the Deployment Error (1222) its always there with ESM 2.0


How did you fix it?
Maybe Tim from COMODO can recommend something else?

[w-e-v]

But i will not give up, the problem must be solved. 

Hope you can solve the problem. To be honest, I dont know where to go with this issue or what other things I can keep trying.

But I think COMODO should be able to help us solving this problem.
A couple of days are gone since their last reply, and we are still experiencing the same problem.

[Tim B.]

Guys, thank you for your personal interest in this ESM functionality and sorry for so long silence from my side.

Unfortunately ESM Agent deployment may be quite unstable because it depends on Windows sharing feature which works very differently on different machines, a lot of things are hidden in registry and security configurations.

As I understood you both have passed \\target\\admin$ share access test from ESM server machine (remote target \WINDOWS folder content opened), but ESM anyway fails to deploy with 1222 error? Correct?

[shan77]

Hi Tim!
Exactly what we are talking about.
Let us also add, not only agent deploying, but CIS updating via ESM is quite unstable too...

[w-e-v]

Thank you Tim for your interest and time.
Yes, we are confirming that what you explained is exactly what is happening to us both.

Regards,

[Tim B.]

Hi guys,

Thank you for your patience. I have prepared a small tool - a recipe program that tests different types of connections to remote endpoints.
It is attached to this post as ZIP archive. Download it and extract archive's content to any place on ESM server machine. The recipe is a console program that should be run under admin privileges. So run Command Prompt (cmd.exe) as administrator and navigate to the recipe folder (using cd command). Then run the following command:

Code:

EsmRemoteRecipe remote_host [-l login -p password]

Where:
remote_host - Remote target name or IP address.
login - Remote admin user's login.
password - Remote admin user's password.

For example:

Code:

EsmRemoteRecipe 192.168.1.10 -l tim -p password

Login with password may be skipped, in this case they will be prompted later.

The recipe starts to test connections. It writes tests results data to console and to recipe.log file located where EsmRemoteRecipe.exe is placed. Note that tests execution may take some time.

Please test issued endpoints and those endpoints which are accessible by ESM normally. Post here your log files that I could investigate them.

Looking forward to hearing any feedback from you!

[shan77]

Thanks Tim!
We will try it soon..

[Radu Georghiu]

Hi, Same error 1222
First endpoint is actually the server
Second is a Virtual machine

recipe log
DSC: Host: 192.168.0.146
DSC: Login: Ranny
DSC: Using LOGON32_LOGON_NETWORK
DSC: Connection FAILED using LOGON32_LOGON_NETWORK. Error:
System.DllNotFoundException: Unable to load DLL 'mpr.dll': Exception from HRESULT: 0x8007007E
   at NetworkHelper.WNetAddConnection2(NETRESOURCE& netResource, String password, String username, Int32 flags)
   at NetworkHelper.GrantNetworkAccessToRemoteComputer(String userName, String password, String remotePath, Boolean impersonateAsNetworkService)
   at EsmRemoteRecipe.DescentHelperRecipe.TryLogin(Boolean impersonateAsNetworkService, String login)
   at EsmRemoteRecipe.DescentHelperRecipe.TryAlternativeLogin1(Boolean impersonateAsNetworkService)
   at EsmRemoteRecipe.DescentHelperRecipe.InitializeInternal(Boolean impersonateAsNetworkService)
   at EsmRemoteRecipe.DescentHelperRecipe.InitWithHostName(Boolean impersonateAsNetworkService)
   at EsmRemoteRecipe.DescentHelperRecipe.Init(Boolean impersonateAsNetworkService)
   at EsmRemoteRecipe.DescentHelperRecipe.Init()
   at EsmRemoteRecipe.Program.Test(Args args)
DSC: Using LOGON32_LOGON_SERVICE
  DSC: Conct SUCC (NSV \\192.168.0.146\ADMIN$   192.168.0.146\Ranny err: 0)
DSC: Connection SUCCEEDED using LOGON32_LOGON_SERVICE

DSC: Host: 10.0.2.15
DSC: Login: Ranny
DSC: Using LOGON32_LOGON_NETWORK
DSC: Connection FAILED using LOGON32_LOGON_NETWORK. Error:
System.DllNotFoundException: Unable to load DLL 'mpr.dll': Exception from HRESULT: 0x8007007E
   at NetworkHelper.WNetAddConnection2(NETRESOURCE& netResource, String password, String username, Int32 flags)
   at NetworkHelper.GrantNetworkAccessToRemoteComputer(String userName, String password, String remotePath, Boolean impersonateAsNetworkService)
   at EsmRemoteRecipe.DescentHelperRecipe.TryLogin(Boolean impersonateAsNetworkService, String login)
   at EsmRemoteRecipe.DescentHelperRecipe.TryAlternativeLogin1(Boolean impersonateAsNetworkService)
   at EsmRemoteRecipe.DescentHelperRecipe.InitializeInternal(Boolean impersonateAsNetworkService)
   at EsmRemoteRecipe.DescentHelperRecipe.InitWithHostName(Boolean impersonateAsNetworkService)
   at EsmRemoteRecipe.DescentHelperRecipe.Init(Boolean impersonateAsNetworkService)
   at EsmRemoteRecipe.DescentHelperRecipe.Init()
   at EsmRemoteRecipe.Program.Test(Args args)
DSC: Using LOGON32_LOGON_SERVICE

[Tim B.]

Hi runnyme!

Thanks for diagnostics! It surely will help us to resolve the issue. It looks like the last machine's (10.0.2.15) log is truncated. Because nothing goes after

DSC: Using LOGON32_LOGON_SERVICE

I may guess it finishes the same way as 192.168.0.146 log, right?

[shan77]

Hi Tim!

Our recipes: ... attached

[Tags:]