DiPersiaTechSo we're running into some issues with credentials. In the beginning, we setup a user account in each customer's AD, which we would then assign to K to use for patching and such. Since this was in AD, everything worked well. Or so we thought.
Then we ran into a customer who has a large number of remote laptops for workers that are never in the office. We couldn't use the AD method above as some of those laptops are never in the office, so they don't have the cached AD/K credential yet.
So we setup local accounts on those machines, added them to the admin group and gave K those credentials to use for scripts and patching.
Problem is now, it appears if one of those machines comes into the office, we get errors from the DC about that local ID trying to autheticate to the DC for (I assume) access to the patch repository.
How is everyone else handling this?
DiPersiaTechWe did try creating this local account in AD, hoping it would just pass the username and password along, but no love.
wodgerI think kaseya distinguishes between local and domain accounts.
I gather that you (understandably) don't want to change the credential and file source settings when the remote laptop user comes into the office. So, if you try patching his laptop when he's in the office, using the local admin credential you set up and using "download from internet" as the file source, does it work? If that works, is there actually a problem? The agent wont' try to access the patch repository unless you actually change the setting, no matter where the laptop is located.
In NZ it might be a problem for a large customer because of data caps and bandwidth used if lots of machines downloaded the same patches from the internet rather than using the local cache on the server. You might have that concern too?
If the only problem is those error messages and you know what's going on, then I'd just ignore them.
DiPersiaTechwe ran into a customer who has a large number of remote laptops for workers that are never in the office ... It appears if one of those machines comes into the office ...
DiPersiaTechwe don't want 100 machines hitting the internet for patching