Search results for query: *

What is the NDR stats code? http://www.computerperformance.co.uk/exchange2003/exchange2003_NDR.htm

Easy to setup? can't say, One of the other guys here set it up. There's nothing to install on the exchange server.. It just pulls logs from your exchange server on a schedule. There can be a bit of network traffic when it's collecting data so we schedule it to run at night. After it's...

Consolidating the DC's isn't in the current project.. The DC's will remain at the current sites, In the future we may bring a DC for each domain onto our Data Center for DR. That will either be on Blades or VM's The new child domain for exchange currently has 3 global catalog servers, 6...

It's right there in the NDR <apxexsvr01.APEX.LOCAL #5.2.1> 5.2.1 The message is too large. Else it could be a permissions problem. Check the recipient's mailbox. Here's a good list of NDR codes http://www.computerperformance.co.uk/exchange2003/exchange2003_NDR.htm

We use Quest Messagestats to gather that type of information http://www.quest.com/messagestats/ It can give you all that plus trending, mailbox size reports, up time and quite a bit more. It does need to be run on it's own server with SQL

MarkDmac is correct.. We are in the middle of doing the exact same consolidation on a larger scale.

For the Exmerge error: check to see if your admin accout has "deny" checked for the SendAs/ReceiveAs permissions.. If so uncheck it and try Exmerge again. As far as forklifting the exchange DB to the new (same name) domain. If I understand you have an entirely new forest/domain with the...

Our standard procedure for Exchange on DC's is to move the FSMO roles to a new DC, move the users and public folders to a new temp exchange server. Uninstall exchange, demote it and rebuild as a clean exchange server (no DC)from bare metal.

I believe the swing method is the only option. 2007 will only run on the 64 bit OS and 2003 only runs on 32bit. There is no in place upgrade path. Other things to think about in AD The Schema master must be running Windows Server 2003 Service Pack 1 (SP1) or Windows Server 2003 R2 At least 1...