UPDATE:  Apparently the Aero issue appears to be unrelated to the driver postinstall.  I will have to look deeper into that...

I am having problems with the driver feed installing the correct video driver for my Optiplex 390/790s.  I can install the driver fine as a postinstall task.  What I want to accomplish though is to have a master image that is the base for all of my images.  So if I include this postinstall task in my system image and deploy it to a different model, it disables Aero for some reason on any new user profiles.  Existing user profiles are unaffected.  It doesn't do this on a 390 or 790 when it actually installs the driver, but if the installer runs on an incompatible model this is the result.

So long story short, has anyone else had issues with the 390/790 video driver?  And how did you resolve it?

This is the latest version from Dell:  Intel_multi-device_A09_R307994  8.15.10.241

Answer Summary:
Cancel
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Answers

1

I had issues with the 390 video drivers and here's what I had to do:

- Create a seperate image instance specifically for the 390s (dup the master)

- Target a Postinstallation task to that instance to install the video driver silently

- Target another Postinstallation task to enable Aero (I used a BAT script with the command "winsat.exe dwm")

That seems to work for me!

 

Answered 05/29/2012 by: jegolf
Red Belt

  • Thanks for the response! It's a shame that certain drivers seem to not work with the feed...
  • "- Create a seperate image instance specifically for the 390s (dup the master)

    - Target a Postinstallation task to that instance to install the video driver silently

    - Target another Postinstallation task to enable Aero (I used a BAT script with the command "winsat.exe dwm")"

    That's not a fix!!! it's a work around that defits the purpose of having KACE in the first place
Please log in to comment
1

In your post installation task you can check for the model of the computer using a vb script and only install it if it matches. Here is part of what you would need.

On Error Resume Next


const HKLM = &H80000002


strComputer = "."


Set oReg=GetObject("winmgmts:{impersonationLevel=impersonate}!\\" &_


strComputer & "\root\default:StdRegProv")


strKeyPath = "SYSTEM\CurrentControlSet\Control\SystemInformation"


strValueName = "SystemProductName"


oReg.GetStringValue HKLM,strKeyPath,strValueName,strValue


WScript.Echo "Model: " & strValue

Youll need to compare that strValue to see if it contains the model your looking for rather than echoing it.

Answered 05/30/2012 by: Tentacle Master
Fourth Degree Black Belt

  • Thanks for the script!
Please log in to comment
Answer this question or Comment on this question for clarity
Five Easy Steps to Smarter Systems Imaging
With traditional methods for systems imaging, each image captures a particular hardware and software configuration at a specific moment in time—static, unchanging, unmanageable.

Share