In this File
- Whatsup Gold Linux
- Whatsup Gold Free Edition
- Whatsup Gold 16.1 Cracked
- Whatsup Gold 16.1 1 Full Download Crack
This video shows how to install Whatsup Gold Network Monitoring software.Please find the WUG release notes at below link:http://docs.ipswitch.com/NM/WhatsUpG. WhatsUp Gold Log Management provides easy visibility and management of device log data – all integrated into an easy-to-use, industry-leading interface. You can monitor, filter, search and alert on syslogs or Windows logs for every device in your network while also watching for meta trends like log volume changes.
Release information
Product name | WhatsUp Gold |
Version | v16.1 Service Pack 1 (v16.1.1) |
Release dates | April 11, 2013 |
New in WhatsUp Gold v16.1 Service Pack 1
WhatsUp Gold 16 1 1 Full Crack Download Free. WhatsUp Gold Premium is the solution one needs for real-time network monitoring of large IT infrastructures. WhatsUp Gold provides complete visibility.
This is a WhatsUp Gold v16.1 Service Pack 1 release. For more information, see Defects resolved in WhatsUp Gold 16.1 Service Pack 1 (v16.1.1).
Defects resolved in WhatsUp Gold 16.1 Service Pack 1 (v16.1.1)
Defect ID | Category | Issues |
16010 | Alert Center | Corrected Alert Center notifications that were prevented from continuing to repeat Step 3 if the Alert Center process was restarted while Step 3 was active. |
16587 | Discovery | Corrected an issue that could cause a discovery service process error: 'System.IO.InvalidDataException' while discovering certain devices. |
17528 | Passive Monitor | It is now possible to perform a text comparison on the Community Name and Protocol Version fields of an SNMP Trap passive monitor event. |
18988 | Alert Center | Alert Center thresholds set to 'Exceeds' now goes out-of-threshold at the proper value. |
19152 | Polling | The IP address information in a wireless database table is no longer updated if the IP address of a client device changes. |
19558 | Interface Traffic | The Flow Monitor Host Search feature now displays the proper interface on which the traffic was present when searching for host devices. |
19922 | Alert Center | Changes to an Alert Center notification policy now correctly take effect if the policy was already active at the time of the change. |
20623 / 21381 | Installation | Upgrading WhatsUp Gold no longer overwrites a custom Windows account configured for the NmConsole virtual directory and NmConsole application pool if the account is configured within IIS. |
20650 | Export | Fixed an issue that could cause unsupported Wireless devices to appear in the Wireless browser. |
21041 | Polling | Replaced the SSH library used by SSH Active Monitor and SSH Performance Monitor for improved stability with the NmPoller.exe process. |
21089 | Active Monitor | HTTPS monitors in Windows 2008 that caused the following error message: 'The request was aborted: Could not create SSL/TLS secure channel,' have been corrected. |
21115 | Discovery | Adjusted the aggressiveness of duplicate device detection during device discovery. Previously, if any IP address on the incoming device existed in the database (including secondary IP addresses of devices), the devices would be merged. In version 16.1.1 and later, only the primary IP address of the incoming device is compared to only the primary IP addresses of devices in the database. |
21116 | Dashboard Views/ Reports | The 'Devices with Down Critical Active Monitors' dashboard report now displays devices in a user-created custom monitor device state. |
21152 | RemoteDBConfig | To help alleviate script timeout errors on systems with limited resources, default ASP script timeout was increased from 90 seconds to 5 minutes. |
21341 | Service | If using the 'Poll Using Hostname' feature, the IP address of the device within the Device |
21342 | Discovery | The 'Use SNMP sysName' option is now respected even if the 'Resolve host names' option is selected during device discovery. |
21382 / 23466 | Map View / Web UI | Corrected an issue that could cause the wrong group information to display in the navigation ribbon when selecting a device from the Map View or Down Active Monitors dashboard report. Corrected an issue that could cause the wrong group information to display in the navigation ribbon when selecting a device from the Map View dashboard report. |
23472 | Wireless | Resolved an issue that could prevent certain Wireless configurations from being discovered properly. |
23514 | Reports - General | Corrected a database stored procedure that could cause a 'duplicate primary key (PK)' error in the Tail of State Change Timeline dashboard report. |
23545 | Active Monitor - Ping | Corrected an issue that could cause active monitor polling to stop after exporting a topology from WhatsConnected to WhatsUp Gold. |
23615 | Credentials | Devices exported from WhatsConnected or WhatsConfigured that have SNMPv3 credentials attached now correctly export their credentials. |
23631 | Discovery | Monitors attached to roles, based on default Ipswitch 'Windows roles,' are now assigned during device discovery. |
23648 | Polling | Wireless polling and monitoring now collect client usage statistics from Aruba Wireless |
23652 | Performance Monitor | Corrected an issue that caused custom SNMP Performance Monitors whose OID configuration included a leading or trailing period to fail with an 'Object reference not set to an instance of an object' exception. |
23657 | Email Action | E-mail actions triggered by events other than incoming Passive Monitor events now scrub any %PassiveMonitor percent variables from the message subject and body. |
23660 / 23740 | Email Action | Corrected an issue that prevented multiple recipients from being specified for an e-mail action. Delimiters now include semi-colon (;), comma (,), and the [SPACE] character. Multiple, contiguous delimiters (for example ',;' are treated as one delimiter. |
23677 | Actions | Percent variables in the System namespace will now properly resolve instead of returning an 'Invalid percent variable' message. |
23751 | Application Profile | WhatsUp Gold now imports all Ipswitch authored APM plug-in application profiles during installation for an improved user experience. |
System Requirements
Operating system and virtual environment requirements
This service pack does not require or introduce changes to the v16.1 operating system and virtual environment requirements.
Database requirements
This service pack does not require or introduce changes to the v16.1 database requirements.
Web server requirements
This service pack does not require or introduce changes to the v16.1 web server or Microsoft IIS requirements.
Framework and accessibility requirements
Whatsup Gold Linux
This service pack does not require or introduce changes to the v16.1 framework and accessibility requirements.
Web and mobile interface requirements
This service pack does not require or introduce changes to the v16.1 web and mobile interface requirements.
WhatsVirtual supported virtual environments
This service pack does not require or introduce changes to the v16.1 WhatsVirtual supported virtual environments.
Wireless supported devices
This service pack does not require or introduce changes to the v16.1 wireless supported devices.
Flow Monitor software requirements
This service pack does not require or introduce changes to the v16.1 Flow Monitor requirements.
Poller Requirements
This service pack does not require or introduce changes to the v16.1 poller requirements.
Installing WhatsUp Gold
Note: WhatsUp Gold v16.1.x Service Pack x supports direct upgrade installations from WhatsUp Gold v14.x or v15.x.
This release is a full install and may be installed without first installing WhatsUp Gold v16.1. Refer to the Installing and Configuring WhatsUp Gold guide for details about installation, upgrade, repair and uninstall.
Configuring ELM Reports for WhatsUp Gold
WhatsUp Gold version 15.0 and later provide integration with the Event Log Management central database. For access to ELM reports and data, you must also have ELM products, specifically WhatsUp Event Archiver and/or WhatsUp Event Alarm, configured to send collected log data to a MS SQL Server. WhatsUp Gold accesses report data through stored procedures in the ELM database. For more information, see Using ELM Reports in Ipswitch WhatsUp Gold v16.1 Service Pack 1.
Troubleshooting
Potential SQL Server Express installation errors
- DO NOT Use Terminal Services or Remote Desktop for the installation.
- Check other services that may be running and stop these services during the install operation. These services include:
- Microsoft SQLServerAgent (for the '
WhatsUp
' instance) - Microsoft COM Transaction Integrator
- Microsoft Distributed Transaction Coordinator (MS DTC)
- Microsoft Message Queuing
- Microsoft Search
- MSSQLServerOLAPService
- Microsoft SQLServerAgent (for the '
- If there was a previous, non-default installation of WhatsUp Gold or WhatsUp Professional that has been removed, a 'WhatsUp' Data Source (DSN) may still exist. Remove the WhatsUp DSN from the Data Sources (ODBC) Control Panel and restart the install.
- There are known issues with installing WhatsUp Gold on a domain controller, therefore installing WhatsUp Gold on a domain controller is not a supported install scenario.
Configuring the firewall to allow WMI traffic
WhatsUp Gold uses Windows Management Instrumentation (WMI) to monitor and restart Windows Services. For each device that is assigned an NT Service Active Monitor, you must supply the Windows credentials. Also, when creating a Service Restart Action, you must supply Windows credentials for each Action. Credentials must have administrative permissions on the remote server. Local accounts with credentials that match remote accounts are no longer required to monitor remote servers.
Whatsup Gold Free Edition
Credentials are configured in the WhatsUp Gold Credentials Library and used in several places throughout WhatsUp Gold. They can also be associated to devices in Device Properties > Credentials, or through Bulk Field Change for Credentials.
Whatsup Gold 16.1 Cracked
The use of WMI could have some implications if target devices are behind a firewall. To successfully monitor and/or restart NT Services, you need to modify firewall settings so that:
- The RPC port (135) is open for connections.
- The DCOM port range is defined and open for connections.
For more Troubleshooting information, see the Troubleshooting section in the application Help or User Guide.