Downloads:

925

Downloads of v 1.4:

925

Last Update:

10 Mar 2015

Package Maintainer(s):

Software Author(s):

  • Virtual Engine

Tags:

RES Automation Manager Workspace VirtualEngine Toolkit VET

Virtual Engine Toolkit

  • 1
  • 2
  • 3

1.4 | Updated: 10 Mar 2015

Downloads:

925

Downloads of v 1.4:

925

Maintainer(s):

Software Author(s):

  • Virtual Engine

  • 1
  • 2
  • 3
Virtual Engine Toolkit 1.4

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed


Validation Testing Unknown


Verification Testing Passed

Details

Scan Testing Resulted in Flagged:

This package was submitted (and approved) prior to automated virus scanning integration into the package moderation processs.

We recommend clicking the "Details" link to make your own decision on installing this package.

Details

Deployment Method: Individual Install, Upgrade, & Uninstall

To install Virtual Engine Toolkit, run the following command from the command line or from PowerShell:

>

To upgrade Virtual Engine Toolkit, run the following command from the command line or from PowerShell:

>

To uninstall Virtual Engine Toolkit, run the following command from the command line or from PowerShell:

>

Deployment Method:

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

1. Enter Your Internal Repository Url

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


2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • 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://community.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. Copy Your Script

choco upgrade vet -y --source="'INTERNAL REPO 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 vet -y --source="'INTERNAL REPO URL'" 
$exitCode = $LASTEXITCODE

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

Exit $exitCode

- name: Install vet
  win_chocolatey:
    name: vet
    version: '1.4'
    source: INTERNAL REPO URL
    state: present

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


chocolatey_package 'vet' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '1.4'
end

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


cChocoPackageInstaller vet
{
    Name     = "vet"
    Version  = "1.4"
    Source   = "INTERNAL REPO URL"
}

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


package { 'vet':
  ensure   => '1.4',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',
}

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


4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved by moderator ferventcoder on 01 May 2015.

Description

The Virtual Engine Toolkit (VET) is primarily a collection of tools for managing the various components of a user’s Workspace. No matter what your User Environment Management (UEM) tool of choice or desktop delivery mechanism, the Virtual Engine Toolkit can help.


tools\ChocolateyInstall.ps1
## Template VirtualEngine.Build ChocolateyInstall.ps1 file for bundled EXE/MSI installations
$packageToolsPath = Split-Path -Path $MyInvocation.MyCommand.Definition -Parent;
$packagePath = Split-Path -Path $packageToolsPath -Parent;
$bundleFilePath = Join-Path -Path $packagePath -ChildPath 'VET.MSI';
Install-ChocolateyInstallPackage -PackageName 'VET' -FileType 'MSI' -SilentArgs '/qn /norestart' -File $bundleFilePath -ValidExitCodes @(0,3010);
tools\ChocolateyUninstall.ps1
## Template VirtualEngine.Build ChocolateyUninstall.ps1 file for MSI installations
try {
    Get-WmiObject -Class Win32_Product | Where { $_.Name -eq 'Virtual Engine Toolkit' } | ForEach-Object {
	    Uninstall-ChocolateyPackage -PackageName 'VET' -FileType 'MSI' -SilentArgs "$($_.IdentifyingNumber) /qn /norestart" -ValidExitCodes @(0,3010); 
    }
}
catch {
    throw $_.Exception;
}
VET.MSI
 
VET.png
 

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.

Add to Builder Version Downloads Last Updated Status

This package has no dependencies.

Discussion for the Virtual Engine Toolkit Package

Ground Rules:

  • This discussion is only about Virtual Engine Toolkit and the Virtual Engine Toolkit 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 Virtual Engine Toolkit, 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