We are testing something out that requires us to stop sharing the SMSPDKD$ share on our Primary Site server. If you do stop sharing this folder does that break anything? We are not doing any software deployments right now so what else can it break? And if you do stop sharing it and then re-creating the share will all clients work for software deployments again?

Requires you to stop sharing? Hmmm, sounds like something I would be very hesitant to do. Restarting the SMS_EXECUTIVE and_or SMS_COMPONENT_MANAGER service(s) should recreate the share properly (I wouldn't do it manually). If that doesn't work, a site reset definitely will.Jason | http://blog.configmgrftw.com | Twitter @JasonSandys

if you will stop the share and again you restart the SMS Executive services then share folder will recreate again,Sharad Singh | My blogs: SharadTech | Twitter: @MrLucknowWale |

We are trying to test a new deployment method. We want to make sure SCCM is not copying anything down from the SMSPKG$ share. We are pre-populating the cache folder with the packages since we have a quicker better way of getting content down to workstations and we want to make sure SCCM does not still try to grab from the share. The content transfer and data transfer logs say it it still trying to grab from the share so we want to know.

I'm curious what method you are using to copy these files into the cache and if you're still utilizing SCCM to trigger the install... I suspect you will run into an issue with the package hash.

We are trying to test a new deployment method. We want to make sure SCCM is not copying anything down from the SMSPKG$ share. We are pre-populating the cache folder with the packages since we have a quicker better way of getting content down to workstations and we want to make sure SCCM does not still try to grab from the share. The content transfer and data transfer logs say it it still trying to grab from the share so we want to know. Not sure if you can convince the Client that the legitimate content is in the cache and ready, maybe just its prescence there is enough, be curious how you get on. Ok to summarise, sure you can disable this share, the ramifications you know, Clients won't be able to access content, to be in control as the others have stated if you recycle the SMS services the share will be fixed\created (if missing).