MSI Mass Deployment
We are currently in the process of a mass deployment and have the MSI configured so all machines will join the "new installs" group. The MSI is configured so that all machines will join with their service tag. We are not setting up any machine with unattended access. But it looks like the initial connection will require input from the end user. They will need to provide their password, and then after the initial connection we can prompt the user to allow, which is the desired behavior. Is there any way to get around the initial connection requiring the end user's password? This will be a long and tedious deployment if we have to do that for every machine.
Best Answer
-
After working with a very helpful Teamviewer support agent, we found a solution.
Deploy the MSI with unattended access, then use a policy to enforce access control. The policy is assigned to a group. The MSI can be configured to have the endpoints join that group, or all endpoints can be joined manually. This allows for great flexibility, should an endpoint require unattended access at a later time.
6
Answers
-
Hi @Rich_ ,
Thank you for your post.
If you are aiming to set up unattended access with MSI Deployment, it should ask the enduser to confirm the account assignment without telling the password. However, as MSI Deployment can be complicated in different scenarios, we suggest you to contact TeamViewer Support Team for further assistnance and discussion on your settings and goals on TeamViewer MSI deployment.
Thank you for your understanding and hope your case can be fixed soon.
Regards
Ying_Q
Community Moderator/中文社区管理员0 -
Hi Ying. Thank you for the response. As stated in my original post we are not aiming to setup with unattended access. Just the opposite. We want to require the end user to accept the connection. The deployment works, but requires the end user to provide their password for the initial connection. Thereafter, we can prompt the user to allow access, which is how we want this setup. This would require us to reach out to each end user after deployement, get their password, and establish a connection. That is a time consuming process that we are trying to avoid. Thanks for input.
@Ying_Q wrote:Hi @Rich_ ,
Thank you for your post.
If you are aiming to set up unattended access with MSI Deployment, it should ask the enduser to confirm the account assignment without telling the password. However, as MSI Deployment can be complicated in different scenarios, we suggest you to contact TeamViewer Support Team for further assistnance and discussion on your settings and goals on TeamViewer MSI deployment.
Thank you for your understanding and hope your case can be fixed soon.
Regards
Ying_Q
0 -
After working with a very helpful Teamviewer support agent, we found a solution.
Deploy the MSI with unattended access, then use a policy to enforce access control. The policy is assigned to a group. The MSI can be configured to have the endpoints join that group, or all endpoints can be joined manually. This allows for great flexibility, should an endpoint require unattended access at a later time.
6
