• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Synchronizing files ONCE on an ActiveDirectory network.

EyeMWing

Banned
This particular application is to synchronize Counterstrike maps between machines, basically just copy a filesystem folder to every system.

Can't find anything in Group Policy that would allow me to do it (unless I went through the arduous process of making an MSI every week or so, and since Counterstrike is NOT our primary task, I'd prefer not to waste time on that when I should be streamlining and debugging our other, more important functions)

The reason behind doing this is that our normal user accounts do not have the NTFS permissions to write to the Steam directory (which is desired in our situation, because we've had issues in the past).

I tried using the SysInternals PSEXEC util to xcopy from a network share to every machine, but it just so happens that only the machine I initially did my testing on will xcopy from an unmounted network share. The rest whine about invalid arguments (this is REALLY odd, since they're all WinXP Pro SP2, and theoretically, should have the same version of xcopy, unless the administration tools updated xcopy)

I suppose I could mount drives through psexec and then perform the xcopy, but as I was contemplating doing that, I decided that there must be a better way.

Thoughts?
 
Also, offline files is not an option, because I don't want the remote systems to be able to write back to the shared copy.
 
Originally posted by: EyeMWing
Also, offline files is not an option, because I don't want the remote systems to be able to write back to the shared copy.

Why not use offline files and take away from the users on the remote systems the write, modify and full control permissions on the shared folder.
 
Originally posted by: nukexbi
Originally posted by: EyeMWing
Also, offline files is not an option, because I don't want the remote systems to be able to write back to the shared copy.

Why not use offline files and take away from the users on the remote systems the write, modify and full control permissions on the shared folder.

Because the second an administrator logs into the client system... Write-back would be inevitable. We would like to avoid having to lock the administrators from being able to write-back from a remote system, since the sync source is a headless fileserver, and remoting into these systems is a tricky task (despite the fact that they're 6-way PPros with 2 gigs of RAM each, it takes just about FOREVER to accomplish under 2k Server)
 
Originally posted by: Rilex
Robocopy? It does do a one-way mirror.

Robocopy + psexec looks like the best choice. Just need to deploy the resource kit network-wide first. Will work on that Monday mornin'.
 
Back
Top