Video Screencast Help
Symantec Appoints Michael A. Brown CEO. Learn more.
Endpoint Management Community Blog
Showing posts tagged with Deployment Solution
Showing posts in English
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...

vikasj | 05 Jan 2012 | 0 comments

We purchased an HP Compaq desktop which has Windows 7 and recovery partition buit in. We tried to deploy a Windows XP image on the same model but it fails every time after the completion of deploy image task.

In the Deployanywhere.txt logs we found critical drivers were missing, but all the necessary drivers were present in the Driverdsb.

Next we tried to install the operating system through our Volume License CD Key, but after verifying all Windows files it gives a blue dump. After that we found it is related to some Hard Disk setting in BIOS.

It is not a drivers problem.

We changed the BIOS SATA Emulation setting from AHCI to IDE mode and my image deployment problem on HP Compaq 6200 desktop with Windows 7 and recovery partition built in is quickly resolved.

On it I selected two tasks:
1. Deploy Image (Deployanywhere option should be ticked)
2. Reboot to production

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

Steven.Riley | 13 Dec 2011 | 0 comments

About Windows-to-Mac Migration Script Tool

The Windows-to-Mac® migration scripted tool provides a simple framework to begin the process of moving Windows user profile files (e.g. documents, movies, photos, music files, iTunes® settings, IE favorites (links), etc.) from a Windows environment to an Apple® Mac. The concept is to capture the majority of the files that a user in a Windows environment uses and move them to their Apple machine. The user items that will be migrated are dependent on the version of Windows that they are running. The Symantec Management Platform is leveraged to run tasks on the Windows computers that need to be targeted. The scripts determine via a data file located on a file share which Apple computer to target for the data. This simplifies the migration of many computers and allows a simple “mass” migration path as needed. Further, once the framework has been put in place the entire process can be...

ianatkin | 07 Dec 2011 | 11 comments

When imaging machines over and over in testing, we occasionally find that after a reboot (initiated by an agent power control task) that the AClient just stops responding. We are using here DS6.9SP4.  We see,

  1. The AClient process is still memory resident
  2. netstat shows TCP 402 still ESTABLISHED
  3. service does not respond to stop requests
  4. Log file is not written to

So, the AClient is pretty much dead. The process needs to be killed, and the service started.

This is a pain though, as when deploying large numbers of machines the unresponsive agent eats into our success statistics and causes frustration. So... how to see if the AClient is running?

Been puzzling this over last night, and came up with the following script with the ever helpful Darren...


'# VBScript to get some AClient process and log
'# data so that we can see if...
grinstb | 05 Dec 2011 | 0 comments

During a patch you get the error that there are remote console sessions open.


Use the configuration tool to clear all connections to the deployment server.


altiris->deployement solution->configuration  the clear connections

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 | 29 Nov 2011 | 1 comment

This is a frequently asked question on forum about required IIS7 settings for Package Server configuration and there are how-tos available. But I though to put it in a simple manner in form of image which much easier in understanding. Where “red circled” are only not required components

Hope this would be helpful.


Vaibhav Sharma

ohzone - CherylPeterson | 28 Nov 2011 | 0 comments

Windows IT Pro (and sister publications SQL SERVER and DEVPRO) 2011 Editor’s Best and Community Choice winners have been officially posted. Symantec was honored with 13 awards with great representation across our diverse portfolio of products. For a complete list of award winners go to

Windows IT Pro

Best Patch-Management Product
Community Choice

Gold: Altiris Client Management Suite

Best Management Suite
Community Choice...