A Complete Guide to Remote Utilities Host Deployment Remote Utilities is a powerful self-hosted remote desktop solution designed for IT professionals and system administrators. Unlike cloud-based alternatives, it gives you complete control over your remote infrastructure. The cornerstone of this setup is the Host, the lightweight service that runs on the target machine to allow incoming connections.
Deploying the Host efficiently across your network ensures seamless support, automated monitoring, and secure access. This guide breaks down the full deployment process from configuration to network management. Step 1: Download and Extract the Deployment Tools
Before installing the Host on target machines, you need the right installer package and configuration utilities.
Get the Host Installer: Download the standard .msi or .exe Host installer from the official Remote Utilities website. The MSI package is highly recommended for network deployment.
Get the Viewer: Download and install the Remote Utilities Viewer on your administrator workstation.
Launch the MSI Configurator: Open the Viewer, navigate to the Tools tab, and select MSI Configurator. This built-in tool allows you to pre-configure the Host installer before distributing it. Step 2: Pre-Configure the Host Installer
Using the MSI Configurator ensures that every installed Host automatically inherits your security policies, access passwords, and network routes without manual intervention. 1. Choose the Deployment Type
Open the MSI Configurator and select Standard Installation. This creates a customized installer that installs the Host as a system service, allowing you to access the remote machine even when no user is logged in. 2. Set Security and Access Control
Authentication: Select your preferred authorization method. You can use a standard Remote Utilities security password, Windows Security (NTLM/Active Directory), or custom permission groups.
Access Rights: Define what the administrator can do (e.g., full control, view only, file transfer, or screen blanking).
2FA: If using Remote Utilities security, enforce 2FA (Two-Factor Authentication) for an extra layer of protection. 3. Configure Connection Settings
Direct Connection: If the target machine has a static IP or is on the same local network, enable direct connection ports (default is inbound TCP 5650).
Internet ID (Relay) Connection: For machines behind strict firewalls or NAT routers, check the Internet ID box. This routes traffic through a mediation server.
Custom RU Server: If you run an independent Remote Utilities Server (RU Server), enter your server’s IP address or DNS name and port (default 5655) here. 4. Customize the Interface (Optional)
You can hide the Host tray icon or customize the text to prevent end-users from accidentally stopping the service or altering settings. 5. Generate the Package
Click Build. The configurator will output a tailored .msi file containing all your settings and registry keys. Step 3: Deploy the Host Across the Network
Once you have your customized MSI package, you can deploy it to target machines using one of several methods. Method A: The Built-In Remote Deployment Tool
If you are operating within a local area network (LAN), the Remote Utilities Viewer features a built-in installation tool. Open the Viewer and click Tools > Remote Deployment.
Scan your network for active machines or import a list of IP addresses. Select the target computers. Point the tool to your customized MSI file.
Provide administrative credentials for the target machines and click Install. Method B: Active Directory Group Policy (GPO)
For large-scale enterprise environments, deploying via GPO is the cleanest option.
Copy your customized MSI file to a shared network folder accessible by all domain computers.
Open the Group Policy Management Console on your domain controller.
Create a new GPO and link it to the appropriate Organizational Unit (OU).
Navigate to Computer Configuration > Policies > Software Settings > Software installation.
Right-click, select New > Package, and select your MSI file from the network share path.
Set the deployment method to Assigned. The Host will install automatically when the target machines restart. Method C: Command-Line and Scripted Deployment
If you use an RMM tool, Microsoft Endpoint Configuration Manager (SCCM), or custom PowerShell scripts, you can deploy the Host silently. Run the following command with administrative privileges: msiexec.exe /i “rut.Host7.x.x.x.msi” /qn /norestart Use code with caution. /i specifies installation.
/qn triggers a completely silent installation with no user interface.
/norestart prevents the machine from rebooting post-installation. Step 4: Network and Firewall Optimization
To ensure stable, uninterrupted remote sessions, configure your network environment to accommodate the Host traffic.
Local Firewalls: Ensure Windows Defender Firewall (or third-party antivirus firewalls) allows traffic through the required ports. The installer usually handles this automatically, but verification is key.
Port Forwarding: For direct connections outside the LAN, forward port 5650 on your router to the target Host machine.
Self-Hosted Server Routing: If using a self-hosted RU Server, ensure the target Hosts can reach the server’s IP over port 5655 (inbound to the server) and port 443 or 80 if utilizing web features. Step 5: Post-Deployment Verification
After the rollout, verify that your hosts are online and secure.
Check the Viewer: Open your Viewer console. The deployed machines should populate your address book (if you enabled automatic importing during configuration).
Test Authentication: Attempt to connect to a few sample machines to ensure your pre-configured password or Active Directory credentials grant access seamlessly.
Audit Log Activation: Ensure that the Host’s built-in event logging is active. This keeps a record of all inbound connections, file transfers, and session durations for compliance and troubleshooting.
To help refine this setup for your specific environment, let me know:
Will you be using the public Internet ID servers or hosting your own RU Server?
What deployment tool do you plan to use (e.g., GPO, PDQ Deploy, RMM, or manual)?
Leave a Reply