There are a couple of ways to approach this – I think the current thinking would be to add a “type” to each script and allow users to define them and then use the View By function. Thoughts?
3 votesJarred Wheeler shared this idea ·
Agreed! Our ARP tables clear every 5 minutes. Wake on LAN is extremely flaky around here (4000+ machines). It gets really frustrating when attempting to image a lab with zero touch...considering that we have to walk to the lab and manually turn on 90% of the machines.
Please fix with a database housed on the appliance!
Also, it'd be nice to have more than a 1GB link. Fibre seems like a viable alternative. We are currently running 10Gb fibre. Imagine the throughput to individual machines if this bandwidth was "tappable". Please update the drivers to support at least 2Gb fibre. 10-50Gb fibre would be optimal.
This is part of a long-term vision in the roadmap towards restoring a machine’s identity on the K1000 when rebuilt from the K2000, with incremental progress being made in each release.
I'm wondering why the K2 is still using a temp file for the naming scheme? Why doesn't it utilize a SQL (or a sql express) server to keep the names/mac address tables in order to rename? If our network "hiccups", the name is lost and a generic name is put in place. Of course, I've remedied this with the application "wsname" but I shouldn't have to. Microsoft's SCOM uses the SQL database for machine naming, so why can't Kace? Just my $.02