logo

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.

Notification

Icon
Error

Options
Go to last post Go to first unread
rich2323  
#1 Posted : Monday, March 2, 2015 3:52:56 PM(UTC)
rich2323


Rank: Advanced Member

Medals: ScreenConnect Advisor: Focus Group MemberLevel 1: Random Act of Kindness! Received One Thanks!

Joined: 1/28/2014(UTC)
Posts: 94
Location: daphne, al

Thanks: 50 times
Was thanked: 4 time(s) in 4 post(s)
Can someone walk me through the process of using the invite only session.

Here is what I have been trying and it does not seem to be working properly.

Create New support session
Enter Name and select join mode:invitation only
Enter session as host
Click on session on website, then click invite guest
Click on open email in outlook

New email is created with link
enter email address to send to user
Click "done"

User receives email, clicks on link
User is taken to the ScreenConnect website login screen

now what?

Rich




Scott  
#2 Posted : Tuesday, March 3, 2015 2:30:24 PM(UTC)
Scott


Rank: Administration

Medals: Level 4: Wise Old Owl! Received 100 Thanks!

Joined: 3/28/2014(UTC)
Posts: 2,862
United States

Thanks: 3 times
Was thanked: 351 time(s) in 303 post(s)
What link are they receiving?

What browser are they using? Does it allow javascript?
ScreenConnect Team
rich2323  
#3 Posted : Tuesday, March 3, 2015 5:49:04 PM(UTC)
rich2323


Rank: Advanced Member

Medals: ScreenConnect Advisor: Focus Group MemberLevel 1: Random Act of Kindness! Received One Thanks!

Joined: 1/28/2014(UTC)
Posts: 94
Location: daphne, al

Thanks: 50 times
Was thanked: 4 time(s) in 4 post(s)
I have tried it on several machines all with the same result. I have tried chrome and internet explorer, both allowing java script.

After you click the link, above the login screen says "The requested resource requires authentication. Please login to continue."

The link is the link generated when you click on Invite Guest. It has my host dns followed by a long session #.

Here is a copy of the email link:

Go to the web address below to join:
https://mydomainname:8040/?Session=c95355a9-a5d9-4a87-96d8-a88b3328b876

Rich

Edited by user Tuesday, March 3, 2015 5:49:37 PM(UTC)  | Reason: Not specified

Scott  
#4 Posted : Tuesday, March 3, 2015 8:53:16 PM(UTC)
Scott


Rank: Administration

Medals: Level 4: Wise Old Owl! Received 100 Thanks!

Joined: 3/28/2014(UTC)
Posts: 2,862
United States

Thanks: 3 times
Was thanked: 351 time(s) in 303 post(s)
Can you PM (or email to scott.linak@screenconnect.com) me one of those links to a session?
ScreenConnect Team
rich2323  
#5 Posted : Wednesday, November 18, 2015 10:45:01 PM(UTC)
rich2323


Rank: Advanced Member

Medals: ScreenConnect Advisor: Focus Group MemberLevel 1: Random Act of Kindness! Received One Thanks!

Joined: 1/28/2014(UTC)
Posts: 94
Location: daphne, al

Thanks: 50 times
Was thanked: 4 time(s) in 4 post(s)
Scott,

This is still happening. In order for us to use this tool for meetings I need the invite function to work. Do you have any suggestions on how we can have a permanent solution to this issue?

I am running on a Windows Server SC version 5.4.9730.5756

We changed the default page to go directly to the host page, and If I remember correctly that was the issue.

Rich
Scott  
#6 Posted : Monday, November 23, 2015 3:54:49 PM(UTC)
Scott


Rank: Administration

Medals: Level 4: Wise Old Owl! Received 100 Thanks!

Joined: 3/28/2014(UTC)
Posts: 2,862
United States

Thanks: 3 times
Was thanked: 351 time(s) in 303 post(s)
Well, changing the DefaultDocumentName to Host.aspx means that any request that does not specify a specific page will be redirected to the Host page. This means that even though the invite URL looks like

Code:

http://sub.domain.com/?Session=ID_HERE


it's actually being interpreted as:

Code:

http://sub.domain.com/Host.aspx?Session=ID_HERE


And the Host page interprets it differently. The obvious fix is to revert DefaultDocumentName to Guest.aspx as it's not really intended to be used in the manner you have it set. Alternatively, you could insert Guest.aspx into the URL when you're sending it out, but that adds another step that would be pretty annoying to have to remember.
ScreenConnect Team
thanks 1 user thanked Scott for this useful post.
rich2323 on 11/25/2015(UTC)
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.