Summary
This Knowledge Base article will explain why the existing catalog items' deployment is not showing after the System Center Configuration Manager is migrated from SCCM 2007/2012 to the current System Center Configuration Manager.Synopsis
Existing catalog items,deployments, and requests are no longer visible under the Deployment tab --> SCCM2012 Tab After an In-Place Upgrade to System Center Configuration Manager (Current Branch).Discussion
If you are performing an in-place upgrade of your deployment technology from System Center 2012 Configuration Manager to System Center Configuration Manager (Current Branch), you will also need to run an SQL script to upgrade your App Portal database. This script will upgrade the existing catalog items, deployments, and requests in your App Portal database.To upgrade your App Portal database after an in-place upgrade to System Center Configuration Manager (Current Branch):
1. Perform the in-place upgrade of your deployment technology from System Center 2012 Configuration Manager to System Center Configuration Manager (Current Branch).
2. If you have not yet installed App Portal 2015 R2, run the App Portal 2015 R2 installer.
3. On your App Portal server, run the App Portal 2015 R2 SP4 Upgrader: AppPortalUpgrade_2015_R2_ServicePack_4.exe.
4. In App Portal, open the SCCM 2012 tab of the Site Management > Settings > Deployment view, remove the site server and database settings, and click Save.
5. Open the ConfigMgr tab and enter the same site server and database settings that you just deleted.
6. Click Test to test the connection, and then click Save.
7. On the App Portal database server, run the App Portal 2015 R2 SP4 Database Upgrade SQL Script onthe App Portal database
Additional Information
Please run the SQL statement in the attached App Portal 2015 R2 SP4 Release Note -- page 15.Please back up your current product database before run the script in case for roll back purpose.
