Video Screencast Help
Endpoint Management Community Blog
Showing posts tagged with Deployment Solution
Showing posts in English
CondorMan | 18 Jun 2008 | 0 comments

Have you ever wanted to start, stop, delete, create, or configure a service in your batch script? The "SC" command will allow you to do this and more.

Here are a few examples of how you can use this command:

Start a service sc start ServiceName
Stop a service sc stop ServiceName
Delete a service sc delete ServiceName
Create a service sc create ServiceName binPath="C:\Program Files\InstallDir\Service.exe" start=auto
Configure a service sc config ServiceName <options>

For more information about the settings you can make when creating and configuring services, go to a command prompt and type "sc create /?" and "sc config /?"

tbowman01 | 16 Jun 2008 | 2 comments

After a week of reading many posts about problems with the new Optiplex 755 and the new Intel 82566 DM-2 network cards I have finally found a solution. I have verified that using this driver that the network card works in both Windows Deployment Server and Altiris Deployment Server. I have not tested BartPE.

  1. Download the latest Intel NIC driver from for the Optiplex 755
  2. Extract the file, current version R162323.exe or newer, copy the file from c:\dell\drivers\R162323 to c:\ and rename the folder to 755-NIC-Driver
  3. Then use imagex to mount the boot.wim file
    Imagex /mountrw c:\boot.wim 1 c:\WinPE_x86\mount
  4. Add the drivers to the mounted boot image
    Peimg /inf=c:\755-NIC-Driver\*.inf c:\WinPE_x86\mount
  5. Unmount the boot image and commit changes
    Imagex /unmount /commit c:\WinPE_x86\mount

I am using WinPE 2.1 vista build boot.wim, therefore, the driver that I loaded was the Vista32 e1e6032.inf...

CondorMan | 09 Jun 2008 | 3 comments

Have you ever needed to modify the registry of an image, so you download the image to a computer, make the registry changes, and re-upload the image? Well, there is a much easier way!

The Symantec KB Article #2584 will give you step-by-step instructions about how to extract the registry of an image, modify it, and inject it back into the image.

This will save you alot of time and effort.

CondorMan | 06 Jun 2008 | 4 comments

Sometimes a Windows Installer will fail with an error 16xx. What does that mean?

You can find out by viewing Microsoft's list of Windows Installer Error Codes and their meanings here. You might want to add that link to your favorites if you manage a lot of .msi installs.

CondorMan | 05 Jun 2008 | 1 comment

If your workstations are using the NTFS file system, you can use COMPACT.EXE that is included with Windows to compress files with a certain extension. For example, to compress all of the .CHM files (which are rarely used), use the command: COMPACT /C /S:C:\ *.CHM

Here is a list of all the available parameters:

COMPACT [/C | /U] [/S[:dir]] [/A] [/I] [/F] [/Q] [filename [...]]

/C Compresses the specified files. Directories will be marked so that files added afterward will be compressed.
/U Uncompresses the specified files. Directories will be marked so that files added afterward will not be compressed.
/S Performs the specified operation on files in the given directory and all subdirectories. Default "dir" is the current directory...
CondorMan | 05 Jun 2008 | 2 comments

I just learned that you can enable MSI logging so that if your installer fails with an error you can see where the MSI failed.

To enable MSI loggging:

  1. Open Regedit.
  2. Go to HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer.
  3. Create a new Reg_SZ value named "Logging" with the value "voicewarmup".

While "voicewarmup" is easy to remember, it actually signifies all of the different options that you want to enable.

Here is the complete list of options:

v Verbose output
o Out-of-disk-space messages
i Status messages
c Initial UI parameters
e All error messages
w Non-fatal warnings
a Start up of actions
r Action-specific records...
Nelo | 03 Jun 2008 | 2 comments

There are times where PXE booting seems to take a long time especially with WinPE. After making some changes to the MTU (Maximum Transmission Unit) I was able to download WinPE 1.6 and 2.1 under 20 seconds.

Note: this depends in the speed of the network; all my tests are in a fast network.

Launch PXE Configuration tool and select the Multicast tab.

Change the Packet Size from 768 to 1456. Now this works OK for me and I have seen reports that others had success with this as well. If this does not work revert back to 768.

Finally, click save then...

BRING | 30 May 2008 | 1 comment

Usually two is better than one. However, in this situation, that is not the case.

When deploying a recently-captured PC Transplant personality, it was discovered that there were 2 Microsoft Excel icons in the Quick Launch Toolbar, as shown in the image below. This was a problem.

To make sure this did not happen again, the PC Transplant personality template was configured to NOT capture Quick Launch toolbar settings. Then, when the personality was deployed, the items in Quick Launch worked correctly.

This only seems to be a problem when migrating settings from Windows 2000 to Windows XP. Migrator, beware!

CondorMan | 23 May 2008 | 5 comments

If you are using WinPE 1.6, you will probably be interested to know that you can enable AClient Remote Control. This allows you to right-click any computer that is running a job in automation so that you can view the progress and troubleshoot any problems that may arise. If you notice that a computer has been stuck in automation for a long time, you can simply remote control the computer to fix the problem.

To enable AClient Remote Control in WinPE 1.6, you will need to edit your Boot Disk Configuration (From PXE or the Boot Disk Creator).

  1. On step 8, you will have the chance to edit the aclient.inp file.
  2. Replace ";PromptRemoteControl=Yes | No" with "PromptRemoteControl=No"
  3. Replace ";AllowRemoteControl=Yes | No" with "AllowRemoteControl=Yes"
  4. Save the changes to aclient.inp
  5. Regenerate your boot environment.

Now you can remote control your clients while they are in WinPE Automation!

ianatkin | 22 May 2008 | 1 comment

I put this on the Altiris Forums a little while ago, but thought it might be useful to place here too.

The link below describes half-a-dozen security vulnerabilities which appear to be only fixed by UPGRADING to DS 6.9 plus the hotfixes Here are the steps I took to remedy the problem.

I've tried to put together a mitigation list. The first draft is below. Can anyone comment on this? A mitigation list would help admins protect their servers now, and allow them to plan the upgrade to 6.9 at a more leisurely pace.

  1. For the SQL-injection vulnerability (exploitable), you have two mitigation options: Follow best practice and ensure that port 80 is heavily firewalled to restrict the Deployment Solution web console...