Video Screencast Help
Endpoint Management Community Blog
Showing posts tagged with Tip/How to
Showing posts in English
B_Raj | 25 Oct 2009 | 0 comments

Msispy is an utility which comes along with Windows installer SDK. If you want to troubleshoot a MSI package in component level or feature level, I will recommend this tool as the best option for repackagers.It provides a nice GUI and command line utilities which makes it very user friendly.

MsiSpy provides a component level view of the products and features installed on a system, using either an MSI Package, or the registry information. Msispy also displays the status of each, and allows you to partially or completely re-install missing or damaged items. You  can also re-configure any product or feature, selecting the install level, and specifying whether to install it locally or run it from a network server.

 Some of the main features are;

  1. It allows you to open an MSI package and display all information about it.
  2. It display information about all the products installed on the computer.
  3. Allows you to load a...
B_Raj | 24 Oct 2009 | 0 comments

This error is due to an error in Directory table of the MSI.

Generally occurs while a directory entry that references something non existent as its parent. If you ignore the ICE 03 validation error (Similar to the below mentioned Eg.) while developing the MSI,During the installation you will be getting the “Internal Error 2705. Directory” error.

Eg: of an ICE 03 error :

Orca validation reports an ICE03 error: “Not a valid foreign key; Table:Directory, Column: Directory_Parent, Key ):newfolder1″

 This error can be fixed by editing the Directory table.The wrong entries in the ‘Directory table’ will be highlighted in red colour.

WiseUser | 23 Oct 2009 | 2 comments
Success = 0
Error: General Detection error = 17301
Error: Applying patch = 17302
Error: Extracting file = 17303
Error: Creating temp folder = 17021
Success: Reboot flag set = 17022
Error: User cancelled installation = 17023
Error: Creating folder failed = 17024
Patch already installed = 17025
Patch already installed to admin installation = 17026
Installation source requires full file update = 17027
No product installed for contained patch = 17028
Patch failed to install = 17029
Detection: Invalid CIF format = 17030
Detection: Invalid baseline = 17031...
WiseUser | 22 Oct 2009 | 0 comments

When we try to install office 2007 which is 32 bit installation on a windows server with terminal services enabled you will be getting the following errors

Error Information :

Loaded Dll : \\sbc-netapp01\Install\microsoft\Sv_office_ent_2007\Enterprise.WW\OSETUP.DLL.
Catalyst version is : 12.0.4518.1014
JobExecutionMode is InstallExecutionMode.
Error: failed MsiEnumProducts ErrorCode: 2(0x2).
Catalyst execution finished: 02/08/2008 10:44:24. Return code: 30015. Exception caught: ErrorCodeOnly.
PERF: TickCount=544812 Name=RunSetup Description=End function

Solution or work around suggested for this problem

  1. Open Terminal Services Configuration.
  2. Click Server Settings.
  3. Right-click Permission Compatibility, and then click Properties.
  4. Click to select the Full Security check box, and then click OK...
BRING | 12 Oct 2009 | 0 comments

When attempting to open a workflow .package file from an external source, (which is the best way to transfer Workflow projects), the following Unexpected Exception, Size Mismatch error occurred, as shown in the screen shot. This error caused frustration, as no matter what I tried to get the .package file to open, it would not. Why? 


Well, lets first understand that the .package file is essentially just a zip file, and the file can be renamed to have a .zip extension and then extracted using standard ZIP utilities. Most of the time that will work.   In this case however,  the .package file was more than likely scanned with a virus scanner during transfer, and certain files contained in the package file probably were flagged by the virus scanner, and were removed from the .package file.  When the check sum process of...

btowne | 01 Oct 2009 | 0 comments

In NS6 there was a function called "GetItemPath" in which return the path for an object in the Console. How can I get the folder path in NS 7?

"GetItemPath" function does not exist in the NS 7 database. Here is the sql behind creating that function for changes in the NS 7 database:

USE [Symantec_CMDB]






ALTER FUNCTION [dbo].[GetItemPath]


      @Guid Varchar(40)


Returns varchar(8000)







  @SearchGuid VARCHAR(40),    

  @ItemPath VARCHAR(500),    

  @ExitCounter INT    


SET @SearchGuid = @Guid

SET @ItemPath = ''    

SET @ExitCounter = 0    


WHILE @ExitCounter = 0    


  IF EXISTS (SELECT * FROM ItemFolder WHERE ItemGuid = @SearchGuid AND ParentFolderGuid != 'D0E33520-C160-11D2-8612-00104B74A9DF')    


    SET @ItemPath = (SELECT TOP 1 [Name] + '/' FROM Item WHERE [Name] NOT LIKE '/_%' escape '/' and Guid...
Steven Grove | 29 Sep 2009 | 2 comments

I have just started a new job in a new place with new people. We have a 16 blade HP server to migrate all services to in the neat future. As of now, multiple services are running on the same servers with no (nada, zip, zero) redundancy. They know it, and they have been trying to get it up but DIACAP has taken all their time. I will chronicle my trials and tribulations on my journey to migrate the Console services and images to a new blade.

neil_rogers | 17 Sep 2009 | 0 comments

I had a call from a customer yesterday.  They had a vulnerability that had to be fix by end of day, and it was 3 pm when I got the call.

He was not the deployment server admin, and had minimal access into DS, but the admin was not available.  Passwords were getting locked out due to the issue.

Opening up the console just pulled up the sql connection option.  So here are the few steps to check:

1.  Check what services are running, Altiris services need to be running, Altiris Deployment services (2-3 of them), and Altiris Express service, Restarting will show if the account is locked.
2.  Check the ODBC connections, Administrative tools, Data Sources (odbc) -> System -> (express service) -> test the connection
3.  Check SQL services to make sure they are running.

We went on to build a new job to deploy the patch, that is for another post.

Jamee McDonald | 08 Sep 2009 | 0 comments


When under Advanced options and the view is set to 'list', right-clicking in open space results in PCA crashing.


Steps to reproduce the issue:

  1. Click on 'Go to Advanced view '. This is located in the left-hand column under 'Views'.
  2. Select 'Remotes'.
  3. Click on 'Views' at the top and select 'List'.
  4. Right-click in open space under the 'Remotes' panel.

This is when the application crashes.


Unknown at this time. Windows event logs point to ntdll.dll as the file that is involved in the failure.


At this time there is no solution or patch to resolve the issue. As a workaround a customer could do one of the following:

  1. Change the 'view' to 'icons'
  2. Change the 'view' to 'details'

Please refer back to this blog for any updates concerning this issue in the future. Should a patch or a new release resolve this...

Terry Cutler | 04 Sep 2009 | 0 comments

On Sept 8 2009 - an Intel hosted webinar occurred.   The webinar discussed and demonstrated Symantec Management Platform with Intel vPro technology.

The recorded material along with responses to questions during the webinar are available at