My DNS host has created a record that will translate our external exchange address to webmail.ourdomain.com. When I go to http://webmail.ourdomain.com I get a "You are not authorized to view this page" error.
I modified the home directory of the default website in IIS to be a "redirection to a...
Agreed 100%. Groups make permissions so much easier to manage. It easy to set full access at the top level and then use granular ntfs permissions at the root resource. And for the record, it is possible to prevent users from deleting items that even they have created.
You should do more...
It depends on the ACL. Are the users in a specific group that grants them full control NTFS permissions? Are the permissions inherited? Start from the root and work your way up. As you can already tell, permissions can be a nightmare.
But to answer your question, remove both delete...
When a user is created in AD and the users home folder is set to \\server\users\user, does AD automatically give the user full control of that folder? How does it know to make it the owner?
My suggestion would be:
1. Set Everyone with full control in share permissions
2. In security permissions, go to advanced then edit and deselect delete subfolders and files, and delete.
Its probably not the best practice but its what I would do for my company. The one thing to remember...
One of my uers has two email address: user@ourdomain.com (primary) and user@secondomain.com. What Im trying to do is have all mail sent to user@secondomain.com go to a specific folder. I have tried different types of rules and it ends up sending all his mail to that folder. Any ideas?
No, you misunderstood the question. I will be removing the 2k box from AD (demoting it). Once Ive successfully demoted it, I will be replacing it with a brand new 2k3 server. I just want to make sure that I do it correctly, thats all.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.