Video Screencast Help
Endpoint Management Community Blog
Showing posts tagged with Altiris Deployment Solution
Showing posts in English
erikw | 23 Sep 2008 | 2 comments

When you install Deployment Solution on a network where other software is already running that uses PXE, you can get in serious trouble.

I found a document that explains what to do when you want to install Deployment Solution on a network that is already running Ardence.

Read it, and get started.

BRING | 17 Sep 2008 | 0 comments

When using Deployment Solution to roll out new IBM x3850 servers, the Linux PE environment received an interesting error when attempting to boot:

'badness in do_exit at kernel/exit.c'

This particular server had 16 processors. Apparently the Linux kernel configured for this boot process was unable to correctly address multiple processors.

Fortunately, this was a fairly simple fix. Deploying the image was not really a multi-processor critical operation. By adding the 'maxcpus=1' statement, as defined below, the kernel was then configured to only operate using one CPU. This resolved the problem.

In the MISC folder


CommandLine="root=/dev/ram0 rw ramdisk_size=32768 maxcpus=1"


default linux
label linux
 kernel linux
 append initrd=rootfs.gz root=/dev/ram0 rw ramdisk_size=262144 quiet...
Antonp | 12 Sep 2008 | 3 comments

As we all know RDeploy gives us the function to convert an already caputered image.img file to image.exe file.

Recently I created a DVD bootdisk with the image spanned over multiple DVD's. I had an .img image that I used in the process.

The WinPE booted fine, but then prompted me to enter the last disk the whole time, even if I did enter the last disk, nothing happened. I then proceeded to load RDeploy in the GUI mode and browse to the image location, cool I found it, but was unable to load it as RDeploy said it cannot access that image file. Bummer....

So then I converted that same .img file to an .exe file on the DS in "Image Explorer", went through the same process and the same end result.

We then thought that the conversion process might have corrupted some files or not properly converted the .img to .exe....

jjesse | 12 Sep 2008 | 0 comments

Just a quick note, that if you are imaging and deploying SUSE Enterprise Linux on VMWares's ESX server you need to be on the latest version for it to work correctly.

If you are running 3.1 when you deploy the images, eth0 does not come active after the reboot and you must manually reconfigure it through YaST.

If you upgrade your ESX box to 3.5 the deployment of the image functions correctly.

dnorris | 10 Sep 2008 | 10 comments

BIOS updates can be automated along with your standard deployment routines. A single job can be used regardless of the model being deployed.

We'll first make use of the Condition feature on DS jobs and then of a command-line parameter available on Dell BIOS update files.

Create a new job in your Deployment console, click the Setup button in the Condition section and create a new condition. Name the new condition to describe the computer model.

This example shows the condition for a Latitude D630.
For the...

CondorMan | 29 Aug 2008 | 3 comments

If you ever need to script NTFS permission changes, SetACL is a powerful alternative to CACLS. Here is a command line that will use SetACL to grant full control to the Administrators and System accounts on folder and all subfolders:

SetACL.exe -on "C:\Program Files" -ot file -actn ace -ace "n:administrators;p:full" -ace "n:system;p:full" -actn clear -clr "dacl,sacl" -actn rstchldrn -rst "dacl,sacl"

erikw | 29 Aug 2008 | 0 comments

In the deep, dark recesses of my harddisk I found this very useful demonstration Joel Russel created.

It explains the installation for the DS 6.8 console and the difference for the Thin Client version. Watch and enjoy.

CondorMan | 28 Aug 2008 | 0 comments

The DSWeb Console and NS Console require .Net Framework 1.1 to be registered with IIS.

A quick way to fix this (or script this for multiple installs) is to run the following command:

%SystemRoot%\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe -i -enable

CondorMan | 25 Aug 2008 | 1 comment

To silently install .Net Framework 2.0 with SP1, follow these two steps.

  1. Download NetFx20SP1_x86.exe from Microsoft
  2. Distribute NetFx20SP1_x86.exe via Deployment Server or Software Delivery Solution with the command-line parameters: /q /norestart

If the silent install finishes with return code 3010, that means that a reboot is required.

CondorMan | 25 Aug 2008 | 0 comments

If you need to silently install the .Net Framework 1.1 to multiple computers, you can follow these two simple steps.

  1. Download the Microsoft .NET Framework Version 1.1 Redistributable Package (dotnetfx.exe)
  2. Crete a Software Delivery Task or Deployment Server Distribute Software Task that runs dotnetfx.exe with the command line parameters: /q:a /c:"install /q"