| | | Junior Member
       
Group: Forum Members Last Login: 11/30/2007 12:51:22 PM Posts: 21, Visits: 21 |
| | I have created several self-installing files on my computer. A folder has been created under c:\program files\sifxinst with many of the rollback pwr files in that folder. I understand how this works. However I also notice a file called Select DM Server.exe - one of my self-installing files located in this folder. In my startup folder I have a shortcut called Install Pending Files - this points to the file C:\Program Files\SIFXINST\SIFXINST.EXE program with an optional paramater /ApplyPending. Now recently I have noticed that when I try installing a new self-installing file (I will call it test.exe), that the Select DM Server self-installing file launches first and disrupts the installation of my test.exe program. I figure this has something to do with the install pending files shortcut and /applypending parameter. A simple solution would be to delete the Select DM Server.exe file from the C:\Program Files\SIFXINST folder altogether - I will do this. However a more basic question is how to "stop" the Install Pending Files shortcut from being created in the startup folder in the first place when I deploy a self installing file - I do not want this shortcut to be created at all. Is this possible? Thanks for any assistance on this query. John Falloon
|
| | | | 
Supreme Being
       
Group: Moderators Last Login: 2 days ago @ 2:43:01 PM Posts: 657, Visits: 797 |
| There are two reasons why a Self-Installing File (SIF) creates the "C:\Program Files\SIFXINST" folder: 1) The SIF has the "Add/Remove Programs" property set. The SIFXINST folder is where the rollback file gets created and SIFXINST.EXE is the program that performs the uninstall of the SIF. No "Install Pending Files" shortcut gets created with this property selected. 2) The SIF has the "Unattended/All Users" property set. When the SIF gets installed, it gets broken into two different portions; a user portion and a machine portion. The user portion contains all the shortcuts and user settings, while the machine portion contains the application files and machine settings. The machine portion of the Package is only installed once. The user portion is installed once for each user of the machine. The Package containing the user-specific settings gets created in the SIFXINST folder. The "Install Pending Files" shortcut gets created in the Start Menu Startup folder which launches at every login and ensures that user-specific settings get installed for each unique user who logs in to the computer. The shortcut runs at every login, however each Package only installs once per user. The "Select DM Server.EXE" is installing the user settings. This SIF must have the "Unattended/All Users" property defined. After deleting the "Install Pending Files" shortcut and removing this property, the SIF should no longer create the shortcut and run at each logon.
New Boundary Technologies Support support@newboundary.com |
| | | | Junior Member
       
Group: Forum Members Last Login: 11/30/2007 12:51:22 PM Posts: 21, Visits: 21 |
| | Thanks for the reply - that will help! |
| | | | Forum Newbie
       
Group: Forum Members Last Login: 11/19/2007 11:14:48 AM Posts: 1, Visits: 11 |
| | If you know the machine will only ever have one end user, is it OK to delete the 'Install Pending Files' shortcut or is that likely to cause a problem in the future? Thanks. |
| | | | 
Supreme Being
       
Group: Moderators Last Login: 2 days ago @ 2:43:01 PM Posts: 657, Visits: 797 |
| It's OK to delete the InstallPendingFiles shortcut if a machine only has one user. The InstallPendingFiles shortcut is left over from the days before the Prism Deploy existed. If you are currently deploying packages as tasks through the Prism Deploy Console, all users of a machine will get their user settings through a newer mechanism.
New Boundary Technologies Support support@newboundary.com |
| |
|
|