search

MSEndpointMgr / ConfigMgr

Microsoft Endpoint Configuration Manager scripts and tools
633 stars 281 forks source link

Fix for accessing content directly from DP #128

Closed carterscottm closed 4 years ago

carterscottm commented 5 years ago

Fixes #14 and #41.

This adds an optional PkgShare parameter to use when calling Invoke-CMDownloadContent.ps1 that allows the driver package to be downloaded from the package share using the Copy-Item cmdlet rather than OSDDownloadContent.exe. It's been tested to work in my environment on single package matches. I haven't attempted a multiple package match scenario with this.

The caveat here is that that the package share name will need to be the same on all DPs for this to work. I suppose setting a custom package share name for all driver packages would suffice here. Maybe this option could be added to the Driver Automation Tool. In my case, the site server I'm turning up has a default content share of SMSPKGF$, but the DPs I'm going to start turning up will most likely have SMSPKGD$.

Hopefully somebody else in the community is better at scripting than myself and could propose changes to this to determine the package share name containing the driver packages and render the PkgShare parameter unnecessary.

NickolajA commented 4 years ago

We've decided that we don't want our solution to support accessing content directly from the DP, so I'm not going to merge this PR. Appreciate you sharing your work though.

carterscottm commented 4 years ago

I DO have an updated version, but it's only updated as far as 2.2.7, I just haven't committed it to my fork (yet).  It seems to work for me on ConfigMgr webservice 1.7.0 without issue. I haven't tried it with 1.8.0. I'll try to get my local changes pushed to my fork in the next couple of days.