M
Marc Michaels
Is the initial OL2K3 client configuration to connect via RPC-HTTP
extremely slow for everyone? Or is it just me (my server)? I'm using
XPSP2 and Office 2K3 SP1 by the way. I'm not on the LAN, I am
configuring the client over the internet with NO VPN connection.
Here are the steps I follow with bottlenecks identified.
A. Create a new profile
B. Select Add New email account
C. Select Exchange Server
D. type my server name and user name (I DO NOT CLICK CHECK NAME HERE)
E. Click "More Settings"
********5-6 MINUTE BOTTLENECK/FREEZE HERE********
F. Error pops up saying Outlook could not log on (obviously, since I
haven't authenticated or set up the proxy addresses yet).
G. Configure the "Connect to my Exchange mailbox using HTTP" proxy
settings (https://mymail.mydomain.com, Connect using SSL only, On fast
is checked, On slow is checked, Basic Authentication is selected).
H. Click OK
I. Now I click "Check Name"
*******3-4 MINUTE BOTTLENECK/FREEZE HERE********
J. Name eventually checks out/verifies ok. Exchange server address is
converted to an internal name (ie. MYSERVER.mylandomain.local).
K. Click Next
*******HUGE BOTTLE NECK HERE!!!! 10 MINUTES!!!********
L. Get the congratulatory screen.
M. Wipe the sweat off of my head.
N. Tell wife I'll be in bed soon (10 minutes tops)
O. Down a quick beer in celebration of finally getting the client
configured.
P. Brush teeth so wife doesn't smell beer.
Q. Go to bed...wife is out cold.
I guess this process is bearable. However, I don't think my
coworkers/clients will be very tolerant of a 30 minute configuration
procedure (longer if they don't know much of what they're doing).
Can anyone find anything that I may be missing?
Marc
extremely slow for everyone? Or is it just me (my server)? I'm using
XPSP2 and Office 2K3 SP1 by the way. I'm not on the LAN, I am
configuring the client over the internet with NO VPN connection.
Here are the steps I follow with bottlenecks identified.
A. Create a new profile
B. Select Add New email account
C. Select Exchange Server
D. type my server name and user name (I DO NOT CLICK CHECK NAME HERE)
E. Click "More Settings"
********5-6 MINUTE BOTTLENECK/FREEZE HERE********
F. Error pops up saying Outlook could not log on (obviously, since I
haven't authenticated or set up the proxy addresses yet).
G. Configure the "Connect to my Exchange mailbox using HTTP" proxy
settings (https://mymail.mydomain.com, Connect using SSL only, On fast
is checked, On slow is checked, Basic Authentication is selected).
H. Click OK
I. Now I click "Check Name"
*******3-4 MINUTE BOTTLENECK/FREEZE HERE********
J. Name eventually checks out/verifies ok. Exchange server address is
converted to an internal name (ie. MYSERVER.mylandomain.local).
K. Click Next
*******HUGE BOTTLE NECK HERE!!!! 10 MINUTES!!!********
L. Get the congratulatory screen.
M. Wipe the sweat off of my head.
N. Tell wife I'll be in bed soon (10 minutes tops)
O. Down a quick beer in celebration of finally getting the client
configured.
P. Brush teeth so wife doesn't smell beer.
Q. Go to bed...wife is out cold.
I guess this process is bearable. However, I don't think my
coworkers/clients will be very tolerant of a 30 minute configuration
procedure (longer if they don't know much of what they're doing).
Can anyone find anything that I may be missing?
Marc