Downloads:

500

Downloads of v 1.2.2.15132:

500

Last Update:

7/4/2017

Package Maintainer(s):

Software Author(s):

  • RealVNC Limited

Tags:

vnc realvnc vncconnect vnc-connect remote control chrome extension

VNC® Viewer for Google Chrome™

1.2.2.15132 | Updated: 7/4/2017

Downloads:

500

Downloads of v 1.2.2.15132:

500

Maintainer(s):

Software Author(s):

  • RealVNC Limited

VNC® Viewer for Google Chrome™ 1.2.2.15132

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

To install VNC® Viewer for Google Chrome™, run the following command from the command line or from PowerShell:

>

To upgrade VNC® Viewer for Google Chrome™, run the following command from the command line or from PowerShell:

>

To uninstall VNC® Viewer for Google Chrome™, run the following command from the command line or from PowerShell:

>

NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://chocolatey.org/api/v2. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade vnc-viewer-chrome -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade vnc-viewer-chrome -y --source="'STEP 3 URL'" 
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode

- name: Ensure vnc-viewer-chrome installed
  win_chocolatey:
    name: vnc-viewer-chrome
    state: present
    version: 1.2.2.15132
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'vnc-viewer-chrome' do
  action    :install
  version  '1.2.2.15132'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: vnc-viewer-chrome,
    Version: 1.2.2.15132,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller vnc-viewer-chrome
{
   Name     = 'vnc-viewer-chrome'
   Ensure   = 'Present'
   Version  = '1.2.2.15132'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'vnc-viewer-chrome':
  provider => 'chocolatey',
  ensure   => '1.2.2.15132',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install vnc-viewer-chrome version="1.2.2.15132" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved by moderator flcdrg on 7/7/2017.

Description

Connects to your computers anywhere in the world and lets you take control.

VNC® Viewer is the only remote access app you’ll need. Why? Because…

  • It’s from RealVNC®, the inventors of VNC remote access and control technology.
  • We’ve 20 years’ experience making the remote control experience as good as it gets.
  • There’s no limit to the number of computers you can access, nor how long you can connect in for.
  • We support the widest range of platforms in the business: www.realvnc.com/products/vnc/tech-specs/#platforms
  • It’s free to use whether you’re connecting locally or over the Internet (and you won’t see an advert, either).

SOCIAL MEDIA:
Facebook | Twitter | Linkedin | YouTube

VNC SERVER SOFTWARE:
VNC Connect

OTHER VNC CLIENT SOFTARE:
Windows Client | Android App | iOS App | macOS Client | Linux Client

PACKAGING NOTE: This installs no software. It installs a registry key for the extension that Chrome will see and then ask you for permission to enable the extension if you are in Chrome or on the next run. Chrome will install the latest version of the extension. The mentioned version is the version at time of packaging, you can ignore it. Chrome will handle updates to the extension.


tools\ChocolateyInstall.ps1
$bits = Get-ProcessorBits
$packageName = 'vnc-viewer-chrome'
$extensionID = 'iabmpiboiopbgfabjmgeedhcmjenhbla'
if ($bits -eq 64)
   {
    if (Test-Path -Path "HKLM:\SOFTWARE\Wow6432node\Google\Chrome\Extensions\$extensionID")
       {
       Write-Host "Extension already installed." -foreground "magenta" –backgroundcolor "blue"
       } else {
         New-Item -Force -Path "HKLM:\SOFTWARE\Wow6432node\Google\Chrome\Extensions\$extensionID" | out-null
         New-ItemProperty -Path "HKLM:\SOFTWARE\Wow6432node\Google\Chrome\Extensions\$extensionID\" -Name "update_url" -Value "https://clients2.google.com/service/update2/crx" | out-null
         New-ItemProperty -Path "HKLM:\SOFTWARE\Wow6432node\Google\Chrome\Extensions\$extensionID\" -Name "ChocolateyPackageName" -Value "$packageName" | out-null
         }
    } else {
      New-Item -Force -Path "HKLM:\SOFTWARE\Google\Chrome\Extensions\$extensionID" | out-null
      New-ItemProperty -Path "HKLM:\SOFTWARE\Google\Chrome\Extensions\$extensionID\" -Name "update_url" -Value "https://clients2.google.com/service/update2/crx" | out-null
      }
tools\ChocolateyUninstall.ps1
$bits = Get-ProcessorBits
$packageName = 'vnc-viewer-chrome'
$extensionID = 'iabmpiboiopbgfabjmgeedhcmjenhbla'

if ($bits -eq 64) {
    Remove-Item "HKLM:\SOFTWARE\Wow6432node\Google\Chrome\Extensions\$extensionID" -Force -ErrorAction SilentlyContinue | out-null
   }else{
    Remove-Item "HKLM:\SOFTWARE\Google\Chrome\Extensions\$extensionID" -Force -ErrorAction SilentlyContinue | out-null
}

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
Discussion for the VNC® Viewer for Google Chrome™ Package

Ground Rules:

  • This discussion is only about VNC® Viewer for Google Chrome™ and the VNC® Viewer for Google Chrome™ package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or VNC® Viewer for Google Chrome™, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus