Here is the list of the top 20 Knowledge Base articles.The list is determined by various factors that prove the article's value to our customers. Therefore, please make it a point to check this list first to see if your issue has already been addressed. And FYI, this list would be updated on a quarterly basis.
31 January 2010
Symantec Backup Exec 2010
Please find some news on the BE2010 new upgraded product on http://www.symantec.com/connect/blogs/are-you-ready-upgrade
Click on the link to find a document on How to Upgrade to Backup Exec 2010 in 3 Simple Steps
28 January 2010
Windows 7 Nonpaged Pool Srv Error 2017
I’m using my Windows 7 machine as a file server to host my BESR2010 images. I’m using a share. However, I ran into a problem after using the mounted share for a small amount of time. I found a simple solution after a bit of research.
After checking the Event Viewer System log, I found the following error:
Source: srv
Event ID: 2017
Level: Error
The server was unable to allocate from the system nonpaged pool because the server reached the configured limit for nonpaged pool allocations.
Some research led me to find this Google Groups discussion about the problem and this Microsoft Technet article discussing the solution (look at the bottom of the page). Apparently you need to tell Windows that you want to use the machine as a file server and that it should allocate resources accordingly. Set the following registry key to ‘1′:
HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\LargeSystemCache
and set the following registry key to ‘3′:
HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\Size
After making these changes and restarting, I haven’t seen this issue arise again. Fixed!
27 January 2010
ServiceDesk install reports "An error has occurred at: AddProfileValueDefinitions"
• ServiceDesk Solution 7.0
Problem/Symptoms
This issue can manifest itself in a number of ways both during the ServiceDesk installation process as well as after the installation (if errors during the installation process are missed or ignored). We will add new symptoms as we are made aware of them:
1) During the ServiceDesk installation the following error appeared:
An error has occurred at: AddProfileValueDefinitions
Error Message: Server was unable to process request. ---> Exception has been thrown by the target of an invocation. ---> could not save object ProfileServiceDeskSettings ---> Could not insert or update. insert error message: String or binary data would be truncated. The statement has been terminated. update error message: String or binary data would be truncated. The statement has been terminated. ---> String or binary data would be truncated. The statement has been terminated.
Stack Trace: System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> Exception has been thrown by the target of an invocation. ---> could not save object ProfileServiceDeskSettings ---> Could not insert or update. insert error message: String or binary data would be truncated. The statement has been terminated. update error message: String or binary data would be truncated. The statement has been terminated. ---> String or binary data would be truncated. The statement has been terminated. at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at LogicBase.Core.Ensemble.Profile.ProfileService.SaveProfileValueDefinitionsWithInitialValues(String sessionID, ProfileValueDefinition[] profileValueDefinitions, KeyValuePair[] nameValuePairs) at LogicBase.Components.Ensemble.Profile.AddProfileValueDefinitions.Run(IData data) at LogicBase.Core.ExecutionEngine.SinglePathProcessComponentExecutionDelegate.Execute(IData data, IOrchestrationComponent comp, String& outputPath, IExecutionEngine engine, TLExecutionContext context) at LogicBase.Core.ExecutionEngine.AbstractExecutionEngine.DoRunComp(IOrchestrationComponent comp, IData data, TLExecutionContext context)
The installation process is allowed to continue despite this error, however the ServiceDesk will not function properly when it is complete.
2) When attempting to create a new incident after the ServiceDesk 7.0 install is complete, the following error appears:
"Value cannot be null. Parameter name: uriString"
Cause
This error is caused by outdated versions of SQL components that must be installed on the ServiceDesk server as prerequisites. Specificially, one or more of these components may be missing or out-of-date:
SQLServer2005_ADOMD_x64.msi (Microsoft ADOMD.NET)
SQLNCLI_X64.msi (Microsoft SQL Server Native Client)
SQLServer2005_XMO_x64.msi (Microsoft SQL Server 2005 Management Objects Collection)
Resolution
We currently recommend that these files be downloaded from the Feature Pack for Microsoft SQL Server 2005 - December 2008.
21 January 2010
Hydraq
Ref Link
Hydraq is a targeted attack that is also currently referred to as Aurora, Google Attacks, and the Microsoft IE Vulnerability (advisory number 979352). Through the exploitation of a vulnerability, it attempts to install a trojan on a specific computer that steals information from that machine. The trojan attempts to make contact with command and control servers in order to receive instructions and to upload any information that it may have collected. This type of attack is often called an advanced persistent threat because of the sophistication and persistence of the attack within a business.
This attack is of concern to all computer users because vulnerabilities used in this attack are now widely know and likely to be exploited by other cybercriminals.
Symantec customers are protected from Hydraq both today and in future using updates, as well as the products and services outlined in the tabs below.
12 January 2010
Remote Altiris Agent Diagnostics 2.0
Download of latest version can be found here
Ref Link : https://kb.altiris.com/article.asp?article=49683&p=1
“Remote Altiris Agent Diagnostics” (RAAD) version 2 expands on the diagnostic checks and remediation actions performed by RAAD version 1 (KB 45023) to allow those checks and actions against a list of machines and not just the one machine. The Health Checks in RAAD version 2 are designed to take a look at the state of the Altiris solution plug-ins such as Patch, Task, SWD and Recovery to determine if they are working properly. Version 2 also allows the ability to run a Custom Inventory XML against the set of machines and return the results immediately so you can customize your own health check. You can examine more in-depth details of the Agents using the Diagnostics tab which is essentially RAAD version 1. The biggest advantage with version 2 is that you can run remediation actions such as Configuration Request and Start Patching Cycle against as many machines as you’d like and all at once.
The process is to get a list of machines, run a health check against them, then by evaluating the results or drilling down into the diagnostics choose a remediation action to run against the machines you choose.
Features:
- Diagnostics and Health Checks
- x86 and x64 compatible for remote clients
- Ability to pass credentials used to connect to remote clients
- Multi-Threaded
- Agent, sub-agent, and customizable Health Checks
- Ability to run an action against multiple remote clients at once
- Customizable User Interface and captured
* Please see KB 45023 for application functionality
Requirements:
- Run the executable locally, not from a share
- Host and remote machine must be Windows OS
- Do not use 'Run As' - you can pass credentials in this version
- .NET 1.1 framework installed on host and remote machine
- Altiris Agent must be installed on host
- Firewall on the remote machine will also prevent Altiris actions.
You will need to add AeXNSAgent.exe to the Firewall exclusion by running the following command on the remote machine:
netsh firewall add allowedprogram "%programfiles%\Altiris\Altiris Agent\AeXNSAgent.exe" ENABLE
Or you can simply run this command from the 'Remote Execute Option' button from the application
Usage:
To distribute desired application settings such as Remote Execute options edit the RAAD.exe.config and place it in the same folder as RAAD.exe. If user has altered application settings have them go to Settings - Change Application Settings and choose Restore All Setting to Default which will import your altered RAAD.exe.config.
Changes:
Ver. 2.1.9.0
- First GA Release
Ver. 2.1.10.0
- Fixed Buttons to show on Vista and Windows 7
- Fixed Collection Picker to import into List after selection
- Add Trusted Connection for database connections to use current Windows Authentication and not just SQL credentials
- Added Stop and Start Recovery service to Actions
- Included RAAD.exe.config to zip so application settings can be distributed to end users. See Usage above.
Ver. 2.1.11.0
- Embedded both dlls into executable so RAAD.exe is a single distributable
- Fixed Recovery Agent Service and Stop
Ver. 2.1.12.0
- Now RAAD minimizes to System Tray on Exit
- Added ability to connect to Client's Diagnostics from System Tray
- Added Select All and Select None on Diagnostic and Health Check options
- Added ability to double-click client from Health Check results or Computer List to launch Diagnostics
- Added horizontal scroll to SWD Packages
- Fixed Task History to show local time not GMT
- Fixed Task History column sizes
- Fixed Logs not refreshing when switching clients
- Fixed exception when running RAAD.exe <computername> from command line
Ver. 2.1.13.0
- Added Garbage Collection to help memory issues
Ver. 2.1.15.0
- Added caching and populating credential password
- Added ability to hit Enter after entering password
- Added populating NS from local agent when using Redirect Agent
- Fixed Redirect Agent UI not executing
- Changed Copy to Ctrl-F so not to impeed Ctrl-C
Subscribe to:
Posts (Atom)