It seems like your browser didn't download the required fonts. Please revise your security settings and try again.
Barracuda RMM
formerly Managed Workplace

Configuring WMI Devices - On Premise

  • Last updated on

Unless configured to use another account, the Onsite Manager Windows services will use the default log on account named MWService, created during installation, to scan the network. Depending on the type of network, this will require different actions to be taken.

Domain Networks

On Domain networks, the account is created as a Domain Administrator, so that it can access all Windows devices attached to the Domain. If installing in a Domain, then the Windows service account is created within Active Directory for Windows-based monitoring and management. Domain Policy settings, which help enable monitoring within a Domain environment, can be found in the Site Management section of Service Center.

To access the Domain Configuration Guide, click here.

Workgroup Networks

On Workgroup networks, the account is created locally on the Onsite Manager server, and also needs to exist as a Local Administrator on each Windows device in the Workgroup. This user must have exactly the same logon and password as that on the Onsite Manager server, and the password must be set to never expire.

If installing in a Workgroup, then the Windows service account is created locally on the Onsite Manager, but you must run the Workgroup Preparation Utility on all the devices you want managed.

The Workgroup Preparation Utility can be run from the Site Management section of Service Center, which creates the user (and makes other changes required for monitoring) with a single click, minimizing setup time for Workgroup devices.

Mixed Domain-Workgroup Networks

Barracuda RMM requires a service account (administrative user) to authenticate against and monitor the devices in your network. Depending on your network configuration, configure Barracuda RMM as follows:

  • If installing in a hybrid (mixed) environment, and you install on a computer that has access to the Domain, then the Windows service account is created within Active Directory for Domain-based Windows devices. You only have to run the Workgroup Preparation Utility on all Workgroup-based devices.
  • If installing in a hybrid (mixed) environment, and you install on a computer that does not have access to the Domain, then you must run the Workgroup Preparation Utility on all managed devices (because the Windows service account cannot be created if Active Directory cannot be accessed).

This configuration limits monitoring of Domain Controllers to availability and SNMP because Windows does not allow the required local User account to be created.

For ease of use, it is recommended that you install the Onsite Manager on a server that is a member of the domain and not a domain controller.

Creating a Workgroup Prep Utility
  1. In Service Center, click Configuration > Site Management.
  2. Click the site for which you want to run the utility.
  3. Click the Resources tab.
  4. In the Workgroup Resources section, click Download Workgroup Prep Utility.
  5. Click Save and select the location where you want to save the Workgroup Prep Utility.
Running a Workgroup Prep Utility
  1. Extract the following file on each Workgroup device that needs to be configured.
    LPIWorkgroupPrep_<om site name>_yyyy-mm-ddThh:mm:ss.zip
    For example: LPIWorkgroupPrep_myOmsitename_2009-05-28T13:01:01.zip
  2. From the extracted location, double click the omsiteprep.exe file.
    When complete, a dialog box opens stating if the site preparation was successful.
  3. Click OK.

The utility generates a log file in the current working directory named OASiteprep.log, which contains a detailed report of all changes and errors.

The site preparation process:

  1. Checks if Barracuda RMM site preparation has been run before.
  2. Checks the type of platform (Window OS) since some site preparation tasks are dependent upon the OS version.
  3. Creates a Barracuda RMM service account. Updates the password if the account already exits.
  4. Starts and configures dependent system services, if required.
  5. Configures and enables WS-MAN and WMI, if required.
  6. Configures UAC options on Windows 8.1 and later versions of Windows Operating Systems.
  7. Configures all firewall profiles regardless of whether the firewall is enabled. This includes allowing ICMP echo; remote administration, file and print sharing, and remote desktop services; and ports required for WMI and Barracuda RMM applications.
  8. Logs all changes to file and update registry with record of execution.