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
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.
CondorMan | 20 Jun 2008 | 1 comment

I just discovered a nifty utility in the eXpress share called wndctl.exe. You can use it to lock the keyboard and mouse prior to any install/script and unlock it later. It can also activate, minimize, maximize, restore, hide, show, flash, close, disable, enable, tile, cascade, center, move, and resize window(s).

wndctl.exe can be found in any of the following places (in x86 and x64 versions):

  • Bootwiz\platforms\Winpe\x86\Optional\Boot
  • Bootwiz\platforms\Winpe\x64\Optional\Boot
  • Bootwiz\platforms\Winpe2\x86\Optional\Boot
  • Bootwiz\platforms\Winpe2\x64\Optional\Boot

The syntax for wndctl.exe is:

wndctl <command> [<"window title text">] [<n>]

<command> is the command to perform, and is one of the following:

-activate Make the...
CondorMan | 20 Jun 2008 | 0 comments

I just discovered that you can customize WinPE using the prestart and startup folders.

Here are some things to keep in mind when using the folders:

  1. All batch files you add to the prestart folder are run just before the network loads.
  2. All batch files you add to the startup folder are run just after the network loads.
  3. The batch files are run in alphabetical order.
  4. If your batch file launches another batch file, be sure to use the call command, or it will not return to the WinPE startup batch.
  5. If your batch file launches a program that will stay running be sure to use the start command, or it will hang and the WinPE boot will not continue.
marcoads | 20 Jun 2008 | 2 comments

Do you have unnecessary machines that are not in use, but are still present in the MSDE database in your Deployment Server? Is there a way to clean them out?

This is a script that will allow the user to clean all old machines manually from the MSDE database. Go to Deployment Server 6.5 build > Tools > Options, then check the box to clean out old computers by date range.

There is a SQL script you can run in Query Analyzer that will clean out computers that have not reported inventory in 35 days. To use this script just open SQL Query Analyzer from the SQL Administrations tools. Select the eXpress Database then copy the following code into the Query Analyzer window and click run.

DELETE from computer
WHERE datediff(dd,last_inventory,getdate())>35

Here is a sample Deployment Server job that can be scheduled in...

CondorMan | 20 Jun 2008 | 8 comments

A useful feature that allows you to use any data in your Deployment Server database in a script task is Custom Tokens. The syntax for a custom token is %#*"Your SQL Query Here"%. Here are some custom tokens that might come in handy.

%#*"SELECT GETDATE()"%

will return the current date and time.

%#*"SELECT @@servername"%

will return the name of the SQL Server.

%#*"SELECT g.name FROM computer c, computer_group g WHERE c.group_id = g.group_id AND c.computer_id = %ID%"%

will return the name of the group that this computer is a member of.

Martin Charker | 20 Jun 2008 | 0 comments

Here's the scenario: you have an HP server and you need to rebuild it. To do this you need to pxe boot it, but its off site and you have no remote view when the OS is not up :-( Well I had to do this and not just 1 server... double :-( Luckily I came across a tool in the HP SmartStart Scripting Toolkit, called setbootorder.exe.

It lets me change the boot order from Windows (or WinPE) to any order I need. So I set it to Network first and at the end of the deployment I set it back to Hard Disk (If only it worked on IBM servers I'd be a happy man).

You just run "setbootorder pxe hd cdrom usb floppy" in any order you need and that's it, job done!

The Toolkit has a number of other tools in it, but this is the only one I have needed to use so far. Hope it helps someone out!

The Toolkit can be found at:...