Downloads:

182,838

Downloads of v 3.1:

540

Last Update:

16 Feb 2016

Package Maintainer(s):

Software Author(s):

  • MikroTik

Tags:

winbox mikrotik network router routeros administration management

WinBox

This is not the latest version of WinBox available.

  • 1
  • 2
  • 3

3.1 | Updated: 16 Feb 2016

Downloads:

182,838

Downloads of v 3.1:

540

Maintainer(s):

Software Author(s):

  • MikroTik

  • 1
  • 2
  • 3
WinBox 3.1

This is not the latest version of WinBox available.

  • 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

Deployment Method: Individual Install, Upgrade, & Uninstall

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

>

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

>

To uninstall WinBox, 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 winbox -y --source="'INTERNAL REPO URL'" --version="'3.1'" [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 winbox -y --source="'INTERNAL REPO URL'" --version="'3.1'" 
$exitCode = $LASTEXITCODE

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

Exit $exitCode

- name: Install winbox
  win_chocolatey:
    name: winbox
    version: '3.1'
    source: INTERNAL REPO URL
    state: present

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


chocolatey_package 'winbox' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '3.1'
end

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


cChocoPackageInstaller winbox
{
    Name     = "winbox"
    Version  = "3.1"
    Source   = "INTERNAL REPO URL"
}

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


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

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package was approved by moderator ferventcoder on 18 Feb 2016.

Description

WinBox is a small utility that allows administration of Mikrotik RouterOS using a fast and simple GUI. It is a native Win32 binary, but can be run on Linux and Mac OSX using Wine.

All WinBox interface functions are as close as possible to Console functions. Some of advanced and system critical configurations are not possible from WinBox, like MAC address change on an interface.

Note: WinBox is obviously freeware, but no details about the license are available either on the application website or in the application itself.


tools\chocolateyInstall.ps1
$packageName = 'winbox'
$appName = 'WinBox'
$url = 'http://download2.mikrotik.com/routeros/winbox/3.1/winbox.exe'
$dir = $(Split-Path -parent $MyInvocation.MyCommand.Definition)
$exe = $packageName + '.exe'
$fullPath = Join-Path -Path $dir -ChildPath $exe
$checksum = '7670a4d4b07bc8597b0365a8c2f2c1584724e89e'
$checksumType = 'sha1'

$startFolder = $appName
$processName = 'winbox'

Function CreateStartMenuShortcut {
    $startMenuFolderPath = Join-Path -Path ([Environment]::GetFolderPath('Programs')) `
        -ChildPath $startFolder
    $startMenuFolder = New-Item $startMenuFolderPath -Type Directory `
        -ErrorAction SilentlyContinue
    If ($startMenuFolder) {
            Install-ChocolateyShortcut -shortcutFilePath `
                (Join-Path -Path $startMenuFolderPath -ChildPath ($appName + '.lnk')) `
                -targetPath $fullPath -workingDirectory $dir
    } Else {
        Write-Warning "Start menu folder couldn't be created."
    }
}

# SCRIPT STARTS HERE #

Stop-Process -Name $processName -ErrorAction SilentlyContinue

Get-ChocolateyWebFile -packageName $packageName -fileFullPath $fullPath -url $url -checksum $checksum -checksumType $checksumType

# create .gui file
New-Item -Path $dir -Name ($exe + '.gui') -ItemType file

CreateStartMenuShortcut

tools\chocolateyUninstall.ps1
$startFolder = 'WinBox'

Function RemoveStartMenuShortcut {
    $startMenuFolderPath = Join-Path -Path ([Environment]::GetFolderPath('Programs')) `
        -ChildPath $startFolder
    Remove-Item $startMenuFolderPath -Recurse -Force -Confirm:$FALSE -ErrorAction SilentlyContinue
}

# SCRIPT STARTS HERE #

Stop-Process -Name 'winbox' -ErrorAction SilentlyContinue
RemoveStartMenuShortcut

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
WinBox 3.30 1725 Sunday, September 12, 2021 Approved
WinBox 3.29 6309 Monday, August 23, 2021 Approved
WinBox 3.28 13881 Wednesday, June 9, 2021 Approved
WinBox 3.27 34676 Saturday, September 12, 2020 Approved
WinBox 3.24 10885 Monday, May 18, 2020 Approved
WinBox 3.23 994 Sunday, April 19, 2020 Approved
WinBox 3.22 1395 Sunday, March 15, 2020 Approved
WinBox 3.21 1116 Sunday, February 9, 2020 Approved
WinBox 3.20 10919 Saturday, October 19, 2019 Approved

This package has no dependencies.

Discussion for the WinBox Package

Ground Rules:

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