Re: Outlook client on SBS 2003 server by Jim
Jim
Wed Feb 11 09:09:06 CST 2004
You can always vpn into the server, yes? If so then you can set up an
account on the machine you are vpning from that will let you open a
full session of Outlook. You can even open up the administrator's
Exchange account from the vpn connection.
"Joseph Welna" <jbwelna@sprynet.com> wrote:
>Dear Ken,
>
>I think you guys misunderstood me. I wasn't interested in running the
>server as a ws. My interest in installing Outlook on the server was to gain
>access from the server console to some of the public folder
>manipulation/properties that OWA lacks. External email is of no
>consideration and wouldn't even be used. I understand I can log into server
>from a ws as administrator and gain access to the administrator mailbox with
>correct rights. However, I do not always have a workstation available
>remotely, whereas a server is always available remotely.
>
>Thank you very much for helping with my question.
>
>
>Joe Welna
>
>
>----- Original Message -----
>From: "Kevin Weilbacher" <kweilbacMVP@gte.net>
>Newsgroups: microsoft.public.backoffice.smallbiz2000
>Sent: Tuesday, February 10, 2004 4:54 PM
>Subject: Re: Outlook client on SBS 2003 server
>
>
>> Joe, the basic rule of thumb is: don't use your server as a workstation.
>>
>> To that end, you would not and should not install Outllok as a client on
>the
>> server. Golly, OWA is so nice in 2003, that if you really and truly needed
>> to see your email from the server, you could open up IE and get it. But,
>> even that is considered off-limit by network vulnerability purists.
>>
>> --
>> Kevin Weilbacher [SBS-MVP]
>> "The days pass by so quickly now, the nights are seldom long"
>>
>>
>>
>> "Joseph Welna" <jbwelna@sprynet.com> wrote in message
>> news:%23VIo78A8DHA.2480@TK2MSFTNGP10.phx.gbl...
>> > I am wondering if it is safe to run an Outlook client on an SBS2003
>server
>> > if I implement dll/com redirection. Despite the warning when you start
>> > Outlook, Q articles on MS web site seem to indicate that you simply need
>> to
>> > copy mapi32.dll to the same directory as outlook.exe and create a blank
>> file
>> > called outlook.exe.local. Any thoughts on this? If my rational is
>correct,
>> > what about mapisvc.inf? Would a matching copy of that file need to
>reside
>> in
>> > the same directories as mapi32.dll?
>> >
>> > Thanks for any help,
>> >
>> >
>> > Joe Welna
>> >
>> >
>>
>>
>
>"Kevin Weilbacher" <kweilbacMVP@gte.net> wrote in message
>news:ujhcHCC8DHA.2404@TK2MSFTNGP11.phx.gbl...
>> Joe, the basic rule of thumb is: don't use your server as a workstation.
>>
>> To that end, you would not and should not install Outllok as a client on
>the
>> server. Golly, OWA is so nice in 2003, that if you really and truly needed
>> to see your email from the server, you could open up IE and get it. But,
>> even that is considered off-limit by network vulnerability purists.
>>
>> --
>> Kevin Weilbacher [SBS-MVP]
>> "The days pass by so quickly now, the nights are seldom long"
>>
>>
>>
>> "Joseph Welna" <jbwelna@sprynet.com> wrote in message
>> news:%23VIo78A8DHA.2480@TK2MSFTNGP10.phx.gbl...
>> > I am wondering if it is safe to run an Outlook client on an SBS2003
>server
>> > if I implement dll/com redirection. Despite the warning when you start
>> > Outlook, Q articles on MS web site seem to indicate that you simply need
>> to
>> > copy mapi32.dll to the same directory as outlook.exe and create a blank
>> file
>> > called outlook.exe.local. Any thoughts on this? If my rational is
>correct,
>> > what about mapisvc.inf? Would a matching copy of that file need to
>reside
>> in
>> > the same directories as mapi32.dll?
>> >
>> > Thanks for any help,
>> >
>> >
>> > Joe Welna
>> >
>> >
>>
>>
>
Jim B. SBS MVP
remove the mvp to send email