I'm working with the KBOX trial, in a VMware VM I did not setup myself. First thing I'm trying to do is get the KBOX agent on some Windows computers. I couldn't make the Simple Provisioning work on either an XP machine or a Vista machine, so now I need to try the Manual Provisioning. However, when I visit the Software Library on my trial box and download the agent installer, it always downloads a 0 bytes.

Any ideas? Sande
0 Comments   [ + ] Show Comments

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.

Answers

0
I haven't deployed the agent by using the software library, but I'm concerned about your issues with provisioning... What sort of errors are you seeing with provisioning?
Answered 12/14/2009 by: airwolf
Tenth Degree Black Belt

Please log in to comment
0
What kinds of errors with Simple Provisioning? Every kind. After enabling this, that, and the other as documented on the Install Agent Guided Tour page (including disabling UAC which I really, really hate to do, and will undo ASAP), both the XP machine and Vista machine are getting this error:

Error: NT_STATUS_IO_TIMEOUT

Possibly there is not machine at this IP address. Another possibility is that there is a router or firewall blocking the required ports. If Windows Firewall is turned ON, "File and Print Sharing" must be enabled in the Exceptions list of the Firewall Configuration.


It doesn't surprise me much. In our XP configurations, we disabled many features we considered unnecessary, like the Remote Registry service and AutoShareWks. Thought I've re-enabled everything I can think of, and everything the documentation requires, I'm not surprised it still doesn't work.

Since we're not going to visit all 1000 of our XP computers to enable the stuff Simple Provisioning wants, I need the Manual Provisioning to work. So how do I get my hands on this KInstallerSetup.exe file? Sande
Answered 12/14/2009 by: snissen0
Senior Yellow Belt

Please log in to comment
0
I'd suggest you submit a support ticket for your provisioning issues, as you may be able to resolve your issues without having to reconfigure all of your clients. One thing I'd suggest you check is the "Enable File Sharing" setting in KBOX Security Settings in the Settings -> General tab in the KBOX admin console. Enable File Sharing must be enabled for provisioning to work.

If you'd like to continue working on a manual installation method, you can access the KInstallerSetup.exe and the MSI's by enabling file sharing - as previously mentioned - and hitting the kbox client share (i.e. \\kbox\client\agent_provisioning\windows_platform if your KBOX is named "KBOX"). Agent_provision.bat resides in this directory and can be used to install the agent by passing a few parameters to the batch file.
Answered 12/14/2009 by: airwolf
Tenth Degree Black Belt

Please log in to comment
0
Sande,

The agent installer files are always on the share at \\kbox\client\agent_provisioning\. There are a few different versions there, but you should start with KInstaller.exe. Make sure that you replace the default hostname, kbox, with fully qualifield hostname or IP address of your kbox. We have a live chat for trial support if you want to see if we can get you working quickly (http://www.kace.com/support/trial-kbox). Also, Can you post the detailed provisioning log from the machine you are trying to provision? Should say Step 1 with some port check data, and then Step 2, etc.

Thanks,

Chris...
Answered 12/14/2009 by: chrisgrim
Senior Purple Belt

Please log in to comment
0
Well, after disabling Windows Firewall on both machines (and UAC on the Vista box), I did finally get Simple Provisioning to work. Then I turned back on these security features quick as I could.

Meanwhile, I was able to access the KBOX client share (following the documentation, it was already enabled) and download the client files for manual provisioning.

Thanks for yout help.
Answered 12/14/2009 by: snissen0
Senior Yellow Belt

Please log in to comment
0
Sande,

One point of clarification on this. We only need the firewall open and UAC off for initial automated provisioning. Once the agent is installed, all communications with the KBOX is outbound only - we have no requirements for inbound access to machines. Also, there is a mechanism for including the KBOX agent in an image, so a lot of people do manual deployment (or GPO) for existing machines, and then deploy us as they build new machines from then on. The Kinstaller has a flag, -clone_prep=true, that tells the agent you are installing into an image, so don't create the unique ID until the next reboot (typically that would be after an image and sysprep).

Chris...
Answered 12/14/2009 by: chrisgrim
Senior Purple Belt

Please log in to comment
Answer this question or Comment on this question for clarity