Managed install on Win 7
Hi all
I've got an issue at managed installs deployment to Win7 machines. They're set up to 'execute at machine bootup' but nothing seems to happen on the Win7 machine. The same install works fine for XP. 'Execute at next available' is ok as well.
Anyone experienced this issue?
Cheers
I've got an issue at managed installs deployment to Win7 machines. They're set up to 'execute at machine bootup' but nothing seems to happen on the Win7 machine. The same install works fine for XP. 'Execute at next available' is ok as well.
Anyone experienced this issue?
Cheers
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
cblake
13 years ago
A few ideas:
First check that Win7 is selected on the supported OS's on the software record.
Does this MI work in other action states, such as while user logged on/off, execute anytime?
Can you verify that you're using the most current version of the agent? A new one was released last week. No guarantees, but it seems like something along those lines may have been addressed. http://www.kace.com/support/customer/downloads.php
First check that Win7 is selected on the supported OS's on the software record.
Does this MI work in other action states, such as while user logged on/off, execute anytime?
Can you verify that you're using the most current version of the agent? A new one was released last week. No guarantees, but it seems like something along those lines may have been addressed. http://www.kace.com/support/customer/downloads.php
Posted by:
KevinG
13 years ago
You may want to enable debug on the client machine to look for errors in the client log files or see if it is even being execute do to some configuration error like Windows 7 not being select as a supported OS for the SW item.
1) On the client machine stop the KBOX SMMP Management Service.
2) Go to Program Files\KACE\KBOX directory
3) Open the smmp.conf file in Wordpad or Notepad and append the following line to the bottom of the SMMP.conf file.
debug=true
4) Save the SMMP.conf file
5) NOTE: If the client is 5.0.x, create a 0 byte file called KBCLIENT_DEBUG in the \Program Files\KACE\KBOX directory.
6) NOTE If the client is 5.0.x Edit the config.xml file in the \Program Files\KACE\KBOX directory and change <DebugLoggingEnabled>false</DebugLoggingEnabled>
TO
<DebugLoggingEnabled>true</DebugLoggingEnabled>
7) Start the KBOX SMMP Management Service.
8) Reproduce the issue on the reported machine that has client debug enabled.
Look at the log files created for errors
1) On the client machine stop the KBOX SMMP Management Service.
2) Go to Program Files\KACE\KBOX directory
3) Open the smmp.conf file in Wordpad or Notepad and append the following line to the bottom of the SMMP.conf file.
debug=true
4) Save the SMMP.conf file
5) NOTE: If the client is 5.0.x, create a 0 byte file called KBCLIENT_DEBUG in the \Program Files\KACE\KBOX directory.
6) NOTE If the client is 5.0.x Edit the config.xml file in the \Program Files\KACE\KBOX directory and change <DebugLoggingEnabled>false</DebugLoggingEnabled>
TO
<DebugLoggingEnabled>true</DebugLoggingEnabled>
7) Start the KBOX SMMP Management Service.
8) Reproduce the issue on the reported machine that has client debug enabled.
Look at the log files created for errors
Posted by:
jkatkace
13 years ago
Also verify that a you're within any deploy window, if any's been set.
Posted by:
folken2k
13 years ago
cblake - I definitely have Win 7 as a supported OS and the MI works fine for the other action states. As for the updates, I've tested both before and after we upgraded yesterday.
jkatkace - I'm using the default deploy window - 0 to 24 hrs
KevinG - I've enabled the debug logging. Hopefully this may help me find a fix.
My thought so far is that the trigger could be different in Win 7. On Win XP I've noticed that the execute before logon action can be triggered both by a reboot or initiating a remote desktop session on the target PC.
jkatkace - I'm using the default deploy window - 0 to 24 hrs
KevinG - I've enabled the debug logging. Hopefully this may help me find a fix.
My thought so far is that the trigger could be different in Win 7. On Win XP I've noticed that the execute before logon action can be triggered both by a reboot or initiating a remote desktop session on the target PC.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.