Jump to content




gvlaarho

Help: How to add DotNet Framework 3.5 to Windows 8 during OSD Task sequence



Recommended Posts

Hello,

I have tried everything but no chance to install dot net 3.5 in Windows 8 x64 during task sequence

Commenad used: Dism /online /enable-feature /featurename:NetFx3 /All /LimitAccess /Source:\\SCCMpri\Win8sxs

\\SCCMpri\Win8sxs with Full access for everyone and SCCM compouter

I always receive The source files could not be found.
Use the "source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, ...
error 0x800F0906 or 0x800F081F

 

Sources \\SCCMpri\Win8sxs comes from DVD and Windows 8 version is Microsoft Windows 8 Enterprise - 9200.16384.-.120725-1247_X64

 

If somebody as an idea, welcome !

Share this post


Link to post
Share on other sites


i copy the files to a local temp folder and then install from there, i'll post the steps when i get home and get access to my lab

Share this post


Link to post
Share on other sites

ok here's how I do it

 

xcopy the files locally

 

xcopy.png

 

then install the .net feature

 

add .net.png

  • Like 1

Share this post


Link to post
Share on other sites

Hi Anyweb,

First, thank you for your interset about this topic.

Unfortunately already tried, but not working, always 0x800F081F

the same error occurs when manually done in the OS (after osd and manual DVD install) :( I have no idea what's happens

If i triy from internet, it's ok ....

Share this post


Link to post
Share on other sites

what version of Windows 8 are you using ? and are you using the SXS folder from the same media that was used to install Windows 8

Share this post


Link to post
Share on other sites

Yes

Just a check: What's the size of your SXS folder ?

My one:

about 271 MB; 1143 Files and 772 Folders

Share this post


Link to post
Share on other sites

Finally found the problem: I have re-extracted the iso file then i had discover that all files where not present in the SXS folder -> "Path File Too long" ...

 

So many time lost for that ....

 

Now, it's perfect, i install from a share so i avoid to copy files to local computer

 

Big thanks Anyweb

 

PS: Size now about 274 MB with 1172 files in 772 folders

Share this post


Link to post
Share on other sites

ok thanks for the update and i'm glad it's working

Share this post


Link to post
Share on other sites

Does this work with windows 8 Enterprise x86?

.I have followed the above steps and all copies and initiates properly but also fails with same error code. If I do it manually it gets to about 65% of running the command and fails.......my sxs folder is only 152 mb and 443 folders..... I have used different extractors to see if it makes a differnce but it is the same.

 

Any ideas?

Share this post


Link to post
Share on other sites

You gotta love windows8....... I have tried everything to get this to work, I am running a windows 8 x86 VM on Hyper-v, I have also resorted to building a windows 8 x64 image and copying the sxs folder from this ISO, which may i add is considerably larger than that of it's x86 counterpart.

 

the process always gets to 65.8% and then bombs out with the usual error code. I have tried various locations for the sxs folder to no avail. The only way that I can get this to work is if and only if I attach the ISO within Hyper-V to the VM and then change the command to point to the DVD drive(not practical unless imaging single machines manually via the disc media).

 

What is the difference in the sxs folder in the DVD drive and the sxs folder in the temp directory.......very annoyingto say the least.....

Even if I try to add the feature manually from with the control panel console it complains and errors out.

 

Going to try this out on a physical machine tomorrow incase it is something to do with the fact the windows 8 OS is sitting on Hyper-v. (dont think so though, but sure worth a try)

Share this post


Link to post
Share on other sites

You can do it like anyweb, or copy the directories to the wim. We chose to copy them, they aren't that big in the grand scheme of things, and who knows if we will need them later down the road. For 64 bit you need to disable 64 bit file system redirection for it to work.

Share this post


Link to post
Share on other sites

Sorry, but I am new to SCCM.

anyweb I see that you have a package for 'Windows 8 sources' in your post. Can you expand what is in this package or link to another page if that has already been covered.

Many thanks

Share this post


Link to post
Share on other sites

Can you not just run the DSIM command with the package source checked and skip xcopy to c:\temp all together? That is... if your Source package just includes the sxs folder and it's contents.

 

DISM.exe /Online /Enable-Feature /FeatureName:NetFx3 /all /limitaccess

 

Also, shouldn't you generate a Restart Computer (to currently installed OS) afterwards?

Share this post


Link to post
Share on other sites

To keep it al nice and easy, there is another method to install .NET 3.5 during a task sequence and that is with using the MDT integration. Select the .NET 3.5 feature in the Install Roles and Features -step and create a Task Sequence variable that set the variable WindowsSource to the (networkshare) location with the SXS folder.

Share this post


Link to post
Share on other sites

To keep it al nice and easy, there is another method to install .NET 3.5 during a task sequence and that is with using the MDT integration. Select the .NET 3.5 feature in the Install Roles and Features -step and create a Task Sequence variable that set the variable WindowsSource to the (networkshare) location with the SXS folder.

 

Peter - What credentials will be used to connect to the network share?? During this step?

 

If this is a build and capture TS and therefore the PC is not on the domain, and with no ability to specify credentials, I do not see how a network share could be accessed.

Share this post


Link to post
Share on other sites

 

Peter - What credentials will be used to connect to the network share?? During this step?

 

If this is a build and capture TS and therefore the PC is not on the domain, and with no ability to specify credentials, I do not see how a network share could be accessed.

 

I believe it would be the network access account.

Share this post


Link to post
Share on other sites

Hi,

just to share my experience:

Had simmilar issue than Rocket Man. No way to get .net 3.5 to Win 8 even not during capture and deploy, DISM offline or online image servicing. I think that /limitaccess switch is not working and it always tries to connect to update repository to download feature and this is probably critical point when you have SUP deployed. I haven't verified this yet but I'm suspecting that it tries to download it from WSUS as it's update source. Or the other option is that ISOs of Win8 Enterprise in MS VLSC portal are missing some files to enable .net 3.5

 

What is working for me:

Install clean Windows 8 as virtual machine from original ISO, enable feature from GUI - let it download from microsoft update and then use SCCM capture media to capture image with .Net 3.5

Share this post


Link to post
Share on other sites

For the record, I did what Peter suggested, and that works like a charm. Only difference is that I added the WindowsSource property to my CustomSettings.ini instead of setting the variable in the TS directly.

Share this post


Link to post
Share on other sites

Hi,

just to share my experience:

Had simmilar issue than Rocket Man. No way to get .net 3.5 to Win 8 even not during capture and deploy, DISM offline or online image servicing. I think that /limitaccess switch is not working and it always tries to connect to update repository to download feature and this is probably critical point when you have SUP deployed. I haven't verified this yet but I'm suspecting that it tries to download it from WSUS as it's update source. Or the other option is that ISOs of Win8 Enterprise in MS VLSC portal are missing some files to enable .net 3.5

 

What is working for me:

Install clean Windows 8 as virtual machine from original ISO, enable feature from GUI - let it download from microsoft update and then use SCCM capture media to capture image with .Net 3.5

 

did you try this method ? it's working 100% here everytime

Share this post


Link to post
Share on other sites

Our method is more efficient than anyweb's, although the same command.

 

1) Map a drive to a network folder containing the appropriate sxs folder for the OS version and CPU architecture, and using credentials that have access to the folder (note that the sxs folder contents will almost certainly change with the release of Windows 8.1 in October). This saves a little hard drive space and uses only required bandwidth on the next step.

 

2) Run the command using the above mapped drive, so for us it is:

DISM.exe /online /enable-feature /featurename:NetFX3 /All /Source:N:\ /LimitAccess /NoRestart /quiet

We use this in our Capture task sequences, to speed up the Deploy task sequences.

Share this post


Link to post
Share on other sites

or just rd /s the sxs folder after .net installs... :)

Share this post


Link to post
Share on other sites

i use everything in the SXS folder (and sub folders) - you dont need all of the 'source'

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

×