Software Deployment

methinks you need to rethink what you're doing, and how you're doing it. To be honest, this looks like a horrible mess. "Auditing Tool"? This is part of the operating system. You, the administrator, can build into the operating system what you want audited, down to a fine level of detail.

Sorry, perhaps I did not explain well enough. The auditing tool is the application I am repackaging. In this case, an Insurance Claims Examiner goes out to a business site and audits that site for worker's compensation safety. The Examiner then uses the audit application to enter the data and present a hard copy of the audit to the insured. This audit finding greatly affects the premium the insured pays.

You are correct in that this is not the ideal situation. I would much prefer to create an A.D. security group, add the users of the application to this group, and then set a logoff script policy on the group. However, as the users are not always on the domain, and domain policies are not cached, this is not ideal. A local policy is the only option I am aware of in order to meet the needs of the customer (namely, that the audit file is backed up at every logoff).

Thanks for the response, though.

I you insist on using this method, what happens if you run a gpupdate after the script/ at the end of the script?

OK I understand, so there is one file you have to have backed up before logoff and these are the actual reg keys where the policy is applied. I still think you should probably use something like secedit and have a consistent network drive to back up to.