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

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 seen this particular issue before. In cases like this, you'd probably be better off submitting a support ticket to KACE.
Answered 03/12/2010 by: airwolf
Tenth Degree Black Belt

Please log in to comment
0
Sounds like firewall or UAC. Turn UAC off.
Answered 03/12/2010 by: bgatech
Orange Senior Belt

Please log in to comment
0
Firewall and UAC are common culprits with Windows 7 deployments, but those error messages are new to me.
Answered 03/12/2010 by: airwolf
Tenth Degree Black Belt

Please log in to comment
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.
Answered 03/12/2010 by: RichB
Third Degree Green Belt

Please log in to comment
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.
Answered 03/12/2010 by: airwolf
Tenth Degree Black Belt

Please log in to comment
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.
Answered 03/12/2010 by: btrotter
Senior Yellow Belt

Please log in to comment
0
Answered 03/12/2010 by: RichB
Third Degree Green Belt

Please log in to comment
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.
Answered 03/12/2010 by: GillySpy
Seventh Degree Black Belt

Please log in to comment
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.
Answered 03/12/2010 by: airwolf
Tenth Degree Black Belt

Please log in to comment
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"
Answered 03/12/2010 by: RichB
Third Degree Green Belt

Please log in to comment
0
Andy,
Thanks for closing the loop on the workaround for provisioning Windows 7!
Answered 03/12/2010 by: RichB
Third Degree Green Belt

Please log in to comment
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.
Answered 03/23/2010 by: btrotter
Senior Yellow Belt

Please log in to comment
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.
Answered 03/23/2010 by: neil.levien
Yellow Belt

Please log in to comment
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!!!
Answered 03/20/2012 by: GreekGeek
Senior Yellow Belt

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