Downloads:

3,964

Downloads of v 2.12:

183

Last Update:

12/2/2017

Package Maintainer(s):

Software Author(s):

  • Nir Sofer

Tags:

browser history ie chrome firefox safari export

BrowsingHistoryView

This is not the latest version of BrowsingHistoryView available.

2.12 | Updated: 12/2/2017

Downloads:

3,964

Downloads of v 2.12:

183

Maintainer(s):

Software Author(s):

  • Nir Sofer

BrowsingHistoryView 2.12

This is not the latest version of BrowsingHistoryView available.

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

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

>

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

>

To uninstall BrowsingHistoryView, 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 browsinghistoryview -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 browsinghistoryview -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 browsinghistoryview installed
  win_chocolatey:
    name: browsinghistoryview
    state: present
    version: 2.12
    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 'browsinghistoryview' do
  action    :install
  version  '2.12'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: browsinghistoryview,
    Version: 2.12,
    Source: STEP 3 URL
);

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


cChocoPackageInstaller browsinghistoryview
{
   Name     = 'browsinghistoryview'
   Ensure   = 'Present'
   Version  = '2.12'
   Source   = 'STEP 3 URL'
}

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


package { 'browsinghistoryview':
  provider => 'chocolatey',
  ensure   => '2.12',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install browsinghistoryview version="2.12" 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/2/2017.

Description

BrowsingHistoryView is a utility that reads the history data of 4 different Web browsers (Internet Explorer, Mozilla Firefox, Google Chrome, and Safari) and displays the browsing history of all these Web browsers in one table.

The browsing history table includes the following information: Visited URL, Title, Visit Time, Visit Count, Web browser and User Profile.

BrowsingHistoryView allows you to watch the browsing history of all user profiles in a running system, as well as to get the browsing history from external hard drive.

You can also export the browsing history into csv/tab-delimited/html/xml file from the user interface, or from command-line, without displaying any user interface.


tools\chocolateyInstall.ps1
$packageName = 'browsinghistoryview'
$url = 'http://www.nirsoft.net/utils/browsinghistoryview.zip'
$checksum = 'dd46d5af61ed11e4229861bbb0af5a40dc24611f2a1b351046250d8591cc8c81'
$checksumType = 'sha256'
$url64 = 'http://www.nirsoft.net/utils/browsinghistoryview-x64.zip'
$checksum64 = '49c87435be291299238ab576b2aabcd7e4267e7b306a0feac81575e52ebd57da'
$checksumType64 = 'sha256'
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$installFile = Join-Path $toolsDir "$($packageName).exe"

Install-ChocolateyZipPackage -PackageName "$packageName" `
                             -Url "$url" `
                             -UnzipLocation "$toolsDir" `
                             -Url64bit "$url64" `
                             -Checksum "$checksum" `
                             -ChecksumType "$checksumType" `
                             -Checksum64 "$checksum64" `
                             -ChecksumType64 "$checksumType64"

Set-Content -Path ("$installFile.gui") `
            -Value $null

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
BrowsingHistoryView 2.20 84 Monday, June 24, 2019 Approved
BrowsingHistoryView 2.17 200 Thursday, August 2, 2018 Approved
BrowsingHistoryView 2.15 285 Saturday, December 16, 2017 Approved
BrowsingHistoryView 2.12 183 Saturday, December 2, 2017 Approved
BrowsingHistoryView 2.11 209 Monday, November 13, 2017 Approved
BrowsingHistoryView 2.10 277 Monday, August 7, 2017 Approved
BrowsingHistoryView 2.00 314 Wednesday, April 5, 2017 Approved
BrowsingHistoryView 1.95 300 Wednesday, February 8, 2017 Approved
BrowsingHistoryView 1.91 268 Wednesday, January 18, 2017 Approved

Package

  • Automatically built and uploaded by dtgm

This package has no dependencies.

Discussion for the BrowsingHistoryView Package

Ground Rules:

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