To disable the check for SIM prerequisites:
Add the key HKEY_LOCAL_MACHINE\SOFTWARE\Altiris\AIM to the registry.
Create a DWord called IgnoreInstallPrerequisites and set the value to 1.
To enable the Next button if any of the install Readiness checks fail:
Add the key HKEY_LOCAL_MACHINE\SOFTWARE\Altiris\AIM\InstallReadinessCheck\
to the registry. Create a DWord called EnableNextbutton and set the value to 1.
The Recovery Solution for Clients 6.2 SP4 beta is now available on SYMANTEC CONNECT.
Available in this beta are the following features:
•Product Listing
–Externally: http://www.solutionsam.com/solutions/pl/symantec.pl.xml.zip
•Symantec Installation Manager (Build 814)
–Externally: http://www.symantec.com/business/it-management-suite (select Trialware)
•Release Notes:
The first Beta is available :
http://www.symantec.com/connect/blogs/itms-71-beta-now-available
Altiris Deployment Solution offers enhanced Dell server deployment capabilities that dramatically reduce the time and cost of deploying and managing your Dell servers. Deployment Solution uses prebuilt scripts to quickly and easily deploy Dell servers. Deployment jobs enable you to update and configure hardware and system settings (including BIOS, RAID, and DRAC configurations), deploy a Microsoft Windows or Linux operating system, install applications (databases and email servers), and more. All from a central, remote console.
For a collection of videos that are a good introduction to Deployment Solution for Dell Servers 3.2 MR1, see Symantec Connect.
This release includes the following new features:
Deployment Solution software provides the infrastructure and the core functionality that is used by Deployment Solution for Dell Servers. Before using this product, you should be familiar with the functionality and requirements of Deployment Solution.
Deployment Solution for Dell Servers 3.2 MR1 has the following requirements in addition to those of Deployment Solution 6.9 SP4:
This release provides support for the servers that are included in version 3.2.1 of the Dell OpenManage Deployment Toolkit (DTK) in the WinPE environment
This release provides support for the servers that are included in version 3.1 of the Dell OpenManage Deployment Toolkit (DTK) in the Linux environment.
When you install Deployment Solution for Dell Servers, the Configuration Wizard prompts you to provide installation (source) files for each operating system that you select to create automated scripted installation jobs. The files are copied to the deployment share if they are located elsewhere.
Drivers for supported Dell server models can be automatically located and copied from the following Dell OpenManage CDs or DVDs: Dell Server Assistant, Dell Systems Build and Update Utility, or Dell Systems Management Tools and Documentation.
The Configuration Wizard prompts you for the CDs or DVDs for your selected systems (supported systems are listed on the front of each disc). If the discs are not available, ISO images can be downloaded from support.dell.com. Browse to the downloads section for your server model and operating system, and then select the Systems Management category.
DS includes jobs to perform scripted installations of the following operating systems:
Complete installation instructions are contained in the Deployment Solution for Dell Servers 3.2 MR1 documentation, which is available at http://www.altiris.com/support/documentation.
Please refer also to the demo videos on the Symantec Connect site.
You can download released versions of Altiris products from http://www.altiris.com/Download.aspx.
You can download Beta versions of Altiris products from http://beta.altiris.com.
You can download files for the Microsoft WinPE and Linux pre-boot or automation environments from the Deployment Solution for Dell Servers download page. Go to http://www.altiris.com/Download.aspx, and then select the appropriate version of Deployment Solution for Dell Servers.
To upgrade, perform a standard installation as outlined in the Deployment Solution for Dell Servers 3.2 MR1 documentation, which is available at http://www.altiris.com/support/documentation.
During the upgrade, any existing folder that is named “Dell” within the Deployment Share is renamed to “Dell_prev.” Any Dell jobs that exist prior to an upgrade remain intact, but their references to the Dell directory in the Deployment Share might need to be redirected to the Dell_prev folder to operate properly.
Performing an upgrade has the following effects:
The jobs from the previous version should still appear in the Deployment Console. They are located in the folder that is named according to the version. For example, Deployment Solution for Dell Servers v3.2Linux. The new jobs in the Deployment Console are in a separate folder that is named according to the version and pre-boot environment. For example, Deployment Solution for Dell Servers v3.2 MR1 Linux.
The Deployment share is usually located in the C:\ProgramFiles\Altiris\eXpress\Deployment Server\ folder. The old Dell file-system folder in the Deployment Share is renamed to "Dell_prev" (or something like Dell_prev1 if a Dell_prev folder already exists). A new file-system folder named "Dell," which contains the version 3.2 MR1 files, is created in the Deployment Share.
The tools menu in the Deployment Console is updated to refer to the new version 3.2 MR1 items. The previous versions of each utility (Configuration Utility, Job Builder, Configuration Wizard) reside in their respective Dell_prev folders. Using these versions is not supported because they might not interact correctly with the updated database schema.
As of today the MR2 is released
Didn’t see a Release note yet, but I guess it is KB 51945
A possible way to fix it is just being released and is to be found here https://kb.altiris.com/article.asp?article=52533&p=1
If you want to know more about Sysprep you can find more here http://technet.microsoft.com/en-us/library/dd744512(WS.10).aspx#ResettingWindowsActivation
There is a limit of 3 times a sysprep can run on a single computer if you do not use rearm option
If you anticipate running the Sysprep command multiple times on a single computer, you must use the SkipRearm setting in the Microsoft-Windows-Security-Licensing-SPP component to postpone resetting the activation clock. Because you can reset the activation clock only three times, if you run the Sysprep command multiple times on a computer, you might run out of activation clock resets. We recommend that you use the SkipRearm setting if you plan on running the Sysprep command multiple times on a computer.
Finally the TMS7 or in the new naming IT Management Suite 7 is released for download. More info to be found here.
https://kb.altiris.com/article.asp?article=51492&p=1
The ITMS7 contains:
CMS7, SMS7, SD7 and AMS7, but also DS7.1 (With PXE) and Virtual management
the Asset workflows that will ship with the product, they are:
1. Ownership Verification
2. Software Purchase Request
3. Hardware Purchase Request
The installation file is a ZIP file to be found in the root folder of the NSCAP Share. Unzip the file and run the exe AFTER you have installed the Workflow engine.
Software Catalog Data Provider enhances Notification Server's ability to identify the software that has been detected on the managed computers in your environment. It uses rules to identify software that otherwise could not be identified. It can then automatically import data into the Software Catalog to create a software resource for the software. After it creates a software resource in the Software Catalog, you can add package resources along with other software information. You can then create policies or tasks that deliver or manage this software on the managed computers in your environment.
Software Catalog Data Provider is needed to identify software in the following instances:
See this article to know more about the home edition of Symantecs Antivuris.
With SIM 555 installed, it may not properly recognize a proxy configuration (regardless of proxy credentials).
In this case, The SIM can never 'connect' to our servers to obtain the proper information for our Product Listing, meaning all Products install items will appear grayed out.
Here is how it was noticed:
1. SIM 553 installed on a customer system
2. Customer updated the Product Listing and received SIM 555 upgrade
3. When SIM 555 launched, it could not 'see' Products install items. All showed as unavailable and grayed out with 'requires internet connection' message.
4. In some other cases SIM was not able to recognize the customer's Proxy settings so he was not able to obtain access to the Internet
Cause
Some changes in SIM 555 code caused some unexpected behaviours during our attempts to connect to the Internet
Resolution
This issue has been reported to our Development Team. A permanent fix has been developed. This issue is fixed with SIM 7.0.556 version. Please check for updates in SIM.
Note: If SIM is not warning you about installing a new version or it is not able to obtain it, please see the attached file. It should be SIM 7.0.556. Just unzip the file and run the executable to upgrade SIM.
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.
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
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!
• 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.
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.
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
