Yes to scup Windows updates,log And watch net stat traffic between the sup client and dp Is odd about the content transfer log
Sent from my iPhone On Aug 26, 2015, at 4:08 PM, Sean Pomeroy <[email protected]<mailto:[email protected]>> wrote: That's odd, nothing recent in your ContentTransferManager.log file. What makes you think they are downloading updates from the wrong DP? By the looks of this, its not downloading anything. I see it scanning against the SUP properly, and it looks like its downloading an Adobe update. Do you have SCUP installed? On Wed, Aug 26, 2015 at 3:37 PM David McSpadden <[email protected]<mailto:[email protected]>> wrote: SUP is 120304vmWU1201.imcu.local Remote DP that I am trying to connect to is 120615VMBR0401.imcu.local Client ip is 10.0.90.144 Boundary 10.0.90.0-10.0.90.255 Boundary Group is Westside Collection is query rule: select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.SystemOUName = 'IMCU.LOCAL/Branch 77 - Business Recovery' (Could it be because I have the client in this ou IMCU.LOCAL/Branch 77 – Business Recovery/Testing’ and not the one in the query rule??? From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Mike Dzikowski Sent: Wednesday, August 26, 2015 3:11 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Dumb? all is fine. ________________________________ From: [email protected]<mailto:[email protected]> To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Dumb? Date: Wed, 26 Aug 2015 19:07:41 +0000 You want all or just a select few. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Mike Dzikowski Sent: Wednesday, August 26, 2015 3:00 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Dumb? can you zip up the logs from a client and send them to the list? ________________________________ From: [email protected]<mailto:[email protected]> To: [email protected]<mailto:[email protected]> CC: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Dumb? Date: Wed, 26 Aug 2015 18:31:55 +0000 Ok, it’s getting more weird. The remote clients do not have an entry in the Locationservices.log for a Distribution point. Not even empty. Only calling back for WSUS in the log?? I read somewhere that the IP subnet for the boundary may be fooling me but it did not give a reason for that. Is that something that maybe causing the clients to believe they are not in a boundary group and coming back to the SUP server? From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of David McSpadden Sent: Wednesday, August 26, 2015 11:30 AM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Dumb? On the Deployment Package: General tab has package source as \\SUP\sources\WindowsUpdates (<<<<<is this my issue, do I need a Package for each DP with the \\DP\sources\WindowsUpdates here??) Distribution Settings set to High and Manual Content Locations has every DP From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of CESAR.ABREG0 . Sent: Wednesday, August 26, 2015 10:57 AM To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] Dumb? You can protect the SUP DP and set the deployment not to fallback. The DP name should be showing in the package content properties. On Wed, Aug 26, 2015, 7:50 AM Marcum, John <[email protected]<mailto:[email protected]>> wrote: It should point to the SUP not the DP's Typos courtesy of Apple. Sent from my iOS device. On Aug 26, 2015, at 10:40 AM, David McSpadden <[email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>>> wrote: I only have one policy for all locations. That points to the SUP not the DP’s???? From: [email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Charles Hiland Sent: Wednesday, August 26, 2015 10:37 AM To: [email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>> Cc: [email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>> Subject: RE: [mssms] Dumb? Is the group policy on the client machine configured properly (e.g. making sure it points to the DP)? Computer configuration > admin templates > windows components > windows update > specify intranet ms update service location From: [email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of CESAR.ABREG0 . Sent: Wednesday, August 26, 2015 10:27 AM To: [email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>> Cc: [email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>> Subject: Re: [mssms] Dumb? Is the SUP a DP as well? CM clients download data from DPs. Did you distribute the update package to that specific DP? On Wed, Aug 26, 2015, 7:22 AM David McSpadden <[email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>>> wrote: Ok I have all of this but my remote clients are not pulling from the remote DP they are pulling from the SUP? I am sitting here watching a client ip on the SUP downloading the update I just deployed to the collection it is in. I am about to open a case with MS to troubleshoot this. It doesn’t make any sense. From: [email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>> [mailto:[email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>>] On Behalf Of Ryan Sent: Tuesday, August 25, 2015 2:27 PM To: [email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>> Subject: Re: [mssms] Dumb? You need these: Boundary with computers in it Boundary in Boundary Group Boundary Group with DP Software Update Deployment Package on DP (Put the DP in a DP group if you want it to do a group instead of an individual DP) Software Update Group deployed to Collection Computer in Collection On Tue, Aug 25, 2015 at 12:58 PM, David McSpadden <[email protected]<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>>> wrote: Ok So to deploy to a branch location I need: IP subnet ties to a boundary A boundary ties to a boundary group A boundary group ties to a collection A software update group ties distribution point A distribution point ties to a distribution point group A distribution point group ties to a collection A collection ties to a deployment? I am a little confused on what I need in place to get a remote distribution point to pull the software updates that have been distributed from the remote distribution install of across the wan from the SUP? David McSpadden Systems Administrator Indiana Members Credit Union P: 317.554.8190<tel:317.554.8190> | F: 317.554.8106<tel:317.554.8106> [Description: imcu email icon]<http://imcu.com/> [Description: facebook email icon] <https://www.facebook.com/IndianaMembersCU> <image003.jpg><https://twitter.com/IndMembersCU> <image004.jpg> [mcp2] This e-mail and any files transmitted with it are property of Indiana Members Credit Union, are confidential, and are intended solely for the use of the individual or entity to whom this e-mail is addressed. If you are not one of the named recipient(s) or otherwise have reason to believe that you have received this message in error, please notify the sender and delete this message immediately from your computer. Any other use, retention, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please consider the environment before printing this email. This e-mail and any files transmitted with it are property of Indiana Members Credit Union, are confidential, and are intended solely for the use of the individual or entity to whom this e-mail is addressed. If you are not one of the named recipient(s) or otherwise have reason to believe that you have received this message in error, please notify the sender and delete this message immediately from your computer. Any other use, retention, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please consider the environment before printing this email. This e-mail and any files transmitted with it are property of Indiana Members Credit Union, are confidential, and are intended solely for the use of the individual or entity to whom this e-mail is addressed. If you are not one of the named recipient(s) or otherwise have reason to believe that you have received this message in error, please notify the sender and delete this message immediately from your computer. Any other use, retention, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please consider the environment before printing this email. ________________________________ Confidentiality Notice: This e-mail is from a law firm and may be protected by the attorney-client or work product privileges. If you have received this message in error, please notify the sender by replying to this e-mail and then delete it from your computer. This e-mail and any files transmitted with it are property of Indiana Members Credit Union, are confidential, and are intended solely for the use of the individual or entity to whom this e-mail is addressed. If you are not one of the named recipient(s) or otherwise have reason to believe that you have received this message in error, please notify the sender and delete this message immediately from your computer. Any other use, retention, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please consider the environment before printing this email. This e-mail and any files transmitted with it are property of Indiana Members Credit Union, are confidential, and are intended solely for the use of the individual or entity to whom this e-mail is addressed. If you are not one of the named recipient(s) or otherwise have reason to believe that you have received this message in error, please notify the sender and delete this message immediately from your computer. Any other use, retention, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please consider the environment before printing this email. This e-mail and any files transmitted with it are property of Indiana Members Credit Union, are confidential, and are intended solely for the use of the individual or entity to whom this e-mail is addressed. If you are not one of the named recipient(s) or otherwise have reason to believe that you have received this message in error, please notify the sender and delete this message immediately from your computer. Any other use, retention, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please consider the environment before printing this email. This e-mail and any files transmitted with it are property of Indiana Members Credit Union, are confidential, and are intended solely for the use of the individual or entity to whom this e-mail is addressed. If you are not one of the named recipient(s) or otherwise have reason to believe that you have received this message in error, please notify the sender and delete this message immediately from your computer. Any other use, retention, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please consider the environment before printing this email. This e-mail and any files transmitted with it are property of Indiana Members Credit Union, are confidential, and are intended solely for the use of the individual or entity to whom this e-mail is addressed. If you are not one of the named recipient(s) or otherwise have reason to believe that you have received this message in error, please notify the sender and delete this message immediately from your computer. Any other use, retention, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please consider the environment before printing this email.
