@Tony - any special account and/or access to run as? I am getting this error while simulating this script.
Invoke-WebRequest : The remote server returned an error: (403) Forbidden.
At line:26 char:14
Hi Justin. Did you set your API key (not access key) in the script along with your orgID? Are you running Powershell as admin? Also if you do a get-executionpolicy, does is say something other than “unrestricted”? If so, do a: set-executionpolicy unrestricted
@Tony - check out above screenshot running with API key and as admin, the execution’s policy is unrestricted
Can you try generating another API key for yourself and trying that one?
Running PowerShell as administrator should only be necessary to make changes to local workstation. Messing with Execution Policy of unrestricted isn’t recommended either. If you want to see if ExecutionPolicy is a problem, then at least limit the scope to the process like Set-ExecutionPolicy -ExecutionPolicy Unrestricted -Scope Process.
I’ve successfully executed Tony’s code. I did change my filepath variable to $filepath = "$env:temp\cve.csv" to keep the results in my user space.
Justin’s PowerShell error is complaining about the remote server response. That can include any proxy servers in between you and Automox. In my early days of learning Automox API, I did get ‘unauthorized’ errors when I used an expired token.
@cgreggo - what do you suggest I change to be able to run this script successfully?
Tony,
Can we jump on a quick WebEx to help me with this script?
Justin
@Tony @cgreggo - 
I know what I did wrong! HA! I reviewed the code again and realized in the org ID - i pasted the entire URL instead of just the Org ID!
I am able to run the script! thanks for your help
Ah-ha! Always an adventure when computers do exactly what we tell them to do instead of what we want them to do.
Any suggestions how to run this in an environment where the limit of 500 is causing to not show all results?
Run it as is. Tony’s code has a pagination loop already. Each loop grabs 500 servers, filters to the ones with matching CVE, and appends the matches to the CSV. Then next run through the loop advances to the next page (servers 501-1000 and so on).
Any suggestions how to run this in an environment where the limit of 500 is causing to not show all results?
And if you do need pagination for any of your other scripts, here’s some sample code to show how to set that up:
I’ve taken @jarod.smilkstein’s code from here.
There’s 3 things to change in this code to make it work:
put in your API key
put in your orgID
set the $limit variable to the size you want, with a maximum of 500
This code will pull down all your device info via the https://console.automox.com/api/servers
API call, but you can sub that out for whatever info you’re wanting to pull. The data is saved to a csv, but you can also do manipulation to the $data object in the script first before outpu…
Mind if I chime in? If I were to guess based on @Maikel ‘s response I think he meant that the pagination loop isn’t working as expected.
I understand what you are trying to say, but I can’t verify it.
You can reproduce this by lowering the $limit variable to 5 and placing a write-host inside the server pagination loop. In this iteration of the script it will only display/iterate once.
This is due to the fact that the pagination is stopped when the response length is less than the limit.
The response length is evaluated by the following line:
if($response.count -lt $limit) {
break
}
However this part is not working as expected because the $response variable has never been defined till this point. An undefined variable with the count method, results in a 0 which is less than the limit, so the pagination immediately stops.
You can test this by entering a random variable with the count method in a Powershell window, for example: $test123.count .
Besides the pagination for the server endpoint, I also see that there is no pagination implemented for the packages endpoint. I don’t know how likely the chances are for a device to contain more than 500 packages, but the chances are there ¯\(ツ)/¯ .
I’m not that well versed in PowerShell, but the below iteration of the script should take pagination into consideration for both the server as packages endpoint:
Summary
# Set these -----------------
$apiKey = 'YOUR_API_KEY'
$orgID = 'YOUR_ORG_ID'
$cve = 'CVE-2020-0689'
$filepath = 'C:\Temp\cve.csv'
# ---------------------------
$page = 0
$limit = 500
$servers = @()
$apiInstance = 'https://console.automox.com/api/'
$apiTable = 'servers'
Set-Content $filepath -Value "Computer,display_name,version,installed"
while($true) {
$orgAndKey = "?o=$orgID&api_key=$apiKey&l=$limit&p=$page"
# Put components together
$uri = $apiInstance + $apiTable + $orgAndKey
$resp = (Invoke-WebRequest -Method GET -Uri $uri -UseBasicParsing).Content | ConvertFrom-Json | Select-Object results
$servers += $resp.results
$page += 1
if($resp.results.Count -lt $limit) {
break
}
}
$servers = $servers | Sort-Object name
# Check each server for software
foreach ($server in $servers) {
$page = 0
$serverID = $server.id
$serverName = $server.name
$packages = @()
while($true) {
$orgAndKey = "/$serverID/packages?o=$orgID&l=$limit&p=$page"
# Put components together
$getURI = $apiInstance + $apiTable + $orgAndKey
$headers = @{ "Authorization" = "Bearer $apiKey" }
$response = (Invoke-WebRequest -Method Get -Uri $getURI -Headers $headers).Content | ConvertFrom-Json
$packages += $response
$page += 1
if($response.Count -lt $limit) {
break
}
}
$packages | Where-Object {$_.cves -Contains $cve} | Select-Object @{label=”Computer”; Expression= {"$serverName"}},Display_Name,Version,Installed `
| Sort-Object Display_Name | Export-Csv -Path $filepath -NoTypeInformation -Append -Force
}
I think you did find a bug! The first loop while/do is collecting results in $resp but measuring count in $response. I did not experience this bug because I had slipped in an -or $page -gt 4 when testing as I did not want to wait for it to get through my entire org. So my loop exited successfully when others would have only run once because like you said, $response doesn’t exist so it’s automatically less that the $limit and breaks out of the loop.
I modified the if statement to look at the $resp contents instead and successfully collected all the servers in my org into $servers.
if($resp.results.count -lt $limit) {
break
}
Maybe the package collection still needs a pagination loop if a server has more packages than what the API allows to be collected in one GET request.
hello, im getting this error when running the scrip.
Select-Object : A positional parameter cannot be found that accepts argument '|'.
At line:154 char:57
+ ... ins $cve} | Select-Object @{label=”Computer”; Expression= {"$serverNa ...
When I try to run the script, it is returning an error indicating that an empty pipe element is not allowed. I am wondering if this is because the query is not returning with results for the CVE I am checking. However, I am not clear on how to determine if there is another issue.
| Sort-Object Display_Name | Export-Csv -Path $filepath
When I go back to the section for the $resp it looks like this invoke is returning a null, but I am not sure why
$resp = (Invoke-WebRequest -Method GET -Uri $uri -UseBasicParsing).Content | ConvertFrom-Json | Select-Object results
Invoke-WebRequest : Cannot validate argument on parameter 'Uri'. The argument is null or empty. Provide an argument that is not null or empty, and then try the command again.
At line:1 char:37
+ (Invoke-WebRequest -Method GET -Uri $uri -UseBasicParsing).Content | ...
+ ~~~~
+ CategoryInfo : InvalidData: (:) Invoke-WebRequest], ParameterBindingValidationException
+ FullyQualifiedErrorId : ParameterArgumentValidationError,Microsoft.PowerShell.Commands.InvokeWebRequestCommand
