Video Screencast Help
Symantec Appoints Michael A. Brown CEO. Learn more.
Endpoint Management Community Blog
Showing posts tagged with Configuring
Showing posts in English
dougj | 12 Nov 2008 | 1 comment

It is a misnomer to state that Custom Inventory supports certain data types. Within the aexcustinv.exe process, all data is treated as a string type. It is incumbent on the Notification Server dataloader to interpret the data types defined in the column attributes, create the table properly in the database, and validate the incoming data.

So, it is a clearer to say that when creating custom inventory XML scripts, certain data types can be processed by the NS dataloader.

Currently, the dataloader will process the following data types:

Custinv Data Type Converts to SQL Data Type
string nvarchar
int int
dateTime datetime
r4 real
float float
R-Vijay | 11 Nov 2008 | 0 comments

Here are some component guidelines which you need to follow in your application MSI. This will solve many issues like installation fix and automatic package repairs.

Always remember,

  • HKLM + HKCU in same component are not allowed
  • HKCR + HKCU in same component are not allowed
  • HKCU + Files in same component are not allowed. (Exception where the files are going to user profiles and key path is HKCU key path)

Also, when you design a custom component having HKCR or HKLM components, do check the Auto increment option; this helps the machine maintain a stable state.

kewidogg | 10 Nov 2008 | 0 comments

There are two steps that have been proven to work when receiving this error. They may not be the only solutions, and may not work for every machine and situation. Only perform these solutions if you are sure you are using the correct NIC driver, and have exhausted most other troubleshooting techniques.

Solution 1:

* If you are able to still boot into Windows on the client machine, do so. Click Start > Run. Type "cmd" and hit enter. Type "chkdsk /f" and hit enter.

Boot into a ghost boot disk.

When ghost loads, exit ghost so that you are at a DOS prompt (in WinPE, it is in the background behind the Ghost client. In PCDOS we need to exit the ghost client and it will exit to a DOS prompt).

In the DOS prompt, type "chkdsk c: /f" where c: is your drive that you are deploying your image to.

Let chkdsk run...

Nelo | 04 Nov 2008 | 0 comments

At times IT personal needs to capture and image of a computer that does not have a management client installed. Here is a manual way to accomplish this need and could be part of a batch file that could automate these steps.

  1. Windows Vista as an administrator execute the following BCDEdit commands:
    Bcdedit.exe -set {bootmgr} device BOOT
    Bcdedit.exe -set {default} device BOOT
    Bcdedit.exe -set {default} osdevice BOOT
  2. Restart the client machine to a pre OS environment. In my case I use WinPE 2.1.
  3. Capture the image using Rdeploy.exe or rdeployt.exe


The BCDEdit commands remove the machine uniqueness and the image could be used on a different machine but the same type.


I use the following batch file when executing the above steps:

LNew | 04 Nov 2008 | 0 comments

On occasion, you may need to compare or evaluate two values based on time as well as a calendar date, specifically any time under a 24-hour period (and therefore not equal to a full day). The process detailed below is an example of a timespan comparison that I created.

In this scenario, we will compare two dates that contain a time value - one representing the log in time of the user, and the other representing a due date/time. This can be utilized for various tasks or response actions.

For instance, you may need to respond to a particular request within 2 hours of the due date/time. The logic in this workflow can be applied in an auto start process that will send you a notification email warning you of the approaching deadline.

For this example, we will create a simple web form project that will provide a true/false value...

Randall Newnham | 03 Nov 2008 | 0 comments

I have seen a few cases with the new HP Elitebook 2530P. The default Windows PE builds do not have the latest Windows Vista driver for this and it must be updated. The driver necessary is the latest from Intel, version 13.1.2 or later. Here is a link:!

I posted this as a heads-up because these machines will not boot to either PC-DOS or MS-DOS with the latest DOS drivers for the network card (version 13.1.2 as well, as of this post. Versions of the NDIS2 after 13.1.2 may work, but the latest Vista driver is necessary...

Andrey Shipov | 03 Nov 2008 | 5 comments

We recently deployed IE7 to the Client PCs using Software Delivery Solution and I wanted to share few things regarding IE7 Deployment.

We used standard installation package from Microsoft, but you can use Internet Explorer 7 Administration Kit to modify installation package.

We created target deployment collection by checking if the IE7 record is present in Add/Remove Programs.

In effect we have two collections:

Collection One: Computers with IE7 installed,

with filter


MaggieH | 31 Oct 2008 | 0 comments

I stumbled upon this site and wanted to share it with you. It contains MSI tips and notes - very handy for beginners.

It covers and explains the below topics in a nice and simple manner.

  • Expanding properties at run time
  • Avoiding custom actions by using the -File tables
  • Fixing up a failed uninstall
  • File versions vs. ProductVersion
  • Some property names (silly)
  • Add or Remove Programs properties
  • Logging switches
  • Merge modules and properties
  • AppSearching
  • Launching a batch file in a custom action
  • "Sorry, but..."
  • Taking inventory of installed products, features...
MaggieH | 30 Oct 2008 | 0 comments

DebugView is an application that lets you monitor debug output on your local system, or any computer on the network that you can reach via TCP/IP.

To monitor MSI installation actions in real time:

  1. Create the Debug (reg_dword) registry entry under
    HKLM\SOFTWARE\Policies\Microsoft\Windows\Installer and set the data value to 00000002.
  2. Start DebugView, now Windows installer installations will write their Standard/Custom Actions and this will be displayed in DebugView.

You can download the latest version here:

piyushnasa | 30 Oct 2008 | 5 comments

Self Heal and Repair are two different concepts in Windows Installer which people many times consider to be the same thing, however there is difference in these two.

Self Heal is triggered by advertised shortcuts, or other advertising information in the package which eventually Repairs the application.

When the application is launched by advertised shortcut, it checks for all the key paths of the Current Feature, if any of the key paths is missing it will launch Repair.

Note that if there are multiple features then it will not check the missing key paths of the other features, but only the feature of which the advertised shortcut is launched.

Repair of an MSI can be triggered by

  1. Repair button in Add/Remove programs
  2. Giving the command line msiexec /f{other option} {MSI name...