Installers and Pre-Requisites - Huddle



Huddle for Windows MSIInstallers and Pre-RequisitesPre-requisitesMicrosoft Downloads 4.5dotNetFx45_Full_setup.exe48.1 Mb InstallersMSI Installer 64-bitHuddle Global: Huddle US Government: Installer 32-bitHuddle Global: Huddle US Government: Installer FeaturesHuddle for Windows is distributed as a Microsoft Installer (MSI). There are packages for each processor architecture; Huddle.msi for 64-bit processors and Huddle_x86.msi. Packages can be installed by double-clicking them in the file explorer. The msiexec.exe command line utility has additional features available, like non-interactive installation and administrative installation.Non-interactive Installationmsiexec /i Huddle.msiAdditional parameters can be passed at the end of this command line, like;/q – No interfacemsiexec /i Huddle.msi /q/l*v install.log – log everything to install.log filemsiexec /i Huddle.msi /q /l*v install.log Additional ParametersAUTOUPDATEENABLEDEnable auto update, default is 0. The user will need admin rights to be able to auto update.AUTOSTARTEnable auto start (auto start the application after MSI completes), default is 0. HAS_PROXYProxy parameters. Discussed laterPROXY_IS_SYS_DEFAULTProxy parameters. Discussed laterPROXY_USE_DEFAULT_CREDENTIALSProxy parameters. Discussed laterPROXY_MANUAL_ADDRESSProxy parameters. Discussed laterSSO_IDPSP initiated Single Sign-On (SSO). This should be set only for those Huddle accounts with SSO activated and the Identity provider is going to be accessible to users at the point they sign in.msiexec /i Huddle.msi /q /l*v install.log AUTOUPDATEENABLED=1 AUTOSTART=1ormsiexec /i Huddle.msi /q /l*v install.log SSO_IDP= for All Users / Single User on MachineThe installation will always be for all users.Uninstallationmsiexec /u Huddle.msiIt is not necessary to have the MSI file available for uninstallation; alternatively, the package or product code can also be specified. Administrative installationmsiexec /a Huddle.msi TARGETDIR=Z:\software\HuddleAn "administrative" (network) installation can be initiated. The files get unpacked into the target directory (which should be a network directory), but no other modification is made to the local system. In addition, another (smaller) MSI file is generated in the target directory, which clients can then use to perform a local installation.Advertisementmsiexec /jm Huddle.msiIt is possible to "advertise" Huddle for Windows to a machine. This would cause the icons to appear in the start menu, without the software actually being installed. The first usage of a Huddle for Windows would cause that Huddle for Windows to be installed.Automatic Installation on a Group of MachinesWith Windows Group Policy, it is possible to automatically install Huddle for Windows on a group of machines. To do so, perform the following steps:Log on to the domain controllerCopy the MSI file into a folder that is shared with access granted to all target machines.Open the MMC snapin "Active Directory users and computers"Navigate to the group of computers that need Huddle for WindowsOpen PropertiesOpen Group PoliciesAdd a new polices, and edit itIn Computer Configuration/Software Installation, chose New/PackageSelect the MSI file through the network pathOptionally, select that you want the Huddle for Windows to be uninstalled if the computer leaves the scope of the policy.Group policy propagation typically takes some time - to reliably deploy the package, all machines should be rebooted.For a full list of msiexec command-line options entriesHKLM\Software\Classes\HuddleHuddle for Windows registers a custom protocol huddle:// in the following registry root, running Huddle.exe to handle this protocol.HKLM\Software\Microsoft\Internet Explorer\MAIN\FeatureControl\FEATURE_BROWSER_EMULATIONHKLM\Software\Wow6432Node\Microsoft\Internet Explorer\MAIN\FeatureControl\FEATURE_BROWSER_EMULATIONThis setting of 0 prevents Internet Explorer emulating different browser characteristics for Huddle.exe.HKLM\Software\Microsoft\Internet Explorer\Low Rights\ElevationPolicy\{024452F1-4DAB-4928-A327-B74E09BA9461}HKLM\Software\Wow6432Node\Microsoft\Internet Explorer\Low Rights\ElevationPolicy\{024452F1-4DAB-4928-A327-B74E09BA9461}This root key contains permission to ensure that when the huddle:// custom protocol is passed from the browser to Huddle.exe after the confirmation dialog, there is no additional dialog detailing the origin of Huddle.exe.HKLM\Software\Microsoft\Windows\CurrentVersion\RunSets Huddle.exe to autostart when AUTOSTART setting enabled.Specifying Proxy ServerTo specify a proxy server a number of different settings can be used. By default we use the system default proxy, by inheriting proxy settings from IE.Auto Proxy Server authenticated (via Group Policy, with default, integrated authentication)msiexec Huddle.msi HAS_PROXY="1" PROXY_IS_SYS_DEFAULT="1" PROXY_USE_DEFAULT_CREDENTIALS="1"Auto Proxy Server unauthenticated (via Group Policy, with default, no authentication)msiexec Huddle.msi HAS_PROXY="1" PROXY_IS_SYS_DEFAULT="1" PROXY_USE_DEFAULT_CREDENTIALS="0"Manual Proxy Server authenticatedmsiexec Huddle.msi HAS_PROXY="1" PROXY_IS_SYS_DEFAULT="0" PROXY_USE_DEFAULT_CREDENTIALS="1" PROXY_MANUAL_ADDRESS=""Manual Proxy Server unauthenticatedmsiexec Huddle.msi HAS_PROXY="1" PROXY_IS_SYS_DEFAULT="0" PROXY_USE_DEFAULT_CREDENTIALS="0" PROXY_MANUAL_ADDRESS=""Manual Proxy ConfigurationThe above steps will ensure MSIs deployed by administrators are correctly configured.On the rare occasion a user needs to set this manually the, rather undesirable, method to configure manually is to add the follow the examples below.No Proxy Example<?xml version="1.0"?><configuration><appSettings><add key="TopLevelDomain" value="dev" /><add key="UserAgent" value="HuddleDesktopPC" />:</appSettings><startup><supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.0" /></startup></configuration>Group-Policy, authenticated (with local user) Proxy<?xml version="1.0"?><configuration><appSettings><add key="TopLevelDomain" value="dev" /><add key="UserAgent" value="HuddleDesktopPC" />:</appSettings><startup><supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.0" /></startup><> <defaultProxy enabled="true" useDefaultCredentials="true"> <proxy usesystemdefault="true" /> </defaultProxy></></configuration>Group-Policy, unauthenticated Proxy<?xml version="1.0"?><configuration><appSettings><add key="TopLevelDomain" value="dev" /><add key="UserAgent" value="HuddleDesktopPC" />:</appSettings><startup><supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.0" /></startup><> <defaultProxy enabled="true" useDefaultCredentials="false"><proxy usesystemdefault="true" /> </defaultProxy></></configuration>Manual, authenticated Proxy (proxy server is )<?xml version="1.0"?><configuration><appSettings><add key="TopLevelDomain" value="dev" /><add key="UserAgent" value="HuddleDesktopPC" />:</appSettings><startup><supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.0" /></startup><> <defaultProxy enabled="true" useDefaultCredentials="true"> <proxy usesystemdefault="false" proxyaddress=”” /> </defaultProxy></></configuration>Manual, unauthenticated Proxy (proxy server is )<?xml version="1.0"?><configuration><appSettings><add key="TopLevelDomain" value="dev" /><add key="UserAgent" value="HuddleDesktopPC" />:</appSettings><startup><supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.0" /></startup><> <defaultProxy enabled="true" useDefaultCredentials="false"> <proxy usesystemdefault="false" proxyaddress=”” /> </defaultProxy></></configuration>Manual, PAC-specified Proxy (PAC file is available from server is )<?xml version="1.0"?><configuration><appSettings><add key="TopLevelDomain" value="dev" /><add key="UserAgent" value="HuddleDesktopPC" />:</appSettings><startup><supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.0" /></startup><> <defaultProxy> <proxy usesystemdefault="false" scriptLocation=” ” /> </defaultProxy></></configuration> ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download