Jump to content


blanalex

Established Members
  • Posts

    3
  • Joined

  • Last visited

blanalex's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. I think there's a fix now: https://support.microsoft.com/en-us/kb/3127032 I applied it and now I'm downloading the software update. It still stuck at 0% after 20 minutes, but I think it's working, it failed faster before the hotfix.
  2. Well, I'm not sure I see the point of doing the WMI query outside the script? I was thinking something along those lines: (don't mind the language, I've never worked with vbs, this is a general algorithm) model=wmi.query("SELECT version FROM Win32_ComputerSystemProduct") if (model like "ThinkPad T510") then mdt.ApplyDriverPackage("T510") elseif (model like "ThinkPad T520") then mdt.ApplyDriverPackage("T520") endif
  3. In our organization we decided to go with the "control freak" driver management model. However that means we have maintain the computer model list for each task sequence. If we were able to create a single script with all our computer models there, calling Apply Driver Package with the right package, it would be a lot easier. All we would have to do is call this script from all our task sequences. After that, all we would have to maintain is this single script. Is it possible (and how?) to call the Apply Driver Package action from a custom .vbs script?
×
×
  • Create New...