Video Screencast Help
Endpoint Management Community Blog
Showing posts tagged with Altiris Deployment Solution
Showing posts in English
songs | 19 May 2008 | 0 comments

On page 187 in the DS SP2 Admin guide, it shows an example of the WLogEvent command used with the -ss switch inside double-quotes. While that syntax may work for you, it didn't for me. As expected, you need the switch (-ss) outside of the quotes, and the message you are sending (if spaces are included) to be quoted.

From the manual:

.\WLogevent.exe -c:0 -l:1 "-ss:Finished with the DIR command on %NAME%" 

What worked for me:

.\WLogevent.exe -c:0 -l:1 -ss:"Finished with the DIR command on %NAME%" 

Another curious issue is that when attempting to use WLogEvent to return various return codes from a script, I could only get the task to process the return code correctly if the level (-l switch) was a 3; level 1 and 2 were ignored regardless of the return code provided (-c switch). Perhaps the latter was by...

frankvandebergh | 16 May 2008 | 0 comments

When you want to add a virtual center server to the Altiris Deployment console, you previously would just need the hostname and authentication settings for the virtual center server. As long as you installed the Web Service component in Virtual Center 1.x everything worked just right.

With Virtual Center 2.x, this web service is now more embedded into the product, and using a different default port, 443 instead of 8443.

When connection to Virtual Center from deployment console, make sure to use port 443. You can change the port in the configuration of the VI client.

Also make sure you select "Virtual Center 1.x compatible" under the Web Service options in the options screen of the VI client.

vortex0007 | 15 May 2008 | 7 comments

The best way to install the Altiris AClient as part of the base imaging task, is to have the Deployment Server copy the most recent version of the AClient to the local drive, followed by a call from the Windows XP Cmdlines.txt file to run the installation.

This method ensures your clients always have the latest version of the agent and ensures freshly imaged computers still can be properly managed.

Unfortunately the command line options available for the aclient install are not as wide-spread as they should be.

Here's what the cmdlines.txt should look like to make this successful. And yes, the quotes are required:

"c:\altiris\aclient\altiris-aclient-6.9.164.X86.exe c:\altiris\aclient\aclient.inp -silent -install -scriptedinstall"

Nelo | 15 May 2008 | 6 comments

The size of the WinPE boot file looks scary when multiple clients are downloading it in a PXE boot. I have found a way to reduce the size of the boot.wim file to 33% less in size than the boot file that Boot Disk Creator creates and of course it downloads 33% faster. The end result should have a 110 Meg size WinPE boot file.

In order to create a play environment, create a second WinPE PXE configuration, meaning create a MenuOption that will not be the first WinPE. The first WInPE PXE configuration is set by default to MenuOption131. We want to play on PXE MenuOption160 or greater.

Also, this assumes that WAIK is installed in your DS server or the Altiris WInPE 2.1 installers were installed.
One more thing, this example is only for x86 proc. The batch file could easily be configured to make the changes for x64 and ia64.


TilakGovind | 08 May 2008 | 3 comments

There are cases where an application needs access to a drive like H: to complete the installation of an application. Since, for example, you might be working on a VMware machine using a local user account.

Here's a trick to help you overcome this obstacle.

Instead of mapping your drive to a production drive, you can fake a drive on the machine using the Subst.exe command. You can fake an existing folder on the machine as a drive.

For creating an H: drive

  • Create a folder under "C:" eg. C:\test
  • Then use this command at command prompt:
    subst H: C:\test

Open My computer and you will see an H: drive there.

MyersW | 05 May 2008 | 14 comments

So the debate went through our office about what is the best pre-image environment... WinPE, BartPE, Linux or DOS. Consequently, we tried to do a complete analysis of many of the factors and determine what is really the fastest route to take. In the end, it all comes down to how quick we can get our imaging done and move on to other projects.

We took an older Compaq D5M as workstation to image and ran it through some tests. The workstation has a 10/100 MB NIC and was imaged from a server across a LAN link. All networking equipment in the link was at least 10/100 MB. We first pulled down a 4.5 GB image using each of the pre-image environments. What we found was...

Environment Time Approx. Avg. Speed
DOS 20:29 10-15 Megs
Kinetic | 24 Apr 2008 | 11 comments

I was setting up an NS server today for the first time and ran into some problems.

Everything installed just fine. Across the board everything looked green, but then I tried to setup up the proxy configuration in the console.

IIS crashes. I reset it and again it crashes.

What in the world did I do wrong?

I didn't RDP into the server using the /console switch:

mstsc /console

After that, I did a complete reinstall and everything went smooth.

This is VERY important when working with servers, especially an Altiris server. In fact, you should probably just set a shortcut to always use the /console switch. Seems like something we all take for granted, until the one time you don't use it and everything gets hosed.

UPDATE - With Vista the switch is mstsc /admin. - Thanks Caleywoods!

CondorMan | 18 Apr 2008 | 3 comments

PowerShell is the new powerful scripting language created by Microsoft. You can install it to Windows XP and above and it is included in Windows Server 2008.

Here is how to run a PowerShell Script through Deployment Server.

  1. Create a new job.
  2. Add a Copy File task
    • The source path points to MyScript.ps1 on the Deployment Server.
    • The destination path is .\MyScript.ps1
  3. Add a Run Script task as the following:
    powershell -command "& { .\MyScript.ps1; exit $lastexitcode }"
    set ret=%errorlevel%
    del .\MyScript.ps1
    exit %ret%
Shadrocks | 16 Apr 2008 | 6 comments

A simple tip to track changes is to create a registry key under "HKLM\Software\\". When you run scripts or installations it is simple through almost all languages to add a string value with some information like install time.

By creating these keys, it becomes very simple to create logic in DS deployment scripts to make decision trees for future deployments and upgrades. This is also helpful for future auditing.

REG (REG /? from a DOS prompt to get help) is a magnificent tool to add registry entries with through DOS and it’s built into XP SP2. It can also be used to Query your key. Vbscript uses RegWrite and RegRead to perform the same actions.

Good luck with your new tracking options!