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

Notification

Icon
Error

Options
Go to last post Go to first unread
Guest  
#1 Posted : Friday, June 17, 2011 11:15:06 AM(UTC)
Guest


Rank: Advanced Member

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

Joined: 4/9/2010(UTC)
Posts: 331

Was thanked: 2 time(s) in 2 post(s)
Is there a way to do a silent install using the build installer? Are there any switches for the MSI file?
thanks 1 user thanked Guest for this useful post.
coriron on 10/31/2012(UTC)
Up2Date  
#2 Posted : Wednesday, September 7, 2011 5:07:45 AM(UTC)
Up2Date


Rank: Member

Joined: 9/7/2011(UTC)
Posts: 14
Location: Aus

Hello All

I'm on trial will be buying ScreenConnect i love it.

I've been trying to get it installed onto my clients computers. i've tried login scripts and group policy none have worked.

Does anyone know how to remotely get the unattended to install on domain computers without the customer needing to do anything.

Regards,
coriron  
#3 Posted : Wednesday, October 31, 2012 5:13:00 PM(UTC)
coriron


Rank: Member

Joined: 10/31/2012(UTC)
Posts: 11
Location: UK

Thanks: 5 times
Guest wrote:
Is there a way to do a silent install using the build installer? Are there any switches for the MSI file?

i'd like to renew this question? with 3.0 is there a way to do a silent install for deployment over a network?
gslonline  
#4 Posted : Friday, November 2, 2012 7:04:20 PM(UTC)
gslonline


Rank: Newbie

Joined: 11/2/2012(UTC)
Posts: 11

MSI installations have a bunch of command line switches, some of which help with silent/unattended installs:

Display Options
/quiet
Quiet mode, no user interaction
/passive
Unattended mode - progress bar only
/q[n|b|r|f]
Sets user interface level
n - No UI
b - Basic UI
r - Reduced UI
f - Full UI (default)

Have these been tried? /qn seems to work okay for me?

Thanks, Nick
michaeldale  
#5 Posted : Sunday, November 10, 2013 9:15:56 PM(UTC)
michaeldale


Rank: Advanced Member

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

Joined: 11/10/2013(UTC)
Posts: 73
Australia

Thanks: 4 times
Was thanked: 4 time(s) in 4 post(s)
I must be doing something wrong.

I want to set this up in Group Policy so that the agent is installed automatically.

While testing, ScreenConnect.ClientSetup.msi /qn works fine, but if I run the command a second time it uninstalls the application!

If I then run the command a third time the agent is successfully installed again but I get duplicate machines in my remote control list.

Any ideas? I'm running version 4.0.5552.5051.
Cloud Helpdesk: http://bluetrait.com/
Jeff  
#6 Posted : Monday, December 16, 2013 1:53:34 PM(UTC)
Jeff


Rank: Administration

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

Joined: 4/14/2010(UTC)
Posts: 1,785
Man
Location: Raleigh, NC

Thanks: 8 times
Was thanked: 156 time(s) in 122 post(s)
While I can not for sure say what is going on with Group Policy. The duplicate session I can help with. Currently the software keeps a list of all sessions for 24 hours (its a configuration setting in web.config) even the ones that have been uninstalled or are disconnected. Now that duration can be changed to be shorter or longer. What a lot of customers wanted was a way to quickly remove those from the list. In 4.1 we are introducing a new end button for unattended that will remove uninstalled clients from the list. It currently does not uninstall the client so if not uninstalled you would want to do that before removing from the list. Other changes around this use model will be released in 4.1 and will be documented in our output stream: http://forum.screenconne...ect-4-1-Release-Log.aspx
ScreenConnect Team
kiteloop  
#7 Posted : Wednesday, February 26, 2014 1:15:52 AM(UTC)
kiteloop


Rank: Newbie

Medals: ScreenConnect Advisor: Focus Group Member

Joined: 1/23/2014(UTC)
Posts: 4
Sweden

Originally Posted by: michaeldale Go to Quoted Post

While testing, ScreenConnect.ClientSetup.msi /qn works fine, but if I run the command a second time it uninstalls the application!


Originally Posted by: Jeff Go to Quoted Post
The duplicate session I can help with.


Jeff: I got a big problem since we are often sending the install commands several times to make it easier and not keeping track of what is installed and not. Making it hard to send out this update to 10 new machines when I uninstall it by misstake on 1000 machines.
Can you add a flag to install and one flag uninstall that would be great in the next release!
Jeff  
#8 Posted : Friday, February 28, 2014 2:50:12 PM(UTC)
Jeff


Rank: Administration

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

Joined: 4/14/2010(UTC)
Posts: 1,785
Man
Location: Raleigh, NC

Thanks: 8 times
Was thanked: 156 time(s) in 122 post(s)
Not sure about next release or not, but I will certainly run this by development to see what is going on and what we can do.
ScreenConnect Team
oakleyross  
#9 Posted : Thursday, April 3, 2014 4:31:24 PM(UTC)
oakleyross


Rank: Newbie

Joined: 4/3/2014(UTC)
Posts: 2
United States
Location: Atlanta

REM *** CUT AND PASTE THIS INTO A BAT OR CMD FILE TO RUN ***
REM *** ONLY AFTER YOU EDIT THE 4 VARIABLES BELOW ***
REM *** ***
REM *************************************************************
REM *************************************************************
REM *************************************************************
REM *************************************************************
REM *** ***
REM *** DATE: April 3rd, 2014 ***
REM *** ***
REM *** DESCRIPTION: ***
REM *** Check and Deploy Screen Connect Client ***
REM *** Via Active Directory Startup Script ***
REM *** ***
REM *** INPUTS: ***
REM *** (1) Package Location/Deployment Directory ***
REM *** (2) Script Logging Directory ***
REM *** (3) Package Installer Command Line Options ***
REM *** (4) Package Installer File Name ***
REM *** ***
REM *** OUTPUTS: Installs the Screen Connect Client ***
REM *** Reports an error if the client ***
REM *** is already installed ***
REM *** ***
REM *** ***
REM *************************************************************
REM *************************************************************
REM *************************************************************
REM *************************************************************
setlocal
REM *************************************************************
REM *************************************************************
REM *************************************************************
REM *************************************************************
REM *** ***
REM *** INPUTS (MODIFY AS APPROPRIATE) ***
REM *** ***
REM *** ***
REM *** (1) Package Location/Deployment Directory ***
REM *** (2) Script Logging Directory ***
REM *** (3) Package Installer Command Line Options ***
REM *** (4) PACKAGE INSTALLER File Name ***
REM *** ***
REM *************************************************************
REM *************************************************************
REM *************************************************************
REM *************************************************************
REM *** (1) PACKAGE LOCATION/DEPLOYMENT DIRECTORY ***
REM *** ***
set DeployDirectory=\\server\share
REM *** ***
REM *** (2) SCRIPT LOGGING DIRECTORY ***
REM *** ***
set logshare=\\server\share
REM *** ***
REM *** (3) PACKAGE INSTALLER COMMAND LINE OPTIONS ***
REM *** ***
set CommandLineOptions=/silent
REM *** ***
REM *** (4) PACKAGE INSTALLER FILE NAME ***
REM *** ***
set InstallFile=ScreenConnect.exe
REM *************************************************************
REM *************************************************************
REM *************************************************************
REM *************************************************************
REM *** ***
REM *** ***
REM *** BEGIN SCRIPT PROCESSING ***
REM *** ***
REM *** ***
REM *************************************************************
REM *************************************************************
REM *************************************************************
REM *************************************************************

echo %date% %time% the %0 script is running >> %logshare%%ComputerName%.log

REM *************************************************************
REM System verification
REM *************************************************************

set CustomConfig=None
REM Check if the screen connect client is already installed
REM IF EXIST "%SYSTEMDRIVE%\Program Files (x86)\ScreenConnect Client*" set CustomConfig=exists
REM IF EXIST "%SYSTEMDRIVE%\Program Files\ScreenConnect Client*" set CustomConfig=exists
REM

if %CustomConfig%==exists goto Found

REM *************************************************************
REM Deployment begins here
REM *************************************************************

:NotFound
REM

echo %date% %time% Package not detected, Begin Deployment >> %logshare%%ComputerName%.log

start /wait %DeployDirectory%\%InstallFile% %CommandLineOptions%
REM
echo %date% %time% Deployment Completed >> %logshare%%ComputerName%.log
echo %date% %time% : >> %logshare%%ComputerName%.log
echo %date% %time% Install Logs: >> %logshare%%ComputerName%.log
echo %date% %time% : >> %logshare%%ComputerName%.log

goto End

:Found
echo %date% %time% Screen Client install was detected, Halting >> %logshare%%ComputerName%.log
goto End

:End
echo %date% %time% the %0 script has completed successfully >> %logshare%%ComputerName%.log

Endlocal
dgparryuk  
#10 Posted : Wednesday, April 16, 2014 2:48:27 PM(UTC)
dgparryuk


Rank: Newbie

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

Joined: 4/16/2014(UTC)
Posts: 5

Was thanked: 1 time(s) in 1 post(s)
oakleyross - genius - there are a few minor bugs in it...
if anyone else is having trouble with it

all the "%logshare%%ComputerName%.log" lines need a \ - ie "%logshare%\%ComputerName%.log"

REM IF EXIST "%SYSTEMDRIVE%\Program Files (x86)\ScreenConnect Client*" set CustomConfig=exists
REM IF EXIST "%SYSTEMDRIVE%\Program Files\ScreenConnect Client*" set CustomConfig=exists

shouldn't be REM'd out

other than that :-)
thanks 1 user thanked dgparryuk for this useful post.
PRIVIX on 2/25/2015(UTC)
jeremyrnelson  
#11 Posted : Friday, September 30, 2016 8:26:21 PM(UTC)
jeremyrnelson


Rank: Member

Joined: 5/9/2015(UTC)
Posts: 17
United States
Location: Fort Wayne, IN

Thanks: 2 times
Please be aware we made the mistake of deploying via Group Policy and were informed by Ryan Dittmar in support that installing via GPO is not supported!
64QyrLh2ddSpB5  
#12 Posted : Thursday, October 4, 2018 6:03:39 PM(UTC)
64QyrLh2ddSpB5


Rank: Guest

Joined: 10/4/2018(UTC)
Posts: 1
United States
Location: Florida

Originally Posted by: dgparryuk Go to Quoted Post
oakleyross - genius - there are a few minor bugs in it...
if anyone else is having trouble with it

all the "%logshare%%ComputerName%.log" lines need a \ - ie "%logshare%\%ComputerName%.log"

REM IF EXIST "%SYSTEMDRIVE%\Program Files (x86)\ScreenConnect Client*" set CustomConfig=exists
REM IF EXIST "%SYSTEMDRIVE%\Program Files\ScreenConnect Client*" set CustomConfig=exists

shouldn't be REM'd out

other than that :-)


I ran into issues using this script this week. I had used it before, and made changes to get it to work, but had forgotten the changes I had to make.
I am re-posting the script, in it's entirety, with changes I had to make to get it to run. Modify as required:



REM *** CUT AND PASTE THIS INTO A BAT OR CMD FILE TO RUN ***
REM *** ONLY AFTER YOU EDIT THE 4 VARIABLES BELOW ***
REM *** ***
REM *************************************************************
REM *************************************************************
REM *************************************************************
REM *************************************************************
REM *** ***
REM *** DATE: October 3rd, 2018 ***
REM *** ***
REM *** DESCRIPTION: ***
REM *** Check and Deploy Screen Connect Client ***
REM *** Via Active Directory Startup Script ***
REM *** ***
REM *** INPUTS: ***
REM *** (1) Package Location/Deployment Directory ***
REM *** (2) Script Logging Directory ***
REM *** (3) Package Installer Command Line Options ***
REM *** (4) Package Installer File Name ***
REM *** ***
REM *** OUTPUTS: Installs the Screen Connect Client ***
REM *** Reports an error if the client ***
REM *** is already installed ***
REM *** ***
REM *** ***
REM *************************************************************
REM *************************************************************
REM *************************************************************
REM *************************************************************
setlocal
REM *************************************************************
REM *************************************************************
REM *************************************************************
REM *************************************************************
REM *** ***
REM *** INPUTS (MODIFY AS APPROPRIATE) ***
REM *** ***
REM *** ***
REM *** (1) Package Location/Deployment Directory ***
REM *** (2) Script Logging Directory ***
REM *** (3) Package Installer Command Line Options ***
REM *** (4) PACKAGE INSTALLER File Name ***
REM *** ***
REM *************************************************************
REM *************************************************************
REM *************************************************************
REM *************************************************************
REM *** (1) PACKAGE LOCATION/DEPLOYMENT DIRECTORY ***
REM *** ***
set DeployDirectory=\\<server FQDN>\ScreenConnect
REM *** ***
REM *** (2) SCRIPT LOGGING DIRECTORY ***
REM *** ***
set logshare=\\<server FQDN>\ScreenConnect\ScreenConnectLogs
REM *** ***
REM *** (3) PACKAGE INSTALLER COMMAND LINE OPTIONS ***
REM *** ***
set CommandLineOptions=/quiet
REM Had to change from silent to quiet
REM *** ***
REM *** (4) PACKAGE INSTALLER FILE NAME ***
REM *** ***
set InstallFile=<.MSI file name>
REM *************************************************************
REM *************************************************************
REM *************************************************************
REM *************************************************************
REM *** ***
REM *** ***
REM *** BEGIN SCRIPT PROCESSING ***
REM *** ***
REM *** ***
REM *************************************************************
REM *************************************************************
REM *************************************************************
REM *************************************************************

echo %date% %time% the %0 script is running >> %logshare%\%ComputerName%.log

REM *************************************************************
REM System verification
REM *************************************************************

set CustomConfig=None
REM Check if the screen connect client is already installed
IF EXIST "%SYSTEMDRIVE%\Program Files (x86)\ScreenConnect Client (<already installed #>)" set CustomConfig=exists
IF EXIST "%SYSTEMDRIVE%\Program Files\ScreenConnect Client (<already installed #>)" set CustomConfig=exists

REM

if %CustomConfig%==exists goto Found

REM *************************************************************
REM Deployment begins here
REM *************************************************************

:NotFound
REM

echo %date% %time% Package not detected, Begin Deployment >> %logshare%\%ComputerName%.log

start /wait %DeployDirectory%\%InstallFile% %CommandLineOptions%
REM
echo %date% %time% Deployment Completed >> %logshare%\%ComputerName%.log
echo %date% %time% : >> %logshare%\%ComputerName%.log
echo %date% %time% Install Logs: >> %logshare%\%ComputerName%.log
echo %date% %time% : >> %logshare%\%ComputerName%.log

goto End

:Found
echo %date% %time% Screen Client install was detected, Halting >> %logshare%\%ComputerName%.log
goto End

:End
echo %date% %time% the %0 script has completed successfully >> %logshare%\%ComputerName%.log

Endlocal
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.