Unpacking Software Livestream

Join our monthly Unpacking Software livestream to hear about the latest news, chat and opinion on packaging, software deployment and lifecycle management!

Learn More

Chocolatey Product Spotlight

Join the Chocolatey Team on our regular monthly stream where we put a spotlight on the most recent Chocolatey product releases. You'll have a chance to have your questions answered in a live Ask Me Anything format.

Learn More

Chocolatey Coding Livestream

Join us for the Chocolatey Coding Livestream, where members of our team dive into the heart of open source development by coding live on various Chocolatey projects. Tune in to witness real-time coding, ask questions, and gain insights into the world of package management. Don't miss this opportunity to engage with our team and contribute to the future of Chocolatey!

Learn More

Calling All Chocolatiers! Whipping Up Windows Automation with Chocolatey Central Management

Webinar from
Wednesday, 17 January 2024

We are delighted to announce the release of Chocolatey Central Management v0.12.0, featuring seamless Deployment Plan creation, time-saving duplications, insightful Group Details, an upgraded Dashboard, bug fixes, user interface polishing, and refined documentation. As an added bonus we'll have members of our Solutions Engineering team on-hand to dive into some interesting ways you can leverage the new features available!

Watch On-Demand
Chocolatey Community Coffee Break

Join the Chocolatey Team as we discuss all things Community, what we do, how you can get involved and answer your Chocolatey questions.

Watch The Replays
Chocolatey and Intune Overview

Webinar Replay from
Wednesday, 30 March 2022

At Chocolatey Software we strive for simple, and teaching others. Let us teach you just how simple it could be to keep your 3rd party applications updated across your devices, all with Intune!

Watch On-Demand
Chocolatey For Business. In Azure. In One Click.

Livestream from
Thursday, 9 June 2022

Join James and Josh to show you how you can get the Chocolatey For Business recommended infrastructure and workflow, created, in Azure, in around 20 minutes.

Watch On-Demand
The Future of Chocolatey CLI

Livestream from
Thursday, 04 August 2022

Join Paul and Gary to hear more about the plans for the Chocolatey CLI in the not so distant future. We'll talk about some cool new features, long term asks from Customers and Community and how you can get involved!

Watch On-Demand
Hacktoberfest Tuesdays 2022

Livestreams from
October 2022

For Hacktoberfest, Chocolatey ran a livestream every Tuesday! Re-watch Cory, James, Gary, and Rain as they share knowledge on how to contribute to open-source projects such as Chocolatey CLI.

Watch On-Demand

Downloads:

3,147

Downloads of v 0.2.7.29815:

1,172

Last Update:

25 Oct 2015

Package Maintainer(s):

Software Author(s):

  • Ryan Conrad

Tags:

powershell virtualmachine virtualbox internetexplorer ie vm machine testing

PSIEVM

  • 1
  • 2
  • 3

0.2.7.29815 | Updated: 25 Oct 2015

Downloads:

3,147

Downloads of v 0.2.7.29815:

1,172

Maintainer(s):

Software Author(s):

  • Ryan Conrad

PSIEVM 0.2.7.29815

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests


Validation Testing Passed


Verification Testing Passed

Details

Scan Testing Successful:

No detections found in any package files

Details
Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install PSIEVM, run the following command from the command line or from PowerShell:

>

To upgrade PSIEVM, run the following command from the command line or from PowerShell:

>

To uninstall PSIEVM, 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 psievm -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 psievm -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 psievm
  win_chocolatey:
    name: psievm
    version: '0.2.7.29815'
    source: INTERNAL REPO URL
    state: present

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


chocolatey_package 'psievm' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '0.2.7.29815'
end

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


cChocoPackageInstaller psievm
{
    Name     = "psievm"
    Version  = "0.2.7.29815"
    Source   = "INTERNAL REPO URL"
}

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


package { 'psievm':
  ensure   => '0.2.7.29815',
  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.

Package Approved

This package was approved by moderator ferventcoder on 16 Aug 2020.

Description

psievm is a powershell module for standing up an IE Virtual Machine in VirtualBox quickly and without hassle. This will do all the steps needed to get the VM running.


tools\chocolateyInstall.ps1
#requires -version 3

$name   = 'psievm'


function Invoke-DownloadFile {
	Param (
		[string]$Url,
		[string]$File
	);
	process {
		"Downloading $Url to $File" | Write-Host;
		$downloader = new-object System.Net.WebClient;
		$downloader.Proxy.Credentials=[System.Net.CredentialCache]::DefaultNetworkCredentials;
		$downloader.DownloadFile($Url, $File);
	}
}

function Install-PSIEVM {
	param (
		[Parameter(Mandatory=$true)]
		[string] $ModulesPath
	)
	begin {
		"Installing PSIEVM PowerShell module" | Write-Host;
		"Copyright (c) 2015 Ryan Conrad" | Write-Host;
		"License: https://github.com/camalot/psievm/blob/master/LICENSE.md" | Write-Host;
		$url = (Get-LatestGithubRelease -Owner camalot -Repo psievm);

		$tempDir = (Join-Path $env:TEMP "psievm");
		if(!(Test-Path -Path $tempDir)) {
			New-Item -Path $tempDir -ItemType Directory | Out-Null;
		}

		$file = (Join-Path $tempDir "psievm.zip");
		$psievmModulePath = (Join-Path $ModulesPath "psievm");

		if(!(Test-Path -Path $psievmModulePath)) {
			New-Item -Path $psievmModulePath -ItemType Directory | Out-Null;
		}
	}
	process {
		# download the package
		Invoke-DownloadFile -url $url -file $file;

		# download 7zip
		"Download 7Zip commandline tool" | Write-Host;
		$7zaExe = (Join-Path $tempDir '7za.exe');
		Invoke-DownloadFile -url 'https://raw.githubusercontent.com/camalot/psievm/master/psievm/.tools/7za.exe' -file "$7zaExe";

		# unzip the package
		"Extracting $file to $ModulesPath" | Write-Host;
		Start-Process "$7zaExe" -ArgumentList "x -o`"$ModulesPath`" -y `"$file`"" -Wait -NoNewWindow;
		"Unblock module files on the system" | Write-Host;
		Get-ChildItem -Path "$psievmModulePath" -File -Recurse | Unblock-File | Out-Null;
	}
	end {
		if(Test-Path -Path $tempDir) {
			"Clean up temp directory [$tempDir]" | Write-Host;
			Remove-Item -Path $tempDir -Force -Recurse | Out-Null;
		}
	}
}

function Get-LatestGithubRelease {
	<#
	.SYNOPSIS
	This gets the download URL for what ever is the latest release.
	#>
	Param(
		[string] $Owner,
		[string] $Repo
	);
	begin {
		$netAssembly = [Reflection.Assembly]::GetAssembly([System.Net.Configuration.SettingsSection])
		if($netAssembly) {
				$bindingFlags = [Reflection.BindingFlags] "Static,GetProperty,NonPublic";
				$settingsType = $netAssembly.GetType("System.Net.Configuration.SettingsSectionInternal");
				$instance = $settingsType.InvokeMember("Section", $bindingFlags, $null, $null, @());

				if($instance) {
						$bindingFlags = "NonPublic","Instance";
						$useUnsafeHeaderParsingField = $settingsType.GetField("useUnsafeHeaderParsing", $bindingFlags);
						if($useUnsafeHeaderParsingField) {
							$useUnsafeHeaderParsingField.SetValue($instance, $true);
						}
				}
		}
	}
	process {
		$webclient = New-Object -TypeName "net.webclient";
		"Getting latest release information from GitHub Repository $Owner/$Repo" | Write-Host;
		$webclient.Headers.Add("User-Agent", "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.52 Safari/537.36");
		$webclient.Headers.Add("Accept","text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8");
		$latest = ($webclient.DownloadString("https://api.github.com/repos/$Owner/$Repo/releases") | ConvertFrom-Json) | select -First 1;
		"Using release '$($latest.name)'" | Write-Host;
		$url = $latest.assets | select -ExpandProperty browser_download_url -First 1;
		return $url;
	}
}


# I hate that these are duplicated in both the install and uninstall
# but because the install is also used to invoke a non-chocolatey install
# via the iex web download, it cannot import an external file easily.
# So they will remain duplicated for now.
function Get-DocumentsModulePath {
	$docsPath = (Get-EnvironmentFolderPath -Name MyDocuments);
	if(-not $docsPath) {
		# if MyDocuments doesn't give anything, use the user profile
		return (Join-Path -Path $env:USERPROFILE -ChildPath "Documents\WindowsPowerShell\Modules\");
	} else {
		return (Join-Path -Path $docsPath -ChildPath "WindowsPowerShell\Modules\");
	}
}

function Get-EnvironmentFolderPath {
	Param (
		[Parameter(Mandatory=$true)]
		[string] $Name
	);

	return [Environment]::GetFolderPath($Name);
}

function Invoke-ShellCommand {
	param (
		[string[]] $CommandArgs
	)
	& cmd /c ($CommandArgs -join " ") *>&1 | Write-Host;
}

function Invoke-Setup {

	$params = ConvertFrom-StringData ($env:chocolateyPackageParameters -replace ';', "`n");
	$ModulesRoot = $params.PSModuleDirectory;

	if(-not $ModulesRoot) {
		$ModulesRoot = Get-DocumentsModulePath;
	}

	if($env:chocolateyPackageFolder) {
		$ModuleTarget = (Join-Path $env:chocolateyPackageFolder "Modules");
		$PSIEVMModuleTarget = (Join-Path $ModuleTarget "psievm");
		$PSIEVMModuleRootPath = (Join-Path $ModulesRoot "psievm");

		Install-PSIEVM -ModulesPath $ModuleTarget;

		if(Test-Path($PSIEVMModuleRootPath)) {
			"Delete $PSIEVMModuleRootPath" | Write-Host;
			# cmd is used because Remove-Item wont delete a junction
			Remove-Item -Path $PSIEVMModuleRootPath -Recurse -Force;
			Invoke-ShellCommand -CommandArgs "rmdir", "/S", "/Q", "`"$PSIEVMModuleRootPath`"";
			#cmd /c rmdir "$PSIEVMModuleRootPath";
		}

		"Creating junction: $PSIEVMModuleRootPath -> $PSIEVMModuleTarget" | Write-Host;
		Invoke-ShellCommand -CommandArgs "mklink", "/j", "`"$PSIEVMModuleRootPath`"", "`"$PSIEVMModuleTarget`"";
		#cmd /c mklink /j "$PSIEVMModuleRootPath" "$PSIEVMModuleTarget";
	} else {
		Install-PSIEVM -ModulesPath $ModulesRoot;
	}
}

if( ($DoSetup -eq $null) -or ($DoSetup -eq $true) ) {
	Invoke-Setup;
}
tools\chocolateyUninstall.ps1

# I hate that these are duplicated in both the install and uninstall
# but because the install is also used to invoke a non-chocolatey install
# via the iex web download, it cannot import an external file easily.
# So they will remain duplicated for now.
function Get-DocumentsModulePath {
	$docsPath = (Get-EnvironmentFolderPath -Name MyDocuments);
	if(-not $docsPath) {
		# if MyDocuments doesn't give anything, use the user profile
		return (Join-Path -Path $env:USERPROFILE -ChildPath "Documents\WindowsPowerShell\Modules\");
	} else {
		return (Join-Path -Path $docsPath -ChildPath "WindowsPowerShell\Modules\");
	}
}

function Get-EnvironmentFolderPath {
	Param (
		[Parameter(Mandatory=$true)]
		[string] $Name
	);

	return [Environment]::GetFolderPath($Name);
}

function Invoke-ShellCommand {
	param (
		[string[]] $CommandArgs
	)
	& cmd /c ($CommandArgs -join " ") *>&1 | Write-Host;
}

function Invoke-Uninstall {

	$params = ConvertFrom-StringData ($env:chocolateyPackageParameters -replace ';', "`n");
	$ModulesRoot = $params.PSModuleDirectory;

	if(-not $ModulesRoot) {
		$ModulesRoot = Get-DocumentsModulePath;
	}

	$PSIEVMModuleRootPath = (Join-Path $ModulesRoot "psievm");

	if($env:chocolateyPackageFolder) {
		$ModuleTarget = (Join-Path $env:chocolateyPackageFolder "Modules");
		if(Test-Path($ModuleTarget)) {
			"Delete $ModuleTarget" | Write-Host;
			Remove-Item -Path $ModuleTarget -Recurse -Force | Out-Null;
		}
	}

	if(Test-Path($PSIEVMModuleRootPath)) {
		"Delete $PSIEVMModuleRootPath" | Write-Host;
		# cmd is used because Remove-Item wont delete a junction
		Invoke-ShellCommand -CommandArgs "rmdir", "/S", "/Q", "`"$PSIEVMModuleRootPath`"";
	}

}


if( ($DoUninstall -eq $null) -or ($DoUninstall -eq $true) ) {
	Invoke-Uninstall;
}


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
PSIEVM 0.2.6.29815 398 Sunday, October 25, 2015 Approved
PSIEVM 0.2.4.29815 421 Sunday, October 25, 2015 Approved
PSIEVM 0.1.92.28915 367 Friday, October 16, 2015 Approved
PSIEVM 0.1.78.28415 398 Sunday, October 11, 2015 Approved
PSIEVM 0.1.44.28215 391 Friday, October 9, 2015 Approved

This package has no dependencies.

Discussion for the PSIEVM Package

Ground Rules:

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