Jump to content




Sign in to follow this  
nhottinger

Enable .Net 3.5 Framework with dism in TS



Recommended Posts

I'm trying to enable .Net 3.5 Framework during OSD and it fails every time.  If I run the exact same command once the imaging TS has completed it works just fine.  SMSTS.log shows it failed with error code 80004005 which is not very helpful.  I have it running as one of the very last steps.  Here is the command I'm using: dism.exe /online /enable-feature /featurename:NetFX3 /All /Source:"\\bvfyfs01\install$\sccm packages\netframework\sxs".  I have the "Start in:" set to c:\windows\system32.  Any idea what I'm missing here?

 

Failed to run the action: Enable .Net Framework 3.5. 
Unspecified error (Error: 80004005; Source: Windows)    TSManager    4/27/2018 3:31:23 PM    2904 (0x0B58)
Set authenticator in transport    TSManager    4/27/2018 3:31:23 PM    2904 (0x0B58)
Set a global environment variable _SMSTSLastActionRetCode=-2147467259    TSManager    4/27/2018 3:31:23 PM    2904 (0x0B58)
Set a global environment variable _SMSTSLastActionSucceeded=false    TSManager    4/27/2018 3:31:23 PM    2904 (0x0B58)
Clear local default environment    TSManager    4/27/2018 3:31:23 PM    2904 (0x0B58)
Let the parent group (Other Applications) decides whether to continue execution    TSManager    4/27/2018 3:31:23 PM    2904 (0x0B58)
Let the parent group (Install Applications) decide whether to continue execution    TSManager    4/27/2018 3:31:23 PM    2904 (0x0B58)
The execution of the group (Install Applications) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows)    TSManager    4/27/2018 3:31:23 PM    2904 (0x0B58)
Failed to run the last action: Enable .Net Framework 3.5. Execution of task sequence failed.
Unspecified error (Error: 80004005; Source: Windows)    TSManager    4/27/2018 3:31:23 PM    2904 (0x0B58)
Set authenticator in transport    TSManager    4/27/2018 3:31:23 PM    2904 (0x0B58)
Task Sequence Engine failed! Code: enExecutionFail    TSManager    4/27/2018 3:46:23 PM    2904 (0x0B58)
****************************************************************************    TSManager    4/27/2018 3:46:23 PM    2904 (0x0B58)
Task sequence execution failed with error code 80004005    TSManager    4/27/2018 3:46:23 PM    2904 (0x0B58)
Cleaning Up.    TSManager    4/27/2018 3:46:23 PM    2904 (0x0B58)
Removing Authenticator    TSManager    4/27/2018 3:46:23 PM    2904 (0x0B58)
Cleaning up task sequence folder    TSManager    4/27/2018 3:46:23 PM    2904 (0x0B58)
Unable to delete file C:\_SMSTaskSequence\TSEnv.dat (0x80070005). Continuing.    TSManager    4/27/2018 3:46:25 PM    2904 (0x0B58)
Failed to delete directory 'C:\_SMSTaskSequence'    TSManager    4/27/2018 3:46:25 PM    2904 (0x0B58)
SetNamedSecurityInfo() failed.    TSManager    4/27/2018 3:46:25 PM    2904 (0x0B58)
SetObjectOwner() failed. 0x80070005.    TSManager    4/27/2018 3:46:25 PM    2904 (0x0B58)
RemoveFile() failed for C:\_SMSTaskSequence\TSEnv.dat. 0x80070005.    TSManager    4/27/2018 3:46:25 PM    2904 (0x0B58)
RemoveDirectoryW failed (0x80070091) for C:\_SMSTaskSequence    TSManager    4/27/2018 3:46:25 PM    2904 (0x0B58)
Deleting volume ID file C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ...    TSManager    4/27/2018 3:46:25 PM    2904 (0x0B58)
Successfully unregistered Task Sequencing Environment COM Interface.    TSManager    4/27/2018 3:46:25 PM    2904 (0x0B58)
Executing command line: "C:\WINDOWS\CCM\TsProgressUI.exe" /Unregister    TSManager    4/27/2018 3:46:25 PM    2904 (0x0B58)
 

Capture.PNG

Share this post


Link to post
Share on other sites


I made a application I use during TS to install it. Command I use is ""%SystemRoot%\System32\Dism.exe" /Online /LogLevel:4 /Add-Package /PackagePath:"microsoft-windows-netfx3-ondemand-package.cab" /NoRestart /Quiet" for Win10 1703.

Make sure the source of the CAB file matches the OS you're deploying.

Hope this helps.

Share this post


Link to post
Share on other sites

For some reason, all I had to do was take out the "Run this step as the following account" and it's all imaging correctly now.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  


×