Maybe I'm missing something or it's a trial limitation. No matter what I put in the range on the IP Scan under Inventory, it only scans my local subnet. I have been able to push the agent to a client on another subnet manually. ????
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


Answered 05/23/2011 by: jds
Senior Yellow Belt

Please log in to comment
Advanced Agent Provisioning is how the K1000 is deployed.
IP Scan is performing a general SNMP scan of network devices such as routers and network printers.
These are not connected in any way for deploying the K1000 Agent.

Using Advanced Provisioning to deploy the K1000 fully supports subnets and even a range of multiple subnets.

Can you post your errors from the failed K1000 agent deployment?

Usually problems in deploying the agent include DNS is not setup correctly and the option to enable .net for 64 bit systems is not checked under the Advanced Provisioning options.

From the /Admin web interface:
Settings > Control Panel > Network Settings

What is listed for:
K1000 DNS Hostname:
K1000 Web Server Name:
Both of them should be the same. For example: k1000.kace.com
From a failed system, try to ping k1000.kace.com does it work? If not, then it's DNS. The K1000 Agent Deployment won't work until this is configured correctly.

For testing only in a non-production environment, you can change the those options to your static IP address if you don't have DNS configured or don't have a DNS server.

Here are some additional technical resources to help you out:
    • Documentation
    • Videos
    • Community Forum
    • Trial Appliance Live Chat
Answered 05/23/2011 by: tstaub
Second Degree Blue Belt

Please log in to comment
As I said, I was able to push the Agent to another subnet successfully to one machine. What I'm asking about is the IP Scan tab. No matter what I put in for the IP range, it always returns the complete local subnet (192.168.2.x in this case). Even trying to specify a range ( within that subnet still returns the entire subnet. Not a big deal just that it doesn't work as it states:

Network Scan IP Range:
(Use hyphens to specify individual IP class ranges - e.g. 192 168 2-5 1-200)
Answered 05/24/2011 by: jds
Senior Yellow Belt

Please log in to comment
I was thrown off by the agent deployment statement. There is no connection to the IP Scan and the Agent. An IP Scan is simply SNMP scans for network devices. No Agent is required for an IP Scan to run.

It will scan what it's been configured for.

Can you share a screen shot of all your Network Scans?
Can you share the results of your Network Scans?

Do you understand how to see the results of the Network Scan?
You need to select Choose Action > View Scan Inventory to actually see the results. These will be results of all the scans entered (Network Scan Settings).
How many Network Scan Schedules do you have? How many are active with a schedule?
Do any of those schedules include the whole subnet?

If you need further assistance, feel free to contact us via Trial Appliance Chat: www.kace.com/chat [be sure to select the Trial Appliance Chat option]
Answered 05/26/2011 by: tstaub
Second Degree Blue Belt

Please log in to comment