The client yes, but what everything before the client is installed? Daniel Ratliff
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Andreas Hammarskjöld Sent: Thursday, January 22, 2015 11:27 AM To: mssms@lists.myitforum.com Subject: RE: [mssms] Can a Task Sequence determine if the client is in a slow boundary? The client should know! When I wrote the BranchCache reporting engine I think I stumbled across it in WMI somewhere. If you really need it I can see if I can dig it up. //A From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Marable, Mike Sent: den 22 januari 2015 15:40 To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: RE: [mssms] Can a Task Sequence determine if the client is in a slow boundary? No, it was all tied to Nomad. If a machine was found to be in a slow site boundary that would trigger all of the Nomad actions (installing the client in WinPE, pre-caching content, using Peer Backup Assistant, etc.) If the script found that the IP address of the machine fell within one of the IP ranges of our slow boundaries we would set a task sequence variable "SlowSite" to TRUE. Then all of the Nomad related actions would key off of that variable. Mike From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Daniel Ratliff Sent: Thursday, January 22, 2015 9:26 AM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: RE: [mssms] Can a Task Sequence determine if the client is in a slow boundary? What did you do in the TS? Kill it? Daniel Ratliff From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Marable, Mike Sent: Thursday, January 22, 2015 9:23 AM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: RE: [mssms] Can a Task Sequence determine if the client is in a slow boundary? We had to use a script to sort it out. We have a number of slow site boundaries, all IP range based. What we have done is to export out the boundaries into a CSV with starting address, ending address and name. During the task sequence we run a script that takes the IP address of the machine and looks it up within the CSV file. If it find that its IP address falls within one of the boundaries we set a task sequence variable that we can key off of showing that it is inside a slow boundary. There may be more elegant ways of doing it but it works for us. Mike From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Roland Janus Sent: Thursday, January 22, 2015 9:17 AM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: RE: [mssms] Can a Task Sequence determine if the client is in a slow boundary? Bump? From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Roland Janus Sent: Mittwoch, 21. Januar 2015 15:03 To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: [mssms] Can a Task Sequence determine if the client is in a slow boundary? You guys have an idea on that? Does a running TS provide somewhere if it is running using a slow boundary? -Roland ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
