Blog site to provide a quick way to find solutions on problems encountered during a day to day work. Some articles are just copies of KB or Forums, but they might come in handy.
31 January 2014
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...;-)
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...;-)
30 January 2014
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
27 January 2014
22 January 2014
21 January 2014
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
http://www.symantec.com/business/support/index?page=content&id=DOC7103&actp=SUBSCRIPTION
17 January 2014
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 3rd 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 App Center
Updated Symantec App Center customer presentation (includes
customer-facing Symantec Sealed slides)
Symantec Mobile Management Suite
09 January 2014
07 January 2014
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
Capture NSEs on the Agent by adding (if not present) or modifying the following string value:
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.
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:
- 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)
- 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.
Subscribe to:
Posts (Atom)