Seite 1 von 1
Help with opsi-client-agent error please
Verfasst: 31 Jul 2013, 20:22
von theothermatt
Hello all!
I am trying to install the opsi client on a machine via the server's command line and am getting an error:
Code: Alles auswählen
root@OPSI:/opt/pcbin/install/opsi-client-agent# ./opsi-deploy-client-agent -v -r -u administrator -p scrubbedpassword D10673
[notice] Starting deployment to host 'd10673..net'
[notice] Querying for ip address of host 'd10673..net'
[notice] Got ip address '10.x.x.x' from syscall
[notice] Pinging host 10.x.x.x ...
[notice] Host 10.x.x.x is up
[notice] Getting hardware ethernet address of host 'd10673..net'
[warning] Failed to get hardware ethernet address for host 'd10673'
[notice] Creating client 'd10673..net'
[notice] Testing winexe
[error] Deployment to 'd10673..net' failed: Failed to execute command on host 'd10673': winexe error: Command '/usr/bin/winexe -U 'administrator%*** confidential ***' //d10673 'cmd.exe /C "del /s /q c:\tmp\opsi-client-agent_inst && rmdir /s /q c:\tmp\opsi-client-agent_inst || echo not found"'' failed (1):
ERROR: Failed to open connection - NT_STATUS_OBJECT_NAME_NOT_FOUND
So, I tried Winexe by itself:
Code: Alles auswählen
root@OPSI:/opt/pcbin/install/opsi-client-agent# winexe -U administrator%scrubbedpassword //D10673..net 'cmd.exe'
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>
Works fine.
Does anyone have a clue what is going wrong? Other than this, OPSI is up and running beautifully, I can manually deploy agents via the "mapped drive/service_setup.cmd" method and even install software programs on demand. This last little bit is proving to be too much for me
Thanks in advance!
Re: Help with opsi-client-agent error please
Verfasst: 01 Aug 2013, 10:31
von n.wenselowski
Hello theothermatt,
did you know that
support contracts are available?
One thing that sticks out to me is that opsi-deploy-client-agent does its execution only against the hostname of the client. You on the other hand seem to specify the FQDN of the client when running Winexe.
Does it work for you if run opsi-deploy-client-agent with the FQDN of the client?
Kind regards
N. Wenselowski
Re: Help with opsi-client-agent error please
Verfasst: 01 Aug 2013, 16:14
von theothermatt
n.wenselowski hat geschrieben:Hello theothermatt,
did you know that
support contracts are available?
One thing that sticks out to me is that opsi-deploy-client-agent does its execution only against the hostname of the client. You on the other hand seem to specify the FQDN of the client when running Winexe.
Does it work for you if run opsi-deploy-client-agent with the FQDN of the client?
Kind regards
N. Wenselowski
Thanks for the quick response!
I did know about Support Contracts. If I can get this going in test I will for sure bring that up in my demo to my director.
Ran it again against the FQDN of that machine and it failed with the same error.
Code: Alles auswählen
root@OPSI:/opt/pcbin/install/opsi-client-agent# ./opsi-deploy-client-agent -v -r -u administrator -p scrubbedpassword D10673..net
[notice] Starting deployment to host 'd10673..net'
[notice] Querying for ip address of host 'd10673..net'
[notice] Got ip address '10.x.x.x' from syscall
[notice] Pinging host 10.x.x.x ...
[notice] Host 10.x.x.x is up
[notice] Getting hardware ethernet address of host 'd10673..net'
[warning] Failed to get hardware ethernet address for host 'd10673'
[notice] Creating client 'd10673..net'
[notice] Testing winexe
[error] Deployment to 'd10673..net' failed: Failed to execute command on host 'd10673': winexe error: Command '/usr/bin/winexe -U 'administrator%*** confidential ***' //d10673 'cmd.exe /C "del /s /q c:\tmp\opsi-client-agent_inst && rmdir /s /q c:\tmp\opsi-client-agent_inst || echo not found"'' failed (1):
ERROR: Failed to open connection - NT_STATUS_OBJECT_NAME_NOT_FOUND
Interestingly, winexe gives the same error when I dont use the FQDN:
Code: Alles auswählen
root@OPSI:/opt/pcbin/install/opsi-client-agent# winexe -U administrator%scrubbedpassword //D10673 'cmd.exe'
ERROR: Failed to open connection - NT_STATUS_OBJECT_NAME_NOT_FOUND
*EDIT* I just noticed the -c option. Giving that a try...
Code: Alles auswählen
root@OPSI:/opt/pcbin/install/opsi-client-agent# ./opsi-deploy-client-agent -v -r -c -p scrubbedpassword D10673..net
[notice] Starting deployment to host 'd10673..net'
[notice] Querying for ip address of host 'd10673..net'
[notice] Got ip address '10.x.x.x' from syscall
[notice] Pinging host 10.x.x.x ...
[notice] Host 10.x.x.x is up
[notice] Getting hardware ethernet address of host 'd10673..net'
[warning] Failed to get hardware ethernet address for host 'd10673'
[notice] Creating client 'd10673..net'
[notice] Testing winexe
[notice] Patching config.ini
[notice] Copying installation files
[error] Command '/usr/bin/winexe -U 'Administrator%*** confidential ***' //d10673..net 'cmd.exe /C "del /s /q c:\tmp\opsi-client-agent_inst && rmdir /s /q c:\tmp\opsi-client-agent_inst"'' failed (2):
Could Not Find c:\tmp\opsi-client-agent_inst
The system cannot find the file specified.
[error] Deployment to 'd10673..net' failed: Command '/usr/bin/smbclient //d10673..net/c$ -U 'Administrator%*** confidential ***' -c 'prompt; recurse; md tmp; cd tmp; md opsi-client-agent_inst; cd opsi-client-agent_inst; mput files; mput utils; cd files\opsi\cfg; lcd /tmp; put i9CgcPsrgw_config.ini config.ini; exit;'' failed (1):
session setup failed: NT_STATUS_LOGON_FAILURE
So, looks like I am past the original issue and on to a new one
Re: Help with opsi-client-agent error please
Verfasst: 01 Aug 2013, 16:36
von n.wenselowski
Hello theothermatt,
please try running the opsi-deploy-client-agent with -c.
opsi-deploy-client-agent --help shows you what options are available.
Kind regards
N. Wenselowski
Re: Help with opsi-client-agent error please
Verfasst: 01 Aug 2013, 19:22
von theothermatt
n.wenselowski hat geschrieben:Hello theothermatt,
please try running the opsi-deploy-client-agent with -c.
opsi-deploy-client-agent --help shows you what options are available.
Kind regards
N. Wenselowski
I think we both figured that out at the same time
I did that, and I changed the user to a domain user with admin rights instead of the local administrator account and it worked.
Thanks again for your help!