Video Screencast Help
Endpoint Management Community Blog
Showing posts tagged with Altiris Deployment Solution
Showing posts in English
MtBiker | 18 Sep 2007 | 2 comments

As an Altiris Administrator, I found it fairly easy to find solutions to my problems from either Connect, Altirigos or the Knowledge base. Then I took a Notification class with 8 other Altiris Administrators and discovered that I was learning more about Altiris and its products just by talking with my classmates on our breaks. I decided that Altiris should have a chat room where Administrators can discuss issues and help others struggling. I was unable to find a chat room so I created one of my own. I decided to use IRC because it was easy enough that anybody could use it.

So please join us on IRC for discussions, help, solutions and chatting.

You can access the chat from the web at 

Channel:     #Altiris

Leave me a message if you get confused or need help

You also may download a client such as mIRC at...

kbuller | 03 Sep 2007 | 0 comments

On and off over the past 6 months I've tried to figure out a way to use Rapid Deploy to image an IBM laptop with an OEM partition and keep the OEM partition functional after the image. I've hunted through the KB's and Forums and no one seems to have an answer.

Why do I want to have the OEM partition there anyway? I need to have a simple solution to quickly have the machine exactly the way it was from the manufacturer. It's handy when lease returns come up.

The only solution that has worked so far is Ghost. Eek! KB 19972 explains how to use ghost with DS here

There is something that you need to know to get this to work correctly. You have to make an image from just the partition (not the entire disk) and image down to only that partition.

I didn't...

SK | 20 Aug 2007 | 2 comments

If you're like me and require a database that has thousands of resources in them, then the Fake Name Generator is for you.

This site now offers to create 40,000 fake names for free. :-)

If you have them populate a CSV file, you can then import them into DS or NS. :-)

eorme | 16 Aug 2007 | 0 comments

Deployment Solution for Dell Servers 3.0 has the ability to communicate with BMC and DRAC devices on Dell Server hardware via the Deployment Console. In order to enable this feature however, DRAC and BMC devices must be "discovered" using the Dell Configuration Utility. This process systematically pings a block of IP addresses searching for DRAC or BMC hardware.

By default, a range of IP addresses will be broken into 15 address blocks, and all pinged in parallel. This can be increased however, to any arbitrary size.

Do the following:

  1. Make sure all Dell utilities are closed (Job Builder, Configuration Wizard, Configuration Utility)
  2. Open your SQL database manager
  3. Open the dbo.dell_settings table
  4. Locate the PowerControlDiscoveryBreadth value, and change it's value from 15, to a larger value (for...
sumit_altiris | 16 Aug 2007 | 1 comment

We recently learned a valuable lesson while creating images using Deployment Solution. We learned (the hard way) that the default mapped path for the SHARE is f:\servername\eXpress. Unfortunately, eXpress is not a folder name but it is a share name.

Hence, (lesson learned) whenever you make changes to the deployment share make sure that the share name is eXpress. If you don't, you'll need to make an the appropriate change to the task.

Hope this helps.

eorme | 09 Aug 2007 | 0 comments

Deployment Solution for Dell Servers 3.0 no longer requires that users supply utility partition images from DSA CDs, but instead ships with the utility partition image that ships with the DTK. This utility partition image should work will all servers.

It may be necessary, under some circumstances, to change the image that is being deployed. Perhaps a newer version of the DTK was released with a new image, or an older image needs to be used for compatibility issues. Regardless of the reason, this image is a file located within the datastore under: Dell\Toolkit\Systems\upimg.bin.

If you update this file, it will then be used on all Scripted OS Deployment Jobs whether already existing or newly created.

As always, it's safe to keep the old image around in case something goes awry.

eorme | 08 Aug 2007 | 0 comments

Installing a Japanese version of Microsoft's Windows Operating System using Deployment Solution for Dell Servers and the Linux preboot has a "gotcha" that in some cases might cause some confusion.

If the DS server is installed on a Japanese Operating System, the installer tweaks the template unattend file that will be used when deploying a Windows OS changing the keyboard, and language settings to Japanese. More importantly however it also changes the Linux script that launches the Windows Installer. It changes the executable being called from "winnt.exe" to "winntus.exe". While this "fixes" the issue of not being able to install Japanese OSs while using a Japanese Deployment Server, it also ONLY allows you to install Japanese OSs from then on (only applies to Linux preboot).

In order to deploy English and Japanese OSs concurrently,...

Global_Altiris | 06 Aug 2007 | 26 comments

Many of the new HP computers come equipped with the latest SATA drivers. This has caused a number of issues including Bluescreens and "Disk Drive Not Found" errors. For those of you who already have SATA set up in your Windows PE PXE image, you'll need to make adjustments to the Boot Disk Creator (BDC) in order to image this machine. We ran into this problem with the new HP 6910P laptop model, and more are sure to come.

This assumes Windows PE, and DS 6.5/8

The KB on adding the SATA drivers is still correct but you may find newer models that run the ICH8M or ICH9M driver, instead the ICH7M. Obviously you have to still support both, but they do not play well with each other when imaging with DS.

Originally, when you added SATA drivers, (ICH7M) you built the folder structure in the BDC under WinPE>I386>system32>diskdrivers>iaahci, per the KB article. Unfortunately, these older drivers do not work with the newer versions of SATA now appearing on the...

townhous13 | 03 Aug 2007 | 2 comments

While I've seen this in several forums, it is a cool trick that doesn't seem to be that well publicized.

If you're planning on reinstalling Deployment Server and don't want to research all your existing licensing info when you reinstall (and who, pray tell, does?) this tip's for you.

If you are planning on reinstalling Deployment Server, first make a copy of the express.exe from the old installation, rename it to express.lic and set it aside.

Once you have reinstalled DS, copy that express.lic back onto the machine. Use Product Licensing Utility to point to that file and all of your licensing will be exactly the same as it previously was. No need to hunt down the old .lic files used with the original install.

Comes in very handy when some of those old files are missing like I ran into several weeks ago. Hope this helps...

daggy_b | 30 Jul 2007 | 7 comments

Just an FYI for others out there. We have our Altiris Deployment Server running on an HP DL380, and I wanted to run two 1 Gig NICs to the server and team them. After I teamed the NICs together, I changed the network settings to disable the TCP Checksum Offload. With these network settings, we were only able to deploy an image to about 10 to 15 computers at a time without problems.

I have since taken the team NICs off, and am only running 1 NIC on the server. We are now getting a full lab of 30 computers to go at one time before we have problems. I'm not sure why this happened, but if anyone else out there has a teamed 2 Gig connections and experienced similar results, you may want to try taking the teaming off. It made a huge different for us.