Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. 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...

Mauro Dalvit | 18 Dec 2014 | 0 comments

If you are experiencing problems booting into WinPE 4.0 or PECTAgent connectivity issues( eg: unknown computer unable to connect to altiris server. PECTAgent.exe error) it may be because you are missing some NIC or Storage driver.

(For troubleshooting purposes also try to change the BIOS options from AHCI to IDE)

HP provides a sets of drivers specifically designed to work with WinPe 4.0

HP Elite 8300 SFF, HP 8200 SFF and HP EliteDesk 800 G1 as now(December 2014) share the same package, named sp64529. This includes NIC and Storage drivers for both x86 and x64

http://h20564.www2.hp.com/hpsc/swd/public/readIndex?sp4ts.oid=5037932&swLangOid=8&swEnvOid=4131

http://h20564....

Igor Perevozchikov | 16 Dec 2014 | 7 comments

Very often user wants to know and see list of managed endpoints, which aren't reporting their basic inventory to NS Server - Last 'N' Days

  • Attached "Computers which are not reporting basic inventory _ already last 'N' days.xml" report is created on SMP 7.5 SP1 HF4 (Should for 7.5.x as well)
  • Attached "Computers which are not reporting basic inventory _ already last 'N' days (7.1 SP2 MP1.1 v10).xml" is created on 7.1 SP2 MP1.1 v10 and should work for 7.1 SP2 MP1.1 vx versions.

222InactiveComputers.jpg

How to import existing .xml report

  • Open SMP Console -> go to "Reports" -> mouse right click menu on root "Reports" folder -> click "Import" -> choose required .xml -> click "OK".

...

Mauro Dalvit | 16 Dec 2014 | 0 comments

DA logs location and use on tech-notes below:

http://www.symantec.com/docs/DOC7408
http://www.symantec.com/docs/HOWTO95200
 

"DA logs are copied to production during the "Reboot To" production task (translation, if you do not run a reboot to production task and reboot another way, the logs are lost). The logs can be found here:
Automation: x:\program files\symantec\deployment\logs
Production: %\Program Files\Altiris\Altiris Agent\Agents\Deployment\PreOS_Task_Logs"
 

DA logs are returning errors below:

C:\Program Files\Symantec\Deployment\DriversDB\Intel.MEI.9.5.10.1658\heci.inf is failed in inf validation(IsINFValid()). So not considering for DA operation. Error: File not found fileExists( C:\Program Files\Symantec\Deployment\DriversDB\Intel.MEI.9.5.10.1658\...

Jan Trnka | 15 Dec 2014 | 0 comments

For maintenance purpose you may like this report:

Security_Roles.png

You can easily create your new SQL Report with Role Name, Created/Modified Date and Description:

Here is the query for you:

SELECT TOP 1000 [Name]
      ,[CreatedDate]
      ,[ModifiedDate]
      ,[Description]
  FROM [Symantec_CMDB].[dbo].[SecurityRole]

You can use it along with Report of Security Accounts

Mauro Dalvit | 09 Dec 2014 | 1 comment

The "Prepare for image capture" stays on "waiting for agent to get the task"indefinitely or until it times-out

The SMA on the client machine gets the task

Sysprep runs for few seconds and then it stops without returning any error message to the SMA/Console

56.jpg

When running Sysprep manually on the client,

C:\Windows\System32\sysprep\sysprep.exe /quiet /generalize /oobe /quit

we are prompted with the following error:

57.jpg

at this stage the client has probably been kicked out from the Domain and put into a Workgroup.

FIX:

1 - implement the workaround at page 15 of the release notes below:

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

2 - Run instructions at...

Mauro Dalvit | 09 Dec 2014 | 0 comments

The Create Image Task fails with generic error:

"ErrorMessage: The Exception have occured in Client Imaging Task. Exception has occured in File Tcube_ClientCaptureImage.cpp at Line No 815. Type of exception is ClientCaptureImageException. Error Description is Child Process returned an error. The exit code from process is 1. Value of Windows error code = 183 and message is Cannot create a file when that file already exists."

1 - Investigating the log folder of the client machine in Automation:

X:\program files\symantec\deployment\logs\

we noticed some Ghost .dmp and txt log files were present; this means Ghost has failed and generated the logs

2 - there are two GHOSTERR_.txt files:

on the first the rror is:

"Error Number: 51928
Message: Invalid URL failed to create the image file.
 HTTP Result: 401, SSL error: 0"

this error is quite misleading

on the second:

...