Sounds like your problem is related to the client being unable to locate the 
content on a DP inside of it's boundary. Double check your boundary settings 
for the IP address, make sure there is a DP assigned to the boundary, or 
optionally enable fallback on your TS deployment settings.

[cid:[email protected]]

From: [email protected] [mailto:[email protected]] On 
Behalf Of Ryan Shugart
Sent: Wednesday, August 06, 2014 10:35 AM
To: [email protected]
Subject: RE: [mssms] what's the deal with the configuration manager client 
package?

Thanks a lot, we did try that and according to the console, at least, it 
redistributed to all the DPs just fine.  The package seems OK although I can't 
edit any details of said package.
Thanks.
Ryan

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of s kissel
Sent: Wednesday, August 6, 2014 11:19 AM
To: [email protected]<mailto:[email protected]>
Subject: RE: [mssms] what's the deal with the configuration manager client 
package?

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.




________________________________

This message is intended for the sole use of the addressee, and may contain 
information that is privileged, confidential and exempt from disclosure under 
applicable law. If you are not the addressee you are hereby notified that you 
may not use, copy, disclose, or distribute to anyone the message or any 
information contained in the message. If you have received this message in 
error, please immediately advise the sender by reply email and delete this 
message.



Reply via email to