Installing .NET Framework 3.5 SP1 Causes Windows Setup Error

For having my images up-to-date I started this week testing the deployment for .NET Framework 3.5 SP1.
At first everything looks ok, and the software installs silenty.

The problem was then deploying the image. For some reason during the setup I was getting this error message:

NETFramwork3_5_SP1_Error_001

Because I’ve made some other changes to the proccess I needed to have sure that .NET Framework 3.5 SP1 was the problem here, so I’ve disable this step on the Task Sequence and then created a new image again.
Now the problem didn’t happen.
h
After some research, asking people about it I’ve run out of options so I’ve installed .NET manually to see if I could understand where the problem was.
After installing I’ve reboot the system and then realized that after restart the .NET installation need to update something on the system (similar to the process after installing some hotfixes via Windows Update).

I’ve then enabled the .NET installation step again and add a Restart Computer step to my Task Sequence. Before this the space between installing .NET and Sysprep the machine had no reboot.

Create the image and now everything works correctly.

How to Change “IT Organization” on Task Sequencer Dialog Box

Here’s a tip for everyone that wants to change the default text that appears on the Task Sequence dialog box.

The default text it’s “IT Organization” and to change it you just need to set a new value for the variable _SMSTSORGNAME on the customsettings.ini file.

For example:

[Settings]
Priority=Default
Properties=MyCustomProperty
[Default]
OSInstall=Y
_SMSTSORGNAME=Frontslash Inc.

Then, you just need to update your deployment point and that’s it.

Task Sequences – Explained

From who cames from Windows XP unattended installations, the new Vista deployment features mais seem a little strange, confusing and scary! That happened to me…
But, that was before having some readiness of the BDD 2007/Microsoft Deployment documents. Now I’m a little less confused.

 One of the first things that made my head go around was the Task Sequencer. I’ve never worked with SMS but who did, told me it was something similar to what we call today Microsoft Deployment tools.

Now, here it’s some info that I’ve extrated from Deployment_Customization_Guide.doc about the task sequences that are set by default when you install MS Deployment:

The Microsoft Deployment process occurs in phases that are defined in the TS.xml file. Task Sequencer parses the TS.xml file to identify the appropriate sequence for performing the deployment process. The phases defined in the TS.xml file include:

Validate Phase
Performs validation checks to make sure that the operating system installation can proceed; specifically blocks installation on server operating systems.

State Capture Phase
Gathers information from the configuration file, databases, and the local machine to determine how the image installation process should proceed, including whether there is enough space to do a local USMT state backup. The scripts also invoke the USMT Scanstate.exe command as appropriate.

Preinstall Phase
Confirms that the necessary information has been gathered in the State Capture Phase for the Refresh Computer and Upgrade Computer scenarios. In the New Computer and Replace Computer scenarios, the script gathers the necessary information in this phase because these scenarios do not perform the State Capture Phase. Also, a backup of the computer can be optionally performed for the Refresh Computer and Upgrade Computer scenarios.

Install Phase
Installs the target operating system on the target computers.

Post Install Phase
Updates the Sysprep.inf file, Sysprep.xml file, or Unattend.txt file with information gathered in the previous custom actions based on the operating system being deployed.

State Restore Phase
Invokes the USMT Loadstate.exe command to restore the user state that was previously backed up.