End of Blog

Due to a change in my carrier I will no longer be able to update the blog.
So if anyone would like to continue my work fel free to drop me a note..

How do I create a Report that shows a general summary for all Patch Management executions?

The Table Evt_AeX_SWD_Execution holds all of the Patch Management execution and status, however it also holds status of Software Management installs.  There is a Report that shows Software Execution Summary (Reports > Software > Delivery > Execution Summary).  

Is there a way to report on only the Patch Management Executions? 

There is, please create a new SQL Report and enter the following data (Default shows the last 30 days.

NOTE: this query shows All Failures, even those that are later successful.

select  [Status] =CASE when e.status = 'Command executed' then 'Success'

      when e.status = 'Failed' then 'Failed'

      when e.Status = 'Terminated' then 'Terminated'

      else 'Other'

End, COUNT ([Status]) as 'Count'

from Evt_AeX_SWD_Execution  e

where e._eventTime > GETDATE() – 30  -- Count Executions from last XX Days

and PackageId in (select distinct ItemGuid from [Evt_NS_Item_Management]

      where [ItemClassGuid] = '6E89DC4B-693A-4BD3-AEFA-385CCD1874E8')  -- Patch Solution Class GUID

group by [Status]

order by 2 desc

AppCenter - Information About "Heartbleed", OpenSSL Vulnerability

AppCenter - Information About "Heartbleed", OpenSSL Vulnerability
http://www.symantec.com/business/support/index?page=content&id=TECH216616&actp=SUBSCRIPTION

Heartbleed Vulnerability Statement

Symantec Endpoint Management ITMS 7.0/7.1 Heartbleed Vulnerability Statement
http://www.symantec.com/business/support/index?page=content&id=TECH216654&actp=SUBSCRIPTION

Symantec Endpoint Management ITMS 7.5 Heartbleed Vulnerability Statement
http://www.symantec.com/business/support/index?page=content&id=TECH216635&actp=SUBSCRIPTION

ITLS 7.5 HF5 Need to know....

As many of you noticed ITMS 7.5 HF5 is now available via SIM. Some of you asked if we were aware of that the Release Notes were not present. Yes, we are aware of it and our CE team is working on getting an updated version of that doc published with the HF5 as soon as possible.

 

As well CE team discovered an issue that caused concerns in regarding releasing HF5 today. This issue is documented in eTrack 3471385 “Task Server upgrade from HF4 to HF5 does not work at first attempt because AexSetupProgress.ini file exists in TS setup directory.”

The Release Notes will have more details on this but for those customers that already installed HF5, these are the current workarounds regarding the known issue mentioned in the eTrack above:

 

Workaround_1: restart computer before Task Server upgrade from HF4 to HF5 - ini file will be removed on restart.

 

Workaround_2: after first attempt to upgrade remote TS ini file will be deleted.

Go to NS Console -> Site Servers and specify schedule for the corresponding Task Server upgrade policy - this time remote Task Server upgrade will work.

 

Besides the known issue mentioned on the eTrack above, HF5 should be just fine to be installed by customers.

 

I don’t have more details to share at this point but as soon as CE team define how they want to proceed, they will share that with this audience in a later time.

 

Symantec™ IT Management Suite 7.5 HF5 powered by Altiris™ technology Release Notes

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

Endpoint Application Virtualisation Nice Links

http://www.symantec.com/connect/endpoint-virtualization/videos

http://www.symantec.com/connect/endpoint-virtualization/downloads

http://www.symantec.com/connect/articles/virtual-application-library

http://www.symantec.com/connect/articles/running-ie6-ie7-and-ie8-side-side-using-symantec-workspace-virtualization

http://www.symantec.com/connect/articles/virtual-internet-explorer-browser-catalog

FAQ on Package Servers

All you need to know about Package Servers
http://www.symantec.com/docs/HOWTO77389

Backup Exec 2012 SP4 Released

Backup Exec 2012 Service Pack 4 (SP4) is now available for download and adds support for Enterprise Vault 10.0.3 and EV 10.0.4 along with critical updates, and enhancements.

We’ve added the following features and enhancements to this release:

·         Enterprise Vault 10.0.3 and 10.0.4 support

·         Exchange 2013 CU3 support

·         DLM changes for Backup to Disk (B2D) and Removable disk cartridge(RDX).

• DLM reclamation changes for Removable Cartridge (RDX)

Additionally, this release addresses customer cases (mentioned in the released notes).

 

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

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

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

Altiris™ Deployment Solution 6.9 SP6 from Symantec™ Release Notes

Can be found here

Altiris diagnostic agent tasks

Howto : http://www.symantec.com/docs/HOWTO75097

The attached tasks can update settings on Managed computers and on the SMP server, to collect additional diagnostic information, and to reset the same settings to their default values.
To use these tasks, you need to import the attached file into the Altiris console, possibly  under Jobs and Tasks. To import this XML,

• Save the attach XML to your local drive
• Select the folder where you wish the folder and it's contents to be imported,
• Right-click on the folder and select import
• Select the the XML on your local drive

How to remove the Symantec Management Agent (Altiris Agent) manually on the SMP server and assign it to a new drive

Note: Removing the Symantec Management Agent from the SMP itself is not recommended. There are usually some side-effects that may affect functionality on Task Management, DS.


The automatic uninstall process used for the Symantec Management Agent (SMA, formally known as the Altiris Agent) should take care of most of the items that were installed.

Prior to the release of ITMS 7.5, the command "aexagentutil.exe /clean" was not intended to remove SMA anymore. It was left for legacy purposes only. It was recommended to use "AeXNSAgent.exe /uninstall" to uninstall the SMA.

Note: As per ITMS 7.5 release,  for the SMA 7.5 the “/clean” command behaves exactly like "AeXNSAgent /uninstall" command. Actually “AeXAgentUtil.exe /clean” simply launches “aexnsagent.exe /uninstall”.  Using "AeXNSAgent.exe /uninstall" should removes ALL registry, binaries, etc created by agent but leaves behind agent guid (i.e. install on this system uses same guid). Also Log files are not removed as it was decided to let them be for troubleshooting purposes.


On those instances where you need to remove any leftovers or make sure that previous references of the Agent location are removed (in case that you need to install the Agent to a different drive but is not taking the new path), you may want to use the following steps (in most cases using the steps on HOWTO45738 "What is the best way to cleanly uninstall the Symantec Management Agent to leave no remnants (or the bare minimum) behind?" should address most uninstalls):

1.      Uninstall any Altiris Agents found in Add/Remove programs

2.      Find any and all copies of the file AeXAgentUtil.exe and from each location

a.   Run AeXAgentUtil.exe /uninstallagents

          b.      Aexnsagent.exe /uninstall

          (Both executables are located, by default at: C:\Program Files\Altiris\Altiris Agent\)

3. Open Registry find keys where old agent path(s) is found and delete those registry keys

a.       This Includes two entries under the Windows Uninstall registry that could still exist (don’t forget the wow64 hive as well) “Altiris Agents” and “NS Client”.

b.      The Altiris Agent is under the uninstall key and NS Client is under the Altiris\Express key both need to be deleted if not already deleted by the /clean.     

HKEY_LOCAL_MACHINE\SOFTWARE\Altiris\eXpress\NS Client
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\AltirisAgent
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\AltirisAgent

c.       As well you need to clean any references of the Altiris Agent on

HKEY_CLASSES_ROOT\CLSID
HKEY_CLASSES_ROOT\Typelib
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Clsid
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Typelib 

4.      Copy AexNSC.exe from “\\localhost\nscap\bin\win32\x86\NS Client Package” and copy the file to “C:\temp”

5.      In a command prompt (Administrator privileges and make sure the smp.domain.com portion reflects the SMP server) execute the following command line contained within the brackets [] but path should be changed appropriately to the correct location where the NS is installed: [C:\temp\AexNSC.exe -s -a NS="smp.domain.com" PATH="D:\program files\altiris" nsweb="http://smp.domain.com/altiris/" NOSTARTMENU /platform=x64 /s]

6.      Verify that the install correctly installed to path specified

7.      Install Task service agent

a.       Windows Explorer, browse to “D:\Program Files\Altiris\Notification Server\NSCap\bin\Win64\x64\Client Task Management\Server Package”

b.      Double click TaskServerSetup.exe

c.       Change the “Destination Folder” to “D:\Program Files\Altiris\Altiris Agent\Client Task Server\” (or whatever the correct path is), click Next

d.      In the Installation type dialogue window, select “Typical”, continue with the install

e.       Restart the Client Task DataLoader and Object Host Service services

Installation Failed at step 1 or 2 for ITMS

In the log you light find that the .net AJAX extentions failed to install, then check the following

The Microsoft .NET Framework NGEN v2.0.50727 services are needed by the installer but are disabled by default. They need to be started by .NET installers. To solve this, change the startup type of both services Microsoft .NET Framework NGEN v2.0.50727_X86 and Microsoft .NET Framework NGEN v2.0.50727_X64 to manual and re-install the application, which now runs fine!

Installing on SQL Non Standard Ports

In order for the Notification Server to be able to communicate with a SQL Server using a non-standard port a SQL alias needs to be created. The alias will contain the necessary information about the SQL Server, including servername/instance and port number.

Perform the following steps on your SQL Server:

1. Click Start > Run and type cliconfg in the run box and click OK.
2. Click the Alias tab on the SQL Server Client Network Utility screen.
3. Click the Add button.
4. In the Server Alias screen enter the name you wish to use to reference your SQL Server.
5. Click the TCP/IP radio button under Network Libraries.
6. Enter the SQL Server Name\Instance in the Server Name box.
7. To specify the specific port, uncheck the Dynamically Determine Port box and input the correct port.
8. Click the OK button.
9. On the main SQL Server Client Network Utility Screen click the OK button.
10. On the SQL Server configuration screen of the Notification Server setup enter the alias name.

Symantec Installation Manager keeps prompting that it needs a reboot...(Workaround)

In some rare occasions the SIM does not start because of Reboot pending....

It looks like the workaround option did its job by now, check the exact steps:

Create the following SIM registry Keys to ignore a pending reboot:
HKEY_LOCAL_MACHINE\SOFTWARE\Altiris\Aim\IgnorPendingReboot

Create a DWord(32) value called “Enable”
Enable = 1 Ignores pending reboot
Enable = 0 Checks for reboot

 

Symantec™ IT Management Suite 7.5 HF4 powered by Altiris™ technology Release Notes

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

How to make a Windows PE boot package with the Ghost Boot Wizard

How to make a Windows PE boot package with the Ghost Boot Wizard.

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

 How to Create a Boot Disk and Start a Ghost Session to Create/deploy to a Connected Local Drive

http://www.symantec.com/connect/articles/readyhow-create-boot-disk-and-start-ghost-session-createdeploy-connected-local-drive

Windows Embedded Standard 7 SP1 Early Support Statement

The document can be found here

Getting the Patch List

How to know which aplications Altiris 7.5 patches?

Run this Qry in SQL or create a report:

SELECT     comp.Name AS Company, vi.Name AS Product
FROM         Inv_Software_Release_Platform AS rp INNER JOIN
                      ResourceAssociation AS ra ON ra.ParentResourceGuid = rp._ResourceGuid AND
                      ra.ResourceAssociationTypeGuid = '292dbd81-1526-423a-ae6d-f44eb46c5b16' LEFT OUTER JOIN
                      RM_ResourceCompany AS comp ON ra.ChildResourceGuid = comp.Guid INNER JOIN
                      RM_ResourceSoftware_Release AS vi ON vi.Guid = rp._ResourceGuid
ORDER BY Company, Product

Press Crtl A in the result pane and past it to Excel...;-)

Remote Altiris Agent Diagnostics (RAAD) for 7.5

Remote Altiris Agent Diagnostics (RAAD) 7.5.1670
http://www.symantec.com/business/support/index?page=content&id=HOWTO95133

Support Recommended Reading List for Deployment Solution 7.5 (updated Jan 8, 2014)

Nice Recap Doc on DS7.5 can be found here

Support Recommended Reading List for Deployment Solution 7.1 (updated October 2013)

Nice Ref doc on DS7.1 can he found here

Windows 8.1 and Windows Server 2012 R2 Full Support statement

The document can be found here

Symantec™ IT Management Suite 7.5 HF3

Symantec™ IT Management Suite 7.5 HF3 powered by Altiris™ technology Release Notes
http://www.symantec.com/business/support/index?page=content&id=DOC7103&actp=SUBSCRIPTION

AppCenter 4.3

I'm pleased to announce that Symantec App Center 4.3 is now available for SaaS customers. We expect the on premise version to be available on Fileconnect on Jan 27. This release of App Center includes the following new features:

• Symantec Sealed Program enables enterprises to confidently embrace third-party mobile apps while meeting data security requirements. Mobile apps in the Sealed Program have been wrapped with a layer of security and management, allowing IT to manage policies such as encryption, authentication and data sharing restrictions. Enterprises can now provide a secure mobile workspace that consists for home-grown apps, Symantec productivity apps and 3^rd party mobile apps. ISV partners are in the process of wrapping and testing their apps.
• Symantec Secure Web*, a standards compliant mobile browser with built-in wrapping technology, provides protected access to internal web-based applications and content. IT administrators can configure policies to meet internal data security requirements. For example, IT can set policy that allows content sharing with other wrapped apps or require internal URLs be opened with Secure Web.
• A wrapped version of Symantec Secure Email* allows IT to set security policies for email.

 

*Pending app store availability

 

The Enterprise Mobility Product Marketing team has prepared the following assets to support this release:

 

Symantec Sealed Program

Symantec Connect blog post

Updated Symantec Sealed Marketplace

Symantec Sealed datasheet (for partners)

 

Symantec App Center

What's New in Symantec App Center 4.3 one pager

Updated Symantec App Center customer presentation (includes customer-facing Symantec Sealed slides)

Updated Symantec App Center data sheet

 

Symantec Mobile Management Suite

Updated Symantec Mobile Management Suite data sheet 

Updated Symantec Mobile Management cheat sheet

ITMS 7.1 SP2 MP1 Rollup Version 8 Release Notes

ref : http://www.symantec.com/business/support/index?page=content&id=HOWTO81832&actp=SUBSCRIPTION

KNOWN ISSUE: Manage > Jobs and Tasks page taking too long to load. Large amount of Jobs and Tasks to be render.

Ref and Download of pointfix :  http://www.symantec.com/docs/TECH213493

Issue

Customer reported that trying to load "Manage > Jobs and Tasks" page is very slow (usually takes over 2 mins to load). Customer applied the pointfix available from TECH198649 and TECH209550 for the Enhanced Console Views: ITMS 7.1 SP2 MP1 but it didn't help.

Environment

ITMS 7.1 SP2 MP1

Cause

Known issue. The amount of Security Roles in the Security Cache was causing a delay in loading the pages. 

Solution

Symantec has acknowledged that the above-mentioned issue is present in the current version of the product mentioned earlier on this article. Symantec is committed to product quality and satisfied customers.
Symantec currently plans to address this issue by including a fix in the next available ITMS 7.1 SP2 MP1 Rollup (Post Rollup v7). Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here. A link to the Release Notes will be added to this document when it becomes available. Please note that Symantec reserves the right to remove any fix from the targeted release if it does not pass quality assurance tests.  Symantec’s plans are subject to change and any action taken by you based on the above information or your reliance upon the above information is made at your own risk.
Development has created a pointfix that can be installed on top of ITMS 7.1 SP2 MP1 Rollup v3. See file "PointFix_eTrack3276200_7.1_SP2_MP1_V3.zip" in the attachments section.

Trapping NSEs on a client

Ref :  http://www.symantec.com/docs/HOWTO4191

Question

For troubleshooting purposes, it can be useful to trap a copy of each outgoing NSE file the Altiris Agent is sending to the Notification Server.

Answer

A good resource when troubleshooting client-side issues involving NSEs is the option to capture NSEs as they are sent to the server.

Capture NSEs on the Agent by adding (if not present) or modifying the following string value:

1. HKLM | Software | Altiris | Altiris Agent | Transport | Capture Events Folder (on a Windows 7 64 Bit machine it is HKLM | WOW6432Node |Altiris |Altiris Agent | Tranport | Capture Events Folder)
2. Modify the String value “Capture Events Folder” so that the Value data points to a directory or path to store a copy of all outgoing NSEs.

Analyze what NSEs are being sent from this client machine. To test if the NS is processing them, place the NSE's captured on the NS\Drive:\Program Files\Altiris\Notification Server\NSCap\EvtQFast.


Be sure to remove the value from this registry entry after testing as it will eventually consume significant disk space.




Note: If trapping NSE's for Patch Management Inventory; Enable the NSE Capture, and then run the AeXPatchUtil.exe /i cmd as outlined in this article: http://www.symantec.com/business/support/index?page=content&id=HOWTO4198. Please allow for 30 minutes to 1 hour for the process to complete concerning the Patch Management Inventories.

After upgrade to SP6 all WinPE variables stopped working

Ref and download file : http://www.symantec.com/docs/TECH213143  

Issue

After upgrade to DS 6.9 SP6 all the PXE variables stopped working on WinPE 4.0. There was no issues with variables with WinPE 2.1.

Environment

DS 6.9 SP6.

Cause

Getpxe.exe command line in the startutl.bat file is not recognizing the 'winpe/4' switch to get the PXE variables for WinPE 4.

Solution

Please replace the existing startutl.bat on your DS 6.9 SP6 environment with the attached one.
To replace the file go to the following locations:
C:\Program Files\Altiris\Deployment\eXpress\bootwiz\platforms\winpe4\x86\templates
And
C:\Program Files\Altiris\Deployment\eXpress\bootwiz\platforms\winpe4\x64\templates
Once you have the new file copied on the above locations you need to recreate your WinPE4 PXE image.