logo
Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Options
Go to last post Go to first unread
trybakqs1  
#1 Posted : Monday, November 20, 2017 1:10:21 PM(UTC)
trybakqs1


Rank: Guest

Joined: 11/20/2017(UTC)
Posts: 1

In our environment (Screenconnect verion 6.4), we have removed admin rights from our users. When we upgrade Screenconnect, the new client install requires admin rights and it causes headaches for our support team. I'd like to use PDQ deploy to push the install out to all of my support staff. However, when I grab the ScreenConnect.ClientSetup.msi file from our server and try to install it, it registers with an identifier of TBD, instead of the identifier of our server. This means that it isn't recognized when one of my hosts tries to join a support session. They are still getting prompted to install the software because the identifiers don't match.

Is there an accepted way to generate the actual msi with the identifier integrated?
Scott  
#2 Posted : Monday, December 11, 2017 1:30:56 PM(UTC)
Scott


Rank: Administration

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

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

Thanks: 3 times
Was thanked: 305 time(s) in 262 post(s)
Sorry, I'm not sure what you mean by this:
Quote:
when I grab the ScreenConnect.ClientSetup.msi file from our server and try to install it, it registers with an identifier of TBD


Can you elaborate a bit more on the behavior you see when you push it out this way?
ScreenConnect Team
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.