Have agent update K1000 when IP changes
I have a problem where employees with laptops cannot get software from the User Console Library because the IP address from their last inventory (up to 4 hours ago) does not match the IP the K1000 web interface is seeing.
For example I have about 50 scripts in the library to automate the installation of printers in Boston, New York, LA, and Dallas. I have smart labels configured so that if you check in on the Boston, NY, LA, or Dallas subnets you get that site label. I then limit all the scripts for the printers in each site to the appropriate site label so employees will only see the printers they care about.
My biggest problem is the laptops. If they are docked at their desk in Boston and they get inventoried so their IP address is 192.168.100.1 then they undock and go to the other side of the building and login to get a printer they cannot see the scripts because their IP address in the User Console Library sees them as 192.168.200.2.
If I force and Inventory update on them and they logout and in they can now see the scripts for Boston, etc.
This problem would go away if the agent could detect an IP configuration change and either run an inventory (runkbot 4 0) on its own or at least just send the updated IP address to the K1000 so they are always in sync.
Anonymous
shared this idea
Thank you for your very thorough desciption of the issue. We will consider this as a feature request in the future. We prioritize based on feedback like yours – so we encourage others to vote for this feature request.
-
Troy commented
@Lucas - No, this request is asking that whenever a computer gets a new IP address the agent updates the K1000 immediately, not just waiting for a check-in, which for us is 12hrs. So laptops, users who sign on/off VPN, all have issues.
-
Lucas McCuistian
commented
Isn't this similar to this request, which says it was completed in 2019?
-
Herve
commented
The workaround for the moment is to deploy a script that would add an entry in the windows scheduler that would run "runkbot 4 0" whenever the user is logging in after a reboot, sleep mode or simply after locking his desktop. I hope this helps.
-
Tony Dudley
commented
Seconded Ted. Hopefully some new attention in the comments section will bump this topic up, and get Quest to revisit the issue.
-
Ted Sturr
commented
It appears nothing has been done on this in several years - it continues to be an issue for us as well since we are supporting a number of remote users. Hopefully Quest will finally get this thing fixed.
-
This is a big issue for us and getting bigger as we roll out more laptops. We used to have inventories at 1hr to combat this issue but that broke everything else in KACE so we are now at a 6hr inventory this issue has only gotten worse. I don't know how crucial a full check in is, but an updated IP on connection would be fantastic.
-
Anonymous
commented
got the same issue as well removing the agent and reinstalling the agent did not help at all.
-
BlaiseG
commented
We're impacted by this issue, as well. Particularly for our mobile users who move between retail locations. We use labels for determining which replication share to use, which is based upon IP (i.e., "where am I now?").