/build/static/layout/Breadcrumb_cap_w.png

network scan inventory not showing in system inventory

we have the trial appliance installed, and I'm sure this is a lack of knowledge on my part, but I cannot get systems that show in the network inventory so show in the system inventory...

0 Comments   [ + ] Show comments

Answers (7)

Posted by: tstaub 11 years ago
Second Degree Blue Belt
0
the IP Scan is for network devices like routers and printers that does not have a KACE agent installed
only Operating Systems that have the KACE agent installed shows up in Inventory as a managed node

Please, refer to the Guided Tour from the K1000 Home Console for additional assistance.

Additionally, we have videos posted up on YouTube to help you get started quickly (also listed in the Guided Tour):
http://www.youtube.com/user/kboxbykace#p/f
Posted by: mtsmed 11 years ago
Senior Yellow Belt
0
I installed the KACE agent on this system and it shows as running in task manager, but it still does not show in system inventory
Posted by: mtsmed 11 years ago
Senior Yellow Belt
0
and this is on the k2000, not the k1000
Posted by: tstaub 11 years ago
Second Degree Blue Belt
0
There is no agent for the K2000, therefore the agent installed does not talk to the K2000.
The KACE agent is used only for the K1000 for systems management.

Computers show up in inventory on the K2000 only when "upload inventory" has been selected from the KACE Boot Environment (KBE) via PXE boot. So, you have to have a working PXE environment first which you need to create.

K2000 inventory shows which drivers have been applied to the K2000 to support a scripted OS deployment.

Posted by: davrog 10 years ago
Senior Yellow Belt
0
Hi there - I see this session is pretty old, but hope someone can clarify lack of 'system inventory' detail further for me, as I am experiencing same situatuion on my newly setup/network scanned k2000.
tstaub explained...
"Computers show up in inventory on the K2000 only when "upload inventory" has been selected from the KACE Boot Environment (KBE) via PXE boot. So, you have to have a working PXE environment first which you need to create."

? I dont really understand this. Do you mean only when you have manually selected a pxe boot from a PC will it upload to system inventory? (i.e - after you have reimaged or some such)
So I cannot remote manage/reinstall my EXISTING, pre-Kace machines from my console? (network inventory action-list doesnt seem to respond to boot action or anything).


I have 1 machine that I have tested sending an image out to in my system inventory list - how do I get the rest added?
Posted by: tstaub 10 years ago
Second Degree Blue Belt
0
ORIGINAL: davrog

Hi there - I see this session is pretty old, but hope someone can clarify lack of 'system inventory' detail further for me, as I am experiencing same situatuion on my newly setup/network scanned k2000.
tstaub explained...
"Computers show up in inventory on the K2000 only when "upload inventory" has been selected from the KACE Boot Environment (KBE) via PXE boot. So, you have to have a working PXE environment first which you need to create."?

Yes

ORIGINAL: davrog
I dont really understand this. Do you mean only when you have manually selected a pxe boot from a PC will it upload to system inventory? (i.e - after you have reimaged or some such)

You can either manually PXE boot a computer or set a boot action for that computer by entering in the MAC address and setting a boot action and it would automatically PXE boot and perform the action selected such as deploying a k-image or scripted install.
To automatically collect Hardware Inventory, you can add the "Upload Hardware Inventory" pre-install task for your scripted install or k-image.

Inventory on the K2000 simply shows you which DRIVERS are missing on the K2 on certain machines and therefore which DRIVERS are needed to load on the K2. This is only relevant if you are doing a Scripted OS Install because only the Scripted Install takes advantage of the Driver Library. This does not apply to Imaging on the K2000.
Collecting Inventory (Driver Inventory) can be done at any time from a KACE Boot Environment (KBE) menu. So it does not have to be after a reimage or some such.


ORIGINAL: davrog
So I cannot remote manage/reinstall my EXISTING, pre-Kace machines from my console? (network inventory action-list doesnt seem to respond to boot action or anything).

I have 1 machine that I have tested sending an image out to in my system inventory list - how do I get the rest added?


UltraVNC is built into the KACE Boot Environment (KBE). So any computer that boots into KBE will show up in System Inventory automatically and can be remote controlled (referring to K2000 version 3.3).

If you want to remote control existing computers, you can use the K1000 for Systems Management and also use UltraVNC that is bundled with the K1000 for remote control.

If not already, you may want to view a demo of the K2000 to understand the process. www.kace.com/demo You can sign up for a Live Demo and ask questions via chat.

If you still have technical questions, you may utilize our Trial Live Chat - www.kace.com/chat and be sure to select Trial Appliance Chat.
Posted by: davrog 10 years ago
Senior Yellow Belt
0
Thanks for the answer, but sorry, I'm still confused - nothing seems to work as either you say or the kace demo explains.
All my PCs have come up in the network inventory - but NOT with their mac addresses. Maybe this is why I seem to be prevented from applying any boot action to them. (doesnt go into the select boot action screen at all).
But I still dont understand what the difference is between the system inventory and the network inventory.

And when we're talking about drivers - the scripted install I've tried to setup for a Dell gx620, after first uploading the drivers from the original machine with the driver harvesting, hasnt managed to install ANY drivers. From the 2000 demo, I got the jist that all drivers are available on the kace database and would be automatically installed on scripted install.
Doesnt seem to be the kace (!)

Any further assistance to resolve my confusion and get this stuff working as it should would be extremely gratefully aprreciated!

Many thanks,
Dave
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ