Software Deployment

The presence of the AS GUIDs will have no effect whatsoever on what Windows Installer sees as the package's installed status. That data is held elsewhere in the registry. If your package isn't updating, then you have other issues. Are you sure you mean 'updating' and not 'repairing'? The correct use of terminology is so important when talking about Windows Installer.

You will NOT get StubPath or IsInstalled in the HKCU hive but you should get 'Version' as the absolute minimum.

The only way to remove GUIDs for all users is either by a scripted Custom Action (labour-intensive) or use the tool which you already have - MSIZap. If you don't have it, why not!?! :) It's a free d/l from MS (as part of the SDK, IIRC)

Thanks for fast reply and explaining this to me. [I'm really new to this![:)]]
Yes, I'm sorry, I ment "repar" not "update".
So, if the msi doesn't repair it self for an existing user it has nothing to do with the prescense of an earlier HKCU AS GUID? Are they always left on uninstall?

I don't even get a "version" in AS GUID for HKCU.
I will look in to this :-)

ORIGINAL: JonnyO
Thanks for fast reply and explaining this to me. [I'm really new to this![:)]]
Yes, I'm sorry, I ment "repar" not "update".
So, if the msi doesn't repair it self for an existing user it has nothing to do with the prescense of an earlier HKCU AS GUID? Are they always left on uninstall?

I don't even get a "version" in AS GUID for HKCU.
I will look in to this :-)
"New" and "Premium Member"? :)

If the HKCU GUID matching the HKLM GUID exists, AS does precisely nothing since, according to its modus operandi, if that key exists, it already successfully ran whatever StubPath points to and thus its work is done.

If you want repair/self-healing to take place, you should re-do your package such that the files are in a separate, user-based feature. It's been discussed to death here so use the search for 'Repair' and/or 'Self-healing'.

Thank you for clearing that out.

I have now managed to get a repair triggered for a new user.
When logging in as a new user (admin) I see the repair dialog for a few seconds. But the repair has now taken place under the profile that installed the package in the first place. This seems strange for me. Where's the link between logging in as a new user and self healing to another users profile?

Regards

Hi Jonny,
as i told you in your earlier thread about the same issue: :-(
Read this carefully and several times: http://www.appdeploy.com/messageboards/fb.asp?m=32927
Regards, Nick

Hi,
Thanks for reply.
I have printed that out and read and read. I've rebulit my msi with currentuser feature at the top and followed the guide. However I don't manage to resolve the problem that administrators logging on trigger a repair(if not logged in earlier) but the repair is taking place in the installers profile. I have searched and read appdeploys forum for several days for hints on what is wrong. I understand there is some permission issues, but where and how do I set them? It works fine for standard users.
A reg entry is "Set as key" under currentuser. I thougt that should also trigger a repair if the key is broken/not apperant. I have no shortcuts or icons to advertise as this is word templates, and a few ini-files need to be placed under user profile.
Am using WPS 7.0 standard.

neo2000 had about the same problem but I'm not able to recapture anything as it only is a few files and two registry entries that should be deployed. read 6th post: http://itninja.com/question/how-do-you-roll-out-new-machines?5925&mpage=1&key=rights&#25925

Thanks for helping me :-)

Hi Jonny,

When logging in as a new user (admin) I see the repair dialog for a few seconds. But the repair has now taken place under the profile that installed the package in the first place. This seems strange for me. Where's the link between logging in as a new user and self healing to another users profile?

Are your paths for the users profile in the MSI building up as they should?
Could you please log the beast and put the logfile online?
Maybe here: http://www.senduit.com
Regards, Nick

Logs:
1:http://senduit.com/133341
2:http://senduit.com/5c05fa
3:http://senduit.com/045fbe
4:http://senduit.com/ad2fec

where (in chronological order)
1_install.log: Installation started manually by administrator 'IIBWISE' (works ok)
2_install.log: Active Setup triggers installation for normal user logging in as 'IIBPCVE' (works ok)
3_install.log: Active Setup triggers installation for administrator 'SOLOMON' (no appdata files but registry keys ok.)
4_install.log: Logging in as administrator 'IIBWISE' for second time triggers a repair. (works ok)

For me it seems like if user have no permission to administrators profile, then deploy current user profile instead?
Am so lost [:(]

Thank you!

Hi Jonny,
wow, you got a big mess here! :-(

MSI (s) (10:F0) [18:45:38:184]: Executing op: ActionStart(Name=DuplicateFiles,Description=Creating duplicate files...,Template=File: [1]
MSI (s) (10:F0) [18:45:38:184]: Executing op: ProgressTotal(Total=2544,Type=0,ByteEquivalent=1)
MSI (s) (10:F0) [18:45:38:184]: Executing op: SetSourceFolder(Folder=C:\Documents and Settings\iibpcve\Application Data\Iggesund\OfficeID\)
MSI (s) (10:F0) [18:45:38:184]: Executing op: SetTargetFolder(Folder=C:\Program\Microsoft Office\Templates\OfficeID\)
MSI (s) (10:F0) [18:45:38:184]: Executing op: FileCopy(SourceName=OfficeIdHolmenTimber.ini,,DestName=OfficeIdHolmenTimber.ini,Attributes=0,FileSize=153,PerTick=32768,IsCompressed=0,VerifyMedia=0,,,,,CheckCRC=0,,,InstallMode=262144,,,,,,,)
MSI (s) (10:F0) [18:45:38:184]: File: C:\Program\Microsoft Office\Templates\OfficeID\OfficeIdHolmenTimber.ini; Overwrite; Won't patch; Existing file is unversioned and unmodified - no source file hash provided to compare
MSI (s) (10:F0) [18:45:38:184]: Source for file 'OfficeIdHolmenTimber.ini' is uncompressed, at 'C:\Documents and Settings\iibpcve\Application Data\Iggesund\OfficeID\'.


You are copying files with the 'DupliacteFiles' action from profile folders to the program folder!
I think you intend to do the opposite, right?
The components in the 'Complete' feature should install the needed files to its location in the program files folders.
The 'User' feature should then duplicate this files to its destination in the profile folders.
And finally, your Acitve Setup action isn't quite the one we need: "REINSTALL=ALL REINSTALLMODE=pu"
Change this to: "REINSTALL=User REINSTALLMODE=pu"

Hope this points you in the right direction.
Regards, Nick

Thank you very much for explaining that to me!
I have some work to do[8|]. I'll let you know when my big mess is a smaller mess [:)]
Thanks![:)]

Hello,

I never got this package to work the way I wanted with self healing. I hade same problem as neo2000 (see link in my earlier post in this thread). I really had to fix this problem now so I made a workaround with a VB-script deploying user profile. That now works great.

I would like to thank all that have helped me out here!
Thanks