GlobalMeet is a powerful tool for both web and audio meetings. The tool is easily installed by most end-users without any help from an IT organization. Likewise, patch updates and upgrades are also automatically installed without the end-user having to involve the IT organization.
PGi recognizes that many of our customer’s IT organizations desire to have more control over software that is pushed out to their user’s systems. This document outlines how the GlobalMeet Microsoft Outlook Toolbar, Stand-alone Desktop application, and ScreenShare applications are deployed using the Microsoft System Center Configuration Manager (SCCM).
Both install methods (managed and unmanaged installation) are supported by the same PGi executable file.
For initial installation:
· Customer must have an IT Deployment system that supports executing a .EXE file to a remote user with command line options (Microsoft System Center Configuration Manager (SCCM) 2007 and 2012 are used for this example)
For Update / Upgrade / Patch installation:
· Customer must have an IT Deployment system that permits remote deployment of .EXE files
· User must be logged in for the HKCU hive to be loaded.
There are two options for installing GlobalMeet desktop tools: managed and unmanaged. In a managed deployment, IT administrators push deployments to their users’ machines, using the installer. This document only covers Managed installations using SCCM.
This section details the programs that are installed by the GlobalMeet installer and guides the IT Professional in choosing the correct program(s). The GlobalMeet installer has three components:
a) GlobalMeet Outlook™ Toolbar
b) GlobalMeet Desktop Tool
c) GlobalMeet ScreenShare
The GlobalMeet toolbar is a plug-in for Microsoft Office Outlook® 2007, 2010, and 2013, running on Windows XP, Windows 7, or Windows 8 (Outlook 2010 and Outlook 2013). There is currently no toolbar for Mac users. The toolbar provides users a simple scheduling capability for all of their meetings.
The toolbar also requires the 32-bit version of Outlook and .NET 3.5 on end user machines. IT Groups performing a managed installation should be aware that in Windows 7 and higher, .NET 4.0 is installed by default; however, the user must be certain that the .NET 3.5 code is active.
The GlobalMeet toolbar mounts in the standard Outlook interface and is managed as a standard Outlook toolbar. Flash version 10 or higher is required. The GlobalMeet Toolbar is displayed as a menu in Outlook 2010 and higher, and as a ribbon in Outlook 2007. NOTE: Outlook 2003 is NOT supported.
GlobalMeet for Desktop is a tool that permits users to manage their meetings without relying on Microsoft Outlook. The tool uses a Graphical User Interface (GUI). GlobalMeet for Desktop monitors a GlobalMeet meeting, letting the host know when someone enters or leaves their web or audio meeting. GlobalMeet for Desktop runs quietly in the background. When someone enters the host’s meeting (or dials in to a monitored audio meeting), an alert pops up on the screen, displaying the name of the guest.
Typically GlobalMeet for Desktop is used when the user’s organization does not use Outlook as the primary mail client (gmail or Lotus Notes). Most IT organizations install the Desktop tool because of the useful “pop-up” notification that is displayed when someone enters the host’s room (see below).
The Screen Share app allows hosts to share an application or their entire screen with meeting participants.
Screen Share is a standalone application invoked by the GlobalMeet client when the user selects the Share My Screen function in the Web interface. If Screen Share is not found, GlobalMeet prompts the host to install it.
Microsoft Outlook must be closed prior to deployment of the GlobalMeet Toolbar for Outlook. If Outlook is not closed, and the “silent” option is used for the installation, then the install will fail without any indication given to the user or administrator. If the administrator has to close Outlook for their users, please see the “Advanced Scripting” section of this document.
While there are many software deployment packages available to the IT Professional it is prudent to focus our attention on the most common (SCCM). Other tools such as KACE from Dell or Altiris by Symantec perform in a similar fashion. This section describes how to deploy GlobalMeet using SCCM.
Deploying GlobalMeet using SCCM is accomplished through the creation of a “Package” (see below).
The IT professional should follow these steps to create their package to deploy GlobalMeet:
1. Copy the GlobalMeet Installer to a folder on the SCCM Server.
2. Access SCCM and create a package.
3. Name the package something “descriptive” such as “GlobalMeet Web Conferencing”
4. Use the “browse” feature to select the GlobalMeet Installer on the SCCM Server (GlobalMeet_Desktop_Tool_Setup.exe).
5. Add command line installer options. Details on the installer options should always be verified against the latest version of the PGi GlobalMeet Deployment Guide. The Deployment Guide is available from your Sales Engineer or Implementation Services team member.
6. For the “Program can run” option, select “Only when a user is logged on”.
7. For “Run Mode” you may select either “Run with user rights” or “Run with Administrator rights”.
At this point the executable should be distributed to the distribution points. After that simply advertise the package to the collection being used for the targeted user group.
The use of a script (such as Powershell) in SCCM is a common method of “customizing” the end user’s experience. By employing a script, the IT Professional may automate the following:
· Prompt the user about the install and inform them that they will need to locate their GlobalMeet Credentials to complete installation.
· Prompt the user to close MS Outlook, or that the script shall be closing Outlook in XX minutes.
· Ensures that Outlook has stopped before continuing
· Inform the user when installation is complete and exits
Scripting can improve user’s performance by removing the user from having to remember to shut down Outlook.
Running a script in conjunction with the GlobalMeet Installer requires the addition of “Requirements” to the package. The user would define their package, then add “requirements” to instruct the script to be run. When adding requirements, the IT Administrator would select “Always run this program first”.
After the determination of the SCCM Deployment method has been decided, the SCCM Developer should consult the PGi GlobalMeet Deployment Guide for the actual command line switches to be used to install the software. The latest version of the Deployment Guide is always available from the PGi Collaboration Sales Engineer or the Enterprise Sales Engineer or Implementation Services Team (IST) member.
View inventory records anonymously contributed by opt-in users of the K1000 Systems Management Appliance.