Windows Remote Assistance - Revision history

Michael.mast: /* Deploy to workstations */

2017-03-28T17:53:13Z

Deploy to workstations

Michael.mast: /* Deploy to workstations */

2017-03-27T17:54:12Z

Deploy to workstations

Michael.mast at 16:11, 27 March 2017

2017-03-27T16:11:43Z

Michael.mast: Created page with "https://technet.microsoft.com/en-us/library/ff356868.aspx https://blogs.msdn.microsoft.com/asklar/2012/03/14/remote-assistance-and-uac-prompts/ http..."

2017-03-27T16:04:48Z

Created page with "<ref>https://technet.microsoft.com/en-us/library/ff356868.aspx</ref> <ref>https://blogs.msdn.microsoft.com/asklar/2012/03/14/remote-assistance-and-uac-prompts/</ref> <ref>http..."

New page

<ref>https://technet.microsoft.com/en-us/library/ff356868.aspx</ref>
<ref>https://blogs.msdn.microsoft.com/asklar/2012/03/14/remote-assistance-and-uac-prompts/</ref>
<ref>https://technet.microsoft.com/en-us/library/dd851479.aspx</ref>

@@ Line 14: / Line 14: @@
 <br>
 Make sure to select the shortcut location as the source, the destination should be C:\Users\Public\Public Desktop\name of shortcut
 ==General Structure==

@@ Line 4: / Line 4: @@
 Looking to spend as little money as possible I have been using Splashtop SSO support tool for remote access. However, this does not play well with UAC and prevents me from typing anything into password prompts. To help mitigate this on machines located on the LAN I want to deploy Microsoft Remote Assistance. Sadly the Easy Connect doesn't play well with firewalls and secured locations. Here are my attempts to get this working as a viable option.
 ==Deploy to workstations==
 ==General Structure==
 The idea is to have the user do as little as possible. For this I deployed the script mentioned above to their desktops. When they launch the script an invitation file is created on a network share that I have access too. The shared secret is the same for all users, but since users will be expecting me to remote in I don't see an issue. Maybe I will rotate it over time? Who knows!

← Older revision		Revision as of 16:11, 27 March 2017
Line 2:		Line 2:
	<ref>https://blogs.msdn.microsoft.com/asklar/2012/03/14/remote-assistance-and-uac-prompts/</ref>		<ref>https://blogs.msdn.microsoft.com/asklar/2012/03/14/remote-assistance-and-uac-prompts/</ref>
	<ref>https://technet.microsoft.com/en-us/library/dd851479.aspx</ref>		<ref>https://technet.microsoft.com/en-us/library/dd851479.aspx</ref>
		+	Looking to spend as little money as possible I have been using Splashtop SSO support tool for remote access. However, this does not play well with UAC and prevents me from typing anything into password prompts. To help mitigate this on machines located on the LAN I want to deploy Microsoft Remote Assistance. Sadly the Easy Connect doesn't play well with firewalls and secured locations. Here are my attempts to get this working as a viable option.
		+	==Deploy to workstations==
		+	==General Structure==
		+	The idea is to have the user do as little as possible. For this I deployed the script mentioned above to their desktops. When they launch the script an invitation file is created on a network share that I have access too. The shared secret is the same for all users, but since users will be expecting me to remote in I don't see an issue. Maybe I will rotate it over time? Who knows!
		+	<br>
		+	<br>
		+	When I am finished the file is deleted and we move on with our lives.