Video Screencast Help
Endpoint Management Community Blog
Showing posts tagged with 7.x
Showing posts in English
Vaibhav Sharma | 30 Nov 2011 | 0 comments

1) Open the registry and go to ‘HKEY_LOCAL-MACHINE\SOFTWARE\Altiris\Deployment’ and check for the presence of the ‘DebugLogs’ string value. If it is not present, add a string value and point to a directory where you would like logs saved.  Cory believes this registry key is currently set to ‘c:\altiris\altiris agent\logs’.

2) Go to the directory mentioned in #1 above.  Delete all logs that are present.

3) Go to ‘c:\windows\debug’ and delete the ‘netsetup’ file.

From the Altiris Console do the following:

1) From Jobs and Tasks create a new ‘Apply System Configuration’ Task.
2) Create  a new ‘Use a predefined system configuration’.
a. Name: Test1
b. Domain: Put in your fully qualified domain name (FQDN).  E.g.  If your domain name is ‘’, enter this in the domain field.  DO NOT enter the netbios...

Vaibhav Sharma | 25 Nov 2011 | 0 comments

Deployment Solution 7.x reports are very easy to get and can be saved in many supported formats.

Most of the DS users already be knowing this but this would be helpful to those new users who are exploring the DS afresh :)

Following is the way to get the DS reports:

On Symantec Management Console > Reports > All Reports > Reports > Deployment and Migration > Computers with Deployment task execution status > {Use filters as required} and “Save as”


Hope this would be bit helpful.


Vaibhav Sharma

ianatkin | 21 Nov 2011 | 1 comment

In preparation for our DS6.x to 7.x upgrade path, I'm looking at how to document DS6.x jobs. Ideally, I'd like to be able to point a SQL Script at a DS6.x Job and have the entire job nicely documented as an HTML report.

Looking at our job trees, I need to document first and foremost,

  1. 'Copy File' tasks
  2. 'Run Script' tasks

These make up the bulk of our DS6.x jobs. Our imaging tasks are typically done with automation 'Run Scripts'.  After a couple of hours I've been able to come up with some SQL which documents a Copy Task as two tables. The first table gives the job details (copy src, dst etc) and the second documents the return code behaviour.


Chucking this up to connect so I don't lose it. ;-)
-- T-SQL to export a Copy ...
R Gines | 13 Oct 2011 | 8 comments

Attached is a poll that we'd like to use to help us determine what supported Linux OS is most important to you. The Poll is open for several weeks so please make your opinion known!



Bourdin Laurent | 11 Sep 2011 | 1 comment

I wrote this words to answering in another bog entry, but I think these simple facts are so significant that they can be a stand alone blog entry if some product manager or devellopper read this blog.

Just for fun, some DS7.1 integration way :

- You have a wonderful tool to create PXE Preboot (Bootwiz). This tool include an agent (Dagent for DS6.9) and a way to include OEM (Dell, HP,...) tools. When you want to change the Agent (PECTAgent for DS7.1), the Symantec way is to drop the original agent and add the new agent through the OEM function. It's ... dirty ???

-You have a tool to replace tokens in your Tasks scripts. You want to implement a replacement token tool for unattend and sysprep files. Extanding the usage of Tokens is not a good idea, it's better to creat a new token replacement process without any user control (changing the %TOKEN% to @TOKEN) and put this tool directly on a dll on the PECTAgent. It's ... stupid

-You deploy a new...

Pascal KOTTE | 10 Sep 2011 | 12 comments

When talking OSD (Operating System Deployment): we speak about "DS" (Altiris Deployment Solution)...
But when speak about DS, must ask for "6.9 or 7.1" ?

About DS 6.9:

We already build with success a single DS 6.9, with 60 remote sites (or perhaps 55 only, but 2 times). So we can afford 60 secondary PXEs, connected to a single central DS.

Where is the maximal limitation ?

Well, in theory, only a total of 5'000 machines can connect the central DS server. I am pretty sure we can upper this number using Windows 2008.

Regarding numbers of remote sites maximum: a secondary PXE will only connect the DS central a single TCP session...

We often got a problem using DS 6.9 because of any change preboot files, immediate impact thousand remote sites, and overload WAN. The workaround is to "stop" the PXE config helper on each site, to start only during "maintenance hours" (...

Bob Kohn | 24 Aug 2011 | 0 comments

Position located on Long Island NY.  Long term and willing to pay excellent rate at this point.

Looking for a Highly skilled Altiris Engineer \ Subject Matter Expert with a strong command of:

  • Altiris Asset Management
  • Workflow coding
  • knowledge of programing methodology and knowledge of SQL
  • understanding of itil framework is a nice to have skill.
  • Also willing to expand your duties to include solving complex third level support issues if\when needed 
  • Resumes to - I promise to get right back to you.
Ishani Bose | 18 Aug 2011 | 0 comments

1. PXEPreZero : Invalid format –

Issue : PXE Image is corrupted

Solution: Recreate the PXE image from Preboot Configuration Page.


2. PXE-E53 No boot filename received

Issue: : Client not able to connect to PXE Server, probably not got IP address. If it has got IP than the PXE image does not exist to download it from PXE Server.

Solution : Probably the PXE image not yet created at NS\SiteServers. Check location - \\localhost\Deployment\Task Handler\SBS\Images\if the PXE image exists.


3. PXE-E55:ProxyDHCP service did not reply to request on port 4011

Issue: Firewall must be ON.

Solution :  Disabled the firewall or open port 4011.


4. PXE-E32: TFTP open timeout.
Issue : TFTP open request was not acknowledged. The "PXE-E32...

Sachin_Joshi5 | 18 Aug 2011 | 5 comments

This blog lists different Linux known issues & limitations in Deployment Solution 7.1 and its components. The items in list will change as and when some support will come in the product or some new issue needs to be documented.

Following are the known issues/limitations in Deployment Solutions 7.1 pertaining to  Linux:

  1. Imaging of Dual boot(Linux & Window) disk is not supported by DS: Creating & restoring image of dual boot disk is not supported by Ghost & ultimately by DS 7.1.
  2. Creating Ext3/Ext4 partitions through DS is not supported: Ext3/Ext4 partition creation is not supported through DS. Only ext2 partitions  can be created using DS partitioning mechanism.
  3. Creating image on HTTP/HTTPS server with authentication is not supported: Creating image on HTTP/HTTPS with authentication is not supported. 
  4. Linux Scripted OS...
R.V. | 07 Aug 2011 | 0 comments


With this blog entry I'm starting to post short troubleshooting tips/steps for Deployment Solution. 

Some of the information I'm puting to these blog post will be most likely in our KB system as well but I hope there will be information/steps that can be useful for users who are not yet very familiar with Deployment Solution 7.1 and need to do some troubleshooting.


I'll start this blog series with basic troubleshooting steps for Package Server. 


1- Verify if the computer is in a site

DECLARE @cName varchar(64)

SET @cName = 'Computer Name'  -- Name of the target computer

SELECT DISTINCT as Site, c.Name as Computer, s.Subnet, s.[Subnet Mask], c.guid


JOIN dbo.vSubnet s

JOIN dbo.vItem i

JOIN dbo.vSiteSubnetMap sm

   ON i.Guid = sm._ResourceGuid