Help with automating "System Update"

[bloo]

---

catman2u wrote:

it seems each QFE I need to install prompts for a license agreement.

---

  Yup, and so it will stay for the forseeable future.  We are not allowed to suppress QFE license agreement prompts.

[Zymer]

Bloo,

This post is unhelpful on so many levels.  Let's look at the extant questions from this thread, namely:

1. Is this QFE agreement behavior clearly outlined in the current documentation?
2. If not, why not?
3. If we need to individually agree to each update's agreement, why can't the agreements be signed either before or after the installation, en masse?  To be clear, I'm talking about agreeing to each update individually and manually - not bypassing them, or signing a single  "master agreement".  This is *critical* to professional system builders and system admins.

But the way this issue is being handled brings to mind other questions:

1. Why is HP's SSM utility not similarly hobbled?  You start it, and walk away; works great.
2. You state, "The problem is that the QFEs each have an individual license agreement which the publisher requires the end user to accept at install time."  Is this publisher Microsoft?  If yes, see question #1, if no, is there another QFE publisher you could use?
3. Is there someone else we can talk to about this?
4. Is this product still supported?  Assuming someone bought a Lenovo device, and was stuck using TVSU, how does one get support for it, outside of this channel?

Finally, I'll mention that my company is moving to HP equipment, though not because of my opinions, or the handling of this issue.  My experience with the SSM driver-update utility has borne out that it works very well (quickly, silently, and without legal agreements stopping the driver update process), is properly documented, and well-supported.

~ Drew

[epic0range]

HP suppresses it.

STOP FAILING!

Bad support, is bad.

[Mark_Lenovo Administrator]

EpicOrange,

We should look into this further as this discussion is now 2 years old as you point out.   There may be some limitations due to our overall implementation that bloo is alluding to, that might not be fully explained here.

Let's see if we can get a further update.

Thanks

Mark

[NVision]

simply don't add the windows 7 update modules to your repository. i struggled with this also and finally figured out that it was not a setting that i was missing... it's the packages themselves. i removed them from my repository for Windows 7 and run a script afterwards to install them.

it's not worth the headache anymore.

[Zymer]

Hey Mark/Bloo, any updates to this issue?  I only ask because it's been two years now, and I've noticed that the frantic bustle of activity on this issue has waned a tad.

Well, while we wait for the (surely) imminent flurry of news and support of this front... just some updates from MY life over the past two years... My son's now in 6th grade, and my daughter's in 3rd.  We sent them to Florida for a month(!) last summer, which was a great experience for them, because they stayed with Uncle Billy, and he took them hunting and fishing, and they got to shoot guns, etc.  Real outdoorsy stuff, y'know?  My parents still live in Lancaster, PA (I know, right?) but they like the quiet life.  My dad sold his old boat and bought a new one - I hope to get a ride some time this year.  I changed jobs at my company last summer and now I'm (formally) in "Desktop Engineering", which has been pretty different from the "Field" tech job I had previously - even though my involvement with System Update (and hence this post) was started way back when we still used IBM tools.  There's been an lot of change around the systems we use here, and we've gone to a much more locked-down environment vis-a-vis driver installations now. We pretty much leave the machines at the "imaged" state with known good drivers.  And if we need to change them, it's on a one-off basis, but we're probably going to do a lot more reimaging to fix problems rather than get into a driver-by-driver troubleshooting mess. 

Anyway... keep in touch!  *Really* looking forward to hearing the answers to my earlier questions though.

Have a great 2011/12/13!