I first setup a laps policy within intune to use a custom account which had another policy to create. We then also had a another local security group policy to make members of the IT team local admins on all computers. This policy was set to add (update). We then unfortunately gave this laps password out to anyone anytime they needed to install software or needed a password as we don’t have any EPM software. We do have the company portal set to have all our company apps but anytime a user wants anything it gets approved so using a company app store is not a complete solution but we don’t have the budget for a EPM software. Anyway people started using the laps password to make their normal accounts local admins bypassing our security. I then set the local security group policy to add (remove) from the add (update) it was set on not thinking about how it would remove the custom laps password we had. Now when I use our laps password both the custom account and I tried using the built in admin account and tried using the managed laps account option it will not allow the password to run an installer exe within the users download folder. The laps password does work and it can be logged into but the only way to run an exe from another users profile is to drag the file to the C drive and run it from there or to logout and back into windows under the laps account. Both of which is not great if we are told we don’t need EPM software and to just give the user the laps password since some users will not know how to drag files into their c drive or switch user accounts. Any idea what policy would have been conflicted or changed or the best way to go about fixing this? I would rather not push a PowerShell script changing the permissions of the user profile folder unless that is the only way.<\/p>","upvoteCount":3,"answerCount":19,"datePublished":"2025-07-18T18:56:04.496Z","author":{"@type":"Person","name":"spiceuser-lqqw","url":"https://community.spiceworks.com/u/spiceuser-lqqw"},"suggestedAnswer":[{"@type":"Answer","text":"
Advertisement
Hello,<\/p>\n
I first setup a laps policy within intune to use a custom account which had another policy to create. We then also had a another local security group policy to make members of the IT team local admins on all computers. This policy was set to add (update). We then unfortunately gave this laps password out to anyone anytime they needed to install software or needed a password as we don’t have any EPM software. We do have the company portal set to have all our company apps but anytime a user wants anything it gets approved so using a company app store is not a complete solution but we don’t have the budget for a EPM software. Anyway people started using the laps password to make their normal accounts local admins bypassing our security. I then set the local security group policy to add (remove) from the add (update) it was set on not thinking about how it would remove the custom laps password we had. Now when I use our laps password both the custom account and I tried using the built in admin account and tried using the managed laps account option it will not allow the password to run an installer exe within the users download folder. The laps password does work and it can be logged into but the only way to run an exe from another users profile is to drag the file to the C drive and run it from there or to logout and back into windows under the laps account. Both of which is not great if we are told we don’t need EPM software and to just give the user the laps password since some users will not know how to drag files into their c drive or switch user accounts. Any idea what policy would have been conflicted or changed or the best way to go about fixing this? I would rather not push a PowerShell script changing the permissions of the user profile folder unless that is the only way.<\/p>","upvoteCount":3,"datePublished":"2025-07-18T18:56:04.562Z","url":"https://community.spiceworks.com/t/intune-laps-and-local-security-group-policy-conflict/1225077/1","author":{"@type":"Person","name":"spiceuser-lqqw","url":"https://community.spiceworks.com/u/spiceuser-lqqw"}},{"@type":"Answer","text":"
That’s…not how LAPS is supposed to work…the password is supposed to rotate based on use, time, or command. If it’s not then there is no point. I would suggest you change the LAPS username from whatever admin account you’ve been using to something else first, then redeploy with password rotation based on use.<\/p>","upvoteCount":1,"datePublished":"2025-07-18T19:02:22.294Z","url":"https://community.spiceworks.com/t/intune-laps-and-local-security-group-policy-conflict/1225077/2","author":{"@type":"Person","name":"Jay-Updegrove","url":"https://community.spiceworks.com/u/Jay-Updegrove"}},{"@type":"Answer","text":"
Yep it rotates but when we get another request we give them the latest password so the company does not have to spend any money for EPM software. Not my choice. I wish we could get something like admin by request. I did try changing the username and redeploy but somehow something changed with the user profile and permissions after updating the local security group policy within intune to remove the unauthorized accounts listed on the admin group.<\/p>","upvoteCount":2,"datePublished":"2025-07-18T19:10:44.743Z","url":"https://community.spiceworks.com/t/intune-laps-and-local-security-group-policy-conflict/1225077/3","author":{"@type":"Person","name":"spiceuser-lqqw","url":"https://community.spiceworks.com/u/spiceuser-lqqw"}},{"@type":"Answer","text":"