Yeah, it would be much easier like that, I've thought of that option before. ;-)

Bandwith isn't that much an issue... however with over 5000 users, mass amounts of open sessions on a server causes problems with the server.

Open sessions on the server often remain, even after the program has stopped running. So you end up with a bunch of workstations connected to your servers, not doing anything, but not letting other workstations do anything either. Some times clearing the sessions will fix it, some times you have to reboot.

I had a small one-way messaging program being run off of a file server on each workstation via login script once. After the program was loaded into memory, the workstations weren't releasing there sessions on the file share. There was no reason the sessions should be kept open, and not every workstation kept them open, but enough of them did to keep crashing it. Ended up having to copy the program to each workstation, instead of running it off the server.

Probably wouldn't be a problem in a smaller environment.

Wasn't very fun.

quote:

Or, depending on how fast your network is, don't even bother copying the executable to the clients. Just dump everything into the NETLOGON share. Then you don't have to worry whether a client has an incorrect version, no Kixtart at all, or whether somebody tries to break the login script. Granted it adds about 300k of traffic for each user, but, unless you're using dial-up or ISDN, you shoudl eb fine with this. It will also make verison control easier.

The FAQ Forum contains multiple threads about this.

--------------------
Jens