New in IT Portal 4.6.41 · Q4 2026
Overview
For years, the fastest way to get a client's environment into IT Portal has been the Portal Agent: download it, run it on a domain machine, and watch servers, PCs, sites and networks appear. That agent was written in VBScript - a technology Microsoft is retiring from Windows.
In IT Portal 4.6.41 the agent has been rebuilt from the ground up in PowerShell. It does everything the old agent did, adds a few things it never could, and is ready for the next generation of Windows.
What it imports
From a single machine on the domain, the new agent documents your client's Active Directory for you:
- Servers and PCs — including full inventory collected remotely: operating system, hardware, disks, network adapters, installed software, services, shares, scheduled tasks and more.
- Sites and IP networks — so your client's locations and subnets are documented too.
- Contacts — with names, phone numbers, addresses and notes from AD.
- Security group memberships — your portal users are added to the matching security groups in IT Portal.
Prefer to deploy per machine? The same PowerShell agent runs from your RMM or a Group Policy Object, with each device reporting its own inventory.
Why it matters
- Future-proof. PowerShell is built into every supported version of Windows. No more depending on a scripting engine that is on its way out.
- No duplicates. Computers are matched by their Active Directory identity, not just their name, so a renamed machine is updated in place instead of appearing twice. Records you have already imported are skipped by default, keeping repeat runs fast and clean.
- Works where the internet does not. If the agent cannot reach your portal — an isolated network, a strict firewall — it saves everything it collected to a single file. Upload that file in the portal later to complete the import.
- Fewer moving parts on the network. Remote inventory works on machines that do not run the Remote Registry service, so more of the environment gets documented on the first pass.
- Set it and forget it. The first interactive run schedules itself, and the agent also supports fully unattended runs for automation.
How it works
- Open the device import screen in IT Portal, name the agent and choose the company it belongs to.
- Pick your options — such as lower-case device names, importing machines that are currently offline, or refreshing devices you have already imported.
- Download the PowerShell agent and run it on a machine in the client's domain.
- Choose what to import, and let the agent do the rest.
The classic VBScript agent is still available as a fallback while you transition, so nothing about your existing process breaks.
Getting started
The new agent is available now in IT Portal 4.6.41, and PowerShell is the default choice on the import screen. For step-by-step setup, scheduling and troubleshooting, see the knowledge base article Importing Active Directory with the PowerShell Portal Agent.
See everything else in this release in the IT Portal 4.6.41 release notes.
Onboarding a new client should take minutes, not days. The new agent gets their environment documented — and keeps it that way.
