Pesquisar no site de suporte

Evite golpes de suporte. Nunca pedimos que você ligue ou envie uma mensagem de texto para um número de telefone, ou compartilhe informações pessoais. Denuncie atividades suspeitas usando a opção “Denunciar abuso”.

Saiba mais

Esta discussão foi arquivada. Faça uma nova pergunta se precisa de ajuda.

Managing multiple client updates in 100PC+ company

  • 2 respostas
  • 1 tem este problema
  • 10 visualizações
  • Última resposta de ervin86

more options

Hi

Is it possible to use some managment tool in corporate network of Thunderbird Clients? We have clients in our company deployed with one version when reinstalling workstations. As Thunderbird can be set so that it does not download the update, it is still in a state where at least it asks and the user clicks on it. The question is that is it possible to do this in some software or update center??? The point ist we dont have the control over the clients updates. We wont to release these updates for the whole company when we agree not when the users do so by accident. What often happens to us, the versions are then different and we would like to have it under control.

Imagine we replace 100 workstations a year. The version is the same. Time will pass and in 3 months it will be a mess. Is there any way to keep it in order ??? Tips on how to keep one version in a large network and then do a massive update on 100+ workstations.

This mess of various versions then causes a problem for users with different views and unnecessary problems in managing clients for administrators in our company. When we know that version 80 is good and then that 85 is good again or does not cause any problem in our environment after the tests. Then we will deploy it for everyone.

Thank you for your help Lubomir

Hi Is it possible to use some managment tool in corporate network of Thunderbird Clients? We have clients in our company deployed with one version when reinstalling workstations. As Thunderbird can be set so that it does not download the update, it is still in a state where at least it asks and the user clicks on it. The question is that is it possible to do this in some software or update center??? The point ist we dont have the control over the clients updates. We wont to release these updates for the whole company when we agree not when the users do so by accident. What often happens to us, the versions are then different and we would like to have it under control. Imagine we replace 100 workstations a year. The version is the same. Time will pass and in 3 months it will be a mess. Is there any way to keep it in order ??? Tips on how to keep one version in a large network and then do a massive update on 100+ workstations. This mess of various versions then causes a problem for users with different views and unnecessary problems in managing clients for administrators in our company. When we know that version 80 is good and then that 85 is good again or does not cause any problem in our environment after the tests. Then we will deploy it for everyone. Thank you for your help Lubomir

Solução escolhida

If you wanted to prevent any update, so it does not ask meaning at least everyone remained on same version: Set a policy in HKEY_LOCAL_MACHINE. See image below:

Please note: This would need to be removed if you intended to allow update.

Ler esta resposta 👍 2

Todas as respostas (2)

more options

Solução escolhida

If you wanted to prevent any update, so it does not ask meaning at least everyone remained on same version: Set a policy in HKEY_LOCAL_MACHINE. See image below:

Please note: This would need to be removed if you intended to allow update.

more options

Hi Toad

Does this registry work for all versions of TB? Or is it possible that only after some version? I feel that this should work on W10 x64. Tested Worked. If anybody have some ideas pleas share :).

Thank you Lubomir