K1000 Agent says it installs but but doesn't...
I ran this the ranged provision on my network today, 4 out of 253 said they succeeded, however they are getting the error below and aren't checking in... also not sure why 4 of these PCs succedded and the others did not.
| + Provisioning Target Info | ||
| IP Address: | 192.168.1.102 | |
| MAC Address: | unknown | |
| Host Name (from DNS): | 192.168.1.102 | |
| Suspected OS (from scan): | Windows | |
| Action: | Agent Install | |
| Provisioning Status: | succeeded | |
| K1000 Agent Installed: | Yes | |
| Error Category: | No Error | |
| Record Created: | 08/02/2013 15:51:24 | |
| Record Last Modified: | 08/02/2013 15:51:24 | |
| Provisioning Log |
||
| [08/02/13 02:18:12 PM] Begin provisioning... [08/02/13 02:18:12 PM] Executing Windows platform provisioning. [08/02/13 02:18:12 PM] Probing tcp ports for accessibility. [08/02/13 02:18:12 PM] Port 139 [netbios-ssn] open [08/02/13 02:18:12 PM] Port 445 [microsoft-ds] open STEP 1: CONNECT TCP/SSH - SUCCESSFUL [08/02/13 02:18:12 PM] Executing remote communications: Initializing RPC Connecting to ADMIN$ ERROR: Failed to open connection - NT_STATUS_INTERNAL_ERROR STEP 3: PUSH SCRIPT\PROVISIONING - SUCCESSFUL [08/02/13 02:18:12 PM] End of remote communications. [08/02/13 02:18:12 PM] End provisioning run. |
||
| + Provisioning Configuration Info | ||
| Associated Configuration: | Agent Provision - | |
| Schedule: | Never | |
1 Comment
[ + ] Show comment
-
Did you ever find out more info on this? I've got this issue as well but it only occurs on computers I really don't care about having the agent on or not, so haven't made a big deal about it. - Wildwolfay 10 years ago
Answers (0)
Please log in to answer
Be the first to answer this question
