Installing .net 3.5 Windows 10 1903 - SCCM
Hello,
I am having problems deploying .net 3.5 on Windows 10 1903 as it is needed for a program that is installed.
i have created a program in sccm and then created a task sequence within sccm to run the program using a powershell script. The task sequence is failing. I did have it working in previous versions of Windows 10 but i am hearing that it is a issue on v1903.
Any help or advice would be greatly appreicated.
Thanks,
Craig
Can you share your script? What part is failing?
Both of these options worked on my Windows 10 2004 VM
DISM
PowerShell
Hi @Mike-Rodrick. I tired those two commands you have shown in your screenshots. I get an error message on both. I had tried running the script in the same directory as the source files with no luck and also tried running it in the Windows\system32 as shown in your example.
I will send you a copy of my script actually i found online but get errors with that as well.
The only way i can get it to run on the machine through a batch file running the dism command. You will see that it shows the source of the files going to the server. is there a way to do that in powershell? I tried copying and pasting the source in powershell but no luck.
If i run the script on a test vm that i have it works fine from the cmd line or running the batch however when i try it in sccm it fails. I think i know what the issue is. You need to run it as an administrator but i am trying to get around that. With powershell you can run as system and it gives you elevated permissions in Sccm. Maybe thats something @Adam-Gordon can suggest something for me.
Maybe you can figure out what is wrong with the PS script and add the sources line in there as well.
When i get the time i am going to take your PS course in-depth. Sorry i have limited knowledge in PS right now.
Thanks 
@Mike-Rodrick I managed to get this script running on the test vm i have with using the Set-Execution Policy to unrestricted.
When I try to create it in SCCM it is not working. Not sure if i am doing it right. I created a package and then a task sequence pointing at the package with this script but no luck.
Any suggestions on what i could do? Maybe @Andy-Gordon can shed some light on it. I will keep plugging away at it.
Craig
@Mike-Rodrick . I have it now working with my script. I had to create a package in sccm and then a custom task sequence using my script that i sent you.
Deployed the task sequence and it is finally working.
Craig
Glad I could help? lol.
Glad you got it working!
In case it comes up again, I believe the DISM command failed because of the space after /featurename: It should be /featurename:"NetFx3" No space between the : and "NetFx3".
@Mike-Rodrick Thanks for the tip. Really appreciate the feedback.
Craig
