Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Endpoint Management Community Blog
Showing posts tagged with Basics
Showing posts in English
cnpalmer75 | 21 Sep 2007 | 0 comments

Here is a pretty decent site that has some good submissions that the user community here might benefit from. It is updated, fairly regularly... I suppose, but hey, it's still a resource to add to your tool bag or tool belt, depending on how you swing your hammer.

Here's the linky...
http://www.myitforum.com/articles/5/section.asp

WiseUser | 19 Sep 2007 | 4 comments

Windows Installer accomplishes rollback by creating a rollback script. A rollback script is a file that contains a linear sequence of operations to perform, such as file and registry updates, configuration information updates, user interface notifications, and state information for other operations.

Each operation recorded in the rollback script is a direct response to an operation in the installation script. Rollback scripts are stored in binary format.

This improves efficiency, avoids the need for parsing the file, and discourages manual editing of the file.

Rollback script files (.RBS and .RBF) are backups of existing files. Files with an .RBS file extension are rollback script files, and files with an .RBF file extension are backups of existing files. Both are stored in hidden folders called Config.msi.

The Config....

Andrew Souter | 19 Sep 2007 | 6 comments

List of Altiris Products Supported by Microsoft SQL Server 2005 and Windows 2003 SP2 (as of September 4th 2007).

Supported by SQL Server 2005 SP1 and SP2

NS 6.0 SP3 with Rollup #5
Application Control 6 SP1
Application Management 6.1 SP1
Application Metering 6.1 SP2
Asset Management 6.5
Audit Integration Component 6.2
Carbon Copy 6.2
CMDB Solution 6.5
Connector Solution 6.5
Console 6.5
Deployment Solution 6.8 SP2
Deployment Soln for Dell Servers 3.0
Inventory (Windows) 6.1 SP2
IT Analytics Solution
Monitor Solution 6 SP5
Patch for Dell Linux Servers
Patch Management for Windows 6.2
PC Transplant 6.8 SP1
Recovery Solution 6.2 SP2
Software Delivery for Windows 6.1 SP3
Software Virtualization 2.1
Wise Integration Component 6.1 SP3

Supported by SQL Server 2005 SP1 Only

Active Directory Connector
AuditExpress 1.3
Barcode...

WiseUser | 13 Sep 2007 | 1 comment

Public properties are differentiated from private properties by being listed in all capital letters. Public properties may be set on the command line (or in a transform file.)

Below are a list of standard public properties you may set. Keep in mind that vendors may also provide additional public properties specific to their applications.

TARGETDIR
Used as the location to copy the Installer installation package during an administrative installation.

ALLUSERS
Determines where configuration information will be stored.

ARPCOMMENTS
Provides Comments for the Add/Remove Control Panel.

ARPCONTACT
Provides Contact for the Add/Remove Control Panel.

ARPNOREPAIR
Disables the Repair button in the Programs...

R-Vijay | 12 Sep 2007 | 29 comments

Existing MSI packages should be deployed as they are. If customization is necessary, a Transform (MST) file should be used to introduce that customization. If you repackage an application and find that it references the MSI.DLL file, it is better not to repackage the application. Microsoft Office 2000 and XP are good examples. These applications are hard coded to use the Windows Installer service, and may make calls back to certain locations within the original MSI package.

Applications containing system files managed by the Windows File Protection features of Windows 2000 and later are also to be avoided, such as Internet Explorer, Windows Service Packs and certain hot fixes. For these, a provided MSI or command line installation is your best bet.

Repackaging certain types of applications is not recommended. These include:

    ...
R-Vijay | 12 Sep 2007 | 5 comments

Here are some rules I picked up through my time spent packaging software.

I live by them. Your mileage may vary.

  • Don't exclude any file from Setup capture Inclusion List.
  • Keep the default directory immediate to the Program Files.
  • In Merge module dialogue, uncheck all the merge modules and proceed.
    Adding Merge module should be done to a particular feature, but modifying or deleting have to done keeping all features into constraint.
    WFP Files will never be replaced.
  • When assigning key Path, avoid keeping it as ODBC, Its preferable to have it as a File Key path.
  • When a key path is missing for a component, it turns to be a broken component.
  • It's preferable to use installation expert to delete the file.
  • Always create a "shared" folder in local directory, to have the...
WiseUser | 12 Sep 2007 | 4 comments

Windows® File Protection (WFP) prevents the replacement of essential system files installed as part of Windows. Applications should not overwrite these files because they are used by the system and other applications. Protecting these files prevents application and operating system failures.

Protected File List

WFP protects files with the following extensions that are installed by Windows: .dll, .exe, .ocx, and .sys. In addition, the TrueType fonts Micross.ttf, Tahoma.ttf, and Tahomabd.ttf are also protected.

At the end of the Windows installation, WFP runs a scan of all protected files to ensure they have not been modified by applications installed through unattended installation. WFP also copies verified versions of these system files to the cache directory. When an application attempts to replace a protected file, WFP...

WiseUser | 06 Sep 2007 | 0 comments

The UPGRADINGPRODUCTCODE property is set by Windows Installer when an upgrade removes an application. The installer sets this property when it runs the RemoveExistingProducts action.

This property is not set by removing an application using the Add or Remove Programs in Control Panel. An application determines whether it is being removed by an upgrade or the Add or Remove Programs by checking UPGRADINGPRODUCTCODE.

You can condition custom actions that are sequenced after InstallValidate to handle major upgrades by using the UPGRADINGPRODUCTCODE property:

  1. If you want a custom action to run during an uninstallation of the product, but not during the removal of the product by a major upgrade, use this condition.
    REMOVE="ALL" AND NOT UPGRADINGPRODUCTCODE
    
    
  2. If you want a custom action to run only during a major upgrade, use this condition.
    UPGRADINGPRODUCTCODE
    
WiseUser | 06 Sep 2007 | 0 comments

Here's some useful information that explains how Windows Installer handles file replacement logic for versioned and unversioned files.

Hope it helps.

  1. In the case when the source and destination files are both versioned files, these rules are straightforward - if the key path file does not exist in the destination location or if it exists in the destination location and it is of a lower version, Windows Installer will install the component (and all of the files in it, including the key path). If the key path file exists in the destination location and it is of an equal or higher version, Windows Installer will not install the component but instead only reference counts the component. It becomes trickier when only one of the files is versioned or neither of them are.
  2. In the case when only one file is versioned, Windows Installer will install the component (and all of the files in it, including the key path file) if the...
jorm76 | 06 Sep 2007 | 6 comments

This is a command line that allow you to create a Helpdesk (HD) incident from a remote location. It uses the Web service that's packaged with the Helpdesk to do the heavy lifting. What's cool about this solution is you can submit an incident without even launching the Helpdesk console on your computer.

This is a command line, so use Internet Explorer or another application/program installed on your computer to run it.

The Web service can either take command line parameters (type "CreateWorkitem or Edit Workitem" to see them) or by using specific commands required for a 3rd party application.

The next line contains the parameters to send a command to the Altiris HD Web service. To create one new incident from IE you use this syntax:

http://MYSERVERHD/AeXHD/WebService.asmx/ProcessWorkItem?workitem_title=This+computer+is+break+fix+are+lost+data&workitem_category_tree_value= Break-fix%5cComputer&workitem_comment=Is+urgency+repair+and+...