Location awareness leads towards having inside and outside our networks the same policy for users and admins but thats not what we wont to have. Users that will then use the laptop beyond our networks without connection to our SEPM, will use the policies from the "admins"-group and that is the problem, users are in the SEPM-Group "users" with a much more limiting policy. If we shut down the laptop with the admin account, the policies from the "admins"-group will remain on it.
The laptop stores all location dependent Policies from that group. Probably my english made it difficult to understand, but the problem is: Before we give out a laptop, we prepare it inside our networks with an administrator account that is in the SEPM-group "admins". Our infrastructure needs to have seperate policies for users and administrators independant of if they are inside our networks or outside our networks. While we made some tests to get concerend with it, we came accross a problem: When the Computer is in user mode, it always gets the policy from the Client that logs on, but if this client logoff he will keep the policy from the client that loged off lastly.
If so, and it is the behavior that I observe, it will not work. Hi there :) We want to change our Client management from Computer Mode to User Mode. What I've checked out is, that the client stores only the policies from the group where it is in (that means all policies that are associated with locations in this group) right? Kindly mark the thread accordingly if it resolved the issue.Your post made me investing more time in the location thing which I was not quite familiar. It will send the temporary password to the Administrator Email.Ĭall the Support team and get the resetpass.bat utility to reset the password If you are running SEPM the resetpass.bat utility will not be available you need to give forget password option on SEPM Login page.
0 kommentar(er)
