.NET Framework 4.0 Deployment

How to Deploy .NET Framework 4.0 via SCCM ?

One of the most common problem when deploying .NET Framework 4.o is handling unexpected restart during a Task Sequence. If you would like to deploy .NET Framework 4.0 in a Task Sequence you would see some kind of logs that the command completed successfully and your Task Sequence will restart unexpectedly.  This issue is directly regarding with handling success codes. 3010 is the code that was genereted by the installation progress and you will see as a success record when you check the report.

You have two options to handle this situation.

1. Deploying via command line

2. Wrapping the installation in a VBScript.

For the first option you may deploy with Command line with the parameters below.

“dotNetFx40_Full_x86_x64.exe /q /norestart /ChainingPackage ADMINDEPLOYMENT”

If you would Return the success code into 0, than you may use the script below ;

—————- script begins —————
Dim Retval
Retval=0
Dim WSHShell
Set WSHShell = WScript.CreateObject(“WScript.Shell”)
WSHShell.Run “dotNetFx40_Full_x86_x64.exe /q /norestart /ChainingPackage ADMINDEPLOYMENT”, 1, True
Set WSHShell = Nothing
Retval = 0
WScript.Quit(Retval)
—————— script ends —————

Advertisements

About gulerergin

SCCM Administrator IT Professional Master Degree Engineer

Posted on June 25, 2012, in SCCM. Bookmark the permalink. Leave a comment.

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: