Paul

Hi everyone,
I wanted to share a simple PowerShell script that you can use within Pulseway Automation to remotely eject any USB storage devices connected to a system. This can be helpful for security-conscious environments or in scenarios where USB usage needs to be tightly controlled.
Works well in combination with the Disable USB Storage Access script in the built in category.
 
The script uses Shell.Application to trigger the native "Eject" action for removable drives (DriveType = 2). Here's the version that loops through all mounted USB volumes:
✅ Works great in Pulseway automation tasks 💡 You can modify it to eject a specific drive letter if needed powershell # Eject all USB volumes using Shell.Application COM object $Eject = New-Object -ComObject Shell.Application # Get all removable (DriveType = 2) volumes with drive letters $volumes = Get-WmiObject -Class Win32_Volume | Where-Object { $_.DriveType -eq 2 -and $_.DriveLetter } foreach ($vol in $volumes) { Write-Host "Ejecting drive $($vol.DriveLetter)..." $Eject.NameSpace(17).ParseName($vol.DriveLetter).InvokeVerb("Eject") }  
Notes:
During my testing, I've seen that USB devices will not be removed if a process is running from the disks in question.
In other words, if there is a write/read process running, the disk is not ejected.
 
Let me know if you have questions or enhancements!

Hey @Leroy,
Do you have an Application Crash event in the Application Windows Event Log?
-Paul

@Jerdal, I cannot locate your email by date nor by address hence why I need your email headers to identify the message IDs and see if our email provider has received it. In the meantime, just PM me your instance name, username and the last 4 digits on the credit card on profile.
-Paul

Hi Jayden,
Refer to this forum post:
-Paul

The Pulseway service runs scripts under the local SYSTEM user. You will probably need to load the correct user registry and make changes there.
-Paul

The Pulseway service runs scripts under the local SYSTEM user. You will probably need to load the correct user registry and make changes there.
-Paul

Hello everyone,
We're investigating the issue and will come back with an update as we hear back from the development team.
-Paul

We have identified the issue and have released the Windows Agent version 9.3.1 with the fix. This seems to be localized to users who have never set up global rules through the WebApp.
We apologize for the inconvenience caused.
-Paul

Update: The database server has finished loading all the databases and the service is now restored.
-Paul

Nobody likes such situations but everyone's frustration is warranted. We keep asking our hosting provider for an ETA but we haven't received any so far.
Our DR committee is evaluating the time it would take to restore the service in a failover DC.
-Paul

Hi there,
Apologies for this. Our hosting provider is running overtime on their scheduled maintenance.
I'll post another update when the service is back up.
-Paul

Hi Tyler,
Thank you for the report. We've managed to identify the issue and we're working on a fix as we speak.
-Paul

Hi Tyler,
Thank you for the report. We've managed to identify the issue and we're working on a fix as we speak.
-Paul

I have recently built a similar script but mine doesn't ignore NPCAP, feel free to issue a pull request to change it: https://github.com/paulcsiki/pulseway-scripts/blob/main/enroll-network-interfaces/enroll-network-interfaces.ps1
-Paul

Yes Josh, apologies again. The root cause of the issue is impacted disk I/O where the SAN has experienced multiple disk failures at the same time greatly reducing I/O capacity. We'll announce tomorrow a maintenance window for the window where we will transition to a SSD-backed SAN which will greatly increase the performance of our cluster.
Update: 5:14PM - We're down again. We've decided to switch to the new storage now.
Update: 5:50PM - We're 20% done with the move to the new storage, we anticipate another 2 hours before we can restore service.
Update: 6:24PM - 69% done with the move.
Update: 6:58PM - Move completed successfully, databases are starting up.
-Paul

Yes Josh, apologies again. The root cause of the issue is impacted disk I/O where the SAN has experienced multiple disk failures at the same time greatly reducing I/O capacity. We'll announce tomorrow a maintenance window for the window where we will transition to a SSD-backed SAN which will greatly increase the performance of our cluster.
Update: 5:14PM - We're down again. We've decided to switch to the new storage now.
Update: 5:50PM - We're 20% done with the move to the new storage, we anticipate another 2 hours before we can restore service.
Update: 6:24PM - 69% done with the move.
Update: 6:58PM - Move completed successfully, databases are starting up.
-Paul

Hi there,
You'd keep the double quotes in the script.
-Paul

Excellent, glad to hear you've managed to get it installed.
-Paul

Hey @TimStark,
Please PM me the details and I'll work with you on getting it done. We do not provide any way of removing archived notifications within the product but we can organize an once-off exception for you to permanently delete the data but we'll need to go through a couple of steps, including identity verification.
-Paul

Hi there,
If you have configured the Autotask integration from the Integrations page in the WebApp, you do not need to configure it again within endpoint policies. You get to pick which RMM Organizations, Sites and Agent Groups will forward notifications into tickets from the integration page.
-Paul

I figured out my own problem.  I had uninstalled the app prior.  But the Service was still active in the list, hanging out.  I installed Autoruns to find the file and eliminate it.

Once it was gone, I downloaded the other Pulseway installer I had found in the list.  It finally installed all the way and I just logged into our server manually.  It's working now.

Hi there,
At this moment it's not possible to override the default notification priority from the user support request.
-Paul

Hi James,
A system is considered as offline when you receive the offline notification. For the Professional product that is about 10 minutes after the agent stops communicating with the Pulseway Cloud Servers and for the Enterprise product this interval can be customized.
-Paul

Thanks for the continued support Nick! You rock !
-Paul

Hi there,
We have released an agent update (v8.9.1) which addresses this issue. The update will reach all systems within 48 hours.
-Paul