M
Mark Landin
OK you are probably thinking "We've answered this a hundred times
already", but I think my case is slightly different.
We have recently switched from Outlook 2000 to Outlook 2003 on our
Terminal Servers. We used to use newprof to create the user's Outlook
2000 profile for them. The users would never actually launch Outlook
themselves .. it was invoked via a MAPI call from Crystal Reports when
the exported a report to a mail recipient. The user was always running
from a published application so they never saw an Outlook icon, etc.
I know newprof does not work for creating Outlook 2003 profiles. My
understanding is that the CIW provides some of this functionality, in
that it can create a user profile for each user based on some default
settings.
My problem is that this does NOT create a profile like newprof did.
Outlook 2000 was completely ready to use once newprof was done. Not so
with Outlook 2003 ... there is still some "setup" that is done the
first time the user opens Outlook 2003 even if a profile has been
auto-created with CIW (or profiler or createprf or any of the other
tools I've tried out).
In our case, this setup that has to be done causes Crystal Reports to
just "hang" because it's waiting for a MAPI session to be created, but
it can't be because Outlook 2003 doesn't have a complete user profile
created for this user yet, and the user has no real opportunity to
complete these setup steps because they don't ever run Outlook
directly on the Terminal Servers.
How can I resolve this?
already", but I think my case is slightly different.
We have recently switched from Outlook 2000 to Outlook 2003 on our
Terminal Servers. We used to use newprof to create the user's Outlook
2000 profile for them. The users would never actually launch Outlook
themselves .. it was invoked via a MAPI call from Crystal Reports when
the exported a report to a mail recipient. The user was always running
from a published application so they never saw an Outlook icon, etc.
I know newprof does not work for creating Outlook 2003 profiles. My
understanding is that the CIW provides some of this functionality, in
that it can create a user profile for each user based on some default
settings.
My problem is that this does NOT create a profile like newprof did.
Outlook 2000 was completely ready to use once newprof was done. Not so
with Outlook 2003 ... there is still some "setup" that is done the
first time the user opens Outlook 2003 even if a profile has been
auto-created with CIW (or profiler or createprf or any of the other
tools I've tried out).
In our case, this setup that has to be done causes Crystal Reports to
just "hang" because it's waiting for a MAPI session to be created, but
it can't be because Outlook 2003 doesn't have a complete user profile
created for this user yet, and the user has no real opportunity to
complete these setup steps because they don't ever run Outlook
directly on the Terminal Servers.
How can I resolve this?