Exchange 5.5 Std Edition to Windows 2003?

Similar Threads:

1.SBS 4.0 to Windows 2003 Std Edition and Exchange 2003

I have a client still running SBS 4.0 with Exchange 5.5 on an old Dell
server.

I also have a new Dell server, Windows 2003 Standard Edition and
Exchange 2003 Standard Edition.

What would be the least painful way to move the existing SBS
environment over to the new server with Windows 2003 and Exchange 2003
whilst preserving the email data, user accounts and data shares?

My main concern is to avoid having to go around around to each user's
desktop and re-configuring outlook and mapped network drives etc.

Thanks,

Raj.

2.Force Apply of Mailbox Settings (Exchange 5.5 Std Edition)

I have change mailbox's primary user account to a user and it takes a long
time before it identifies from the workstation side. For example, I have
userA is viewing MailboxA. Then after a time, I want userB to view MailboxA
by changing the Primary User Account of his Mailbox. I have check userB if
he can view it but there is an error, permission not allowed. I have restart
the userB's computer but it didn't work also. I have experience this before
but what I did is I only wait for the time that it takes effect. Can I force
apply the settings immediately?

Hoping for your response.

Mark

3.Exchange 5.5 with Windows Server 2003 Std. Ed.

4.Outlook 2003 (Cached mode) / Exchange 2003 Enterprise (Win 2003 Std Edition)

Keep getting this machine periodically in Outlook:

Outlook Send/Receive Progress


Task 'Microsoft Exchange Server - Receiving' reported error (0x8004010F) : 
'The operation failed. An object could not be found.'

Any ideas?

TIA 

5.Outlook 2003 / Windows XP Tablet Edition / Exchange 5.5

Hi all,

I'm setting up new Tablet PCs for deployment within our IT section.  All
these machines have both 10/100 and 802.11g nics installed.  Here's the
software load set -

    Windows XP Tablet Edition
    MS Office 2003, including Outlook 2003
    Norton AntiVirus Corp Edition

The subnet we are connected to is behind a firewall, and uses NAT/PAT to
access the outside world.  Our Exchange 5.5 Server (let's call it
MAIL_SERVER) is inside the firewall, and just like the other servers, is set
up with a static NAT path to it thru the firewall.

We are using the NT40 Domain model.  Our subnet uses DHCP and WINS, no
internal DNS. Our DHCP Server hands out the addresses of DNS Servers outside
the firewall.  The MAIL_SERVER is registered in WINS.

When I try to create a new mail profile in Outlook 2003, I see some strange
things happening when I click the Check Name button.  I enter the server
name (MAIL_SERVER) and the user name.  Then when I click the button, I get
an hourglass cursor for quite a while (over 90 seconds) then the server name
and user name become underlined, except the server name has changed to
MAIL_SERVER.domain.name.com.

If I put the numeric IP address (inside address) of the server, it changes
to MAIL_SERVER.domain.name.com after resolution.

If I open a command prompt window and ping MAIL_SERVER, I get a appropriate
response, with the inside IP address.  This tells me that the name is being
resolved thru WINS.

Further confusing me is the fact that on the Tablet PC assigned to me, when
I logged onto the domain for the first time, my roaming profile was copied
down to the Tablet, and when I first fired up Outlook 2003, it connected
with no apparent delay.  If I look at my Outlook profile, it shows
MAIL_SERVER without the domain suffix as the server name.  If I try to set
up another profile on this machine, it adds the domain suffix.

I de-installed Outlook 2003 and installed Outlook 2002 (XP) in its place.
The problem does NOT exist in Outlook 2002.  I was able to add a new profile
(let's call it profile1), and there was no appreciable delay in the name
resolution, the server name came up as MAIL_SERVER.

I then de-installed Outlook 2002 and re-installed Outlook 2003.  I then
opened Outlook 2003, and it connected to MAIL_SERVER with no appreciable
delay.  I checked the profile properties, and the server name was shown as
MAIL_SERVER (without the domain suffix).  I closed Outlook and tried to add
another profile.  The delay was there again, and when the name resolved the
server name had the domain suffix on it again.

Does anyone have any idea why Outlook 2003 is doing this?

Thanks in advance.

6. FIXED - Outlook 2003 / Windows XP Tablet Edition / Exchange 5.5

7. Exchange 5.5 on Windows 2003 Enterprise Edition

8. Upgrade exchange 2003 beta to 2003 Std edition