Monitorpack Guard can be used as agent and / or proxy, you can monitor server or workstation on which it is installed, you can also monitor
everything that has an IP address on the same network from this single server or PC. You can combine these configurations as functions of your infrastructure.
Supervision (agent mode) in an Active Directory forest.
Monitoring (agent mode) and remote (proxy mode) in an Active Directory forest.
Supervision (agent mode) in a DMZ or a workgroup.
Supervision (agent mode) and remote (proxy mode) a DMZ or a workgroup.
Supervision (agent mode) in a DMZ or a workgroup from an Active Directory forest.
Monitoring (agent mode) and remote (proxy mode) in a DMZ or workgroup from an Active Directory forest
Download latest version of MonitorPack Guard
here https://www/MonitorPack/en/start-monitorpack-guard-en.php, install MonitorPack Guard by default.
Once MonitorPack Guard is installed you must change the MonitorPack Guard shortcut on the Windows desktop as follows:
Right-click > [Properties] > [Compatibility] tab > select the [Run this program as administrator] check box in [Privilege Level] > click [OK].
(Optional), download a package or contact us for any application, unzip the file
and replace Schedule.mdb file in the "C:\Program Files (x86)\MonitorPack
Guard\Databases\" folder.
Your server or PC is now supervised with the chosen Pack, your first logs will be visible after five minutes, you can then, add as many alerts as you want, the pack will be incremented by your new alerts.
The installation is identical to the agent mode, the difference lies in the choice of the service account, which this time must have an Active Directory forest or Workgroup scope.
The MonitorPack solution works with the Windows MonitorPackEngine service.
This is the Windows service account that is declared for the Windows "MonitorPackEngine" service that must have rights, for Agent mode the installation works with the default local system account.
In an Active Directory forest and for Proxy mode only,
the Windows account used for the MonitorPackEngine Windows service must
have local administrator rights on the remote computers. The easiest
way is to use the Domain Administrator account, which is by default
in local administrators' group for all servers or workstations in your
Active Directory forest. You can also create a service account such
as "svc_monitorpack" in your Active Directory forest and integrate this
account into the "built-in group" domain administrator, so you can disable
this account when you stop working. use MonitorPack.
Data Execution Prevention (DEP)
is a security feature that helps prevent damage from viruses and other security threats
by monitoring your programs to ensure they use system memory safely. It also blocks non-Microsoft editors running on the machine.
1. Select Start> Control Panel.
2. Click System Security.
3. Click Advanced System Settings.
The System Properties dialog box appears.
4. Click the "Advanced" tab.
5. Click the Settings button. The Options dialog box
performance is displayed.
6. Click the Data Execution Prevention tab.
7. Select "Enable run prevention
data for Windows programs and services only »
8. Click OK twice and finish.
Enable .NET Framework 3.5
yourself through the Panel
configuration. In Control Panel, choose Programs
and features, choose Turn Windows enable or disable
functionality, and then check the .NET Framework 3.5 box (includes
.NET 2.0 and 3.0).
Local Rights Restriction (UAC)
Once MonitorPack installed, you must reduce the security level of the UAC to “Never notify” or run MonitorPack Guard as administrator,
otherwise you will have an incorrect behavior of the application.
Data Execution Prevention (DEP)
is a feature
security that helps prevent damage from viruses
and other security threats by monitoring your programs in order to
make sure they use the system memory safely. he
also blocks non-Microsoft editors running on
the machine, it also blocks the execution of non-Microsoft software.
1. Select Start> Control Panel.
2. Click System Security.
3. Click Advanced System Settings.
The System Properties dialog box appears.
4. Click the "Advanced" tab.
5. Click the Settings button. The Options dialog box
performance is displayed.
6. Click the Data Execution Prevention tab.
7. Select "Enable run prevention
data for Windows programs and services only »
8. Click OK twice and finish
Enable .NET Framework 3.5
yourself through the Control Panel
configuration. In Control Panel, choose Programs
and features, choose Turn Windows enable or disable
functionality, and then check the .NET Framework 3.5 box (includes
.NET 2.0 and 3.0).
Local Rights Restriction (UAC)
Once MonitorPack installed, you must reduce the security level of the UAC to “Never notify” or run MonitorPack Guard as administrator,
otherwise you will have an incorrect behavior of the application.
On all servers and PCs to supervise
Servers and PCs to supervise where MonitorPack Guard is not installed
(Proxy mode).
The MonitorPack Guard service account used for the MonitorPackEngine
Windows service must be integrated into the local group "Logbook users".
performance "(PLU) or PMU group" monitor users and "Administrator"
local group of all remote machines to be supervised.This can be done
per server or from a Active Directory GPO.
The remote registry service must be started on every computer that
you remotely monitor in automatic mode.
From Windows 7 versions for workstations and from of Windows 2008
for servers the approach is to create a key registry "LocalAccountTokenFilterPolicy"
(GPO to execute a only once per Active Directory forest or on each
machines in a context of Workgroup) to give the service account svc_Monitorpack
the right to supervise and inventory remotely in a secure manner,
so this relates to remote machines or MonitorPack is not directly
installed (Proxy mode).
Allow Remote Administration (GPO to run once only by Active Directory
forest and on each machine in context from Workgroup).
The site on which MonitorPack Guard and / or MonitorPack Asset are installed must be allowed to connect to port 25 of the server whose IP address we provide during your subscription.
The site on which MonitorPack Guard and / or MonitorPackAsset are installed must be allowed to connect to port 1433 of the server whose IP address we provide during your subscription.
MonitorPack will allow and manage secureity for 20 fixed public IP addresses for an SA-2 offer with dedicated server.
To update local machine's firewall rules with MonitorPack's needs:
Execute the script named MonitorPack_Firewall.vbs located in C:\Program Files (x86)\MonitorPack Guard\Tools.
No need of messaging server!, we provide you with a dedicated SMTP gateway in SaaS mode.
MonitorPack Deployment.