ITRC DDM Inventory (Enterprise Discovery) Forum
Showing results for 
Search instead for 
Do you mean 

deployment credentials not taken ?

Occasional Visitor

deployment credentials not taken ?

i get this error even after i have entered the deployment credentials. Looks like i have missed out some linking between the credentials and device.
pls help.

Error :
Installing on 16.138.50.21 (workgroup="") using RPC.
No administrator accounts configured for deployment.
3 REPLIES
Esteemed Contributor Esteemed Contributor

Re: deployment credentials not taken ?

Did you add your credentials to your Agent Profile and is the agent profile added to the Device Group where the device's IP address is configured?
Occasional Visitor

Re: deployment credentials not taken ?

I was trying that for autodeployment of agent and then later i got this error:
Installing on 16.138.53.20 (workgroup="") using RPC.
Using "'ASIAPACIFIC\abc'".
Successfully connected to "ADMIN$" .
Unable to create file "\\16.138.53.20\ADMIN$\ovedagentinstaller.exe", error: \\16.138.53.20\ADMIN$\ovedagentinstaller.exe (Access is denied).

THen i tried Agentless scanning, I got a similar error:

2009-02-17 08:03 Read 142.log "Authentication failed." error error=-53
142.failure
2009-02-17 08:03 Write 142.open ssh://16.138.53.20 maxkbs=0 agentprofileid=201
2009-02-17 08:03 Read 141.log "Unable to create file '\\16.138.53.20\ADMIN$\ovedscansvc.exe', error: \\16.138.53.21\ADMIN$\ovedscansvc.exe (Access is denied)." error error=-53
141.failure
2009-02-17 08:03 Write 141.open winrpc://16.138.53.20 maxkbs=0 agentprofileid=201

May i know why i am getting access denial even if i have shared the destination folder with full permissions ?
Esteemed Contributor Esteemed Contributor

Re: deployment credentials not taken ?

The errors are stright forward. The problem is not with DDM I as DDM I is only using the credentials supplied. I can't really tell you what is wrong without looking at the issue directly. It looks as if the user that you are using cannot copy files. I would open a ticket with support to look at this issue more.