The ConnectWise Control forum has moved to ConnectWise University! This forum has been locked and is in read-only mode. Click here for instructions on how to access the new forum.

Welcome Guest! You can not login or register.



Go to last post Go to first unread
#1 Posted : Monday, December 22, 2014 8:19:24 PM(UTC)

Rank: Member

Medals: Level 1: Random Act of Kindness! Received One Thanks!

Joined: 12/22/2014(UTC)
Posts: 16
United States
Location: San Diego

Thanks: 2 times
Was thanked: 1 time(s) in 1 post(s)
For the backstory here, I'm using Windows Server 2012R2 Essentials for my host.

This has a website already, which includes an SSL website (as well as remote desktop gateway, and SSTP VPN). So I'd rather not host the site on a second set of ports.

This requires the use of URL Rewrite and Application Request Routing packages for IIS.

Additionally, you need to change the IIS configuration to allow the "Bin" folder to be accessed, or else you won't be able to download the client software.

These issues apply to any version of IIS, but especially with Server Essentials (as I don't want to alter the main site in any way).

• Set ScreenConnect to use a subfolder, http://help.screenconnec...t_of_web.config_settings
o <add key="WebServerListenUri" value="http://+:8040/ScreenConnect/" />
o <add key="WebServerAddressibleUri" value="https://mysite.com/ScreenConnect/" />

• Install the URL Rewrite and Application Request Routing features for IIS (using the WPI Wizard in IIS).

• Launch the IIS Manager and click the server node in the tree view.
o Double click the “Application Request Routing Cache” icon
o Set the "timout" value to a higher value (periodically, you will see a "bad gateway" error from ScreenConnect's website, and this will change how often it occurs).
o Select the “Server Proxy Settings…” task in the Actions panel
o And Make sure that “Enable Proxy” checkbox is marked.
What this will do is allow any request in the server that is rewritten to a server that is not the local machine will be routed to the right place automatically without any further configuration.

• Open the site (in IIS) that you are going to be using, and create a directory in the main site for ScreenConnect (for instance “ScreenConnect”, so it will show up as http://mysite.com/ScreenConnect)
• Open the folder in IIS, and open the “Configuration Editor” option.
o Find the section “system.webServer/security/RequestFiltering” or type it into the “Section” box at top.
o Find the “FileExtensions” entry, and open it’s section.
o Find the “(Collection)” entry and click on the “Ellipse” button.
o Remove the “.config” entry, and then close the “Collection Editor” window.
o Now, find the “hiddenSegments” entry, and open it’s section.
o Find the “(Collection)” entry and click on the “Ellipse” button.
o Remove the “bin” entry, and then close the “Collection Editor” window.
o Hit “Apply” (in the left-hand sidebar), and then go back to the “features view” window for the “ScreenConnect”

• Open the URL Rewrite feature.
• Add a new incoming, blank rule.
o Set the pattern to be “^ScreenConnect/(.*)”
o Set the Rewrite URL to be http://localhost:8040/ScreenConnect/{R:1}
This works better (less errors in the status page) if you can use http://mysite.com:8040/ScreenConnect/{R:1}, but that requires that the server resolves the “mysite.com” to the local IP address
o Hit “Apply”

• Close IIS

This should allow ScreenConnect to work properly, and use the correct URL in every place that actually matters (client facing).

Edited by user Wednesday, January 21, 2015 1:24:16 AM(UTC)  | Reason: Adding additional rule (file extensions)

#2 Posted : Wednesday, September 2, 2015 6:32:02 AM(UTC)

Rank: Newbie

Joined: 9/2/2015(UTC)
Posts: 1
United Arab Emirates
Location: dubai

More about.....What is IIS ?

Users browsing this topic
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.