Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Endpoint Management Community Blog
Showing posts tagged with 7.x
Showing posts in English
JKrauseCUSA | 06 Jan 2012 | 0 comments

Canon USA has a full time opening for a Senior Client Technologies Analyst at our Lake Success Headquarters. The ideal candidate will be an expert in Altiris Notification Server & Deployment Solution. The position can be viewed at:

If you or anyone you know is interested, please reach out to Jennifer Krause at

ianatkin | 06 Jan 2012 | 1 comment

Been working over the last few days trying to finish up a project for a standalone Altiris imaging wrapper for Linux. The idea is to re-create the basic Windows RDeploy interface in Linux. But with less features... thankfully.....

The requirement is to be able to boot from a USB device and to be instantly thrown into an offline imaging menu where they can either upload an image to the USB device, or download an image from the device to the computer. Mostly there, but as usual (for me) the last 10% of the project takes up the bulk of the time....

Using whiptail to drive the menu, and lots of bash scripting goodness to bring it all together.

Very challenging piece finished today -the disk info screen. Now have the systems disks indexed nicely with partition ennumeration. The images on the source drive listed with sizes.

Some handy links...

A tip which finally showed me...

ianatkin | 20 Dec 2011 | 2 comments

Beta testing on the Symantec Management Platform is a pain. The hardware prerequisite for a responsive console throws the traditional workstation beta testing VMs out into the cold. Whilst they work, it's pretty frustrating beta testing when you're waiting ages for console refreshes.

So.. for this round of beta testing I decided to bite the bullet and get a OCZ RevoDrive for my beta testing virtual machines. The Revodrive 3 240GB capacity is more than enough to house my beta SMP server, domain controller, a site server,  some dhcp routers and a couple of client VMs.

I am not disappointed. HDTune registers drive transfer rates of over 400MB/s and 0.1ms access times. Even within a VMWare workstation VM, the times are sweet. When benchmarking within a VM, the most notable change is in the access time. Initial tests show this ballooning to over 0.7ms, but in context this is still 20-30 times faster than my harddisk!

My Windows 2008 R2 server VM...

Vaibhav Sharma | 02 Dec 2011 | 1 comment

When any new driver/s are added to Deploy Anywhere/Preboot Driver Database Manager; being these special packages with dynamic data, it takes 8-10 hours to replicate these to existing Site Server under corresponding folder if if added single driver.

This creates following issues:

  1. During DA process of Imaging or SOI; user will not get correct drivers added to its computer working under a particular Site Server
  2. During Preboot creation; user will not find the appropriate drivers inside image which are getting created at Site Server before driver replication

So once the drives are added at NS; following is the method to achieve such driver replication immediately/on demand:

Go to SM Console > Settings > All Settings > Deployment and Migration > Drivers > [{Click on the package type for which drivers are added} (Say Drivers) > on Package Tab {Click Update Distribution Points} [Below is the image to present the same]...

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" (...