Hi
From experience of shipping to customers an installer that can do both
scenarios, the two part install might be intuitive, but it's a right pain in
practice. I now avoid doing the two part installs if at all possible.
Also the single install location is generally much easier if the
Hi Brad,
My experience is that you need to work out what the class registrations are
(either by Harvesting or otherwise) and do these using the Registry elements in
the installation. Doing so gives you registration on install and removal
afterwards. It's a bit of a pain to setup the first
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Registering/Unregistering ActiveX contolrs
Hi Mike,
Thanks for your insights - just a question What tool(s) did you use to
find the differences in the registry?
Brad.
-Original Message-
From: Michael
The error message is pretty generic, the service can't start for almost any
reason.
We have MSIs that run in full dialog mode so there is a dialog popped when the
service fails to start with the error you are seeing in the eventlog, with a
retry and cancel options.
When you get this dialog
: 'master'
Do you think it is an issue of SqlExtension? Or is it supposed to require
TCP/IP enabled even on the same server?
-- Yan
On Mon, Oct 17, 2011 at 9:54 AM, Michael Osmond mosm...@baytech.com.auwrote:
Hello Yan
Thanks for letting me know,
I don't fully know how it finds instances
sqldatabase.msi SQLSERVER=.\SQLEXPRESS USER=sa PASSWORD=***
LOGVERBOSE=1 /l*v install_named.log
Any ideas, people?
-- Yan
On Sat, Oct 8, 2011 at 12:05 AM, Michael Osmond mosm...@baytech.com.auwrote:
Yan,
You will find the Server Log in Management Studio - Under Management - SQL
Server
installs fine (referencing named SQL instance):*
msiexec /i sqldatabase.msi SQLSERVER=.\SQLEXPRESS USER=sa PASSWORD=***
LOGVERBOSE=1 /l*v install_named.log
Any ideas, people?
-- Yan
On Sat, Oct 8, 2011 at 12:05 AM, Michael Osmond mosm...@baytech.com.auwrote:
Yan,
You will find
Hi
Looks like an Access Denied to me.
Try the following to work out what is going on;
This is from an MS Blog
If the server encounters an error that prevents a login from succeeding, the
client will display the following error mesage.
Msg 18456, Level 14, State 1, Server server name, Line
error log where a corresponding entry will be written.
Could you please point out where I can find this server's error log
referenced here?
-- Yan
On Fri, Oct 7, 2011 at 10:12 AM, Michael Osmond mosm...@baytech.com.auwrote:
Hi
Looks like an Access Denied to me.
Try the following to work out
John
Have a look at the Start command (help start) which can be used to start and
wait in batch files.
Michael
-Original Message-
From: John Bergman [mailto:john.berg...@xpedienttechnologies.com]
Sent: Tuesday, 4 October 2011 8:47 AM
To: General discussion for Windows Installer XML
Hi Daniel
With a Major Upgrade you are essentially installing a new product and
uninstalling an old one, so I found the commandline needed the MSINEWINSTANCE=1
set for upgrading the instance.
Also try searching the Wix-Users email archive as there are some very good
emails on how people
Mark
Not 100% sure on this answer, but try BuiltIn\NetworkService or
[ComputerName]\NetworkService
Michael
-Original Message-
From: Mark Modrall [mailto:mmodr...@mzinga.com]
Sent: Tuesday, 23 August 2011 8:00 AM
To: General discussion for Windows Installer XML toolset.
Subject:
Hi
Not sure what the UAC behaviour is, but our install creates and upgrades
databases on 2008, so in theory it is possible. I am assuming you are using
SQL Server - you can check if it is permissions type issue by looking in the
SQL Management Log - see if there are login problems or other
Hi
What I have done, is to have two components for the Database, one is
conditioned to be installed if it is a clean install (not a major upgrade) and
the other is installed on the major upgrade, not on clean install. The initial
table creation script is against the first component, but not
Be carefull using USERDOMAIN, it is the domain of the account that is logged
in, which is not necessarily that of the domain the machine is in - for
instance if you are logged in as a local account on the machine USERDOMAIN will
be the computer name. I have not found an environment variable
Your CustomAction will need to be a deferred custom action, if it is to occur
after the database is created.
-Original Message-
From: Thai-Hoa Nguyen [mailto:taiwa...@hotmail.com]
Sent: Friday, 17 June 2011 9:57 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] When the DB
Hi
1. Is it possible to uninstall just a single instance, if that instance is
no longer needed?
Yes, Add/Remove programs will do it, or you can use the command line if you
know the Instance ProductCode
2. Is it possible to upgrade just a single instance, if needed.
Yes, but again you need
Hi
Here is a snipit of how I determine if I should use name\IIS_WPG (IIS6) or
builtin\IIS_IUSRS (IIS7) group in our installs. It has to deal with both the
domain part and the name. Gets messy because of domain controllers as well.
You could take something like this as a starting point.
Hello Kevin
I have been able to do a similar thing with no problem.
I expand out the command arguments using custom actions and then pass one
property through to the ExecCommand
This does allow you to see what is happening quite well in the log.
My approach:
CustomAction
Hi Martin
You could build up a single property with the PATH entry you wish to add using
a series of Type 51 Custom Actions. Each would add the path option for a
feature and be conditioned by the feature state. You then have a single
component (linked to you Register Environment Variables
Not certain, but try saving the Path add string to registry and read it back in
on Uninstall.
Also if someone adds a Feature through maintenance mode, you can append to the
path string. Your biggest issue would be if someone selectively removes a
feature.
Michael
-Original
Nick
I would recommend all Major Upgrade. I started with Minor and then introduced
Major upgrade in our products, and currently use a mix of them - which was a
mistake.
Complete uninstall verses upgrade - it all depends on how you are deploying in
production. Whatever you are doing there
Mike,
SqlDatabase has an option ConfirmOverwrite, if set to yes the installer will
prompt if it finds a database already created, and allows you to cancel or
continue. Using this option the installer only needs to deal with option 1
and you get 2 for free.
If you want to be defensive
?
-Original Message-
From: Michael Osmond [mailto:mosm...@baytech.com.au]
Sent: Monday, April 11, 2011 3:46 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] SqlDatabase install optional and SqlString
execute
Mike,
SqlDatabase has an option
before the db is created in the
scenario where the db doesn't exist yet.
I'm guessing that the locator will be resolved when the first SqlString
in the 2nd component tries to run against it?
Thanks.
-Original Message-
From: Michael Osmond [mailto:mosm...@baytech.com.au]
Sent: Monday, April
There is currently no built in facility that I know of for this. You would
need to build a custom action.
-Original Message-
From: kim [mailto:contactme...@gmail.com]
Sent: Friday, 25 March 2011 8:26 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Check if database exists
Not sure, have not done it myself. It really depends on how you want to detect
the error and have the user respond to it.
-Original Message-
From: kim [mailto:contactme...@gmail.com]
Sent: Friday, 25 March 2011 8:39 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users]
Kim
I can't see anything wrong with the script. But the error seems to be
specifically with the creation of the database itself from the error.
Things you could try:
1. Check that your account actually is an administrator in SQL Server. I have
not had much experience with Express, but in a
Hi
-2147467259 converts to 80004005. Try searching on this value.
Michael
-Original Message-
From: kim [mailto:contactme...@gmail.com]
Sent: Friday, 18 March 2011 7:17 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Error 26201. Error -2147467259: failed to create SQL
Kim
General guidance. Are you setting the file path for the MDF and LDF files of
the database in the WIX code? I can't see this in the emails I get.
If so the Account that the SQL Server service logs on as, will need to have
write / modify access to the folders in the paths you specify.
Hi
I suspect the error is that the service account for the SQL Server does not
have permissions to the file path to actually create the database files. Your
WXS snipit was not visable, so I am guessing that you are specifying a file
path for the data file and log file.
With SQL Server the
Hi Kevin
I think your error that it can't find the CA is in the call
private static bool CheckCredentials
Should be something like:
[CustomAction]
public static ActionResult CheckCredentials(Session session)
The class it is a member of also needs to be public.
Note
to tackle it if this is indeed
the problem. So the binary element that makes the DLL part of the .msi maybe
needs to know about the bited-ness: of the source and target. All of this is
just supposition as I am a relative beginner with WiX.
-Original Message-
From: Michael Osmond
HI
One of two options. My recommendation would be don't use SQL Authentication
unless you really need to, or only provide it as an advanced option for SQL
upgrades. The SQL tool will use Integrated Auth if the SQL user and password
are left blank. That would mean that the user running the
You could have two .reg files one for each situation condition the customaction
using the Msix64 property.
Having said that, would recommend you use the Wix RegistryKey/RegistryValue
instead.
Michael
-Original Message-
From: Arun Kumar [mailto:arun_jku...@persistent.co.in]
Sent:
I haven't found it so far.
I know some others have done some work around this, but you would have to
search for it.
We deploy reports via MSI and it's troublesome. My first solution was to get a
command process and use rs.exe which is a deployment tool that comes with
report server. The
Hi
Two things to consider
IIS_USRS is a built in group try not setting the Domain in the group record
(that has worked for me on Win7).I don't know if its relevant but it won't
work on Windows 2003 Server (it uses a different group).
For your user - %USERDOMAIN resolves to the domain of
Hi
I'd guess your problem is in the script
BEGIN
ALTER DATABASE [SOLUTIONDATABASENAME]
SET SINGLE_USER WITH ROLLBACK IMMEDIATE;
USE MASTER;
DROP DATABASE [SOLUTIONDATABASENAME];
END
Does this work in sql management studio - I would guess you need some go
Hate to say this, but write it to a registry key and read it back is the only
way I am aware of to do this.
Its not very much XML: You need a component with a registry entry, a property
with a registry search.
Michael
-Original Message-
From: Sanjay Rao
I not sure this is the best way, but I manually added the following to my
solution and project files.
I've removed all of the other msbuild properties that are not relevant:
The project file effectively defines 4 different configurations as property
groups. The property group with no
Well done,
We are in the process of closing off our migration from WIX 2.0, and I have
been pretty impressed with what's in WIX 3.5.
Thanks to you and the team
Michael
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Tuesday, 1 February 2011 1:07 AM
To:
Hello all,
I have a need where a package will determine if a previous version exists, and
then allow the user the option to upgrade the previous version, or to install
the new version side by side with the existing, so both are available.
My current thought was to use the Upgrade table to
Hi
The actual error from SQL server is -2147567259 - you need to find what this
equates to.
You can also look in the SQL Server Logs (via SQL Management Studio) it may
give some more hints.
I suspect you have a permissions issue - either the user running the install
does not have sufficient
Neil
Suggestion (but not tested).
Close visual studio, then edit the project file manually. When setting the path
use the either the $(SolutionDir) or $(ProjectDir) as the root of the path, so
that the project is transportable.
Then reopen in Vis studio. Haven't done this with wix project
Hello
Is anyone aware of a setting in Windows that forces a Windows restart after any
installation?
We have had an instance with a customer where the server restarted after an
upgrade, from the logs the restart looks like it was initiated by the user.
The update that was run should not
Hi
Another angle, to determine the location of an instance, connect to the
instance and use the SERVERPROPERTY('MachineName') and compare to your local
name.
You may need to be careful where the instance is running on a cluster.
Michael
-Original Message-
From: Blair
Hi
Another option to trace this is to use SQL Profiler - it should show the calls
being made and any errors occurring.
By setting ContinueOnError=yes any errors will be swallowed (they may be in
the log). If you are doing this only to make the uninstall robust against the
database not
Matt
Do you have the action MigrateFeatureStates in your Install and UI execution
sequences.
Michael
-Original Message-
From: Matt Johnson [mailto:ma...@timeamerica.com]
Sent: Friday, 7 May 2010 6:54 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users]
I found one case where this doesn't work. It seems dotnet apps by default
leave it up to the framework to determine if they are 64 or 32 bit. So when
you package this as a 32 Bit MSI and install it on a 64 Bit machine the
registry settings are redirected to the Wow6432bit node, but when the
the build targets from any cpu to x86 in
our .net compliation, forcing the assmblies to be 32 bit.
Its also possible to detect what os you are on in the .net application and to
override any redirection in the registry access calls.
Dave
-Original Message-
From: Michael Osmond [mailto:mosm
Hi
Error 0x80004005: failed to create to database:
80004005 - is Access Denied.
Regards
Michael
-Original Message-
From: Asiri Wanigarathne [mailto:waas...@gmail.com]
Sent: Thursday, 25 March 2010 3:43 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re:
Hi John
That is correct for a minor upgrade. You keep the UpgradeCode and ProductCode
the same, and the PackageCode and Version must change (see the MSI SDK for
details). FindRelatedProducts is not used for a minor upgrade.
Also be aware when you start an MSI with a minor upgrade it is
Jeff
I set the name and version information in the Description field of the Package
definition (as well as the version of the Product). This becomes part of the
SummaryInfo.
This is available through the file properties of the final MSI - ie right click
on the MSI, select Properties and go
that will automatically resolve to the right account name depending on the
target platform? If I have to define this property myself, is there a way to
automatically set its value depending on the target platform?
Thank you,
Raz
-Original Message-
From: Michael Osmond [mailto:mosm
Hi
I know I am coming in late on this one, so forgive me if I cover something that
has already been said.
My understanding is that NetworkService came in with Windows 2003 so it is not
native so to speak to windows 2000/XP.
What you could do set the Account to be a property, and depending on
I put them to a folder, and then exec RS.exe to call an rss script to do the
deployment.
This has a number of problems
1. We rely on RS.exe being on the path to find it. This should be the case,
but we have had issues particularly where two versions of SQL Server are on the
same machine.
2.
Hi
is for features not components
I think you want
?component=2
or possiblye NOT ?component=3 (which would cover all of the different not
installed situations).
Regards
Michael
From: Amy Rosewater [arosewa...@spectrumhr.com]
Sent: Thursday, 17
Hi
If you are using MSI Instances and installing to different locations, you don't
need different component GUIDs for each component in each installed instance
and the reference counting seems to work okay. I will be honest and say I
don't know how it works under the hood, but it does work.
The big issue with %USERDOMAIN is that it is the domain of the user account
that is logged on (and running the install). This may not be the Domain you
are after. Example: You are installing software on a Server in an Active
Directory domain. You want the domain name of AD - but the user
Hi
To do the rollback via the WIX Sql tools
1. You need to have a SqlScript or SqlString that has RollbackOnInstall (and
maybe RollbackOnReinstall) set. This schedules the Sql to be run when rolling
back. It needs to be scheduled prior to the SqlScript that adds the role.
The TSQL for the
do you do that? That is something I find could be very very useful
to me, not only username information, but all sorts of information that
could be useful during database creation, or update.
TYI
/Thomas
-Original Message-
From: Michael Osmond [mailto:mosm...@baytech.com.au]
Sent: 6
of
SQLServer.
Dominique.
-Original Message-
From: Michael Osmond [mailto:mosm...@baytech.com.au]
Sent: 07 October 2009 07:11
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Creating SQLServer Users/Logins
Here's an example of how I create the user
: Michael Osmond [mailto:mosm...@baytech.com.au]
Sent: Wednesday, October 07, 2009 1:01 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Creating SQLServer Users/Logins
Dominique
I think your right that the SPs are still in 2008, I tested this yesterday
Louis
You need to look at SqlDatabase, SqlScript and SqlString.
I use SqlString to create users (with TSQL) and then assign them a role in the
target database, as SqlString expands formatted strings. This way I can pass
username information into the SQL script as an MSI property.
You could
Hello Adnan
The way I do this is I bind each of the input values into properties and then
write each property to a registry value, then on upgrade I use the Registry
Search facility in MSI to read these properties from the registry back into the
properties
In most cases I also give the
(DBDlg.wxs) will bind with the property (in main file product.wxs)?
Can you please give me a Code example for understanding this concept? In
this case to accomplish Step 1 (Server) with checkbox?
Thanks in advance
Best Regards
Adnan
Michael Osmond wrote:
Hello Adnan
The way I do this is I bind
Hi,
When SQL Server creates the database files in the O/S it does so using the
identity of the SQL Server Service, the Service identity does not have access
to your program files area.
I suspect you will have big issues trying to create the database in My
Documents for this reason. If you
Xavier
The actual connection error is -2147467259, which converts to hex 80040005
which I believe is a generic access denied error.
Michael
-Original Message-
From: BOURDET Xavier [mailto:xbour...@generixgroup.com]
Sent: Saturday, 22 August 2009 12:26 AM
To:
John
No worries. Sorry I could not think of something more useful.
Regards
Michael
-Original Message-
From: John Stevenson-Hoare [mailto:john.stevenson-ho...@ffei.co.uk]
Sent: Monday, 3 August 2009 5:21 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Help: 'Error
for the Assert that you
mention and how I ensure that the custom action is included in the
installation? I just can't spot where the code is located in the source tree
that defines the custom action nor can I find any documentation to that
effect.
John
Michael Osmond wrote:
John,
I have
to debug the steps that the installer is
performing to see exactly where the error is generated and perhaps try some
alternative values?
John
Michael Osmond wrote:
John,
Firstly what value is the property SQLSERVER being set to, and where is it
set?
If that is okay, then i suspect it is a SQL
John,
Firstly what value is the property SQLSERVER being set to, and where is it set?
If that is okay, then i suspect it is a SQL Express set up issue.
The 0x80004005 error could also be an access denied error from the file system
- it does not look like you are specifying a path to where
Hello Mary, Romeo
Try the following:
1. Create a SqlDatabase for Master, that is not under a component (so its just
a reference)
2. Under you component for the target database, but not under the SqlDatabase
entry for that database, add a SqlString which is run against Master, executed
on
Neil,
I am not aware of anyway to use trusted as you indicate (not built in to the
WIX CA anyway). In the end you have to have a valid windows user context to
use trusted from, so you would still need a password (or security context) to
do a runas/switch user type of operation to run as a
Niel,
Two things to consider.
1. My experience is that in the trusted case the connection to SQL is as the
user running the MSI.
2. There is also an issue of what you are actually doing in the SQL
string/script - if it is doing anything outside of SQL (say a backup) then when
it interacts
Alex,
Use the Registry Search to read the values into Properties before the upgrade,
and use the Properties to write the registry settings.
Michael
From: Alex Ivanoff [alex.ivan...@shavlik.com]
Sent: Thursday, 14 May 2009 12:34 AM
To: General
David,
To automate the deployment you need the every build to be able to update the
last. I am guessing that because of your versioning of the MSI with the sprint
number being the third number, you can't process the install as an upgrade. I
am assuming you have authored upgrades into the
Murray
I know there is some stuff if you search through the history of this mailing
list. I don't know of any tutorials or other info, but that doesn't mean there
isn't any.
First what runs in an upgrade is really going to depend on if you are doing an
MSI Major Upgrade or Minor Upgrade. If
Murray,
Try writing the properties into registry values at install and then using the
Registry Search to read the values back into properties at the start of an
upgrade
Michael
-Original Message-
From: Murray Hipper [mailto:mhip...@snowdengroup.com]
Sent: Tuesday, 5 May 2009 3:17 PM
Johan,
Here is what I do,
I want a welcome dialog for a first time install, upgrade dialog if it is a
major or minor upgrade and a maintenance dialog (ie change features) dialog if
it is launched from the Add/Remove programs
Show Dialog=Welcome_Dialog After=MigrateFeatureStates![CDATA[(NOT
this... there is no info more than
this in eventvwr.
Please suggest me any other way to tackle this.
or else i would be left to last option of using DTF CA for executing
sqlscripts.
regards,
Akash
On Thu, Mar 12, 2009 at 11:04 AM, Michael Osmond
mosm...@baytech.com.auwrote:
Akash
First check
Akash
First check the application event log (for a failure error from
MSInstaller), the full text of the SQL error is there (I am assuming
that the Check related errors.. means you are reading this error from
the error dialog).
I suspect there is an MDF or LDF file hanging around in the SQL
Value=KMFUNINSTALL/
In the execute sequence:
Custom Action=CheckKMFUninstall After=InstallInitializeInstalled
AND NOT UPGRADINGPRODUCTCODE/Custom
Michael Osmond wrote:
Joe,
My appologies, I was not carefull. If you put that SQL code in a
SQLString element (not SQLScript
Joe
Try looking at the SKIPCONFIGUREIIS property (its part of WIX), this is
how I stop the installer from doing the IIS Custom action if
MainComponent is not selected.
!-- Suppress the IIS CA if we are not installing the
web site --
CustomAction Id=SkipIISCA
what's the difference between the two and
is it important to use two of them together?
Thanks.
Michael Osmond wrote:
Joe
Try looking at the SKIPCONFIGUREIIS property (its part of WIX), this
is how I stop the installer from doing the IIS Custom action if
MainComponent is not selected
on your suggestion I've created the following
sql script:
USE [master]
GO
IF ('[REMOVE]' = 'ALL')
BEGIN
DROP DATABASE MyDataBase
END
but the database doesn't get removed on uninstall. How can the sql
script determine the value of [REMOVE] on uninstall?
Thank you.
Michael Osmond wrote:
Hello Joe
Hello Joe,
I've been in a similar situation. The possible solutions I am aware of:
1. If you schedule the DeleteExistingProduct action at the end of the
install (I think after the InstallFinalise), my understanding is that
the install should calculate that there still is a count of one on the
Joe,
I don't think you cam do this in WIX V2 (if that's what you using).
Michael
-Original Message-
From: Joe Osman [mailto:joe.os...@tait.co.nz]
Sent: Monday, 16 February 2009 12:14 PM
To: General discussion for Windows Installer XMLtoolset.
Subject: [WiX-users] sql:SqlDatabase drops
Robert,
Just one observation, are you sure that the difference in between using
create (in the exampel that works) and wrapping the create inside an
exec command (in the example that fails) is not the problem. Both look
okay to me, but I have had fun in the past with getting exec('strings')
to
Thomas,
Removing the old version is important if the new version is structurally
different (eg different assembly names, different registry keys, different
folder layout). Believe me it happens.
To just go over the top look at Minor Upgrades, these work if you are simply
refreshing existing
Adam,
I suspect there is something more going on here. We have been following
a test deployment process like yours for several years for a suite of
large web applications, and the only time we have file lock issues is if
someone is actively testing (hitting the pages) when the upgrade occurs.
too quick to start installing
before we its let the service settle (althought like i said I would
think its smarter than that) but the website I am a bit stumped with.
Adam
On Wednesday 21 January 2009 22:10:55 Michael Osmond wrote:
Adam,
I suspect there is something more going on here. We
I get the time.
Thanks for your help so far.
Adam
On Wednesday 21 January 2009 22:59:01 Michael Osmond wrote:
Adam,
I agree (and our experience bears it out), IIS reset should kill off
any thing that the web app is doing (actually we rarely even need to
do that. Unless is some
Joe,
How is the Uninstall of the old product version scheduled in the
upgrade. My guess is that your update is uninstalling and then
installing the web pool and when it reinstalls it, it no longer has the
identity to use.
Michael
-Original Message-
From: Joe Osman
Hello Ryan,
From my experience, most of what you want to do in the Install Sequence
you actually need to do in the Bootstrap, some of this information is
actually required as you start the MSI engine up. You should probably
have a read of the MSI SDK which talks about what is need for multiple
Colin,
You can set an environment variable in the build process and then access
that inside wix as $(env.projectVersion)
Or you can set an Wix variable in the candle command line
candle -dMyProject.Version=value
Michael
-Original Message-
From: Colin Fox
Hi,
The approach I would recommend is try not to put so much meaning into
the version number. Make the MSI version number something simple, which
always changes.
We have deliberately restricted things to Major.Minor.build for the MSI
version number. Internally the buil number is rolled every
Peter,
I am not sure of all the details, but try saving the SQL script as ANSI
format.
Michael
-Original Message-
From: Peter McClymont [mailto:[EMAIL PROTECTED]
Sent: Friday, 28 November 2008 11:01 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Running SQL scripts under
Hello Robert
You can't set the value of a property from another property that way.
Not supported in the MSI.
If you wish to do this you need to use a custom action type 51 to do
this.
Regards
Michael
-Original Message-
From: Robert O'Brien [mailto:[EMAIL PROTECTED]
Sent: Thursday,
Hello Amy,
I actually use [ComputerName]\iis_wpg this is IIS Working Process Group of
which network service is a member. Although that said, this group only exists
if IIS is an installed windows component. This covers, system, network
service, local service and I think Aspnet.
Michael
1 - 100 of 136 matches
Mail list logo
