Radia deployment of an MSI changing date/time stamp
My company, at present, time is using a product called Radia that was originally owned by Novadigm, but is now owned by Hewlet Packard. Before it was sold, Novadigm aquired a company called WALLS, an MSI creation tool, and incorporated it into their product. That they're using Radia is not something I can control, so I'm stuck with this product which works...most of the time.
Now that I have that out of the way and hopefull don't get the, "Switch Products," response, here's the problem:
When Radia deploys an MSI it attaches a date/time stamp to all files that is actually the date and time the application was deployed down, rather than what they actually are. The work around is attaching a /T (capital T there) to the deployment command line which goes and verifies every single file and resets their date/time back to what it was originally. This is a bit of a resource hit on larger applications.
My question is, does anyone know of any way to allow the MSI itself to verify the date/time on certain files and keep them the same? Note these files are database files, which are then updateable by outside applications, and cannot be 'healed' by the MSI's self repair feature either.
Now that I have that out of the way and hopefull don't get the, "Switch Products," response, here's the problem:
When Radia deploys an MSI it attaches a date/time stamp to all files that is actually the date and time the application was deployed down, rather than what they actually are. The work around is attaching a /T (capital T there) to the deployment command line which goes and verifies every single file and resets their date/time back to what it was originally. This is a bit of a resource hit on larger applications.
My question is, does anyone know of any way to allow the MSI itself to verify the date/time on certain files and keep them the same? Note these files are database files, which are then updateable by outside applications, and cannot be 'healed' by the MSI's self repair feature either.
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
Radia709
18 years ago
Unfortunately this is the way Radia deploys msi’s. Because Radia uses http translations it will change all the files in the msi to the date the files were deployed.
One solution is to use a zip utility to unpackage your files that require the original date and time stamps after deployment. A small script will have to be used to unzip the files.
One solution is to use a zip utility to unpackage your files that require the original date and time stamps after deployment. A small script will have to be used to unzip the files.
Posted by:
sdexpert
18 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.