Jump to content


This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
Photo

Per User Repair Questions(s)...


4 replies to this topic

Superfreak3

Superfreak3
  • Full Members
  • 437 posts

Posted 30 November 2011 - 18:26

Hi All,

Here's my situation in a nutshell... Both installing users are Admins on the target machine. User1 installs our software and is able to initiate the software without repair. User2 logs into the system and initiates our application (from an advertised shortcut), which initiates a repair install to write various user specific items.

Now, we switch back to User1. When he/she launches the install, a repair is initiated. After checking the Event Log, the process detects that a user item from User2's profile is missing. Why in the world is this occuring?

Is the repair process initiated by User2's initial login somehow not registered as the install process 'owner'.

If I log on as User2 and initiate our app at this point, a repair is once again initiated as a User1 piece is missing. What in the world gives?

I guess I should mention that I'm testing on a Win 7 x64 system with UAC set as the highest level (the only level above the default I believe).

I am making a push to remove user specific items from our install in a move to a per machine installation. Our application could/should then handle user specific settings on launch.

If anyone can help me sort this out and determine if there is any way around this behavior or if it is typical Windows Behavior I would be more than appreciative. I wonder if it is because I changed our shortcut to advertised a while back.

Thanks in advance!

Superfreak3

Superfreak3
  • Full Members
  • 437 posts

Posted 30 November 2011 - 19:17

There's no difference if the launching shortcut is Advertised or not. The behavior is the same.

Why, when the apps are repaired, are they then broken for another user that was already functioning?

Stefan Krueger

Stefan Krueger

    InstallSite.org

  • Administrators
  • 13,269 posts

Posted 05 December 2011 - 15:02

My guess is that the installer is storing a path to a per-user file in the registry. After the initial install, the path points to user1's directory. After user2 launched the application and the repairt ran, it points to user2's directory and so forth.
This article will help you identify the component which is causing the problem:
http://www.msifaq.com/a/1037.htm
Check to see if it inlcudes some per-user registry entries (this could also be COM registation entries)

Superfreak3

Superfreak3
  • Full Members
  • 437 posts

Posted 07 December 2011 - 17:44

I believe the component didn't involve any registry entries that I added. It dealt with information in My Documents.

I think it may be a Windows Installer caching 'thing'.

Stefan Krueger

Stefan Krueger

    InstallSite.org

  • Administrators
  • 13,269 posts

Posted 08 December 2011 - 11:50

"My Documents" is also per-user data.