Yeah the back and forth is going to hurt. Robocopy is date/time aware and won't copy current files again.
Cheers. From: Sean Martin [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 16, 2008 10:39 AM To: NT System Admin Issues Subject: Re: Citrix farm issue I created logon/logoff scripts for a couple of applications that saved user specific settings under the 'local settings' directory in the user profile. I copy the data from the Citrix server to their home directory at logoff and then copy it back to server when they logon. This could obviously impact user logon depending on how much data we're talking about... - Sean On Tue, Sep 16, 2008 at 7:26 AM, lists <[EMAIL PROTECTED]> wrote: Robocopy is pretty polite on the WAN. I use it for similar purposes keeping roaming folks scans folders current and such. Use a scheduler to run it every 15 minnows and forget about it. Cheers. From: James Rankin [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 16, 2008 8:20 AM To: NT System Admin Issues Subject: Re: Citrix farm issue I am just thinking down the redirection line now, however this software appears to be hard-coded to write to the c: drive. Unless - I have just discovered (after getting no response from application support) that this software uses .ini files to get its file locations. There are 30 ini files on every server (!). if I can figure out how these things are supposed to interact, maybe I can fathom out how to make it play... 2008/9/16 <[EMAIL PROTECTED]> "James Rankin" <[EMAIL PROTECTED]> wrote on 09/16/2008 08:42:44 AM: > That would mean running a robocopy job from one server to 21 > destinations every time a user logs off, all day while people are > trying to work. I could do that, but I was hoping for something a > little more elegant... :-) Re-directed folders? If the app will always save to a specific location, and you can have that location set to the user's home folder as set by AD, that should solve that problem, yes? For example, we set drive Z: to be the user's home folder, which is on a SAN share. And so if the app will always write to drive Z:, won't the user always have access to that drive, even while executing the app? There must be something more to this that I am not seeing. :-) And we're doing the exact same thing - rolling out public housing software via Citrix environment, but perhaps not the same software ... > 2008/9/16 lists <[EMAIL PROTECTED]> > Brute force method... > Use Robocopy to copy everything everywhere everyday. > > Cheers. > > From: James Rankin [mailto:[EMAIL PROTECTED] > Sent: Tuesday, September 16, 2008 7:35 AM > To: NT System Admin Issues > Subject: Citrix farm issue > > I have a farm of 22 identical cloned Citrix servers. Onto said > servers, the powers-that-be have decided that we will have a new > housing system deployed. This decision was taken before I started, > so there's no getting away from it. Now, unfortunately, this POS > housing system stores its reports on the client (i.e. when a user > changes a report, a file is updated in the reports folder on the > Citrix server, not the back-end database server). However, the user > could log on to any one of 22 servers the next day, so we need a > mechanism for replicating his/her changes across the farm. This also > needs to be intelligent enough to get around the fact that we may > have multiple users accessing the same server and possibly making > changes to the same reports, then logging off independently of each other. > > I first thought of DFS, but sitting and thinking about it this > doesn't really seem suitable. Does anyone know of any solution that > might help me out here? The less hands-off the better :-) > > TIA, > > > > JRR > > > > > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
