Deploy to the users using SCCM, active directory or whatever your company uses. Answered 04/12/ by: olditguy. Second Degree Blue. Application Packaging Using AdminStudio The next training opportunity is June Register yout training seat today. Get trained with Application Packaging trainer. Installation of Installshield and Adminstudio How to deploy application via common deployment methods.

Author: Tonos Vunos
Country: Sao Tome and Principe
Language: English (Spanish)
Genre: Medical
Published (Last): 7 November 2013
Pages: 441
PDF File Size: 15.99 Mb
ePub File Size: 5.97 Mb
ISBN: 910-5-59621-892-1
Downloads: 29229
Price: Free* [*Free Regsitration Required]
Uploader: Mezit

Install the repackager package from k: If you adminstudoo the additional features discussed in the second half of this document, install the whole AdminStudio suite from physical media. Repackaging is a last-resort option. In ALL cases, we want to try using the vendor-supplied package and method for automated installation before resorting to repackaging. It is a messy procedure, but in some cases completely necessary.

Please exhaust ALL other options before resorting to repackaging. Login to Windows as an administrator and start the repackager application. Place any desired shortcuts to the desktop or start menu in the ‘all users’ profile so all users can get to them. Make any changes necessary to the configuration options in the application.

Make any necessary registry changes as well. This time select analyze system changes.

Application Deployment: Using AdminStudio Repackager

Be sure that you save the project 20113 the local hard drive C: If this message comes up, select “Yes”. The second snapshot will start now. The second snapshot will take a bit longer than the initial one.

The repackager application will automatically load with all of the information collected. Look at the files. Make sure that only the files that are supposed to be included are. Exclude all files that do not need to be packaged. If there are any registry entries that do not belong to your application, exclude them. You will probably always get something from McAfee Network Associates and something about printer drivers.

Exclude those as well. Only modify registry entries that you know 1 are not associated with the application being repackaged, 2 are associated and need to be added, or 3 need to be changed. Leave all others alone. The product registry key will be added by the script that installs the application, so do not insert it here.


This particular program adminatudio not install any registry items so all of them will be excluded. This will not always be the case. Now select Shortcuts from the left frame. You should only include the shortcuts or start menu items in the “all users” profile. Also, you will need to exclude any shortcuts to an uninstall file.

We do not want to make it convenient for any user who is not supposed to uninstall programs to do so. You may now check the package information and edit anything necessary, but packaying not configure any advanced options.

Keeping Applications at the Ready

Exclude 20013 INI files that do not need to be part of the package. Generally speaking, pavkaging this point the package is complete. If a package needs additional tweaking, including modifying icons, then read on and adjust the package as necessary.

To build an MSI file at this point, click the build icon on the toolbar. If you are not finished, skip this step and move on. Also change any relevant information in Add or Remove Programs.

Select Product Properties and chose the appropriate application type. This may include items in the Prefetch folder and the Administrator profile’s desktop.

Just highlight them and press delete. Be sure that all essential shortcuts have been discovered and that you delete all undesired shortcuts.

If necessary, you can add shortcuts here. In this case, no changes are necessary since we added the correct shortcuts between the discovery processes. To be sure that the users can start this application and that the shortcut is self-repairing, you must make sure that the ‘Advertised’ property is set to ‘Yes’. Also, check to make sure that the appropriate shortcuts are pointed to the appropriate file via the ‘Component’ property. Shortcuts that are used to start a program should be self-repairing shortcuts.

This is necessary when the application self-repair feature is expected to run before the first time the application runs.

This is also desirable for repairing broken applications when the user starts it. By default, Repackager may set these shortcuts to be a normal type, not the self-repairing type.

To make a shortcut the self-repairing type, in the “Shortcuts” view list, highlight the shortcut and change the “Advertised” value to “Yes”. Then change the “Component” value to be the component that contains the target of the shortcut. Remember to do this for ALL shortcuts that the user might use to start the application. Finally, browse the Environment Variables. If this contains anything to be added to or removed from the path, check to be sure that the project is appending or prepending this value, not replacing the entire path with this value.


Default value for imported projects is “replace” which will replace the entire path with the imported value. You have now completed all of the typical changes needed to produce an MSI file. Select “Compress all files” to produce an MSI that contains all of the necessary files to install the application.

Uncheck the “Create installation launcher Setup. We want a MSI not an executable. You will always get a warning as outlined above.

Application Packaging Using AdminStudio

That warning is InstallShield complaining about us putting a shortcut in the “all users” profile. It should be ignored. Close the Developer application. To test the application, login to Windows as an administrator, then copy the MSI that you created to another machine. By adminstuudio, the file is located in the C: To test the MSI for dependencies on network drives, unmap all network drives before installing the application.

Look for errors during installation. If you use a default Perl Script to install this application, further confirmation that everything was installed properly can be found by looking at the log file that was created during the MSI install. It can be found here: Now check all of the shortcuts the product is supposed to install and verify their existence and functionality. Run the application to make sure that it aminstudio properly and that all custom configurations are in place.

Appllcation documentation becomes dated, and this document is no exception. Please refer to our web site to obtain the latest documentation available. If you experience problems with the contents of these web pages, please visit the IT Solution Center and admonstudio a ticket with information relevant to the problem.

admin History