Downloads:

695

Downloads of v 106.0.201.2:

695

Last Update:

29 Jan 2017

Package Maintainer(s):

Software Author(s):

  • OPC Foundation

Tags:

opc opcclassiccorecomponents admin

OPC Classic Core Components

106.0.201.2 | Updated: 29 Jan 2017

Downloads:

695

Downloads of v 106.0.201.2:

695

Maintainer(s):

Software Author(s):

  • OPC Foundation

OPC Classic Core Components 106.0.201.2

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

To install OPC Classic Core Components, run the following command from the command line or from PowerShell:

>

To upgrade OPC Classic Core Components, run the following command from the command line or from PowerShell:

>

To uninstall OPC Classic Core Components, 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 opc-components -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 opc-components -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 opc-components installed
  win_chocolatey:
    name: opc-components
    state: present
    version: 106.0.201.2
    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 'opc-components' do
  action    :install
  version  '106.0.201.2'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: opc-components,
    Version: 106.0.201.2,
    Source: STEP 3 URL
);

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


cChocoPackageInstaller opc-components
{
   Name     = 'opc-components'
   Ensure   = 'Present'
   Version  = '106.0.201.2'
   Source   = 'STEP 3 URL'
}

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


package { 'opc-components':
  provider => 'chocolatey',
  ensure   => '106.0.201.2',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install opc-components version="106.0.201.2" 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 03 Feb 2017.

Description

OPC Classic Core Components installer


tools\chocolateyinstall.ps1

$ErrorActionPreference = 'Stop';
# Check system architecture
if ([System.IntPtr]::Size -eq 4) { 
	# 32-bit
	$path = Join-Path "$(Split-Path -parent $MyInvocation.MyCommand.Definition)" 'opc-core-componentsx86.msi'
	echo "Installing as 32-bit"
} else { 
	# 64-bit
	$path = Join-Path "$(Split-Path -parent $MyInvocation.MyCommand.Definition)" 'opc-core-componentsx64.msi'
	echo "Installing as 64-bit"
}
$name= 'OpcClassicCoreComponents'
$silent = '/quiet'

echo $path

Install-ChocolateyPackage $name 'msi' $silent $path
 
tools\chocolateyuninstall.ps1


$ErrorActionPreference = 'Stop';

$packageName = 'OpcClassicCoreComponents'
$softwareName = 'OpcClassicCoreComponents*'
$installerType = 'MSI' 

$silentArgs = '/qn /norestart'
$validExitCodes = @(0, 3010, 1605, 1614, 1641)
if ($installerType -ne 'MSI') {
  $validExitCodes = @(0)
}

$uninstalled = $false
$local_key     = 'HKCU:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*'
$machine_key   = 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*'
$machine_key6432 = 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\*'

$key = Get-ItemProperty -Path @($machine_key6432,$machine_key, $local_key) `
                        -ErrorAction SilentlyContinue `
         | ? { $_.DisplayName -like "$softwareName" }

if ($key.Count -eq 1) {
  $key | % { 
    $file = "$($_.UninstallString)"

    if ($installerType -eq 'MSI') {
      $silentArgs = "$($_.PSChildName) $silentArgs"

      $file = ''
    }

    Uninstall-ChocolateyPackage -PackageName $packageName `
                                -FileType $installerType `
                                -SilentArgs "$silentArgs" `
                                -ValidExitCodes $validExitCodes `
                                -File "$file"
  }
} elseif ($key.Count -eq 0) {
  Write-Warning "$packageName has already been uninstalled by other means."
} elseif ($key.Count -gt 1) {
  Write-Warning "$key.Count matches found!"
  Write-Warning "To prevent accidental data loss, no programs will be uninstalled."
  Write-Warning "Please alert package maintainer the following keys were matched:"
  $key | % {Write-Warning "- $_.DisplayName"}
}



tools\opc-core-componentsx64.msi
md5: 125CD6D49D2D52B6276274B674DD0CBC | sha1: 6C82B645D800B390A55C5B547CF98F5EDA973373 | sha256: A0E34BC1DFD01CA53C0F4E56AD687FB273CFA1AE78AF8A3AEE3662E172149C89 | sha512: 63B7200FA5035A4BE200F1EE5044797DD6FA4D32771EDC6CEF9F62FED0615BD0860C4B2288FD3E5333EAFC1F037D37EB1786062D188D7651440D26CF6EC4F35B
tools\opc-core-componentsx86.msi
md5: 2D8CF58355B671CB312DB302B6B8E057 | sha1: FD29B77B75B049308E02EC814E4522A0172E62A5 | sha256: 2A36F10C0B0A561502DD565B4C59008A83905227FC320A74AB4E59BB53C110D3 | sha512: 600276C69C432820F34F59423514EE023371C2AFA1451EAC925DAECC28DFA14FF9B8C2B61DB799EEE1419737EB16779F34D632D831FFDA3FB7FD92F5F86B711C

Log in or click on link to see number of positives.

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

Initial release


This package has no dependencies.

Discussion for the OPC Classic Core Components Package

Ground Rules:

  • This discussion is only about OPC Classic Core Components and the OPC Classic Core Components 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 OPC Classic Core Components, 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