/build/static/layout/Breadcrumb_cap_w.png

Cannot deploy agent to Windows 7

I have a half-dozen Windows 7 computers in our network, and I cannot get the KBOX agent to deploy to them.
I go to the KBOX agent provisioning and try to manually push it to any one of them and get the error message below.
I have tried using a domain admin account to push with as well as a domain account that is a local admin on each of the computers.

I am running KBOX agent: 5.0.28592, and server 5.0.25766.


{ERROR MESSAGE}


Error: ERROR: Failed to copy file

Record Last Modified:
Record Created:

Provisioning Log

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


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

[03/12/10 10:41:07 AM] Begin provisioning...
[03/12/10 10:41:07 AM] Executing Windows platform provisioning.
[03/12/10 10:41:07 AM] Probing tcp ports for accessibility.
[03/12/10 10:41:07 AM] Port 139 [netbios-ssn] open.
[03/12/10 10:41:07 AM] Port 445 [microsoft-ds] open.

STEP 1: CONNECT TCP/SSH - SUCCESSFUL

[03/12/10 10:41:08 AM] Executing remote communications:

Unknown parameter encountered: "passdb backend"
Ignoring unknown parameter "passdb backend"
Unknown parameter encountered: "username map"
Ignoring unknown parameter "username map"
Unknown parameter encountered: "force user"
Ignoring unknown parameter "force user"
Unknown parameter encountered: "force group"
Ignoring unknown parameter "force group"
Unknown parameter encountered: "guest only"
Ignoring unknown parameter "guest only"
Unknown parameter encountered: "guest ok"
Ignoring unknown parameter "guest ok"
Unknown parameter encountered: "valid users"
Ignoring unknown parameter "valid users"
Unknown parameter encountered: "writeable"
Ignoring unknown parameter "writeable"
Initializing RPC
Connecting to ADMIN$
Copying service file
ERROR: Failed to copy file - /kbox/bin/KBRemoteService.exe - NT_STATUS_SHARING_VIOLATION

STEP 3: PUSH SCRIPT\PROVISIONING - FAILED

End of remote communications.

[03/12/10 10:41:08 AM] End provisioning run.

0 Comments   [ + ] Show comments

Answers (14)

Posted by: GreekGeek 12 years ago
Senior Yellow Belt
0
I am attempting to deploy thru MS GPO the 5.3 MSI (edited with my kbox FQDN) and it goes fine on XP and manually on 7 but fails every time as Group Policy. I have made all changes needed by the agent (UAC off, domain network, file and print sharing on) but the msi fails anyway. opened a support ticket with KACE but no response yet. This is the most trouble I've ever gotten from an MSI thru native MS GPO...arrrggghhh!!!
Posted by: airwolf 14 years ago
Red Belt
0
I haven't seen this particular issue before. In cases like this, you'd probably be better off submitting a support ticket to KACE.
Posted by: bgatech 14 years ago
Orange Senior Belt
0
Sounds like firewall or UAC. Turn UAC off.
Posted by: airwolf 14 years ago
Red Belt
0
Firewall and UAC are common culprits with Windows 7 deployments, but those error messages are new to me.
Posted by: RichB 14 years ago
Second Degree Brown Belt
0
I may be wrong but believe provisioning for Windows 7 is not working yet. Use the manual install method from \\kbox\client\agent_provisioning\windows as long as you are running KBOX version 5.
Posted by: airwolf 14 years ago
Red Belt
0
Windows 7 has been supported by the Server and Client for a few releases. I have been able to successfully provision Windows 7 clients.
Posted by: btrotter 14 years ago
Senior Yellow Belt
0
I did open a ticket with Kace, but they are being very slow in responding.
My only response 2 days ago was asking what account I was running it with.

The firewall is disabled, and I have tried turning UAC off, but with no success.
Posted by: RichB 14 years ago
Posted by: GillySpy 14 years ago
7th Degree Black Belt
0
Also remember the knowledge base. here's the faq that covers the basics: http://www.kace.com/support/customer/faq/index.php?action=artikel&cat=2&id=1013&artlang=en

You will get a faster response from support if you have:
* gone through the faq
* provide all pertinent evidence and information
* provide any pertinent information about your environment. e.g what may have changed in your environment, etc

Maybe "faster" is the wrong word. More accurately, your first response will be further along in the troubleshooting process rather than confirming you have covered the basics.
Posted by: airwolf 14 years ago
Red Belt
0
ORIGINAL: RichB

Provisioning Windows 7 fails


Take a look at the thread, I just posted my results from the ticket I submitted to KACE about this.
Posted by: RichB 14 years ago
Second Degree Brown Belt
0
http://www.kace.com/support/customer/faq/index.php?action=artikel&cat=2&id=1013&artlang=en

Needs to have a paragraph added for Windows 7:

1. Open gpedit.msc
2. Browse to Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options
3. Disable the setting "User Account Control: Run all Administrators in Admin Approval Mode"
Posted by: RichB 14 years ago
Second Degree Brown Belt
0
Andy,
Thanks for closing the loop on the workaround for provisioning Windows 7!
Posted by: btrotter 14 years ago
Senior Yellow Belt
0
I went and made the change under gpedit.msc and am now getting this error:

Provisioning Log

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


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

[03/23/10 05:08:59 PM] Begin provisioning...
[03/23/10 05:08:59 PM] Executing Windows platform provisioning.
[03/23/10 05:08:59 PM] Probing tcp ports for accessibility.
[03/23/10 05:08:59 PM] Port 139 [netbios-ssn] open.
[03/23/10 05:08:59 PM] Port 445 [microsoft-ds] open.

STEP 1: CONNECT TCP/SSH - SUCCESSFUL

[03/23/10 05:09:39 PM] Executing remote communications:

Unknown parameter encountered: "passdb backend"
Ignoring unknown parameter "passdb backend"
Unknown parameter encountered: "username map"
Ignoring unknown parameter "username map"
Unknown parameter encountered: "force user"
Ignoring unknown parameter "force user"
Unknown parameter encountered: "force group"
Ignoring unknown parameter "force group"
Unknown parameter encountered: "guest only"
Ignoring unknown parameter "guest only"
Unknown parameter encountered: "guest ok"
Ignoring unknown parameter "guest ok"
Unknown parameter encountered: "valid users"
Ignoring unknown parameter "valid users"
Unknown parameter encountered: "writeable"
Ignoring unknown parameter "writeable"
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: 011] .NET 1.1 is installed
[MSGCODE: 015] Executing KInstallerSetupSilent.msi
.Return code (MSI_ERROR_LEVEL) from MSI execution: [1603]
MSI Info: [ERROR_INSTALL_FAILURE] A fatal error occurred during installation.
[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.

[03/23/10 05:09:39 PM] End provisioning run.
Posted by: neil.levien 14 years ago
Yellow Belt
0
Are you running 32 bit or 64 bit windows 7?

We have 3 64bit windows 7 machines that currently have UAC enabled and are running the kbox agent fine. We are using the same agent version as you as well.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
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