Jump to content


Leaderboard

Popular Content

Showing content with the highest reputation on 08/15/2017 in all areas

  1. Okay, resolution to this was to basically create a new Configuration Manager Package which I did do, but what Microsoft did was basically Re-Create the Client Package as if we built in the CAS. Since my Client package was created in the Stand Alone initially and was Expanded to the CAS it might have caused some issues??? I don't really totally agree with that, but oh well. Here are the Resolution they did: 1. Create a new ConfigMgr client package with any name and no programs (Source: \\server\SMS_Site\Client) 2. Create a new ConfigMgr client upgrade package with any name and no programs (Source: \\server\SMS_Site\Client Upgrade) The packages you created manually will be automatically deleted; no need to remove them later. New default packages will be automatically created. 3. run the following queries in the CAS site database – change the old and new package Ids accordingly: update ClientDeploymentSettings set FullPackageID = 'new Client PkgID' where FullPackageID ='old Client PkgID' update ClientDeploymentSettings set UpgradePackageID = 'new Upgrade PkgID' where UpgradePackageID ='old Upgrade PkgID' 4. Restart SMS_Executive and SMS_Site_Component Services 5. Delete the problematic package after distributing the new default client package to the desired DPs. This is how it looks now: (You will see WFT000D2 is the new Client Package)
    1 point
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.