Jump to content


xerxes2985

.NET Framework 3.5 - SCCM/MDT Not installing?

Recommended Posts

Morning all,

I'm running into an odd problem with my SCCM OSD TS. I am using MDT integration and have selected the steps Install Roles and Features to install the .NET Framework 3.5. I have this step right after the Setup Windows and Configuration Manager step. However, upon OSD completion, the process is not complete.

image.png.80cc8a67ce94f1b8665d74df8986f617.png

Here is the excerpt of the step from SMSTS.log, it doesn't show any failures

 

Adding begin group instruction at 38	TSManager	7/16/2018 2:13:53 PM	1620 (0x0654)
There are 1 first level steps or groups	TSManager	7/16/2018 2:13:53 PM	1620 (0x0654)
Parsing step node: Install .NET Framework 3.5 (Includes .NET 2.0 and 3.0)	TSManager	7/16/2018 2:13:53 PM	1620 (0x0654)
Description: 	TSManager	7/16/2018 2:13:53 PM	1620 (0x0654)
ContinueOnError: true	TSManager	7/16/2018 2:13:53 PM	1620 (0x0654)
SuccessCodeList: 0	TSManager	7/16/2018 2:13:53 PM	1620 (0x0654)
RetryCount: 0	TSManager	7/16/2018 2:13:53 PM	1620 (0x0654)
No condition is associated with the step.	TSManager	7/16/2018 2:13:53 PM	1620 (0x0654)
Disable: 	TSManager	7/16/2018 2:13:53 PM	1620 (0x0654)
Run in attribute: WinPEandFullOS	TSManager	7/16/2018 2:13:53 PM	1620 (0x0654)
Timeout: 	TSManager	7/16/2018 2:13:53 PM	1620 (0x0654)
DefaultVarlist found	TSManager	7/16/2018 2:13:53 PM	1620 (0x0654)
Variable name: OSFeatures	TSManager	7/16/2018 2:13:53 PM	1620 (0x0654)
Variable name: OSRoleIndex	TSManager	7/16/2018 2:13:53 PM	1620 (0x0654)
Variable name: OSRoleServices	TSManager	7/16/2018 2:13:53 PM	1620 (0x0654)
Variable name: OSRoles	TSManager	7/16/2018 2:13:53 PM	1620 (0x0654)
Action command line: smsswd.exe /run: cscript.exe "%DeployRoot%\Scripts\ZTIOSRole.wsf"	TSManager	7/16/2018 2:13:53 PM	1620 (0x0654)
Adding instruction at 39	TSManager	7/16/2018 2:13:53 PM	1620 (0x0654)
Processed all elements	TSManager	7/16/2018 2:13:53 PM	1620 (0x0654)

Any assistance is greatly appreciated.

Share this post


Link to post
Share on other sites

We use a package in our environment (don't use MDT, that's why).

1. copy the file microsoft-windows-netfx3-ondemand-package.cab from your install media to a folder on your SCCM server (sources folder)

2. Create a powershell script with the following code

Import-Module Dism

$currentLocation = Split-Path -Parent $MyInvocation.MyCommand.Path;
Enable-WindowsOptionalFeature -Online -FeatureName NetFx3 -Source $currentLocation -LimitAccess -All

3. Create a package which invokes the ps1 script + the cab file (both in same folder)

 

Hopefully this works for you.

Share this post


Link to post
Share on other sites

On 7/20/2018 at 3:41 AM, kevlar01 said:

We use a package in our environment (don't use MDT, that's why).

1. copy the file microsoft-windows-netfx3-ondemand-package.cab from your install media to a folder on your SCCM server (sources folder)

2. Create a powershell script with the following code


Import-Module Dism

$currentLocation = Split-Path -Parent $MyInvocation.MyCommand.Path;
Enable-WindowsOptionalFeature -Online -FeatureName NetFx3 -Source $currentLocation -LimitAccess -All

3. Create a package which invokes the ps1 script + the cab file (both in same folder)

 

Hopefully this works for you.

+1

I also use MDT; however, I use a TS after the section in MDT called "State Restore".  It is just before I start installing applications.  My ps1 is the same as above (minus the Import command).  I have the cab file "microsoft-windows-netfx3-ondemand-package.cab" and ps1 in the same source folder.  The TS is straight forward.

1. Run PowerShell script
2. Browse for the package that is created
3. Script name <insert ps1 file name>
4. PowerShell execution policy = Bypass

 

The package in step #2 is an empty package that just points to the source folder with the ps1 and cab file.  

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.