Dell Inventory & Updates
Hi,
I am having a slight problem deploying Dell Updates to machines. I scheduled an inventory of Dell Machines - the inventory kicks off but gives an error
"Device Inventory status as of 2011-01-19 'Failed while downloading'.
This did use to work - but I cannot figure out why it doesnt now. I did think this could be due to setting up a replication area and suspected that something was wrong there. However if I run a straight inventory of the machine I get the same error - and this should not be downloading any updates.
Anyone come across this before ? I am new to KACE so its probably an end user problem!
Thanks
I am having a slight problem deploying Dell Updates to machines. I scheduled an inventory of Dell Machines - the inventory kicks off but gives an error
"Device Inventory status as of 2011-01-19 'Failed while downloading'.
This did use to work - but I cannot figure out why it doesnt now. I did think this could be due to setting up a replication area and suspected that something was wrong there. However if I run a straight inventory of the machine I get the same error - and this should not be downloading any updates.
Anyone come across this before ? I am new to KACE so its probably an end user problem!
Thanks
0 Comments
[ + ] Show comments
Answers (6)
Please log in to answer
Posted by:
brucegoose03
10 years ago
Posted by:
cblake
13 years ago
I haven't run across this specific error. Since replication is in play, my first thought would be does this work for machines that aren't in a replication label? Are other replicated objects working properly (eg patches, MI's, etc.) for the affected machines? If multiple replication sites exist, are they also affected? AMP connection is required during the entire process as well, is that possibly being interrupted? Some agent logging might be useful here as well. If all else fails maybe try deleting all dell updates and redownload?
Just a few troubleshooting ideas; I'd certainly open a support ticket though to be sure. Let us know how it turns out.
Just a few troubleshooting ideas; I'd certainly open a support ticket though to be sure. Let us know how it turns out.
Posted by:
the_wolf_of_oz
13 years ago
Thanks for your input cblake.
I havent tried it for machines that are not in the replication label - as my Dell machines are all in one label.
I did however disable the replication share (figured if that was the problem disabling it would resolve the problem) but this made no changes.
I'm only using replication for Dell Updates - and I am not using the kbox for patch distribution.
Only a single replication site exists at this stage - am still in the testing / rollout phase.
I've opened a support ticket and will be sure to feedback any information here.
Thanks.
I havent tried it for machines that are not in the replication label - as my Dell machines are all in one label.
I did however disable the replication share (figured if that was the problem disabling it would resolve the problem) but this made no changes.
I'm only using replication for Dell Updates - and I am not using the kbox for patch distribution.
Only a single replication site exists at this stage - am still in the testing / rollout phase.
I've opened a support ticket and will be sure to feedback any information here.
Thanks.
Posted by:
the_wolf_of_oz
13 years ago
UPDATE :
We have multiple organisations setup in our KACE system that depicts the multiple companies we have operating worldwide.
I have tried this on an organisation that does not have any replication setup and I have the same problem - so I dont believe it is a replication problem.
Just wanted to provide further information as I fiddle.
We have multiple organisations setup in our KACE system that depicts the multiple companies we have operating worldwide.
I have tried this on an organisation that does not have any replication setup and I have the same problem - so I dont believe it is a replication problem.
Just wanted to provide further information as I fiddle.
Posted by:
the_wolf_of_oz
13 years ago
Another Update.
I think it has something to do with the replication share but I dont understand why ALL organisations would be looking at the share when its only set up under one organisation.
I enabled debugging as per KACE support suggestion and the pluginweb.long has the following :
unable to copy: '\\servername\sharename/repl2/dell/cmsdk/InvColPC_7.0.2.1.exe.84471b76a756efb877cae9f166cc4ecb' to: 'C:\Program Files (x86)\KACE\KBOX\dell\InvColPC_7.0.2.1.exe'
Now I think with the \\ and / there is confusion ? I hav my replication path specified as \\servername\sharename which I thought would work but doesnt seem to ?
About to send back the results to Kace support but if someone has done replications and can see an obvious error please let me know.
Thanks !
EDIT : Checking the log again it says it cannot find the path specified so my above statement is not true. Checking the server share those specific files do not appear....no idea why !
I think it has something to do with the replication share but I dont understand why ALL organisations would be looking at the share when its only set up under one organisation.
I enabled debugging as per KACE support suggestion and the pluginweb.long has the following :
unable to copy: '\\servername\sharename/repl2/dell/cmsdk/InvColPC_7.0.2.1.exe.84471b76a756efb877cae9f166cc4ecb' to: 'C:\Program Files (x86)\KACE\KBOX\dell\InvColPC_7.0.2.1.exe'
Now I think with the \\ and / there is confusion ? I hav my replication path specified as \\servername\sharename which I thought would work but doesnt seem to ?
About to send back the results to Kace support but if someone has done replications and can see an obvious error please let me know.
Thanks !
EDIT : Checking the log again it says it cannot find the path specified so my above statement is not true. Checking the server share those specific files do not appear....no idea why !
Posted by:
the_wolf_of_oz
13 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.