"New updates are ready to install"

[aircooled]

I want to leave Automatic Updates on, but do not want desktop users to see the pop-up balloon that says "New updates are ready to install". They are scheduled to install every night so I do not want the users to see the pop-up.

Anything?

Thanks!

 

[timswim78]

Are you running SP1, SP2, or no service packs?

 

[aircooled]

XP SP1

 

[Kilrsat]

If the users are a local administrator, they will see that message. If they are a limited user, they shouldn't see it when the updates are set to install on a schedule.

 

[aircooled]

I found a reg-hack that removes system tray balloon tips:

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced\

Create a DWORD value of EnableBalloonTips

Give it a value of 0


anyone know if this also works for the update balloon (I assume it removes them all, which I don't think I want to do). I may test it on my machine for a while.

 

[spyordie007]

That will remove the pop-up balloons, but it wont remove the icon from the tray. As was stated as far as I'm aware the only way to make it not appear alltogether would be to not give them admin rights (which I would reccomend anyways).

 

[aircooled]

Originally posted by: spyordie007
That will remove the pop-up balloons, but it wont remove the icon from the tray. As was stated as far as I'm aware the only way to make it not appear alltogether would be to not give them admin rights (which I would reccomend anyways).

Unfortunatley, we use a 3rd party app that requires the user ba a local admin (poorly written application).

 

[spyordie007]

what does the app do that requires the user be an admin?

The reason I ask is that *most* applications that claim they require admin privilages will work fine if you just give users permissions to the appropreate directories and/or registry keys.

 

[aircooled]

It's our customer/member database client, written specifically for non-profit membership organizations.
It worked fine on NT4 as a local user, but with 2000/XP that changed.
The company that owns this has a regular consultant that works here alot and basically it was their decision to make the users local admins.
We will be upgrading to their latest (completely re-written for 2000/XP) version in a month or two that should correct this.

 

[mikecel79]

Originally posted by: aircooled
It's our customer/member database client, written specifically for non-profit membership organizations.
It worked fine on NT4 as a local user, but with 2000/XP that changed.
The company that owns this has a regular consultant that works here alot and basically it was their decision to make the users local admins.
We will be upgrading to their latest (completely re-written for 2000/XP) version in a month or two that should correct this.

If it worked in NT as a local admin then it can be made to work in 2k/XP. I recommend getting filemon and regmon from Sysinternals and run the program as a limited user and see what files and/or registry keys it is touching and give them permission to them.

I recently had to do this with our labor tracking program. Their developers insisted the only way to make it work was to set the user to local admin. We had it working except for one part of the program. After using regmon and filemon for a little while I was able to see the registry key it was trying to write to. Once I changed permissions on that it worked perfectly.