mark_sharman Posted February 12, 2007 Posted February 12, 2007 Please help!!! This may be a very easy problem to solve, but have tried everything and we are running out of ideas. We have recently moved over from roaming profiles to mandatory profiles, to reduce logon times, which all works fine. The only problem is that we use Ranger; and so when we delete a user through Ranger, it also removes the mandatory profile specified in the profile path. This is quite a nightmare, as you could imagine, considering that one profile is used by a whole year group. When deleting the user, we can remove the profile path first, which then does not remove the profile, but as you can see, this is not very practical. Also, when creating a new user through Ranger, it adds permissions to the mandatory profile for that user, unless we dont put a profile path in on the account creation, again, not very practical. Any ideas on this matter would be very gratefully received Thank you
ajbritton Posted February 12, 2007 Posted February 12, 2007 First of all, I would report it to Ranger themselves. There may be another workaround for this 'feature'. Presumably you could 'bulk remove' the user profile settings using AD Users & Computers (select multiple accounts, right click, properties, change profile path to anything you like), and then use Ranger to delete the users.
maniac Posted February 23, 2007 Posted February 23, 2007 Just spotted this post. I also had the same problem when I moved to mandatory profiles with ranger last year. Ranger are aware of this problem with their current product, it was never designed to work with mandatory profiles apparently. They were very surprised when I mentioned I had it working with mandatory profiles on our network! The simple answer is not to use ranger to delete the user accounts, we delete all accounts using active directory. Takes a bit longer to do thou as you have to delete the homfolder manually. You can also protect the mandatory profile so ranger can't delete it, it will give you a nice error and crash if you try, but no harm will be done. As for it adding permissions to the profile folder, this is something else we noticed. We worked around this by changing the sharing permissions on the folder so students had read only access, so no matter what ranger adds to the security permissions it made no difference, the kids still can't do any harm to it. Periodically I manually remove the added SIDs from the folder to keep it tidy. Mike
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now