I belive that the timeouts are long enough to handle that. I haven't seen that as a problem anyway, but our WAN connectivity here in the states is quite good and we keep all the profiles within that WAN. _____ From: Steve Greenberg [mailto:steveg@xxxxxxxxxxxxxx] Sent: Saturday, September 06, 2003 10:01 AM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: DFS and Profiles One problem though is that if the profiles are huge, or scattered across a WAN or busy LAN, isn't there a potential problem with timeouts leading the client to get halfway through the profile download or upload and then having to re-poll the DFS tree? If it has to start the process over, or continue it this could glitch the profile process, or, what if the client is then re-directed to a different version of the profile on a different store? the other thing you mentioned is that you use a NetApp, which I also put in my frist reply. I am not sure that DFS is as elegant or reliable when using NT file servers..... Steve Greenberg Thin Client Computing 34522 N. Scottsdale Rd. suite D8453 Scottsdale, AZ 85262 (602) 432-8649 (602) 296-0411 fax steveg@xxxxxxxxxxxxxx -----Original Message----- From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Nail, Larry Sent: Friday, September 05, 2003 10:42 PM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: DFS and Profiles If you're talking about Microsoft's Distributed File system, I've heard that comment before about DFS & user profiles... it's a bunch of baloney. DFS is a file system redirector... you connect to the tree, the tree tells you which server to connect to & its out of the story. The only communications back to the DFS tree are when your SMB session state times out or the file share becomes unavailable. I don't remember how long the session time out it is, but its a pretty good amount of time. If your SMB session state times out, the client goes back to the DFS tree, asks again which server do I connect to & starts over. If a server connection dies, it goes back to the tree after it's complete with it's retry routine, and asks the tree for the next server sharing that DFS leaf (incase you're using a DFS leaf against multiple servers). I've been using DFS against a Netapp 860 cluster with 8000+ shares (& a 760 before that)... close to 2000 of them are WTS profiles... never, ever heard a peap. In fact because of DFS, I've moved data from one volume on the pair to another volume on the partner & with ZERO downtime... thank you SnapMirror & DFS. My humble opinion is to fire away... DFS is just a redirector... _____ From: Joe shonk [mailto:jshonk_dhl@xxxxxxxxx] Sent: Friday, September 05, 2003 11:43 AM To: thin@xxxxxxxxxxxxx Subject: [THIN] DFS and Profiles I've been doing some research on using a DFS Share to store user profiles. From what I understand, it is generally not recommended to store profiles on a DFS as DFS was not designed to handle it. Also, there are examples of systems that are currently using DFS to store profiles. However, I cannot find any concrete information that supports one theory over another. Does anyone know of any white papers, faq, anything that might be of help? Joe _____ Do you Yahoo!? Yahoo! SiteBuilder <http://us.rd.yahoo.com/evt=10469/*http://sitebuilder.yahoo.com> - Free, easy-to-use web site design software