Endpoint Network Threat Protection

I need a solution

Hi all,

I have had an issue with Backup Exec 20.5 failing on one Windows 2012 R2 server where it loses connectivity to that server and fails. The other 2 servers backing up are ok. I traced it back to Endpoint Protection Version 14 and the Network Threat Protection. If I disable that in Endpoint on the backup server and the remote server that is failing the backup works. Any ideas how to fix network threat protection so I can run it again on both servers and backup successfully? Am I able to put a network threat protection firewall exception in for those two servers to get it to work again? If someone could step me through what to add and where in the firewall settings that would be great!






  • No Related Posts

Starting March 1, 2019, Bay Area Systems Will Begin Providing It Support Services on the Latest …

SAN FRANCISCO (PRWEB)February 23, 2019

Bay Area Systems, Inc. (http://www.BayAreaSystems.com), premier Information Technology (IT) consulting provider in San Francisco Bay Area, is on the forefront of providing cost-effective IT outsourcing solutions for small businesses.

Starting March 1, 2019, Bay Area Systems will begin providing IT support services on the latest Microsoft Server: Windows Server 2019. Through utilization of Microsoft Windows Server 2019’s native Hyper-V virtualization technology, Bay Area Systems helped deployed web server farms, clustered database servers, remote desktop workstations, and cloud computing platforms. When businesses need Virtual Private Network (VPN) access and remote desktop services; rather than adding individual workstations to be used for remote office desktop connection needs, virtual workstations offer the same experience with greater efficiency. Clients praise our virtual machine solutions that are space saving (often one server can serve the needs of 10 – 30 servers and/or workstations, reducing the need to have these physical machines scattered around in the office); energy saving in terms of electricity needs as well as cooling requirements; easy deployment – adding a server or workstation is much faster than having to order an additional machine, and often may not be of the same exact specification; fast recovery – by utilizing the cloning feature, essential virtual machines can be cloned and quickly replaced should a catastrophic software error occurred.

Microsoft Windows Server 2019’s Server Core App Compatibility feature on demand (FOD) significantly improves the app compatibility of the Windows Server Core installation option by including a subset of binaries and components from Windows Server with the Desktop Experience, without adding the Windows Server Desktop Experience graphical environment itself.

Windows Defender ATP Exploit Guard is a new set of host-intrusion prevention capabilities. The four components of Windows Defender Exploit Guard (Attack Surface Reduction (ASR), Network protection, Controlled folder access, Exploit protection) are designed to lock down the device against a wide variety of attack vectors and block behaviors commonly used in malware attacks, while enabling you to balance security risk and productivity requirements.

Microsoft Windows Server 2019’s Security with Software Defined Networking (SDN) delivers many features to increase cutstomer confidence in running workloads, either on-premises, or as a service provider in the cloud.

Windows Server 2019 also has a new Storage Migration Service that makes it easier to migrate servers to a newer version of Windows Server. It provides a graphical tool that inventories data on servers, transfers the data and configuration to newer servers, and then optionally moves the identities of the old servers to the new servers so that apps and users don’t have to change anything.

Hyper-V virtual server provides one of the most stable platforms for virtual machines, and the multitude of tools available making cloning, clustering and failover available to support critical business needs. The time it takes to restore a cloned Microsoft Exchange Server in Hyper-V could be as little as 2 hours, compared to having to rebuild a physical server, reinstall Operating Systems and Exchange Server, setup accounts, and can easily take 6 to 8 hours and thousands of dollars. In Windows Server 2019, you can now add NIC on the fly without taking down the server.

Bay Area Systems have fully tested and deployed Hyper-V solutions to solve customers’ growing needs of testing new Operating Systems as well as program upgrades. It is much more convenient, and cost-effective, to use a virtual machine to test system integration, software upgrades, patches, and new installations before deploying into the production environment. Efficient resource sharing and distribution in Hyper-V also ensure a much better performance for individual virtual machines than purchasing separate physical units.

The combination of cutting-edge, professional services of Bay Area Systems and production proven virtual machine solutions provided by Microsoft’s Windows Server 2019 will serve to deliver energy saving, cost-effective, cutting-edge, fast and complete services to Bay Area Systems customers.

Since 2002,Bay Area Systems has provided cost-effective computer systems and network support and services to small businesses all around the San Francisco Bay Area. Bay Area Systems LLC has become a pioneer in providing customized technology solutions that are efficient, cost-effective, and improve bottom line of small businesses. Bay Area Systems’ business model is based on their passion to provide the best customer service experience in the industry, and building long-term business relationship with their customers.


SCOM R2 doesn’t work: SDK Service isn’t initialized

In this case we need to stop all SCOM R2 services on the RMS and the Health Service on the MS servers. Since SQL wasn’t working either with the filled log files for the SCOM R2 databases and it’s a dedicated SQL server,we need to restart the SQL engine so everything is fresh.

First action item is to give more space to the log files of both SCOM R2 databases, just a couple of GBs per log file, but just enough to perform the task.

  1. Open SQL Server Management Studio, log on to the correct instance, select the SCOM R2 database, right click it and select Properties;
  2. Go to the second page on the left (Files) and adjust the file size of the log file by incrementing it with a couple of GBs;
  3. Click OK and the change will be applied right away;
  4. Repeat this action for the other SCOM database as well.

Now the log files have some space again so the can ‘breath’. Now it’s time for the second action, backing up the SCOM R2 databases. When you don’t add space to the log files, you’ll get this error when trying to backup the SCOM R2 databases:

User-added image

In SQL Server Management Studio:

  1. Right click the SCOM R2 database, select Tasks and the option Back Up;
  2. Backup the database to a file location and select the on the page Options under the header Reliability the option Verify backup when finished;
  3. Let the backup job run by clicking OK and wait until it’s finished;
  4. Repeat this action for the other SCOM database as well.

Now we have valid backups of both SCOM R2 databases, so there is a way back when things fail.

Since SCOM R2 was installed in such a manner to facilitate the full Recovery Model of both SCOM R2 databases (not enough disk space nor enough I/O power for having a smooth running SCOM R2 environment) we need to change the Recovery Model back to Simple for both SCOM R2 databases:

In SQL Server Management Studio:

  1. Select the SCOM R2 database, right click it and select Properties;
  2. Go to the fourth page on the left (Options) and adjust the Recovery Model of the database to Simple;
  3. Click OK. Now the Recovery Model will be set back to Simple;
  4. Repeat this action for the other SCOM database as well.

Now the log files of both SCOM R2 databases are still huge but they’re almost empty. Perfect time for some shrinking of the size of the databases! Before that it’s better to run a backup again of the databases. Also make sure the shrink actions will land properly.

In SQL Server Management Studio:

  1. Select the SCOM R2 database, right click it and select Tasks > Shrink > Files;
  2. Make sure for File Type to select Log;
  3. Under the header Shrink Action select the option Reorganize pages before releasing unused space. Shrink File to: xyz MB (minimum is 0 MB);
  4. Select a proper file size (not too big since the Recovery Model is Simple);
  5. And click OK. This can take some minutes, depending on the size and speed of the SQL server;
  6. Repeat this action for the other SCOM database as well.

Now all is well again and SCOM will operate smoothly again AFTER the SCOM R2 services are started of course on the RMS and MS servers.


7021037: How to Update GWAVA 6

To update GWAVA 6 follow the instructions below:

1. Enter the GWAVA Management Console by typing in the iIP address of the server followed by :49282.

2. Click on System Management – System management – Online Updates

3. Check the Version history to see if any updates are available for your server.

4. Click on Submit Update Request

This will proceed to download the latest version of GWAVA 6 from the GWAVA server.

Note: Proxy servers and firewalls may hinder the online update and will fail in downloading the new version. Be sure to allow port 80 on your firewall and if needs be you may enter in the proxy information within the Proxy Configuration on the server configuration page.

If your server does not have an internet connection, have a look at this article to perform a manual update.

5. When the update is completed you will see a screen that will prompt you to restart GWAVA.

6. Restart GWAVA:

How To Restart GWAVA on Linux

How To Restart GWAVA on Windows


7920904: System Requirements for PlateSpin Recon

Recon 3.6 Server:

NOTE: Running PowerRecon v3.1 or lower in a virtual machine is not supported by PlateSpin. However, PowerRecon v3.2 and higher are supported. See below for more information on running Recon in a VM.

  • Windows 2003 Server (SP0, SP1, SP2) – English, French and German
  • Windows 2008* (SP0)

* User Access Control (UAC) should be turned off on Windows Server 2008. See page 10 of the Recon User Guide for detailed instructions on disabling UAC.

Note: PlateSpin Recon is not supported on WOW64 (Windows-on-Windows 64-bit) or any other 64-bit Operating System.


  • PostgreSQL 8.3.4 (included with Recon 3.5)
  • PostgreSQL 8.2.x and 8.3.x
  • Microsoft SQL Server 2000 (SP3A+)
  • Microsoft SQL Server 2005


  • Microsoft IIS 5.0/6.0 (with ASP.NET)
  • Microsoft .NET Framework 3.5
  • Microsoft Data Access Components (MDAC) 2.6

Note: Please ensure that Microsoft IIS is installed before installing Microsoft .NET Framework 3.5.

Recommended Hardware

Monitoring 1 to 250 servers:

  • 2 GB memory
  • Physical Machine: Pentium 4, 2.8 GHz with hyperthreading or better
  • Virtual Machine: 1 vCPU
  • 20 GB free disk space

Monitoring 250 to 2000 Servers

  • 4 GB memory
  • Physical Machine: Xeon, 2.8 or 3.2 GHz dual core or multi-processor
  • Virtual Machine: 2 vCPUs
  • 100 GB free disk space

Note: Disk space requirements will depend on the number of servers being monitored and the duration for storing summary and raw utilization data. If using a SQL Server database which is on a remote server, ensure that there are 2GB of allocated space on that server. Disk space requirements are based on 30 days of monitoring. At least one CPU core per 750 monitored servers is recommended.

Scale Limits for running on a physical server

Number of inventoried workloads


Number of monitored workloads


Scale Limits for running in a virtual machine

Recon 3.6 only supports running in VMware ESX 3.x virtual machine

Number of inventoried workloads


Number of monitored workloads

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

  • Document ID:7920904
  • Creation Date:05-APR-07
  • Modified Date:01-AUG-17
    • NetIQPlateSpin Recon

Did this document solve your problem? Provide Feedback