KACE client does not act the same on Win7 as it does XP at bootup - ??
We have several MI’s that are set to install at bootup prior to logon. We are running the latest released versions of KACE server/client.
In an XP environment, the client boots up and KACE installs the MI’s then the user is prompted with the Ctrl+Alt+Del screen.
In a Windows 7 environment, the client boots up, the user is prompted with the Ctrl+Alt+Del screen, the user has to acknowledge the our company banner screen, then KACE installs the MI’s.
Is this working as expected by KACE? If so, in our opinion, it needs to be changed to match that of how it works with XP.
We’ve told our users the best time to reboot is at lunch. The user reboots, walks away, and comes back to find all MI’s have installed then the user logs in. On Window 7, they will come back, log in, only to be stopped by KACE installing MI’s.
Is anyone seeing what we are with Windows 7 using the latest client/server versions?
Dave
In an XP environment, the client boots up and KACE installs the MI’s then the user is prompted with the Ctrl+Alt+Del screen.
In a Windows 7 environment, the client boots up, the user is prompted with the Ctrl+Alt+Del screen, the user has to acknowledge the our company banner screen, then KACE installs the MI’s.
Is this working as expected by KACE? If so, in our opinion, it needs to be changed to match that of how it works with XP.
We’ve told our users the best time to reboot is at lunch. The user reboots, walks away, and comes back to find all MI’s have installed then the user logs in. On Window 7, they will come back, log in, only to be stopped by KACE installing MI’s.
Is anyone seeing what we are with Windows 7 using the latest client/server versions?
Dave
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
Ryan_Reed
12 years ago
Sounds as if they half-fixed an outstanding issue with the latest release... About a year ago, I updated our server and clients to 5.2.38773\5.1.38724 and lost the ability to run MI's at bootup before login. WinXp or Win7 didn’t matter; it would begin the MI and then immediately continue to the CTRL+ALT+DEL prompt. This allows the user to login right in the middle of a software installation. I reported this problem in May 2011 and was told this would be addressed in a future client update.... took them until Feb 2012 to finally release the update, and it sounds as if this issue is not completely resolved.
Posted by:
rmeyer
12 years ago
you can choose both before and after logon in the Manage Install :)
Comments:
-
rmeyer -
I realize you can choose between those, but the fact is any MI that is set to install at bootup acts differently on an XP than it does on Win7. The install would actually install prior to the user seeing the CTRL+ALT+DEL prompt. With Win7, the user sees the CTRL+ALT+DEL prompt, hits CTRL+ALT+DEL then the MI starts to install.
This is not good when you ask your users to reboot before going to lunch to install software through lunch - only to come back, press CTRL+ALT+DEL , then the MI installs.
Dave - diverdaveman1 11 years ago
Posted by:
diverdaveman1
12 years ago
rmeyer
We do want our MI's to install before logon - that way our users can reboot, walk away/go to lunch, come back and this installs are done. With Windows 7 they have to hang around login to start the installs. They can't leave because then they're leaving their computer unlocked/unattended which is against our company policy.
Installing MI's before logon or prior to Ctrl+Alt+Del also allows us to reboot machines in the middle of the night and get updates before users login the next morning.
Ryan_Reed
Yeah - the 5.1 client/5.3 server broke my MI installation at startup as well. However, the 5.3 client/server combo does bring this back and works great on XP.
Here is the big question: Is anyone else seeing this issue with Windows 7?
Dave
We do want our MI's to install before logon - that way our users can reboot, walk away/go to lunch, come back and this installs are done. With Windows 7 they have to hang around login to start the installs. They can't leave because then they're leaving their computer unlocked/unattended which is against our company policy.
Installing MI's before logon or prior to Ctrl+Alt+Del also allows us to reboot machines in the middle of the night and get updates before users login the next morning.
Ryan_Reed
Yeah - the 5.1 client/5.3 server broke my MI installation at startup as well. However, the 5.3 client/server combo does bring this back and works great on XP.
Here is the big question: Is anyone else seeing this issue with Windows 7?
Dave
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.