![]() ![]() This can be done by creating a SOURCELIST (property name) in Windows Installer. Make sure the logged in users are able to access the original MSI used to deploy Snagit. Make the source installer available so that the auto-repair completes successfully.If users are locked, it is possible to enable some features via group policy to avail running MSI's. Deploy Snagit through the logged in user accounts rather than through a SYSTEM account.If the source is no longer accessible to the user (the source being the MSI that was used to deploy Snagit), then this prompt will appear: If a user logs into a machine, and the necessary resources under HKEY_CURRENT_USER\Software\TechSmith\SnagIt\12\ do not exist, the auto-repair will be triggered. ![]() ![]() So, when a normal user logs in and attempts to launch Snagit, Snagit will trigger an auto-repair for the missing resources.Īnother possible cause for this behavior is if the HKEY_CURRENT_USER hive is deleted every time a user logs out of a machine. Therefore, the registry keys that are placed in the registry under HKEY_CURRENT_USER in Snagit are being created for the account that the software was deployed with, rather than the logged in user account. The common cause for this behavior is when Snagit is being deployed under a SYSTEM account (or an administrator account through whichever deployment solution is being used). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |