K1000 Windows 8.1 Support
We are currently running v5.4.76848 of the K1000 and have rolled out Windows 8 x64 across our organization. All is working well. We are now testing Windows 8.1 images by deploying them with our K2000 but the K1000 agent gets installed but the machines never show up in inventory. Anyone else running or testing Windows 8.1?
-
Windows 8.1 Enterprise x64 is working fine as far as checking in with agent 5.4.10622 but as was mentioned patching isn't working yet. This OS is seen as different from 8 so is not a supported OS yet. - RichB 11 years ago
-
I have the same issue. Just got in some 8.1 systems and I can't put an agent on them. We have the latest software installed on our server. - iceheat 10 years ago
Answers (14)
I wasn't 100% clear on whether you were including the agent within your image or not, but it's usually recommended to deploy it post-installation to prevent problems such as this.
If it is included within your image, the below article may be of help:
http://www.kace.com/support/resources/kb/solutiondetail?sol=SOL112151
We are trying to deploy the Kace agent to a Windows 8.1 computer but it fails everytime. We are using agent version 5.5.25198. Pushing the agent fails everytime on step 3:
STEP 3: PUSH SCRIPT\PROVISIONING - FAILED
[11/11/13 11:36:19 AM] End of remote communications.
[11/11/13 11:36:19 AM] End provisioning run.
I have completely uninstalled Virus Scan from the computer and the firewall is off. Has anyone else had trouble pushing the agent to Windows 8.1?
Comments:
-
I've had trouble pushing the agent to 8.1 with the following error: ERROR: Cannot open pipe - NT_STATUS_INVALID_PARAMETER - Ultimation 10 years ago
Yes, we are using a post install task to add the K1000 agent. It installs, but the 8.1 clients don't ever check in. I have tried running runkbot 4 0 manually and rebooted many times. Verified firewall etc. No luck. Nico_K, you mention you have it working under 8.1, are you running v5.4 or v5.5? From what I remember reading there were a number of issues with 5.5 when it first released which is why we held off updating.
Comments:
-
5.5.90545 (aka 5.5GA) with 5.5.25198 agent.
Yes, there are some issues but no one causing not to check in.
I would try to uninstall the agent and reinstall. may be a antivirus solution - Nico_K 11 years ago
Ok we just setup a test on v5.5 and the agent is working correctly on Windows 8.1. We were just concerned about moving to v5.5 since we saw some people having various issues.
Comments:
-
What is your setup for it to work? ive tried everything possible - abechtold 10 years ago
Provisioning Log |
||
[11/11/13 11:36:17 AM] Executing Windows platform provisioning. [11/11/13 11:36:17 AM] Probing tcp ports for accessibility. [11/11/13 11:36:17 AM] Port 139 [netbios-ssn] open [11/11/13 11:36:17 AM] Port 445 [microsoft-ds] open STEP 1: CONNECT TCP/SSH - SUCCESSFUL [11/11/13 11:36:19 AM] Executing remote communications: Initializing RPC Connecting to ADMIN$ Copying service file Disconnecting ADMIN$ Connecting to IPC$ STEP 2: AUTHENTICATION - SUCCESSFUL Opening pipe to service ERROR: Cannot open pipe - NT_STATUS_INVALID_PARAMETER Connecting to ADMIN$ Deleting service file Disconnecting ADMIN$ STEP 3: PUSH SCRIPT\PROVISIONING - FAILED [11/11/13 11:36:19 AM] End of remote communications. [11/11/13 11:36:19 AM] End provisioning run. |
||
I did the following on my 4 Windows 8.1 machines, then it worked correctly....
1) Change UAC GUI to lowest option
2) Change Reg Setting for UAC:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
In the details pane (Right Pane), locate the EnableLUA key (REG_DWORD type). Double click to Modify. In the Value data box, type 0 (zero), and then click OK.
NOTE: Solution:
On the client system that has the KACE agent, please follow the steps below to uninstall the KACE agent:
Type cmd in the search programs and files box.
The cmd box will pop up. Go to c:\Program Files (or Program File x86 if 64 bit)\Dell\KACE
Type amptools.exe uninstall. The AMPAgent will stop and the agent is uninstalled
I am currently running server version: 5.5.90547
I am also running kace agent version: 5.5.30275
The agent runs perfectly fine for windows 7, but fails on windows 8
Tree connect request after request to end session or internal error.
Top Answer
This is a known issue with 5.5 Server. This issue is fixed in next server release.
Comments:
-
Forgive me, but I get tired of hearing this from providers. 8.1 has been available for months now, and was in beta for longer. How can there not be a minor update to make 8.1 pushes work yet? - DurocShark 10 years ago
-
We have version 5.5 of the server and still have the same issue when trying to deploy the agent on Windows 8.1
Is this working for anyone?
Currently Installed Server Version: 5.5.90546
Currently Downloaded Agent Bundle Version: 5.5.30276
STEP 1: CONNECT TCP/SSH - SUCCESSFUL
[01/24/14 10:38:06 AM] Executing remote communications:
Initializing RPC
Connecting to ADMIN$
Copying service file
Disconnecting ADMIN$
Connecting to IPC$
STEP 2: AUTHENTICATION - SUCCESSFUL
Opening pipe to service
ERROR: Cannot open pipe - NT_STATUS_INVALID_PARAMETER
Connecting to ADMIN$
Deleting service file
Disconnecting ADMIN$
STEP 3: PUSH SCRIPT\PROVISIONING - FAILED
[01/24/14 10:38:06 AM] End of remote communications.
[01/24/14 10:38:06 AM] End provisioning run. - JGoof 10 years ago-
I'm still having this issue as well. - jlazerus 10 years ago
-
I am as well - Aaron vanwormer 10 years ago