Downloads:

428

Downloads of v 2016.1803:

200

Last Update:

24 Sep 2018

Package Maintainer(s):

Software Author(s):

  • Bill Curran

Tags:

bcurran3 dependency osdependency server2016

Package Dependency on Windows Server 2016

2016.1803 | Updated: 24 Sep 2018

Downloads:

428

Downloads of v 2016.1803:

200

Maintainer(s):

Software Author(s):

  • Bill Curran

Package Dependency on Windows Server 2016 2016.1803

This Package Contains an Exempted Check

1 Test Passing and 1 Exempted Test


Validation Testing Passed


Verification Testing Exempt:

requires Windows Server 2016

To install Package Dependency on Windows Server 2016, run the following command from the command line or from PowerShell:

>

To upgrade Package Dependency on Windows Server 2016, run the following command from the command line or from PowerShell:

>

To uninstall Package Dependency on Windows Server 2016, 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 dependency-server2016 -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 dependency-server2016 -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 dependency-server2016 installed
  win_chocolatey:
    name: dependency-server2016
    state: present
    version: 2016.1803
    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 'dependency-server2016' do
  action    :install
  version  '2016.1803'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: dependency-server2016,
    Version: 2016.1803,
    Source: STEP 3 URL
);

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


cChocoPackageInstaller dependency-server2016
{
   Name     = 'dependency-server2016'
   Ensure   = 'Present'
   Version  = '2016.1803'
   Source   = 'STEP 3 URL'
}

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


package { 'dependency-server2016':
  provider => 'chocolatey',
  ensure   => '2016.1803',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install dependency-server2016 version="2016.1803" 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 gep13 on 25 Sep 2018.

Description

Package Dependency on Windows Server 2016 is a Chocolatey package for use as a dependency by package maintainers/creators. It is similar in concept to Chocolatey Fast Answers Extension to provide a (proposed) standard way for dealing with packages/programs that are OS version specific. This package will purposely fail (throw) when Windows Server 2016 is not found or an equal to or greater than version you specify.

Other OS specific dependencies can be found here.

EXAMPLE USE FOR MAINTAINERS/PACKAGERS:

Examples

Look at Version History for the builds you can specify as a minimum requirement for your package.

NOTE TO CHOCOLATEY MODERATORS:

Seeing dependency-server2016 listed as dependency on any package indicates the package has a requirement of Windows Server 2016. The package will fail automated testing because of this and require an exemption.

PACKAGE NOTES


Click here to Patreon-ize the package maintainer.



tools\ChocolateyInstall.ps1
$packageName    = 'dependency-server2016'

$IsWinServer=((Get-CimInstance Win32_OperatingSystem | Select-Object Caption) -match "Server")
if ($IsWinServer) {
  } else {
    Write-Warning "This package requires Windows Server 2016."
	throw
  }

$IsCorrectBuild=[Environment]::OSVersion.Version.Build
if ($IsCorrectBuild -lt "17134")
   {
    Write-Warning "This package requires at least Windows Server 2016 1803/OS build 17134.x."
    throw
   }

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
Package Dependency on Windows Server 2016 2016.1709 71 Monday, September 24, 2018 Approved
Package Dependency on Windows Server 2016 2016.1607 72 Monday, September 24, 2018 Approved
Package Dependency on Windows Server 2016 2016.0 85 Friday, September 21, 2018 Approved

This package has no dependencies.

Discussion for the Package Dependency on Windows Server 2016 Package

Ground Rules:

  • This discussion is only about Package Dependency on Windows Server 2016 and the Package Dependency on Windows Server 2016 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 Package Dependency on Windows Server 2016, 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