{"id":312,"date":"2017-11-27T12:19:06","date_gmt":"2017-11-27T14:19:06","guid":{"rendered":"http:\/\/docs.unitplatform.io\/?p=312"},"modified":"2019-04-10T13:52:12","modified_gmt":"2019-04-10T16:52:12","slug":"unit-platform-cloud-agent-advanced-options-windows","status":"publish","type":"post","link":"https:\/\/docs.unitplatform.io\/en\/unit-platform-cloud-agent-advanced-options-windows\/","title":{"rendered":"Unit Platform Cloud Agent advanced options (Windows)","raw":"Unit Platform Cloud Agent advanced options (Windows)"},"content":{"rendered":"

How the agent works<\/h2>\n

The Cloud Agent is installed as a service on Windows, and can be started\/stopped\/restarted using the service list provided by the operating system (services.msc<\/code>).<\/p>\n

\"\"

Unit Platform Cloud Agent service<\/p><\/div>\n

The installation directory is at: C:\\Program Files (x86)\\Netwall\\CloudAgent\\<\/code>. The file var\\CloudAgent.log<\/code> has all log messages generated by the agent. The config\\<\/code> directory stores all configuration files.<\/p>\n

Auto updates<\/h2>\n

Starting on version 6.0, o Unit Platform Cloud Agent comes with an additional service, responsible for updating the agent’s files. The updates are downloaded directly from Unit Platform.<\/p>\n

The update service can be managed using Windows’s service list (services.msc<\/code>):<\/p>\n

\"\"

Unit Platform Cloud Agent Update Service<\/p><\/div>\n

The updates are enabled by default. If you don’t want the agent to update automatically, simply stop the service and disable it, so it will not start at boot. Click with the right mouse button on the update service, select properties, and on startup type select disabled:<\/p>\n

\"\"

Disabling the updates<\/p><\/div>\n

Customizing the configuration<\/h2>\n

The main configuration file is specified at config\\agent.conf<\/code>. In this file you can change the following items:<\/p>\n

    \n
  • Enable\/disable sending monitoring information.<\/li>\n
  • Enable\/disable sending inventory information.<\/li>\n
  • Change the interval on which the agent will send monitoring or inventory information to Unit Platform.<\/li>\n
  • Change the company key.<\/li>\n
  • Change the address the agent will send information to. Default: app.unitplatform.io. Change this only if you are using Unit Platform on-premises.<\/em><\/li>\n
  • Configure the data collection timeout value.<\/li>\n
  • Enable\/disable showing more detailed debug messages in the log file.<\/li>\n<\/ul>\n

    IMPORTANT:<\/strong> after making any changes in the agent.conf<\/code> file, restart the agent service<\/strong> for the changes to take effect.<\/p><\/blockquote>\n

    Monitoring process and services<\/h3>\n

    To monitor processes and services you should edit the config\\process.conf<\/code> and config\\services.conf<\/code> files.<\/p>\n

    For processes, inform the process names in the file process.conf<\/code>. The names must be listed one per line in the same way the Task Manager shows in the “Details” tab. See the example below:<\/p>\n

    \"\"

    Monitoring Windows processes<\/p><\/div>\n

    To monitor Windows services, edit the services.conf<\/code> file and inform the process names that should be monitored one per line. To discover the service name, open the service’s properties and look for the field “Service name”:<\/p>\n

    \"\"

    Service properties<\/p><\/div>\n

    Configuration example:<\/p>\n

    \"\"

    Service monitoring configuration<\/p><\/div>\n

    IMPORTANT:<\/strong> after making any changes in the process.conf<\/code> or services.conf<\/code> files, restart the agent service<\/strong> for the changes to take effect.<\/p><\/blockquote>\n

    Troubleshooting<\/h2>\n

    These are the most common problems that may prevent the agent from sending information to the Unit Platform:<\/p>\n

    The device does not have internet access<\/h3>\n

    The device being monitored must have access to the Unit Platform using HTTPS. By default the address the agent will send information to is https:\/\/app.unitplatform.io\/. Please check if there are any firewall rules denying access to the internet or the Unit Platform.<\/p>\n

    The agent’s service is not running<\/h3>\n

    The agent’s service is configured to stop in case one of the following situations happen:<\/p>\n

      \n
    • The company key was not informed or is invalid.<\/li>\n
    • The monitoring\/inventory interval is invalid.<\/li>\n<\/ul>\n

      If one of these errors occur, there will be messages detailing the errors in the log file (CloudAgent.log<\/code>). To correct these errors, edit the agent.conf<\/code> file, and follow the instructions in the comments and restart the agent. As a last resort, uninstall the agent and reinstall it.<\/p>\n

      The device limit for your plan has been exceeded<\/h3>\n

      In this case, revise your Unit Platform subscription and restart the agent.<\/p>\n","protected":false,"raw":"

      How the agent works<\/h2>\r\nThe Cloud Agent is installed as a service on Windows, and can be started\/stopped\/restarted using the service list provided by the operating system (services.msc<\/code>).\r\n\r\n[caption id=\"attachment_323\" align=\"alignnone\" width=\"646\"]\"\" Unit Platform Cloud Agent service[\/caption]\r\n\r\nThe installation directory is at: C:\\Program Files (x86)\\Netwall\\CloudAgent\\<\/code>. The file var\\CloudAgent.log<\/code> has all log messages generated by the agent. The config\\<\/code> directory stores all configuration files.\r\n

      Auto updates<\/h2>\r\nStarting on version 6.0, o Unit Platform Cloud Agent comes with an additional service, responsible for updating the agent's files. The updates are downloaded directly from Unit Platform.\r\n\r\nThe update service can be managed using Windows's service list (services.msc<\/code>):\r\n\r\n[caption id=\"attachment_1237\" align=\"alignnone\" width=\"668\"]\"\" Unit Platform Cloud Agent Update Service[\/caption]\r\n\r\nThe updates are enabled by default. If you don't want the agent to update automatically, simply stop the service and disable it, so it will not start at boot. Click with the right mouse button on the update service, select properties, and on startup type select disabled:\r\n\r\n[caption id=\"attachment_1238\" align=\"alignnone\" width=\"399\"]\"\" Disabling the updates[\/caption]\r\n

      Customizing the configuration<\/h2>\r\nThe main configuration file is specified at config\\agent.conf<\/code>. In this file you can change the following items:\r\n
        \r\n \t
      • Enable\/disable sending monitoring information.<\/li>\r\n \t
      • Enable\/disable sending inventory information.<\/li>\r\n \t
      • Change the interval on which the agent will send monitoring or inventory information to Unit Platform.<\/li>\r\n \t
      • Change the company key.<\/li>\r\n \t
      • Change the address the agent will send information to. Default: app.unitplatform.io. Change this only if you are using Unit Platform on-premises.<\/em><\/li>\r\n \t
      • Configure the data collection timeout value.<\/li>\r\n \t
      • Enable\/disable showing more detailed debug messages in the log file.<\/li>\r\n<\/ul>\r\n
        IMPORTANT:<\/strong> after making any changes in the agent.conf<\/code> file, restart the agent service<\/strong> for the changes to take effect.<\/blockquote>\r\n

        Monitoring process and services<\/h3>\r\nTo monitor processes and services you should edit the config\\process.conf<\/code> and config\\services.conf<\/code> files.\r\n\r\nFor processes, inform the process names in the file process.conf<\/code>. The names must be listed one per line in the same way the Task Manager shows in the \"Details\" tab. See the example below:\r\n\r\n[caption id=\"attachment_294\" align=\"alignnone\" width=\"675\"]\"\" Monitoring Windows processes[\/caption]\r\n\r\nTo monitor Windows services, edit the services.conf<\/code> file and inform the process names that should be monitored one per line. To discover the service name, open the service's properties and look for the field \"Service name\":\r\n\r\n[caption id=\"attachment_295\" align=\"alignnone\" width=\"417\"]\"\" Service properties[\/caption]\r\n\r\nConfiguration example:\r\n\r\n[caption id=\"attachment_298\" align=\"alignnone\" width=\"677\"]\"\" Service monitoring configuration[\/caption]\r\n
        IMPORTANT:<\/strong> after making any changes in the process.conf<\/code> or services.conf<\/code> files, restart the agent service<\/strong> for the changes to take effect.<\/blockquote>\r\n

        Troubleshooting<\/h2>\r\nThese are the most common problems that may prevent the agent from sending information to the Unit Platform:\r\n

        The device does not have internet access<\/h3>\r\nThe device being monitored must have access to the Unit Platform using HTTPS. By default the address the agent will send information to is https:\/\/app.unitplatform.io\/. Please check if there are any firewall rules denying access to the internet or the Unit Platform.\r\n

        The agent's service is not running<\/h3>\r\nThe agent's service is configured to stop in case one of the following situations happen:\r\n
          \r\n \t
        • The company key was not informed or is invalid.<\/li>\r\n \t
        • The monitoring\/inventory interval is invalid.<\/li>\r\n<\/ul>\r\nIf one of these errors occur, there will be messages detailing the errors in the log file (CloudAgent.log<\/code>). To correct these errors, edit the agent.conf<\/code> file, and follow the instructions in the comments and restart the agent. As a last resort, uninstall the agent and reinstall it.\r\n

          The device limit for your plan has been exceeded<\/h3>\r\nIn this case, revise your Unit Platform subscription and restart the agent."},"excerpt":{"rendered":"

          Advanced configurations and troubleshooting.<\/p>\n","protected":false,"raw":"Advanced configurations and troubleshooting."},"author":3,"featured_media":987,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_pt_post_content":"

          Funcionamento do agente<\/h2>\r\nO Cloud Agent \u00e9 instalado como um servi\u00e7o no Windows, e pode ser iniciado\/parado\/reiniciado atrav\u00e9s da tabela de servi\u00e7os (services.msc<\/code>).\r\n\r\n[caption id=\"attachment_323\" align=\"alignnone\" width=\"646\"]\"\" Servi\u00e7o do Unit Platform Cloud Agent[\/caption]\r\n\r\nO local de instala\u00e7\u00e3o fica em: C:\\Program Files (x86)\\Netwall\\CloudAgent\\<\/code>. No arquivo\u00a0var\\CloudAgent.log<\/code> estar\u00e3o os logs de erro do agente. Em\u00a0config\\<\/code> ficam os arquivos de configura\u00e7\u00e3o.\r\n

          Atualiza\u00e7\u00e3o autom\u00e1tica<\/h2>\r\nA partir da vers\u00e3o 6.0, o Unit Platform Cloud Agent possui um servi\u00e7o adicional que \u00e9 respons\u00e1vel por atualizar os arquivos do agente. Os updates s\u00e3o baixados direto da Unit Platform.\r\n\r\nO servi\u00e7o de atualiza\u00e7\u00e3o pode ser gerenciado usando a tabela de servi\u00e7os do Windows (services.msc<\/code>):\r\n\r\n[caption id=\"attachment_1237\" align=\"alignnone\" width=\"668\"]\"\" Unit Platform Cloud Agent Update Service[\/caption]\r\n\r\nAs atualiza\u00e7\u00f5es s\u00e3o habilitadas por padr\u00e3o. Caso voc\u00ea deseje que o agente n\u00e3o atualize automaticamente, simplesmente pare o servi\u00e7o de atualiza\u00e7\u00e3o e desabilite o servi\u00e7o para que ele n\u00e3o inicie durante o boot (clique com o bot\u00e3o direito no nome do servi\u00e7o, escolha propriedades e em altere o tipo de inicializa\u00e7\u00e3o para desativado):\r\n\r\n[caption id=\"attachment_1238\" align=\"alignnone\" width=\"399\"]\"\" Desabilitando as atualiza\u00e7\u00f5es[\/caption]\r\n

          Personaliza\u00e7\u00e3o da configura\u00e7\u00e3o<\/h2>\r\nA configura\u00e7\u00e3o geral do agente \u00e9 especificada no arquivo config\\agent.conf<\/code>. Nesse arquivo \u00e9 permitido alterar os seguintes itens:\r\n
            \r\n \t
          • Habilitar\/desabilitar o envio de informa\u00e7\u00f5es de monitoramento.<\/li>\r\n \t
          • Habilitar\/desabilitar o envio de informa\u00e7\u00f5es de invent\u00e1rio.<\/li>\r\n \t
          • Alterar o intervalo de envio de informa\u00e7\u00f5es de monitoramento e invent\u00e1rio para a Unit Platform.<\/li>\r\n \t
          • Alterar a chave da empresa.<\/li>\r\n \t
          • Alterar o endere\u00e7o para o qual as informa\u00e7\u00f5es de monitoramento devem ser enviadas. Por padr\u00e3o: app.unitplatform.io. Apenas altere este campo se voc\u00ea estiver usando a Unit Platform on-premises.<\/em><\/li>\r\n \t
          • Configurar o tempo de timeout para a execu\u00e7\u00e3o dos comandos de coleta de dados.<\/li>\r\n \t
          • Habilitar\/desabilitar a exibi\u00e7\u00e3o de mensagens de debug no arquivo de log do agente.<\/li>\r\n<\/ul>\r\n
            IMPORTANTE:<\/strong> ap\u00f3s fazer altera\u00e7\u00f5es nos arquivo agent.conf<\/code>, reinicie o servi\u00e7o do agente<\/strong> para que as altera\u00e7\u00f5es entrem em efeito.<\/blockquote>\r\n

            Monitoramento de processos e servi\u00e7os<\/h3>\r\nO monitoramento de processos e servi\u00e7os deve ser configurado manualmente nos arquivos config\\process.conf<\/code> e config\\services.conf<\/code>.\r\n\r\nPara monitoramento de processos, informe no arquivo\u00a0process.conf<\/code> os nomes dos processos que devem ser monitorados. Os nomes devem ser preenchidos um por linha e da mesma forma que aparecem na aba \"Detalhes\" do Gerenciador de Tarefas do Windows. Veja o exemplo abaixo:\r\n\r\n[caption id=\"attachment_294\" align=\"alignnone\" width=\"675\"]\"\" Configura\u00e7\u00e3o do monitoramento de processos[\/caption]\r\n\r\nPara monitorar servi\u00e7os do Windows, informe no arquivo\u00a0services.conf<\/code> os nomes dos servi\u00e7os que devem ser monitorados um por linha. Atente para o fato que o nome do servi\u00e7o que deve ser informado no arquivo \u00e9 o que aparece em \"Service name\" nas propriedades do servi\u00e7o:\r\n\r\n[caption id=\"attachment_295\" align=\"alignnone\" width=\"417\"]\"\" Propriedades de um servi\u00e7o do Windows[\/caption]\r\n\r\nExemplo de configura\u00e7\u00e3o de monitoramento de servi\u00e7os:\r\n\r\n[caption id=\"attachment_298\" align=\"alignnone\" width=\"677\"]\"\" Configura\u00e7\u00e3o do monitoramento de servi\u00e7os[\/caption]\r\n
            IMPORTANTE:<\/strong> ap\u00f3s fazer as altera\u00e7\u00f5es nos arquivos process.conf<\/code> e services.conf<\/code>, reinicie o servi\u00e7o do agente<\/strong> para que as altera\u00e7\u00f5es entrem em efeito.<\/blockquote>\r\n

            Resolu\u00e7\u00e3o de problemas<\/h2>\r\nAbaixo est\u00e3o listados os problemas mais comuns que podem impedir o envio de informa\u00e7\u00f5es do dispositivo para a Unit Platform:\r\n

            O dispositivo n\u00e3o possui acesso \u00e0 internet<\/h3>\r\n\u00c9 necess\u00e1rio que o dispositivo tenha permiss\u00f5es para trafegar dados via HTTPS para o endere\u00e7o https:\/\/app.unitplatform.io\/.\u00a0 Revise as regras de firewall que possivelmente estejam impedindo o dispositivo de acessar a internet.\r\n

            O servi\u00e7o do agente n\u00e3o est\u00e1 rodando<\/h3>\r\nO servi\u00e7o do agente est\u00e1 configurado para parar automaticamente caso os seguintes erros de configura\u00e7\u00e3o ocorram:\r\n
              \r\n \t
            • A chave da empresa n\u00e3o foi informada ou \u00e9 inv\u00e1lida.<\/li>\r\n \t
            • Foi informado um intervalo de monitoramento\/invent\u00e1rio inv\u00e1lido.<\/li>\r\n<\/ul>\r\nSe algum desses erros estiver ocorrendo, haver\u00e3o mensagens de log em CloudAgent.log<\/code>. Para corrigir esses erros, edite o arquivo agent.conf<\/code>, siga as instru\u00e7\u00f5es nos coment\u00e1rios do arquivo e reinicie o agente. Em \u00faltimo caso, desinstale o agente e instale novamente.\r\n

              O limite de dispositivos contratados no plano foi excedido<\/h3>\r\nNeste caso, revise a sua configura\u00e7\u00e3o de assinatura da Unit Platform e reinicie o agente.","_pt_post_name":"configuracao-avancada-do-unit-platform-cloud-agent-windows","_pt_post_excerpt":"Personaliza\u00e7\u00e3o da instala\u00e7\u00e3o e resolu\u00e7\u00e3o de problemas.","_pt_post_title":"Configura\u00e7\u00e3o avan\u00e7ada do Unit Platform Cloud Agent (Windows)","_en_post_content":"

              How the agent works<\/h2>\r\nThe Cloud Agent is installed as a service on Windows, and can be started\/stopped\/restarted using the service list provided by the operating system (services.msc<\/code>).\r\n\r\n[caption id=\"attachment_323\" align=\"alignnone\" width=\"646\"]\"\" Unit Platform Cloud Agent service[\/caption]\r\n\r\nThe installation directory is at: C:\\Program Files (x86)\\Netwall\\CloudAgent\\<\/code>. The file var\\CloudAgent.log<\/code> has all log messages generated by the agent. The config\\<\/code> directory stores all configuration files.\r\n

              Auto updates<\/h2>\r\nStarting on version 6.0, o Unit Platform Cloud Agent comes with an additional service, responsible for updating the agent's files. The updates are downloaded directly from Unit Platform.\r\n\r\nThe update service can be managed using Windows's service list (services.msc<\/code>):\r\n\r\n[caption id=\"attachment_1237\" align=\"alignnone\" width=\"668\"]\"\" Unit Platform Cloud Agent Update Service[\/caption]\r\n\r\nThe updates are enabled by default. If you don't want the agent to update automatically, simply stop the service and disable it, so it will not start at boot. Click with the right mouse button on the update service, select properties, and on startup type select disabled:\r\n\r\n[caption id=\"attachment_1238\" align=\"alignnone\" width=\"399\"]\"\" Disabling the updates[\/caption]\r\n

              Customizing the configuration<\/h2>\r\nThe main configuration file is specified at config\\agent.conf<\/code>. In this file you can change the following items:\r\n
                \r\n \t
              • Enable\/disable sending monitoring information.<\/li>\r\n \t
              • Enable\/disable sending inventory information.<\/li>\r\n \t
              • Change the interval on which the agent will send monitoring or inventory information to Unit Platform.<\/li>\r\n \t
              • Change the company key.<\/li>\r\n \t
              • Change the address the agent will send information to. Default: app.unitplatform.io. Change this only if you are using Unit Platform on-premises.<\/em><\/li>\r\n \t
              • Configure the data collection timeout value.<\/li>\r\n \t
              • Enable\/disable showing more detailed debug messages in the log file.<\/li>\r\n<\/ul>\r\n
                IMPORTANT:<\/strong> after making any changes in the agent.conf<\/code> file, restart the agent service<\/strong> for the changes to take effect.<\/blockquote>\r\n

                Monitoring process and services<\/h3>\r\nTo monitor processes and services you should edit the config\\process.conf<\/code> and config\\services.conf<\/code> files.\r\n\r\nFor processes, inform the process names in the file process.conf<\/code>. The names must be listed one per line in the same way the Task Manager shows in the \"Details\" tab. See the example below:\r\n\r\n[caption id=\"attachment_294\" align=\"alignnone\" width=\"675\"]\"\" Monitoring Windows processes[\/caption]\r\n\r\nTo monitor Windows services, edit the services.conf<\/code> file and inform the process names that should be monitored one per line. To discover the service name, open the service's properties and look for the field \"Service name\":\r\n\r\n[caption id=\"attachment_295\" align=\"alignnone\" width=\"417\"]\"\" Service properties[\/caption]\r\n\r\nConfiguration example:\r\n\r\n[caption id=\"attachment_298\" align=\"alignnone\" width=\"677\"]\"\" Service monitoring configuration[\/caption]\r\n
                IMPORTANT:<\/strong> after making any changes in the process.conf<\/code> or services.conf<\/code> files, restart the agent service<\/strong> for the changes to take effect.<\/blockquote>\r\n

                Troubleshooting<\/h2>\r\nThese are the most common problems that may prevent the agent from sending information to the Unit Platform:\r\n

                The device does not have internet access<\/h3>\r\nThe device being monitored must have access to the Unit Platform using HTTPS. By default the address the agent will send information to is https:\/\/app.unitplatform.io\/. Please check if there are any firewall rules denying access to the internet or the Unit Platform.\r\n

                The agent's service is not running<\/h3>\r\nThe agent's service is configured to stop in case one of the following situations happen:\r\n
                  \r\n \t
                • The company key was not informed or is invalid.<\/li>\r\n \t
                • The monitoring\/inventory interval is invalid.<\/li>\r\n<\/ul>\r\nIf one of these errors occur, there will be messages detailing the errors in the log file (CloudAgent.log<\/code>). To correct these errors, edit the agent.conf<\/code> file, and follow the instructions in the comments and restart the agent. As a last resort, uninstall the agent and reinstall it.\r\n

                  The device limit for your plan has been exceeded<\/h3>\r\nIn this case, revise your Unit Platform subscription and restart the agent.","_en_post_name":"unit-platform-cloud-agent-advanced-options-windows","_en_post_excerpt":"Advanced configurations and troubleshooting.","_en_post_title":"Unit Platform Cloud Agent advanced options (Windows)","edit_language":"en","footnotes":""},"categories":[11,10,4,9],"tags":[],"class_list":["post-312","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-asset-management","category-multisite-monitoring","category-tutorials","category-unit-platform-cloud"],"_links":{"self":[{"href":"https:\/\/docs.unitplatform.io\/en\/wp-json\/wp\/v2\/posts\/312","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/docs.unitplatform.io\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/docs.unitplatform.io\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/docs.unitplatform.io\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/docs.unitplatform.io\/en\/wp-json\/wp\/v2\/comments?post=312"}],"version-history":[{"count":8,"href":"https:\/\/docs.unitplatform.io\/en\/wp-json\/wp\/v2\/posts\/312\/revisions"}],"predecessor-version":[{"id":341,"href":"https:\/\/docs.unitplatform.io\/en\/wp-json\/wp\/v2\/posts\/312\/revisions\/341"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/docs.unitplatform.io\/en\/wp-json\/wp\/v2\/media\/987"}],"wp:attachment":[{"href":"https:\/\/docs.unitplatform.io\/en\/wp-json\/wp\/v2\/media?parent=312"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/docs.unitplatform.io\/en\/wp-json\/wp\/v2\/categories?post=312"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/docs.unitplatform.io\/en\/wp-json\/wp\/v2\/tags?post=312"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}