Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

ALLUSERS property

8 views
Skip to first unread message

James

unread,
Aug 2, 2002, 9:40:31 AM8/2/02
to
I need to make a per machine MSI install with Visual Studio Installer for a
vb app. I looked a MSDN. They talk about it but do not say how to set it
or where in VS Installer you set it. Anybody know?

James

Phil Wilson

unread,
Aug 2, 2002, 2:35:52 PM8/2/02
to
Use a type 51 custom action to set ALLUSERS to 1, really early in the Execute sequence is the usual
best place.

"James" <jam...@advertech-ltd.com> wrote in message news:ukl2ugq...@corp.supernews.com...

Dennis Schmidt

unread,
Aug 2, 2002, 3:17:56 PM8/2/02
to
Hi James,

My name is Dennis Schmidt. Thank you for using the Microsoft Windows
Installer Newsgroups.

There isn't anyplace within a Visual Studio.Net output project that you can
specify a per machine install. You would need to open up the .msi package
in something like ORCA or one of the authoring packages to set the
properties. You also need to check the AllUsers properties associated with
dialogs. VS.Net .msi packages change this value a couple of places on the
exit of dialogs.

I hope this helps! If you have additional questions on this topic, please
reply to this posting.

Need quick answers to questions like these? The Microsoft Knowledge Base
provides a wealth of information that you can use to troubleshoot a problem
or answer a question! It's located at
http://support.microsoft.com/support/c.asp?M=F>.

This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. © 2001 Microsoft Corporation. All rights
reserved.

Regards,
Dennis Schmidt
Microsoft Support

James

unread,
Aug 2, 2002, 3:39:54 PM8/2/02
to
I opened the msi in OCRA and did a search for ALLUSERS, nothing. And under
properties is no property ALLUSERS.

"Dennis Schmidt" <Dennis...@microsoft.com> wrote in message
news:EhSbyklOCHA.2592@cpmsftngxa07...

Phil Wilson

unread,
Aug 2, 2002, 3:54:22 PM8/2/02
to
That's because (somewhat like VB maybe) properties don't need explicit declaration, they get created
by being set to a value. So create a type 51 CA using Orca, or set it from the msiexec command line
with ALLUSERS=1.

"James" <jam...@advertech-ltd.com> wrote in message news:uklo0bm...@corp.supernews.com...

James

unread,
Aug 2, 2002, 4:42:00 PM8/2/02
to
Do I need to create a Property ALLUSERS and reference it in the CA?
Action Type Source Target
SetAllUsers 51 ALLUSERS ALLUSERS=1

Do I need to have the action any where special in the InstallExecuteSequence
?


"Phil Wilson" <phil....@unisys.spamcom> wrote in message
news:O#CbG5lOCHA.1996@tkmsftngp12...

James

unread,
Aug 2, 2002, 5:05:21 PM8/2/02
to
If I'm reading this correctly that is not the correct way.

"It is strongly recommended that developers do not author packages that set
the ALLUSERS property using a dialog or custom action on Windows95 or
Windows98. An upgrade may fail on Windows95 or Windows98 if the ALLUSERS
property is set using a dialog or a custom action. On Windows95 or
Windows98, the installer ignores any attempt to set ALLUSERS by either the
command line or by the Property table. The ALLUSERS property can however
still be set using a dialog or a custom action, and this will cause upgrades
of that install to fail."

"Phil Wilson" <phil....@unisys.spamcom> wrote in message
news:O#CbG5lOCHA.1996@tkmsftngp12...

Torgeir Bakken

unread,
Aug 2, 2002, 5:17:58 PM8/2/02
to
James wrote:

> If I'm reading this correctly that is not the correct way.
>
> "It is strongly recommended that developers do not author packages that set
> the ALLUSERS property using a dialog or custom action on Windows95 or
> Windows98. An upgrade may fail on Windows95 or Windows98 if the ALLUSERS
> property is set using a dialog or a custom action. On Windows95 or
> Windows98, the installer ignores any attempt to set ALLUSERS by either the
> command line or by the Property table. The ALLUSERS property can however
> still be set using a dialog or a custom action, and this will cause upgrades
> of that install to fail."

This could be solved by adding a condition to the CA to not set the property for
Win9x/WinME

--
torgeir


James

unread,
Aug 2, 2002, 5:46:21 PM8/2/02
to
Ok, If I add a property ALLUSERS with Value 1
Then CA SetALLUsers type 51 Source ALLUSERS Target ALLUSERS
then ADD SetALLUsers to InstallExecuteSequence that would make this msi a
Per-Machine?
Then Only install on 95/98 with Admin rights.
Correct?

"Torgeir Bakken" <Torgeir.B...@hydro.com> wrote in message
news:3D4AF706...@hydro.com...

Phil Wilson

unread,
Aug 2, 2002, 7:07:18 PM8/2/02
to
In the CA, the Source is ALLUSERS, the Target is 1. (Think of it as like a line of code that sets
ALLUSERS to 1. )

You don't need to declare ALLUSERS in the property table

In the condition in the InstallExecuteSequence, just say VersionNT - then it will run only on the NT
family, NT, 2000, XP. It's the same kind of condition that you'd need if you were installing an NT
service on the InstallServices standard action, just in case Visual Studio Installer did the right
thing and automatically conditioned services (even though you're not installing them).

"James" <jam...@advertech-ltd.com> wrote in message news:uklvde9...@corp.supernews.com...

0 new messages