You have two options for this:

  • In-place upgrade – Shopping 5.0 running on Configuration Manager 2007 is upgraded and pointed to Configuration Manager 2012
  • Side-by-side migration – two parallel systems are configured one running Shopping 5.0 with Configuration Manager 2007 and the other running Shopping 5.5.200 with Configuration Manager 2012

In-place upgrade

You can use Shopping with either Configuration Manager 2012 or Configuration Manager 2007.  Shopping 5.5.200 has features related to Configuration Manager 2012 Application model. To utilize these new features you may want to consider upgrading to both  Shopping 5.5.200 and Configuration Manager 2012.  Shopping 5.5.200 supports conversion of Configuration Manager 2012 legacy packages to Application model applications.

We recommend the migration from Configuration Manager 2007 to Configuration Manager 2012 is only carried out during a Shopping installation or an upgrade. It is feasible to do this post-upgrade but it requires implementation by 1E Professional Services.

Shopping and the Configuration Manager 2007 environment prior to upgrading

The following describes the likely state of an existing production Shopping environment where the its Central and Receiver components are installed and the system is set up to use Configuration Manager 2007:

  • There may be completed orders in Shopping and corresponding adverts/folders created in Configuration Manager 2007
  • There may be pending orders in users' Shopping baskets
  • There may be orders that have been placed and are pending approval. Approved Applications may be either pending installation or the status may not yet have been determined by the Shopping Receiver
  • Administrators may have shopped for applications for other users. These applications may still be in a pending state
  • There may be OS Deployment tasks associated with a Task Sequence that may require processing by Shopping

Upgrading Shopping Central to  Shopping 5.5.200

  1. During the upgrade, point Shopping to the new Configuration Manager 2012 site.
  2. The upgrade will migrate all the existing applications and history to  Shopping 5.5.200
  3. After the upgrade, when new applications are created in the Shopping Admin Console, Shopping will behave as follows:
    1. Legacy packages, for both Configuration Manager 2007 and Configuration Manager 2012 are processed as normal, as long as Shopping Receiver 4.2 or later is installed.
    2. New Application model applications that are created will only be processed if Shopping Receiver 4.5 or later is installed on the Configuration Manager 2012 sites and Shopping Central is set to use the new Configuration Manager 2012 hierarchy.
    3. Depending on the version of the Shopping Receivers installed, the following restrictions apply:
      • Shopping Receiver 4.2 will process only legacy packages in Configuration Manager 2012
      • Shopping Receiver 4.5 will process legacy packages and Application model applications but will not be able to convert legacy packages to Application model in Shopping
      • Shopping Receiver 4.6 or later will process legacy packages and Application model applications and will convert legacy packages to Application model in Shopping
  4. When existing Shopping Receivers are upgraded Shopping 5.5.200, any Application Model applications that have been converted within Configuration Manager are identified and converted in Shopping and processed as expected.
After pointing Shopping Central to the new Configuration Manager 2012 site, the Site Node in the Shopping Admin Console will display both the new Configuration Manager 2012 site code and the previously used site code. The previous site code is kept to help identify machines that were registered with the old site code. When those machines log in to Shopping they will be moved across to the latest site code if they have been upgraded to the Configuration Manager 2012 client.

Migration to System Center 2012 Configuration Manager

The following sequence of events takes place when upgrading to  Shopping 5.5.200 and Configuration Manager 2012:

  1. According to the schedule set up in the migration job for Configuration Manager 2012, all the packages from the Configuration Manager 2007 site will be brought into the Configuration Manager 2012 environment. See Planning a Migration Job Strategy in System Center 2012 Configuration Manager for more information on Migrations Jobs.
  2. In Configuration Manager 2012, use the Microsoft Package Conversion Manager to convert Configuration Manager 2007 legacy packages to System Center 2012 Configuration Manager applications. See Configuration Manager Package Conversion Manager on the Microsoft TechNet site for further information.
  3. Where Shopping recognizes any new Application model packages in Configuration Manager 2012, it converts the legacy packages to Application model applications based on the administrator's choice.
  4. Once the application is converted, it will be available to all Configuration Manager 2012 site machines.

Things that Shopping will do following an upgrade

The following list shows the tasks that are performed following an upgrade:

    1. Retrieve all the user's order history information.
    2. Keep all the applications in the basket/pending approval intact.
    3. Process any application pending installation or waiting to be picked up by the Shopping Receiver.
    4. Create the collections and deployments in the Configuration Manager 2012 CAS for legacy packages that have been converted to Application model applications.
    5. Shopping will subsequently show only the Application model and legacy packages that are present in the Configuration Manager 2012 environment.
    6. Legacy packages are available on all Shopping machines and the new Configuration Manager 2012 Application model applications are only available on Configuration Manager 2012 clients.
    7. Convert all legacy packages, which have been converted to Application model applications in Configuration Manager 2012, to machine-centric Application model applications in Shopping once the Shopping Receivers have been upgraded to  Shopping 5.5.200.
During the migration from Configuration Manager 2007 to Configuration Manager 2012, there may be an interim period where the old Configuration Manager 2007 is running in parallel with the new Configuration Manager 2012. New applications and new machines created in Configuration Manager 2007 during this period can also be imported into Shopping 5.5.200. See importing applications and machines from Configuration Manager 2007 for further details.

Things that Shopping will not do following an upgrade

The following list shows the tasks that will not be performed following an upgrade:

  1. OSD objects are not migrated, these will need to be recreated in Configuration Manager 2012 and Shopping.
  2. Any orders for clients moving from Configuration Manager 2007 to Configuration Manager 2012, placed with the old site code where the clients are moved to Configuration Manager 2012 before the request has been processed will fail.
  3. Configuration Manager 2007 clients will not be able to see any Application model applications in Shopping.
  4. Once the Shopping Central service has been upgraded and migrated to Configuration Manager 2012, no new applications can be created for Configuration Manager 2007 without using the package import script (see importing applications and machines from Configuration Manager 2007). Avoid converting legacy packages to Application model applications if you want to make them available to both Configuration Manager 2007 and Configuration Manager 2012 clients.

Side-by-side migration

We describe the process performing a parallel migration from Shopping 4.7 running on a Configuration Manager 2007 environment to Shopping 5.5.200 running on a Configuration Manager 2012 environment. Although we refer to Shopping 4.7 throughout, the steps will also work for earlier supported Shopping versions with the following caveats:

There are two options for handling simultaneous Shopping and Configuration Manager migration, both of which rely on standing up two parallel implementations of Shopping and Configuration Manager. The two scenarios are largely the same with one main difference – how Shopping applications from the earlier version get migrated to Shopping 5.5.200. The sections below describe the scenarios in more detail.

Scenario 1

An existing Configuration Manager 2007 and Shopping 4.7 implementation exists in parallel with a new Configuration Manager 2012 and Shopping 5.5.200 implementation and clients managed by the old Configuration Manager 2007 system are progressively migrated to Configuration Manager 2012 when convenient. The new Shopping 5.5.200 must be configured with a different URL to enable the two Shopping systems to co-exist.

The goal is to enable a seamless transition for each client using the previous versions of Shopping and Configuration Manager to be switched to the new version of Shopping when the Configuration Manager client migration takes place. For this to happen, Shopping applications and associated Configuration Manager packages and programs must be present in the new versions of Shopping and Configuration Manager at the time the client switch over.

The Shopping 4.7 website should be configured to forward users browsing from Configuration Manager 2012 machines to the new  Shopping 5.5.200 website, conversely the  Shopping 5.5.200 website should be configured to forward users browsing from Configuration Manager 2007 machines to the Shopping 4.7 website (see site forwarding for more details).

The forwarding can be coded to include or exclude forwarding on a page-by-page basis. For example, approvers will still need to be able to access the earlier version of Shopping in order to approve requests from users on Configuration Manager 2007.

The general outline and order of the process is as follows:

  1. Packages and programs associated with Shopping 4.7 applications get migrated from Configuration Manager 2007 to Configuration Manager 2012.
  2. A bulk import of Configuration Manager applications is performed from  Shopping 5.5.200
  3. Configuration Manager clients are migrated from Configuration Manager 2007 to Configuration Manager 2012.
  4. Users browsing from Configuration Manager 2007 client machines use the Shopping 4.7 website.
  5. Using the same URL users browsing from Configuration Manager 2012 client machines get forwarded from the Shopping 4.7 website to the  Shopping 5.5.200 website.

Scenario 2

An existing Configuration Manager 2007 and Shopping 4.7 implementation exists in parallel with a new Configuration Manager 2012 implementation and clients managed by the old Configuration Manager 2007 system are progressively migrated to Configuration Manager 2012 when convenient. Again, the goal is to enable a seamless transition for each client using the previous versions of Shopping and Configuration Manager to be switched to the new version of Shopping when the Configuration Manager client migration takes place.

In this scenario, prior to installing the Shopping database component, a backup is taken of the earlier Shopping database. This is then restored onto the target SQL server where the new Shopping database is to be installed.

Prior to installing Shopping over the backup copy of the Shopping database, all the packages and programs associated with the previous Shopping applications must be migrated to the new Configuration Manager 2012 implementation. Once this is done, installing the Shopping Central components, including the Shopping database, will upgrade the existing database and bring all the previously used Shopping applications over to the new implementation of Shopping. As in scenario 1, the new Shopping system must be configured with a different URL to enable the two Shopping systems to co-exist.

After Shopping 5.5.200 has been installed, the Shopping 4.7 website should be configured to forward users browsing from Configuration Manager 2012 machines to the new  Shopping 5.5.200 website, conversely the  Shopping 5.5.200 website should be configured to forward users browsing from Configuration Manager 2007 machines to the Shopping 4.7 website (see site forwarding for more details).

The forwarding can be coded to include or exclude forwarding on a page-by-page basis. For example, approvers will still need to be able to access the earlier version of Shopping in order to approve requests from users on Configuration Manager 2007.

The general outline and order of the process is as follows:

  1. Prior to installing Shopping 5.5.200, packages and programs associated with the Shopping 4.7 applications you intend to use must be migrated from Configuration Manager 2007 to Configuration Manager 2012.
  2. Prior to installing  Shopping 5.5.200 on the Configuration Manager 2012 hierarchy, a backup of the existing Shopping 4.7 database is taken and then restored to the target SQL Server where the  Shopping 5.5.200 database is to be installed.
  3. Shopping 5.5.200 is installed and upgrade the restored Shopping 4.7 backup database.
  4. Shopping applications not intended for use should be removed from Shopping from the Shopping Admin console.
  5. Configuration Manager clients are migrated from Configuration Manager 2007 to Configuration Manager 2012.
  6. Users browsing from Configuration Manager 2007 client machines use the Shopping 4.7 website.
  7. Using the same URL, users browsing from Configuration Manager 2012 client machines are forwarded from the Shopping 4.7 website to the Shopping 5.5.200 website.

The ongoing migration process

While the migration is underway, there are two parallel Shopping and Configuration Manager systems running and servicing users and machines. It may happen that new applications get created in Configuration Manager 2007 – these can be imported to  Shopping 5.5.200 on a case-by-case basis using an SQL script

When migration has finished

When the migration process has concluded and all machines have been migrated from Configuration Manager 2007 to Configuration Manager 2012 clients, you can stand-down the Configuration Manager 2007 and Shopping 4.7 systems to free up resources. At the point the Shopping 4.7 Website is decommissioned, notify all users to change the URL they use to access Shopping to the one for the new  Shopping 5.5.200 website.

Site forwarding

When running parallel Shopping and Configuration Manager systems, you may want to implement site forwarding to prevent machines with the new Configuration Manager client from using the old Shopping site and machines with the old Configuration Manager client from using the new Shopping site. To do this, Shopping provides a mechanism in the index.cshtml on each site that can be used to forward users to the other site based on the Configuration Manager client version detected on the user's machine.

Custom Identity Page

Forwarding is achieved by using custom code on the Identity page to determine the Configuration Manager client version and forwards to the appropriate URL. This is the page that shows the logging in message when a user starts a session. It is hooked into all pages on the Shopping portal which ensures users are forwarded to the correct site irrespective of which page they first navigate to. 

The Identity page on each system is configured to forward to the other system, by editing the Views\Identity\index.cshtml file on each site and adding the configuration options shown in the following table:

Shopping 4.7 version of index.cshtml (Configuration Manager 2007 system)Shopping 5.x version of index.cshtml (Configuration Manager 2012 system)
other_SccmVersion = "5.1"other_SccmVersion = "4.0"
other_Portal = " http://shopsrv5:4880 "other_Portal = " http://shopsrv:4880 "

Importing applications and machines from Configuration Manager 2007

Machines and applications that exist prior to setting up the parallel systems are migrated from Configuration Manager 2007 to Configuration Manager 2012 during the initial migration process. We describe how to import applications and newly added machines that get added to Configuration Manager 2007 after Shopping 5.5.200 has been installed and configured to use Configuration Manager 2012.

Importing applications from Configuration Manager 2007

Configuration Manager 2007 applications are imported using the CreateApplicationScript_Configuration Manager_Migration_Support.sql script available from 1E support. The Configuration Manager Install_PackageIDInstall_Program_Name and Shopping Shopping_Application_Name parameters need to be set in the SQL script and only one application can be imported at a time. For an extended script that uses an Excel spreadsheet to enable the definition of multiple Shopping applications in a single operation, engage 1E Professional Services.

The Uninstall_PackageID and Uninstall_Program_Name can also be set in the script, but for this to work the Shopping_Application_ID must also be provided and unique from any existing Shopping application ID. Otherwise the Uninstall Package/Programs for the imported Shopping Application can simply be configured later in the Shopping Admin Console.

Using the example script, the imported application is created in Shopping with default settings which can be modified from the Shopping Admin Console.

Importing newly added machines from Configuration Manager 2007

Importing new machines from Configuration Manager 2007 does not require a script. It only requires two settings to be made in the Shopping Admin Console.

Sync Machines From Old Sccm: Set to True to enable machine synchronisation or False to disable the synchronisation.
SCCM Old Connection String: The SQL connection string for the Configuration Manager 2007 system.

The new imported machines from Configuration Manager 2007 must have the Shopping probe installed for Shopping to behave correctly.

Converting legacy applications to Application model applications

With the introduction of the Application model applications in Configuration Manager 2012, some method for automatically migrating the legacy ackage-program type applications to the new model is needed. Microsoft provides the Package Conversion Manager add-on tool for Configuration Manager 2012 to do this. Shopping applications based on the legacy application type also require a tool for migrating to the new model.

The new version of Shopping implements a regular check, initially run on starting the Shopping Admin Console, that informs the Shopping administrator of any legacy applications that it believes can be converted and giving them the option to do so.

Notifying the Administrator

When any suitable legacy application to Application model application conversions have been found, the new Convert Applications toolbar button in the Shopping Admin Console will change from  to  to prompt the administrator to start the conversion if required. Clicking the toolbar button opens the Convert applications to AppModel dialog, containing the identified applications

You can choose which applications to convert to machine-centric applications – Shopping does not allow the application to be converted to user-centric in case it is a branch application. To convert an application or multiple applications, tick the checkbox next to each application and click Convert. When the selected applications have been converted they are removed from the list. You can select all applications by checking Select All.

The dialog stays open until you click Close. The contents of the Shopping Admin Console will not be updated until this is done.