Category: IT (Page 7 of 11)

Ultrex LTT Partners Bid process (electrical)

November 4, 2025 / Jim Smith

🧰 Ultrex IT – Low Voltage Bid Process (Backup Vendor)

Purpose

To streamline how we gather and send information to LTT Partners (Harper Wimble’s team) or other low-voltage vendors for cable run bids—especially when no walkthrough is needed.

1. Overview

Vendor:

Company: LTT Partners (Backup Low Voltage Team)
Primary Contact: Harper Wimble – harper@lttpartners.com

Goal:
To request bids for low voltage runs (cameras, access control, etc.) without needing an on-site walkthrough by providing complete documentation, photos, and videos.

2. Preparation Before Requesting a Bid

✅ Gather Required Information

Make sure you collect and/or create the following materials:

PDF floor plans of the building
- If available, mark up with:
  - Camera locations
  - Door access control points
  - Any other wire run endpoints
Photos and videos
- Walk through each area where runs will go
- Show key locations (IDF, ceiling type, entry points, etc.)
Picture of IDF (network closet)
- Show racks, switches, and available ports
Note ceiling type (e.g., drop ceiling, drywall, open industrial)
Confirm if lift is needed (based on ceiling height or access)
Document mounting heights
- Interior cameras
- Exterior cameras
Identify system type
- Which camera or access control system is being installed (e.g., UniFi Protect, Verkada, etc.)
Doors requiring electrification
- List which doors will need power for access control
Preferred wire path runs (if known)
- Example: “Follow HVAC chase” or “Run through plenum ceiling above hallways”
Switch information
- Note if there’s an open switch port or if they’ll need to provide one
Installation hours
- Confirm if there are preferred or restricted working hours
Drilling requirements
- Note surfaces like brick, sheetrock, concrete, etc.
Device onboarding responsibility
- Confirm whether Ultrex IT or the vendor handles final setup/configuration

3. Sending the Bid Request

📧 Email Template

To: harper@lttpartners.com

Uninstall Atera agent by powershell

October 27, 2025 / Jim Smith

How to Uninstall the Atera Agent via PowerShell Script

Purpose

This article explains how to completely remove the Atera Agent (and any associated Splashtop components) from a Windows computer using a PowerShell script.

This process is typically required when:

An agent installation has become corrupted or stuck.
A device was previously managed under a different customer.
The Atera trial or old deployment needs to be fully cleaned up before reinstalling.

When to Use

Use this procedure before reinstalling the Atera Agent, particularly if:

The device shows as “Offline” or “Unmanaged” in the Atera console even though the agent is installed.
The machine was renamed or reassigned to a new customer site.
Previous uninstall attempts (via Control Panel or MSI uninstall) failed.

Steps to Remove the Atera Agent

1. Reboot and Prepare the System

Before running the script:

Rename the computer if needed (for reassignment or cleanup).
Reboot the device to ensure no agent processes are stuck.

2. Open PowerShell ISE as Administrator

Press Start, type PowerShell ISE, right-click, and choose Run as Administrator.
Create a new blank script window.

3. Copy and Paste the Uninstall Script

Paste the full script from Atera’s documentation (linked below):

👉 Atera Official Script Reference

Or use the version below (verified and compatible for Ultrex use):

Function Get-UninstallCodes ([string]$DisplayName) {
‘HKLM:SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall’, ‘HKLM:SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall’ | ForEach-Object {
Get-ChildItem -Path $_ -ErrorAction SilentlyContinue | ForEach-Object {
If ( $(Get-ItemProperty -Path $_.PSPath -Name ‘DisplayName’ -ErrorAction SilentlyContinue) -and ($(Get-ItemPropertyValue -Path $_.PSPath -Name ‘DisplayName’ -ErrorAction SilentlyContinue) -eq $DisplayName) ) {
$str = (Get-ItemPropertyValue -Path $_.PSPath -Name ‘UninstallString’)
$UninstallCodes.Add($str.Substring(($str.Length – 37),36)) | Out-Null
}}}}

Function Get-ProductKeys ([string]$ProductName) {
Get-ChildItem -Path ‘HKCR:Installer\Products’ | ForEach-Object {
If ( $(Get-ItemProperty -Path $_.PSPath -Name ‘ProductName’ -ErrorAction SilentlyContinue) -and ($(Get-ItemPropertyValue -Path $_.PSPath -Name ‘ProductName’ -ErrorAction SilentlyContinue) -eq $ProductName) ) {
$ProductKeys.Add($_.PSPath.Substring(($_.PSPath.Length – 32))) | Out-Null
}}}

Function Get-ServiceStatus ([string]$Name) { (Get-Service -Name $Name -ErrorAction SilentlyContinue).Status }
Function Stop-RunningService ([string]$Name) { If ( $(Get-ServiceStatus -Name $Name) -eq “Running” ) { Write-Output “Stopping : ${Name} service” ; Stop-Service -Name $Name -Force }}
Function Remove-StoppedService ([string]$Name) { $s = (Get-ServiceStatus -Name $Name); If ( $s ) { If ( $s -eq “Stopped” ) { Write-Output “Deleting : ${Name} service”; Start-Process “sc.exe” -ArgumentList “delete ${Name}” -Wait } } Else { Write-Output “Not Found: ${Name} service” }}
Function Stop-RunningProcess ([string]$Name) { $p = (Get-Process -Name $_ -ErrorAction SilentlyContinue); If ( $p ) { Write-Output “Stopping : ${Name}.exe” ; $p | Stop-Process -Force } Else { Write-Output “Not Found: ${Name}.exe is not running”}}
Function Remove-Path ([string]$Path) { If ( Test-Path $Path ) { Write-Output “Deleting : ${Path}”; Remove-Item $Path -Recurse -Force } Else { Write-Output “Not Found: ${Path}” }}
Function Get-AllExeFiles ([string]$Path) { If ( Test-Path $Path ) { Get-ChildItem -Path $Path -Filter *.exe -Recurse | ForEach-Object { $ExeFiles.Add($_.BaseName) | Out-Null } }}

New-PSDrive -Name HKCR -PSProvider Registry -Root HKEY_CLASSES_ROOT | Out-Null

$UninstallCodes = New-Object System.Collections.ArrayList
‘AteraAgent’, ‘Splashtop for RMM’, ‘Splashtop Streamer’ | ForEach-Object { Get-UninstallCodes -DisplayName $_ }

$ProductKeys = New-Object System.Collections.ArrayList
‘AteraAgent’, ‘Splashtop for RMM’, ‘Splashtop Streamer’ | ForEach-Object { Get-ProductKeys -ProductName $_ }

$Directories = @(
“${Env:ProgramFiles}\ATERA Networks”,
“${Env:ProgramFiles(x86)}\ATERA Networks”,
“${Env:ProgramFiles}\Splashtop\Splashtop Remote\Server”,
“${Env:ProgramFiles(x86)}\Splashtop\Splashtop Remote\Server”,
“${Env:ProgramFiles}\Splashtop\Splashtop Software Updater”,
“${Env:ProgramFiles(x86)}\Splashtop\Splashtop Software Updater”,
“${Env:ProgramData}\Splashtop\Splashtop Software Updater”
)

$ExeFiles = New-Object System.Collections.ArrayList
“${Env:ProgramFiles}\ATERA Networks” | ForEach-Object { Get-AllExeFiles -Path $_ }

$ServiceList = @(‘AteraAgent’,’SplashtopRemoteService’,’SSUService’)

$RegistryKeys = @(
‘HKLM:SOFTWARE\ATERA Networks’,
‘HKLM:SOFTWARE\Splashtop Inc.’,
‘HKLM:SOFTWARE\WOW6432Node\Splashtop Inc.’
)

$UninstallCodes | ForEach-Object { Write-Output “Uninstall: ${}” ; Start-Process “msiexec.exe” -ArgumentList “/X{${}} /qn” -Wait }

$ServiceList | ForEach-Object { Stop-RunningService -Name $_ }

$ExeFiles.Add(‘reg’) | Out-Null
$ExeFiles | ForEach-Object { Stop-RunningProcess $_ }

$ServiceList | ForEach-Object { Remove-StoppedService -Name $_ }

$ProductKeys | ForEach-Object { Remove-Path -Path “HKCR:Installer\Products\${_}” }

Remove-PSDrive -Name HKCR

$RegistryKeys | ForEach-Object { Remove-Path -Path $_ }

$Directories | ForEach-Object { Remove-Path -Path $_ }

4. Run the Script

Click the Run Script (F5) button.
Wait for it to finish — it may take a few minutes.
Review the output for any errors or missing paths.

5. Reboot the Computer

After the script completes, reboot again.

This ensures all registry keys and service entries are cleared.

6. Reinstall the Atera Agent

Once the machine has restarted:

Use the CMD installation method from Atera instead of the .MSI installer. This ensures the device correctly registers to the right customer/site in your Atera dashboard.

Example CMD install:

msiexec /i “AteraAgentSetup.msi” CUSTOMER_ID=123456 /qn

Final Notes

Always perform a reboot before and after running the script.
Confirm that all Atera and Splashtop folders are gone before reinstalling.
For stubborn removals, re-run PowerShell as Admin and execute the script again.

Setting Up RustDesk for Remote Access

October 27, 2025 / Jim Smith

Setting Up RustDesk for Remote Access

Purpose

This article shows you how to install and configure RustDesk, an open-source remote access tool. It’s used to remotely control or access client or internal computers for support or management purposes.

When to Use

Use this guide when setting up a new device for remote support via RustDesk — either for internal use (Ultrex techs) or when helping a client establish a connection for remote service.

Overview: What Is RustDesk?

RustDesk is a secure, open-source remote desktop solution that allows remote access and control of another computer. It’s a great alternative to TeamViewer or AnyDesk, providing:

Easy remote access for IT support.
Secure connections with optional 2FA.
Full desktop control from anywhere.

We’ll cover setup on both ends:

Destination computer – the system being controlled.
Source computer – the system used to connect remotely.

Step 1: Install RustDesk on the Destination Computer

Go to rustdesk.com and click Download.
You’ll be redirected to RustDesk’s GitHub releases page. Under the Windows column, download the file marked .MSI.
Once downloaded, open the file and proceed with installation:
- Click Next through the prompts.
- Accept the license agreement.
- Click Finish when done.
RustDesk will launch automatically. You’ll see your computer’s unique ID on the left-hand side — record this ID, as it will be needed to connect.

Step 2: Configure Security Settings

Set a Permanent Password

Click the three dots next to your computer’s ID and select Settings.
Go to the Security tab.
Click Unlock to enable editing.
Scroll to Password Options → select Use Permanent Password.
Create a strong, unique password (you can use passgen.co to generate one).
Enter it in both fields and click OK.

Enable Two-Factor Authentication (Optional)

Still in the Security tab, check Enable 2FA.
Scan the displayed QR code with an authenticator app (Google Authenticator or Microsoft Authenticator are both fine).
Enter the six-digit code from the app to finalize setup.

Tip: If you’re not already using an authenticator app, Google Authenticator is quick and easy to set up.

Step 3: Install RustDesk on the Source Computer

Repeat the same installation process on the computer you’ll be connecting from.

Once installed:

Open RustDesk.
In the Control Remote Desktop field, enter the destination computer’s unique ID.
Click Connect.
Enter the permanent password set earlier. Optionally check Remember password for future use.
If 2FA is enabled, enter your six-digit authentication code to complete the connection.

Tips for Reliable Remote Access

Keep the destination PC awake and online. RustDesk requires it to stay powered on and connected to the internet.
Trust devices selectively. Only check “Trust this device” on private computers — never on public or shared systems.
Be aware of visibility. Actions performed while connected are visible on the destination’s monitor if it’s on.

Troubleshooting

If RustDesk fails to connect or shows a timeout:

Ensure both devices are online.
Verify the ID and password are correct.
Restart the RustDesk service or the app on both devices.

If issues persist, Ultrex IT retainer clients can contact support for remote troubleshooting assistance.

Recap / Key Takeaways

RustDesk provides a free, secure, and simple way to connect remotely to computers — ideal for both internal management and client support. With optional 2FA and permanent password setup, it balances ease of use with strong security.

Use this setup as a standard procedure when enabling remote access for clients or internal systems.

BIOS Flash

October 27, 2025 / Jim Smith

If you have a computer that is unable to load the BIOS and won’t let you continue, you’ll more than likely need to update the BIOS via a USB Drive

Look at the manufacturer’s website (HP, Dell, Asus, etc.) and look for the make and model of the computer you’re working on.

Go to Drivers and Software and hopefully they’ll have a BIOS section.

Select the installer you need and download it

Once downloaded, run the program on any computer (like the one you did the download on) that currently works.

The program should give you the option to create a USB drive. Make sure you have a blank USB Drive or a drive you’re okay with formatting. Click start and let the program do its thing.

Once the drive is created, slap the USB drive in the computer that needs the BIOS flash and then power the computer on. It should automatically initialize and update.

Atera removed from console, need it to come back

October 27, 2025 / Jim Smith

If you delete an agent from the console, it can still be running on the client, but not show up in our dashboard. You need to delete a few registry keys then reinstall the agent of that client. This powershell script is also hosted on itstuff.ultrex.com for ease of copy/paste from target device.

Run the following fully in command line (ignore any errors). Then reboot machine, then reinstall Atera Agent.

# Stop Atera service if running

Write-Output “Stopping Atera services…”

Stop-Service -Name “AteraAgent” -Force -ErrorAction SilentlyContinue

Stop-Service -Name “AteraAgentHelper” -Force -ErrorAction SilentlyContinue

# Kill lingering processes

Write-Output “Killing Atera processes…”

Get-Process -Name “AteraAgent*” -ErrorAction SilentlyContinue | Stop-Process -Force

# Uninstall via MSI if registered

Write-Output “Checking for MSI uninstall entry…”

$msi = Get-WmiObject -Class Win32_Product | Where-Object { $_.Name -like “Atera*” }

if ($msi) {

$msi.Uninstall()

}

# Remove leftover folders

Write-Output “Removing leftover directories…”

$paths = @(

“C:\Program Files\Atera Networks\AteraAgent”,

“C:\Program Files (x86)\Atera Networks\AteraAgent”,

“C:\ProgramData\Atera Networks\AteraAgent”

)

foreach ($path in $paths) {

if (Test-Path $path) {

Remove-Item -Path $path -Recurse -Force -ErrorAction SilentlyContinue

}

# Remove registry keys

Write-Output “Cleaning registry entries…”

$regPaths = @(

“HKLM:\SOFTWARE\ATERA Networks”,

“HKLM:\SOFTWARE\WOW6432Node\ATERA Networks”,

“HKLM:\SYSTEM\CurrentControlSet\Services\AteraAgent”,

“HKLM:\SYSTEM\CurrentControlSet\Services\AteraAgentHelper”

)

foreach ($reg in $regPaths) {

if (Test-Path $reg) {

Remove-Item -Path $reg -Recurse -Force -ErrorAction SilentlyContinue

}

Write-Output “Atera agent removal complete. A reboot is recommended.”

Install Winget on machines that don’t have it

October 27, 2025 / Jim Smith

✅ Step-by-Step Installation via PowerShell

Open PowerShell as AdministratorEnsure you’re running PowerShell with administrative privileges.
Set Execution Policy (if not already set)This allows the script to run:
powershell
CopyEditSet-ExecutionPolicy RemoteSigned -Scope Process -Force

Install the winget-install Script
This script automates the installation of WinGet and its dependencies:
powershell
CopyEditInstall-Script -Name winget-install -Force
If prompted to install the NuGet provider or trust the repository, respond with ‘Yes’ or ‘Y’.
Run the Installation Script
Execute the script to install WinGet:
powershell
CopyEditwinget-install.ps1
This will download and install all necessary components, including dependencies like Microsoft.UI.Xaml and Microsoft.VCLibs.
Verify the Installation
After completion, confirm that WinGet is installed:
powershell
CopyEditwinget --version
You should see the installed version number displayed.

Extracting RST Drivers from an EXE

October 27, 2025 / Jim Smith

Extracting RST Drivers from an EXE

**************************************************************************

* 6. INSTALLING THE SOFTWARE

**************************************************************************

6.1 General Installation Notes

a. If you are installing the operating system on a computer configured for RAID or AHCI

mode, you may pre-install the Intel(R) Rapid Storage Technology driver using the

“F6” (Load Driver) installation method described in section 6.3 below.

b. If you’re installing the operating system on a computer configured for ‘Intel(R) Smart

Response Technology’ or ‘System Acceleration with Intel(R) Optane(TM) Technology’, you

must pre-install the Intel(R) Rapid Storage Technology driver using the

“F6” (Load Driver) installation method described in section 6.3 below. The Intel(R) RST pre-OS version must support the Intel(R) RST technology that you are installing to.

c. To install Intel(R) Rapid Storage Technology from within the OS during runtime,

double-click on the self-extracting and self-installing setup file and answer all

prompts presented.

6.2 Intel(R) RST Windows Automated Installer*. Installation from HDD, USB, or CD-ROM

Note: This method is applicable to computers configured for RAID or AHCI mode.

a. Obtain the Intel(R) Rapid Storage Technology setup file name: SetupRST.exe and

double-click to self-extract and to begin the setup process.

b. The Welcome window appears. Click ‘Next’ to continue.

c. For systems running in RAID mode, the Uninstallation Warning window appears. You will

not be able to uninstall the driver in this mode. Click ‘Next’ to continue.

d. The Software License Agreement window appears. If you agree to these terms, click the

check box then click ‘Yes’ to continue.

e. Select the check box to install Intel(R) Optane(TM) Memory and Storage Management application if required then click ‘Next’ to continue.

f. If the Windows Automated Installer* Wizard Complete window is shown without a prompt

to restart the system, click ‘Finish’ and proceed to step “g”. If it is shown with a

prompt to restart the system, select ‘I want to restart my computer now.’

(selected by default) and click ‘Finish’. Once the system has restarted, proceed to

step “g”.

g. To verify that the driver was loaded correctly, refer to section 7.

6.3 Pre-Installation of INTEL(R) RST driver using the “Load Driver” Method.

a. Extract driver files from SetupRST.exe:

– Open terminal in the directory with SetupRST.exe by right-clicking the directory

and selecting “Open in Terminal” or “Open PowerShell here”

– Enter the following command:

./SetupRST.exe -extractdrivers SetupRST_extracted

b. Copy all driver files from the SetupRST-extracted to a USB key media.

c. For Microsoft Windows OS*:

– During the operating system installation, after selecting the location to install

Windows, click ‘Load Driver’ to install a third party SCSI or RAID driver.

d. When prompted, insert the USB media and press Enter.

e. Follow the prompts and browse to the location of the installation files. Select the

appropriate ‘.inf’ file (64 or 32 bit). If a supported controller is detected there

will be no error message. Follow prompts to continue and complete the installation.

How to Install Applications for clients using Atera (like office)

October 27, 2025 / Jim Smith

Overview / Purpose

This article explains how to install software—such as Microsoft 365 Apps, Adobe Reader, or other common programs—on client computers using the App Installer feature within Atera RMM.

This process allows Ultrex technicians to remotely deploy software without needing to manually connect to the device or log into the user’s session. It’s especially useful when onboarding new systems, setting up replacements, or resolving missing software issues.

When to Use This

Use this process when:

A client needs Microsoft 365 or another standard software package installed remotely.
You are preparing new or reimaged machines.
You are missing software on a workstation and want to reinstall it silently through Atera.

Do not use this for:

Complex or custom software that requires license keys or user interaction during installation (these should be handled manually or via a custom script).

Steps to Install Software from Atera’s App Installer

1. Log into Atera

Go to https://app.atera.com and sign in with your Ultrex admin credentials.
From the left-hand sidebar, navigate to Devices.

2. Select the Client and Device

Find the correct Customer in the device list.
Click on the specific device you want to install software on.
Verify that the agent is online before proceeding.

3. Open the App Installer

In the device view, click the “Manage” tab (or the “Actions” dropdown depending on the view).
Select App Installer from the available options.

4. Choose the Software to Install

Browse the list of available apps. Atera maintains a catalog of common programs including:
- Microsoft 365 Apps (Office)
- Google Chrome
- Adobe Acrobat Reader DC
- Zoom
- 7-Zip
- VLC Media Player
Click Install next to the application you want.

Tip: You can install multiple applications by queueing them up one after another.

5. Monitor the Installation

Once triggered, the installation begins automatically in the background on the client device.
You can view progress or check logs under the Activity Log or Agent Console Output in Atera.

6. Confirm the Installation

After a few minutes, verify that the software appears in the device’s Installed Applications list within Atera.
Optionally, connect via Splashtop or remote session to visually confirm the program is installed and functional.

Notes and Best Practices

The App Installer works best on Windows devices with the Atera Agent online and administrative privileges enabled.
If an install fails, review the Atera event logs or attempt a manual install using PowerShell or a deployment script.
For Microsoft 365 installations, ensure the user has a valid license assigned in Microsoft 365 Admin Center before installation.

Wrap-Up / Recap

Using the App Installer in Atera streamlines software deployment—saving time and avoiding unnecessary remote sessions. This tool should be your first stop for installing standard apps like Office, Chrome, or Reader.

If the installer fails or the application is not listed, escalate to a manual installation or package deployment script as needed. Always confirm completion by checking the installed software list.

How to export emails from Microsoft Purview

October 27, 2025 / Jim Smith

How to export emails from Microsoft Purview

Raised from ticket #2038

If you need to export emails from a Microsoft 365 tenant using the Microsoft Purview compliance portal, follow these steps:

Step 1: Assign eDiscovery Permissions

Ensure your account has the necessary permissions by adding it to the eDiscovery Manager role group.
In the Microsoft Purview compliance portal, navigate to Permissions > Email & collaboration roles > Roles, and select the eDiscovery Manager role group.
Add your account to the eDiscovery Administrator list. NOTE: You need to have Business Premium / Office E3 or higher to allow for actual eDiscovery exports.
Verify that the Export role is assigned to this role group.
Note: Changes in permissions might take up to 24 hours to apply.

Step 2: Create a Content Search

In the compliance portal, go to Content search and select New search.
Provide a name and description for the search.
Under Locations, enable Exchange mailboxes and select the mailboxes you wish to export.
To export all emails, leave the Conditions section empty.
To export only a specific date range, add a Condition for “Received” and select before, after, or between certain dates
Submit the search and wait for it to complete.

Step 3: Export Search Results

Once the search is complete, select it from the list and choose Export results.
In the export options:
- Under Output options, select All items, including ones that have unrecognized format, are encrypted, or weren’t indexed for other reasons.
- Under Export Exchange content as, choose One PST file for each mailbox and can likely leave the default selections. Read them carefully though.
Start the export process. Note: This can take over an hour to export depending on the size of export you’re doing.

Step 4: Download the Exported PST Files

After the export job is prepared, navigate to the Exports tab in the compliance portal.
Select your export job and copy the Export key.
Click Download results, which will prompt you to install the eDiscovery Export Tool if it’s not already installed.
In the eDiscovery Export Tool, paste the export key and specify the download location on your local computer.
Initiate the download to retrieve the PST files.

How to Add Shared Mailboxes in Outlook

October 27, 2025 / Jim Smith

How to Add Shared Mailboxes in Outlook

Purpose

This article explains how to add a shared mailbox in both Outlook.com (web) and the Outlook mobile app.
You’ll typically need to do this when you have access to a departmental or team mailbox (for example, info@, support@, or billing@) and need to view or send emails on its behalf.

Adding a Shared Mailbox in Outlook.com (Web Version)

Sign in to your Outlook.com account.
In the left folder pane, right-click on Folders and select Add shared folder.
Enter the email address of the shared mailbox.
Click Add.

✅ Result: The shared mailbox will now appear in your folder list, usually under your personal mailbox folders. You can read, send, and manage emails based on the permissions assigned.

Adding a Shared Mailbox in the Outlook Mobile App (iOS/Android)

Open the Outlook app on your mobile device.
Tap the profile icon (top-left corner).
Tap the gear icon to open Settings.
Scroll down and select Add Mail Account → Add a Shared Mailbox.
Enter the shared mailbox email address and tap Add Shared Mailbox.

✅ Result: The shared mailbox will now appear alongside your personal mailbox in the account list.

Final Notes

Make sure your account has been granted access to the shared mailbox by an administrator before attempting to add it.
If the mailbox does not appear after adding it, try restarting Outlook or removing and re-adding your account.