Requirements

• PowerShell 3.0 or later (the script uses Invoke-RestMethod).
• An Autotask REST API user with permission to read companies and contacts and to create client portal users.
• The Autotask REST API base URL for your zone, the API integration code, and the API username and secret, supplied as environment variables (see Parameters).
• Network access to the Autotask REST API.

Parameters

The script has no param block. It reads its settings from these environment variables, which must be set in the session before it runs.

Two values in the script are specific to the author's Autotask instance and must be adjusted before you run it: the companyCategoryID filter and Select-Object -Skip 3. See Notes.

Usage

Set the environment variables for the current session, then run the script. It lists the contacts it enables as it goes.

$env:at_uri = "<autotask-rest-url>"
$env:at_integrationcode = "<integration-code>"
$env:at_username = "<api-username>"
$env:at_secret = "<api-secret>"

.\Enable-AutotaskClientPortal.ps1

Script

<#
.SYNOPSIS
    Enables the simple client portal for every active Autotask contact that does not have it yet.
.DESCRIPTION
    Queries Autotask companies (filtered by company category), then the active
    contacts of each company, and compares them with the existing client portal
    users. For every contact without a client portal user it creates one, with
    the contact's e-mail address as the user name and a random 10-character
    password. Settings are read from environment variables, not parameters.
.PARAMETER at_uri
    Environment variable. Base URL of your Autotask REST API zone, without /v1.0.
.PARAMETER at_integrationcode
    Environment variable. API integration code (sent as the ApiIntegrationcode header).
.PARAMETER at_username
    Environment variable. Autotask API user name.
.PARAMETER at_secret
    Environment variable. Secret for the Autotask API user.
.EXAMPLE
    $env:at_uri = "<autotask-rest-url>"
    $env:at_integrationcode = "<integration-code>"
    $env:at_username = "<api-username>"
    $env:at_secret = "<api-secret>"
    .\Enable-AutotaskClientPortal.ps1
.NOTES
    Author  : Thomas Lasswell (https://www.techcolumnist.com)
    Version : 1.0 (2022-10-12)
    Requires: PowerShell 3.0 or later, Autotask REST API user
    Adjust  : Select-Object -Skip 3 skips the first three companies returned and
              companyCategoryID 101 is a category ID from the author's Autotask
              instance. Change or remove both before running.
    Limit   : Only companies with 500 or fewer contacts are handled.
#>
function New-SecurePassword {
    $Password = "!?@#$%^&*0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ_abcdefghijklmnopqrstuvwxyz".ToCharArray()
    ($Password | Get-Random -Count 10) -join ''
}

$at_uri = $($env:at_uri)
$at_integrationcode = $($env:at_integrationcode)
$at_username = $($env:at_username)
$at_secret = $($env:at_secret)

# Autotask headers.
$headers = New-Object "System.Collections.Generic.Dictionary[[String],[String]]"
$headers.Add("ApiIntegrationcode", "$at_integrationcode")
$headers.Add("Content-Type", 'application/json')
$headers.Add("UserName", "$at_username")
$headers.Add("Secret", "$at_secret")

# Get the companies to process.
$companies = $(Invoke-RestMethod -Uri $($at_uri + '/v1.0/Companies/query?search={"IncludeFields": ["id", "companyName","companyNumber","isActive"],"filter":[{"op":"eq","field":"companyCategoryID","value":"101"}]}') -Headers $headers -Method Get).items

foreach ($company in $companies | Select-Object -Skip 3) {
    # Get the active contacts of the company.
    $contacts = $(Invoke-RestMethod -Uri $($at_uri + '/v1.0/Contacts/query?search={"IncludeFields": ["id", "firstName","lastName","isActive","emailAddress"],"filter":[{"op":"and","items":[{"op":"eq","field":"companyID","value":"' + $($company.id) + '"},{"op":"eq","field":"isActive","value":"true"}]}]}') -Headers $headers -Method Get).items
    $query = $null
    $x = 0
    $y = 0
    $clientportal = @()

    # Get the existing client portal users, 100 contacts per query.
    do {
        foreach ($contact in $contacts) {
            if ($query) {
                $query += ',{"op":"eq","field":"contactID","value":"' + $($contact.id) + '"}'
            }
            if (!$query) {
                $query = '{"op":"eq","field":"contactID","value":"' + $($contact.id) + '"}'
            }
            $y++
            $x++
            if ($x -eq $contacts.Count) {
                $y = 100
            }
            if ($y -eq 100) {
                $postbody = '{"filter":[{"op":"or","items":[' + $query + ']}]}'
                $clientportal += $(Invoke-RestMethod -Uri $($at_uri + '/v1.0/ClientPortalUsers/query') -Body $postbody -Headers $headers -Method Post).items
                $query = $null
                $y = 0
            }
        }
    }
    while ($x -lt $contacts.Count)

    # Create client portal users for the contacts that are missing one.
    if ($clientportal.Count -ne $contacts.Count) {
        Write-Host "Contacts: $($contacts.Count)"
        Write-Host "Enabled: $($clientportal.Count)"
        $missing = $null
        $missing = $contacts.id | Where-Object { $_ -notin $clientportal.contactId }
        foreach ($miss in $missing) {
            $contact = $null
            $contact = $contacts | Where-Object { $miss -eq $_.id }
            Write-Host "$($contact.emailAddress)"
            $json = [PSObject]@{
                contactID            = $($contact.id)
                userName             = "$($contact.emailAddress)"
                securityLevel        = 1
                password             = "$(New-SecurePassword)"
                numberFormat         = 22
                dateFormat           = 1
                timeFormat           = 1
                isClientPortalActive = $true
            }
            $json = $json | ConvertTo-Json
            Start-Sleep -Milliseconds 10
            Invoke-RestMethod -Uri $($at_uri + '/v1.0/ClientPortalUsers') -Method POST -Body $json -Headers $headers
        }
    }
}

Notes

• There are a few places you might want to update. I use a filter for a specific customer category, so where your $companies variable is, you may want to change or remove this part of the query:

  {"op":"eq","field":"companyCategoryID","value":"101"}
  

• Category 101 and the Select-Object -Skip 3 (which skips the first three companies returned) are specific to my Autotask instance. Adjust or remove both for yours.
• The script currently only handles companies with 500 or fewer contacts. I’ll update it with a loop to get all the contacts as well.

Requirements

• An Exchange Online PowerShell session, for example from the ExchangeOnlineManagement module with Connect-ExchangeOnline.
• Permission to run Get-Mailbox and Get-MailboxStatistics against every mailbox you want to check.

Parameters

The command has no parameters. The one value you change is the size threshold.

Walkthrough

Here is a breakdown of the code, one stage of the pipeline at a time.

Get-Mailbox

Get-Mailbox gets all the mailboxes available, there’s no search filter on this one.

Get-Mailbox -ResultSize Unlimited

Select-Object for Identity

The Select-Object statement is used for doing a select expression where we can transform the Identity parameter that is being used as pipeline input for the Get-MailboxStatistics. I did this mainly because we have duplicate display names and differing email addresses in this specific tenant.

| Select-Object @{ Name = 'Identity'; Expression = { $_.PrimarySmtpAddress } }

Get-MailboxStatistics

Get-MailboxStatistics accept pipeline input of the default variable Identity. By doing the select statement above, we’re now using -Identity via the pipeline using the primary SMTP email address. This command outputs the data about a mailbox.

| Get-MailboxStatistics

Select-Object for TotalItemSize

This next select statement gives us the TotalItemSize formatted for use with comparison.

| Select-Object DisplayName, @{ Name = "TotalItemSize"; Expression = { [math]::Round($($_.TotalItemSize.Value.ToString().Replace(",", "").Split("(")[1].Split(" bytes")[0]) / 1GB, 2) } }

This part of the select statement is broken down as follows:

The first part is the beginning of a select expression, the { after Expression = is the start of the expression that will now become TotalItemSize.

@{ Name = "TotalItemSize"; Expression = {} }

Next up, we have the [math] function, we use this because by doing the simple math, we’d have a large amount of decimal places, so we round it.

[math]::Round()

Inside the () for the Round, we have this expression

$($_.TotalItemSize.Value.ToString().Replace(",", "").Split("(")[1].Split(" bytes")[0]) / 1GB

The TotalItemSize is modified to become a string

$_.TotalItemSize.Value.ToString()

then we replace the commas in the string

.Replace(",", "")

split it at the first ( and grab the second part of the array

.Split("(")[1]

then split again at bytes and grab the first part of that array

.Split(" bytes")[0]

Finally we finish the Round() statement with a ,2 which gives us 2 decimal places rounded.

Where-Object

The next pipeline sets the Where-Object and we’re only concerned about mailboxes over 45 GB in this example. You can change this to whatever you’d like to filter based on.

| Where-Object { $_.TotalItemSize -gt 45 }

Format-Table

The last stage, Format-Table -AutoSize, prints the result as a table sized to fit its content.

| Format-Table -AutoSize

Usage

Connect to Exchange Online, then run the command from the Script section below.

Connect-ExchangeOnline

It prints each mailbox over the threshold with its display name and size in GB.

DisplayName    TotalItemSize
-----------    -------------
<display-name>         52.31

To list mailboxes over 100 GB instead, change the 45 in the Where-Object stage.

| Where-Object { $_.TotalItemSize -gt 100 }

Script

The full command, expanded across lines. Each line ends with a pipe so it can be pasted straight into an Exchange Online session.

<#
.SYNOPSIS
    Lists Exchange Online mailboxes larger than a size threshold.
.DESCRIPTION
    Gets all mailboxes, passes each primary SMTP address to Get-MailboxStatistics (so
    duplicate display names do not matter), converts TotalItemSize to GB and keeps the
    mailboxes over 45 GB.
.EXAMPLE
    .\Get-MailboxOverSize.ps1
.NOTES
    Author  : Thomas Lasswell (https://www.techcolumnist.com)
    Version : 1.0 (2021-02-18)
    Requires: Exchange Online PowerShell session; permission to run Get-Mailbox and Get-MailboxStatistics
#>

Get-Mailbox -ResultSize Unlimited |
    Select-Object @{ Name = 'Identity'; Expression = { $_.PrimarySmtpAddress } } |
    Get-MailboxStatistics |
    Select-Object DisplayName, @{
        Name       = "TotalItemSize"
        Expression = {
            [math]::Round($($_.TotalItemSize.Value.ToString().Replace(",", "").Split("(")[1].Split(" bytes")[0]) / 1GB, 2)
        }
    } |
    Where-Object { $_.TotalItemSize -gt 45 } |
    Format-Table -AutoSize

Phew, this one took a minute to figure out. ConnectWise has a form based documents API (technically not really API, but it’s the way you get yourself a document into a CW ticket). First is the really amazing documentation that CW provides around the documents API

Second is then working with PowerShell to handle streamed encoding correctly, build a multipart form data payload, and then getting it to actually send the correct thing. Ultimately there were some good learning steps here. Mainly on how to construct a proper content type of “multipart/form-data”. I’m writing this in hopes that many of you that are out there that are facing a similar challenge on getting documents to upload into CW via PowerShell aren’t faced with the same 2 day challenge I just had.

Requirements

• PowerShell 5.1 or later, with Invoke-RestMethod.
• A ConnectWise API member with its public key, private key and your company identifier. Creating one is covered in Query Contacts by Email Address. The member's security role must be allowed to add documents to the record you upload to.
• Outbound HTTPS to the ConnectWise documents endpoint on na.myconnectwise.net. Use the regular host here, not the api- one.
• The file to upload, readable from the machine running the script, and the ID of the record (for example a ticket) it should be attached to.

Parameters

The script has no parameters. Edit these values in it before running.

Walkthrough

Encoding Issues

Mainly the Encoding Issues were around reading a file into PowerShell and then using Invoke-RestMethod to send it off. Typically you’d work in UTF-8, while that’s great in PS when working, sending that encoding via the Invoke-RestMethod seems to break things a little and none of the characters are correct, thus resulting in a data stream sent to your destination being garbled.

Left – Proper Data | Right – Garbled Data

I happened to stumble, and by stumble, I’ve been searching the Google masters for quite a while trying to understand why the encoding wasn’t working correctly, upon this article:

https://social.technet.microsoft.com/Forums/en-US/26f6a32e-e0e0-48f8-b777-06c331883555/invokewebrequest-encoding?forum=winserverpowershell

which nicely pointed me here:

https://windowsserver.uservoice.com/forums/301869-powershell/suggestions/13685217-invoke-restmethod-and-invoke-webrequest-encoding-b

Taking from this, I modified the following from:

$fileEnc = [System.Text.Encoding]::GetEncoding('UTF-8').GetString($fileBytes)

To using the ISO 8859-1 encoding type of 28591. Converting this line to:

$fileEnc = [System.Text.Encoding]::GetEncoding(28591).GetString($fileBytes)

Multipart boundaries

The rest of the time was learning to deal with boundaries in a multipart/form-data payload. Essentially finding this article:

https://gist.github.com/weipah/19bfdb14aab253e3f109

This taught me a bit about the boundaries that need to be set and more-so having to use `r`n in different places, you’ll see this referenced the same way as in the link in my script below using the $LF variable.

Usage

Edit the values listed above, save the script as Add-CWDocument.ps1 and run it from a PowerShell prompt.

.\Add-CWDocument.ps1

Invoke-RestMethod prints whatever the CW documents API returns for the upload. To attach to a different record, change recordType and recordId in $bodyLines.

Script

Enjoy, here’s the full code layout:

<#
.SYNOPSIS
    Uploads a file to a ConnectWise record (for example a ticket) through the Documents API.
.DESCRIPTION
    Reads the file at $FilePath, re-encodes its bytes as ISO 8859-1 (code page 28591) so
    Invoke-RestMethod does not garble them, builds a multipart/form-data body by hand
    (recordType, recordId, Title and the file) and posts it to the ConnectWise
    system/documents endpoint using an API member's keys.
.EXAMPLE
    .\Add-CWDocument.ps1
.NOTES
    Author  : Thomas Lasswell (https://www.techcolumnist.com)
    Version : 1.1 (2026-09-20)
    History : 1.0 2019-01-09 Initial version.
              1.1 2026-09-20 The uploaded file name now comes from $FilePath.
    Requires: PowerShell 5.1 or later; ConnectWise API member with permission to add documents
.LINK
    https://gist.github.com/weipah/19bfdb14aab253e3f109
#>

# Initializations
$global:CWcompany    = "<company-id>"
$global:CWprivate    = "<private-key>"
$global:CWpublic     = "<public-key>"
# Don't use the api- URL here for the server.
$global:CWserver     = "https://na.myconnectwise.net/v4_6_release/apis/3.0/system/documents"

# CW auth string
[string]$Authstring  = $CWcompany + '+' + $CWpublic + ':' + $CWprivate
$encodedAuth         = [Convert]::ToBase64String([Text.Encoding]::ASCII.GetBytes(($Authstring)))

# CW headers
$headers = New-Object "System.Collections.Generic.Dictionary[[String],[String]]"
$headers.Add("Authorization", "Basic $encodedAuth")

# Read the file and build the multipart body
$FilePath = 'C:\path\to\file.jpg'
$fileName = [System.IO.Path]::GetFileName($FilePath)
$fileBytes = [System.IO.File]::ReadAllBytes($FilePath)
$fileEnc = [System.Text.Encoding]::GetEncoding(28591).GetString($fileBytes)
$boundary = [System.Guid]::NewGuid().ToString()
$LF = "`r`n"

$bodyLines = (
    "--$boundary",
    "Content-Disposition: form-data; name=`"recordType`"$LF",
    "Ticket",
    "--$boundary",
    "Content-Disposition: form-data; name=`"recordId`"$LF",
    "<record-id>",
    "--$boundary",
    "Content-Disposition: form-data; name=`"Title`"$LF",
    "<document-title>",
    "--$boundary",
    "Content-Disposition: form-data; name=`"file`"; filename=`"$fileName`"",
    "Content-Type: application/octet-stream$LF",
    $fileEnc,
    "--$boundary--$LF"
) -join $LF

# Upload
Invoke-RestMethod -Uri $CWserver -Method Post -ContentType "multipart/form-data; boundary=`"$boundary`"" -Body $bodyLines -Headers $headers

Notes

• Update 2026-09-20 (v1.1): the file name in the multipart body was hard-coded as image001.jpg, so every upload was named that way whatever $FilePath pointed at. It is now taken from $FilePath.

I’ve found myself at a new job, recreating many of the processes that I spent the last few years putting together, tweaking, modifying, building a new managed services provider with an exciting new company. One of those challenges lead me to Email parsing and ConnectWise (CW). Previously I had the opportunity to use Autotask and email2ticket, however with the modifications to the API that CW did a few years ago, email2ticket is no longer supported for CW. With my found love of Azure Functions and looking at existing mail based parsing tools (https://mailparser.io/, https://www.thinkautomation.com/) which have amazing feature sets, they didn’t do quite what I was looking for and to replace the functionality that I once had with email2ticket.

That is leading me to this PowerShell series for how to utilize the CW REST API and the things that took some understanding and digging in a little to determine how to do simple queries. The CW developer portal has some great resources, and I stumbled upon the forums that ultimately made it possible to finally build a wildcard query via PowerShell to identify whether a contact exists in CW.

Requirements

• PowerShell 5.1 or later, with Invoke-RestMethod.
• A CW API Access Account (an API member on the Members tab) with its public key, private key and your company identifier. First things first, you have to authenticate to the CW REST API, and you need access to the Admin Setup tables to create the account. The member's security role must be able to read contacts.
• An Azure Functions PowerShell function with an HTTP trigger binding. The script reads the email query string parameter from $req_query_email and writes its JSON response to the output binding file path in $res.
• Outbound HTTPS from the function to your CW API host (api-na.myconnectwise.net for the North America cloud).

CW Members Tab – API Members

Parameters

Walkthrough

Once you have an integration setup you can proceed with creating a PowerShell script to handle the automation. I build in Azure Functions mostly, so there will be some pieces in here that relate to that, I’ll breakdown each section (and eventually move some of these pieces to linked articles).

Authentication

Authentication to the CW rest API is fairly simple. It requires your public and private keys and your company identifier.

First set your variables for your credentials.

$global:CWcompany    = "<company-id>"
$global:CWprivate    = "<private-key>"
$global:CWpublic     = "<public-key>"
$global:CWserver     = "https://api-na.myconnectwise.net"

Second configure the authentication string and setup the standard headers for your GET request.

[string]$Accept      = "application/vnd.connectwise.com+json; version=3.0"
[string]$ContentType = 'application/json'
[string]$Authstring  = $CWcompany + '+' + $CWpublic + ':' + $CWprivate
$encodedAuth         = [Convert]::ToBase64String([Text.Encoding]::ASCII.GetBytes(($Authstring)))

$headers = New-Object "System.Collections.Generic.Dictionary[[String],[String]]"
$headers.Add("Authorization", "Basic $encodedAuth")
$headers.Add("Content-Type", 'application/json')
$headers.Add("Accept", $Accept)

Request URI

Then for the URI, this consists of a few parts, your base URL, your query parameters, and your target for your request.

Query String – this is the conditions you’re going to pass to do the lookup. In this case I’m looking for the email address of a contact. This requires the use of CW’s childconditions parameters. Initially the communicationItems is used to determine the value of the email address, then forcing it to only look for the type of email address to speed the query result. The “%” is used as the wildcard for the “like” operator. I spent some time trying to determine what would work best, contains and in both resulted in invalid syntax so using the like operator was the eventual conclusion.

[string]$query       = '?childconditions=communicationItems/value like "%' + $email + '%" AND communicationItems/communicationType="Email"'

Putting it all together, you have a target of /company/contacts and use the query string. $email is the full or partial email address you’re searching for. Benefits of using a partial, such as @xyz.corp, would yield all contacts for that domain and you can use some logic there to determine what company they belong to (more to come on that subject).

[string]$TargetUri   = '/company/contacts'
[string]$query       = '?childconditions=communicationItems/value like "%' + $email + '%" AND communicationItems/communicationType="Email"'
[string]$BaseUri     = "$CWserver" + "/v4_6_release/apis/3.0" + $TargetUri + $query

Sending the request

Finally, send the Invoke-RestMethod command to get the results. This returns a JSON table that Invoke-RestMethod converts to a PS Object.

$JSONResponse = Invoke-RestMethod -Uri $BaseUri -Headers $headers -ContentType $ContentType -Method Get

Usage

Once the function is deployed, request it with the full or partial email address in the query string.

https://<function-app>.azurewebsites.net/api/<function-name>?email=<email>

The same call from PowerShell:

Invoke-RestMethod -Uri "https://<function-app>.azurewebsites.net/api/<function-name>?email=<email>" -Method Get

If the function's authorization level is not anonymous, add &code=<function-key> to the URL. A matching contact comes back in this shape:

{
    "id":  1234,
    "firstName":  "<first-name>",
    "lastName":  "<last-name>",
    "emails":  "<email>;",
    "company":  "<company-name>",
    "companyid":  56,
    "companyidentifier":  "<company-identifier>"
}

If nothing matches, the script returns $false and writes nothing to $res.

Script

Here’s the full code that I’m using to query for a specific contact’s email address.

<#
.SYNOPSIS
    Queries ConnectWise for contacts by full or partial email address.
.DESCRIPTION
    Runs as an Azure Functions PowerShell HTTP trigger. Reads the email address from the
    query string ($req_query_email), authenticates to the ConnectWise REST API with an API
    member's keys, searches /company/contacts with a wildcard "like" condition on the
    contact's email communication items, and writes the matching contacts (id, name,
    emails and company details) as JSON to the output binding file path in $res.
.PARAMETER email
    Full or partial email address to search for. Passed in the query string and read from $req_query_email.
.EXAMPLE
    Invoke-RestMethod -Uri "https://<function-app>.azurewebsites.net/api/<function-name>?email=<email>" -Method Get
.NOTES
    Author  : Thomas Lasswell (https://www.techcolumnist.com)
    Version : 1.1 (2026-09-20)
    History : 1.0 2018-12-27 Initial version.
              1.1 2026-09-20 The Accept header value no longer includes an "Accept: " prefix.
    Requires: PowerShell 5.1 or later; Azure Functions HTTP trigger ($req_query_email, $res); ConnectWise API member
.LINK
    https://developer.connectwise.com/products/manage/rest?a=Company&e=Contacts&o=GET
#>

# GET method: each querystring parameter is its own variable
if ($req_query_email) {
    $email = $req_query_email
}

# Initializations
$global:CWcompany    = "<company-id>"
$global:CWprivate    = "<private-key>"
$global:CWpublic     = "<public-key>"
$global:CWserver     = "https://api-na.myconnectwise.net"

# CW auth string
[string]$Accept      = "application/vnd.connectwise.com+json; version=3.0"
[string]$Authstring  = $CWcompany + '+' + $CWpublic + ':' + $CWprivate
[string]$ContentType = 'application/json'
$encodedAuth         = [Convert]::ToBase64String([Text.Encoding]::ASCII.GetBytes(($Authstring)))

# CW headers
$headers = New-Object "System.Collections.Generic.Dictionary[[String],[String]]"
$headers.Add("Authorization", "Basic $encodedAuth")
$headers.Add("Content-Type", 'application/json')
$headers.Add("Accept", $Accept)

# CW query
[string]$TargetUri   = '/company/contacts'
[string]$query       = '?childconditions=communicationItems/value like "%' + $email + '%" AND communicationItems/communicationType="Email"'
[string]$BaseUri     = "$CWserver" + "/v4_6_release/apis/3.0" + $TargetUri + $query

# Get response
$JSONResponse = Invoke-RestMethod -Uri $BaseUri -Headers $headers -ContentType $ContentType -Method Get

# Parse contact info to usable short table
$contactInfo = @()
foreach ($contact in $JSONResponse) {
    $email = $null
    $emails = $null
    $obj = New-Object PSObject
    $obj | Add-Member -MemberType NoteProperty -Name "id" -Value $contact.id
    $obj | Add-Member -MemberType NoteProperty -Name "firstName" -Value $contact.firstName
    $obj | Add-Member -MemberType NoteProperty -Name "lastName" -Value $contact.lastName
    foreach ($commtype in $contact.communicationItems) {
        $email = $($commtype | Where-Object { $_.communicationType -eq "Email" }).value
        if ($email.length -gt 2) {
            $emails += $email + ";"
        }
    }
    $obj | Add-Member -MemberType NoteProperty -Name "emails" -Value $emails
    $obj | Add-Member -MemberType NoteProperty -Name "company" -Value $contact.company.name
    $obj | Add-Member -MemberType NoteProperty -Name "companyid" -Value $contact.company.id
    $obj | Add-Member -MemberType NoteProperty -Name "companyidentifier" -Value $contact.company.identifier
    $contactInfo += $obj
}

if ($contactInfo) {
    Out-File -Encoding Ascii -FilePath $res -InputObject $($contactInfo | ConvertTo-Json)
} else {
    return $false
}

Notes

• Update 2026-09-20 (v1.1): $Accept used to be "Accept: application/vnd.connectwise.com+json; version=3.0", which put a second Accept: inside the header value. It is now just the media type.

Requirements

• Windows PowerShell 3.0 or later (Invoke-RestMethod).
• A LogicMonitor user that is allowed to read the access (audit) logs.
• HTTPS access to <account>.logicmonitor.com.

Parameters

The script takes no parameters. Edit these values before running it.

Usage

Edit the variables at the top of the script, then run it.

.\Get-LogicMonitorAuditLog.ps1

To keep the result, redirect the output to a file.

.\Get-LogicMonitorAuditLog.ps1 | Out-File .\logicmonitor-audit.txt

Script

<#
.SYNOPSIS
    Downloads the LogicMonitor audit (access) log for the last hour through the REST API.
.DESCRIPTION
    Builds the start time as UTC epoch seconds, builds a Basic authentication
    header from the user name and password, and calls the /santaba/rest/setting/accesslogs endpoint of
    your LogicMonitor account. The events are returned with the username, local time and description
    fields and displayed.
.EXAMPLE
    .\Get-LogicMonitorAuditLog.ps1
.NOTES
    Author  : Thomas Lasswell (https://www.techcolumnist.com)
    Version : 1.1 (2026-09-20)
    History : 1.0 2016-02-22 Initial version.
              1.1 2026-09-20 Start time is computed in UTC instead of a fixed EST offset;
                  removed the unused end time.
    Requires: Windows PowerShell 3.0+ (Invoke-RestMethod), a LogicMonitor user with access log rights
#>
$user = "<username>"
$pass = "<password>"

# How many hours back to read the audit log.
$hours = 1

# Get the start time as UTC epoch seconds, rounded to not have decimals.
$epoch = New-Object DateTime 1970, 1, 1, 0, 0, 0, ([DateTimeKind]::Utc)
$epochStart = [math]::Round(((Get-Date).ToUniversalTime().AddHours(-$hours) - $epoch).TotalSeconds)

# Check the LogicMonitor documentation on filters.
$filter = "_all~update"
$fields = "username,happenedOnLocal,description"

# Build the URI for the access logs.
$uri = "https://<account>.logicmonitor.com/santaba/rest/setting/accesslogs?sort=-happenedOn&filter=$filter,happenedOn>:$epochStart&fields=$fields"

# Build the base64 authentication string for the header.
$base64AuthInfo = [Convert]::ToBase64String([Text.Encoding]::ASCII.GetBytes(("{0}:{1}" -f $user, $pass)))

# Get the events.
$events = Invoke-RestMethod -Headers @{Authorization = ("Basic {0}" -f $base64AuthInfo)} -Uri $uri

# Display the events that were gathered.
$events

Notes

• Update 2026-09-20 (v1.1): the start time used to be the local time plus a hard-coded 4 hours (EST, and wrong during daylight saving), and an end time was calculated but never used. The start is now computed in UTC from $hours, so it works in any timezone.

Edit: Updated to give a more friendly output

Requirements

• Windows PowerShell 2.0 or later. New-WebServiceProxy is not available in PowerShell 6 and later.
• An Autotask user with API access (username and password).
• HTTPS access to the Autotask web services (webservices1.autotask.net and the zone URL that getZoneInfo returns).

Parameters

The script takes no parameters. Edit these values before running it.

Usage

Fill in the username and password, then run the script.

.\Get-AutotaskPicklistValues.ps1

For each field in the entity it prints the name, label and description, followed by the picklist values (Label, Value, IsActive). It ends with your API threshold and usage message.

To look at another entity, change the entity name in the getFieldInfo call.

$entity = $atws.getFieldInfo("Account")

Script

<#
.SYNOPSIS
    Lists the picklist values for an Autotask entity (Ticket by default) through the Autotask SOAP API.
.DESCRIPTION
    Connects to the Autotask web service with the given credentials, looks up the zone for the user
    and reconnects to the zone WSDL. It then calls getFieldInfo for the Ticket entity and prints each
    field with its picklist values, and finishes by printing the API threshold and usage message.
.EXAMPLE
    .\Get-AutotaskPicklistValues.ps1
.NOTES
    Author  : Thomas Lasswell (https://www.techcolumnist.com)
    Version : 1.0 (2015-02-06)
    Requires: Windows PowerShell 2.0+ (New-WebServiceProxy), an Autotask API user
#>
# Username and password for Autotask.
$ATurl = "https://webservices1.autotask.net/atservices/1.5/atws.wsdl"
$ATusername = "<autotask-username>"
$ATpassword = ConvertTo-SecureString "<autotask-password>" -AsPlainText -Force
$ATcredentials = New-Object System.Management.Automation.PSCredential($ATusername, $ATpassword)

# Look up the zone for this user and connect to it.
$atws = New-WebServiceProxy -Uri $ATurl -Credential $ATcredentials
$zoneInfo = $atws.getZoneInfo($ATusername)
$ATurl = $zoneInfo.URL.Replace(".asmx", ".wsdl")
$atws = New-WebServiceProxy -Uri $ATurl -Credential $ATcredentials

# Get the field information for the entity.
$entity = $atws.getFieldInfo("Ticket")

foreach ($picklist in $entity) {
    $picklist | Select-Object Name, Label, Description | Format-Table
    foreach ($values in $picklist.PicklistValues) {
        $values | Select-Object Label, Value, IsActive
    }
}

# Show the API threshold and usage information.
$output = $atws.getThresholdAndUsageInfo()
$output.EntityReturnInfoResults.message

Requirements

• PowerShell 2.0 or later.
• NetApp Data ONTAP PowerShell Toolkit 1.2 or later (the DataONTAP module). The script imports it if it is not already loaded and stops with an error if the version is older.
• NetApp 7-Mode controllers reachable over HTTPS.
• An account on each controller that can read volume, autosize and dedupe (SIS) information.

Parameters

The same credentials are used for every node in nodes.

Usage

Pass the controllers and account on the command line. You are prompted for the password.

& '.\NetApp-Gather Volume Information.ps1' -nodes "<filer-1>","<filer-2>" -username "<domain>\<username>" -IsVerbose

Or run the script with no parameters and answer the prompts.

& '.\NetApp-Gather Volume Information.ps1'

cmdlet NetApp-Gather Volume Information.ps1 at command pipeline position 1
Supply values for the following parameters:
nodes[0]: <filer-1>
nodes[1]: <filer-2>
nodes[2]:
username: <domain>\<username>
password: *************

The results are written to GatherVolumeInformation_<timestamp>_Detail.csv in the same folder as the script.

Script

<#
.SYNOPSIS
    Gathers NetApp 7-Mode volume information, including dedupe schedule and autogrow settings.
.DESCRIPTION
    Connects to each node with the Data ONTAP PowerShell Toolkit and collects
    details for every online volume that is not read-only: aggregate, total
    size, used, available, dedupe (SIS) status and schedule, and autogrow
    status, maximum size and increment size. The results are written to
    GatherVolumeInformation_<timestamp>_Detail.csv in the script folder.
.PARAMETER nodes
    One or more controllers to connect to. When prompted, enter one per line and press Enter on an empty line to continue.
.PARAMETER username
    Account used to connect to every controller, for example <domain>\<username>.
.PARAMETER password
    Password for the account. Prompted for as a secure string when not supplied.
.PARAMETER IsVerbose
    Display the collected property table for each volume as it is gathered.
.EXAMPLE
    & '.\NetApp-Gather Volume Information.ps1' -nodes "<filer-1>","<filer-2>" -username "<domain>\<username>" -IsVerbose
.EXAMPLE
    & '.\NetApp-Gather Volume Information.ps1'

    cmdlet NetApp-Gather Volume Information.ps1 at command pipeline position 1
    Supply values for the following parameters:
    nodes[0]: <filer-1>
    nodes[1]: <filer-2>
    nodes[2]:
    username: <domain>\<username>
    password: *************
.NOTES
    Author  : Thomas Lasswell (https://www.techcolumnist.com)
    Version : 1.1 (2026-09-20)
    Requires: Data ONTAP PowerShell Toolkit 1.2 or later, NetApp 7-Mode
    History : 1.0 2014-04-28 Initial version.
              1.1 2026-09-20 Fixed the timestamp in the CSV file name (it used minutes
                  where the month belongs) and the volume progress message.
#>
param (
    [Parameter(Mandatory = $true)]
    [Array]$nodes,
    [Parameter(Mandatory = $true)]
    [String]$username,
    [Parameter(Mandatory = $true, ParameterSetName = 'Secret')]
    [Security.SecureString]$password,
    [switch]$IsVerbose
)

# Create outfile information.
$exedir = Split-Path -Path $MyInvocation.MyCommand.Definition -Parent
$currentDate = (Get-Date -Format yyyyMMdd.HHmmss)
$outdetails = ($exedir + "\" + "GatherVolumeInformation_" + $currentDate + "_Detail.csv")

# Load ONTAP PowerShell Toolkit.
$module = Get-Module DataONTAP
if ($module -eq $null) {
    Import-Module DataONTAP
}

try {
    $requiredVersion = New-Object System.Version(1.2)
    if ((Get-NaToolkitVersion).CompareTo($requiredVersion) -lt 0) {
        throw
    }
} catch [Exception] {
    Write-Host "`nThis script requires Data ONTAP PowerShell Toolkit 1.2 or higher`n" -ForegroundColor Red
    return
}

$cred = New-Object -TypeName System.Management.Automation.PSCredential -ArgumentList $username, $password

# Declare object arrays.
$objDetail = @()

# Connect to each node individually.
foreach ($node in $nodes) {
    Write-Host "connecting to node $node..."
    $conn = Connect-NaController -Name $node -HTTPS -Credential $cred

    if ($conn -ne $null) {
        Write-Host "node connected, continuing on to volume calculations..."
        Write-Host "gathering node volumes..."
        $vols = Get-NaVol | Where-Object { $_.state -eq "online" -and $_.raidstatus -notmatch "read-only" }
        if ($vols -ne $null) {
            foreach ($vol in $vols) {
                Write-Host "`ngathering volume data for volume $vol..."
                $nasis = $null

                # Get volume details.
                Write-Host "    ... gathering volume details"
                $navol = Get-NaVol -Name $vol
                Write-Host "    ... gathering AutoSize details"
                $navolautosize = Get-NaVolAutosize -Name $vol
                Write-Host "    ... gathering Dedupe (SIS) details"
                if ($navol.Dedupe -eq "True") {
                    $nasis = Get-NaSis -Name $vol
                }
                if ($nasis -eq $null) {
                    $sissched = "None"
                }
                if ($nasis -ne $null) {
                    $sissched = $nasis.Schedule
                }

                # Format numbers.
                $ftotalsize = ConvertTo-FormattedNumber $navol.TotalSize DataSize "0.0"
                $favailable = ConvertTo-FormattedNumber $navol.Available DataSize "0.0"
                $fmaxsize = ConvertTo-FormattedNumber $navolautosize.MaximumSize DataSize "0.0"
                $fincrement = ConvertTo-FormattedNumber $navolautosize.IncrementSize DataSize "0.0"

                # Build array for details.
                $detailprop = @{
                    'Node'            = $node
                    'Volume'          = $vol
                    'Aggregate'       = $navol.Aggregate
                    'TotalSize'       = $ftotalsize
                    'Used'            = $navol.Used
                    'Available'       = $favailable
                    'DedupeEnabled'   = $navol.Dedupe
                    'DedupeSchedule'  = $sissched
                    'AutogrowEnabled' = $navolautosize.IsEnabled
                    'MaxSize'         = $fmaxsize
                    'IncrementSize'   = $fincrement
                }
                $objectD = New-Object -TypeName PSObject -Property $detailprop
                $objDetail += $objectD
                if ($IsVerbose) {
                    Write-Host "`n`nShowing Verbose Output...`n`n"
                    $detailprop
                }
            }
        }
    }
}

# Save files.
$objDetail | Select-Object Node, Volume, Aggregate, TotalSize, Used, Available, DedupeEnabled, DedupeSchedule, AutogrowEnabled, MaxSize, IncrementSize | Export-Csv -Path $outdetails -NoTypeInformation

Notes

• Update 2026-09-20 (v1.1): the timestamp in the output file name was yyyymmdd.Hm.s, where mm is minutes, so it never contained the month. It is now yyyyMMdd.HHmmss, for example GatherVolumeInformation_20140428.140530_Detail.csv.

Requirements

• The Data ONTAP dfm command-line tool, available on the OnCommand Core server.
• A PowerShell prompt on the OnCommand Core server, and an account allowed to list and delete events.

Usage

Run this in PowerShell on the OnCommand Core server. It lists the IDs of all Information events and deletes them one at a time.

dfm event list -q -S information |
    Select-String -Pattern "(?<ID>[0-9]+)" |
    Select-Object @{Name = "ID"; Expression = { $_.Matches[0].Groups["ID"].Value }} |
    ForEach-Object { dfm event delete $_.ID }

Notes

• dfm event list -q -S information is the key part of this line. It prints only the IDs of the events whose severity is Information.
• Select-String picks the numeric event ID out of each line, Select-Object turns it into an ID property, and ForEach-Object calls dfm event delete with each ID.
• If you’d want to delete all events, remove the -S information from the line. This deletes events of every severity, so use it with care.

Source

https://communities.netapp.com/message/94591#94591

This PowerShell script uses the Data ONTAP PowerShell Toolkit to collect that information for every online volume on each 7-Mode controller and writes a summary CSV and a detail CSV.

Requirements

• Data ONTAP PowerShell Toolkit 1.2 or higher (the DataONTAP module)
• NetApp 7-Mode controllers reachable over HTTPS
• An account that can list volumes and snapshots on each controller
• Write access to the folder the script runs from (the CSV files are saved next to the script)

Parameters

Usage

Pass the controllers and account on the command line. The password is prompted for:

& '.\NetApp-Gather Snapshot Information v1.1.ps1' -nodes filer1.company.biz,filer2.company.biz -username "domain\username" -IsVerbose

Or run it with no parameters and answer the prompts:

& '.\NetApp-Gather Snapshot Information v1.1.ps1'

cmdlet NetApp-Gather Snapshot Information v1.1.ps1 at command pipeline position 1
Supply values for the following parameters:
nodes[0]: filer1.company.biz
nodes[1]: filer2.company.biz
nodes[2]:
username: domain\username
password: *************

Script

Original (v1.1)

<#
.SYNOPSIS
    NetApp-Gather Snapshot Information
.DESCRIPTION
    Collects snapshot information, summary and detail, for every online volume
    on each 7-Mode controller, including created time, total snapshots, total
    days, average per day and oldest snapshot. Saves a Summary and a Detail CSV
    next to the script.
.PARAMETER nodes
    Controllers to query, one per entry.
.PARAMETER username
    Account used to connect, for example domain\username.
.PARAMETER password
    Password for the account, as a SecureString.
.PARAMETER IsVerbose
    Display snapshot detail for each volume.
.EXAMPLE
    & '.\NetApp-Gather Snapshot Information v1.1.ps1' -nodes filer1.company.biz,filer2.company.biz -username "domain\username" -IsVerbose
.EXAMPLE
    & '.\NetApp-Gather Snapshot Information v1.1.ps1'
.NOTES
    Author  : Thomas Lasswell (https://www.techcolumnist.com)
    Version : 1.2 (2026-09-20)
    Requires: Data ONTAP PowerShell Toolkit 1.2 or higher
    History : 1.0 2014-01-17 Initial version.
              1.1 2014-01-21 Added CSV export, days old column fixed.
              1.2 2026-09-20 Fixed the timestamp in the CSV file names (it used minutes
                  where the month belongs).
#>
# Parameters: nodes is each node; when finished, press Enter and it will continue.
param(
    [Parameter(Mandatory = $true)]
    [Array]$nodes,
    [Parameter(Mandatory = $true)]
    [String]$username,
    [Parameter(Mandatory = $true, ParameterSetName = 'Secret')]
    [Security.SecureString]$password,
    [switch]$IsVerbose
)

# Create output file names
$exedir = Split-Path -Path $MyInvocation.MyCommand.Definition -Parent
$currentDate = (Get-Date -Format yyyyMMdd.HHmmss)
$outsummary = ($exedir + "\" + "GatherSnapshotInformation_" + $currentDate + "_Summary.csv")
$outdetails = ($exedir + "\" + "GatherSnapshotInformation_" + $currentDate + "_Detail.csv")

# Load the ONTAP PowerShell Toolkit
$module = Get-Module DataONTAP
if ($module -eq $null) {
    Import-Module DataONTAP
}

try {
    $requiredVersion = New-Object System.Version(1.2)
    if ((Get-NaToolkitVersion).CompareTo($requiredVersion) -lt 0) { throw }
} catch [Exception] {
    Write-Host "`nThis script requires Data ONTAP PowerShell Toolkit 1.2 or higher`n" -ForegroundColor Red
    return
}
$cred = New-Object -TypeName System.Management.Automation.PSCredential -ArgumentList $username, $password

# Calculate the difference between two dates
function Get-DateDiff {
    param (
        [CmdletBinding()]
        [parameter(Mandatory = $true)]
        [datetime]$date1,
        [parameter(Mandatory = $true)]
        [datetime]$date2
    )
    if ($date2 -gt $date1) {
        $diff = $date2 - $date1
    } else {
        $diff = $date1 - $date2
    }
    $diff
}

# Declare object arrays
$objDetail = @()
$objSummary = @()

# Connect to each node individually
foreach ($node in $nodes) {
    Write-Host "connecting to node $node..."
    $conn = Connect-NaController -Name $node -HTTPS -Credential $cred

    if ($conn -ne $null) {
        Write-Host "node connected, continuing on to snapshot calculations..."
        Write-Host "gathering node volumes..."
        $vols = Get-NaVol | Where-Object { $_.state -eq "online" -and $_.raidstatus -notmatch "read-only" }
        if ($vols -ne $null) {
            foreach ($vol in $vols) {
                Write-Host "gathering snapshots for volume $vol..."
                # Get snapshots
                $snaps = Get-NaSnapshot -TargetName $vol

                # Group to count snapshots per day
                $snapsdatecount = $snaps | Group-Object { ((Get-Date) - $_.Created).Days } -NoElement | Sort-Object Name -Descending
                # Measure to get count and average; the average is snapshots per day
                $totalavgdays = $snapsdatecount | Measure-Object Count -Average | Select-Object Count, Average
                $avgdays = $totalavgdays.Average
                $totaldays = $totalavgdays.Count

                # Sum snapshots for total snapshot consumption
                $totalsize = $snaps | Measure-Object Total -Sum | Select-Object Count, Sum
                $ftotalsize = ConvertTo-FormattedNumber $totalsize.sum DataSize "0.0"

                # Get oldest snapshot
                $foldestsnap = $snaps | Sort-Object Created -Descending | Select-Object -Last 1

                # Build array for summary
                if ($avgdays -ne $null) {
                    $summaryprop = @{
                        'Node'       = $node
                        'Volume'     = $vol
                        'TotalSnaps' = $snaps.length
                        'TotalDays'  = $totaldays
                        'AvgPerDay'  = $avgdays
                        'TotalSize'  = $ftotalsize
                        'Oldest'     = $foldestsnap.created
                    }
                    $objectS = New-Object -TypeName PSObject -Property $summaryprop
                    $objSummary += $objectS
                    $objectS

                    foreach ($snap in $snaps) {
                        $daysold = Get-DateDiff (Get-Date) $snap.created
                        $ftotal = ConvertTo-FormattedNumber $snap.total DataSize "0.0"
                        $fcumulative = ConvertTo-FormattedNumber $snap.CumulativeTotal DataSize "0.0"

                        # Build array for details
                        $detailprop = @{
                            'Node'            = $node
                            'Volume'          = $vol
                            'Name'            = $snap.name
                            'Created'         = $snap.created
                            'DaysOld'         = $daysold.days
                            'TotalSize'       = $ftotal
                            'CumulativeTotal' = $fcumulative
                        }
                        $objectD = New-Object -TypeName PSObject -Property $detailprop
                        $objDetail += $objectD
                    }
                    if ($IsVerbose) {
                        $snaps | Format-Table `
                            @{Expression = {$node}; Label = "Node name"; Width = 20},`
                            @{Expression = {$vol}; Label = "Volume"; Width = 40},`
                            @{Expression = {$_.Name}; Label = "Name"; Width = 150},`
                            @{Expression = {$_.Created.ToShortDateString()}; Label = "Created"; Width = 12},`
                            @{Expression = {'{0} Days' -f (Get-DateDiff (Get-Date) $_.created).days}; Label = "Days Old"; Width = 20},`
                            @{Expression = {ConvertTo-FormattedNumber $_.Total DataSize "0.0"}; Label = "Total"; Width = 15},`
                            @{Expression = {ConvertTo-FormattedNumber $_.CumulativeTotal DataSize "0.0"}; Label = "Cumulative"; Width = 10} -AutoSize `
                            | Out-String -Width 1000 | Write-Host
                    }
                }
                if ($avgdays -eq $null) { Write-Host "`tNo Snapshots Exist on $vol..." }
            }
        }
    }
}

# Save files
$objSummary | Select-Object Node, Volume, TotalSnaps, TotalDays, AvgPerDay, TotalSize, Oldest | Export-Csv -Path $outsummary -NoTypeInformation
$objDetail | Select-Object Node, Volume, Name, Created, DaysOld, TotalSize, CumulativeTotal | Export-Csv -Path $outdetails -NoTypeInformation

ChatGPT rewrite

I was curious to see what ChatGPT code interpreter would do with this code and this is its output.

<#
.SYNOPSIS
    NetApp-Gather Snapshot Information
.DESCRIPTION
    Collects snapshot information, summary and detail, including created time,
    total snapshots, total days, average per day and oldest snapshot.
.PARAMETER nodes
    Controllers to query, one per entry.
.PARAMETER username
    Account used to connect, for example domain\username.
.PARAMETER password
    Password for the account, as a SecureString.
.PARAMETER IsVerbose
    Display snapshot detail for each volume.
.NOTES
    Author  : Thomas Lasswell (https://www.techcolumnist.com)
    Version : 1.2 (2026-09-20), rewritten by ChatGPT
    Requires: Data ONTAP PowerShell Toolkit 1.2 or higher
#>
param(
    [Parameter(Mandatory = $true)]
    [Array]$nodes,
    [Parameter(Mandatory = $true)]
    [String]$username,
    [Parameter(Mandatory = $true, ParameterSetName = 'Secret')]
    [Security.SecureString]$password,
    [switch]$IsVerbose
)

$exedir = Split-Path -Path $MyInvocation.MyCommand.Definition -Parent
$currentDate = (Get-Date -Format "yyyyMMdd.HHmmss")
$outsummary = -join ($exedir, "\GatherSnapshotInformation_", $currentDate, "_Summary.csv")
$outdetails = -join ($exedir, "\GatherSnapshotInformation_", $currentDate, "_Detail.csv")

Import-Module DataONTAP -ErrorAction SilentlyContinue

try {
    $requiredVersion = New-Object System.Version(1.2)
    if ((Get-NaToolkitVersion).CompareTo($requiredVersion) -lt 0) { throw "This script requires Data ONTAP PowerShell Toolkit 1.2 or higher." }
} catch {
    Write-Host "`nThis script requires Data ONTAP PowerShell Toolkit 1.2 or higher`n" -ForegroundColor Red
    return
}

$cred = New-Object -TypeName System.Management.Automation.PSCredential -ArgumentList $username, $password

function Get-DateDiff {
    param (
        [parameter(Mandatory = $true)]
        [datetime]$date1,
        [parameter(Mandatory = $true)]
        [datetime]$date2
    )
    return [Math]::Abs(($date2 - $date1).Days)
}

$objDetail = @()
$objSummary = @()

foreach ($node in $nodes) {
    Write-Host "Connecting to node $node..."
    $conn = Connect-NaController -Name $node -HTTPS -Credential $cred

    if ($conn) {
        Write-Host "Node connected, continuing on to snapshot calculations..."
        $vols = Get-NaVol | Where-Object { $_.state -eq "online" -and $_.raidstatus -notmatch "read-only" }

        foreach ($vol in $vols) {
            $snaps = Get-NaSnapshot -TargetName $vol
            $snapsdatecount = $snaps | Group-Object { ((Get-Date) - $_.Created).Days } -NoElement | Sort-Object Name -Descending
            $totalavgdays = $snapsdatecount | Measure-Object Count -Average | Select-Object Count, Average
            $totalsize = $snaps | Measure-Object Total -Sum | Select-Object Count, Sum
            $foldestsnap = $snaps | Sort-Object Created -Descending | Select-Object -Last 1

            if ($totalavgdays.Average) {
                $summaryprop = @{
                    'Node'       = $node
                    'Volume'     = $vol
                    'TotalSnaps' = $snaps.length
                    'TotalDays'  = $totalavgdays.Count
                    'AvgPerDay'  = $totalavgdays.Average
                    'TotalSize'  = [System.Math]::Round($totalsize.Sum, 2)
                    'Oldest'     = $foldestsnap.created
                }
                $objSummary += New-Object -TypeName PSObject -Property $summaryprop

                foreach ($snap in $snaps) {
                    $daysold = Get-DateDiff (Get-Date) $snap.created
                    $detailprop = @{
                        'Node'            = $node
                        'Volume'          = $vol
                        'Name'            = $snap.name
                        'Created'         = $snap.created
                        'DaysOld'         = $daysold
                        'TotalSize'       = [System.Math]::Round($snap.total, 2)
                        'CumulativeTotal' = [System.Math]::Round($snap.CumulativeTotal, 2)
                    }
                    $objDetail += New-Object -TypeName PSObject -Property $detailprop
                }
            } else {
                Write-Host "`tNo Snapshots Exist on $vol..."
            }
        }
    }
}

$objSummary | Export-Csv -Path $outsummary -NoTypeInformation
$objDetail | Export-Csv -Path $outdetails -NoTypeInformation

Notes

• Output is two CSV files next to the script: GatherSnapshotInformation_<date>_Summary.csv (one row per volume) and GatherSnapshotInformation_<date>_Detail.csv (one row per snapshot).
• The ChatGPT version is a straight rewrite of the original and has not been run against a filer. It is not a drop-in replacement: it drops the -IsVerbose table output and formats sizes with [Math]::Round instead of ConvertTo-FormattedNumber.
• Update 2026-09-20 (v1.2): the CSV file name timestamp was yyyymmdd.Hm.s, where mm is minutes, so it never contained the month. It is now yyyyMMdd.HHmmss. The ChatGPT rewrite also grouped snapshots by $_.Created.Days, which does not exist on a date, so every snapshot landed in one group; it now groups by age in days like the original.

Cisco IOS Software, Catalyst 4500 L3 Switch Software (cat4500e-ENTSERVICESK9-M), Version 12.2(54)SG, RELEASE SOFTWARE (fc3)
# conf t
(config)#crypto key zeroize rsa
% No Signature RSA Keys found in configuration.
(config)# crypto key generate rsa general-keys label ssh modulus 1024
The name for the keys will be: ssh

% The key modulus size is 1024 bits
% Generating 1024 bit RSA keys, keys will be non-exportable...[OK]
(config)# ip ssh authentication-retries 5
(config)# ip ssh version 2
(config)# line vty 0 4
(config)# transport input ssh telnet

Note: You can leave the “telnet” off vty transport, but if you do ensure that you’ve tested SSH first!

Requirements

• PowerShell 2.0 or later.
• VMware vSphere PowerCLI 5.x, loaded as the VMware.VimAutomation.Core snap-in (the script calls Add-PSSnapin).
• Network access from the machine running the script to both the vCenter 4.1 and vCenter 5.1 servers.
• Permission to browse and upload files on the datastores, and to register (New-VM) virtual machines in vCenter 5.1.
• The datastores holding the VMs must be visible to the vCenter 5.1 server and to the ESX host you import to.
• The two local working folders and the import folder in vCenter 5.1 must already exist (see the values to edit below).

Parameters

The script exits with a message if either server is missing. Edit these variables near the top of the script before running it:

Usage

Pass the vCenter 4.1 server first and the vCenter 5.1 server second.

.\VM-GatherVMX.ps1 -vcServer4 "<vcenter-4-server>" -vcServer5 "<vcenter-5-server>"

Script

<#
.SYNOPSIS
    Downloads, updates and uploads VMX files with PowerCLI, then adds the VMs to the vCenter 5.1 inventory.
.DESCRIPTION
    Downloads the VMX file of every "PoweredOn" VM in the vCenter 4.1 cluster,
    removes the vShield VFILE lines, and uploads the result to the same
    datastore folder under a new name (<name>-51.vmx). Once uploaded, each VM is
    imported into the new vCenter 5.1 server.
.PARAMETER vcServer4
    The vCenter 4.1 server to connect to.
.PARAMETER vcServer5
    The vCenter 5.1 server to connect to.
.EXAMPLE
    .\VM-GatherVMX.ps1 -vcServer4 "<vcenter-4-server>" -vcServer5 "<vcenter-5-server>"
.NOTES
    Author  : Thomas Lasswell (https://www.techcolumnist.com)
    Version : 1.1 (2026-09-20)
    Requires: VMware vSphere PowerCLI 5.x (VMware.VimAutomation.Core snap-in)
    History : 1.0 2013-10-25 Initial version.
              1.1 2026-09-20 Fixed VM folder lookup (now after connecting to vCenter 5.1)
                  and a variable clash that overwrote it, VMX names that contain
                  ".", "v", "m" or "x", and the unassigned $VMFullPath output.
#>
param(
    [string]$vcServer4,
    [string]$vcServer5
)

Clear-Host

if (!$vcServer4) {
    Write-Host "No vCenter 4 Server Specified"
    exit
}
if (!$vcServer5) {
    Write-Host "No vCenter 5 Server Specified"
    exit
}

# Load PowerCLI.
Add-PSSnapin VMware.VimAutomation.Core
$host.ui.rawui.WindowTitle = "PowerShell [PowerCLI Snap-in Loaded]"

# Download VMX file location.
$outvmxdir = "C:\scripts\vmxfiles"
# Modified VMX file location.
$outvmxnewdir = "C:\scripts\vmxfiles-new"
# Cluster name in vCenter 4.1 to gather PoweredOn VMs.
$vCluster = "NA Cluster"
# VM folder name in vCenter 5.1. This folder needs to exist.
$VMFolderName = "Import"
# ESX host in vCenter 5.1 to import VM.
$ESXHost = "<esx-host>"
# Resource pool in vCenter 5.1 to import VM.
$ResPool = "Infrastructure"

# Connect to vCenter 4.1 server.
Connect-VIServer $vcServer4

$aVM = Get-VM -Location $vCluster | Where-Object { $_.PowerState -eq "PoweredOn" } | Select-Object Name, PowerState
$aVMInfo = @()
foreach ($vm in $aVM) {
    $vname = $vm.name
    Write-Host $vname

    # Process VMX information.
    $VMView = Get-VM $vname | Get-View
    $VMPathName = $VMView.Config.Files.VmPathName
    Write-Host $VMPathName

    # Download VMX file.
    $dsname = $VMPathName.Split(" ")[0].TrimStart("[").TrimEnd("]")
    $vmRelativePath = $VMPathName.Split(']')[1].TrimStart(' ')
    Remove-PSDrive -Name fromds -ErrorAction SilentlyContinue
    New-PSDrive -Name fromds -Location (Get-Datastore $dsname) -PSProvider VimDatastore -Root '/' | Out-Null
    $dlvmx = $outvmxdir + ("/") + $vmRelativePath.Split('/')[1]
    $checkforoutfile = Test-Path $dlvmx
    if ($checkforoutfile) {
        Remove-Item $dlvmx
    }
    Copy-DatastoreItem -Item fromds:\$vmRelativePath -Destination $outvmxdir -Force

    # Update VMX file to -51 file without vShield lines.
    $vmxfile = $VMPathName.Split("/")[1]
    $vmxsource = $outvmxdir + "\" + $vmxfile
    $vmxdest = $outvmxnewdir + "\" + [System.IO.Path]::GetFileNameWithoutExtension($vmxfile) + "-51.vmx"
    $checkforoutfile = Test-Path $vmxdest
    if ($checkforoutfile) {
        Remove-Item $vmxdest
    }
    Get-Content $vmxsource | Where-Object { $_ -notmatch 'VFILE.globaloptions' -and $_ -notmatch 'scsi0:0.filters = "VFILE"' } | Set-Content $vmxdest
    Add-Content $vmxdest "`n#Modified to remove VFILE Lines"

    # Upload new VMX file to datastore.
    Write-Host $vmxdest
    $vmxupload = ($vmRelativePath -replace '\.vmx$', '') + "-51.vmx"
    Write-Host $vmxupload
    Copy-DatastoreItem -Item $vmxdest -Destination fromds:\$vmxupload -Force

    # Set array for addition of VMs.
    $obj = New-Object PSObject
    $obj | Add-Member -MemberType NoteProperty -Name "VMName" -Value $vname
    $obj | Add-Member -MemberType NoteProperty -Name "VMDatastore" -Value $dsname
    $obj | Add-Member -MemberType NoteProperty -Name "VMPathName" -Value $vmxupload
    $aVMInfo += $obj
}

Remove-PSDrive -Name fromds -ErrorAction SilentlyContinue
Disconnect-VIServer $vcServer4 -Force -Confirm:$false
Start-Sleep 5

# Connect to vCenter 5.1 server.
Connect-VIServer $vcServer5
$VMFolder = Get-Folder $VMFolderName

# Import VM to vCenter 5.1.
foreach ($vm in $aVMInfo) {
    $vname = $vm.VMName
    $datastore = $vm.VMDatastore
    $VMPath = $vm.VMPathName
    Write-Host $vname
    Write-Host $datastore
    Write-Host $VMPath
    $VMFullPath = "[" + $datastore + "] " + $VMPath
    Write-Host $VMFullPath
    New-VM -VMFilePath $VMFullPath -VMHost $ESXHost -Location $VMFolder -ResourcePool $ResPool | Out-Null
}

Disconnect-VIServer $vcServer5 -Force -Confirm:$false

Notes

• The original VMX files are left untouched. The modified copy is uploaded next to each original as <name>-51.vmx, and that copy is what gets registered in vCenter 5.1.
• The script expects each VM to live in a single datastore folder of the form [datastore] <folder>/<name>.vmx.
• Update 2026-09-20 (v1.1): the import folder is now looked up after connecting to vCenter 5.1 (it previously ran before any connection, and its variable was overwritten inside the download loop, so New-VM -Location received a path string instead of the folder). VMX file names that contain ., v, m or x are also no longer truncated, and the fromds: drive is removed at the end.

Requirements

• Windows PowerShell with VMware vSphere PowerCLI installed. The script loads the VMware.VimAutomation.Core snap-in, so it needs a PowerCLI release that ships it (5.x era).
• A vCenter account that can read datacenters, datastores and VMs. Connect-VIServer prompts for credentials.
• Network access to the vCenter Server.
• A D:\scripts folder, or change the export path.

Parameters

Usage

Pass the vCenter Server name and sign in when prompted.

.\Get-VMDatastore.ps1 -vcServer vcenter.example.com

The results are written to D:\scripts\datastore-output.csv, one row per VM and datastore, with Name, DataStore, VMHost, PowerState, Version and Folder columns.

Script

<#
.SYNOPSIS
    Lists all VMs in a vCenter Server together with their datastore.
.DESCRIPTION
    Connects to the vCenter Server, walks every datastore in every datacenter and collects the VMs
    stored on it (name, datastore, host, power state, hardware version and folder). The result is
    written to D:\scripts\datastore-output.csv and the session is disconnected.
.PARAMETER vcServer
    Name or address of the vCenter Server. The script exits with a message if it is missing.
.EXAMPLE
    .\Get-VMDatastore.ps1 -vcServer vcenter.example.com
.NOTES
    Author  : Thomas Lasswell (https://www.techcolumnist.com)
    Version : 1.1 (2026-09-20)
    History : 1.0 2013-10-14 Initial version.
              1.1 2026-09-20 Disconnects without a confirmation prompt.
    Requires: VMware PowerCLI with the VMware.VimAutomation.Core snap-in
#>
param(
    [string]$vcServer
)

Clear-Host

if (!$vcServer) {
    Write-Host "No vCenter Server Specified"
    exit
}

Add-PSSnapin VMware.VimAutomation.Core
$host.UI.RawUI.WindowTitle = "PowerShell [PowerCLI Module Loaded]"

Connect-VIServer $vcServer

$aDatastoreVM = Get-Datacenter | Get-Datastore | ForEach-Object {
    $ds = $_.Name
    $_ | Get-VM | Select-Object Name, @{n = 'DataStore'; e = { $ds } }, VMHost, PowerState, Version, Folder
}

$aDatastoreVM | Export-Csv "D:\scripts\datastore-output.csv" -NoTypeInformation -UseCulture
Disconnect-VIServer $vcServer -Confirm:$false

Notes

• Update 2026-09-20 (v1.1): Disconnect-VIServer now uses -Confirm:$false, so an unattended run no longer stops at a confirmation prompt.

Remember —- %ALLUSERSPROFILE%

http://rufus.akeo.ie/

Requirements

• Windows PowerShell 2.0 or later.
• The Remote Registry service running on every computer in the list.
• An account with administrative rights on those computers, and network access to them.
• A computerlist.csv file in the same folder as the script, with a computername column (for example an Active Directory export).

Parameters

The script takes no parameters. Edit these values before running it.

Usage

Create computerlist.csv next to the script.

computername
SERVER01
SERVER02

Then run the script. Matches are shown as a table and also written to searchpublisher-NetApp_<ddMMyyyy>.csv in the script folder (an existing file with the same name is deleted first).

.\Find-InstalledNetAppProducts.ps1

To search for another vendor, change $LikePublisher at the top of the script.

Script

<#
.SYNOPSIS
    Finds software from a given publisher (NetApp by default) installed on the computers in a CSV file.
.DESCRIPTION
    Reads computerlist.csv from the script folder (it needs a computername column), opens the
    remote registry on each computer and walks HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall,
    skipping KB entries. Entries whose publisher matches $LikePublisher are displayed as a table and
    exported to searchpublisher-<publisher>_<ddMMyyyy>.csv in the script folder.
.EXAMPLE
    .\Find-InstalledNetAppProducts.ps1
.NOTES
    Author  : Thomas Lasswell (https://www.techcolumnist.com)
    Version : 1.1 (2026-09-20)
    History : 1.0 2013-09-03 Initial version.
              1.1 2026-09-20 The CSV no longer starts with a #TYPE line.
    Requires: Windows PowerShell 2.0+, Remote Registry service on the target computers
    Based on a Scripting Guy post.
#>
$ErrorActionPreference = 'silentlycontinue'
$exedir = Split-Path -Path $MyInvocation.MyCommand.Definition -Parent

# Variables
$LikePublisher = "NetApp"

$infile = ($exedir + "\computerlist.csv")
Write-Host "$infile"
$computers = Import-Csv $infile
$totalComputers = $computers.Count
$currentDate = (Get-Date -UFormat "%d%m%Y")
$outfile = ($exedir + "\" + "searchpublisher-" + $LikePublisher + "_" + $currentDate + ".csv")
Write-Host "$outfile"
$checkforoutfile = Test-Path $outfile
if ($checkforoutfile) {
    Remove-Item $outfile
}

$counter1 = 0
$array = @()
foreach ($pc in $computers) {
    $subkeys = $null
    $computername = $pc.computername
    $counter1++
    Write-Progress -Activity "Processing" -Status "Processing computer $counter1 of $totalComputers" -PercentComplete (100 * ($counter1 / $computers.Count)) -Id 1
    Write-Progress "Initializing" "Connecting to the Windows System: $computername" -ParentId 1

    # Define the variable to hold the location of currently installed programs.
    $UninstallKey = "SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Uninstall"

    # Create an instance of the registry object and open the HKLM base key.
    $reg = [Microsoft.Win32.RegistryKey]::OpenRemoteBaseKey('LocalMachine', $computername)

    # Drill down into the Uninstall key using the OpenSubKey method.
    $regkey = $reg.OpenSubKey($UninstallKey)

    # Retrieve an array of strings that contain all the subkey names.
    $subkeys = $regkey.GetSubKeyNames()

    # Open each subkey and use the GetValue method to return the required values for each.
    $counter2 = 0
    foreach ($key in $subkeys) {
        $counter2++
        if ($subkeys.Count -eq $null) {
            Write-Host "Could not connect to $computername continuing ..."
        }
        if (($subkeys.Count -ne $null) -and ($key -notlike "*KB*")) {
            Write-Progress -Activity "Gathering Key information on $computername" -Status "Processing Key $key" -PercentComplete (100 * ($counter2 / $subkeys.Count)) -ParentId 1
            $thisKey = $UninstallKey + "\\" + $key
            $thisSubKey = $reg.OpenSubKey($thisKey)
            $obj = New-Object PSObject
            $obj | Add-Member -MemberType NoteProperty -Name "ComputerName" -Value $computername
            $obj | Add-Member -MemberType NoteProperty -Name "DisplayName" -Value $($thisSubKey.GetValue("DisplayName"))
            $obj | Add-Member -MemberType NoteProperty -Name "DisplayVersion" -Value $($thisSubKey.GetValue("DisplayVersion"))
            $obj | Add-Member -MemberType NoteProperty -Name "InstallLocation" -Value $($thisSubKey.GetValue("InstallLocation"))
            $obj | Add-Member -MemberType NoteProperty -Name "Publisher" -Value $($thisSubKey.GetValue("Publisher"))
            $array += $obj
        }
    }
}

# Show and export the matches.
$array | Where-Object { $_.DisplayName -and $_.Publisher -like "*$LikePublisher*" } | Select-Object ComputerName, DisplayName, DisplayVersion, Publisher | Format-Table -AutoSize
$array | Where-Object { $_.DisplayName -and $_.Publisher -like "*$LikePublisher*" } | Select-Object ComputerName, DisplayName, DisplayVersion, Publisher | Export-Csv $outfile -NoTypeInformation

Notes

• Update 2026-09-20 (v1.1): the export now uses -NoTypeInformation. Without it, Windows PowerShell 5.1 and earlier write a #TYPE ... line at the top of the CSV that breaks most importers.

Basically, increasing the maxfiles cannot be reversed, however when you grow a volume the maxfiles grows as well. When you shrink a volume the maxfiles is still set at what it was and is not shrunk.

The maxfiles also grows if you’ve set a higher maxfiles than what the volume would originally specify but you grow the volume and the new maxfiles for that volume size is higher than what you’ve previously set.

na-ifas-01: vol create testvol1 aggr0 10g
Creation of volume 'testvol1' with size 10g on containing aggregate
'aggr0' has completed.
na-ifas-01: maxfiles testvol1
Volume testvol1: maximum number of files is currently 311280 (96 used).
na-ifas-01: maxfiles testvol1 411280

The new maximum number of files specified is more than twice as big as
it needs to be, based on current usage patterns. This invocation of the
operation on the specified volume will allow disk space consumption for
files to grow up to the new limit depending on your workload. The maxfiles
setting cannot be lowered below the point of any such additional disk space
consumption and any additional disk space consumed can never be reclaimed.
Also, such consumption of additional disk space could result in less
available memory after an upgrade.
The new maximum number of files will be rounded to 411270.

Are you sure you want to change the maximum number of files? y
na-ifas-01: maxfiles testvol1
Volume testvol1: maximum number of files is currently 411270 (96 used).
na-ifas-01: vol size testvol1 20g
vol size: Flexible volume 'testvol1' size set to 20g.
na-ifas-01: maxfiles testvol1
Volume testvol1: maximum number of files is currently 622580 (96 used).

na-ifas-01: vol create testvol2 aggr0 10g
Creation of volume 'testvol2' with size 10g on containing aggregate
'aggr0' has completed.
na-ifas-01: vol size testvol2 20g
vol size: Flexible volume 'testvol2' size set to 20g.
na-ifas-01: maxfiles testvol2
Volume testvol2: maximum number of files is currently 622580 (96 used).
na-ifas-01: vol size testvol2 10g
vol size: Flexible volume 'testvol2' size set to 10g.
na-ifas-01: maxfiles testvol2
Volume testvol2: maximum number of files is currently 622580 (96 used).

SAN:

nosnap=on, nosnapdir=off, minra=off, no_atime_update=off, nvfail=off, ignore_inconsistent=off, snapmirrored=off, create_ucode=on, convert_ucode=on, maxdirsize=xxxx, schedsnapname=ordinal, fs_size_fixed=off, guarantee=volume, svo_enable=off, svo_checksum=off, svo_allow_rman=off, svo_reject_errors=off, no_i2p=on, fractional_reserve=0, extent=off, try_first=volume_grow, read_realloc=off, snapshot_clone_dependency=off, dlog_hole_reserve=off, nbu_archival_snap=off

vol create {volname} {aggr} {size}g
vol options {volname} nosnap on
vol options {volname} convert_ucode on
vol options {volname} no_i2p on
vol options {volname} fractional_reserve 0
snap reserve {volname} 0
vol autosize {volname} -m {size+20%} -i {50g}
snap autodelete {volname} on

NAS:

nosnap=off, nosnapdir=off, minra=off, no_atime_update=off, nvfail=off, ignore_inconsistent=off, snapmirrored=off, create_ucode=on, convert_ucode=on, maxdirsize=xxxx, schedsnapname=ordinal, fs_size_fixed=off, guarantee=volume, svo_enable=off, svo_checksum=off, svo_allow_rman=off, svo_reject_errors=off, no_i2p=off, fractional_reserve=100, extent=off, try_first=volume_grow, read_realloc=off, snapshot_clone_dependency=off, dlog_hole_reserve=off, nbu_archival_snap=off

vol create {volname} {aggr} {size}g
vol options {volname} convert_ucode on
snap reserve {volname} 5

In case you have an issue with getting your remote device to show up for /sdcard/ the following commands will help you out:

adb devices
adb push filename.zip /sdcard/

Example:

D:\and\sdk\platform-tools\adb devices
List of devices attached
9132ce46b device

D:\and\sdk\platform-tools\adb push gapps-jb-20130301-signed.zip /sdcard/
3280 KB/s (95417279 bytes in 28.403s)

To install a new .apk run the following (such as installing a new beta software, etc):

D:\and\sdk\platform-tools\adb<filename.apk>

or to force the install

D:\and\sdk\platform-tools\adb -r <filename.apk>

esxcli system coredump network get
esxcli system coredump network set --interface-name vmk0 --server-ipv4 10.0.1.11 --server-port 6500
esxcli system coredump network set --enable true
esxcli system coredump network get
esxcli system coredump network check

esxcli system syslog config get
esxcli system syslog config set --loghost="tcp://10.0.1.11:514";
esxcli network firewall ruleset set --ruleset-id=syslog --enabled=true
esxcli network firewall refresh
esxcli system syslog reload

Broken disks

RAID Disk Device HA SHELF BAY CHAN Pool Type RPM Used (MB/blks) Phys (MB/blks)
--------- ------ ------------- ---- ---- ---- ----- -------------- --------------
label version 0d.01.0 0d 1 0 SA:B - BSAS 7200 1695466/3472315904 1695759/3472914816
label version 0d.01.2 0d 1 2 SA:B - BSAS 7200 1695466/3472315904 1695759/3472914816
label version 0d.01.3 0d 1 3 SA:B - BSAS 7200 1695466/3472315904 1695759/3472914816

Here’s the fix:

disk assign
priv set diag
labelmaint isolate
label wipe
label wipev1
label makespare
labelmaint unisolate
priv set

disk assign {diskid} -s unowned -f

Here’s the common command line arguments that come with the new-backup cmdlet

new-backup -Clusteraware 'True|False' -lcr 'True|False' -VerifyOnDestVolumes 'src_storage_system_list:src_vol:dest_storage_system:dest_vol' -Verify 'True|False' -Server 'server_name' -StorageGroup 'storage_grp1, storage_grp2, ...' -ManagementGroup 'Standard|Weekly|Daily' -ActiveDatabaseOnly 'True|False' -PassiveDatabaseOnly 'True|False' -BackupTargetServer 'server name' -ActivationPreference 'ActivationPreferenceNum' -UpdateMirror 'True|False' -VerDestVolume 'True|False' -NoUTMRestore 'True|False' -NoTruncateLogs 'False' -Throttle 'throttle_val' -VerificationServer 'server_name' -UseMountPoint 'True|False' -CCRActiveNode Boolean 'True|False' -MountPointDir 'mountpoint_dir' -RetainBackups 'no_of_days_to_retain_backup' -RetainDays 'no_of_days_delete_backup' -Command 'True|False' -RunCommand 'win_path_and_script_name' -GenericNaming 'True|False' -BackupCopyRemoteCCRNode Boolean 'True|False' -RecoveryPoint 'win_path_and_script_name' -ReportProgress 'True|False' -ArchiveBackup 'True|False' -ArchiveBackupCopyRemoteCCRNode 'True|False' -ArchivedBackupRetention 'Hourly|Monthly|Daily|Weekly|Unlimited' -RetainUtmBackups 'no_of_log_backups_to_retain'

I’ve found this one to be useful to backup all members of a DAG, active databases are full backups, secondary/passive databases are copy based backups, no up to the minute backups:

new-backup –Server 'dagname' –ClusterAware –ManagementGroup 'Standard/Daily/Weekly' –RetainDays xx –NoUTMRestore –ActiveDatabaseOnly -UseMountPoint –MountPointDir 'C:\Program Files\NetApp\Snap Manager for Exchange\SnapMgrMountPoint' –RemoteAdditionalCopyBackup $True –RetainRemoteAdditionalCopyBackupDays xx

This one requires an individual task on every server in the DAG however this task will only run on one of the servers, the server that holds the cluster role. This allows for all databases to be backed up and still be able to backup your databases if your nodes fail. This command also allows you to add databases to your exchange environment and not have to modify your backup jobs.

\\{netapp}\etc$\log\autosupport

NetApp has released some commands in the 8.1.x code line release to check autosupport information.

netapp> autosupport
autosupport destinations
autosupport history
autosupport manifest
autosupport trigger

You will get some outputs like this:

netapp> autosupport history show
Seq                                    Attempt Last
Num   Destination Status               Count   Update
----- ----------- -------------------- ------- --------------------
66
      smtp        ignore               1       2/6/2013 09:35:46
      http        sent-successful      1       2/6/2013 09:35:49
      noteto      ignore               1       2/6/2013 09:35:46
65
      smtp        collection-failed    -       2/6/2013 09:34:51
      http        collection-failed    -       2/6/2013 09:34:51
      noteto      collection-failed    -       2/6/2013 09:34:51

esxcli storage nmp device list
esxcli storage nmp satp rule add -s VMW_SATP_LOCAL -d naa.630f70d99950c0001822f33e055d5d4b -o=enable_ssd
esxcli storage nmp satp rule list | grep enable_ssd
esxcli storage core claimrule load
esxcli storage core claimrule run
esxcli storage core claiming reclaim -d naa.630f70d99950c0001822f33e055d5d4b
esxcli storage core device list -d naa.630f70d99950c0001822f33e055d5d4b

The configuration for this achievement was:

• NetApp FAS6210
• 1x Flash Pool with 10x SSD, 11x 600GB SAS
• One 10G iSCSI connection
• Cisco UCS C-class server

Here’s a fun picture of the outcome:

Some additional information about the shelves:

• Supported on the following systems:
  • FAS/V3240
  • FAS/V3270
  • FAS/V6000 Series
  • FAS/V6200 Series
• Requires Data OnTap 8.1.1RC1 or higher
• No MetroCluster support
• Requires it’s own stack, meaning no mixing and matching DS4243 shelves, but this is the case with all the disk shelf models that are SAS.
• Recommended to have four (4) spare disks instead of two (2), this accommodates the evacuation of two disks that are needed to replace a drive.
• You replace 2 disks at once, not just one disk at a time.
• Maximum shelves per stack: 5

The DS4486 is currently available to order via your NetApp sales representative.

Disk Shelf Photo:

Disk Tray Photo:

dfm service stop http
dfm service start http

If you only do this then the images still point to the old http port. What actually needs to be run is:

dfm service stop
dfm service start

to fully restart oncommand.

DS{U}{# Disks}{SAS Speed}

For example, the DS4243:
DS – Disk Shelf, 4 – 4U, 24 – the number of disks, 3 – 3Gb/s SAS interface

and the DS2246
DS – Disk Shelf, 2 – 2U, 24 – the number of disks, 6 – 6Gb/s SAS interface

and the DS4486
DS – Disk Shelf, 4 – 4U, 48 – the number of disks, 6 – 6Gb/s SAS interface

Look forward to new and exciting blog posts as I take my adventures into specializing in NetApp. I’ll most likely be more active with tips and tricks that will be tailored around new experiences. Stay tuned!

Keep in mind that this is my personal blog. The views and opinions expressed on this site do not represent my employer.