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]] On Behalf Of Daniel Ratliff Sent: Tuesday, April 15, 2014 3:13 PM To: [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.
<<image001.jpg>>
