Category: IT Knowledge Base Articles (Page 7 of 11)

Install Winget on machines that don’t have it

✅ Step-by-Step Installation via PowerShell

  1. Open PowerShell as AdministratorEnsure you’re running PowerShell with administrative privileges.
  2. Set Execution Policy (if not already set)This allows the script to run:
    powershell
    CopyEditSet-ExecutionPolicy RemoteSigned -Scope Process -Force
  1. 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’.
  2. 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.
  3. 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

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)

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

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

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)

  1. Sign in to your Outlook.com account.
  2. In the left folder pane, right-click on Folders and select Add shared folder.
  3. Enter the email address of the shared mailbox.
  4. 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)

  1. Open the Outlook app on your mobile device.
  2. Tap the profile icon (top-left corner).
  3. Tap the gear icon to open Settings.
  4. Scroll down and select Add Mail Account → Add a Shared Mailbox.
  5. 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.

How to Export Microsoft Teams Chats Using Microsoft Purview (eDiscovery Premium)

How to Export Microsoft Teams Chats Using Microsoft Purview (eDiscovery Premium)


Purpose of This Article

This guide explains how to export Microsoft Teams chat conversations using the Microsoft Purview Compliance Portal through the eDiscovery (Premium) feature.

You’ll need this process when:

  • A client or internal request requires archived Teams conversations for review or compliance.
  • You’re performing legal discovery, HR investigations, or internal audits.
  • Teams data must be preserved or exported in a readable format (such as PDF or native message files).

Step-by-Step Instructions

1. Access the Microsoft Purview Compliance Portal

  1. Open a browser and go to: https://compliance.microsoft.com.
  2. Sign in with an admin or compliance account that has eDiscovery Manager or Administrator permissions.

2. Create an eDiscovery (Premium) Case

  1. In the left-hand navigation, go to eDiscovery (Premium).
  2. Select + New case.
  3. Give the case a clear name and description (e.g., “HR Chat Review – October 2025”).
  4. Click Save to create the case.

3. Add Custodians (Users) to the Case

  1. Open the case you just created.
  2. Navigate to the Data sources tab.
  3. Click Add custodians.
  4. Search for and select the users whose Teams chats you need to export.
    • When you add custodians, their connected data sources (mailboxes, OneDrive, etc.) are automatically linked to the case.

4. (Optional) Apply a Legal Hold

If you need to preserve data to prevent deletion:

  1. Select the custodians you added.
  2. Click Apply hold.
  3. Confirm which data sources (Exchange, OneDrive, etc.) to include.
  4. Apply the hold.
    • This ensures that even deleted messages are retained for the duration of your investigation.

5. Create a Collection for Teams Chats

  1. Go to the Collections tab within your case.
  2. Click + New collection.
  3. Define your search parameters:
    • Locations: Select Exchange mailboxes (Teams messages are stored there).
    • Query: To target Teams messages, use kind:im OR kind:microsoftteams
  4. Run the search to estimate how many items match.
  5. When satisfied, save the collection.

6. Add Search Results to a Review Set

  1. From the search results, choose Add to review set.
  2. This allows you to view Teams conversations in a threaded (chat-style) layout.
  3. Name the review set and click Add.

7. Export the Teams Chats

  1. In the Review sets tab, open the review set you created.
  2. Select the conversations you wish to export.
  3. Click Export.
  4. Configure your export options:
    • Export entire conversations as PDFs or individual chat messages as separate files.
    • Choose whether to include metadata or transcripts.
  5. Start the export.
  6. Once complete, download the export package from the Exports section to your local system.

Final Notes

  • Licensing: eDiscovery (Premium) requires Microsoft 365 E5 or a similar add-on license. Ensure your tenant has access before starting.
  • Permissions: The user performing this task must have the eDiscovery Manager role in Purview.
  • Storage Location: Teams chat exports are derived from Exchange mailboxes, not from Teams directly—this is by design.

Summary

Exporting Teams chats through Microsoft Purview ensures compliance, transparency, and legal defensibility. By following these steps—creating a case, adding custodians, collecting chat data, and exporting—you can retrieve Teams conversations safely and in a reviewable format.

Finished Result: You’ll have a downloadable export (PDF or file set) of Teams chat conversations, properly preserved and ready for review or recordkeeping.

Defederate Steps from GoDaddy to MS365

A few things to do first. Make sure you can login with the godaddy admin account to Portal.Azure.com
And change the password for the “admin@net…..” account. This will be your new admin account to login into MS365

1. PowerShell Execution Policy:

Problem: By default, PowerShell often blocks running scripts.

Check: Run Get-ExecutionPolicy in PowerShell.

Solution: If it shows “Restricted,” run Set-ExecutionPolicy Bypass -Scope Process.

This temporarily allows scripts to run in the current PowerShell session.

2. Install Microsoft Graph Module:

Run: Install-Module Microsoft.Graph -Scope CurrentUser -Repository PSGallery -Force in PowerShell (as administrator).

Wait: This may take time. Wait until it returns to the system prompt.

3. Run the De-federation Script:

Run the provided script from the blog post. 

https://docs.tminus365.com/configurations/godaddy/defederating-godaddy-365

Here is the primary Script to run

Write-Host “Checking for MSGraph module…”

$Module = Get-Module -Name “Microsoft.Graph.Identity.DirectoryManagement” -ListAvailable

if ($Module -eq $null) {

        Write-Host “MSGraph module not found, installing MSGraph”

        Install-Module -name Microsoft.Graph.Identity.DirectoryManagement

    }

Connect-MgGraph -Scopes “Directory.Read.All”,”Domain.Read.All”,”Domain.ReadWrite.All”,”Directory.AccessAsUser.All”

#Enter the Admin credentials from “Become a tenant Admin in GoDaddy”

Get-MgDomain

#See that the domain is “federated”#

Update-MgDomain -DomainId “<InsertFederatedDomain>” -Authentication Managed

Prompts:

You might be asked about allowing network paths and untrusted modules.

Answer “Yes” or “Yes to All” to these prompts.

You will be asked to enter your godaddy admin credentials.

Action: The script will change the domain from “federated” to “managed.”

Note – Don’t close Powershell yet!

4. Post-Script Actions:

Log in to the Microsoft 365 admin center.

Remove GoDaddy from the partner list.

Reset all the logins for the users.

Remove Global Admin from any account not freshly created during this process.

Assign proper licenses for users- often they’ll come over with only exchange online licenses. 

When all is done. Run Disconnect-MgGraph  in powershell. This will disconnect from the domain so the computer can do a different migration without issues. 

Windows Protected Print Mode: Disable to Fix Print Drivers not Installing by TCP/IP

Microsoft has made an update in Windows 11 in an update. Windows 11 version 24H2.

Windows Protected Print Mode (WPP) is a driver‑free, security‑focused printing mode in Windows that relies solely on the modern IPP (Internet Printing Protocol) stack and Mopria‑certified printers—eliminating third‑party drivers.

This eliminates the ability to use print drivers that don’t use IPP and makes TCP/IP unavailable completely. 

Microsoft as started to enable this by default on some newer PC’s.

If you have any print drivers that fail to install check here

Settings>Bluetooth and Devices>Printers and Scanners. Make sure it’s off.

Admin Username and Password for Copiers

Machine Password List

Kyocera Passwords:

Newer models:

User Name: Admin

Password: Admin
-OR-

First two numbers of the model number followed by two zeros:

Example: CS-5551ci would be:

User Name: 5500

Password: 5500

EPSON Passwords:

For WF-C879R:

Username: Admin

Password: Admin
Other Epson’s models – Customer Create their Own Password

Toshiba Passwords:

User Name: Admin

Password: 123456

The network password is also 123456.

NOTE: These OKI Machines have the same passwords as Toshiba: MPS4242, MPS 3537, MPS5502, ES9465 & ES9474

OKI Passwords:

User Name: admin

Copier interface Password: aaaaaa (the letter ‘a’ six times) -OR-

Password: 123456

Web interface Password: 000000 (6 zeros)

NOTE: These OKI Machines have the same passwords as the Toshiba: MPS4242, MPS 3537, MPS5502, ES9465 & ES9474

Older Models: 2530, 3530, 4030, 3035, 4035, 5035, 2525C, 3225C, 4035C admin password 6482 (We don’t change)

Older Model: 3050, 4050, 5050 admin login and password are both 5050

Older Models: 250, 300, 400, 500 admin password is the model and add a zero. (Password for 250ci is 2500)

Older Models: 550, 650 admin password is 123456

None of the copiers have admin passwords for the command center (web interface) except the 250, 300, 400, 500 the admin password is admin00.

CS-420i the admin password is admin00.

« Older posts Newer posts »

© 2026 Ultrex Staff

Theme by Anders NorenUp ↑