(imported topic written by bc6591)
I began updating some clients from 7.0.9.110 to 7.0.9.164 after server, console and relay updates.
Most of our users are lowly domain users and after the bigfix client update we got the “Administrative Login Needed” fixlet for an entry in the RunOnce:
C:\PROGRA~1\INSTAL~1{BF702~1\Setup.exe -rebootC:\PROGRA~1\INSTAL~1{BF702~1\reboot.ini -l0x9
First, why does this occur? And…
Is there an easier way around this than logging into each machine as admin?
Thanks, bc
(imported comment written by SystemAdmin)
Hi bc,
It’s not expected that the client upgrades would need a reboot or admin login. Could you help us learn more about what is happening?
Does the client report it is version 7.0.9.164 without you logging in? Ie, does it appear to have upgraded successfully even though the login key exists.
Is this happening on all upgraded clients? Or is it some subset based on OS or having had another BES Component (console/relay) upgraded before?
Tyler
(imported comment written by SystemAdmin)
Actually, we’ve been able to reproduce your problem here and we are doing an investigation into possible fixes. We’ll report back once a solution is ready.
(imported comment written by bc6591)
Hi, Tyler:
Yes the BES Componant Versions Analyses shows the 7.0.9.164 for those clients we upgraded.
Yes is appears to have done it on about all but 3 that were updated. Those 3 were actually set up as local admins; they had just the client, AV and AP on them. All machines are XP sp2 with current updates.
I also had a similar problem with IE 7 fixlet #467. See http://forum.bigfix.com/viewtopic.php?id=1759
Thanks, bc
(imported comment written by bc6591)
Any word on this yet ? Thanks
(imported comment written by StacyLee)
Is this only an issue when upgrading from 7.0.9.110 to 7.0.9.164 ?
I am upgrading from 6.0.21.5 to 7.0.9.164 on May 24th, if it is I may have to hold off on my upgrade then
(imported comment written by SystemAdmin)
I wanted to post an update on this but we are still researching a resolution. The restart needed behavior is caused if you are using one of the BigFix extensions (AntiPest, AntiVirus, Firewall) which install the BES Logging Service. If you aren’t using those extensions you shouldn’t see a restart needed on upgrade. Of those extensions, only the Firewall piece is affected by the restart, the other extensions and the client itself don’t need the restart to work after upgrade.
(imported comment written by bc6591)
Tyler:
We are using AV and AP, but we are NOT using the Firewall. Just FYI.
bc
(imported comment written by StacyLee)
OK we are not using AV/AP/FW so it sounds as if we are OK.
(imported comment written by bc6591)
No joy on this yet, so here are a few of questions ?
It has been suggested that maybe our SYSTEM accounts are screwed up. I dont think they are, but how do you check to make sure your SYSTEM accounts are setup and/or functioning correctly ? We have checked the BES Client service is running as the Local System Account, that the SYSTEM account at the C: has full control, and that group policy is not controlling SYSTEM somehow. Is there anything else to check ? It seems to effect all clients the same unless they have local admin privleges.
Is it true that the BES clients run as SYSTEM by default unless you use RunAsCurrentUser.exe or are there other exceptions to it running as SYSTEM ?
And…
The following command appears to be generated in the HKLM RUNONCE key by the fixlet “Updated BES Client Now Available! (Version 7.0.9.164)” ref #480 perhaps because our users have just domain user privleges.
C:\PROGRA~1\INSTAL~1{BF702~1\Setup.exe -rebootC:\PROGRA~1\INSTAL~1{BF702~1\reboot.ini -l0x9
(Note: {BF702~1 seems to be the InstallShield for the BES client if I had to guess)
What does it do ? When I try to run it manually it errors out. Is the syntax even correct ? Is it necessary ? Everything seems to be running without it as far as I can tell.
Thanks for any help.
(imported comment written by SystemAdmin)
Hi bc,
I believe that we updated the BES Client upgrade Fixlets such that they should no longer cause restart needed states to be created. We did have to split the upgrade Fixlet into a regular upgrade and a (Logging Service Installed) version (ID 480) which should be relevant for you. So, any new upgrades you deploy should not cause the restart needed behavior.
Also, everything should be working normally on your clients that were put into a restart needed state, the restart isn’t necessary for the components to work (unless you are using BigFix Firewall).
Are new upgrade deployments still triggering restart needed?
(imported comment written by bc6591)
Tyler:
I tried a few upgrades just now and it seemed to work just fine.
Thanks very much for all your help.
bc