RE: Palm Sync to Terminal Server Session

Tech-Archive recommends: Speed Up your PC by fixing your registry

For an office with less than 76 users, Small Business Server 2003 is the best
way to get Exchange 2003. Ideally you'd have a Dual Processor or Dual CPU
Server with 2 SCSI disks configured at RAID1 and 4GB RAM. If money is not an
object I'd have the OS on one RAID1 Array, Exchange DBs on another and log
files on a third. It can definitely run with more modest hardware, but the
cost difference between the two would not be too much.

HP offers hardware discounts for 501(c)3 non-profit organizations. You
might also want to check with techsoup.org, as you may be able to get the
software for nothing from them.

How many users do you need to support.

--
Patrick C. Rouse
Microsoft MVP - Terminal Server
Provision Networks VIP
Citrix Technology Professional
President - Session Computing Solutions, LLC
http://www.sessioncomputing.com



"MattShell" wrote:

Which is very true and I am looking forward to trying it, however the thing
that is not cheap is the hardware that it takes to run exchange. Unless
Microsoft has a hardware donation program as well ;) Although now that I
think of it, what would you recommend running exchange with? Because maybe I
have this idea of what it needs and it really doesn't.

Matt

"Patrick Rouse" wrote:

The good thing is that 501(c)3 non-profit organizations get MSFT liceses for
next to nothing. I think the Exchange CALs are something rediculous like $6.
--
Patrick C. Rouse
Microsoft MVP - Terminal Server
Provision Networks VIP
Citrix Technology Professional
President - Session Computing Solutions, LLC
http://www.sessioncomputing.com



"MattShell" wrote:

Thanks for your informative reply. We have though about going with an
exchange server but have been held back by the cost of a new server at this
time. (I work for a non-profit camp, so what little cash there is, is used
pretty conservativly). Look foward to more time on the boards with you Paul.

Matt

"Patrick Rouse" wrote:

I've been managing Exchange Servers since 1999 and I'm a big fan of its'
information stores. The list of reasons why it's better than PST is pretty
long, but includes:

1. Multi-user/instance access to each mailbox
2. Secure Remote Access via Outlook Web Access and Outlook Mobile Access
3. Mailbox Recovery
4. Deleted item retention and recovery via the Outlook Client
5. Single Instance Storage, i.e. a 5MB PPT attachment send to 100 users on
the same Exchange Server uses about 5MB of storage, whereas with PST it uses
500MB.
6. Reduced bandwidth usage. A 5MB PPT attachment sent to 100 users (from
the Internet) consumes 40Mb of bandwidth, whereas with POP email and PST it
consumes 4000Mb of bandwidth (as it needs to be delivered individually to
each client, instead of just to the Exchange Server)
7. PST is not supported on network storage.


Search google for PST=BAD

--
Patrick C. Rouse
Microsoft MVP - Terminal Server
Provision Networks VIP
Citrix Technology Professional
President - Session Computing Solutions, LLC
http://www.sessioncomputing.com



"MattShell" wrote:

Patrick,

Not to debate you further, and especially because you are helping me in
other threads so I don't want to burn bridges but you made some points that I
wonder about.

1. A local install of Outlook - yeah you do have to install it locally but
when you are talking about 1 user or in my case 3 users, who cares? If I had
to sync 100 palms, I am still not sure I would care, but I can understand the
want to sync USB

2. Users that have to follow directions. Not really, not any more than
they did when the "sunk" their palm in the first place. Except for close
Outlook on the Remote machine, and if they cannot do that, I bet they have
more problems than sync not working

3. Logical Network Connectivity between the client and server, i.e. VPN.
yep, as I stated as well, this is a limitation. But to keep their USB ports
off the server and not have to install another piece of software to the
server, I say it is worth not having the remote sync. Although if I had 25
sales employees on the road, I might feel different, although I probably
would not run them through TS anyway.

How would you recommend keeping our mailbox store and why? And I know this
probably goes better in another group, but I know where to find you here :)

Matt

"Patrick Rouse" wrote:

This, although is working, is a solution that does not scale very well as you
need:

1. A local install of Outlook
2. Users that know how to follow directions
3. Logical Network Connectivity between the client and server, i.e. VPN.

The solution I mentioned would allow an end user to sync with the terminal
server install of Outlook, as it redirects to the client's local USB Ports.

I am glad to hear that you found a work around for your situation.

P.S. I wouldn't recommend using PST as your primary mailbox store in a
corporate environment.

--
Patrick C. Rouse
Microsoft MVP - Terminal Server
Provision Networks VIP
Citrix Technology Professional
President - Session Computing Solutions, LLC
http://www.sessioncomputing.com



"MattShell" wrote:

David,

I still hope you are checking this because I had this problem with three
users and now have it fixed, and it requires no special application to get
the job done. We currently sync with two Palm 700p's and a ZX100 (I think
that is the name)

So here are the requirements:
Outlook 2003 or Outlook 2007
The user uses the same machine to sycn their Palm device to their data

So how does this work you ask?
1. Install Outlook 2003 on the local machine that the user uses for RDP
2. Find the user's PST file on the Terminal Server and share the folder to
the network with the appropriate permisions.
3. Open Outlook 2003 on the local machine and go into the following menu
File -> Data File Managment. Tell it you want to Add a new Data file and
point it to the shared PST.
4. Close Outlook on the local machine.
5. Re-open Outlook on the local machine and go back into the File -> Data
File Managment menu. Once here tell it you want to change the default data
file to the new share file and then delete the old date file.

Now the local outlook which sycns to his palm syncs to his remote pst file.
Here are the things you need to keep in mind.

1. As stated you have to use the same machine to sync.
2. If you are not on the local network it might be really slow
3. You must shut down Outlook on the remote machine in order to sync on the
local machine as Outlook cannot open the PST file when another outlook has it
open. Strange errros will occur.

Let me know if you need any help beyond this.

Matt


"Patrick Rouse" wrote:

TS only natively supports Palm Sync via Serial Port Redirection. If you need
to sync via USB, you'd need to use software like USB-IT from Provision
Networks. If that's something you're interested in learning more about, you
may contact me via my website.


--
Patrick C. Rouse
Microsoft MVP - Terminal Server
Provision Networks VIP
Citrix Technology Professional
President - Session Computing Solutions, LLC
http://www.sessioncomputing.com



"David G. Hoch" wrote:

I'm installing a Windows 2003 Terminal Server that will be used to provide
thin client sessions to all users.
One user has a Palm Pilot that they need to synchronize with MS Outlook. Is
there a way to be able to sync the Palm Pilot with MS Outlook running in a
Thin Client session?

My goal is to move most of the users to Thin Client Terminals rather than
PC's running an RDP client, but if that makes a difference for this one user
I can give them whatever makes the most sense.

Thanks for your input.
--David



.

Relevant Pages

  • Re: Critical e-mail problem.
    ... I upgraded from Win2K Server to WinSBS2003 on my desktop ... of my POP3 e-mail accounts as an Exchange Server account. ... I found that I was only receiving mail from the Exchange ... your Outlook profile will have Exchange as its default (and this ...
    (microsoft.public.windows.server.sbs)
  • Re: Critical e-mail problem.
    ... I upgraded from Win2K Server to WinSBS2003 on my desktop ... of my POP3 e-mail accounts as an Exchange Server account. ... I found that I was only receiving mail from the Exchange ... your Outlook profile will have Exchange as its default (and this ...
    (microsoft.public.windows.server.sbs)
  • Re: Faxe per Email über Outlook-2003
    ... Der Exchange Server ist ein Groupware- und Messaging-System der Firma ... Microsoft Exchange Server benutzt ein proprietäres RPC Protokoll namens ... Microsoft Office Outlook Web Access ...
    (microsoft.public.de.outlook)
  • Re: Outlook2003 POP3-IMAP Exchange | Confused!?
    ... exchange and sharepoint not being used. ... Folder Re-Direction and roaming profiles. ... with Outlook 2003 as the preferred choice of email client. ... registry to point to the server. ...
    (microsoft.public.windows.server.sbs)
  • Re: Offline Files -- & -- Migration Strategy
    ... Happy to help - IMO Exchange Server and Outlook are why offices need ... Exchange won't use Net Folders, and you probably won't have calendar ... messages from your PST into your server mailbox. ...
    (microsoft.public.windows.server.sbs)