{"id":613,"date":"2012-05-01T08:46:29","date_gmt":"2012-05-01T07:46:29","guid":{"rendered":"https:\/\/medical.mediware.fr\/blog\/?p=613"},"modified":"2022-04-11T14:18:27","modified_gmt":"2022-04-11T12:18:27","slug":"debugger-les-installations-du-client-medical-objects","status":"publish","type":"post","link":"https:\/\/www.mediware.fr\/blog\/?p=613","title":{"rendered":"Debugger ou  adapter les installations du Client Medical Objects"},"content":{"rendered":"<table>\n<tbody>\n<tr>\n<td style=\"border-width: 0px; background-color: transparent;\"><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-349 alignnone\" alt=\"\" src=\"https:\/\/www.mediware.fr\/blog\/wp-content\/uploads\/logos\/moclient.png\" width=\"145\" height=\"145\" \/><\/td>\n<td style=\"border-width: 0px; background-color: transparent;\">\n<p>Il arrive parfois que l&#8217;installation du Client Medical Objects \u00e9choue.<br \/>Les raisons, souvent li\u00e9es aux droits de l&#8217;utilisateur courant, peuvent \u00eatre tr\u00e8s nombreuses.<\/p>\n<p>Si la mise \u00e0 jour a \u00e9t\u00e9 lanc\u00e9e via un &#8220;TODO&#8221; (dans le Gestionnaire MO), l&#8217;utilisateur valide souvent les fen\u00eatres d&#8217;avertissement sans pour autant noter le message d&#8217;erreur.<\/p>\n<p>Un dispositif permet d\u00e9sormais \u00e0 l&#8217;administrateur de savoir plus en d\u00e9tails ce qui s&#8217;est r\u00e9ellement pass\u00e9.<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><!--more--><\/p>\n<h2><strong>G\u00e9n\u00e9rer un fichier de traces de l&#8217;installation :<\/strong><\/h2>\n<p>Les commandes ci-dessous peuvent \u00eatre lanc\u00e9es depuis une fen\u00eatre de commandes DOS, ou param\u00e9tr\u00e9es depuis le Gestionnaire MO (TODO).<\/p>\n<div class=\"alert alert_info\"><div class=\"alert_icon\"><svg viewBox=\"0 0 28 28\"><defs><style>.path{fill:none;stroke:#000;stroke-miterlimit:10;stroke-width:1.5px;}<\/style><\/defs><g><circle class=\"path\" cx=\"14\" cy=\"14\" r=\"12\"\/><path class=\"path\" d=\"M11.2,9.12a3.4,3.4,0,0,1,3-1.69,2.84,2.84,0,0,1,3,2.76,3.16,3.16,0,0,1-.84,2.23c-.63.74-1.58,1.18-2.19,1.88a1,1,0,0,0-.26.64v2.32\"\/><circle class=\"path\" cx=\"14\" cy=\"20\" r=\"0.33\"\/><\/g><\/svg><\/div><div class=\"alert_wrapper\"><\/p>\n<p>Attention : il faut veiller \u00e0 ce que le fichier de log soit accessible durant l&#8217;installation, sinon celle-ci \u00e9chouera !<\/p>\n<p><\/div><a href=\"#\" class=\"close mfn-close-icon\"><span class=\"icon\">\u2715<\/span><\/a><\/div>\n\n<p>Par exemple, vous pouvez param\u00e9trer :<\/p>\n<blockquote class=\"code\">\n<p>pub\/MOClient_maj.net.exe \/VERYSILENT \/LOG=&#8221;D:\\TEMP\\MOCLIENT_INSTALL.LOG&#8221;<\/p>\n<\/blockquote>\n<p>Ou encore (si on est pas s\u00fbr que le r\u00e9pertoire TEMP existe) :<\/p>\n<blockquote class=\"code\">\n<p>pub\/MOClient_maj.net.exe \/VERYSILENT \/LOG=&#8221;D:\\MOCLIENT_INSTALL.LOG&#8221;<\/p>\n<\/blockquote>\n<p>Ou encore, si onsouhaite mettre le fichier de LOG dans le r\u00e9pertoire temporaire de l\u2019utilisateur (\\Documents and settings\\xxxxx\\Local Settings\\Temp) :<\/p>\n<blockquote class=\"code\">\n<p>pub\/MOClient_maj.net.exe \/VERYSILENT \/LOG<\/p>\n<\/blockquote>\n<p>Le plus simple est toujours de faire d\u2019abord des tests sur un poste, en lan\u00e7ant la commande manuellement dans une fen\u00eatre de commandes.<\/p>\n<h2>Installations en mode silencieux<\/h2>\n<p>Il est possible de g\u00e9n\u00e9rer des installations ou des mises \u00e0 jour dans deux modes silencieux, en ajoutant le param\u00e8tre ad\u00e9quat \u00e0 la ligne de commande.<\/p>\n<ul>\n<li>\/SILENT : Affiche les \u00e9crans, mais ne permet pas \u00e0 l&#8217;utilisateur de modifier les choix.<\/li>\n<li>\/VERYSILENT : n&#8217;affiche aucun \u00e9cran.<\/li>\n<\/ul>\n<div class=\"alert alert_warning\"><div class=\"alert_icon\"><svg viewBox=\"0 0 28 28\"><defs><style>.path{fill:none;stroke:#000;stroke-miterlimit:10;stroke-width:1.5px;}<\/style><\/defs><g><circle class=\"path\" cx=\"14\" cy=\"14\" r=\"12\"\/><line class=\"path\" x1=\"11.5\" y1=\"17.25\" x2=\"16.5\" y2=\"17.25\"\/><path class=\"path\" d=\"M16.46,17.8A3.94,3.94,0,0,1,17.64,15a4.61,4.61,0,0,0-.12-6.65A5.09,5.09,0,0,0,14,7h0A5.14,5.14,0,0,0,10.5,8.36,4.66,4.66,0,0,0,9,11.63a4.6,4.6,0,0,0,1.4,3.43,3.85,3.85,0,0,1,1.14,2.74h0V19c0,.87.59,2,1.67,2h1.58c1.08,0,1.67-1.16,1.67-2Z\"\/><\/g><\/svg><\/div><div class=\"alert_wrapper\">Attention : l&#8217;utilisation des modes silencieux lors d&#8217;une premi\u00e8re installation (i.e. pas une mise \u00e0 jour) inhibe l&#8217;installation du driver d&#8217;impression PDF.<\/div><a href=\"#\" class=\"close mfn-close-icon\"><span class=\"icon\">\u2715<\/span><\/a><\/div>\n\n<h2>Mise \u00e0 jour sans lancement automatique du Client MO<\/h2>\n<p>Il est possible de faire une mise \u00e0 jour du Client MO sans qu&#8217;il soit lanc\u00e9 automatiquement en fin d&#8217;installation : ajouter le param\u00e8tre &#8220;\/NOSTART&#8221; \u00e0 la ligne de commande.<\/p>\n<p>Exemple :<\/p>\n<blockquote class=\"code\">\n<p>MOClient_maj.net.exe \/VERYSILENT \/NOSTART<\/p>\n<\/blockquote>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Il arrive parfois que l&#8217;installation du Client Medical Objects \u00e9choue.Les raisons, souvent li\u00e9es aux droits de l&#8217;utilisateur courant, peuvent \u00eatre tr\u00e8s nombreuses. Si la mise \u00e0<span class=\"excerpt-hellip\"> [\u2026]<\/span><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4,5,3,29],"tags":[51,52],"class_list":["post-613","post","type-post","status-publish","format-standard","hentry","category-client-medical-objects","category-gestionnaire-medical-objects","category-medical-objects","category-tips","tag-installation","tag-todo"],"_links":{"self":[{"href":"https:\/\/www.mediware.fr\/blog\/index.php?rest_route=\/wp\/v2\/posts\/613","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.mediware.fr\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.mediware.fr\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.mediware.fr\/blog\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.mediware.fr\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=613"}],"version-history":[{"count":0,"href":"https:\/\/www.mediware.fr\/blog\/index.php?rest_route=\/wp\/v2\/posts\/613\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.mediware.fr\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=613"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.mediware.fr\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=613"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.mediware.fr\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=613"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}