But now that nice laptop you use to do your work on a plane or when you are offline is just a terminal, and you have no offline mail or anything....
I'm not saying TS doesn't have its place, I'm just mentioning that for someone who is used to taking their office with them may not appreciate those changes. -----Original Message----- From: Andy David [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 26, 2003 4:49 AM To: Exchange Discussions Subject: Re: Port 135 and Exchange Issue >From within Citrix, its simply a matter of copying over the file you need to work on to your local drive on the laptop. ----- Original Message ----- From: "Chris Scharff" <[EMAIL PROTECTED]> To: "Exchange Discussions" <[EMAIL PROTECTED]> Sent: Monday, August 25, 2003 10:11 PM Subject: Re: Port 135 and Exchange Issue > Makes laptop use a little tough though. > > > From: "Hague, Jeff" <[EMAIL PROTECTED]> > > Reply-To: "Exchange Discussions" <[EMAIL PROTECTED]> > > Date: Mon, 25 Aug 2003 11:23:15 -0400 > > To: "Exchange Discussions" <[EMAIL PROTECTED]> > > Subject: RE: Port 135 and Exchange Issue > > > > Definitely more costly but it really works well. The setup and configuration > > aspects alone (client-side anyway) are much simpler and the performance is > > probably much better than a straight VPN solution. I think if you look it at > > all the factors there is a positive "ROI". > > > > Jeff > > > > -----Original Message----- > > From: Martin Blackstone [mailto:[EMAIL PROTECTED] > > Sent: Sunday, August 24, 2003 9:43 PM > > To: Exchange Discussions > > Subject: RE: Port 135 and Exchange Issue > > > > > > That's certainly an option, but a much more costly one IMHO. > > > > > > > > -----Original Message----- > > From: Hague, Jeff [mailto:[EMAIL PROTECTED] > > Sent: Sunday, August 24, 2003 5:43 PM > > To: Exchange Discussions > > Subject: RE: Port 135 and Exchange Issue > > > > Have you considered Terminal Server or (better yet) Citrix? This works > > wonders for us - full Outlook & Exchange as well as all the other apps we > > run. We only have a dozen or so users so far but my understanding is that > > Terminal by itself on one decent server (dual Xeon 2.0GHz/1.5GB RAM) is fine > > for 20 or so clients simultaneously. Beyond that, Citrix on top of Terminal > > is the way to go. Citrix also provides better support for local printers, > > sound cards, etc plus a host of additional functionality. Either 1 requires > > only a single port through the firewall which hasnt been blocked by any ISPs > > (yet?) and the traffic is already encrypted although I dont imagine its as > > "tight" as most VPN solutions. The other thing we found so convenient is the > > "Advanced" Terminal client which is simply a web page that loads the client > > software through an ActiveX control in an IE session. The directions to get > > our clients set up was litterally "go to wwww.whatever.com and follow the > > instructions". There is some work to do getting the apps set up properly but > > common apps like Outlook, Word and Excel are very well documented. Getting > > our custom apps running wasnt near as difficult as I had expected either. > > The big trick for us is handling profiles because some of our clients can > > not have access to certain apps that other clients need so we had to modify > > some profiles manually but with so few clients it hasnt been a big deal. > > > > Jeff Hague > > MCSE > > Network Manager > > Randolph-Macon College > > Ashland, VA > > > > > > -----Original Message----- > > From: Hank [mailto:[EMAIL PROTECTED] > > Sent: Sunday, August 24, 2003 3:18 PM > > To: Exchange Discussions > > Subject: Port 135 and Exchange Issue > > > > > > We are trying to recover from ISPs closing down port 135. We have an > > dedicated Exchange Server at a hosting company. 20 of our 23 people > > scattered around the country can not use the full functionality of > > Outlook/Exchange because of this problem. > > > > We are a classic case study of how a company has suceeded in business by > > using most of the functionality of Outlook/Exchange. We built our 3 year > > old company's communications, task management, and database using the > > Exchange Platform, including extensive use of custom 'forms' that track > > hundreds of tasks and our workflow. > > > > The ISP's closing out port 135 has brought us to our knees. We are > > scambling just trying to stay on schedule with our committments to our > > clients. > > > > I have no hope that the ISPs will turn open up 135 again, so I also need an > > alternative way to connect to the *full* functionality we had before, or be > > forced to migrate completely off exchange and rebuild our entire > > infrastructure using another platform. > > > > We have tried to implement a VPN solution, but now realize that unless we > > run the connection on our client and have a full internet connection at the > > same time, this will not work for us. We do not know how to do this. We > > must have full access to the internet and exchange at the same time because > > of the nature of our service we provide. > > > > Any ideas? > > > > Regards, > > Hank > > > _________________________________________________________________ > List posting FAQ: http://www.swinc.com/resource/exch_faq.htm > Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang =english > To unsubscribe: mailto:[EMAIL PROTECTED] > Exchange List admin: [EMAIL PROTECTED] > _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang =english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED]
