Hi all,

Im facing a small but annoying issue with agent deployment on W7 clients. I keep getting a MSI 1603 error whatever I do with recommended settings (UAC, sharing, firewall, .NET1.1, ...).
I managed to install the agent manually, by copying the \\kace_server\client\...\windows_platform\ locally, then executing agent_provision.bat with proper parameters (agent_provision.bat kace_server client kace_server 0 0 0) (I could not establish SMMP communication but lets keep it for later :)).

My conclusion is that something might go wrong with the fact that the installer is 'called' via a UNC path... is there a way to force KBOX mounting a "provisionning drive" on the client machine and then use that drive for provisionning ? Or maye am i looking the wrong direction ?

Many thanks in advance for your help.

0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


Make sure UAC is completely disabled, and turn off the firewall if it's on. It's possible to deploy the agent to Windows 7, but most of my systems have been installed manually. It definitely isn't as straight-forward as provisioning XP clients.

As for your question about a "provisioning drive" - no, this isn't possible via KBOX provisioning. You could do something like this with custom scripts (logon script, script deployment via GPO, etc.), but what you see is what you get with built-in provisioning in the KBOX.
Answered 04/20/2010 by: airwolf
Tenth Degree Black Belt

Please log in to comment
Thanks for your reply.

I just triple-checked UAC and Fwall but didn't found any issue there. I guess W7 is still pretty new and that we will have some upgraded KBOX agent/installer later on.

For the moment I will dig manual installation / parameters and why not push it with a GPO or maybe better with a psExec script.

Answered 04/20/2010 by: yabo
Senior Yellow Belt

Please log in to comment