Overview
You may have multiple GoToMeeting versions installed
from Windows Installer (MSI) files on your computer. The active version is set
by your GoToMeeting administrator on our GoToMeeting server. If the active
version is not available on your computer, it will be automatically downloaded
and installed when you log in and start a session. To run sessions using the
version installed by the MSI, your GoToMeeting account must have the same
version set on the server.
Note: If multiple versions of
GoToMeeting are installed on your computer from the GoToMeeting website and
from the MSI file, uninstalling the MSI file may remove all existing versions
of GoToMeeting.
Quick Start
To install the GoToMeeting MSI file, you need
administrative rights on your computer. You can either double-click the MSI
file in Windows Explorer or simply run the following commands in a command
prompt:
Install or uninstall GoToMeeting in Default Mode:
msiexec /i G2MSetup6.3.1.1468_IT.msi
msiexec
/x G2MSetup6.3.1.1468_IT.msi
Install or uninstall GoToMeeting in Quiet Mode:
msiexec /i G2MSetup6.3.1.1468_IT.msi
/quiet msiexec /x G2MSetup6.3.1.1468_IT.msi
/quiet
Configuring the GoToMeeting Installer
Some GoToMeeting default preferences can be
overridden and specified during the installation process. MSI Property
parameters can be controlled by command line arguments or transform files. The
following configuration parameters are currently available when installing the
GoToMeeting MSI:
Description
|
Configuration Option
|
Valid Values
|
Default Value
|
Description
|
Start automatically at login
|
G2MRUNATLOGON
|
true | false
|
true
|
Start
GoToMeeting automatically after logging in to the computer.
|
Integration
|
G2MINTEGRATION
|
None | Notes | Outlook |
Email | Auto
|
None
|
Specify
GoToMeeting integration with other applications.
|
Recording audio
|
G2MRECAUDIO
|
true | false
|
true
|
|
Recording convert
|
G2MRECCONVERT
|
true | false
|
false
|
Convert
the video content to
|
Recording save location
|
G2MRECPATH
|
<..valid path..>
|
<...user personal
folder..
.>
|
Specify the location where the media content is
stored.
|
Chat save location
|
G2MCHATSAVEPATH
|
<..valid path..>
|
<...user personal folder..
|
Specify the location where the chat content is
stored.
|
.>
If some of these options have an invalid value or the
paths do not exist, the corresponding option results in its default value. If
an existing GoToMeeting version is already setup with specific user
preferences, those values are reset with the new values that were specified
during the installation process. If GoToMeeting is running during the
installation process, you must restart the GoToMeeting application to apply the
new preferences.
Examples
Override all GoToMeeting default preferences with
custom values:
msiexec /i G2MSetup6.3.1.1468_IT.msi
G2MRUNATLOGON=false G2MINTEGRATION=Notes
G2MRECAUDIO=false G2MRECCONVERT=true
G2MRECPATH="C:\My Recordings" G2MCHATSAVEPATH="C:\My Personal
Chat"
Enable the installation process logging (refer to the
“msiexec.exe” command help for more options):
msiexec /i G2MSetup6.3.1.1468_IT.msi /l*
C:\MyLogFile.log
For a more convenient way to install a specific
configuration, you can pack the commands in batch files or use a UI tool (e.g.,
Microsoft Orca) to add the options in the MSI Property table, which will
override the default values.
Installing GoToMeeting for All Users
When the installer is used from either the command
prompt or Windows Explorer, GoToMeeting is only installed for the current
logged in user by default. There is currently no option exposed by the
installer that can be used to install GoToMeeting for all users who are using a
computer – only Group Policy installations that are configured accordingly are
capable of doing so.
Transform Files
For a more convenient way to run installations with
custom parameters, you can use MSI transform (MST) files.
Note: The Group Policy installations do
not support command line options. You may need to use MST files to apply custom
settings for multiple users.
msiexec /i G2MSetup6.3.1.1468_IT.msi
TRANSFORMS=CorporateSettings.mst To
create an MST file, you can use a UI tool like Microsoft Orca. Using Microsoft
Orca, select New Transform >
specify the configuration options described above with the new values in the
Property table > Generate Transform
command.
Installing GoToMeeting to Multiple Computers within Network Domains
through an Active Directory
Domain administrators can automatically
update multiple computers with different versions of GoToMeeting. This is a
very convenient way to deploy and install software to thousands of computers
throughout a network by simply configuring Group Policy Objects on the Domain
Controller.
Domain administrators can deploy versions of
GoToMeeting to specific computers, users or groups within a network domain.
Deploying a software package to a user or a group (which consists of multiple
users) installs the software and is then ready to use by a user once the user
logs in to any computer in the domain. Deploying a software package to a
computer installs the software and is then ready to use by all users using that
particular computer.
Also, domain administrators can install software
through the Active Directory, by either Publishing or Assigning applications.
• Assigning software: When the user logs
in, the software will be installed automatically for the user (or to your
computer) without any prompts to download software.
• Publishing software: When the software
is published, the user will have the option to install it on demand if needed.
To see all published software that is assigned to the domain user, group or
computer on Windows 7 or Vista, go to the Control
Panel > Programs and Features.
In the left navigation, click Install a
program from the network, and you will see all the software published to
you. You can't publish software to computers using Group Policy, only to users
and groups.
All these installation scenarios can be configured
in the Group Policy Management console on the Windows Server.
Additionally, domain administrators have the ability
to configure GoToMeeting installations with specific GoToMeeting user
preferences. See Configuring
the GoToMeeting Installer to see which GoToMeeting options you can
configure. You can control GoToMeeting user preferences using an MST file.
To configure GoToMeeting installations, create a Transform File
and open the Group Policy Management console on a Windows Server. To create an
“Advanced” Group Policy Object, specify the GoToMeeting installer package and
then chose the transform file you just created from the Modifications tab.
Note: If the GoToMeeting installer is
used with Group Policy assigned to network computers, the installation cannot
be configured with transform files. We currently do not support this, so only
installations assigned to Users and Groups can be configured. Furthermore, we
do not recommend installing older versions of GoToMeeting alongside GoToMeeting
v5.2 with Group Policy since it may conflict with the version.
Uninstalling GoToMeeting from Multiple Computers within Network Domains
Domain administrators can automatically uninstall
GoToMeeting from multiple users’ computers by configuring the Group Policy
Object that they used to install GoToMeeting. However, we do not recommend
using Group Policy to uninstall GoToMeeting from multiple users’ computers
because not all aspects of the installation can be removed, and some
GoToMeeting remnants may remain.
• Uninstall
GoToMeeting from multiple users’ computers (not recommended):
1. Go
to Group Policy Object properties.
2. Select
the Deployment tab > “Uninstall this application when it falls
out of the scope of management” check box.
• Uninstall
GoToMeeting manually (recommended):
1. First
check that the Start Manually option
is enabled from the GoToMeeting user preference – and not Start automatically after I log in to Windows (which may result in
an incomplete installation).
2. Go
to the Control Panel > Programs and Features > Uninstall GoToMeeting.
Note: We recommend using Group Policy
installations, but the current installer should cover the basic requirements
and installation scenarios of more powerful deployment solutions like
Microsoft’s SMS/SCCM.
0 comments:
Post a Comment
Note: Only a member of this blog may post a comment.