Search results for query: *

Who would normally go through the time and effort of configuring and deploying Exchange 2003 in the Enterprise and then turn around and deploy ver. 5.5....Hummm..any takers

If you're looking for an Enterprise solution check out Vircom's Modus Gate. We've had it inplace two years and it does a remarkable job. Quarentines on average 6000 SPAM messages a day. Very low false positive rate as well.

Go into the Exchange 2003 system manager and specify itself as a replication partner under the properties of each public folder. Let it take care of the migration for you. Once replication has taken place remove the 2000 server from the replication partner list.

What you should if you can is turn the old 5.5 Exchange server back on. When performing a migration if you leave the old server on Outlook clients will automatically be redirected to the new server. If you dont you will have to go around to all of the clients and manually redirect them.

Make sure you have "conduit permit gre any any" in the config

Call your ISP and have them open 25. Your paying for the service. If they refuse change ISP's

You have to move the internet mail connector to the new server that will be relaying outbound emails to the internet. Right click on the organzation name within the Exchange System Manager and click "Internet Mail Wizard". Follow the instructions to install it to the server you want to act as...

We're debating on removing SMS for our corp infrastructure all together. Is it neccesary to remove all agents from the workstation prior to SMS server removal or is it possible to just disable the services on the workstation? Disabling the services is easiest for us because we're implementing XP...

In your DNS configuration where is say allow "Dynamic Updates", change it from Secure to Yes. If you using DHCP to issue IP addresses to you clients ensure that you "enable DNS updates" from all DHCP clients in your DHCP server config.

From you mail server your having trouble with Go to a command prompt Type: nslookup Then: set type=mx Then type: companydomain.com The resolved IP addy displayed will reflect the one that your bad server is using. Use this IP addy to verify the end pouint to companydomain.com...

Is the routing problem your having DNS related?

As long as you have an internal DNS server to resolve the FQDN. Take it easy

So if the perimiter router is 192.168.10.2 Firewall external should be 192.168.10.1 Firewall Internal should be 192.168.1.1 Your config in the PIX states External is 192.168.1.1 Internal is192.168.10.1 You have your interface assignments mismatched...Reconfigure and test

I think instead of selecting the users mailbox then the advanced tab and changing the server name in the home server box you may want to try "moving" the mailbox. Highlight the mailbox you want to move then go to tools and select "move mailbox". Then select the destination...

Are you using Active Directory or a flat NT4 domain?

As soon as you install Exchange 5.5 on W2K, with the intermet mail services, it requires you to use a fully qualified domain name instead of using a plain old Netbios name. The communication (RPC) is getting broken from the NT4 server to the W2K server and the way to resolve it is to either...