Hi,
Is there a way to include the OPSI agent in the system image? I noticed that there's a PChostkey unique to each computer and generated during installation of the agent. It uses the fully qulified domain name also. I hope there's a way to do it so we don't push the agent after commissioning the machine. Thanks.
OPSI agent in system image
Re: OPSI agent in system image
Perhaps, what you could do is to try to integrate a "run once" batch that is called at the end of the main os installation. This batch could then mount \\opsi_server\opsi_depot and run the service_setup.cmd or silent_setup.cmd from opsi_client_agent folder to set up the agent. Thisd would install the client in a correct way and you don't have to fiddle around with unique key and such...
See this: http://www.tech-recipes.com/rx/21558/ho ... plete-cmd/
See this: http://www.tech-recipes.com/rx/21558/ho ... plete-cmd/
Wer mir einen Kaffee spendieren mag , bitte gerne!
opsi PackageBuilder - Python Edition
opsibian-gen - RaspberryPi Image Generator mit opsi 4.1
Winst32 Preprocessor
opsi PackageBuilder - Python Edition
opsibian-gen - RaspberryPi Image Generator mit opsi 4.1
Winst32 Preprocessor
- n.wenselowski
- Ex-uib-Team
- Beiträge: 3194
- Registriert: 04 Apr 2013, 12:15
Re: OPSI agent in system image
Hello,
you need to make sure that after rolling out the image to the machine the agent does get the correct information into his configuration file.
Otherwise you will not be able to distinguish between clients.
There is a possibility to disable/enable the agent realised as scripts in the uninst-folder on the client.
With kind regards
Niko
you need to make sure that after rolling out the image to the machine the agent does get the correct information into his configuration file.
Otherwise you will not be able to distinguish between clients.
There is a possibility to disable/enable the agent realised as scripts in the uninst-folder on the client.
With kind regards
Niko
Code: Alles auswählen
import OPSI