We are running in to problems with disk space on a small exchange server I have just inherited. Originally IMS stopped as it was complaining of low disk space. I created a pagefile on D and removed the one on C. In the short term this has solved the problem or perhaps more accurately bought me some time to figure the problem out.
We currently have 200MB free which is dropping by approx 15mb per day. Last week we were getting 9318 warnings with code of 5 which looks as if it is a security problem- the suggestion from MSoft (Q165324) is to synchronise exchange service accounts for the MTA across the trusted domain setup we are running. We run site connectors through to two other larger sites with multiple exchange servers. Last week (after clearing the disk space) we were getting these errors every few seconds even when mail was being delivered fine- this week we are still getting the errors but much less.
Other possible relevant factors: at one of the sites we connect to (the one refernced in the 9318s) the exchange 5.5 has been moved to a new server. At my site we have recently moved to a new WAN and ISP setup. We have also recently change our inbound mail route from coming in through one of our sites to directly to us (updated MX) and outbound through our ISPs virus towers rather than directly to DNS.
My main question is how do I arrest the disk space issues?
Is the 9318 issue relevant and worth addressing?(we have no Qs backing up)
My main idea is to run Exchange Optimizer in an effort to make sure we are not logging to C ( I am inexperinced in running this)
any other ideas?
many thanks for suggestions
Galloshes
We currently have 200MB free which is dropping by approx 15mb per day. Last week we were getting 9318 warnings with code of 5 which looks as if it is a security problem- the suggestion from MSoft (Q165324) is to synchronise exchange service accounts for the MTA across the trusted domain setup we are running. We run site connectors through to two other larger sites with multiple exchange servers. Last week (after clearing the disk space) we were getting these errors every few seconds even when mail was being delivered fine- this week we are still getting the errors but much less.
Other possible relevant factors: at one of the sites we connect to (the one refernced in the 9318s) the exchange 5.5 has been moved to a new server. At my site we have recently moved to a new WAN and ISP setup. We have also recently change our inbound mail route from coming in through one of our sites to directly to us (updated MX) and outbound through our ISPs virus towers rather than directly to DNS.
My main question is how do I arrest the disk space issues?
Is the 9318 issue relevant and worth addressing?(we have no Qs backing up)
My main idea is to run Exchange Optimizer in an effort to make sure we are not logging to C ( I am inexperinced in running this)
any other ideas?
many thanks for suggestions
Galloshes