How to distribute old SCCM 2007 packages in 2012 environment?

[Ente]

I'm trying to wrap my head around the new concept of applications vs packages in 2012, but so far I think I'm correct in saying that only applications will appear under the Software Center.

 

I have a large number of older packages migrated from our 2007 environment, but none of them appear under Software Center and nothing works under the old "Get Programs" link within Control Panel.

 

I've distributed them to my new DP and copied all package source files.

 

I'm using a PKI and successfully pushing the new Client to my old 2007 devices.

 

What am I missing?

[Peter33]

Did you create boundary groups for site assignment and Content Location? Did you also migrate the collections and deplyoments(advertisments)?

[Ente]

I created Boundaries and a Boundary Group, but I'm not sure what you mean by "for site assignment and content location". My Boundary Group points to my DP as the Site system server, do I need to add my SQL server as well?

 

I migrated all Collections and Advertisements. I created a new Application and Package with the same source and nothing is showing up in either the Software Center or Application Catalog.

[Peter33]

No, you don't Need to add the SQL Server. If you only run a single Primary Server, as it seems, one boundary Group is doing well enough.

Check your Client logs (clientlocation.log ,locationservices.log , execmgr.log, smscliui.log). Alos check if the Client components are installed and enabled (Software Distribution Agent).

[Ente]

I'm seeing a few errors.

 

LocationServices.log:

<![LOG[WSUS Path='http://SERVER:8530', Server='SERVER', Version='13']LOG]!><time="12:39:45.394+300" date="07-29-2013" component="LocationServices" context="" type="1" thread="7424" file="lsutils.cpp:2963">
<![LOG[Calling back with locations for WSUS request {300286BA-0296-431B-9C57-B091788D14FA}]LOG]!><time="12:39:45.394+300" date="07-29-2013" component="LocationServices" context="" type="1" thread="7424" file="replylocationsendpoint.cpp:282">
<![LOG[Executing Task LSSiteRoleCycleTask]LOG]!><time="13:07:42.512+300" date="07-29-2013" component="LocationServices" context="" type="1" thread="4616" file="scheduledcleanupendpoint.cpp:116">
<![LOG[1 assigned MP errors in the last 10 minutes, threshold is 5.]LOG]!><time="13:07:42.524+300" date="07-29-2013" component="LocationServices" context="" type="2" thread="4616" file="lsutils.cpp:3160">
<![LOG[Current AD site of machine is RJAC]LOG]!><time="13:09:36.841+300" date="07-29-2013" component="LocationServices" context="" type="1" thread="4616" file="lsad.cpp:746">
<![LOG[Current AD site of machine is RJAC]LOG]!><time="13:14:36.319+300" date="07-29-2013" component="LocationServices" context="" type="1" thread="6696" file="lsad.cpp:746">
 

smscliui.log:

<![LOG[WARNING - Client is currently unassigned or an error occurred retrieving the assigned site. GetAssignedSite() returned : 0X0]LOG]!><time="11:57:37.731+300" date="05-21-2013" component="smscliui" context="" type="2" thread="5812" file="clicfgdlg.cpp:1410">
<![LOG[Currently assigned FQDN: ]LOG]!><time="11:57:39.606+300" date="05-21-2013" component="smscliui" context="" type="1" thread="5812" file="clicfgdlg.cpp:4279">
<![LOG[Software Distribution site settings (CCM_SoftwareDistributionClientConfig) policy does not yet exist on the client.
If the client is not yet registered, this is expected behavior.]LOG]!><time="08:22:56.839+300" date="05-29-2013" component="smscliui" context="" type="2" thread="11332" file="softdistpolicy.cpp:1398">

I've been thinking, do I need to remove the existing boundaries on my old SCCM 2007 server? Could my client devices be confused as to where to grab software?

 

Software Distribution Agent is Enabled.

[Peter33]

As long as you do not activate the auto assignement for Clients you can run both environments even in the same boundaries. Use the SMSSITECODE property for Client push.

I assume your site server is publishing correctly to the AD?

[Ente]

As long as you do not activate the auto assignement for Clients you can run both environments even in the same boundaries. Use the SMSSITECODE property for Client push.

I assume your site server is publishing correctly to the AD?

 

I believe it is as I see the new 2012 server's FQDN under System Management along with the old 2007 server.

 

Yes I'm specifying the SMSSITECODE with the Client Push from the 2012 server.

 

I noticed all my packages have a compliance of 0.0% as well.

[Peter33]

Is your Management Point installed correctly? Check the mpsetup.log and mpmsi.log on your Server.

 

You should also have an entry for the Management Point in the System Management Container, not only a single one for the site. Do you?

[Ente]

Those logs look fairly clean. I see some entries from June 12th, but nothing after that.

<06/12/13 11:10:16> Installing D:\Program Files\Microsoft Configuration Manager\bin\x64\mp.msi CCMINSTALLDIR="D:\Program Files\SMS_CCM" CCMSERVERDATAROOT="D:\Program Files\Microsoft Configuration Manager" USESMSPORTS=TRUE SMSPORTS=80 USESMSSSLPORTS=TRUE SMSSSLPORTS=443 USESMSSSL=TRUE SMSSSLSTATE=63 CCMENABLELOGGING=TRUE CCMLOGLEVEL=1 CCMLOGMAXSIZE=1000000 CCMLOGMAXHISTORY=1
<06/12/13 11:10:38> mp.msi exited with return code: 1603
<06/12/13 11:10:38> Backing up D:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log to D:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log.LastError
<06/12/13 11:10:38> Fatal MSI Error - mp.msi could not be installed.
<06/12/13 11:10:38> ~RoleSetup().

MSI (s) (14:AC) [11:21:12:769]: Product: ConfigMgr Management Point -- Installation operation completed successfully.

MSI (s) (14:AC) [11:21:12:769]: Windows Installer installed the product. Product Name: ConfigMgr Management Point. Product Version: 5.00.7804.1000. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 0.

Under System Management I have an entry for the Management Point: SMS-MP-CODE-SERVERFQDN

 

I think part of the problem is that now my clients no longer list the PKI within the SCCM client. They used to display "PKI" under Client Certificate in the General tab, but now they display "None". Connection type is also "Unknown".

[Peter33]

Nope, That's not clean. Check the mpmsi.log and mpmsi.log.lasterror.

Anyways, i would just remove and reinstall the Management Point role to see if that will fix the Problem.

<06/12/13 11:10:16> Installing D:\Program Files\Microsoft Configuration Manager\bin\x64\mp.msi CCMINSTALLDIR="D:\Program Files\SMS_CCM" CCMSERVERDATAROOT="D:\Program Files\Microsoft Configuration Manager" USESMSPORTS=TRUE SMSPORTS=80 USESMSSSLPORTS=TRUE SMSSSLPORTS=443 USESMSSSL=TRUE SMSSSLSTATE=63 CCMENABLELOGGING=TRUE CCMLOGLEVEL=1 CCMLOGMAXSIZE=1000000 CCMLOGMAXHISTORY=1
<06/12/13 11:10:38> mp.msi exited with return code: 1603
<06/12/13 11:10:38> Backing up D:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log to D:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log.LastError
<06/12/13 11:10:38> Fatal MSI Error - mp.msi could not be installed.
<06/12/13 11:10:38> ~RoleSetup().