Welcome to OCS Inventory NG community support, where you can ask questions and receive answers from other members of the community.

Please ask questions only in English or French.

Release 2.6 available

The official documentation can be found on http://wiki.ocsinventory-ng.org. Read it before asking your question.

Choisir l'heure des déploiements [closed]

Bonjour,

Version Agent : 2.0.5.0
Version server : 2.1.2

Je n’ai trouvé pas sur le forum un cas ressemblant au problème que j’ai rencontré.

Dans le processus de télédeploiement par action « Lancer » tout a fonctionné :
1.    le build
2.    l’activation
3.    l’assignement au PC
4.    le téléchargement & l’installation sur le client

Le problème que j’ai rencontré est sur la date d’installation choisie lors de l’assignement qui diffère du jour d'installation réelle:

Mardi 12 avril j’ai choisi une installation pour le 14 avril et elle s’est produite le 13 avril juste après l’inventaire quotidien comme vous pouvez le voir dans le logs (ce n'est pas le premier exemple que j'observe dans ce cas) :

log serveur :
            
12/04/2016 17:22    ocsweb    PAGE    visu_search
            
12/04/2016 17:22    ocsweb    SEARCH_RESULT    1 Result(s)
            
12/04/2016 17:22    ocsweb    PAGE    visu_search           
          
12/04/2016 17:23    ocsweb    Deployment    delete from devices where name='DOWNLOAD_SCHEDULE' and ivalue=20 and hardware_id in  (  '17' )
            
12/04/2016 17:23    ocsweb    Deployment    insert into devices (HARDWARE_ID, NAME, IVALUE,TVALUE) select ID,'DOWNLOAD_SCHEDULE','20','2016/04/14 07:00' from hardware where id in  (  '17' )
            
12/04/2016 17:23    ocsweb    Deployment    delete from devices where name='DOWNLOAD' and ivalue=20 and hardware_id in  (  '17' )
            
12/04/2016 17:23    ocsweb    Deployment    insert into devices (HARDWARE_ID, NAME, IVALUE,TVALUE) select ID,'DOWNLOAD','20',null from hardware where id in  (  '17' )
            
12/04/2016 17:23    ocsweb    PAGE    pack_search
            
12/04/2016 17:28    ocsweb    Deployment    delete from devices where name='DOWNLOAD_SCHEDULE' and ivalue=21 and hardware_id in  (  '17' )
            
12/04/2016 17:28    ocsweb    Deployment    insert into devices (HARDWARE_ID, NAME, IVALUE,TVALUE) select ID,'DOWNLOAD_SCHEDULE','21','2016/04/14 08:00' from hardware where id in  (  '17' )
            
12/04/2016 17:28    ocsweb    Deployment    delete from devices where name='DOWNLOAD_POSTCMD' and ivalue=21 and hardware_id in  (  '17' )
            
12/04/2016 17:28    ocsweb    Deployment    insert into devices (HARDWARE_ID, NAME, IVALUE,TVALUE) select ID,'DOWNLOAD_POSTCMD','21','REBOOT' from hardware where id in  (  '17' )
            
12/04/2016 17:28    ocsweb    Deployment    delete from devices where name='DOWNLOAD' and ivalue=21 and hardware_id in  (  '17' )
            
12/04/2016 17:28    ocsweb    Deployment    insert into devices (HARDWARE_ID, NAME, IVALUE,TVALUE) select ID,'DOWNLOAD','21',null from hardware where id in  (  '17' )
   

   
OCSInventory.log (Paquet de 7h non téléchargé et 1460464067 est paquet de 8h):

==============================================================================
Starting OCS Inventory NG Agent on Wednesday, April 13, 2016 05:16:00.
AGENT => Running OCS Inventory NG Agent Version 2.0.5.0
AGENT => Using OCS Inventory NG FrameWork Version 2.0.5.0
AGENT => Loading plug-in(s)
    DLL PLUGIN => Searching for Plug-in DLL(s) in folder <C:\Program Files (x86)\OCS Inventory Agent\plugins>
    DLL PLUGIN => 0 DLL Plug-in(s) succesfully loaded on 0 DLL(s) found
AGENT => Using network connection with Communication Server
    COM PROVIDER => Loading Communication Provider <C:\Program Files (x86)\OCS Inventory Agent\ComHTTP.dll>
AGENT => Using Communication Provider <OCS Inventory NG cURL Communication Provider> Version <2.0.5.0>
AGENT => Sending Prolog
    DID_CHECK => Read DeviceID <OCS_AGENT_NAME-2016-02-02-15-15-38> and MACs <MACADRESS OCS_AGENT_NAME> in file <ocsinventory.dat>
    COM SERVER => Initializing cURL library for sendRequest
    COM SERVER => Using cURL without server authentication
    COM SERVER => Disabling cURL proxy support
    COM SERVER => Enabling cURL SSL server validation support using CA Bundle <certificate file OCS_AGENT_NAME>
    COM SERVER => Sending HTTP Post request to URL <https://OCS_SERVER_NAME/ocsinventory>
    COM SERVER => HTTP Post response received <HTTP Status Code #200>
    COM SERVER => Cleaning cURL library
AGENT => Prolog successfully sent
SUPPORT => No support detected, Registration key : N/A
    AGENT => Prolog Frequency set to 24 hour(s)
AGENT => Inventory required

AGENT => Inventory successfully sent
    INVENTORY => Writing new inventory state
AGENT =>  Communication Server ask for Package Download
    DOWNLOAD => Package history file cleaning not required
    DOWNLOAD => Metadata file <info> for package <1460464067> is located at <https://OCS_SERVER_NAME/download/1460464067/info>
    COM SERVER => Initializing cURL library for getFile
    COM SERVER => Using cURL without server authentication
    COM SERVER => Disabling cURL proxy support
    COM SERVER => Enabling cURL SSL server validation support using CA Bundle <certificate file OCS_AGENT_NAME>
    COM SERVER => Sending fileGet request to URL <https://OCS_SERVER_NAME/download/1460464067/info>
    COM SERVER => fileGet response received <HTTP Status Code #200>
    COM SERVER => Cleaning cURL library
    DOWNLOAD => Unloading communication provider
    DOWNLOAD => Retrieve info file...OK (pack 1460464067)
DOWNLOAD => Package <1460464067> added to download queue
DOWNLOAD => Download and setup tool successfully started
AGENT => Unloading communication provider
AGENT => Unloading plug-in(s)
AGENT => Execution duration: 00:00:38.

Download.log:
==============================================================================
Starting OCS Inventory NG Package Download and Setup Tool on Wednesday, April 13, 2016 05:16:39.
DOWNLOAD => Running OCS Inventory NG Download Version 2.0.5.0
DOWNLOAD => Using OCS Inventory NG FrameWork Version 2.0.5.0
DOWNLOAD => Using network connection with Communication Server
    COM PROVIDER => Loading Communication Provider <C:\Program Files (x86)\OCS Inventory Agent\ComHTTP.dll>
DOWNLOAD => Using Communication Provider <OCS Inventory NG cURL Communication Provider> Version <2.0.5.0>
DOWNLOAD => Starting new period of 10 cycles
    DOWNLOAD => Flushing package queue
DOWNLOAD => Parsing directory <C:\ProgramData\OCS Inventory NG\Agent\download> for packages
    DOWNLOAD => Verifying package <C:\ProgramData\OCS Inventory NG\Agent\download\1460464067>
DOWNLOAD => Package <1460464067> verified and added to process queue

        DOWNLOAD SUCCESSFULL
        
DOWNLOAD => Building package <1460464067>
    PACKAGE => Verifying fragment files of package <1460464067>
    PACKAGE => Checking free disk space for package <1460464067>
    PACKAGE => Building ZIP for package <1460464067>
    PACKAGE => Verifying ZIP signature for package <1460464067>
    DOWNLOAD => Package <1460464067> built successfully
DOWNLOAD => Executing action <LAUNCH> for package <1460464067>
    PACKAGE => Launching command <setup.exe> for package <1460464067>
    PACKAGE => Package <1460464067> successfully launched. Command exit code is <1>
ERROR *** DOWNLOAD => Will not register package <1460464067> in history: result <EXIT_CODE_1> not a success
DOWNLOAD => Sending result code <EXIT_CODE_1> for package <1460464067>
DOWNLOAD => Result code request successfully sent
    

DOWNLOAD => Starting new period of 10 cycles
    DOWNLOAD => Flushing package queue
DOWNLOAD => Parsing directory <C:\ProgramData\OCS Inventory NG\Agent\download> for packages
DOWNLOAD => No package found, exiting

DOWNLOAD => Execution duration: 00:37:00.

J’aimerai fournir plus de logs mais l’outil me limite à 8000 caractères…
Y-a-t-il un paramètre à modifier sur le serveur comme le paramètre Config -> Deployment -> deploy ou download à off (actuellement à « on » dans ma config) ?

Merci d’avance de votre aide.

Cordialement.

Julien
closed with the note: Résolu
in OCS Inventory NG server for Windows by (160 points)
closed by

2 Answers

0 votes
Il faudrait que tu essais avec un agent en version 2.1 pour voir si ça règle le problème. En effet je connais mal cette fonctionnalité mais il est possible que l'agent 2.0 ne soit simplement pas compatible avec.
by (21.7k points)
0 votes
Merci pour votre réponse, c'est en effet à partir de la v2.1.0.1 que la fonctionnalité de choix de l'heure et du jour de déploiement est disponible dans l'agent:

Agent Changelog:

2.1.0.1
  * Add agent ability to force package reinstall, and support for package setup schedule
by (160 points)
 
Powered by Question2Answer
...