Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Endpoint Management Community Blog
Showing posts tagged with Tip/How to
Showing posts in English
Randall Newnham | 11 Nov 2009 | 0 comments

Ghost was not designed to work with solid state drives. The recommendations below may or may not work in a given environment, though they have been tested and verified on at least some machines. Please not that before trying this in a production environment, you should try this in a test environment so as to not risk data loss.

Officially, Ghost does not support solid state drives. I have verified that these steps worked on Dell Latitude E4200 machines:

1. Take the image with these command line switches:


2. Restore the image with these command line switches:


This  has been verified to work. This has only been tested with the same model of machine, so it is not expected that this would work to deploy to different models. I would expect that you could restore a solid state image to an IDE/SATA drive,but not the other way around. Assuming this is...

G Ross | 30 Oct 2009 | 0 comments

When working with Asset management there are occassions where there is incorrect or missing data within some of the asset summary fields such as the system manufacturer or model. This becomes especially problematic depending on the reports your asset management team uses to keep track of hardware in your environment.

It may be that your manufacturer is missing from some of your assets. In this case you can use the built in Dell hardware collections or create your own Dell collection to update the manufacturer to Dell for all your Dell workstations. Using the bsaic inventory you should be able to create collections for IBM, Lenovo, HP, etc to update the manufacturer information for all of your systems. In order to do this from the 6.5 console go to View > Configuration > Solution...

riva11 | 30 Oct 2009 | 1 comment

DevManView 1.0 is a portable software program made by Nirsoft. It allows to manage devices on your local computer and also of another computer on your network.  This tool is a good alternative to the standard Microsoft Device Manager,  it is really a small program , only 37 Kb , and should be considered in case you have problems during the boot and you want to identify and disable the problematic device.

Main features:

  • Local and remote device management
  • Flat Table view
  • Easy device management, including Enable/Disable and Uninstall features
  • Export the Device list in different format files (TXT, CSV, HTML, XML)
  • Small portable tool, only 37 kb


System Requirements: Supported all Windows Operative Systems , starting from Windows...

KSchroeder | 28 Oct 2009 | 0 comments

I came across a handy link to a tool from Microsoft for creating bootable USB sticks from your Windows 7 (or Vista or Linux) bootable DVD ISO file.  IanAtkin posted another method here, but this is an official MS tool.  I haven't done much testing with it myself (I only have a 2GB USB stick handy currently) but it seems you can use it to "burn" a bootable DVD ISO of any sort to USB quickly and easily...and it will apparently burn DVD ISOs as well to a DVD burner.  From my brief testing, it only seems to work with DVD ISOs, but not CD ISOs.

You can download it from the Microsoft Store.

Terry Cutler | 27 Oct 2009 | 0 comments

Earlier this year, Lenovo made a small change on their T400 and related platforms.   The Ctrl-P option disappeared when attempting to access the MEBx (Management Engine BIOS Extension screens for Intel Active Management Technology).   If you browse through the Lenovo BIOS update posting at, there is a brief mention of this change.

The main reason was to improve boot times.   The difference is a few seconds.   All of the Intel AMT functionality is still present.

To access the MEBx screen, press F12 during the POST process to access the Boot Menu. 


The option "Enter ME Configuration Screens" will access the MEBx.

The option "Initiate a...

B_Raj | 27 Oct 2009 | 1 comment

I’m here with 10 Questions & Answers to describe some of the basic things we need to take care while we approach to repackage an application.

 1.How do you Customize the vendor MSI?

 Vendor MSI’s should not be re-packaged or edited. Create a transform file to customize the vendor MSI. 

  • Some vendors supply utilities to customize their MSI behavior. Where this is the case, such utilities should be first considered as the appropriate method of customizing the MSI.  For example, use Microsoft’s Custom Installation Wizard  to customize the Office XP suite.  

2.When will you create a new MSI wrapper/ Wrapper Script?

This technique can be used in scenarios in which the installation program is not in MSI format and a setup capture is not appropriate.

Example:  Service packs and security patches

3.How do you treat INI files while repackage an...

B_Raj | 27 Oct 2009 | 0 comments

The table below lists some of  the language IDs for which the Windows Installer has

localized resource strings.


LangID           (Hex)              ACP                (Abbr)           Language (country)

 1025                 401                1256                ARA               Arabic (Saudi Arabia)

 1027            ...

B_Raj | 27 Oct 2009 | 3 comments


My intention by publishing this post is to help the newbies to understand the basics about packaging and repackaging technologies.And ofcurse for those who prepare for interviews !! :-)

 1.What is Application Packaging?

Simply Application packaging means,the process of Creation of an Installation Program for a Software. Or we can say it as creation of a setup file. Setup.exe is an installation file, a program that puts all of the files and registry keys in the right places so that everything works correctly.

  2.What is Application Repackaging?

The process of creating a customized installation using an already packaged installation is termed as Re-packaging.

The setup routine can sometimes be very complex and open to user error especially when thousands of repeat installations are required in a corporate environment. In such environments reliability and repeatability are crucial.


B_Raj | 26 Oct 2009 | 0 comments

While we deal with large windows installer packages, time required to install the package is one of the key factor in measuring the efficiency\quality of the package.

I’m briefing  here about some of the techniques that can be used to reduce the installation time of a MSI package.


The MSIFASTINSTALL property can be used to reduce the time required to install a large Windows Installer package. The property can be set on the command line or in the Property table to configure operations that the user or developer determines are non-essential for the installation.

How MSIFASTINSTALL Property will help to reduce the time?

1. This property helps to skip creating system restore point action in MSI install sequence.

2. This property helps to skip calculating the space requirements action in MSI install sequence. (Filecost)

Thus,if the developer is sure...

Randall Newnham | 26 Oct 2009 | 0 comments

There have been network latency issues observed on slower networks with Ghost. These issues can be resolved when booting to a Windows PE boot disk by exiting Ghost, and performing the Release and Renew commands for IPCONFIG, or by editing the START.BAT file at the end of the Ghost Boot Wizard by adding these commands. In the Ghost Console, it is not very clear how to do this. These steps will clarify that:

When Ghost executes a task that requires booting to Windows PE, it executes a file called START.BAT. This file automates the launch of the Ghost client executable, ngctw32.exe. Though not recommended, it is possible to add custom commands to this batch file. Please note that this batch file affects all  tasks that run in a specific build of Windows PE. By default, Ghost has two builds of Windows PE, winpe and winpe-512. It is recommended that you make a copy on the Windows PE build and that you edit the START.BAT associated with only your copy.