Downloads:

2,244,500

Downloads of v 6.5.2:

1,690

Last Update:

12/6/2018

Package Maintainer(s):

Software Author(s):

  • Robert Palethorpe

Tags:

winlogbeat beat elastic admin

winlogbeat

This is not the latest version of winlogbeat available.

6.5.2 | Updated: 12/6/2018

Downloads:

2,244,500

Downloads of v 6.5.2:

1,690

Maintainer(s):

Software Author(s):

  • Robert Palethorpe

Tags:

winlogbeat beat elastic admin

winlogbeat 6.5.2

This is not the latest version of winlogbeat available.

All Checks are Passing

2 Passing Test

Validation Testing Passed

Verification Testing Passed

Details

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

>

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

>

To uninstall winlogbeat, 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 winlogbeat -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 winlogbeat -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 winlogbeat installed
  win_chocolatey:
    name: winlogbeat
    state: present
    version: 6.5.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 'winlogbeat' do
  action    :install
  version  '6.5.2'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: winlogbeat,
    Version: 6.5.2,
    Source: STEP 3 URL
);

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


cChocoPackageInstaller winlogbeat
{
   Name     = 'winlogbeat'
   Ensure   = 'Present'
   Version  = '6.5.2'
   Source   = 'STEP 3 URL'
}

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


package { 'winlogbeat':
  provider => 'chocolatey',
  ensure   => '6.5.2',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install winlogbeat version="6.5.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.

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

This package was approved as a trusted package on 12/6/2018.

Description

Contains the chocolatey package for winlogbeat

tools\chocolateybeforemodify.ps1 
Stop-Service winlogbeat
Start-Sleep -s 3
tools\chocolateyinstall.ps1 
$ErrorActionPreference = 'Stop';

$packageName= 'winlogbeat'

$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$url        = 'https://artifacts.elastic.co/downloads/beats/winlogbeat/winlogbeat-6.5.2-windows-x86.zip'
$url64      = 'https://artifacts.elastic.co/downloads/beats/winlogbeat/winlogbeat-6.5.2-windows-x86_64.zip'

$installationPath = $toolsDir

# Chocolatey seems to copy the old lib folder in case of upgrade. Uninstall first.
$zipContentGlob=dir "$($installationPath)/.." "winlogbeat-*.zip.txt"
$zipContentFile=$zipContentGlob.Name
$folder = ($zipContentFile -replace ".zip.txt","") + "\\"
if (($zipContentGlob -ne $null)) {
    $zipContentFile
    $zipContents=(get-content $zipContentGlob.FullName) -split [environment]::NewLine
    for ($i = $zipContents.Length; $i -gt 0; $i--) {
        $fileInZip = $zipContents[$i]
        if ($fileInZip -ne $null -and $fileInZip.Trim() -ne '') {
            $fileToRemove = $fileInZip -replace $folder,""
            Remove-Item -Path "$fileToRemove" -ErrorAction SilentlyContinue -Recurse -Force
        }
    }
    Remove-Item -Path $zipContentGlob.FullName -ErrorAction SilentlyContinue -Recurse -Force
}

$folder = if(Get-ProcessorBits 64) { [io.path]::GetFileNameWithoutExtension($url64) } else { [io.path]::GetFileNameWithoutExtension($url) }

$packageArgs = @{
  packageName   = $packageName
  unzipLocation = $installationPath
  url           = $url
  url64bit      = $url64
  checksum      = '3499f14e29faf76d6d56a6617de617bc7a51d5629b531851b2d6e74dd99e2f02cc91cf943b4b1c28f180627dcfe142e33bfc4b26dca1d06b9228a3025c78532d'
  checksumType  = 'sha512'
  checksum64    = '3516b9831d7d08285819cb92351dded4ba5d19bcfea76b3597f6ccdc231aef30acc04941741709422d8bb12ab832ce0b2f533887bb765f46b58804879325a10e'
  checksumType64= 'sha512'
  specificFolder = $folder
}

Install-ChocolateyZipPackage @packageArgs

# Move everything from the subfolder to the main tools directory
$subFolder = Join-Path $installationPath (Get-ChildItem $installationPath $folder | ?{ $_.PSIsContainer })
Get-ChildItem $subFolder -Recurse | ?{$_.PSIsContainer } | Move-Item -Destination $installationPath
Get-ChildItem $subFolder | ?{$_.PSIsContainer -eq $false } | Move-Item -Destination $installationPath
Remove-Item "$subFolder"

Invoke-Expression $(Join-Path $installationPath "install-service-$($packageName).ps1")
tools\chocolateyuninstall.ps1 
$packageName= 'winlogbeat'
$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$uninstallScript = Join-Path $toolsDir "uninstall-service-winlogbeat.ps1"
Invoke-Expression $uninstallScript

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
winlogbeat 7.4.0 6422 Wednesday, October 2, 2019 Approved
winlogbeat 7.3.2 13755 Friday, September 13, 2019 Approved
winlogbeat 7.3.1 10029 Friday, August 23, 2019 Approved
winlogbeat 7.3.0 7897 Thursday, August 1, 2019 Approved
winlogbeat 7.2.1 498 Wednesday, July 31, 2019 Approved
winlogbeat 7.2.0.20190708 9289 Monday, July 8, 2019 Approved
winlogbeat 7.0.0 22763 Thursday, April 11, 2019 Approved
winlogbeat 6.7.1 5002 Friday, April 5, 2019 Approved
winlogbeat 6.7.0 4424 Wednesday, March 27, 2019 Approved

This package has no dependencies.

Discussion for the winlogbeat Package

Ground Rules:

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