Hi All,I think there's something a little mis-configured about the permission on my exchange server.In System Manager - First Administrative Group - ServerName... When I right click the servername and go to Properties - Security, I can see our SQL Service account from there, but when I click remove there it tells me it's inheriting permissions from the higher level... So how to I get to those permissions please?Incidentally when I log on to the SQL Service Account and try and open outlook it pops up the username/password box and won't accept anything so I have to cancel out. So something's not right......Many ThanksGraham

All of the permissions that you see on an Exchange server are inherited from somewhere above that in Active Directory. The permissions start out in the Configurationpartition and under the Services container (you can see this in ADSIEDIT.MSC). Someone may have inadvertantly assigned the SQL Server service account permissions somewhere or it is possible that was the account that was actually used to install Exchange Server. Just because the service account has permissions to administrate the Exchange organization does not mean you can open up Outlook and view a mailbox or view other mailboxes. The SQL service account may not even have a mailbox. Is there a specific reason this concerns you? Tinkering with the inherited permissions is not for the faint of heart. If you trust the people that have the password to that account, I would leave it "as is". If not, you may need to remove that account from the permissions list. You would probably have to do it from the Microsoft Exchange object found directly under the CN=Services container in the Configuration partition. I would recommend leaving it alone unless you really need to remove it.My $0.02 worth.Jim McBee - Blog - http://mostlyexchange.blogspot.com

Hi Jim,Many Thanksfor your response. OK, the only reason it's concerning me is that I can't logon (as the SQL Service Account) and access through outlook the mailbox for the SQL Service Account, due to it permanently pushing up a Usenrmame/password dialog. I've only ever experienced this before when a domain account was locked out, but this isn't the case this time round.Many ThanksGraham