Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Endpoint Management Community Blog
Showing posts tagged with Deployment Solution
Showing posts in English
pioneer | 08 Oct 2008 | 1 comment

Our company has recently purchased the Altiris Deployment Solution only to find out there was no support for solaris 10 sparc or x86. Altiris logged the below feature enhancement request on our behalf.

So, if there are any other companies out there using solaris and would like this feature please subscribe to the request to put some weight behind supporting solaris. Article ID #43841

Nelo | 08 Oct 2008 | 3 comments

A change to the PXEManager.ini allows a PXE menu theme.

To change the default PXE them open the PXEManager.ini with your favorite text editor and change the following:

  1. Stop the PXEManager service.
  2. Open PXEManager.ini with notepad
  3. Under the [PXEConfig] section change PxeSrvBoot="0,0" to PxeSrvBoot="3,96"
  4. Save the changes. Close the file.
  5. Start the PXEManager service.

Now the next time PXE comes up on initial deployment a PXE Halloween theme is displayed.

sumit_altiris | 07 Oct 2008 | 0 comments

Be careful while deploying ADLAGENT to a Red Hat Enterprise Linux 5.0. If you have already installed ADLAGENT on RHEL5.0 and are trying to again install ADLAGENT while not removing the agent completely then you may encounter big trouble -all OS files will get deleted.

I've tested it several times and have concluded that all the files of RHEL are deleted if one tries to install ADLAgent on a system where ADLAGENT has already been installed and not removed completely. So better be careful while installing ADLAGENT.

Environment: Deployment Solution 6.9
Operating System: RHEL 5.0

dnorris | 07 Oct 2008 | 0 comments

When packaging an application requiring an exception within the XP firewall, you can automate the exception using netsh.

The XP firewall can be configured using the firewall command of the netsh utility. For full usage options, type the following:

netsh firewall ?

To add a program exception to the firewall, you will need to specify a descriptive name for the exception and the path to the executable. For this example, we'll use a description of SomeAppException and an executable path of C:\Program Files\SomeApp\App.exe.

The following script performs a check to ensure that XP is running, then calls the netsh command.

REM Allow exception in XP Firewall

REM Only perform this for XP
ver | find "XP" > nul
if %ERRORLEVEL% == 0 goto Is_XP
goto exit

:Run Windows XP...
Pikoshi | 03 Oct 2008 | 2 comments

I recently had a coworker who wanted an easy way to reimage a machine while at the machine. Since we use HII, I needed to find a way that he could select the whole job since it includes driver injection based on the computer model. Upon investigation, I found an option within the Linux Pre Boot environment.

The Linux agent portion of the preboot environment has a parameter called FORCE_NEW. By default this is set to false. If you set it to new, every time a computer boots to this pre boot environment, it will be treated as a new computer and automatically go to the initial deployment screen.

Nelo | 02 Oct 2008 | 3 comments

Ubuntu by default creates a symbolic link for "sh" that points to "dash". Modifying the "sh" to point to "bash" will allow the adlagent to install and be configured.

The following are the steps to point "sh" to bash:

  1. Open a Linux shell in an Ubuntu machine.
  2. CD to the /bin folder.
  3. Type "sudo rm sh" without the quotes and press enter.
  4. Type "sudo ln -s bash sh".
  5. Finally, execute "sudo ./ altiris-adlagent-x.x-xxx (this is the version of the adlagent).

If everything worked ok you should see the following:

Linux i386
 Adding system startup for /etc/init.d/adlagent ...
  /etc/rc0.d/K20adlagent -> ../init.d/adlagent
  /etc/rc1.d/K20adlagent -> ../init.d/adlagent
  /etc/rc6.d/K20adlagent -> ../init.d/adlagent
  /etc/rc2.d/S88adlagent -> ../init.d/adlagent
erikw | 01 Oct 2008 | 1 comment

I found a very good article about PXE errors, and I wish to share it with you.

In the article the Sun blade is described with Linux, but the errors are general and you will find it still very worthwhile. It is one of the documents that I have saved in my favorites.

Erik Westhovens

Nelo | 29 Sep 2008 | 0 comments

Deployment Solution 6.9 adds a new feature to import/export computers to an XML file.

The XML file contains the computer name, asset tag, serial number, UUID, NICs information. The most useful information is the computer group that the computer is a member.

Importing computers now allows importing an XML file and such file could now be modified to import multiple computers to computer groupings in the Deployment Console.

Import and Export computers is located under the File Menu - Deployment Solution Console.

The following is an example of one computer:

- <?xml version="1.0" encoding="utf-8" ?> 
- <computers ver="14" xmlns:xsi="" -xsi:noNamespaceSchemaLocation="computers.xsd">
- <computer>
- <name>RACK01C10</name> 
- <...
CondorMan | 29 Sep 2008 | 13 comments

I recently installed Deployment Server 6.9 SP1 Beta and noticed that the Distribute Disk Image task now has the option "Use DeployAnywhere hardware independent imaging"!

With this option enabled, I can deploy a single image to computers with different mass storage devices without even preparing it with sysprep beforehand. No more mess-work!!

nravenscroft | 26 Sep 2008 | 1 comment

PXE boot option will not map a drive (default F:) to the DS. All the configuration seems correct and the password has been verified.


Altiris uses a LAN Manager Hash file to store and use the password. Most security polices require the hashing of passwords to be disabled for the domain /server. This is normally disabled via group policy in the Network Security: Do not store LAN Manager hash value on next password change setting being enabled.


In most environments it will not be possible to enable this setting across the domain due to security policies. But you can do it for local accounts if you move the server in question to an OU where a policy over the Network Security: Do not store LAN Manager hash value on next password change to disabled. After the policy...