|
|
   |
 |
           |
 |
  |
 |
|
                      |
 |
AppMetrics Resource Center - FAQ's Background — answers "what" Installation— answers "how" SQL Server | SCOM | W2K8 | .NET | VMWARE Product Comparisons — answers "why" 
Background What types of applications does Xtremesoft's AppMetrics monitor? Which platforms are supported by AppMetrics? What part of Windows does AppMetrics monitor? Are source code modifications required? How do I access AppMetrics on my network? Does AppMetrics integrate with my existing enterprise management system? How much load does the AppMetrics agent place on my application server while in production? Can I detect component memory leaks with AppMetrics? Installation How can I use AppMetrics to handle hung components and applications? How does AppMetrics allocate percent of CPU in a monitored multi-processor server? When running reports for the first time I get an error "no data from machine has been loaded". How do I control the size of the AppMetrics databases? What kinds of credentials do I need with AppMetrics? How can I use AppMetrics between two domains that don't share a Trust Relationship? How can I use the Custom Component notification feature of AppMetrics? Do you have Sample reports I can look at? SQL Server | SCOM | W2K8 | .NET | VMWARE Can AppMetrics be used with SQL Server 2008? Can AppMetrics be used with SQL Server 2005 Express? Does AppMetrics support Windows Server 2008? What are .NET Serviced Components? Can AppMetrics help me as I begin to migrate to .NET? Does AppMetrics report correctly when VMWare is in use on a server? Product Comparisons Can you differentiate Xtremesoft's AppMetrics from Identify's AppSight for me? Why do I need AppMetrics if I already have Application Center 2000? Older Issues Does AppMetrics SNMP alerting share the same vulnerabilities listed in CERT Advisory CA-2002-03 How does AppMetrics work with a workgroup instead of a domain? When I try to start up the monitor I am getting an error that tells me "Access Denied"?
Background Xtremesoft AppMetrics is a product designed to manage, monitor and measure applications. Depending on the stage of an application's lifecycle, AppMetrics will deliver statistical information (metrics) that provide an early warning system, production reports, diagnostics and capacity trends for COM+-built applications. What types of applications does Xtremesoft's AppMetrics monitor? AppMetrics monitors applications that are running as COM+ server or library applications. These applications can be packaged applications written in-house or by third parties. The applications must be registered with COM+, but need not be marked as "Transactional". To track aborted transactions, one must mark the component as "Transactional" however. Which platforms are supported by AppMetrics? AppMetrics currently supports the following operating systems (listed by AppMetrics component); AppMetrics Manager, Console, and Reports:
AppMetrics Agent:
What part of Windows does AppMetrics monitor? AppMetrics focuses on the logic tiers of multi-tier applications. Typically, a three-tier application has a web browser in the first tier, business logic in a middle tier, and a database or legacy system as the third tier. Unlike system monitoring products, AppMetrics examines what's happening with the application. Instead of obtaining metrics on system data such as network traffic, AppMetrics helps you assess how successfully your business is being transacted by monitoring the activities of components registered with COM+. Are source code modifications required? No modifications to the application are required for COM+ or MTS components. For .Net Serviced Components, some attributes may need to be set to public in order for those components to be monitored. These are minor changes. Please refer to the .Net Serviced Component guidelines in the Installation Guide (Chapter 6, page 41) for more information. How do I access AppMetrics on my network? AppMetrics provides an Microsoft Management Console (MMC) user interface, making it accessible remotely on your network. System management information is easy to access, easy to understand, and most importantly, easy to act upon. Does AppMetrics integrate with my existing enterprise management system? AppMetrics can be used as an integral part of your enterprise management architecture and strategy. The product integrates seamlessly with most commercially available enterprise application frameworks. For those using NetIQ AppManager for system management, AppMetrics offers out-of-box integration allowing them to use the AppManager Console to alert, report, and store data for important mission critical metrics. Users developing in-house management solutions can integrate with AppMetrics by querying against a fully documented database schema. How much load does the AppMetrics agent place on my application server while in production? Xtremesoft AppMetrics utilizes an Agent/Manager architecture that is designed to minimize impact on system resources. The AppMetrics Agent resides on the COM+ server, where it collects data and routes it to the AppMetrics Manager. We have surveyed customers, and they report little impact from the AppMetrics Agent on their production applications. The AppMetrics Manager resides on a separate machine, away from production servers. The AppMetrics Manager undertakes the data analysis, alerting, reporting and interpretation functions on its own, non-production machine. When diagnostic detail is required, an authorized user can increase the amount of data the AppMetrics Agent collects in a controlled manner, one component at a time. The impact on the system during problem resolution can vary significantly, depending on the number of users, the number of components, and the relative length of each method call to the mix of calls. However, by ensuring precise control, problems are resolved efficiently while the impact to the system is low. Can I detect component memory leaks with AppMetrics? Yes. This is the process used to detect component memory leaks:
--> Charts for Applications that are leaking should display a linear rise. Installation How can I use AppMetrics to handle hung components and applications? Instructions for how to handle Hung Components and Applications What networking protocols does AppMetrics need to function? Will AppMetrics communication work across a firewall? AppMetrics uses the DCOM (Distributed COM) protocol to communicate. It is necessary to open up the DCOM Service Control Manager port 135, along with a specified range of dynamic ports in order for AppMetrics to communicate between the manager and agent properly. The dynamic range depends on how many monitors you wish to use, and whether or not you intend to use another application which makes use of DCOM. Here are some guidelines on what you need to do in order to ensure the proper connectivity between the AppMetrics manager and agent machines, along with the number of dynamic ports you'll need to open in relation to the number of monitors you wish to run:
I have received the error "These console files saved with an earlier version of the MMC, do you want to update to MMC version 1.2 format?" What should I do? This error indicated that your MMC is a newer version than that in which AppMetrics created its MMC files. These MMC files were created in an older version to meet ‘lowest common denominator’. Click the OK button to this message, because there is no reason not to upgrade. How does AppMetrics allocate percent of CPU in a monitored multi-processor server? AppMetrics will average the CPU utilization across all processors in the server. For example, if AppMetrics determines that package/application Foo is using 60% of one processor in a two-processor server configuration, it will average this utilization across all processors (i.e. divide by two) to yield a CPU percentage value of 30%. When running reports for the first time I get an error "no data from machine has been loaded." What happens is the agent collects the data and sends it over to the manager, which keeps the collected data in log files. The default to upload this data into SQL Server is every fifteen minutes. If you would like to see this data sooner you can go to the "Logging Options" in the user interface of the monitor in question. There is a button called "Upload the AppMetrics Log files to the Database Now". If you click this button then all the data collected up to that point would then be uploaded into the SQL Server database. When running a Production Monitor and having the detail at "component" or "component and method", how come I can't see any data for transactions or components with COM+? One thing to look at is whether the components of your application supports events and statistics. In order to do this you have to go into component services on the agent machine and open up the application that you are monitoring. Open up the components in that application, and right click a component and go into the properties. There is an "activation" tab. click on that and then check to make sure the "components supports events and statistics" is checked. If it is not check it and click "apply". This change will not take effect until your application is shutdown and restarted. How do I control the size of the AppMetrics databases? There is no easy answer to this question. The size of your database depends on what is being monitored, for how long, how many applications, how many components per application and the detail requested. The eventing system generates a massive number of events per physical transaction, sometimes of the order of ten to one, so the only answer is to focus the requests as tightly as possible. Our field techs are experts in helping you in this area. In general the lower detail results in smaller volumes of data. So that:
The Diagnostic monitor collects all it can for everything it is monitoring and cannot be changed. In general time control is the major control. Each one of these is a contributor to the size of your database In the configuration of the monitors (Production and Diagnostic) you can configure the database for how many days of data to keep in the database. Once the data has reached that limit then the oldest days data will be purged from the database before the new days data is uploaded. At that time the database should not change in size and should be consistent. Xtremesoft suggests collecting data for a specified amount of time to get an idea of how YOUR monitoring will affect the size of your database and then plan accordingly What kinds of credentials do I need with AppMetrics? You can use either Windows or SQL Authentication for db operations. You will be asked during setup for either Windows or SQL authentication credentials to set up the SQL Server environment. You will also be asked during setup for a password for the ‘AppMetrics’ user, which will be a SQL account. The AppMetrics SQL account is used during db operations. For this reason, SQL Server must be set up for Mixed Authentication to work with AppMetrics. The AppMetrics service itself runs as a Windows service, and needs Windows credentials. The service account does not need to be a domain account, but it is much easier if it is. The service account needs to be in the AppMetrics Administrators Group on the AppMetrics Manager machine and the AppMetrics Agent machine (where the COM+ components are). How do I access a AppMetrics database from another machine that is behind a firewall if I want to run AppMetrics reports remotely? We use ADO to access the report data from SQL Server. As such, the following MSDN article may help you configure your firewall in order to allow you to connect to your AppMetrics manager database from outside the firewall. How To Use ADO to Connect to a SQL Server That Is Behind a Firewall Is there any alternative gui from excel like a web client? Or excel reports that we can distribute to stakeholders? There are ways to embed Excel objects into a web client. Microsoft’s FMStocks example code shows how to go about embedding Excel objects into ASP pages. As far as AppMetrics reports, you can easily bring up the AppMetrics.xls report file by opening the file in Internet Explorer. A URL to the file can be hyperlinked from a webpage and opened as long as the client has MS Excel installed, and there is connectivity to an AppMetrics database. Additionally, report data can be stored in the AppMetrics Excel report file, and viewed by dismissing the report dialog and navigating the report tabs. How can I use AppMetrics between two domains that don't share a Trust Relationship? Typically, the AppMetrics Manager and the AppMetrics agents run on computers in the same domain, or in separate domains that have a Trust Relationship. Occasionally, there is a desire to have the Manager and Agents in different domains, where those domains do not have a Trust Relationship. In the latter case, follow these steps: The local Administrator account needs to be used as the run as account for the AppMetrics service, and the user needs to logon as the Administrator in order to run AppMetrics When installing AppMetrics have the AppMetrics service run as that local user that you just created with administrator rights. Make sure that the local user is in the AppMetrics Administrators group on both the Manager and Agent machines. How can I use the Custom Component notification feature of AppMetrics? AppMetrics comes with a sample component already configured to respond to alerts. This feature is described in the AppMetrics documentation in Chapter 3, Page 36. The sample component is called XSNotification.wsc, and it is in this subdirectory: yourdrive:\Program Files\Xtremesoft\AppMetrics for Transactions\ The work done by the sample component is purely for illustration purposes – it writes out the parameters that have been passed to it into a log file (c:\xsnotificationLogFile.log). The work that you want the component to do is customizable by you There is a sample vbscript that demonstrates interacting with COM+ published by Microsoft here: The work you want done is sometimes on the application server, where your application and our agent reside. In that case, the component that the AppMetrics Manager invokes will in turn need to invoke a script on the application server machine. There is a discussion of that on MSDN: Do you have sample reports I can look at? You can find an Overview of Sample Reports here. When I try to create a monitor with AppMetrics I get the error: Create database for monitor "monitor_name" failed. What should I do? Check the name of the monitor you are trying to create It is possible that the name is reserved in SQL such as "asc" and "desc". Try another name for the monitor. SQL Server | SCOM | W2K8 | .NET | VMWARE Can AppMetrics be used with SQL Server 2008? Yes, both the 32-bit and 64-bit versions of SQL Server 2008 are supported. In order for AppMetrics to function correctly with SQL Server 2008, the following SQL Server 2008 feature needs to be selected at install time or added by running SQL Server setup in maintenance mode.
Additionally, the Microsoft SQL Server 2005 Backward Compatibility Components package needs to be installed once the SQL Server Client Tools Backward Compatibility feature has been successfully added. SQL Distributed Management Objects (SQL-DMO) and the Data Transformation Services (DTS) runtime are located in this package, and are necessary for the proper operation of AppMetrics. The package is available on the SQL Server 2008 installation DVD, as well as from the Microsoft SQL Server 2008 Feature Pack webpage, located at the following link: Microsoft SQL Server 2008 Feature Pack Scroll down to the section entitled "Microsoft SQL Server 2005 Backward Compatibility Components". Select the appropriate link, depending on whether you are using 32-bit or 64-bit SQL Server 2008, and run the install file, SQLServer2005_BC.msi. After accepting the license, the install program will display a screen. Ensure that the Data Transformation Services 2000 runtime and SQL Distributed Management Objects (SQL-DMO) items are selected. The other components are optional, and may be deselected if so desired. Continue the install by clicking the Next button and following the remaining instructions given in the setup program. Once finished, AppMetrics can then be installed. How to change Server Role settings for the AppMetrics user account in SQL Server 2000 and Server 2005? Instructions for how to change SQL Server Role Settings Can AppMetrics be used with SQL Server 2005 Express? Yes. In order for AppMetrics to function correctly with SQL Server 2005 Express, the Microsoft SQL Server 2005 Backward Compatibility Components package needs to be installed prior to the installation of AppMetrics. (Note: Please ensure that TCP/IP is enabled on the SQL instance you will be using for AppMetrics, as TCP/IP is disabled by default and needs to be enabled in order for AppMetrics to connect.) Also, AppMetrics runs with both a named and default instance. Usually on a named instance, TCP/IP is enabled by default, but it is still probably a good idea to check the named instance to verify that TCP/IP is enabled. The package is available from the Feature Pack for Microsoft SQL Server 2005 webpage, located at the following link: Feature Pack for Microsoft SQL Server 2005 Scroll down to the section entitled "Microsoft SQL Server 2005 Backward Compatibility Components", and run the install file, SQLServer2005_BC.msi. After accepting the license, the install program will display a screen. Ensure that the Data Transformation Services 2000 runtime item is selected. The other components are optional, and may be deselected if so desired. Continue the install by clicking the Next button and following the remaining instructions given in the setup program. Once finished, AppMetrics can then be installed. The DBAs want to keep control over all of the SQL Server Databases - how can I accommodate them and use AppMetrics? Overview The AppMetrics Manager needs to have a SQL Server or SQL Express database present locally (on a local drive) when it is installed. It is an integral part of the AppMetrics Application and is used for a variety of purposes and has to be local for data integrity purposes. We'll look at the following AppMetrics configurations:
Option 1: Install the AppMetrics Manager on a machine already running SQL Server.
Here you would do all the reporting from the AppMetrics Manager machine and the remote workstations. Option 2: Download and install SQL Express (free from Microsoft) on the machine which will be used as the central AppMetrics workstation, or install full SQL Server onto it if large database sizes are expected. This keeps all of AppMetrics off of the production DBservers. This is the optimal configuration, since there is no impact on production data integrity or performance. You can then set up security as desired without impacting the production environement. The AppMetrics data comprises stored events and timings which are particular to AppMetrics. There is no customer or important internal data collected as such.
Here you would use SQL Express for the AppMetrics Manager machine and take the DBServer out of the process and be able to run reports from the AppMetrics Manager machine and the User's machine. Option 3: You would use the DBServer as the database repository for AppMetrics, but could move the database at specific times over to the AppMetrics Manager machine and do all the reporting from that machine and the User's machine.
Option 4: If you have a cluster configuration, all drives in the cluster are considered local drives. AppMetrics can be located on any clustered machine and use a database resident on another machine within the cluster. If I want to send AppMetrics alerts to SCOM, does each machine running the AppMetrics agent, require a Management License for SCOM? We think the answer is yes from April 1, 2007. Effective April 1, 2007, Microsoft is implementing changes to the definition of "manage" that will broaden the requirements for Management Licenses and ensure consistency across products that work with System Center products. Purchases of any System Center products after this date will be subject to this new definition of manage, which is as follows: For purposes of this paragraph, to “manage” a device means to
You do not need a management license for any of your devices
This effectively means that no matter how information about any device on a network gets into a System Center product’s management data repository, that device will require a Management License, except for servers licensed to run the System Center product’s management server software, or devices functioning only as network infrastructure devices (OSI layer 3 or below). Does AppMetrics support Windows Server 2008? Yes. Xtremesoft will continue to support new Microsoft OS's and architectures as they are deployed by our customers. We expect Windows Server 2008 to advance Microsoft’s success in the enterprise, support of it is therefore a priority for Xtremesoft. Why don’t I see the Client IP or ASP URL in the AppMetrics Reports with ASP.NET applications? I saw them with my ASP applications. The implementation of ASP.NET is quite different from the implementation of ASP. There is more integration between ASP and COM+ than there is between ASP.NET and COM+. As a result, there are no COM+ Identity Events fired when ASP.NET is calling COM+ applications. AppMetrics depends on these COM+ events in order to report the Client IP and ASP URL. Why don’t I see any activity when monitoring one of my COM+ Applications that uses .NET Serviced Components? For Server Applications: For .NET Serviced Components, some attributes may need to be set to public in order for those components to be monitored. These are minor changes. Please refer to the .NET Serviced Component guidelines in the Installation Guide (Appendix B: Page 44) for more information. For Library Applications: Microsoft has confirmed that there is an issue with Library Applications implemented with .NET Serviced Components when more than one such Library Application is executed under the same process. The responsible Microsoft team has filed a design change request for Vista to address this issue. Note: This issue does not arise with .NET Serviced Components deployed as COM+ Server Applications. So that your application can be managed, we recommend that you either use Server Applications instead of Library Applications for your .NET Serviced Components or use unmanaged code for your Library Application. If you have only one Library Application being executed, then follow the process for Server Applications. What are .NET Serviced Components? Click here to find out. Can AppMetrics help me as I begin to migrate to .NET? Yes
Does AppMetrics report correctly when VMWare is in use on a server? All reporting functions appear to be correct, though we do not warranty on this platform as we are not be in control of the internals of a third party product. AppMetrics is an ideal way to measure the applications "before" and "after" performance after an implementation of VMWare. The following may be of interest in this process: Background Assuming the server (Before and after) are running the same application, with a similar load then the only performance difference is that the server is now running one to six VMWare virtual machines. As a reference, this blog points to how processing is degraded over multiple VMWare machines. Our comments: We believe that the AppMetrics timings are accurate and that you are simply observing what would be expected from an application running on a six-way virtual machine. A virtual machine shares actual hardware resources on the physical machine with not only the physical machine itself, but with the other virtual machines running on that system. It is normal for processing times to increase since there is less actual CPU time available than when running by itself directly on the physical machine. The processing time would be directly proportional to the number of virtual machines running on any one physical machine. Our conclusion: AppMetrics is simply showing the real degradation of your application caused by utilizing one to six virtual machines. Remember one physical and six virtual machines result in a total of 7 slices of the CPU and associated overhead. Showing you how an application, at its core, is impacted by server/OS/code changes is one of the major values of AppMetrics. The document above shows how performance is adversely affected with each additional VM instance and we believe that AppMetrics is simply showing you what you would expect. AppMetrics is performing its role in identifying the degradation in performance. Product Comparisons Can you differentiate Xtremesoft's AppMetrics from Identity Software's AppSight for me? Sometimes AppSight is mistakenly believed to provide the same capabilities as Xtremesoft’s AppMetrics, when in fact, the two products solve very different and separate problems. AppMetrics focuses on the quantity, quality and performance of the Business Transactions that are taking place within a production application, with the goal of keeping that application running longer than it would without the software being present. (Incidentally, it does this job very well!) It alerts you when transactions are either failing, slowing down, or when there are too many transactions occurring at one time for the system to handle. AppMetrics does this by monitoring your COM+ components and then producing metrics representing these business transactions. Identity Software's product is targeted at tracing application crashes. AppSight collects an application's system level interactions and creates a recording of all these low level operations. It enables a programmer to analyze what was going on when the crash occurred. Additional software also allows you to ‘playback’ what has happened. AppSight is development focused - it helps you trace the execution of the application through its interaction with system level operations. In a production environment transactions can utterly fail without anything resembling an application crash even occurring. If, for instance, your credit card processing vendor’s system is running very slowly, or is not responding, this could cause a business transaction to fail. However, this is clearly a very serious and business critical application issue and the administrator needs to know of the problem, before they get a call from the business unit. AppMetrics is predominantly production focused - it keeps your application running better and longer. See our Customer story about a failed dot.com Maintaining a healthy application using a product like AppMetrics improves the production uptime of your application. If crashes do appear in your production applications, then application development tools like AppSite or those from Numega can be employed to debug the crash. Why do I need AppMetrics if I already have Application Center 2000? The main purpose of Application Center Server is for the deployment and maintenance of applications built on IIS and COM+. This includes setting up clusters of machines onto which Application Center Server can deploy content and configure load balancing for such applications. Application Center Server has a module in it called "Health Monitor" which was developed by Xtremesoft under contract for Microsoft. Health Monitor collects performance information from a variety of sources, one of which is COM+. Health Monitor collects data on an COM+ Application-wide basis (e.g. total aborted transactions, total committed, etc.). AppMetrics, on the other hand, lets you monitor on an individual-transaction basis (i.e. by each component within the COM+ Application, and in some cases provides detail down to a method-invoked level). Older Issues I am using Windows Server 2003, and my disk is filling up with complustrace.log files in the \Windows\System32\Com folder. Why is it happening, and what can I do to clean up those files from the disk? The complustrace.log files are created when an application subscribes to COM+ instrumentation events. AppMetrics subscribes to those events in order to collect instrumentation data from monitored applications. There is always at least one current log file plus any number of archived log files on the system, with a minimum of one, where ten is the default value. The number of archived log files can be adjusted by editing the following registry key; HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole\Instrumentation\TraceLogFilesLimit This is mentioned on the following Microsoft support page; http://support.microsoft.com/kb/883955 The manner in which these files are created is that whenever a COM+ subscription is made, such as starting an AppMetrics agent on an application server, the current log file is archived by appending a time stamp to the file name, the number of archived files are trimmed to the value set in the registry, and a new complustrace.log file is created. When the subscription terminates, such as when an active AppMetrics agent is stopped, the current log file is closed. No further action takes place until a new subscription is made, where the above process repeats itself. This is assuming that you are running Windows 2003 Service Pack 2, which resolves an earlier Microsoft issue with COM+ trace log files not being deleted. If you aren't running Service Pack 2, you'll either need to upgrade to that service pack, or install the following hotfix; http://support.microsoft.com/kb/912818/ I am told that all my application issues will go away when I move to COM+ and Windows 2000. I am wary of that claim but will I still need a tool like AppMetrics? If your application has bugs on NT4, the bugs will still be there on W2K. The need for the diagnostic features of AppMetrics will not go away. People who get sick or hurt but don't have medical coverage often wish they had. People who get regular medical checkups can detect problems before they become serious. This applies equally well to deployed business applications. Crash diagnostics is but one of the features of AppMetrics. Other features areas include: Health Monitoring The requirement to monitor the business-transactional health of applications in deployment is ongoing. Business transactions don't slow down or outright fail solely due to coding errors! Several other factors - often outside your direct control can cause problems:
Historical Reporting Those that are ignorant of history are bound to repeat it. How can you diagnose problems without a historical record of what happened? Further, how can you predict future performance without a historical record? Questions like: "Do I need more servers?" and "Can I consolidate applications?" only start once the application is in deployment. Those questions cannot be responsibly answered without the history of what has gone before. Performance Bottleneck Identification When the call comes, the message is "The app is too slow!" What to do next is not nearly so concise… The ops manager who takes the call has a daunting task:
The number of outages and the length of time of the outages have both decreased significantly, since we moved to COM+. This has shifted our priorities, at least until the next major outage! This isn't the right answer is it? No! If your application has bugs on NT4, the bugs will still be there on W2K. The need for the diagnostic features of AppMetrics will not go away. People who get sick or hurt but don't have medical coverage often wish they had. People who get regular medical checkups can detect problems before they become serious. This applies equally well to deployed business applications. Crash diagnostics is but one of the features of AppMetrics. Other features areas include: Health Monitoring The requirement to monitor the business-transactional health of applications in deployment is ongoing. Business transactions don't slow down or outright fail solely due to coding errors! Several other factors - often outside your direct control can cause problems: Trading partner performance problems (e.g. credit card validation on a shopping cart module);
Historical Reporting Those that are ignorant of history are bound to repeat it. How can you diagnose problems without a historical record of what happened? Further, how can you predict future performance without a historical record? Questions like: "Do I need more servers?" and "Can I consolidate applications?" only start once the application is in deployment. Those questions cannot be responsibly answered without the history of what has gone before. Performance Bottleneck identification When the call comes, the message is "The app is too slow!" What to do next is not nearly so concise… The ops manager who takes the call has a daunting task:
I thought when we moved to COM+ that our issues would go away forever; furthermore, if problems do arise, doesn't COM+ provide more visibility into what's going on inside my application than MTS did? MTS is a black box, and so is COM+. COM+ has different behaviors due to differences in the threading model Your components may act differently under COM+ than they did under MTS, and you won't know why without a solution like AppMetrics. SNMP Does AppMetrics SNMP alerting share the same vulnerabilities listed in CERT Advisory CA-2002-03 http://www.cert.org/advisories/CA-202-03.html No. AppMetrics does not invoke or contribute toward the vulnerabilities documented in this CERT advisory. This advisory documents decoding and processing vulnerabilities in SNMP Service handling of SNMP request messages (SNMP managers to SNMP agents), and SNMP trap messages (SNMP agents to SNMP managers). AppMetrics does not decode SNMP request messages, and the processing vulnerabilities documented by CERT occur outside of the extension agent in the SNMP service (which processes request messages related to AppMetrics objects). AppMetrics does not decode or process SNMP traps. Xtremesoft recommends the application of any appropriate patches from Microsoft and any other vendor's SNMP service they currently have implemented. How does AppMetrics work with a workgroup instead of a domain? AppMetrics will work with workgroups. You need to create the same userid with the same password on each of the machines you are using. (Manager, Agent) Then during install you will use that userid for the "Run As" account and the local machine name for the domain name. When I try to start up the monitor I am getting an error that tells me "Access Denied"? There are a few things to check in regards to security.
|
|
|
          |
|
|
|
|||||