bb.donnay-software.com

Roger,

Just looking for a recommendation. We do updates weekly at a large customer, who has 100+ users across the nation using their remote server. We have been doing this with no issues on normal NON client server by closing files using computer management (when only a very users are working. No method to contact) and rebooting the remote server and updating the dll files.
With ADS should the ADS server just be shut down to close files,and then follow the other steps for the update. Do not want to damage any files, which has never occurred.

For this client, they also do something similar every night for their backup, they shut down the data server and disconnect users at 2am.

Going on ADS Monday.


Thanks

Fred
Omni

Hey Fred,

Use the remote server option in the ADS Architect.
You can see who is using the software and what files they are using and locking.
You can clear all connections from there.

However, I'm confused as to why you need to shut down in order to backup.
I have several clients with different software and we do not need to shut down anyone in order to backup or update DLL's.

We should talk next time we get together.

Bobby

Hi Bobby,

SbDrakos wrote: I have several clients with different software and we do not need to shut down anyone in order to backup or update DLL's.

Updating DLL's when they are in use? Are you sure about this? I never succeeded to do that. No problem to backup files when they are in use, but never succeeded to replace DLL files when someone still was using the software. Since dclipx.dll is sometimes part of our updates, this would be a nice to have.

Hi Chris,

We use a very simple routine that renames all the files by adding the date.
In other words, medallion.exe becomes medallion.exe.20160930, medallion.dll becomes medallion.dll.20160930, etc.
Then the current files are copied to the server.

The next time the user logs in, they get the updated files.

So far this has worked for cases where the files are downloaded into the local directory and in cases where the users connect via RDP.

Of course we have to go in every so often and purge some of the older files, but it has an advantage as well.
We have a routine that renames the current files and restores the previous version in case we need to revert to an older version.

Bobby