To automatically migrate all your low risk programs at onceIf you are migrating SMS 1.2 packages and programs to SMS 2.0, you can take advantage of the PGC Migration Wizard to analyze each program, advise you about how to migrate each one, and automatically migrate low risk programs.
Automatic migration means that the wizard analyzes the programs and migrates them to SMS 2.0 format. In some cases, the run command line and the configuration command line may be altered in the process to allow the creation of a shortcut or to remove a wrapper program that is no longer needed, but otherwise, they remain the same.
Manual migration means that you use the pages of the wizard to modify command lines, to enter new command lines, or to choose from existing installation scripts to migrate the program.
An SMS 2.0 single-phase setup is an SMS 1.2 package that is migrated to an SMS 2.0 package with a single client-side program (the run command line).
An SMS 2.0 double-phase setup is an SMS 2.0 package that contains a configuration command line and a run command line.
Note that the wizard makes no attempt to migrate SMS 1.2 program groups or their associated user groups. In order to deploy migrated programs to your clients, you must advertise them as described in “Deploying Shared Applications” later in this chapter.
The exact method you should use for migrating existing SMS 1.2 PGC programs depends on the wizard’s assessment of the risks. Depending on information the wizard can determine from the application’s source files, the wizard assesses the application as one of the following:
You can use the wizard to analyze high risk programs. Then, examine the files and test the program outside the wizard using the SMS Installer or other tools. For example, you can use SMS Installer to repackage the programs, or you can use Installer to create a script that isolates the changes that are made to the client during an SMS 1.2 installation, so you can make the same changes to your SMS 2.0 client installation script. Finally, you can use the wizard to manually migrate the program.
You should inspect each program that the wizard classifies as high risk and determine whether the risks actually apply to your situation. For example, the wizard regards programs that can run on both Windows and DOS platforms as high risk, because the wizard has no automatic solution for DOS clients. But if you have no DOS clients, then you can regard the program as low risk and migrate it anyway.
The highest risk program has a configuration command line that is actually one of the high risk SMS-provided wrapper programs:
These wrapper programs do not work on an SMS 2.0 client because they require the presence of the PGC feature.
If a program has a configuration command line that is actually the SMS-provided Smsacm32.exe wrapper program, it is a low risk program as long as it is in the following format:
Smsacm32.exe <regkey> <stf-file>.stf "<installcmd>" "<uninstallcmd>"If the configuration command line is in this format, the wizard converts this command line to an appropriate form and inserts a new generic wrapper program that is based on the SMS Installer, so you can modify and fine-tune the configuration process.
When you choose to migrate a program, the wizard returns an analysis of the program and an assessment of the risk of migrating it. You can use this analysis to determine how you want to migrate the programs to SMS 2.0. The wizard also tracks the status of all the preserved programs.
The analysis consists of examining the configuration and run command lines and their associated scripts. If the wizard determines that these programs do not refer to known SMS 1.2-specific wrapper programs and they do not meet other criteria that the wizard considers high risk, the wizard marks the application low risk because the wizard can probably migrate it automatically. The analysis informs you of this. If there is a configuration command line that the wizard cannot handle automatically, the wizard informs you that there are risks. In this case, you may want to research the installation script functions. You can still migrate such applications within the wizard by using the manual migration wizard pages.
Some other conditions that are required by the SMS 1.2 programs can be detected by the wizard and are reported back to you. For example, if the application requires a specific drive letter, this information is reported back to you so you can use the same drive letter in your client installation script.
Because the methods of distributing software are different in SMS 1.2 and SMS 2.0, and because software applications have many different requirements when they are installed, the PGC Migration Wizard cannot always migrate applications smoothly from SMS 1.2 to SMS 2.0. Nor can the wizard guarantee a correct analysis of whether an automatic migration is possible.
In some cases, it is possible for the wizard to update the status of a program to Migrated that does not run correctly on clients. In these situations, you must repair the programs so that they do execute. If you have a program that was migrated, but the resulting application cannot be run successfully, you can:
So, you should not assume that a migration has completed successfully until you have fully tested the migrated application. You should first migrate the programs to a single server and fully test them before distributing them across your site. For more information, see “Testing Server-Based Applications” later in this chapter.
When you install this Resource Kit, the PGC Migration Wizard is automatically installed as part of the SMS Administrator console. You can invoke the PGC Migration Wizard from the SMS Administrator console by right-clicking any package under Packages in the SMS Administrator console. Point to All Tasks and then click PGC Migration Wizard.
The PGC Migration Wizard automates the process of migrating programs from SMS 1.2 to SMS 2.0. The wizard allows you to:
Before you begin migrating programs, make sure you have permission to the package source directory so the wizard can add programs. If you are not sure where the package source directory is located, right-click Properties on the package, select the Data Source tab, and note the location of the directory.
Also, when the wizard adds programs to the package source directory, it attempts to refresh the files on the distribution points. By default, no distribution points are enabled for the non-migrated packages. If you want the wizard to refresh the files, enable distribution points for each non-migrated program.
The following sections contain information and procedures for completing each of the PGC Migration Wizard functions.
You can use the PGC Migration Wizard to migrate all your low risk programs at once. When you start the PGC Migration Wizard, it determines whether there are any low risk programs that have not yet been migrated. If it finds any, the wizard displays them on the Automatic Migration page. You can then choose whether to have the wizard migrate all the low risk programs at once or to analyze them individually.
The Automatic Migration page appears only once each time you use the wizard, and only if the wizard finds that there are low risk programs you have not yet migrated.
To automatically migrate all your low risk programs at once
If you decide that you do not want the wizard to migrate all of the low risk programs, or you would like to generate a report or see analysis before you migrate, click Back and choose No, analyze and migrate these programs individually to display the Migration Status wizard page. For more information, see “Analyzing and Migrating Individual Programs” later in this chapter.
If you decide that you want the wizard to migrate the programs, you must choose whether to exit when all the programs have been migrated or to continue migrating. When you have chosen, click Next. The wizard migrates the programs.
If you choose to continue migrating, the wizard migrates all the low risk programs and then displays the Migration Status page so you can migrate an individual program.
The Migration Status page lists each PGC shared package and program along with its status.
The View menu allows you to choose which groups of programs you would like to see on this wizard page. The choices are:
The migration states allowed for the wizard are:
You can view the status of the programs, then choose from the following options:
In addition to having the wizard automatically migrate low risk programs, you can also analyze and migrate programs individually. You should migrate programs individually if the programs are low risk but you do not want to migrate all the programs at once, or if you have high risk programs and you need to perform additional work to migrate them.
After you have analyzed individual programs, you can have the wizard automatically migrate them for you, or you can use the manual migration sequence within the wizard, where you can create, select, or change the configuration and run command lines for the program yourself. If you prefer, after the analysis, you can mark a program as Won’t migrate and then research further before you return to the wizard to migrate it, or you can create a new client installation script to use as a configuration command line.
To analyze and migrate an individual program
The wizard displays the Migration Status page. This Migration Status page lists each PGC shared package and program along with its status.
The View menu allows you to choose which groups of programs you would like to see on this wizard page. The choices are:
The migration states allowed for the wizard are:
Programs that you have migrated and confirmed as working.
You can view the status of the programs, then choose from the following options:
The analysis of the program displays the following information:
You can read the analysis on the wizard page. This analysis is identical to the notes for the program if this program was included in a report you generated.
If you want to print the analysis or save it to a file, you can copy the content of the analysis and paste it into a file using the Cut/Paste function, or you can generate a report. If you do, the report will contain all of the information in the analysis of the programs you selected for the report. For more information, see “Generating Reports on Migration Status” later in this chapter.
After you read the analysis, choose from one of the following three options:
If the program has a configuration command line, the wizard displays the Configuration Program page. For more information, see “Manually Migrating Programs with Configuration Command Lines” later in this chapter.
If the program does not have a configuration command line, the wizard displays the Program Command Line page. For more information, see “Manually Migrating Programs with Run Command Lines” later in this chapter.
If the program you are migrating has a configuration command line, and you are migrating it manually rather than automatically, you must choose how to migrate the configuration command line:
Use the Configuration Program page to analyze the command line and select how to migrate it.
To migrate programs with Configuration Command Lines
The Analysis field returns the migration analysis for the configuration command line. On this page, choose from the following options:
Enter the appropriate values for Program Name and the Command Line. You can also enter a comment. The new program is added to the package you are migrating. This option is useful if you have created a new client installation script that is a configuration command line and placed it in the package.
The wizard assumes that the command line entered in this box will run successfully. Nothing is created in the package source directory by the wizard. The SMS 1.2 command line can be used if it is not one of the high risk wrappers mentioned in “Risks of Automatic Migration” earlier in this chapter. In fact, the wizard suggests the old configuration command line if the SMS 1.2 program uses a non-standard configuration command line.
When you click Next, the wizard transfers to the Program Command Line page. For more information, see “Manually Migrating Programs with Run Command Lines” later in this chapter.
You select the package and program to run before the run command line. This option is useful if you have created a general client preparation program in another package that configures a workstation correctly for the current program.
When you click Next, the wizard transfers to the Program Command Line page. For more information, see “Manually Migrating Programs with Run Command Lines” later in this chapter.
If you create a new program or select an existing program, the run command line is set to be dependent on the new program (the configuration command line), so it will run before the run command line.
When you have decided how to construct the configuration command line, the wizard displays the Program Command Line page. You then migrate the run command line in exactly the same way as if your program had no configuration command line.
If the program you are manually migrating does not have a configuration command line, or if you have finished migrating the configuration command line, you must choose how to migrate the run command line. Use the Program Command Line page to select how to migrate it.
To migrate the run command line
This shortcut is installed on the client. Double-clicking it causes the application on the distribution point to execute. If the same shortcut should be common to all clients, you can select Shortcut is common to all users.
This shortcut is actually created by the Setstart client installation script, which is available for you to edit if you want to fine-tune your application. By default, the wizard creates an appropriate Setstart-based command line for all the run command entries so that they point back to the server. When this Setstart-based program is advertised to clients and executed, it causes a configuration command to be run, if one is defined. Then, it creates a shortcut pointing back to the distribution point that it uses to run the application.
When you click Next, the wizard displays the Migration Status page. For more information, see “Analyzing and Migrating Individual Programs” earlier in this chapter.
You can use the PGC Migration Wizard to keep track of the status of programs you are migrating. The first time you start the wizard, all of the SMS 1.2 PGC programs are marked with a status of Not migrated. When you analyze or migrate programs, you can use the wizard to update the status to keep track of where each program is in the migration process. The wizard updates the status of programs as it migrates them.
If you have tried to migrate a program, but the resulting program does not run successfully, you can change the status of the program and migrate again using a different strategy:
To update the migration status of a program
The wizard displays the Migration Status page. This Migration Status page lists each PGC shared package and program along with its status.
The View menu allows you to choose which groups of programs you would like to see on this wizard page. The choices are:
The migration states allowed for the wizard are:
View the status of the programs and then choose from the following options:
The wizard page displays the program you selected with its current status. Select a new status for the program from the drop-down box, which only displays states that are valid. You can also type an optional comment for the program. When you click Next, the wizard displays the Update Status Summary page.
The Update Status Summary page returns the updated status of the shared program you selected. From this page, you can choose to exit the wizard or to migrate additional programs. For more information, see “Analyzing and Migrating Individual Programs” earlier in this chapter.
You can use the PGC Migration Wizard to generate reports on the migration status of programs. When you generate a report, you select one or more status characteristics to report. The report lists all of the SMS 1.2 PGC programs marked with that status and provides notes with the migration analysis of each program.
To generate a report on migration status
The wizard displays the Migration Status page.
The Migration Status page lists each PGC shared package and program along with its status.
The View menu allows you to choose which groups of programs you would like to see on this wizard page. The choices are:
The migration states allowed for the wizard are:
View the status of the programs and then choose from the following options:
Choose the states you want to report and then click Next. The wizard displays the Report page. The Report page displays the text of the report, including:
Choose from the following options for the report:
The Notes fields of the Shared Programs text box are given as numbers that correspond to the Notes fields at the bottom of the page. If you want to see the comments associated with the numbers, as well as the entire list of numbers associated with each program, print the report or save it to a file.
To see the comments while in the wizard, scroll down to Notes.
From this page, you can choose to exit the wizard or to migrate additional programs. For more information, see “Analyzing and Migrating Individual Programs” earlier in this chapter. If you want to return to the Report Contents page to generate another report, press Back.