Client installation using service_setup.cmd
-
- Beiträge: 25
- Registriert: 18 Feb 2013, 11:33
Re: Client installation using service_setup.cmd
Thanks a lot .
It worked and the configuration files etc all have been created .
Now , I am using 4.2.1.1 , p.no 33/83 .
I have mapped a drive h: , in the client mc , under win7 .
Then from the command prompt h:/>opsi-client-agent\service_setup.cmd is executed .
The service_setup.cmd is giving an error :
Opsi_winst not found
<File "files\opsi\opsi-winst\winst32.exe" does not exist>
installation aborted
I have opened the service_setup.cmd and can corrected the .cmd file but could not save it ;
also tried to copy the winst32.exe in the folder "files\opsi\opsi-winst\" but the samba share did not allow to do so as I do not have rights .
Pls help -- what to do now ....
best regards
barun
- SisterOfMercy
- Beiträge: 1556
- Registriert: 22 Jun 2012, 19:18
Re: Client installation using service_setup.cmd
Oops, never mind about that.
Have you used the basic troubleshooting steps?
opsi-setup --set-rights
And you do not need to map a network drive on the client machine. Just add the machine to the opsi configed interface, and manage from there.
Re: Client installation using service_setup.cmd
I have seen this in a inhouse-workshop. In our case, it was the Antivirus utility, which has marked opsi-winst32.exe as possible dangerous file and have deleted the file, after copy but before the installation from opsi-client-agent starts. You should check your Antivirus Logfiles. If I'm right, you can normaly put the opsi-winst32.exe file in a local Whitelist to get a workarround for this issue and please post your antivirus-Vendor, so we can contact them to get a solution for this problem.
Vielen Dank für die Nutzung von opsi. Im Forum ist unser Support begrenzt.
Für den professionellen Einsatz und individuelle Beratung empfehlen wir einen Support-Vertrag und eine Schulung.
Gerne informieren wir Sie zu unserem Angebot.
uib GmbH
Telefon: +49 6131 27561 0
E-Mail: sales@uib.de
-
- Beiträge: 25
- Registriert: 18 Feb 2013, 11:33
Re: Client installation using service_setup.cmd
Thank you - very much -- all the directories , sub-directories , samba shared folders are updated correctly / properly .
1 ) Now , I am following the item # 4.2.1.1 ------ usage of service_setup.cmd .
2 )In the client pc , logged in as Administrator .
3 ) Then , I have mapped a free drive letter h: to the samba shared directory \\<opsiserver>\opsi_depot.
In doing this mapping , I have used the user login :pcpatch and its password , as as created in the step #3.2.6
4 ) then ran cmd command from the start menu .
5) from the command prompt h:\> , i ran the script : h:\>opsi-client-agent\service_setup.cmd , and the following error is shown :
opsi-Winst not found
<File "files\opsi\opsi-winst\winst32.exe" does not exist > ..... installation aborted .
6)grep pcpatch /etc/group provides the following output :
pcpatch
Do I have to use the the user adminuser and its password ....
Pls help .
regards
barun
-
- Beiträge: 25
- Registriert: 18 Feb 2013, 11:33
Re: Client installation using service_setup.cmd
Thanks for your support and advice .
In my case , the file winst32.exe exist , ls -al shows
-rw-rw----opsiconfd pcpatch winst32.exe
I need to find the correct login / password combination from the file config.ini . Where can I find the file config.ini ... /etc/opsi ...
regards
barun
-
- Beiträge: 25
- Registriert: 18 Feb 2013, 11:33
Re: Client installation using service_setup.cmd
Thanks a lot .
It worked and the configuration files etc all have been created .
Now , I am using 4.2.1.1 , p.no 33/83 .
I have mapped a drive h: , in the client mc , under win7 .
Then from the command prompt h:/>opsi-client-agent\service_setup.cmd is executed .
The service_setup.cmd is giving an error :
Opsi_winst not found
<File "files\opsi\opsi-winst\winst32.exe" does not exist>
installation aborted
I have opened the service_setup.cmd and can corrected the .cmd file but could not save it ;
also tried to copy the winst32.exe in the folder "files\opsi\opsi-winst\" but the samba share did not allow to do so as I do not have rights .
In my case , the file winst32.exe exist , ls -al shows
-rw-rw----opsiconfd pcpatch winst32.exe
The user I am using is adminuser and is a member of the group pcpatch
Pls help -- what to do now ....
best regards
barun
-
- Beiträge: 25
- Registriert: 18 Feb 2013, 11:33
Re: Client installation using service_setup.cmd
the error is "files\opsi\opsi-winst\winst32.exe" -----> does not exists ;
but actually winst32.exe exists in :
/var/lib/opsi/depot/opsi-client-agent/files/opsi/opsi-winst/winst32.exe
With chmod 777 I have set the rwx ....
still not working .
pls help
regards
barun
Re: Client installation using service_setup.cmd
i think the file on the local client is not found for installation, not the file on depot-Share. The Errormessage means, that the opsi-winst32.exe file doesn't exist on Client. service_setup.cmd copies all needed files (opsi-client-agent and opsi-winst) from server to a local tmp-directory and starts opsi-winst32.exe on the local machine and install the opsi-client-agent.
Vielen Dank für die Nutzung von opsi. Im Forum ist unser Support begrenzt.
Für den professionellen Einsatz und individuelle Beratung empfehlen wir einen Support-Vertrag und eine Schulung.
Gerne informieren wir Sie zu unserem Angebot.
uib GmbH
Telefon: +49 6131 27561 0
E-Mail: sales@uib.de
-
- Beiträge: 25
- Registriert: 18 Feb 2013, 11:33
Re: Client installation using service_setup.cmd
Now --- can you please provide a solution .....
regards
barun
-
- Beiträge: 25
- Registriert: 18 Feb 2013, 11:33
Re: Client installation using service_setup.cmd
The installer finally run --- but there is an error --- I am enclosing the error log file
1] [2/20/2013 19:26:56] opsi-winst 4.11.3.2 started at >>2/20/2013 19:26:55
[1] [2/20/2013 19:26:56] startmessage opsi-winst created at CentralForm.FormCreate: 2/20/2013 19:26:55
[1] [2/20/2013 19:26:56] startmessage StartProgramModes and create log: 2/20/2013 19:26:55
[1] [2/20/2013 19:26:56]
[1] [2/20/2013 19:26:56] ============ Version 4.11.3.2 WIN32 script "c:\tmp\opsi\setup.ins"
[1] [2/20/2013 19:26:56] start: 2013-02-20 19:26:56
[1] [2/20/2013 19:26:56] on client named "ADSL_IT-PC"
[1] [2/20/2013 19:26:56] loggedin user "Administrator"
[1] [2/20/2013 19:26:56] winst running as "Administrator"
[1] [2/20/2013 19:26:56] winst running with admin privileges
[1] [2/20/2013 19:26:56] winst running in standard script mode
[1] [2/20/2013 19:26:56] [executing: "c:\tmp\opsi\opsi-winst\winst32.exe"]
[1] [2/20/2013 19:26:56] system infos:
[1] [2/20/2013 19:26:56] 40-61-86-33-A6-4C - PC hardware address
[1] [2/20/2013 19:26:56] ADSL_IT-PC - IP name
[1] [2/20/2013 19:26:56] 10.1.10.74 - IP address
[1] [2/20/2013 19:26:56] ENU - System default locale
[1] [2/20/2013 19:26:56] MS Windowds 6.1 32 Bit
[1] [2/20/2013 19:26:56]
[1] [2/20/2013 19:26:56] LogLevel was 6
[1] [2/20/2013 19:26:56] LogLevel set to 7
[1] [2/20/2013 19:26:56] LogLevel was 7
[1] [2/20/2013 19:26:56] LogLevel set to 7
[1] [2/20/2013 19:26:56] LogLevel was 7
[1] [2/20/2013 19:26:56] LogLevel set to 7
[3] [2/20/2013 19:26:56] Error: service not initialized
[3] [2/20/2013 19:26:56] Error: no connection to service
[1] [2/20/2013 19:26:56] LogLevel was 7
[1] [2/20/2013 19:26:56] LogLevel set to 7
[3] [2/20/2013 19:26:59] Error: retrieveJSONObject --- opsi service problem ----> {"message":"Opsi authentication error: Forbidden: Backend authentication error: Backend authentication error: PAM authentication failed for user 'adminuser': ('Authentication failure', 7)","class":"OpsiAuthenticationError"}
[3] [2/20/2013 19:27:01] Error: retrieveJSONObject --- opsi service problem ----> {"message":"Opsi authentication error: Forbidden: Backend authentication error: Backend authentication error: PAM authentication failed for user 'adminuser': ('Authentication failure', 7)","class":"OpsiAuthenticationError"}
[4] [2/20/2013 19:27:01] opsi service version could not retrieved, perhaps no connection
[3] [2/20/2013 19:27:01] Error: no connection to service
[1] [2/20/2013 19:27:01] LogLevel was 7
[1] [2/20/2013 19:27:01] LogLevel set to 7
[1] [2/20/2013 19:27:01] LogLevel was 7
[1] [2/20/2013 19:27:01] LogLevel set to 7
[1] [2/20/2013 19:27:45] LogLevel was 7
[1] [2/20/2013 19:27:45] LogLevel set to 7
[3] [2/20/2013 19:27:46] Error: retrieveJSONObject --- opsi service problem ----> {"message":"Bad hostname: 'adsl_it-pc'","class":"ValueError"}
[3] [2/20/2013 19:27:46] Error: -> {"message":"Bad hostname: 'adsl_it-pc'","class":"ValueError"}
[1] [2/20/2013 19:27:46] LogLevel was 7
[1] [2/20/2013 19:27:46] LogLevel set to 7
[3] [2/20/2013 19:27:46] Error: retrieveJSONObject --- opsi service problem ----> {"message":"Bad fqdn: 'adsl_it-pc.uib.local'","class":"ValueError"}
[3] [2/20/2013 19:27:46] Error: -> {"message":"Bad fqdn: 'adsl_it-pc.uib.local'","class":"ValueError"}
[1] [2/20/2013 19:27:46] LogLevel was 7
[1] [2/20/2013 19:27:46] LogLevel set to 7
[1] [2/20/2013 19:27:46] LogLevel was 7
[1] [2/20/2013 19:27:46] LogLevel set to 7
[3] [2/20/2013 19:27:46] Error: retrieveJSONObject --- opsi service problem ----> {"message":"Bad hostname: 'adsl_it-pc'","class":"ValueError"}
[3] [2/20/2013 19:27:46] Error: -> {"message":"Bad hostname: 'adsl_it-pc'","class":"ValueError"}
[3] [2/20/2013 19:27:46] Error: retrieveJSONObject --- opsi service problem ----> {"message":"Bad fqdn: 'adsl_it-pc.uib.local'","class":"ValueError"}
[3] [2/20/2013 19:27:46] Error: -> {"message":"Bad fqdn: 'adsl_it-pc.uib.local'","class":"ValueError"}
[3] [2/20/2013 19:27:46] Error: Could not get hostkey - aborting
[1] [2/20/2013 19:27:53] ___________________
[1] [2/20/2013 19:27:53] script finished
[1] [2/20/2013 19:27:53] 13 errors
[1] [2/20/2013 19:27:53] 1 warning
[1] [2/20/2013 19:27:53]
[1] [2/20/2013 19:27:53]
[1] [2/20/2013 19:27:53] ============ opsi-winst Version 4.11.3.2 WIN32 is regularly exiting. Time 2013-02-20 19:27:53 .
Request , pls help to resolve this error .
regards
barun