Re: Installation when "Everyone" selected

Tech-Archive recommends: Fix windows errors by optimizing your registry



The event log will have some MsiInstaller entries that say what component
guid is missing - I should have mentioned that before.

The DesktopFolder documentation says that it will add the shortcut to the
all users profile, and the ProgramMenuFolder says the same thing. So it
shouldn't need a repair to create them for other users that log on, so
non-advertised shortcuts should work if you're not bothered about repair
working in general.. I've seen people report issues like this before, and I
think maybe that there's something inside the setup that's causing the
repair that you can't see, like a HKCU registry.

--
Phil Wilson
Definitive Guide to Windoows Installer
http://www.apress.com/book/view/1590592972


"chris" <chris@xxxxxxxxxxxx> wrote in message
news:4A7370F8-872D-4C90-BAC6-81CE1F3AF7DB@xxxxxxxxxxxxxxxx
Thanks Phil for the quick reply.

I've stripped everything out except the shortcuts to the User's Desktop
and
User's Programs Menu. Would these be the "user profile location" you
mentioned? If so, how else would I install shortcuts for all user's?

What do you think about using Orca to mark these shortcuts as
Non-Advertised?

Thanks again for your time,
Chris



"Phil Wilson" wrote:

There's something in your setup that's user specific (registry entry,
file
in a user profile location) that is absent when another user starts using
the app. The MSI repair kicks in when a shortcut is used, and that
installs
whatever is missing. It's normal. I think some older versions of MS
Office
used to do this for new users.
--
Phil Wilson
[MVP Windows Installer]

"chris" <chris@xxxxxxxxxxxx> wrote in message
news:627628F3-A1EE-4C80-B0C9-27E4D3C41A71@xxxxxxxxxxxxxxxx
Hi All,

When testing my software installation for "Everyone", I noticed the
first
time each user accesses the shortcut to the application, the .MSI file
is
targetted and it looks like a partial reinstall takes place. Once the
.MSI
file is successfully re-run, the shortcuts work as expected from then
on...
even when removing the application and re-installing it.

It seems like once an administrator installs the application for
"Everyone",
each user should not need the CD (.MSI file) to access the application
for
the first time.

Does anyone know why?
Am I missing something?

I'm using:
VS2008 setup project
Installing .NET Framework 2.0
Installing Windows Installer 3.1

Thanks for your time,
Chris






.



Relevant Pages

  • Re: Installation when "Everyone" selected
    ... Program Menu with the "Always Create" flag set. ... Definitive Guide to Windoows Installer ... I've stripped everything out except the shortcuts to the User's Desktop ... time each user accesses the shortcut to the application, the .MSI file ...
    (microsoft.public.vsnet.general)
  • Re: Where can I find the installation package for the assistant?
    ... This type of message can be caused by a missing or corrupt *.msi file. ... to point the Windows Installer to your installation CD: ... install the assistant separately? ...
    (microsoft.public.office.misc)
  • Re: Trouble Installing a COM Add-in for Non-Admin Users
    ... then it's up to them how they use the MSI file. ... It could even then launch ... the reason this won't work for me is because my "master installer" must be ... then it will set HKCU to the Standard User ...
    (microsoft.public.office.developer.com.add_ins)
  • Error 1335 in MSI
    ... We created an MSI file to install a VB.Net application via the web. ... downloads the MSI file to the temporary internet files folder and then ... 1335 when the installer is attempting to do it's job. ... someone suggested making sure that the IIS MIME setting ...
    (microsoft.public.vstudio.general)
  • Re: want to get app.path
    ... CustomActionData - that's the location of your MSI file. ... Phil Wilson [MVP Windows Installer] ... files from the folder *where my setup is present*, ... custom action and it will be the path to your ...
    (microsoft.public.dotnet.framework.setup)