/build/static/layout/Breadcrumb_cap_w.png

Stubborn client install on Win 7

New Win 7 OS, the machine had the client, would never check in. Restarting the service did nothing. Removed the client, reinstall from the client desktop just does nothing. Provisioning result below - fails with no specific error. how do I fix this to get a client installed?

Provisioning Log

--------------------------------------------------------------------------------


[07/20/11 03:19:04 PM] Begin provisioning...
[07/20/11 03:19:04 PM] Executing Windows platform provisioning.
[07/20/11 03:19:04 PM] Probing tcp ports for accessibility.
[07/20/11 03:19:04 PM] Port 139 [netbios-ssn] open.
[07/20/11 03:19:04 PM] Port 445 [microsoft-ds] open.

STEP 1: CONNECT TCP/SSH - SUCCESSFUL

[07/20/11 03:19:42 PM] Executing remote communications:

Initializing RPC
Connecting to ADMIN$
Copying service file
Disconnecting ADMIN$
Connecting to IPC$

STEP 2: AUTHENTICATION - SUCCESSFUL

Creating service
Opening pipe to service
Sending commands
Sending login credentials
[MSGCODE: 000] Begin agent_provision.bat processing.
[MSGCODE: 064] Detected 64-bit platform
[MSGCODE: 011] .NET 1.1 is installed
[MSGCODE: 015] Executing KInstallerSetupSilent.msi
.Return code (MSI_ERROR_LEVEL) from MSI execution: [0]
MSI Info: [ERROR_SUCCESS] The action completed successfully.
[MSGCODE: 002] KBOX Agent is not installed.
.[MSGCODE: 092] AMP is not connected.
[MSGCODE: 095] KUID file not written by kinstaller.
[MSGCODE: 100] agent_provision.bat exiting.
exit code: 0Removing service
Connecting to ADMIN$
Deleting service file
Disconnecting ADMIN$

STEP 3: PUSH SCRIPT\PROVISIONING - FAILED

End of remote communications.

[07/20/11 03:19:42 PM] End provisioning run

0 Comments   [ + ] Show comments

Answers (3)

Posted by: mwaychoff 13 years ago
Senior Yellow Belt
0
This may sound stupid, but did you try installing the .net 1.1 package that came with the client? Or are you using the 5.3 agent that doesn't require .net?
Posted by: mlathrop 13 years ago
Fifth Degree Brown Belt
0
We image all new machines with .NET 1.1 and the 5.1.38724 client.
Posted by: GillySpy 13 years ago
7th Degree Black Belt
0
There are some issues that .net 1.1 sp1 fixes and I don't know why. 5.3 client doesn't require .Net when that comes out
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ