Hi there.<\/p>\n
For a few years now, it’s always a pain installing software from my MDM that requires the .Net framework since I have to change the below key to 0, reboot, then install the software, change it back to 1, then reboot.<\/p>\n
Even if I get the package from the ISO and run a powershell script, it errors out because I think it’s still looking to reach out to Windows update.<\/p>\n
Any way around Windows Update? I can ask our admins to add .Net to the server, but I read that is not standard practice.<\/p>\n
Computer\\HKEY_LOCAL_MACHINE\\SOFTWARE\\Policies\\Microsoft\\Windows\\WindowsUpdate\\AU
\nName: UseWUServer<\/p>\n
*******Updated the above. I said WSUS above when I meant to say Windows Update! My fault!<\/p>","upvoteCount":2,"answerCount":8,"datePublished":"2025-05-08T13:12:50.719Z","author":{"@type":"Person","name":"spiceuser-nf4tb","url":"https://community.spiceworks.com/u/spiceuser-nf4tb"},"acceptedAnswer":{"@type":"Answer","text":"
Sorry about that. I tried a lot of things, like mounting the ISO then pointing it to D:.… But, the files mainly experiment with are in C:\\temp\\Source\\sxs<\/p>\n
The single quotes… It still seemed to take the command. That error came up after maybe 5 seconds, but I can try normal quotes. No problem.<\/p>\n
I’ll get back to you later. I now am trying to download the PDQ package, zip up the files and the bat file, import it into my MDM. Looking at the registry and taskmanger, it seems to be work.<\/p>\n
I’ll report back later.<\/p>\n
*EDIT Yes, the bat file, along with the .cab file from PDQ seem to work. The PDQ bat file script language is below if it helps anyone else:<\/p>\n
ECHO OFF
\n%SYSTEMROOT%\\System32\\dism.exe /online /Get-Featureinfo /FeatureName:NetFx3 | findstr Enabled
\nIF %ERRORLEVEL% EQU 0 (
\nECHO .NET 3.5 is already enabled
\n) ELSE (
\n%SYSTEMROOT%\\system32\\DISM.exe /online /enable-feature /featurename:NetFx3 /All /Source:.\\sxs /LimitAccess
\n)<\/p>","upvoteCount":0,"datePublished":"2025-05-12T13:43:36.403Z","url":"https://community.spiceworks.com/t/how-to-handle-net-framework-installs-in-a-domain/1203802/7","author":{"@type":"Person","name":"spiceuser-nf4tb","url":"https://community.spiceworks.com/u/spiceuser-nf4tb"}},"suggestedAnswer":[{"@type":"Answer","text":"
Hi there.<\/p>\n
For a few years now, it’s always a pain installing software from my MDM that requires the .Net framework since I have to change the below key to 0, reboot, then install the software, change it back to 1, then reboot.<\/p>\n
Even if I get the package from the ISO and run a powershell script, it errors out because I think it’s still looking to reach out to Windows update.<\/p>\n
Any way around Windows Update? I can ask our admins to add .Net to the server, but I read that is not standard practice.<\/p>\n
Computer\\HKEY_LOCAL_MACHINE\\SOFTWARE\\Policies\\Microsoft\\Windows\\WindowsUpdate\\AU
\nName: UseWUServer<\/p>\n
*******Updated the above. I said WSUS above when I meant to say Windows Update! My fault!<\/p>","upvoteCount":2,"datePublished":"2025-05-08T13:12:50.825Z","url":"https://community.spiceworks.com/t/how-to-handle-net-framework-installs-in-a-domain/1203802/1","author":{"@type":"Person","name":"spiceuser-nf4tb","url":"https://community.spiceworks.com/u/spiceuser-nf4tb"}},{"@type":"Answer","text":"
You have a number of options.<\/p>\n