Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
remotecontrol:screenconnect:how_to_give_your_customers_access_to_their_computers_with_screenconnect [2018/02/25 01:18]
127.0.0.1 external edit
remotecontrol:screenconnect:how_to_give_your_customers_access_to_their_computers_with_screenconnect [2018/12/21 21:04] (current)
nullzilla
Line 4: Line 4:
  
 If you're looking for a wedge, eating up their LogMeIn/​GoToMyPC bill is a pretty nice way to get them to stop paying them and start paying you instead. If you're looking for a wedge, eating up their LogMeIn/​GoToMyPC bill is a pretty nice way to get them to stop paying them and start paying you instead.
 +
 +**<font inherit/​inherit;;#​c0392b;;​inherit>​Note:​ Instead of following these steps you can use the new</​font>​[[https://​docs.connectwise.com/​ConnectWise_Control_Documentation/​Supported_extensions/​Productivity/​Remote_Workforce|Remote Workplace Extension]]<​font inherit/​inherit;;#​c0392b;;​inherit>​.</​font>​**
 +
 ===== 1. Secure Screenconnect ===== ===== 1. Secure Screenconnect =====
 +
   - If Self-hosted   - If Self-hosted
-    ​- If you haven'​t already, install an SSL certificate on your ScreenConnect server to secure user logins +      ​- If you haven'​t already, install an SSL certificate on your ScreenConnect server to secure user logins 
-      - [[https://​help.screenconnect.com/​SSL_certificate_installation]] +        - [[https://​help.screenconnect.com/​SSL_certificate_installation|https://​help.screenconnect.com/​SSL_certificate_installation]] 
-    - You can also piggyback off an existing SSL certificate if you're sharing the server with something else +      - You can also piggyback off an existing SSL certificate if you're sharing the server with something else 
-      - [[https://​help.screenconnect.com/​Piggybacking_off_existing_SSL_certificate]]+        - [[https://​help.screenconnect.com/​Piggybacking_off_existing_SSL_certificate|https://​help.screenconnect.com/​Piggybacking_off_existing_SSL_certificate]]
   - If Cloud-hosted   - If Cloud-hosted
-    ​- Open a ticket with Labtech and ask them to secure your ScreenConnect web interface and remind them that it's 2017 and how dare they +      ​- Open a ticket with Labtech and ask them to secure your ScreenConnect web interface and remind them that it's 2017 and how dare they 
-    - While they'​re at it, see if they'​ll update you to the latest ScreenConnect,​ it's nice+      - While they'​re at it, see if they'​ll update you to the latest ScreenConnect,​ it's nice
   - In LabTech Control Center   - In LabTech Control Center
-    ​- Change the ScreenConnect URL to match your new HTTPS url +      ​- Change the ScreenConnect URL to match your new HTTPS url 
-      - Dashboard > Config > Integrations > ScreenConnect Dashboard\\ {{:​rmm:​pasted:​20161015-232005.png}}+        - Dashboard > Config > Integrations > ScreenConnect Dashboard \\ {{:​rmm:​pasted:​20161015-232005.png}} 
 ===== 2. Create User-based Session Groups ===== ===== 2. Create User-based Session Groups =====
 +
   - You'll group the machines in the Host page using a CustomPropertyN field. You have 8 possible choices for the N value (1 through 8); only CustomProperty1 is turned on by default, and is labeled "​Organization"​. It's recommended that you use CustomProperty2 for this. Name the group something that will make sense to you as machines are added later on, such as "​Assigned User":   - You'll group the machines in the Host page using a CustomPropertyN field. You have 8 possible choices for the N value (1 through 8); only CustomProperty1 is turned on by default, and is labeled "​Organization"​. It's recommended that you use CustomProperty2 for this. Name the group something that will make sense to you as machines are added later on, such as "​Assigned User":
   - To do this, go to Administration > Appearance and search for "​SessionProperty.Custom2"​   - To do this, go to Administration > Appearance and search for "​SessionProperty.Custom2"​
   - Click on Edit and change these two variables   - Click on Edit and change these two variables
-    ​- SessionProperty.Custom2.AccessVisible = true +      ​- SessionProperty.Custom2.AccessVisible = true 
-    - SessionProperty.Custom2.LabelText = Assigned User: +      - SessionProperty.Custom2.LabelText = Assigned User: 
-    - {{:​remotecontrol:​screenconnect:​pasted:​20170127-204124.png}}+      - {{:​remotecontrol:​screenconnect:​pasted:​20170127-204124.png}}
   - Go to your Hosts page, click on Access, click on Manage Session Groups. For the filter, add in the following text exactly as written below except change the capital N to the number of the custom property that you used (very likely this will be 2, but could be 1-8):   - Go to your Hosts page, click on Access, click on Manage Session Groups. For the filter, add in the following text exactly as written below except change the capital N to the number of the custom property that you used (very likely this will be 2, but could be 1-8):
-    ​- CustomPropertyN = $USERNAME\\ {{:​rmm:​pasted:​20161015-231630.png}}+      ​- CustomPropertyN = $USERNAME \\ {{:​rmm:​pasted:​20161015-231630.png}}
   - Nothing will appear in this group yet - this is normal. There'​s more documentation on Session Groups here:   - Nothing will appear in this group yet - this is normal. There'​s more documentation on Session Groups here:
-    ​- [[http://​help.screenconnect.com/​Managing_session_groups]]+      ​- [[http://​help.screenconnect.com/​Managing_session_groups|http://​help.screenconnect.com/​Managing_session_groups]]
   - Go to the Admin page > Security tab.   - Go to the Admin page > Security tab.
-    ​- Create a security role called "User Access Only" (or whatever you would like) for your end users that will have access to their own machine on the Give the following permissions to this role: +      ​- Create a security role called "User Access Only" (or whatever you would like) for your end users that will have access to their own machine on the Give the following permissions to this role: 
-      - ViewSessionGroup:​ SpecificSessionGroup:​ My Machines +        - ViewSessionGroup:​ SpecificSessionGroup:​ My Machines 
-      - HostSessionWithoutConsent:​ SpecificSessionGroup:​ My Machines +        - HostSessionWithoutConsent:​ SpecificSessionGroup:​ My Machines 
-      - Depending on if you would like the users to be able to transfer files, you may also want to give them the File Transfer permission. +        - Depending on if you would like the users to be able to transfer files, you may also want to give them the File Transfer permission. 
-      - JoinSession:​ SpecificSessionGroup:​ My Machines +        - JoinSession:​ SpecificSessionGroup:​ My Machines 
-      - {{:​remotecontrol:​screenconnect:​pasted:​20170127-205014.png}} +        - {{:​remotecontrol:​screenconnect:​pasted:​20170127-205014.png}} 
-      - More info here +        - More info here 
-        - [[http://​help.screenconnect.com/​index.php?​title=Defining_user_roles_and_permissions]]+          - [[http://​help.screenconnect.com/​index.php?​title=Defining_user_roles_and_permissions|http://​help.screenconnect.com/​index.php?​title=Defining_user_roles_and_permissions]]
   - Create a test user with the username of Test, and give the new security role you created to this user. Be sure to click Save Security on the bottom right corner   - Create a test user with the username of Test, and give the new security role you created to this user. Be sure to click Save Security on the bottom right corner
   - Go to your Hosts page > All Machines under Access, then right click on a machine. Under the "​Assigned User" field, enter the username as you entered it on the security page (it's case sensitive).   - Go to your Hosts page > All Machines under Access, then right click on a machine. Under the "​Assigned User" field, enter the username as you entered it on the security page (it's case sensitive).
Line 41: Line 47:
  
 ===== Optional: Getting Your Customers to Use It ===== ===== Optional: Getting Your Customers to Use It =====
-  ​- You //could// tell your customers to go to https://​company.hostedrmm.com:​8040 to get to their PC, but that's not a nice URL, so do this instead+ 
 +  ​- You //​could// ​ tell your customers to go to [[https://​company.hostedrmm.com:​8040|https://​company.hostedrmm.com:​8040]] ​to get to their PC, but that's not a nice URL, so do this instead
   - Make a subdomain of your domain name, like remote.yourcompany.com   - Make a subdomain of your domain name, like remote.yourcompany.com
-    ​- make sure to get an SSL certificate for this subdomain+      ​- make sure to get an SSL certificate for this subdomain
   - We're going to make an iframe and wrap it around your ScreenConnect login page   - We're going to make an iframe and wrap it around your ScreenConnect login page
   - Make an index.html in it and use the following code in it, making sure to change to your SC server URL in the iframe   - Make an index.html in it and use the following code in it, making sure to change to your SC server URL in the iframe
-  - <code html index.html><​!DOCTYPE html PUBLIC "​-//​W3C//​DTD XHTML 1.0 Transitional//​EN"​ "​http://​www.w3.org/​TR/​xhtml1/​DTD/​xhtml1-transitional.dtd">​+  - 
 + 
 +index.html 
 + 
 +<code html4strict> 
 +<​!DOCTYPE html PUBLIC "​-//​W3C//​DTD XHTML 1.0 Transitional//​EN"​ "​http://​www.w3.org/​TR/​xhtml1/​DTD/​xhtml1-transitional.dtd">​
 <html xmlns="​http://​www.w3.org/​1999/​xhtml">​ <html xmlns="​http://​www.w3.org/​1999/​xhtml">​
     <​head>​     <​head>​
Line 58: Line 70:
             #content             #content
             {             {
-                position:​absolute;​ left: 0; right: 0; bottom: 0; top: 0px; +                position:​absolute;​ left: 0; right: 0; bottom: 0; top: 0px;
             }             }
         </​style>​         </​style>​
Line 67: Line 79:
         </​div>​         </​div>​
     </​body>​     </​body>​
-</​html></​code>​+</​html>​ 
 +</​code>​ 
  
  • Last modified: 2018/12/21 21:04
  • by nullzilla