Remote Altiris Agent Diagnostics 2.0 (RAADv2)

How do I remotely troubleshoot an agent without logging into the machine?

"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

Download:

http://www.symantec.com/business/support/index?page=content&id=HOWTO21449

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.

pcAnywhere Diagnostic and Connect Tool v1.0013

pcAnywhere Diag Features

• Encrypts and stores connection and diagnostic credentials
• Remembers the last PC connected to
• Ability to store a favorites list
• Single click to modify, double click to set as connection PC
• Checks the client status and repairs any issues
• Eliminates the “Raising Encryption” message upon connect
• Works even if the Altiris console is unavailable

Link to the article can be found here

Deployment Solution Samples for v7.1 SP1 (on SMP/CMS 7.1) x64

Well, it was a long time coming, and it's not 100% perfect.  Call this a public BETA of sorts.  Support was given permission to release a set of Deployment Samples for the current shipping code.  This set is an x64 installation and thus will not run on previous versions of the product.  The XML files that it extracts MIGHT work on previous versions, but of course it will be use-at-your-own-risk.  (Truthfully, MOST of it should work fine, but we don't have time to test it).

A link to this article can be found here

Web Page for Enabling Support to Deploy Tasks or Packages to Specific Machines in NS7

Do you ever need to push a package out to a single computer but the hassle of creating a job in the console takes too long? Wouldn't you like to give desktop support or the helpdesk this ability and still control what packages they can deploy? Then this is the answer to all you have hoped for! We've been using this page for months now on NS7 and it rocks!

Link to tis nice article can be found here

DS 69SP5 is available here

You can find the download for DS69SP5 here

The Release Notes can be found here

Backup Exec SBS (Small Business Server) Licensing is not accepted on a physical host machine running Windows Standard Edition and backups to tape hard

Problem

Backup Exec SBS (Small Business Server) Licensing is not accepted on a physical host machine running Windows Standard Edition and backups to tape hardware are not possible if the SBS Licensing is entered on a Hyper-V Guest running Windows SBS

Cause

Backup Exec Small Business Server Edition (BE SBS) is designed, licensed, and priced for the Microsoft Small Business Server operating system. The Backup Exec SBS Edition includes all of the necessary components to protect both the Standard and Premium versions of the Microsoft Small Business Server platform, including Microsoft SBS 2008 R2. As a result, Backup Exec SBS Edition will only install on a Microsoft SBS operating system and will perform verification during installation to ensure the product is installed only on a Microsoft SBS operating system.

Microsoft SBS 2008 R2 introduces a number of enhancements and now includes Hyper-V components necessary to virtual the SBS operating system as a Guest virtual machine. Backup Exec SBS Edition is supported when virtualized and installed into the SBS Guest virtual machine. However, BE SBS Edition cannot be installed on the physical Hyper-V host server or the second “Line of Business” Windows 2008 Server operating system (included in the Premium versions of Microsoft SBS) because they are not running the Microsoft SBS operating system required by the Backup Exec SBS Edition.

As a result of the requirement that Backup Exec SBS Edition be installed in the Guest virtual machine running the SBS operating system when virtualized, there are will be limitations on what backup devices can be supported. The Hyper-V 2008 and 2008 R2 platform do not currently support the virtualization of tape devices connected to the physical Hyper-V host through to the SBS Guest virtual machine. As a result, tape devices cannot be currently used when Backup Exec SBS Edition has been virtualized on the Hyper-V platform since tape communication cannot be passed through to the Guest SBS virtual machine. This is a limitation of the Hyper-V platform and not Backup Exec SBS Edition.

Solution

I. For backing up to tape from the host machine
The issue with the SBS Licensing not being accepted by the host machine is resolved with Backup Exec 2010-R2. The install now looks at the active guest machines for an SBS 2008 or greater server during the installation to the host. For tape backup in this environment, install Backup Exec 2010-R2 with the SBS License to the host machine. Per Microsoft KB (957006) Microsoft does not suport SBS 2003 server running as a virtual machine on a Hyper-V host.
II. For backing up to non-tape media from the guest machine
Continue using the Backup Exec SBS Edition Licensing and install it in the Guest virtual machine running the Microsoft SBS operating system for use with backup-to-disk devices or Deduplication storage folders only.
Related Articles

Backup Exec reports Evaluation mode on Hyper-V host and no serial numbers present after rebooting the Hyper-V host
How to troubleshoot issues with a Robotic Library (autoloader/changer) and/or Tape Drive(s)
How to obtain the installation source download and license keys for the Backup Exec core product, agents, and options
Backup Exec 12.5 Hardware (HCL)
Backup Exec 12.5 Software (SCL)
Customer Pricing and Licensing Guide: Symantec Backup Exec (TM) 12.5 for Windows Servers

Updated version of Platform Support Matrix ITMS7.1

An updated version of Platform Support Matrix has been posted to the following KB article:

http://www.symantec.com/docs/HOWTO9965

Important changes for this version:
• Updated: SQL Server 2008 SP2 support for ITMS 7.1
• Updated: Windows Server editions for ITMS 7.1
• Updated: Descriptions for OS support with CMS/SMS
• Updated: Description for Agent Localization

{CWoC 2010} A Scripting Guide to Simulating Agent Workload on the Notification Server / Symantec Management Platform

Nice article about stress testing and simulating an agent.

(well done Ludo…)

http://98.129.119.162/connect/zh-hant/articles/scripting-guide-simulating-agent-workload-notification-server-symantec-management-platform

Management Platform (Formerly known as Notification Server)

Official Documentation Landing Page : http://www.symantec.com/business/support/index?page=content&key=55274&channel=DOCUMENTATION

Symantec Management Platform and Altiris Solutions Support Matrix

Link to the Support page : http://www.symantec.com/business/support/index?page=content&id=HOWTO9965

Migrate to ITMS 7.1

Comprehensive Migration Resources

Product Management and Development created a full complement of best practice recommendations to enable customers to design, migrate, and deploy Altiris 7.1 suites and solutions successfully. The documents cover planning and implementation, effective migration of agents, how to use available migration wizards, and more.

A dedicated migration area is now live on Symantec Connect.

Altiris 7.1 Suites and Solutions are Now Generally Available

On March 7, 2011 Altiris 7.1 Suites and Solutions were release to general availability. This release includes IT Management Suite and its integrated suites: Client Management Suite, Server Management Suite, Asset Management Suite and ServiceDesk. Symantec will issue a public press release on April 11, 2011. This release not only includes tremendous quality advances, but also significant improvements in performance and scalability. In addition to a solid release vetted by over 500 beta customers there are many new features that improve IT operational efficiency and control costs. Altiris 7.1 is a release to feel confident about in terms of quality and competitiveness: · Scalability increase of 320% and an overall increase of 480% in hierarchy minimizes our overall management footprint - a fraction of the typical Microsoft System Center implementation · A new management interface delivers the fastest console performance with consolidated management of common tasks, drag and drop functionality, and tighter product integration – ease of use is a strength · Deeper automation and intelligence drives innovation and optimizes software expenditures – freeing up valuable human and financial capital · Broad patch management coverage helps organizations protect against a growing list of non-Microsoft, 3rd party applications – over 2/3 of vulnerabilities exist in third party desktop applications

Release Notes ITMS 7.1

Can be found here

Backup Exec Known Issues

A special page has being created to list all known issues.

You can find the page here

Backup Exec 2010 revision 2896 Service Pack 1

A new Service Pack have being released. A link can be found Here

Altiris IT Management Suite 7.0 MR3 Release Notes

We are pleased to announce the release of Altiris IT Management Suite 7.0 MR3. This release continues to build on the progress that our previous releases have provided to our customers.  We want to thank everyone involved and those who continue to help make our products better.

To obtain this release use the following:

- http://www.solutionsam.com/solutions/pl/symantec.pl.xml.zip

Also, you can find the release notes at http://www.symantec.com/docs/DOC3465

Dell DMC 2.0 (Based on NS7.1)

Dell DMC 2.0 has launched. This build is based omn SMP 7.1 platform.

The other CMS/SMS/AMS/Service Desk solutions from Symantec will be launched at 07 of march.

Click Here to go to the download link

Skip the readiness checks for NS7

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.

Recovery Solution for Clients Beta is Now Available

The Recovery Solution for Clients 6.2 SP4 beta is now available on SYMANTEC CONNECT.

Available in this beta are the following features:

• Windows 7 (32-bit and 64-bit) support for RS Agent
• Rollup of all existing official 6.2 SP3 hot fixes
• WBFR-based recovery audit reporting in the File Recovery History report
• No reboot requirement for RS Agent upgrade

ITMS 7.0 SP5 en MR2

•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:

–http://www.symantec.com/docs/DOC1956 (SMP)

–http://www.symantec.com/docs/DOC2165 (MR2)

DS 7.1: Support Tools for DS 7.1.013

http://www.symantec.com/business/support/index?page=content&id=HOWTO26135

Beta SMP 7.1 (Hampton)

The first Beta is available :

http://www.symantec.com/connect/blogs/itms-71-beta-now-available

Deployment Solution for Dell Servers 3.2 MR1 Release Notes

Introduction

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.

New features

This release includes the following new features:

• Support for the latest version of the Dell OpenManage Deployment Toolkit (DTK version 3.2.1) in the WinPE environment.
• Improved performance.
• Sample Jobs to provide access to Lifecycle Controller drivers on 11th Generation Dell Servers for use during scripted OS installations.

Prerequisites

System Requirements

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 6.9 SP4. See the Deployment Solution release notes, article 51559. Deployment Solution 6.9 SP4 documentation is available at http://www.altiris.com/support/documentation.

Deployment Solution for Dell Servers 3.2 MR1 has the following requirements in addition to those of Deployment Solution 6.9 SP4:

• Installation of Deployment Solution for Dell Servers on Windows versions later than Windows 2000.
• The Deployment server, console, and datastore (deployment share) must be installed on the same machine as Deployment Solution for Dell Servers.

Supported Dell servers

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.

Operating system files for scripted installations

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 Windows scripted installations

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.

Supported platforms for scripted installations

DS includes jobs to perform scripted installations of the following operating systems:

• Windows Server 2008 (32- and 64-bit)
• Windows Server 2003 (all versions, 32- and 64-bit)
• Windows 2000 Server and 2000 Advanced Server
• Red Hat Enterprise Linux AS 3, 4, and 5 (all versions, 32- and 64-bit)
• Red Hat Enterprise Linux ES 3, 4, and 5 (all versions, 32- and 64-bit)
• SUSE Linux Enterprise Server 10 (32- and 64-bit)

Installation

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.

Where to download

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.

WinPE and Linux pre-boot files

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.

Upgrade

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:

Deployment Console jobs folder

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.

Deployment share file-system folder

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.

Deployment Console tools menu

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.

SMP / CMS/ AMS / SMS SP2 MR1 Released

As of today the MR2 is released

Didn’t see a Release note yet, but I guess it is KB 51945

Dagent command line Parameters

DAgent.msi /qn TCPaddr= 172.19.17.180 tcpport=402

McAfee rebooting Windows XP Systems - False positive detection of w32/wecorl.a in 5958 DAT - svchost.exe - Fix via Deployment Solution

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

Limitations when runnning Sysprep for WIN7

 

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.

Inventory Solution 7.0 Database Schema

 

Answer

The schema information can be accessed using the Symantec Connect links provided: http://www.symantec.com/connect/articles/inventory-solution-70-database-schema http://www.symantec.com/connect/articles/inventory-solution-70-database-schema-part-1-operating-system-inventory http://www.symantec.com/connect/articles/inventory-solution-70-database-schema-part-2-hardware-inventory http://www.symantec.com/connect/articles/inventory-solution-70-database-schema-part-3-software-and-user-inventory http://www.symantec.com/connect/articles/inventory-pack-servers-database-schema-part-1-virtual-machine-data http://www.symantec.com/connect/articles/inventory-pack-servers-database-schema-part-2-database-and-web

Altiris™ IT Management Suite 7 Release Notes

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

AssetManagement 7.0

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 7.0 Release Notes

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:

• The information that identifies the software cannot be gathered from Add/Remove Programs.
• The software is identified as a suite, and you need to identify a specific product in the suite.
• The software is identified as a product, and you need to identify the suite.

Home Use: Norton 360 Version 4 - Finally!

See this article to know more about the home edition of Symantecs Antivuris.

KNOWN ISSUE: With SIM 7.0.555 (Symantec Installation Manager) installed, SIM is not properly recognizing certain proxy configurations

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.

Top 20 Most Valued Backup Exec Articles

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.

http://www.symantec.com/connect/node/1123091

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

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!

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.

http://www.microsoft.com/downloads/details.aspx?FamilyID=536fd7d5-013f-49bc-9fc7-77dede4bb075&displaylang=en

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.

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

Query7: Show OwnerNS for Computers

SELECT     vRM_Resource_Item_Partitioned.Name, vRM_Resource_Item_Partitioned.Guid, Item.Name AS ResourceType, Item_1.Name AS OwnerNS,
                      vRM_Resource_Item_Partitioned.IsManaged
FROM         vRM_Resource_Item_Partitioned INNER JOIN
                      Item ON vRM_Resource_Item_Partitioned.ResourceTypeGuid = Item.Guid INNER JOIN
                      Item AS Item_1 ON vRM_Resource_Item_Partitioned.OwnerNSGuid = Item_1.Guid
WHERE     (vRM_Resource_Item_Partitioned.ResourceTypeGuid = '493435f7-3b17-4c4c-b07f-c23e7ab7781f') OR
                      (vRM_Resource_Item_Partitioned.ResourceTypeGuid = '2c3cb3bb-fee9-48df-804f-90856198b600')

Query7: Show when a filter has being last updated

SELECT     Item.Name, Collection.LastUpdated, Collection.LastUpdateEventDate, Item.Description
FROM         Collection INNER JOIN
                      Item ON Collection.Guid = Item.Guid
ORDER BY Collection.LastUpdated DESC

Notification Server 6 Agent for Macintosh Update for Mac OS X 10.5 and 10.6

An update that provides support for Mac OS X 10.5 (Leopard) and 10.6 (Snow Leopard) by the Notification Server 6.2 Agent for Macintosh is now available. This update allows 10.5 and 10.6 clients to be managed by an NS and for retrieval of Basic Inventory from these clients. This only updates the agent. The solutions, i.e., Inventory and Software Delivery, do not support Snow Leopard.

The update can be found at: https://kb.altiris.com/article.asp?article=50717&p=1.

Supported platforms:

Previously supported Mac OS X versions will remain the same: 10.2.8 – 10.4.X. New platforms with agent-only support in this addon are:

Mac OS X 10.5 (ppc and x86)

Mac OS X Server 10.5 (ppc and x86)

Mac OS X 10.6 (Intel only platform)

Mac OS X Server 10.6 (Intel only platform)

Prerequisite: NS 6.0.6074 with Altiris Agent for Mac 6.2.1302.

Site Server / Package Service/Task Service Support for NS7 SP3

Package Service

For Deskstops:

As of WIN2000 SP4 till VISTA SP2 64, but NOT W7 yet

For Servers

WIN 2000 SP4 to WIN2003 R2 32, but not WIN2003 R2 SP2 3W2 and 64 bit

And WIN2008 SP1 32 AND 64 bit, NOT higher

Task Service

For Deskstops:

only WIN XP SP3

For Servers

WIN2003 SP2 32, WIN2003 R2, WIN2003 R2 SP2 (all 32 bit only)

IE8 and .NET35SP1 support

Are supported as of NS7 SP3

REf : https://kb.altiris.com/article.asp?article=46349&p=2

SQL2008 SP1 support

As of NS7SP3 the SQL2008 SP1 is supported

Ref : https://kb.altiris.com/article.asp?article=46349&p=2

Managing Microsoft Windows 7 computers using Client and Server Management Suite 7.0 SP1 and Symantec Management Platform 7.0 SP3

 

Client Management Suite 7.0 SP 1 was released in September 2009 before the release of Microsoft Windows 7. However, when updated with the subsequent release and application of Symantec Management Platform 7.0 SP3 (December 2009), CMS/SMS 7.0 SP1 provides limited support for Windows 7 and Server 2008 R2 subject to the limitations listed below. In 2010, a CMS/SMS Service Pack 2 is planned that addresses these limitations.

For more information about Client Management Suite 7.0 SP1, see article 48420.
For more information about Symantec Management Platform 7.0 SP3, see article 49356.
The purpose of this document is to note those issues that you may encounter if managing Windows 7 computers using CMS/SMS 7.0 SP1 with SMP 7.0 SP3.

Known limitations:

Inventory Solution:

• The Inventory Plug-in for Windows will not install on Windows 7 client computers using the default filter (Windows Computers without Inventory Plug-in). It will install if the computer is targeted directly.
• The Application Metering Plug-in for Windows will not install on Windows 7 client computers using the default filter (Windows Computers without Application Metering Plug-in). It will install if the computer is targeted directly.
• Some data classes may not report back correct information.

Inventory for Network Devices (Agentless Inventory):

• No issues have been discovered.

Software Management Solution:

• A managed delivery policy configured to install an .exe or .msi to a software virtualization layer will not run successfully. 
• A managed delivery policy that is configured to run from the server will not execute on a Windows 7 client computer.
• A managed delivery policy that is configured to run as a specified user will not execute on a Windows 7 client computer.

Deployment Solution:

• Deployment Solution 6.9 SP3 supports Windows 7 and Server 2008 R2. Deployment Solution 7 will support these operating systems in a separately-scheduled release (either included in or prior to the CMS/SMS SP2 release).

Patch Management:

• Windows 7 or Server 2008 R2 patch data will be available with the CMS/SMS SP2 release.

RTSM:

• A Windows 7 client computer cannot be shutdown when the ‘Graceful power action’ option is enabled. 
• Deactivating SVS layers on Windows 7 clients via RTSM will not remove the application’s desktop icon or entry in the start menu. In other words, the layer will be deactivated but will appear to be active.

PCAnywhere:

• Windows 7 is reported as Vista in the remote console.
• The desktop background on the host and in the remote console is black rather than blue when a connection is made. When using the freehand draw capabilities of the white board, the pointer is difficult to see as it is black as well.

Out of Bands Management Component:

• No issues have been discovered.

Network Discovery:

• No issues have been discovered.

Altiris Service after NS7 SP3

 

The service has a new name. It is now the Symantec Management Agent Service.

Microsoft SQL Server Management Objects Collection patch is not installed

The following three files are necessary for a remote SQL host:

· Microsoft SQL Server Native Client

· SQL Server 2005 Management Objects Collection -

· Microsoft ADOMD.NET -

Use the following link to download the missing SQL components

http://www.microsoft.com/downloads/details.aspx?FamilyID=D09C1D60-A13C-4479-9B91-9E8B9D835CDC&displaylang=en

NS7 SP3 Available and some critical updates

AS of today the SP3 is available.

Make sure your sourcefiles are not deleted. As per design the system performs a repair first in some cases

The release notes can be found here

Turn off the Network Location Wizard in W7

1. Click Start, and then click Run.

2. In the Open box, type regedit, and then click OK.

   Registry Editor opens.

3. On the Edit menu, click New, and then click Key.

4. Enter the following registry entry:

   HKLM\System\CurrentControlSet\Control\Network\NewNetworkWindowOff