Customer is using IP Ranges. They work for Software A and B on machine C, but only for Software A on machine D. All on the same network and boundary.
------- David http://www.david-obrien.net From: [email protected] To: [email protected] Subject: RE: [mssms] machines roaming between locations Date: Mon, 3 Feb 2014 14:30:47 +0000 What kind of boundaries are you using? Correct, clients look for content locations dynamically when content is requested. J From: [email protected] <[email protected]> on behalf of David O'Brien <[email protected]> Sent: Monday, February 3, 2014 8:07 AM To: [email protected] Subject: RE: [mssms] machines roaming between locations Ok, checked now. Hearbeat is once a week. But that has nothing to do with it, right? The client should go look for content locations when an installation is being triggered. I had a look at one client being affected by this issue, that installs other software just fine, but hangs at 0% download for an other software (for the last 4 weeks!). Checked with R2 Deployment Monitoring Tool and it tells me for that Deployment there are no Content Locations found. This doesn't happen, as far as I know, to clients not leaving and re-entering boundaries. ------- David http://www.david-obrien.net Date: Thu, 30 Jan 2014 13:42:35 -0600 Subject: Re: [mssms] machines roaming between locations From: [email protected] To: [email protected] ok, I misread that. I was thinking home network as the customers primary location in the office. home office.. meaning base office. On Thu, Jan 30, 2014 at 11:34 AM, Dzikowski, Michael <[email protected]> wrote: How would you even begin to create boundaries for home networks? That's like saying create boundaries for any network a roaming asset attaches to... Or am I missing something? Mike D Sent with Good (www.good.com) -----Original Message----- From: Todd Hemsell [[email protected]] Sent: Thursday, January 30, 2014 11:28 AM Central Standard Time To: [email protected] Subject: Re: [mssms] machines roaming between locations "Obviously we did not create boundaries for their home offices" you need to. define them as fast. no boundary = slow boundary Also, why "Obviously". It has always always been obvious to me you must define boundaries. On Thu, Jan 30, 2014 at 11:23 AM, David O'Brien <[email protected]> wrote: I'll check tomorrow when back at customer. But shouldn't the client automatically check for new content locations without any other cycles running? Looks like the clients sometimes think they're still in an unmanaged network location. --- Original Message --- From: "Dzikowski, Michael" <[email protected]> Sent: 30 January 2014 17:23 To: [email protected] Subject: RE: [mssms] machines roaming between locations How is heartbeat configured? What happens if you run a data discovery cycle on a client that has roamed? Michael Dzikowski Senior Systems Engineer | Ally Technical Infrastructure – Windows Hosting From: [email protected] [mailto:[email protected]] On Behalf Of David O'Brien Sent: Thursday, January 30, 2014 11:06 AM To: [email protected] Subject: RE: [mssms] machines roaming between locations Hi, anyone an idea? Can't see why clients wouldn't realize when they're in a new boundary... ------- David http://www.david-obrien.net From: [email protected] To: [email protected] Subject: [mssms] machines roaming between locations Date: Wed, 29 Jan 2014 21:20:35 +0100 Hi all, experiencing a weird issue again at a customer. Their users roam nearly daily between onsite and their home offices. Obviously we did not create boundaries for their home offices, we did though for the VPN connections and configured them as slow to only get Security Updates. What happens is that those machines get a required deployment policy to install something while at home connected via VPN. It's obviously not being executed, because of the slow boundary. They get in to work the next day and are now in the company's fast boundary. A lot of machines are now stuck at Downloading 0% for a lot of apps. Locationservices.log is saying "Calling back with empty distribution points list" and "Failed to return the distribution points (0x87d00215)" and then "Error invoking LSInvokeCallback". Clients not roaming boundaries do not have these problems. The Deployment Monitoring Tool tells me what above made me expect, that the client didn't find any content location. The boundaries are configured correctly, I just checked the same application with a client that doesn't roam and the content got downloaded right away. Has any of you saw issues with machines roaming locations and then failing to download content? Am I thinking wrong or shouldn't the client realize it's in a managed boundary and get the content location right away? Thanks. ------- David http://www.david-obrien.net
<<inline: image001.png>>
