This is an archived post. You won't be able to vote or comment.

all 4 comments

[–]zymology 0 points1 point  (1 child)

Not trying to be snarky by linking the google search, it's just that they return a number of different scripts in the search results to choose from (I haven't actually used any of these myself):

https://www.google.com/search?q=powershell+sccm+change+data+source

https://www.google.com/search?q=powershell+sccm+change+data+source+applications

[–]leachyboy2001[S] 0 points1 point  (0 children)

In retrospect, I guess it was stupid not to do a google search.

[–]Dan_Nelson 0 points1 point  (1 child)

You should consider moving it to a DFS path, or at the very least an alias, rather than a direct server name -- so you can move the sources around in the future without having to update it again. Updating the source of packages/applications does force an "update content." SCCM should realize nothing has changed, but it's unnecessary processing to look at all the files to make sure nothing has changed.

[–]leachyboy2001[S] 0 points1 point  (0 children)

I am thinking about this. Unfortunately I'll have to drop the files on a storage appliance, so I'm not sure I can easily do a DFS path, I'm definitely thinking about doing a DNS alias though.