Hello everyone. I’ve deployed TightVNC through GPO (multiple networks, msi + mst) and everything works well.
By default, TightVNC allow us to log in into a user desktop without user’s permission.
What I would like to deploy now is one of two possibilities:
1.
TightVNC only runs when user wants to.
a.
TightVNC must be already preconfigured. Don’t want user to set password and other options 2.
TightVNC is always running, but user is always queried.
a.
TightVNC must be deployed with this option. I don’t want to configure manually on every machine. Thank you for your time. Best regards, Manuel Monteiro. Manuel Monteiro Departamento Tecnologias de Informação e Telecomunicações Aviso A informação contida nesta mensagem é confidencial
e dirigida apenas aos destinatários. Se recebeu esta mensagem por erro ou se houver algum problema, por favor contacte imediatamente o remetente. O uso não autorizado, divulgação, cópia ou alteração desta mensagem é estritamente proibido. A INDAQUA não será responsável por qualquer consequência direta, especial ou indireta, originada pela alteração
do conteúdo desta informação, por terceiros, ou como resultado de qualquer vírus transmitido. Se receber esta mensagem por engano, por favor, apague-a. A INDAQUA permite o uso razoável a título pessoal deste endereço de email. As opiniões, comentários ou imagens
transmitidos através do mesmo não representam, necessariamente, a INDAQUA. A INDAQUA não pode garantir que as comunicações veiculadas pelo presente email são seguras ou não contêm erros,
uma vez que as mesmas podem ser intercetadas, alteradas, perdidas, destruídas, chegar incompletas ou tardiamente, ou conter vírus. Disclaimer This message contains confidential information and is intended for the addressee only. If you have
received this message by mistake or if there is any problem, please notify the sender immediately. Any unauthorised use, distribution, copying or modification of this message is strictly forbidden. INDAQUA will not be responsible for any direct, special or indirect consequence, originated by the
modification of the content of this information, by third parties, or as resulted of any transmitted viruses. If you have received this message by mistake, please, delete it. INDAQUA
allows a reasonable use of this e-mail address for personal purposes. The opinions, commentaries or images transmitted through it do not, necessarily, represent INDAQUA. INDAQUA cannot guarantee that the communications in the present e-mail are secure or error-free since
they can be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot ___________________________________________________________ TightVNC mailing list, [hidden email] To change your subscription or to UNSUBSCRIBE, please visit https://lists.sourceforge.net/lists/listinfo/vnc-tight-list |
Manuel,
For #2, look at the answer to this thread (Access Control tab and "Query local user" option in access rule) and config that in your current deployment method (not sure of specifics, but this should map to registry settings that can be set at deploy time - have you found otherwise?): http://tightvnc.10971.n7.nabble.com/User-acceptance-td2128.html
Thanks, -Matt From: Manuel Monteiro <[hidden email]>
Sent: Monday, January 23, 2017 10:08 AM To: [hidden email] Subject: TightVNC User Query Hello everyone.
I’ve deployed TightVNC through GPO (multiple networks, msi + mst) and everything works well. By default, TightVNC allow us to log in into a user desktop without user’s permission. What I would like to deploy now is one of two possibilities: 1. TightVNC only runs when user wants to. a. TightVNC must be already preconfigured. Don’t want user to set password and other options 2. TightVNC is always running, but user is always queried. a. TightVNC must be deployed with this option. I don’t want to configure manually on every machine.
Thank you for your time. Best regards,
Manuel Monteiro.
Manuel Monteiro Departamento Tecnologias de Informação e Telecomunicações
Aviso A informação contida nesta mensagem é confidencial e dirigida apenas aos destinatários. Se recebeu esta mensagem por erro ou se houver algum problema, por favor contacte imediatamente o remetente. O uso não autorizado, divulgação, cópia ou alteração desta mensagem é estritamente proibido. A INDAQUA não será responsável por qualquer consequência direta, especial ou indireta, originada pela alteração do conteúdo desta informação, por terceiros, ou como resultado de qualquer vírus transmitido. Se receber esta mensagem por engano, por favor, apague-a. A INDAQUA permite o uso razoável a título pessoal deste endereço de email. As opiniões, comentários ou imagens transmitidos através do mesmo não representam, necessariamente, a INDAQUA. A INDAQUA não pode garantir que as comunicações veiculadas pelo presente email são seguras ou não contêm erros, uma vez que as mesmas podem ser intercetadas, alteradas, perdidas, destruídas, chegar incompletas ou tardiamente, ou conter vírus.
Disclaimer This message contains confidential information and is intended for the addressee only. If you have received this message by mistake or if there is any problem, please notify the sender immediately. Any unauthorised use, distribution, copying or modification of this message is strictly forbidden. INDAQUA will not be responsible for any direct, special or indirect consequence, originated by the modification of the content of this information, by third parties, or as resulted of any transmitted viruses. If you have received this message by mistake, please, delete it. INDAQUA allows a reasonable use of this e-mail address for personal purposes. The opinions, commentaries or images transmitted through it do not, necessarily, represent INDAQUA. INDAQUA cannot guarantee that the communications in the present e-mail are secure or error-free since they can be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses.
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot ___________________________________________________________ TightVNC mailing list, [hidden email] To change your subscription or to UNSUBSCRIBE, please visit https://lists.sourceforge.net/lists/listinfo/vnc-tight-list |
Thank you, Matthew.
I was aware of
Access Control Rules, and that option is just perfect. Right now I’m unable to find a way to deploy it to all machines.
Best regards, Manuel Monteiro Departamento Tecnologias de Informação e Telecomunicações From: Matthew Kozak [mailto:[hidden email]]
Manuel, For #2, look at the answer to this thread (Access Control tab and "Query local user" option in access rule) and config that in your current deployment method (not sure of specifics, but this should
map to registry settings that can be set at deploy time - have you found otherwise?): http://tightvnc.10971.n7.nabble.com/User-acceptance-td2128.html Thanks, -Matt From: Manuel Monteiro <[hidden email]> Hello everyone. I’ve deployed TightVNC through GPO (multiple networks, msi + mst) and everything works well.
By default, TightVNC allow us to log in into a user desktop without user’s permission.
What I would like to deploy now is one of two possibilities:
1.
TightVNC only runs when user wants to. a.
TightVNC must be already preconfigured. Don’t want user to set password and other options 2.
TightVNC is always running, but user is always queried.
a.
TightVNC must be deployed with this option. I don’t want to configure manually on every machine. Thank you for your time. Best regards, Manuel Monteiro.
Manuel Monteiro Departamento Tecnologias de Informação e Telecomunicações Aviso A informação contida nesta mensagem é confidencial e dirigida apenas
aos destinatários. Se recebeu esta mensagem por erro ou se houver algum problema, por favor contacte imediatamente o remetente. O uso não autorizado, divulgação, cópia ou alteração desta mensagem é estritamente proibido. A INDAQUA não será responsável por qualquer consequência direta, especial ou indireta, originada pela alteração do conteúdo desta informação, por terceiros,
ou como resultado de qualquer vírus transmitido. Se receber esta mensagem por engano, por favor, apague-a. A INDAQUA permite o uso razoável a título pessoal deste endereço de email. As opiniões, comentários ou imagens transmitidos através do mesmo não representam,
necessariamente, a INDAQUA. A INDAQUA não pode garantir que as comunicações veiculadas pelo presente email são seguras ou não contêm erros, uma vez que as mesmas podem ser intercetadas,
alteradas, perdidas, destruídas, chegar incompletas ou tardiamente, ou conter vírus. Disclaimer This message contains confidential information and is intended for the addressee only. If you have received this message by mistake or if there
is any problem, please notify the sender immediately. Any unauthorised use, distribution, copying or modification of this message is strictly forbidden. INDAQUA will not be responsible for any direct, special or indirect consequence, originated by the modification of the content of this information,
by third parties, or as resulted of any transmitted viruses. If you have received this message by mistake, please, delete it. INDAQUA
allows a reasonable use of this e-mail address for personal purposes. The opinions, commentaries or images transmitted through it do not, necessarily, represent INDAQUA. INDAQUA cannot guarantee that the communications in the present e-mail are secure or error-free since they can be intercepted, corrupted, lost,
destroyed, arrive late or incomplete, or contain viruses. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot ___________________________________________________________ TightVNC mailing list, [hidden email] To change your subscription or to UNSUBSCRIBE, please visit https://lists.sourceforge.net/lists/listinfo/vnc-tight-list |
Matthew, it’s done.
SET_IPACCESSCONTROL
and VALUE_OF_IPACCESSCONTROL fields at MST file. Thank you! Best regards, Manuel Monteiro Departamento Tecnologias de Informação e Telecomunicações From: Manuel Monteiro
Thank you, Matthew.
I was aware of
Access Control Rules, and that option is just perfect. Right now I’m unable to find a way to deploy it to all machines.
Best regards, Manuel Monteiro Departamento Tecnologias de Informação e Telecomunicações From: Matthew Kozak [[hidden email]]
Manuel, For #2, look at the answer to this thread (Access Control tab and "Query local user" option in access rule) and config that in your current deployment method (not sure of specifics, but this should
map to registry settings that can be set at deploy time - have you found otherwise?): http://tightvnc.10971.n7.nabble.com/User-acceptance-td2128.html Thanks, -Matt From: Manuel Monteiro <[hidden email]> Hello everyone. I’ve deployed TightVNC through GPO (multiple networks, msi + mst) and everything works well.
By default, TightVNC allow us to log in into a user desktop without user’s permission.
What I would like to deploy now is one of two possibilities:
1.
TightVNC only runs when user wants to. a.
TightVNC must be already preconfigured. Don’t want user to set password and other options 2.
TightVNC is always running, but user is always queried.
a.
TightVNC must be deployed with this option. I don’t want to configure manually on every machine. Thank you for your time. Best regards, Manuel Monteiro.
Manuel Monteiro Departamento Tecnologias de Informação e Telecomunicações Aviso A informação contida nesta mensagem é confidencial e dirigida apenas
aos destinatários. Se recebeu esta mensagem por erro ou se houver algum problema, por favor contacte imediatamente o remetente. O uso não autorizado, divulgação, cópia ou alteração desta mensagem é estritamente proibido. A INDAQUA não será responsável por qualquer consequência direta, especial ou indireta, originada pela alteração do conteúdo desta informação, por terceiros,
ou como resultado de qualquer vírus transmitido. Se receber esta mensagem por engano, por favor, apague-a. A INDAQUA permite o uso razoável a título pessoal deste endereço de email. As opiniões, comentários ou imagens transmitidos através do mesmo não representam,
necessariamente, a INDAQUA. A INDAQUA não pode garantir que as comunicações veiculadas pelo presente email são seguras ou não contêm erros, uma vez que as mesmas podem ser intercetadas,
alteradas, perdidas, destruídas, chegar incompletas ou tardiamente, ou conter vírus. Disclaimer This message contains confidential information and is intended for the addressee only. If you have received this message by mistake or if there
is any problem, please notify the sender immediately. Any unauthorised use, distribution, copying or modification of this message is strictly forbidden. INDAQUA will not be responsible for any direct, special or indirect consequence, originated by the modification of the content of this information,
by third parties, or as resulted of any transmitted viruses. If you have received this message by mistake, please, delete it. INDAQUA
allows a reasonable use of this e-mail address for personal purposes. The opinions, commentaries or images transmitted through it do not, necessarily, represent INDAQUA. INDAQUA cannot guarantee that the communications in the present e-mail are secure or error-free since they can be intercepted, corrupted, lost,
destroyed, arrive late or incomplete, or contain viruses. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot ___________________________________________________________ TightVNC mailing list, [hidden email] To change your subscription or to UNSUBSCRIBE, please visit https://lists.sourceforge.net/lists/listinfo/vnc-tight-list |
Free forum by Nabble | Edit this page |