Search the Community

Since I cannot find any discussion about this I decided to start this new topic. Is .NET Framework 4.6 (and 4.7) supported on ConfigMgr site servers? When doing automated upgrades to stay current, the .NET Framework 4.6 will be installed eventually when you're also using Feature Packs Update Classification. Take a look at KB3102467 for example. Reading documentation it looks like .NET Framework 4.5.2 is the only version supported. No "(or later)" to be found here . I think I know the answer to this question, but I want to be 100% certain in my mind it is not supported. Who can confirm? This is a technet support discussion I have found, it actually could give problems. Any information about when this will be supported?

Hi Guys, I have take ownership of our company sccm recently. We're currently using sccm 2007, right now we have a single site server, I am looking to setup another distribution point on a new site. What's the best practice for this? Can you please point me to some useful guides if possible? Thank you.

Hello, I need some help in figuring out why my site server crashes after I update packages to their Remote Distribution Points. We have had our SCCM environment in place since February and not had an issue until this month. We have had 5 BSODs this month. We thought the problem was resolved after we added an additional 12 GB of RAM to bring the total to 24 GB. I have noticed that it only crashes after I update packages or add new packages to distribution points. It doesn't do it all the time though. The time between the last crash and the most recent is 14 days. Anybody have any thoughts?

Probably a dumb question but does the site server have to have a DP role for any reason. Our SCCM environment was setup before I even knew what SCCM was. We have the management point and like 28 DPs. The package share is located on the site server and because it's a DP it also gets the packaged versions of those source files. So in an interest to rid our selves of some redundancy and regain some server space. I want to remove the DP role, however I wasn't sure if it was originally setup this way because it had to be or because the person who set it up just didn't know any better. Nothing connects to this server as a DP. Each of our 28 offices across the state (including us, central office) have there own DPs. Also the SQL server was placed on the same server as SCCM. It seems to be causing a lot of problems. Is this common or do most connect to SQL on another box. Thanks for any input.

I am running SCCM 2012. I have one site server, running DP, MP, and RP. I have another server just running as a DP. How can I stop my from all my packages being cached in my Main server when I do not set it as a distribution point for my packages. It appears all packages whether or not I apply them to a DP are being stored on my main server. Thanks