Migrate User Story

Introduction

A user wants to import a complete MIM-Setup from a development configuration (called devConf from now on) to a target MIM-Setup in a production configuration (called prodConf now). The user has access to the MIM installer account from both MIM environments to collect all resources from the configurations. Before the user can start importing this configuration, the user wants to get all the resources from the devConf. To retrieve all these resources the user has to start an export first.

If the user wants to use any function of the IS4U.FimPortal module, the user has to execute an install from the IS4U-FIM-Powershell-Master folder.

./Install.ps1

This will ensure all the required modules (including Lithnet) and functions are installed and ready to be used.

Exporting

While in the devConf environment the user can collect all resources by calling:

Export-MIMSetup -ExportAll

After the command has been executed the user will receive a prompt asking in what folder the xml config files will be saved. If for example the user chooses path 'C:' a folder will be created: 'C:\MIMExportFiles'.

Or the user could declare a path in the export by 'Export-MIMSetup -ExportAll -PathForExport "C:"'.

When all resources are exported the folder will look something like this:

The user then has to bring the folder to the devConf environment.

Comparing

The user has arrived at the prodConf environment and unzips or pastes the folder in a chosen directory. The user wants to import the entire configuration so he chooses to do a compare on all resources.

Start-Migration -All

When calling Start-Migration without paths, two prompts will appear.

• The first prompt will ask the user where the configuration xml files are stored (that the user has brought from the devConf). The user chooses the folder where the files are copied.

• The second prompt will ask where the user wants to save the ConfigurationDelta.xml file. This is the file that will later be used to import the configurations.

Now the compares will begin and the user gets an overview of all the differences and new objects that are found between the devConf and prodConf. From the found differences a ConfigurationDelta.xml file is created in the folder that the user has chosen.

Importing

The configuration delta file has been created and has to be imported now. The user once again calls Start-Migration.

Start-Migration -ImportDelta

The ImportDelta flag will cause the FimDelta.exe program to start. In this program the user can choose which objects he wants to keep and import. The user chooses Object type as the 'Group by' filter as this gives a clear image of what will be imported.

The user wiches not to import certain resources and deselects them. The user then presses save and closes the application. This will create a ConfigurationDelta2.xml that will be used for the import. When the exe is closed the import will automatically begin and the user can see what is being imported. Some objects are imported again and give the message "up to date" (so are not imported), this is because some resources require references to devConf resources that may not be available in the prodConf.

The import is now done and the new resources are implemented in the prodConf environment. The user may have to look for certain references that are not imported. For example users that are linked to certain MPR's, usually different environments have different users and administrators with their own permissions.