Daniel,
Ah, that makes sense. I didn't realize that Nomad was causing a delay in content distribution in your environment. Normally, at most of my customers, when I'm using standard server Distribution Points, content changes replicate fairly quickly. I can certainly relate to the pain of trying to run an OSD task sequence, only to find that there's a content mismatch, and have to restart the process. :) It's just part of dealing with ConfigMgr that I've grown accustomed to, though. With great power comes great responsibility (and patience, if you have ConfigMgr), haha. :) You bring up a good point though. If / since you're on R2, you could replace the Run Command Line step with a Run PowerShell Script task sequence item. This may help to reduce confusion in the syntax. You can use the built-in $PSScriptRoot variable (PowerShell v3.0 and later) to determine the "current" folder path where the script resides. I'm not sure if ConfigMgr executes the code as a script, or as an in-line command. There is a difference, and if it's not being executed as a script, then the $PSScriptRoot variable would be $null. It's worth testing out, however. # Recursively copy all items from script's directory to the $env:SystemDrive\test folder Copy-Item -Path $PSScriptRoot\* -Destination $env:SystemDrive\test -Recurse; Cheers, Trevor Sullivan Microsoft PowerShell MVP From: [email protected] [mailto:[email protected]] On Behalf Of Daniel Ratliff Sent: Tuesday, April 15, 2014 4:11 PM To: [email protected] Subject: RE: [mssms] OSD task sequence - Run Command Line - xcopy pulling entire DP share? But not if I want to make a change during the day. If I have to change the content of a prod package, it's a good 15 minutes to distribute to the DPs, and then another 15-30 to get to all the local peers. If I just have to make a task sequence change, it's just a policy update that has to replicate to the site servers, and usually happens within 5 minutes. My biggest headache is when a prod package gets modified or deleted and then any task sequence referencing that package fails or won't start because the content isn't on the DPs. I just try to limit this as much as possible. I do understand some of this process is due to using Nomad (local peers) but that decision was out of my control. If it makes you feel any better, I try to do as many 'Run Command Lines' using PowerShell as possible. I think my record right now is 8 commands in a single Run Command Line step, separated by pipes and semi-colons. :) Daniel Ratliff From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Trevor Sullivan Sent: Tuesday, April 15, 2014 4:54 PM To: [email protected] <mailto:[email protected]> Subject: RE: [mssms] OSD task sequence - Run Command Line - xcopy pulling entire DP share? Daniel, Right, but if you're referencing the package in that task sequence step anyway, then it makes sense to just wrap it up in a batch file (IMO). It's predictable and straightforward (stealing from Niall's article title). :) Cheers, Trevor Sullivan Microsoft PowerShell MVP From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Daniel Ratliff Sent: Tuesday, April 15, 2014 3:13 PM To: [email protected] <mailto:[email protected]> Subject: RE: [mssms] OSD task sequence - Run Command Line - xcopy pulling entire DP share? I had not seen that, it's exactly what I am looking for. Thanks guys! Trevor, I don't mind throwing a wrapper around it, but I do prefer to do as much in the task sequence as possible, therefor I don't have to worry about content. Daniel Ratliff From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Tuesday, April 15, 2014 3:40 PM To: [email protected] <mailto:[email protected]> Subject: RE: [mssms] OSD task sequence - Run Command Line - xcopy pulling entire DP share? Niall did a blog post about this behavior a while back: http://www.niallbrady.com/2010/10/23/how-can-i-copy-files-from-a-package-not -as-straightforward-as-you-think/ J From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Trevor Sullivan Sent: Tuesday, April 15, 2014 2:22 PM To: [email protected] <mailto:[email protected]> Subject: RE: [mssms] OSD task sequence - Run Command Line - xcopy pulling entire DP share? Daniel, How about sticking the xcopy command into a batch file, and using: %~dp0\* instead? Cheers, Trevor Sullivan Microsoft PowerShell MVP From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Daniel Ratliff Sent: Tuesday, April 15, 2014 1:57 PM To: [email protected] <mailto:[email protected]> Subject: [mssms] OSD task sequence - Run Command Line - xcopy pulling entire DP share? Anyone ever seen this before? Perhaps this is how xcopy is intended to work? Assuming I need to change the asterisk to something more granular? We use 1E Nomad and if the content isn't cached locally it pulls from the DP share (Copy content to DP share has to be checked on the pkg). Well, after recently resolving some issues, my Run Command Line is now copying the entire DP share to the Public\Desktop if the content isn't found on a local peer. Shouldn't the task sequence only pull the content from the package source I specified in the Run Command Line step? Daniel Ratliff 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. 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. 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.
<<image001.jpg>>
