Make a new Client package and point it to the same source location, problem 
solved.

From: [email protected] [mailto:[email protected]] On 
Behalf Of Russ Rimmerman
Sent: Thursday, August 07, 2014 1:41 PM
To: [email protected]
Subject: RE: [mssms] what's the deal with the configuration manager client 
package?

I wouldn’t remind hacking the db, but you can use powershell to refresh it.

$SiteCode = "<Site code>"
$PackageID = "<ConfigMgr Client Package ID>"
     $distpoints = Get-WmiObject -Namespace "root\SMS\Site_$($SiteCode)" -Query 
"Select * From SMS_DistributionPoint WHERE PackageID='$PackageID'"
        foreach ($dp in $distpoints)
        {
                $dp.RefreshNow = $true
                $dp.Put()
        }

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Todd Hemsell
Sent: Thursday, August 7, 2014 11:59 AM
To: [email protected]<mailto:[email protected]>
Subject: Re: [mssms] what's the deal with the configuration manager client 
package?

It is a built in package,
SCCM controls it. Have to hack the DB to refresh it

On Wed, Aug 6, 2014 at 1:25 PM, Ryan Shugart 
<[email protected]<mailto:[email protected]>> wrote:
So really odd, I can validate the package on that DP and it validates 
successfully but I can’t remove it, the remove button is greyed out for some 
reason.  I actually can’t edit the package at all and I’m not sure why, I have 
rights to it in security.
Ryan

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]<mailto:[email protected]>] 
On Behalf Of Niall Brady
Sent: Wednesday, August 6, 2014 12:11 PM
To: [email protected]<mailto:[email protected]>
Subject: Re: [mssms] what's the deal with the configuration manager client 
package?

failed to resolve PackageID=䊘Ȏ
that's a package problem (in wmi) on whatever dp it's referring to, i would 
revalidate the package on that dp or use smsdpmon to validate it, if that 
doesn't help, remove the package from the dp, and then re-add it

On Wed, Aug 6, 2014 at 8:00 PM, Todd Hemsell 
<[email protected]<mailto:[email protected]>> wrote:
I made an additional one. I did not like it when the built in one auto 
incremented when I installed hotfixes etc.
With an additional one I can control when os deployment goes down

On Wed, Aug 6, 2014 at 12:18 PM, s kissel 
<[email protected]<mailto:[email protected]>> wrote:
Hi - I don't think it's necessary to create another client package from 
definition - That might have been a 2007 thing.

The Configuration Manager Client Upgrade package is also pre-defined, and can 
be deployed to systems to upgrade them from say SP1 to R2, for example, and 
where applicable.

As for the OSD task sequence indicating that it can't find the client package, 
have you tried to update the content on the distribution points? This might 
also be helpful, if you run into not being able to distribute the client 
package:
http://social.technet.microsoft.com/Forums/en-US/11df0f63-d146-434d-91f3-c4e826fee92c/redistribute-configuration-manager-client-upgrade-package-xxx00003?forum=configmanagermigration

-S
________________________________
From: [email protected]<mailto:[email protected]>

To: [email protected]<mailto:[email protected]>
Subject: [mssms] what's the deal with the configuration manager client package?
Date: Wed, 6 Aug 2014 16:47:44 +0000
Hi:
        So we’re getting errors in our OSD task sequences saying the task 
sequence can’t find the files needed for the Configuration Manager Client 
Package.  We do have such a package available, it appears to have been created 
when SCCM was set up but I really can’t change any of the options for this 
package.  In doing some web research I’m finding this is by design for some 
reason, and you’re supposed to create a new Configuration Manager client 
package from definition.  So I guess two questions.  First, what’s the point of 
the Configuration Manager Client Package in the first place if you can’t do 
anything with it, and if you’re supposed to create a new Configuration Manager 
Client Package from definition how is that done?  I have definitions for Device 
Management Client Transfer and Configuration Manager Client Upgrade.  Should I 
use the Configuration Manager Client Upgrade definition?
Thanks a lot for any help, finding this very confusing.
Ryan

Ryan Shugart
LAN Administrator
MiTek USA, MiTek Denver
314-851-7414


MiTek Holdings, Inc., 2011-2014, All Rights Reserved
  ________________________________
This communication (including any attachments) contains information which is 
confidential and may also be privileged. It is for the exclusive use of the 
intended recipient(s). If you are not the intended recipient(s), please note 
that any distribution, copying, or use of this communication or the information 
in it is strictly prohibited. If you have received this communication in error, 
please notify the sender immediately and then destroy any copies of it.











________________________________


Legal Notice: This email is intended only for the person(s) to whom it is 
addressed. If you are not an intended recipient and have received this message 
in error, please notify the sender immediately by replying to this email or 
calling +44(0) 2083269015 (UK) or +1 866 592 4214 (USA). This email and any 
attachments may be privileged and/or confidential. The unauthorized use, 
disclosure, copying or printing of any information it contains is strictly 
prohibited. The opinions expressed in this email are those of the author and do 
not necessarily represent the views of 1E Ltd. Nothing in this email will 
operate to bind 1E to any order or other contract.

Reply via email to