Provisioning error NT_STATUS_RESOURCE_NAME_NOT_FOUND
Has anyone ever seen this error before while provisioning?
NT_STATUS_RESOURCE_NAME_NOT_FOUND
NT_STATUS_RESOURCE_NAME_NOT_FOUND
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
brucegoose03
11 years ago
Yes i did!
Cause - KBRemoteService was still running.
I used pskill to stop it and then I was able to provision again.
Posted by:
brucegoose03
13 years ago
Yes, results attached below.
I tried searching google to find out what that error means, and found nothing. I've seen it happen in two different environments.
I tried searching google to find out what that error means, and found nothing. I've seen it happen in two different environments.
Posted by:
brucegoose03
13 years ago
I'm going to check the NTLM lan authentication and see what it's set to on the clients and on the KBOX security settings.
Posted by:
GillySpy
13 years ago
If you follow http://www.kace.com/support/kb/index.php?action=artikel&cat=2&id=1013&artlang=en#Testing_Admin_Share_Credentials
is the admin$ active? can you connect to it with psexec?
is the admin$ active? can you connect to it with psexec?
Posted by:
j.hough_FNP
11 years ago
Did you ever happen to figure out what the issue was? We're having the same problem on some of our machines we're trying to deploy the agent too.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.