Deployment Solution

Hello,

We've been doing scripted OS installs in DS 6.9 for some time.  We've run a Windows XP x86 one for years, and I created two Windows 7 x64 builds at the beginning of this year.  One for laptops and one for desktops.

All of our machines are Dell computers.  Both of these builds Windows 7 have been tested on about 20 machines and have been working fine.

Within the past few weeks, my 7 builds are starting to throw errors on various software installs after the initial OS install completes.

Today for example, I ran my x64 laptop build on a Dell Latitude E6520 and it worked just fine.  I ran my x64 desktop build on a Optiplex 755 and a Optiplex 990.  The 755 failed on a .net framework 4.0 install further into the build with error -2145124341, and the 990 failed on copying my dagent config with error 1.  The 755 performed the copy of the dagent config just fine, and it's the same build.  The laptop build is identical to the desktop build after the OS is installed.  Both of these builds worked just fine a few weeks ago, and the job complete logs are still in the system.  I've checked the files where it errors, they are still present on the server and the permissions are correct.  The correct drivers are installed for the builds.  Nothing has changed since it was working a few weeks ago.

How is this happening?

Maybe the Windows Automatic Update service is using or trying to use the Windows Installer service whilst Altiris is. The Altiris Agent checks to see if the Windows Installer service is in use before running installs but that may be only for programs marked as Windows Installer installs; .NET will be a .exe. Or Automatic Updates may sieze the Windows Installer service whilst the .exe is extracting.

I stop the Automatic Update service during the build, it then starts once the reboot at the end of the build occurs.

I ran the builds again on the 755 and 990.  The 755 went through this time without error.  The 990 again hung on a .net install.  They are running the same build.  No changes were made.

We run WSUS.  If WSUS was causing the issue it would be consistent.

Is there a way to perform the scripted OS installs as 100 base instead of the nic using auto detect?  Our network requires the NIC's to be set to 100.

This always worked in the past however.  I don't know why we would need to set it now.

Try turning WSUS off while the scripted install is running.

but it needs to be set differently for different NICs. Usually reg keys. You might be abel to edit the inf file for the driver, again it would depends on the NIC.