Video Screencast Help
Endpoint Management Community Blog
Showing posts tagged with Altiris Deployment Solution
Showing posts in English
Antonp | 07 Jul 2008 | 4 comments

Resetting a local user account on one or more computers on your network, whether they are in a domain or workgroup, using Altiris Deployment Solution is very simple.

Making use of Micrsoft's commands to create a script that will do this for you.

Here's how:

  1. Create a new "Run Script Job" in your DS console.
  2. Run this script:
    net user 'account' 'password'
    
    

    (do not use the inverted commas, but replace the content inside with the account and password that you need)

  3. Drag and drop this job on the selected computers of your choice in DS console.
  4. Password is now changed.

For more comments on how to do this see the knowledgebase article on Microsoft KB Site: Article ID: 251394

MikeCharles | 03 Jul 2008 | 0 comments

As I was working on our hardware independent imaging, it occurred to me that checking Active Directory for the existence of the computername that I was about to image would be pretty cool. We use WinPE 2.1 on DS 6.9, so my first thought was to pilfer someone else's vbscript (in I/T, plagiarism is the sincerest form of flattery) and modify it for my needs. The script worked well enough on my laptop, so off to a deployment task it went. And failed. I beat my head upon this problem for awhile, and called tech support. Apparently, ldap binds do not work with WinPE 2.1, so I couldn't query Active Directory with vbscript (Thanks anyway, Nate!). "How about dsquery?" I asked myself. It doesn't work from WinPE 2.1 either. What was I to do?

Batch file programming! I created a Run Script task, set to execute locally from the server when the agent is...

Nelo | 02 Jul 2008 | 11 comments

Create a bootable WinPE 2.1 DVD with a self-contained restoration image. This was addressed for Linux in a precious Juice Article. I have asked permission from the creator of that article and I modified it for WinPE 2.1

Altiris® Deployment Solution™ software provides a number of tools to remotely image computers. On occasion, you might encounter situations where you need to image a computer without network connectivity or you want the image and tools available locally.

This article outlines the process to create a bootable DVD using automation tools and a computer image. With these tools you can quickly and easily restore an image from a bootable DVD.

Prerequisites

  • Deployment Solution 6.9.
  • WinPe 2.1 automation. Instructions for installing this are in the Deployment Solution Reference Guide (...
Martin Charker | 01 Jul 2008 | 0 comments

If you’re planning to use ianatkin’s suggestion of “MS-DOS as a PXE Automation Option”, you use Emulex Fibre Cards, and you would you like to configure them remotely, this is the program you need, DosLpCfg from Emulex.

DosLpCfg is for use with MS-DOS, FreeDOS, IBM PC DOS and DR DOS operating systems.

You can use the utility to do the following:

  • View information on an Emulex HBA
  • Reset the HBA
  • Download firmware and boot code files
  • Select a boot device
  • Read and update World Wide Names (WWNs)
  • Enable BootBIOS
  • Update configuration regions
  • Set the HBA to use soft jumpers
  • Run diagnostic tests
  • Read and process script files

Get it here:...

Martin Charker | 30 Jun 2008 | 0 comments

Do you use Emulex Fibre Cards? Would you like to configure them in Winpe? Then the program you need is WinLpCfg from Emulex.

WinLpCfg is for use with 32-bit and 64-bit versions of the Microsoft WinPE operating system. (Although not the intended use, you can use WinLpCfg with Windows Server 2003)

You can use the utility to do the following:

  • View information on an Emulex HBA
  • Reset the HBA
  • Download firmware and boot code files
  • Select a boot device
  • Read and update World Wide Names (WWNs)
  • Enable BootBIOS
  • Update configuration regions
  • Set the HBA to use soft jumpers
  • Run diagnostic tests
  • Read and process script files

Get it here:...

cl3tUs | 30 Jun 2008 | 1 comment

Ever go looking for a device, but can't seem to find out what it is?

While searching for a device one day, I stumbled onto this website called PCIDatabase. I can type in the Vendor info or the Dev info and get an idea who makes it. Granted, this does not find it for me, but I can find out who makes it and it points me in the right direction, which is more than what I started with.

Let's begin.

First, we will take a look at the "PCI Device" in our Device Manager.

Double-click "PCI Device" or right-click...

scotthansenpaysoneast@gmail.com | 26 Jun 2008 | 0 comments

If you do an Unattended install of 2k8 or Vista and it does not finish as you expected it or if you just want to know what went on while it installed, look for these log files.

  1. C:\Windows\Panther\UnattendGC\setupact.log
  2. C:\Windows\Panther\UnattendGC\setuperr.log

These should give you an idea of what could have gone on during the install and failure thereof.

CondorMan | 26 Jun 2008 | 4 comments

There are a few ways to have a batch script wait for a number of seconds. The simplest and most widely available without any additional programs is to use the ping command.

The following is is an example... PING!

ECHO Waiting 5 seconds
PING 1.1.1.1 -n 1 -w 5000 > NUL

CondorMan | 25 Jun 2008 | 0 comments

OSQL is a flexible command-line utility that allows you to run SQL Queries, Commands, and Stored Procedures from the command-line or through a Batch script.

In order to run OSQL, you can either run it on your SQL Server or copy OSQL.EXE and osql.rll to a location that a client machine can run them from.

The syntax for OSQL is:

usage: osql       [-U login id]     [-P password]
 [-S server]      [-H hostname]     [-E trusted connection]
 [-d use database name] [-l login timeout]   [-t query timeout]
 [-h headers]      [-s colseparator]   [-w columnwidth]
 [-a packetsize]    [-e echo input]    [-I Enable Quoted Identifiers]
 [-L list servers]   [-c cmdend]      [-D ODBC DSN name]
 [-q "cmdline query"]  [-Q "cmdline query" and exit]
 [-n remove numbering] [-m errorlevel]
 [-r msgs to stderr]  [-V severitylevel]
 [-i inputfile...
CondorMan | 23 Jun 2008 | 1 comment

Have you ever deployed a Sysprep image to have it fail half-way through? Sometimes it can be a pain to figure out why. These log files can help tremendously:

  1. C:\Windows\setupapi.log logs driver installations.
  2. C:\Windows\setupact.log logs install actions.
  3. C:\Windows\setuperr.log logs install errors.
  4. C:\Windows\Debug\netsetup.log logs domain joins.