Video Screencast Help
Protect Your POS Environment Against Retail Data Breaches. Learn More.
Endpoint Management Community Blog
Showing posts in English
SymantecWorkflowTeam | 13 Aug 2012 | 0 comments

The release of Workflow 7.5 revolutionizes the concept of community-based documentation by creating component wiki pages for every component included in Workflow. This new component wiki model makes structured, community-based content available at its point of use.

You can access these component pages in the articles section of the Endpoint Management Community. You can also access these component pages from within Workflow Designer that shipped with ServiceDesk 7.5. Once Workflow 7.5 is released, you can access the component pages from within the Workflow Designer.

As a member of the Workflow community, you can earn Symantec Connect points and help others in the Workflow community by adding your knowledge, use cases, and examples to the wiki pages for the components that you use

Symantec will continually add content to these pages. However, we encourage you to submit ideas, use cases, and suggestions to help develop the community based articles.

We hope...

Jason Short | 03 Jul 2012 | 6 comments

As an innovation leader, Symantec has broken new ground again, this time in developer documentation. After an in-depth review of documentation for development frameworks similar to Workflow, we found that the best available documentation is community based. Unfortunately, community-based documentation tends to be both unstructured and difficult to find.  

For the upcoming release of Workflow 7.5, we have revolutionized the concept of community-based documentation by creating component wiki pages for every component included in Workflow. These wiki pages are available inside the Workflow Designer, where Workflow developers need to find it, as part of each component’s Online Help. This new component wiki model makes structured, community-based content available at its point of use.  

As a member of the Workflow community, you can earn Symantec Connect points by adding your knowledge, use cases, and examples to the wiki pages for the...

ianatkin | 05 Sep 2014 | 2 comments

I often find myself peeking into Altiris databases with the goal of finding a particular piece of information. The only problem is, I rarely know what table it's stored in.

There are three options at this point,

  1. Stare vacantly at the database, scanning through every table name waiting for an internal bell to tinkle
  2. Google till you dribble
  3. Run a SQL Query to find your table

In case you are an option (3) type of admin, this is the query to use,

SELECT  *
FROM    sys.tables
WHERE   Name LIKE '%BIOS%'

SELECT  *
FROM    sys.views
WHERE   Name like '%BIOS%'

Where here, in this instance, I'm looking for tables and views whose name includes the string "BIOS". This is a truely invaluable little query, and very helpful when trying to update reports across database versions. It's even quite handy if you simply are feeling a bit nosey.

ohzone - CherylPeterson | 04 Sep 2014

You may notice a few changes in the Endpoint Management Community product names. We've updated the product names to align more closely with what appears on the Symantec.com site as well as the terms that Symantec Support use. Product descriptions have also been updated. These changes offer a better description of what the product does and in some cases indicates a product's End of Life (EOL) status.

All forums and threads are still available and searchable. We hope you find these changes helpful.

ianatkin | 02 Sep 2014 | 0 comments

Yesterday I was looking at my SMP licensing using SIM (the Symantec Installation Manager) and I was troubled that certain licenses might not be applying correctly.

So, I decided to take a look at the installed licenses through an alternative route, the RemoveLicense.exe utility which is located in C:\Program Files\Altiris\Notification Server\Bin\Tools

When I loaded it though, I got a dialog displaying the following error,

Can not get the license
System.Exception: Certificate Chain is invalid.
  at RemoveLegacyLicense.LegacyLicenseUtil.Verify(X509Certificate2certificate)
  at RemoveLegacyLicense.LegacyLicenseUtil.GetLegacyLicenses()

 

This is a known issue, and Altiris Support directed me to this SMP 7.0 and 7.1 tech note TECH198685,

This cites the following,

Microsoft released a critical update (...

kedar_k | 26 Aug 2014 | 7 comments

ITMS 7.5 SP1 HF2 is available through SIM. It has fixes for the following components:

  • Symantec Management Platform
  • Deployment Solution
  • Inventory Solution

You can access the ITMS 7.5 SP1 HF2 release notes from the following location:

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

khelms | 25 Aug 2014 | 0 comments

When trying to access Process Manager portal the browser states "Page Cannot Be Displayed"

You may see these kinds of errors in the Windows Event Logs:

computer | Error | 10/27/2008 2:56:05 PM | Microsoft-Windows-IIS-W3SVC-WP | 2297
The worker process for application pool 'application pool id' encountered an error 'Configuration file is not well-formed XML
' trying to read global module configuration data from file 'path to the file', line number 'line number'. Worker process startup aborted.

Computer | Error | 10/27/2008 2:55:41 PM | Microsoft-Windows-WAS | 5172
The Windows Process Activation Service encountered an error trying to read configuration data from file 'path to the file', line number 'line number'.
The error message is: 'Configuration file is not well-formed XML '. The data field contains the error number.

 

 MicroSoft has a fix that may resolve your issue. The article is listed...

dpatterson3485 | 21 Aug 2014 | 0 comments

As suggested by the title I recently had a problem with MS revoking updates. It seems simple enough, but even though those updates are marked as disabled in the Altiris Database, the Zero-Day Patch workflow still tries to download them. This causes all kinds of problems because when the workflow can't download a patch it crashes. If you are like me you don't want to manually create and manage patches. So what do you do?

1. Figure out what database you are using. This seems simple enough, but if you have dealing with Legacy like we were it can get a little silly. CMDB is the default.

2. Check the correct tables in our case Altiris-2014. I jumped onto our SQL server and ran the following QUERY.

SELECT
TOP 1000 [Guid]
,[Enabled]
FROM [Altiris-2014].[dbo].[ItemActive]
--where Guid in ('41F066A7-0E7E-4BF1-B6A5-195573F9F3D6','BA28B8E2-289A-4FA3-8D6D-...