Windows Installer and Impersonalization

P

Paul Bacelar

Hi and happy good year,



I use a msi file, generated by a VS.NET deployment project, to install my
components.



My problem is:

My setup.exe is launched by a user having extra rights on the Exchange
Server of domain, extra rights which allows my install procedure, via
"MyServiceName /Service", to request the Exchange Server. But, on a "Win2000
Server With Final Server" machine into my customer test domain, the install
process (my service) isn't processed under my initial user context but under
a "NT AUTHORITY\System" context, account of "Windows Installer" service.
"Windows Installer" service probably refuses to impersonalize my
installation program. I didn't reproduce this behaviour on my test
platform.

The "AlwaysInstallElevated" group policies (user and machine) don't seem to
influence the "Windows Installer" impersonalization. In brief, Why "Windows
Installer" doesn't keep the security context of the installation program
(setup.exe) and which are the parameters which influence its behaviour from
the security point of view?



Thank you, for your suggestions.



--
Paul Bacelar



PS: Sorry for my very very bad English ;-{
 
P

Phil Wilson

Because when the installer service is updating the system from the data in
the MSI tables, the security is mostly controlled by policy rather than by
the user privileges. When the installer calls custom actions it *does*
impersonate the calling user.
 
P

Paul Bacelar

Yes, but why my custom actions weren't impersonate with one policy and were
impersonate with another policy.

"AlwaysInstallElevated" policy attribute don't seem involved.

In MSI Log of unsuccessful install, I see this strange line:

"MSI (s) (FC:D4): Not impersonating action for per-machine Win2000 TS
install."

It's a legal situation or TS (Terminal Server) installation isn't
successfully terminated?
--
Paul Bacelar


Phil Wilson said:
Because when the installer service is updating the system from the data in
the MSI tables, the security is mostly controlled by policy rather than by
the user privileges. When the installer calls custom actions it *does*
impersonate the calling user.
--
Phil Wilson
[MVP Windows Installer]
Paul Bacelar said:
Hi and happy good year,



I use a msi file, generated by a VS.NET deployment project, to install my
components.



My problem is:

My setup.exe is launched by a user having extra rights on the Exchange
Server of domain, extra rights which allows my install procedure, via
"MyServiceName /Service", to request the Exchange Server. But, on a "Win2000
Server With Final Server" machine into my customer test domain, the install
process (my service) isn't processed under my initial user context but under
a "NT AUTHORITY\System" context, account of "Windows Installer" service.
"Windows Installer" service probably refuses to impersonalize my
installation program. I didn't reproduce this behaviour on my test
platform.

The "AlwaysInstallElevated" group policies (user and machine) don't seem to
influence the "Windows Installer" impersonalization. In brief, Why "Windows
Installer" doesn't keep the security context of the installation program
(setup.exe) and which are the parameters which influence its behaviour from
the security point of view?



Thank you, for your suggestions.



--
Paul Bacelar



PS: Sorry for my very very bad English ;-{
Click to expand...
Click to expand...
 
P

Phil Wilson

Could you post the rest of the log around there? That may just apply to a
particular action.
--
Phil Wilson [MVP Windows Installer]
----
Paul Bacelar said:
Yes, but why my custom actions weren't impersonate with one policy and were
impersonate with another policy.

"AlwaysInstallElevated" policy attribute don't seem involved.

In MSI Log of unsuccessful install, I see this strange line:

"MSI (s) (FC:D4): Not impersonating action for per-machine Win2000 TS
install."

It's a legal situation or TS (Terminal Server) installation isn't
successfully terminated?
--
Paul Bacelar


Phil Wilson said:
Because when the installer service is updating the system from the data in
the MSI tables, the security is mostly controlled by policy rather than by
the user privileges. When the installer calls custom actions it *does*
impersonate the calling user.
--
Phil Wilson
[MVP Windows Installer]
Paul Bacelar said:
Hi and happy good year,



I use a msi file, generated by a VS.NET deployment project, to install my
components.



My problem is:

My setup.exe is launched by a user having extra rights on the Exchange
Server of domain, extra rights which allows my install procedure, via
"MyServiceName /Service", to request the Exchange Server. But, on a "Win2000
Server With Final Server" machine into my customer test domain, the install
process (my service) isn't processed under my initial user context but under
a "NT AUTHORITY\System" context, account of "Windows Installer" service.
"Windows Installer" service probably refuses to impersonalize my
installation program. I didn't reproduce this behaviour on my test
platform.

The "AlwaysInstallElevated" group policies (user and machine) don't seem to
influence the "Windows Installer" impersonalization. In brief, Why "Windows
Installer" doesn't keep the security context of the installation program
(setup.exe) and which are the parameters which influence its behaviour from
the security point of view?



Thank you, for your suggestions.



--
Paul Bacelar



PS: Sorry for my very very bad English ;-{
Click to expand...
Click to expand...
Click to expand...
 
P

Paul Bacelar

Thank you for your help ;-)



=== Verbose logging started: 09/01/2004 17:18:49 Build type: SHIP UNICODE
2.00.2600.1183 Calling process: C:\WINNT\system32\MsiExec.exe ===
MSI (c) (E8:EC): Resetting cached policy values
MSI (c) (E8:EC): Machine policy value 'Debug' is 7
MSI (c) (E8:EC): ******* RunEngine:
******* Product: H:\install\mPIM\Connecteur\linkuallServer.msi
******* Action:
******* CommandLine:
MSI (c) (E8:EC): Machine policy value 'DisableUserInstalls' is 0
MSI (c) (E8:EC): Cloaking enabled.
MSI (c) (E8:EC): End dialog not enabled
MSI (c) (E8:EC): Original package ==>
H:\install\mPIM\Connecteur\linkuallServer.msi
MSI (c) (E8:EC): Package we're running from ==>
C:\DOCUME~1\ADMINI~2\LOCALS~1\Temp\6527439.msi
MSI (c) (E8:EC): APPCOMPAT: looking for appcompat database entry with
ProductCode '{9475BFDC-32F3-4514-9625-40F08EAF490A}'.
MSI (c) (E8:EC): APPCOMPAT: no matching ProductCode found in database.
MSI (c) (E8:EC): Machine policy value 'TransformsSecure' is 0
MSI (c) (E8:EC): User policy value 'TransformsAtSource' is 0
MSI (c) (E8:EC): APPCOMPAT: looking for appcompat database entry with
ProductCode '{9475BFDC-32F3-4514-9625-40F08EAF490A}'.
MSI (c) (E8:EC): APPCOMPAT: no matching ProductCode found in database.
MSI (c) (E8:EC): Transforms are not secure.
MSI (c) (E8:EC): Command Line: CURRENTDIRECTORY=H:\install\mPIM\Connecteur
CLIENTUILEVEL=0 CLIENTPROCESSID=1768 %HOMEPATH=\Documents and
Settings\administrateur %HOMEDRIVE=C: %HOMESHARE=
MSI (c) (E8:EC): Product Code passed to Engine.Initialize: ''
MSI (c) (E8:EC): Product Code from property table before transforms:
'{9475BFDC-32F3-4514-9625-40F08EAF490A}'
MSI (c) (E8:EC): Product Code from property table after transforms:
'{9475BFDC-32F3-4514-9625-40F08EAF490A}'
MSI (c) (E8:EC): Product not registered: beginning first-time install
MSI (c) (E8:EC): Entering CMsiConfigurationManager::SetLastUsedSource.
MSI (c) (E8:EC): User policy value 'SearchOrder' is 'nmu'
MSI (c) (E8:EC): Adding new sources is allowed.
MSI (c) (E8:EC): Package name extracted from package path:
'linkuallServer.msi'
MSI (c) (E8:EC): Package to be registered: 'linkuallServer.msi'
MSI (c) (E8:EC): Note: 1: 2262 2: Error 3: -2147287038
MSI (c) (E8:EC): Note: 1: 2729
MSI (c) (E8:EC): Note: 1: 2729
MSI (c) (E8:EC): Note: 1: 2729
MSI (c) (E8:EC): Note: 1: 2729
MSI (c) (E8:EC): Note: 1: 2729
MSI (c) (E8:EC): Note: 1: 2729
MSI (c) (E8:EC): Note: 1: 2729
MSI (c) (E8:EC): Note: 1: 2729
MSI (c) (E8:EC): Note: 1: 2729
MSI (c) (E8:EC): Note: 1: 2729
MSI (c) (E8:EC): Note: 1: 2729
MSI (c) (E8:EC): Note: 1: 2729
MSI (c) (E8:EC): Note: 1: 2729
MSI (c) (E8:EC): Note: 1: 2729
MSI (c) (E8:EC): Note: 1: 2729
MSI (c) (E8:EC): Note: 1: 2729
MSI (c) (E8:EC): Note: 1: 2262 2: AdminProperties 3: -2147287038
MSI (c) (E8:EC): Machine policy value 'DisableMsi' is 0
MSI (c) (E8:EC): Machine policy value 'AlwaysInstallElevated' is 0
MSI (c) (E8:EC): User policy value 'AlwaysInstallElevated' is 0
MSI (c) (E8:EC): Running product '{9475BFDC-32F3-4514-9625-40F08EAF490A}'
with user privileges: It's not assigned.
MSI (c) (E8:EC): TRANSFORMS property is now:
MSI (c) (E8:EC): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\administrateur\Application Data
MSI (c) (E8:EC): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\administrateur\Favorites
MSI (c) (E8:EC): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\administrateur\NetHood
MSI (c) (E8:EC): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\administrateur\My Documents
MSI (c) (E8:EC): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\administrateur\PrintHood
MSI (c) (E8:EC): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\administrateur\Recent
MSI (c) (E8:EC): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\administrateur\SendTo
MSI (c) (E8:EC): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\administrateur\Templates
MSI (c) (E8:EC): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\All Users\Application Data
MSI (c) (E8:EC): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\administrateur\Local Settings\Application Data
MSI (c) (E8:EC): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\administrateur\My Documents\My Pictures
MSI (c) (E8:EC): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\administrateur\Start Menu\Programs\Administrative Tools
MSI (c) (E8:EC): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\administrateur\Start Menu\Programs\Startup
MSI (c) (E8:EC): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\administrateur\Start Menu\Programs
MSI (c) (E8:EC): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\administrateur\Start Menu
MSI (c) (E8:EC): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\administrateur\Desktop
MSI (c) (E8:EC): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\All Users\Start Menu\Programs\Administrative Tools
MSI (c) (E8:EC): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\All Users\Start Menu\Programs\Startup
MSI (c) (E8:EC): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\All Users\Start Menu\Programs
MSI (c) (E8:EC): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\All Users\Start Menu
MSI (c) (E8:EC): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\All Users\Desktop
MSI (c) (E8:EC): SHELL32::SHGetFolderPath returned: C:\WINNT\Fonts
MSI (c) (E8:EC): Note: 1: 2898 2: MS Sans Serif 3: MS Sans Serif 4: 0 5: 16
MSI (c) (E8:EC): MSCOREE not loaded loading copy from system32
MSI (c) (E8:EC): Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\MS
Setup (ACME)\User Info 3: 2
MSI (c) (E8:EC): Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\MS
Setup (ACME)\User Info 3: 2
=== Logging started: 09/01/2004 17:18:50 ===
MSI (c) (E8:EC): Machine policy value 'DisableRollback' is 0
MSI (c) (E8:EC): User policy value 'DisableRollback' is 0
MSI (c) (E8:EC): Doing action: INSTALL
MSI (c) (E8:EC): Note: 1: 2262 2: ActionText 3: -2147287038
Action start 17:18:50: INSTALL.
MSI (c) (E8:EC): UI Sequence table 'InstallUISequence' is present and
populated.
MSI (c) (E8:EC): Running UISequence
MSI (c) (E8:EC): Skipping action: ERRCA_UIANDADVERTISED (condition is false)
MSI (c) (E8:EC): Doing action: AppSearch
Action start 17:18:50: AppSearch.
MSI (c) (E8:EC): Note: 1: 2262 2: AppSearch 3: -2147287038
Action ended 17:18:50: AppSearch. Return value 1.
MSI (c) (E8:EC): Doing action: FindRelatedProducts
Action start 17:18:50: FindRelatedProducts.
Action ended 17:18:50: FindRelatedProducts. Return value 1.
MSI (c) (E8:EC): Skipping action: ERRCA_CANCELNEWERVERSION (condition is
false)
MSI (c) (E8:EC): Doing action: LaunchConditions
Action start 17:18:50: LaunchConditions.
MSI (c) (E8:EC): Note: 1: 2262 2: LaunchCondition 3: -2147287038
Action ended 17:18:50: LaunchConditions. Return value 1.
MSI (c) (E8:EC): Doing action: CCPSearch
Action start 17:18:50: CCPSearch.
MSI (c) (E8:EC): Note: 1: 2262 2: CCPSearch 3: -2147287038
Action ended 17:18:50: CCPSearch. Return value 1.
MSI (c) (E8:EC): Doing action: RMCCPSearch
Action start 17:18:50: RMCCPSearch.
MSI (c) (E8:EC): Note: 1: 2262 2: CCPSearch 3: -2147287038
Action ended 17:18:50: RMCCPSearch. Return value 0.
MSI (c) (E8:EC): Doing action: ValidateProductID
Action start 17:18:50: ValidateProductID.
Action ended 17:18:50: ValidateProductID. Return value 1.
MSI (c) (E8:EC): Doing action: DIRCA_TARGETDIR
Action start 17:18:50: DIRCA_TARGETDIR.
Action ended 17:18:50: DIRCA_TARGETDIR. Return value 1.
MSI (c) (E8:EC): Doing action: CostInitialize
Action start 17:18:50: CostInitialize.
Action ended 17:18:50: CostInitialize. Return value 1.
MSI (c) (E8:EC): Doing action: FileCost
Action start 17:18:50: FileCost.
MSI (c) (E8:EC): Note: 1: 2262 2: RemoveFile 3: -2147287038
MSI (c) (E8:EC): Note: 1: 2262 2: MsiAssembly 3: -2147287038
MSI (c) (E8:EC): Note: 1: 2262 2: Class 3: -2147287038
MSI (c) (E8:EC): Note: 1: 2262 2: Extension 3: -2147287038
MSI (c) (E8:EC): Note: 1: 2262 2: TypeLib 3: -2147287038
MSI (c) (E8:EC): Note: 1: 2262 2: IniFile 3: -2147287038
MSI (c) (E8:EC): Note: 1: 2262 2: MoveFile 3: -2147287038
MSI (c) (E8:EC): Note: 1: 2262 2: DuplicateFile 3: -2147287038
MSI (c) (E8:EC): Note: 1: 2262 2: ReserveCost 3: -2147287038
MSI (c) (E8:EC): Note: 1: 2262 2: Shortcut 3: -2147287038
Action ended 17:18:50: FileCost. Return value 1.
MSI (c) (E8:EC): Doing action: IsolateComponents
Action start 17:18:50: IsolateComponents.
MSI (c) (E8:EC): Note: 1: 2262 2: IsolatedComponent 3: -2147287038
MSI (c) (E8:EC): Note: 1: 2262 2: BindImage 3: -2147287038
MSI (c) (E8:EC): Note: 1: 2262 2: Patch 3: -2147287038
Action ended 17:18:50: IsolateComponents. Return value 1.
MSI (c) (E8:EC): Skipping action: ResumeForm (condition is false)
MSI (c) (E8:EC): Skipping action: MaintenanceForm (condition is false)
MSI (c) (E8:EC): Doing action: CostFinalize
Action start 17:18:50: CostFinalize.
MSI (c) (E8:EC): Note: 1: 2262 2: Patch 3: -2147287038
MSI (c) (E8:EC): Note: 1: 2262 2: Condition 3: -2147287038
MSI (c) (E8:EC): Target path resolution complete. Dumping Directory table...
MSI (c) (E8:EC): Note: target paths subject to change (via custom actions or
browsing)
MSI (c) (E8:EC): Dir (target): Key: TARGETDIR , Object: C:\Program
Files\sinpag\MPIM\
MSI (c) (E8:EC): Dir (target): Key: WindowsFolder , Object: C:\WINNT\
MSI (c) (E8:EC): Dir (target): Key: DesktopFolder , Object: C:\Documents and
Settings\administrateur\Desktop\
MSI (c) (E8:EC): Dir (target): Key: ProgramMenuFolder , Object: C:\Documents
and Settings\administrateur\Start Menu\Programs\
MSI (c) (E8:EC): Dir (target): Key: _15F7195FBC43449BA29B18250A126173 ,
Object: C:\Program Files\sinpag\MPIM\htdocs\
MSI (c) (E8:EC): Dir (target): Key: _CBF2D77DDC5A49E6AEBA1D20CF7D2D08 ,
Object: C:\Program Files\sinpag\MPIM\logs\
MSI (c) (E8:EC): Dir (target): Key: SystemFolder , Object:
C:\WINNT\system32\
MSI (c) (E8:EC): Dir (target): Key: _9823290E7B79499AB18187A93CA1792F ,
Object: C:\Program Files\sinpag\MPIM\cgi-bin\
MSI (c) (E8:EC): Dir (target): Key: _C094BE8D64E74E87A8D0E1A2FEA633B3 ,
Object: C:\Program Files\sinpag\MPIM\conf\
MSI (c) (E8:EC): Dir (target): Key: _390CBC155305424BA11416F2C242DBA0 ,
Object: C:\Program Files\sinpag\MPIM\conf\ssl\
MSI (c) (E8:EC): Dir (target): Key: _0A093580C456483BAB174F9F62F4AB35 ,
Object: C:\Program Files\sinpag\MPIM\lib\
MSI (c) (E8:EC): Dir (target): Key: _477CC96D36B140D78D269CF789F2B9BB ,
Object: C:\Program Files\sinpag\MPIM\bin\
MSI (c) (E8:EC): Dir (target): Key: _47AD186AAB5C42B181B1E21422CFF03B ,
Object: C:\Program Files\sinpag\MPIM\modules\
MSI (c) (E8:EC): Note: 1: 2262 2: RemoveFile 3: -2147287038
Action ended 17:18:50: CostFinalize. Return value 1.
MSI (c) (E8:EC): Doing action: WelcomeForm
Action start 17:18:50: WelcomeForm.
Info 2898. VSI_MS_Sans_Serif13.0_0_0, MS Sans Serif, 0
DEBUG: Error 2826: Control Line1 on dialog WelcomeForm extends beyond the
boundaries of the dialog to the right by 3 pixels
The installer has encountered an unexpected error installing this package.
This may indicate a problem with this package. The error code is 2826. The
arguments are: WelcomeForm, Line1, to the right
DEBUG: Error 2826: Control Line2 on dialog WelcomeForm extends beyond the
boundaries of the dialog to the right by 3 pixels
The installer has encountered an unexpected error installing this package.
This may indicate a problem with this package. The error code is 2826. The
arguments are: WelcomeForm, Line2, to the right
DEBUG: Error 2826: Control BannerBmp on dialog WelcomeForm extends beyond
the boundaries of the dialog to the right by 3 pixels
The installer has encountered an unexpected error installing this package.
This may indicate a problem with this package. The error code is 2826. The
arguments are: WelcomeForm, BannerBmp, to the right
Info 2898. VsdDefaultUIFont.524F4245_5254_5341_4C45_534153783400, MS Sans
Serif, 0
Info 2898. VSI_MS_Sans_Serif16.0_1_0, MS Sans Serif, 0
Action 17:18:50: WelcomeForm. Dialog created
DEBUG: Error 2826: Control Line1 on dialog FolderForm extends beyond the
boundaries of the dialog to the right by 3 pixels
The installer has encountered an unexpected error installing this package.
This may indicate a problem with this package. The error code is 2826. The
arguments are: FolderForm, Line1, to the right
DEBUG: Error 2826: Control Line2 on dialog FolderForm extends beyond the
boundaries of the dialog to the right by 3 pixels
The installer has encountered an unexpected error installing this package.
This may indicate a problem with this package. The error code is 2826. The
arguments are: FolderForm, Line2, to the right
DEBUG: Error 2826: Control BannerBmp on dialog FolderForm extends beyond
the boundaries of the dialog to the right by 3 pixels
The installer has encountered an unexpected error installing this package.
This may indicate a problem with this package. The error code is 2826. The
arguments are: FolderForm, BannerBmp, to the right
Info 2898. VSI_MS_Shell_Dlg13.0_0_0, MS Shell Dlg, 0
Action 17:18:52: FolderForm. Dialog created
DEBUG: Error 2826: Control Line1 on dialog ConfirmInstallForm extends
beyond the boundaries of the dialog to the right by 3 pixels
The installer has encountered an unexpected error installing this package.
This may indicate a problem with this package. The error code is 2826. The
arguments are: ConfirmInstallForm, Line1, to the right
DEBUG: Error 2826: Control Line2 on dialog ConfirmInstallForm extends
beyond the boundaries of the dialog to the right by 3 pixels
The installer has encountered an unexpected error installing this package.
This may indicate a problem with this package. The error code is 2826. The
arguments are: ConfirmInstallForm, Line2, to the right
DEBUG: Error 2826: Control BannerBmp on dialog ConfirmInstallForm extends
beyond the boundaries of the dialog to the right by 3 pixels
The installer has encountered an unexpected error installing this package.
This may indicate a problem with this package. The error code is 2826. The
arguments are: ConfirmInstallForm, BannerBmp, to the right
Action 17:18:55: ConfirmInstallForm. Dialog created
Action ended 17:18:57: WelcomeForm. Return value 1.
MSI (c) (E8:EC): Doing action: ProgressForm
Action start 17:18:57: ProgressForm.
DEBUG: Error 2826: Control Line1 on dialog ProgressForm extends beyond the
boundaries of the dialog to the right by 3 pixels
The installer has encountered an unexpected error installing this package.
This may indicate a problem with this package. The error code is 2826. The
arguments are: ProgressForm, Line1, to the right
DEBUG: Error 2826: Control Line2 on dialog ProgressForm extends beyond the
boundaries of the dialog to the right by 3 pixels
The installer has encountered an unexpected error installing this package.
This may indicate a problem with this package. The error code is 2826. The
arguments are: ProgressForm, Line2, to the right
DEBUG: Error 2826: Control BannerBmp on dialog ProgressForm extends beyond
the boundaries of the dialog to the right by 3 pixels
The installer has encountered an unexpected error installing this package.
This may indicate a problem with this package. The error code is 2826. The
arguments are: ProgressForm, BannerBmp, to the right
Action 17:18:57: ProgressForm. Dialog created
Action ended 17:18:57: ProgressForm. Return value 1.
MSI (c) (E8:EC): Doing action: ExecuteAction
Action start 17:18:57: ExecuteAction.
MSI (c) (E8:EC): Grabbed execution mutex.
MSI (c) (E8:EC): Incrementing counter to disable shutdown. Counter after
increment: 0
MSI (c) (E8:EC): Switching to server: TARGETDIR="C:\Program
Files\sinpag\MPIM\" _47AD186AAB5C42B181B1E21422CFF03B="C:\Program
Files\sinpag\MPIM\modules\" _477CC96D36B140D78D269CF789F2B9BB="C:\Program
Files\sinpag\MPIM\bin\" _0A093580C456483BAB174F9F62F4AB
35="C:\Program Files\sinpag\MPIM\lib\"
_C094BE8D64E74E87A8D0E1A2FEA633B3="C:\Program Files\sinpag\MPIM\conf\"
_9823290E7B79499AB18187A93CA1792F="C:\Program Files\sinpag\MPIM\cgi-bin\"
_CBF2D77DDC5A49E6AEBA1D20CF7D2D08="C:\Program Files\sinpag\MPIM\logs\"
_390CBC155305424BA11416F2C242DBA0="C:\Program Files\sinpag\MPIM\conf\ssl\"
_15F7195FBC43449BA29B18250A126173="C:\Program Files\sinpag\MPIM\htdocs\"
CURRENTDIRECTORY="H:\install\mPIM\Connecteur" CLIENTUILEVEL="0"
CLIENTPROCESSID="1768" USERNAME="SFR" COMPA
NYNAME="Cegetel" SOURCEDIR="H:\install\mPIM\Connecteur\" ACTION="INSTALL"
EXECUTEACTION="INSTALL" ROOTDRIVE="H:\" INSTALLLEVEL="1" ALLUSERS="2"
SECONDSEQUENCE="1" ADDLOCAL=DefaultFeature
MSI (s) (FC:D4): Resetting cached policy values
MSI (s) (FC:D4): Machine policy value 'Debug' is 7
MSI (s) (FC:D4): ******* RunEngine:
******* Product: H:\install\mPIM\Connecteur\linkuallServer.msi
******* Action: INSTALL
******* CommandLine: TARGETDIR="C:\Program Files\sinpag\MPIM\"
_47AD186AAB5C42B181B1E21422CFF03B
="C:\Program Files\sinpag\MPIM\modules\"
_477CC96D36B140D78D269CF789F2B9BB="C:\Program Files\sinpag\MPIM\bin\"
_0A093580C456483BAB174F9F62F4AB35="C:\Program Files\sinpag\MPIM\lib\"
_C094BE8D64E74E87A8D0E1A2FEA633B3="C:\Program Files\sinpag\MPIM\conf\" _98
23290E7B79499AB18187A93CA1792F="C:\Program Files\sinpag\MPIM\cgi-bin\"
_CBF2D77DDC5A49E6AEBA1D20CF7D2D08="C:\Program Files\sinpag\MPIM\logs\"
_390CBC155305424BA11416F2C242DBA0="C:\Program Files\sinpag\MPIM\conf\ssl\"
_15F7195FBC43449BA29B18250A126173="C:\
Program Files\sinpag\MPIM\htdocs\"
CURRENTDIRECTORY="H:\install\mPIM\Connecteur" CLIENTUILEVEL="0"
CLIENTPROCESSID="1768" USERNAME="SFR" COMPANYNAME="Cegetel"
SOURCEDIR="H:\install\mPIM\Connecteur\" ACTION="INSTALL"
EXECUTEACTION="INSTALL" ROOTDRIVE="H:\"
INSTALLLEVEL="1" ALL
MSI (s) (FC:D4): Machine policy value 'DisableUserInstalls' is 0
MSI (s) (FC:D4): Setting cached product context: machine assigned for
product: 4F4A3A53297B6D117AA8000B0D410201
MSI (s) (FC:D4): Using cached product context: machine assigned for product:
4F4A3A53297B6D117AA8000B0D410201
MSI (s) (FC:D4): Setting cached product context: machine assigned for
product: 68AB67CA7DA73301B744000000000010
MSI (s) (FC:D4): Using cached product context: machine assigned for product:
68AB67CA7DA73301B744000000000010
MSI (s) (FC:D4): Setting cached product context: machine assigned for
product: 8A0F841731866D117AB7000B0D410201
MSI (s) (FC:D4): Using cached product context: machine assigned for product:
8A0F841731866D117AB7000B0D410201
MSI (s) (FC:D4): Setting cached product context: machine assigned for
product: C838BEBA7A1AD5C47B1EB83441066020
MSI (s) (FC:D4): Using cached product context: machine assigned for product:
C838BEBA7A1AD5C47B1EB83441066020
MSI (s) (FC:D4): Setting cached product context: machine assigned for
product: C8D617F6F8933D11581E000540386890
MSI (s) (FC:D4): Using cached product context: machine assigned for product:
C8D617F6F8933D11581E000540386890
MSI (s) (FC:D4): File will have security applied from OpCode.
MSI (s) (FC:D4): End dialog not enabled
MSI (s) (FC:D4): Original package ==>
H:\install\mPIM\Connecteur\linkuallServer.msi
MSI (s) (FC:D4): Package we're running from ==>
C:\WINNT\Installer\652953d.msi
MSI (s) (FC:D4): APPCOMPAT: looking for appcompat database entry with
ProductCode '{9475BFDC-32F3-4514-9625-40F08EAF490A}'.
MSI (s) (FC:D4): APPCOMPAT: no matching ProductCode found in database.
MSI (s) (FC:D4): Machine policy value 'TransformsSecure' is 0
MSI (s) (FC:D4): User policy value 'TransformsAtSource' is 0
MSI (s) (FC:D4): APPCOMPAT: looking for appcompat database entry with
ProductCode '{9475BFDC-32F3-4514-9625-40F08EAF490A}'.
MSI (s) (FC:D4): APPCOMPAT: no matching ProductCode found in database.
MSI (s) (FC:D4): Transforms are not secure.
MSI (s) (FC:D4): Command Line: TARGETDIR=C:\Program Files\sinpag\MPIM\
_47AD186AAB5C42B181B1E21422CFF03B=C:\Program Files\sinpag\MPIM\modules\
_477CC96D36B140D78D269CF789F2B9BB=C:\Program Files\sinpag\MPIM\bin\
_0A093580C456483BAB174F9F62F4AB35=C:\Program
Files\sinpag\MPIM\lib\ _C094BE8D64E74E87A8D0E1A2FEA633B3=C:\Program
Files\sinpag\MPIM\conf\ _9823290E7B79499AB18187A93CA1792F=C:\Program
Files\sinpag\MPIM\cgi-bin\ _CBF2D77DDC5A49E6AEBA1D20CF7D2D08=C:\Program
Files\sinpag\MPIM\logs\ _390CBC155305424BA114
16F2C242DBA0=C:\Program Files\sinpag\MPIM\conf\ssl\
_15F7195FBC43449BA29B18250A126173=C:\Program Files\sinpag\MPIM\htdocs\
CURRENTDIRECTORY=H:\install\mPIM\Connecteur CLIENTUILEVEL=0
CLIENTPROCESSID=1768 USERNAME=SFR COMPANYNAME=Cegetel SOURCEDIR=H:\insta
ll\mPIM\Connecteur\ ACTION=INSTALL EXECUTEACTION=INSTALL ROOTDRIVE=H:\
INSTALLLEVEL=1 ALLUSERS=2 SECONDSEQUENCE=1 ADDLOCAL=DefaultFeature
%HOMEPATH=\Documents and Settings\administrateur %HOMEDRIVE=C: %HOMESHARE=
ACTION=INSTALL
MSI (s) (FC:D4): Product Code passed to Engine.Initialize: ''
MSI (s) (FC:D4): Product Code from property table before transforms:
'{9475BFDC-32F3-4514-9625-40F08EAF490A}'
MSI (s) (FC:D4): Product Code from property table after transforms:
'{9475BFDC-32F3-4514-9625-40F08EAF490A}'
MSI (s) (FC:D4): Product not registered: beginning first-time install
MSI (s) (FC:D4): Entering CMsiConfigurationManager::SetLastUsedSource.
MSI (s) (FC:D4): User policy value 'SearchOrder' is 'nmu'
MSI (s) (FC:D4): Adding new sources is allowed.
MSI (s) (FC:D4): Package name extracted from package path:
'linkuallServer.msi'
MSI (s) (FC:D4): Package to be registered: 'linkuallServer.msi'
MSI (s) (FC:D4): Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2729
MSI (s) (FC:D4): Note: 1: 2729
MSI (s) (FC:D4): Note: 1: 2729
MSI (s) (FC:D4): Note: 1: 2729
MSI (s) (FC:D4): Note: 1: 2729
MSI (s) (FC:D4): Note: 1: 2729
MSI (s) (FC:D4): Note: 1: 2729
MSI (s) (FC:D4): Note: 1: 2729
MSI (s) (FC:D4): Note: 1: 2729
MSI (s) (FC:D4): Note: 1: 2729
MSI (s) (FC:D4): Note: 1: 2729
MSI (s) (FC:D4): Note: 1: 2729
MSI (s) (FC:D4): Note: 1: 2729
MSI (s) (FC:D4): Note: 1: 2729
MSI (s) (FC:D4): Note: 1: 2729
MSI (s) (FC:D4): Note: 1: 2729
MSI (s) (FC:D4): Note: 1: 2262 2: AdminProperties 3: -2147287038
MSI (s) (FC:D4): Machine policy value 'DisableMsi' is 0
MSI (s) (FC:D4): Machine policy value 'AlwaysInstallElevated' is 0
MSI (s) (FC:D4): User policy value 'AlwaysInstallElevated' is 0
MSI (s) (FC:D4): Product installation will be elevated because user is admin
and product is being installed per-machine.
MSI (s) (FC:D4): Running product '{9475BFDC-32F3-4514-9625-40F08EAF490A}'
with elevated privileges: Product is assigned.
MSI (s) (FC:D4): Engine has iefSecondSequence set to true.
MSI (s) (FC:D4): TRANSFORMS property is now:
MSI (s) (FC:D4): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\administrateur\Application Data
MSI (s) (FC:D4): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\administrateur\Favorites
MSI (s) (FC:D4): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\administrateur\NetHood
MSI (s) (FC:D4): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\administrateur\My Documents
MSI (s) (FC:D4): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\administrateur\PrintHood
MSI (s) (FC:D4): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\administrateur\Recent
MSI (s) (FC:D4): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\administrateur\SendTo
MSI (s) (FC:D4): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\administrateur\Templates
MSI (s) (FC:D4): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\All Users\Application Data
MSI (s) (FC:D4): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\administrateur\Local Settings\Application Data
MSI (s) (FC:D4): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\administrateur\My Documents\My Pictures
MSI (s) (FC:D4): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\All Users\Start Menu\Programs\Administrative Tools
MSI (s) (FC:D4): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\All Users\Start Menu\Programs\Startup
MSI (s) (FC:D4): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\All Users\Start Menu\Programs
MSI (s) (FC:D4): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\All Users\Start Menu
MSI (s) (FC:D4): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\All Users\Desktop
MSI (s) (FC:D4): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\administrateur\Start Menu\Programs\Administrative Tools
MSI (s) (FC:D4): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\administrateur\Start Menu\Programs\Startup
MSI (s) (FC:D4): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\administrateur\Start Menu\Programs
MSI (s) (FC:D4): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\administrateur\Start Menu
MSI (s) (FC:D4): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\administrateur\Desktop
MSI (s) (FC:D4): SHELL32::SHGetFolderPath returned: C:\Documents and
Settings\All Users\Templates
MSI (s) (FC:D4): SHELL32::SHGetFolderPath returned: C:\WINNT\Fonts
MSI (s) (FC:D4): Note: 1: 2898 2: MS Sans Serif 3: MS Sans Serif 4: 0 5: 16
MSI (s) (FC:D4): MSCOREE not loaded loading copy from system32
MSI (s) (FC:D4): Machine policy value 'DisableRollback' is 0
MSI (s) (FC:D4): User policy value 'DisableRollback' is 0
MSI (s) (FC:D4): Doing action: INSTALL
MSI (s) (FC:D4): Note: 1: 2262 2: ActionText 3: -2147287038
Action start 17:18:58: INSTALL.
MSI (s) (FC:D4): Running ExecuteSequence
MSI (s) (FC:D4): Doing action: AppSearch
Action start 17:18:58: AppSearch.
MSI (s) (FC:D4): Skipping AppSearch action: already done on client side
Action ended 17:18:58: AppSearch. Return value 0.
MSI (s) (FC:D4): Doing action: FindRelatedProducts
Action start 17:18:58: FindRelatedProducts.
MSI (s) (FC:D4): Skipping FindRelatedProducts action: already done on client
side
Action ended 17:18:58: FindRelatedProducts. Return value 0.
MSI (s) (FC:D4): Skipping action: ERRCA_CANCELNEWERVERSION (condition is
false)
MSI (s) (FC:D4): Doing action: LaunchConditions
Action start 17:18:58: LaunchConditions.
MSI (s) (FC:D4): Note: 1: 2262 2: LaunchCondition 3: -2147287038
Action ended 17:18:58: LaunchConditions. Return value 1.
MSI (s) (FC:D4): Doing action: CCPSearch
Action start 17:18:58: CCPSearch.
MSI (s) (FC:D4): Skipping CCPSearch action: already done on client side
Action ended 17:18:58: CCPSearch. Return value 0.
MSI (s) (FC:D4): Doing action: RMCCPSearch
Action start 17:18:58: RMCCPSearch.
MSI (s) (FC:D4): Skipping RMCCPSearch action: already done on client side
Action ended 17:18:58: RMCCPSearch. Return value 0.
MSI (s) (FC:D4): Doing action: ValidateProductID
Action start 17:18:58: ValidateProductID.
Action ended 17:18:58: ValidateProductID. Return value 1.
MSI (s) (FC:D4): Skipping action: DIRCA_TARGETDIR (condition is false)
MSI (s) (FC:D4): Doing action: CostInitialize
Action start 17:18:58: CostInitialize.
Action ended 17:18:58: CostInitialize. Return value 1.
MSI (s) (FC:D4): Doing action: FileCost
Action start 17:18:58: FileCost.
MSI (s) (FC:D4): Note: 1: 2262 2: RemoveFile 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: MsiAssembly 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: Class 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: Extension 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: TypeLib 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: IniFile 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: MoveFile 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: DuplicateFile 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: ReserveCost 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: Shortcut 3: -2147287038
Action ended 17:18:58: FileCost. Return value 1.
MSI (s) (FC:D4): Doing action: IsolateComponents
Action start 17:18:58: IsolateComponents.
MSI (s) (FC:D4): Note: 1: 2262 2: IsolatedComponent 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: BindImage 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: Patch 3: -2147287038
Action ended 17:18:58: IsolateComponents. Return value 1.
MSI (s) (FC:D4): Doing action: CostFinalize
Action start 17:18:58: CostFinalize.
MSI (s) (FC:D4): Note: 1: 2262 2: Patch 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: Condition 3: -2147287038
MSI (s) (FC:D4): Target path resolution complete. Dumping Directory table...
MSI (s) (FC:D4): Note: target paths subject to change (via custom actions or
browsing)
MSI (s) (FC:D4): Dir (target): Key: TARGETDIR , Object: C:\Program
Files\sinpag\MPIM\
MSI (s) (FC:D4): Dir (target): Key: WindowsFolder , Object: C:\WINNT\
MSI (s) (FC:D4): Dir (target): Key: DesktopFolder , Object: C:\Documents and
Settings\All Users\Desktop\
MSI (s) (FC:D4): Dir (target): Key: ProgramMenuFolder , Object: C:\Documents
and Settings\All Users\Start Menu\Programs\
MSI (s) (FC:D4): Dir (target): Key: _15F7195FBC43449BA29B18250A126173 ,
Object: C:\Program Files\sinpag\MPIM\htdocs\
MSI (s) (FC:D4): Dir (target): Key: _CBF2D77DDC5A49E6AEBA1D20CF7D2D08 ,
Object: C:\Program Files\sinpag\MPIM\logs\
MSI (s) (FC:D4): Dir (target): Key: SystemFolder , Object:
C:\WINNT\system32\
MSI (s) (FC:D4): Dir (target): Key: _9823290E7B79499AB18187A93CA1792F ,
Object: C:\Program Files\sinpag\MPIM\cgi-bin\
MSI (s) (FC:D4): Dir (target): Key: _C094BE8D64E74E87A8D0E1A2FEA633B3 ,
Object: C:\Program Files\sinpag\MPIM\conf\
MSI (s) (FC:D4): Dir (target): Key: _390CBC155305424BA11416F2C242DBA0 ,
Object: C:\Program Files\sinpag\MPIM\conf\ssl\
MSI (s) (FC:D4): Dir (target): Key: _0A093580C456483BAB174F9F62F4AB35 ,
Object: C:\Program Files\sinpag\MPIM\lib\
MSI (s) (FC:D4): Dir (target): Key: _477CC96D36B140D78D269CF789F2B9BB ,
Object: C:\Program Files\sinpag\MPIM\bin\
MSI (s) (FC:D4): Dir (target): Key: _47AD186AAB5C42B181B1E21422CFF03B ,
Object: C:\Program Files\sinpag\MPIM\modules\
Action ended 17:18:58: CostFinalize. Return value 1.
MSI (s) (FC:D4): Doing action: SetODBCFolders
Action start 17:18:58: SetODBCFolders.
MSI (s) (FC:D4): Note: 1: 2262 2: ODBCDriver 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: ODBCTranslator 3: -2147287038
Action ended 17:18:58: SetODBCFolders. Return value 1.
MSI (s) (FC:D4): Doing action: InstallValidate
Action start 17:18:58: InstallValidate.
MSI (s) (FC:D4): Feature: DefaultFeature; Installed: Absent; Request:
Local; Action: Local
MSI (s) (FC:D4): Component: C__0070E254E7F54E5CBBF4DFEA0A8DF3EB; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__02CF39D7FDA7460A9BEFFB9C9B621427; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__047B5CE8CB1E4126B320D79139F1A396; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__0EB88DC8FC424F668C5C1C560498CA14; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__0F1D0E0EFDF84BCE89E73830D330511B; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__10A098ABC0C643DA825A7E005DDD5BD1; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__174F663D46E043589ABB596184F8182A; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__1A0DB8A9BE9E41DAA9F04F02085BC313; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__1D0C6FB995204F3F91EB657432DCCDF5; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__1EC92CE1D8C748EEA0CE6304A2414DE0; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__224B91D1C60548F7BEDA1CF2F177E811; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__285508AEA1E5471E8C43C8F0B1FA29F9; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__29D9B000F22B4EC5A614BB1E643C3069; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__2DA6CAAFDB044EA59F1602DAE7594794; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__328CF043559A4CFBA9BFC761DE0EB547; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__367E3805B46B4F9194E0D4E5B1E02C2D; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__381BABE4BFC4420CA3B82831AB37DEA6; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__3C476827AF7A48A0839FE11721AC5512; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__3DBD2E3C0F7C46AEBE71571C199DE64A; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__4148A6BEACD94709984EF4E733DC03B1; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__45442285720A47A6A5DAEB77F3F50A5A; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__459042D2D4984081A5B2689773808B73; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__5146801ED862483A91D11B0CD18BC4C7; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__52DF97F82F5042F884C975E94213D712; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__536296DD2F2E4478B6DB545C390846E4; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__537FE51FFB9741C7991D8BAD8B7C5162; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__55C7A65E3A104908A4FB445F7B516F99; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__56AC26868A4E4888874C4916472E1798; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__5CF664F2D79F4C69852B6582363DB0F9; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__5D39799F17DF45E791FCA6A682C921E2; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__5E9B3A7CFC454F3186D1C648F205F7B9; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__67860AD491504CFA9A3603B1A4E1FEB9; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__69C4F4876E434645976210CD4DA0FEDE; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__6CC2B9996B8F4A6BB7659D5375AE656F; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__6E22A6C19358439794DAE0437E0C9B6D; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__717F68A41D3641BCBA21CCF871C095AD; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__7AAC42C2794E4D7A9A5635618714039C; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__83869182505346568B556634DEB80000; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__848F91747B99442B912918E5C536E4EA; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__86DA0F240F0249C38B7F2C25E96ADADD; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__87402597812E47D09D703335489E8FC0; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__8A3092FF1DD347C182F4851097D72FBC; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__8ABC302C7B684EAD88A0D7837D77B2BA; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__8BBE17B301D34B05957FEE88909D6DCE; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__8D05894E28B24658A720358515A66C56; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__8DAA9647F1EC48749E234EFF8B1E5ED6; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__8E5B351A10B2434B9078EECB79AB7CA7; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__8F4E17688D0B4186A6F795603D012193; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__91DF0C943C574852AF5001503F7C14C0; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__93A85FF128DD405BB87D01BD4C4BF1B8; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__93F643ABDF124702AFC9EA8180942475; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__999A2C1E6A834F15BA0908A93944813D; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__9CCCBEDBEEAA4983A744F0C3CBB1C669; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__A10076D1C544455199B2575E02CD888E; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__A3E9FEBEBEE941E1AFFF07A890DBA14F; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__A5A434DC64AA4475A07947F345DD4D10; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__A5C8F55D3F7F4309B55FB264F0F8EEF8; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__A76FFA837CF6492E8F001F316036DE2E; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__A7A5DFB9B11F4275A66BF0D3E65FDDA8; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__AB14F6B8CA8F4E659A369A1345973651; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__B496F9FF860243C58D624BA23B558727; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__B8F3433CFA5A417A9F46E4DB8AF886A5; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__BA14B067663B49D19A73477DEC03A9FF; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__BE5C04CB26B746CE83F35B965DD5FB59; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__C1632818387642B897C82E98EBF352C2; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__C32EE660DBCD450F82009D40200CB364; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__C45A8BAD4EEE4B73B7E2C7010B73B4F5; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__C97CA1220E394ABDA73EA979BE19F674; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__C9A9E5358A974C9AB2FC308525169C82; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__CE805453C0964A2F8EADA2EEB71548B5; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__D2DFE0C9FF5D45FCB218E2BB59D7F505; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__D5C0D9C65DFB4B4D966D987637BACF50; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__D5EF6BDF02104C1389B6E5FE4948335E; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__D7725F87BFC44D7E81F021E0AEAC2229; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__DCEEEC6AF2304C488A99A7060D342DA1; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__DF202912D1394EF8BE1F0022B1D8EE6A; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__DF33D39B9AC24C00AD4AEE30C012666A; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__E05B5164C50045608B1A06E2ABA1C594; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__E1064B9B5DE84747B941F68AF1A5AD85; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__E3540FB778F44CF4BB97A68FABF399FB; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__E5F07A8EB503446E8F090911D8A8B9D7; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__E9EA53E4A182413D8067DB365DA237D5; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__EA196B9A5950434589C0257DBFBBF89B; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__EA69637125424866A4BEC227CD2C3992; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__F85F6E486D4047F38A9ACBB55EB43A42; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__FB170200BDB34EC9809A729FFBEFAE66; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__FB35010A241844488C8D48276FC5C305; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__D695A7A0245D42E3ADEF9580EB5E5E6C; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__7B1FAEF75EB1435A89ACFABA6F90B897; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__8F9E28EC22C1497EB5EE9BDA6C1F6DC4; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: C__14A10D9574494257AE776F2FE3DE5246; Installed:
Absent; Request: Local; Action: Local
MSI (s) (FC:D4): Component: __C__D695A7A0245D42E3ADEF9580EB5E5E6C65;
Installed: Null; Request: Local; Action: Local
MSI (s) (FC:D4): Component: __C__7B1FAEF75EB1435A89ACFABA6F90B89765;
Installed: Null; Request: Local; Action: Local
MSI (s) (FC:D4): Component: __C__8F9E28EC22C1497EB5EE9BDA6C1F6DC465;
Installed: Null; Request: Local; Action: Local
MSI (s) (FC:D4): Component: __C__14A10D9574494257AE776F2FE3DE524665;
Installed: Null; Request: Local; Action: Local
MSI (s) (FC:D4): Note: 1: 2262 2: BindImage 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: ProgId 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: PublishComponent 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: SelfReg 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: Extension 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: Font 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: Shortcut 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: Class 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: RemoveFile 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2205 2: 3: _RemoveFilePath
MSI (s) (FC:D4): Note: 1: 2262 2: MsiFileHash 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: RemoveFile 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: DuplicateFile 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: MoveFile 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: ReserveCost 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: Shortcut 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: TypeLib 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: Class 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: Extension 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: Class 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: Extension 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: Class 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: Extension 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: Class 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: Extension 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: BindImage 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: ProgId 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: PublishComponent 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: SelfReg 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: Extension 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: Font 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: Class 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2205 2: 3: #_PatchCache
MSI (s) (FC:D4): Note: 1: 2228 2: 3: #_PatchCache 4: SELECT `TempCopy` FROM
`#_PatchCache` ORDER BY `Sequence`
MSI (s) (FC:D4): Note: 1: 2727 2:
MSI (s) (FC:D4): Note: 1: 2727 2:
Action ended 17:18:58: InstallValidate. Return value 1.
MSI (s) (FC:D4): Doing action: InstallInitialize
Action start 17:18:59: InstallInitialize.
MSI (s) (FC:D4): Machine policy value 'AlwaysInstallElevated' is 0
MSI (s) (FC:D4): User policy value 'AlwaysInstallElevated' is 0
MSI (s) (FC:D4): BeginTransaction: Locking Server
MSI (s) (FC:D4): Server not locked: locking for product
{9475BFDC-32F3-4514-9625-40F08EAF490A}
MSI (s) (FC:D4): Opening Terminal Server registry propogation window.
Action ended 17:18:59: InstallInitialize. Return value 1.
MSI (s) (FC:D4): Doing action: RemoveExistingProducts
Action start 17:18:59: RemoveExistingProducts.
MSI (s) (FC:D4): Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: Error 3: -2147287038
Action ended 17:18:59: RemoveExistingProducts. Return value 1.
MSI (s) (FC:D4): Doing action: AllocateRegistrySpace
Action start 17:18:59: AllocateRegistrySpace.
Action ended 17:18:59: AllocateRegistrySpace. Return value 1.
MSI (s) (FC:D4): Doing action: ProcessComponents
Action start 17:18:59: ProcessComponents.
MSI (s) (FC:D4): Resolving source.
MSI (s) (FC:D4): Resolving source to launched-from source.
MSI (s) (FC:D4): Setting launched-from source as last-used.
MSI (s) (FC:D4): SOURCEDIR ==> H:\install\mPIM\Connecteur\
MSI (s) (FC:D4): SOURCEDIR product ==>
{9475BFDC-32F3-4514-9625-40F08EAF490A}
MSI (s) (FC:D4): Determining source type
MSI (s) (FC:D4): Source type from package 'linkuallServer.msi': 2
MSI (s) (FC:D4): Source path resolution complete. Dumping Directory table...
MSI (s) (FC:D4): Dir (source): Key: TARGETDIR , Object:
H:\install\mPIM\Connecteur\ , LongSubPath: , ShortSubPath:
MSI (s) (FC:D4): Dir (source): Key: WindowsFolder , Object:
H:\install\mPIM\Connecteur\ , LongSubPath: , ShortSubPath:
MSI (s) (FC:D4): Dir (source): Key: DesktopFolder , Object:
H:\install\mPIM\Connecteur\ , LongSubPath: User's Desktop\ , ShortSubPath:
USER'S~2\
MSI (s) (FC:D4): Dir (source): Key: ProgramMenuFolder , Object:
H:\install\mPIM\Connecteur\ , LongSubPath: User's Programs Menu\ ,
ShortSubPath: USER'S~1\
MSI (s) (FC:D4): Dir (source): Key: _15F7195FBC43449BA29B18250A126173 ,
Object: H:\install\mPIM\Connecteur\ , LongSubPath: htdocs\ , ShortSubPath:
HTDOCS\
MSI (s) (FC:D4): Dir (source): Key: _CBF2D77DDC5A49E6AEBA1D20CF7D2D08 ,
Object: H:\install\mPIM\Connecteur\ , LongSubPath: logs\ , ShortSubPath:
LOGS\
MSI (s) (FC:D4): Dir (source): Key: SystemFolder , Object:
H:\install\mPIM\Connecteur\ , LongSubPath: System Folder\ , ShortSubPath:
SYSTEM~1\
MSI (s) (FC:D4): Dir (source): Key: _9823290E7B79499AB18187A93CA1792F ,
Object: H:\install\mPIM\Connecteur\ , LongSubPath: cgi-bin\ , ShortSubPath:
CGI-BIN\
MSI (s) (FC:D4): Dir (source): Key: _C094BE8D64E74E87A8D0E1A2FEA633B3 ,
Object: H:\install\mPIM\Connecteur\ , LongSubPath: conf\ , ShortSubPath:
CONF\
MSI (s) (FC:D4): Dir (source): Key: _390CBC155305424BA11416F2C242DBA0 ,
Object: H:\install\mPIM\Connecteur\ , LongSubPath: conf\ssl\ , ShortSubPath:
CONF\SSL\
MSI (s) (FC:D4): Dir (source): Key: _0A093580C456483BAB174F9F62F4AB35 ,
Object: H:\install\mPIM\Connecteur\ , LongSubPath: lib\ , ShortSubPath: LIB\
MSI (s) (FC:D4): Dir (source): Key: _477CC96D36B140D78D269CF789F2B9BB ,
Object: H:\install\mPIM\Connecteur\ , LongSubPath: bin\ , ShortSubPath: BIN\
MSI (s) (FC:D4): Dir (source): Key: _47AD186AAB5C42B181B1E21422CFF03B ,
Object: H:\install\mPIM\Connecteur\ , LongSubPath: modules\ , ShortSubPath:
MODULES\
Action 17:18:59: GenerateScript. Generating script operations for action:
GenerateScript: Updating component registration
Action ended 17:18:59: ProcessComponents. Return value 1.
MSI (s) (FC:D4): Doing action: MsiUnpublishAssemblies
Action start 17:18:59: MsiUnpublishAssemblies.
Action ended 17:18:59: MsiUnpublishAssemblies. Return value 1.
MSI (s) (FC:D4): Skipping action: _B0891831_CFEB_49A3_8F1B_EA7B529BD823
(condition is false)
MSI (s) (FC:D4): Skipping action: _3E43F35A_18EB_4809_BFF7_BBC1ED185BAC
(condition is false)
MSI (s) (FC:D4): Skipping action: _083C673A_FA25_4F97_8697_7A7254969941
(condition is false)
MSI (s) (FC:D4): Doing action: UnpublishComponents
Action start 17:18:59: UnpublishComponents.
MSI (s) (FC:D4): Note: 1: 2262 2: PublishComponent 3: -2147287038
Action ended 17:18:59: UnpublishComponents. Return value 1.
MSI (s) (FC:D4): Doing action: UnpublishFeatures
Action start 17:18:59: UnpublishFeatures.
Action ended 17:18:59: UnpublishFeatures. Return value 1.
MSI (s) (FC:D4): Doing action: StopServices
Action start 17:18:59: StopServices.
MSI (s) (FC:D4): Note: 1: 2262 2: ServiceControl 3: -2147287038
Action ended 17:18:59: StopServices. Return value 1.
MSI (s) (FC:D4): Doing action: DeleteServices
Action start 17:18:59: DeleteServices.
MSI (s) (FC:D4): Note: 1: 2262 2: ServiceControl 3: -2147287038
Action ended 17:18:59: DeleteServices. Return value 1.
MSI (s) (FC:D4): Doing action: UnregisterComPlus
Action start 17:18:59: UnregisterComPlus.
MSI (s) (FC:D4): Note: 1: 2262 2: Complus 3: -2147287038
Action ended 17:18:59: UnregisterComPlus. Return value 1.
MSI (s) (FC:D4): Doing action: SelfUnregModules
Action start 17:18:59: SelfUnregModules.
MSI (s) (FC:D4): Note: 1: 2262 2: SelfReg 3: -2147287038
Action ended 17:18:59: SelfUnregModules. Return value 1.
MSI (s) (FC:D4): Doing action: UnregisterTypeLibraries
Action start 17:18:59: UnregisterTypeLibraries.
Action ended 17:18:59: UnregisterTypeLibraries. Return value 1.
MSI (s) (FC:D4): Doing action: RemoveODBC
Action start 17:18:59: RemoveODBC.
MSI (s) (FC:D4): Note: 1: 2262 2: ODBCDataSource 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: ODBCDataSource 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: ODBCTranslator 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: ODBCTranslator 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: ODBCDriver 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: ODBCDriver 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2711 2: ODBCDriverManager
GenerateScript: Removing ODBC components
MSI (s) (FC:D4): Note: 1: 2711 2: ODBCDriverManager64
Action ended 17:19:00: RemoveODBC. Return value 1.
MSI (s) (FC:D4): Doing action: UnregisterFonts
Action start 17:19:00: UnregisterFonts.
MSI (s) (FC:D4): Note: 1: 2262 2: Font 3: -2147287038
Action ended 17:19:00: UnregisterFonts. Return value 1.
MSI (s) (FC:D4): Doing action: RemoveRegistryValues
Action start 17:19:00: RemoveRegistryValues.
MSI (s) (FC:D4): Note: 1: 2262 2: RemoveRegistry 3: -2147287038
Action ended 17:19:00: RemoveRegistryValues. Return value 1.
MSI (s) (FC:D4): Doing action: UnregisterClassInfo
Action start 17:19:00: UnregisterClassInfo.
MSI (s) (FC:D4): Note: 1: 2262 2: Class 3: -2147287038
Action ended 17:19:00: UnregisterClassInfo. Return value 1.
MSI (s) (FC:D4): Doing action: UnregisterExtensionInfo
Action start 17:19:00: UnregisterExtensionInfo.
MSI (s) (FC:D4): Note: 1: 2262 2: Extension 3: -2147287038
Action ended 17:19:00: UnregisterExtensionInfo. Return value 1.
MSI (s) (FC:D4): Doing action: UnregisterProgIdInfo
Action start 17:19:00: UnregisterProgIdInfo.
MSI (s) (FC:D4): Note: 1: 2262 2: ProgId 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: Class 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: ProgId 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: Extension 3: -2147287038
Action ended 17:19:00: UnregisterProgIdInfo. Return value 1.
MSI (s) (FC:D4): Doing action: UnregisterMIMEInfo
Action start 17:19:00: UnregisterMIMEInfo.
MSI (s) (FC:D4): Note: 1: 2262 2: MIME 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: Extension 3: -2147287038
Action ended 17:19:00: UnregisterMIMEInfo. Return value 1.
MSI (s) (FC:D4): Doing action: RemoveIniValues
Action start 17:19:00: RemoveIniValues.
MSI (s) (FC:D4): Note: 1: 2262 2: IniFile 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: RemoveIniFile 3: -2147287038
Action ended 17:19:00: RemoveIniValues. Return value 1.
MSI (s) (FC:D4): Doing action: RemoveShortcuts
Action start 17:19:00: RemoveShortcuts.
Action ended 17:19:00: RemoveShortcuts. Return value 1.
MSI (s) (FC:D4): Doing action: RemoveEnvironmentStrings
Action start 17:19:00: RemoveEnvironmentStrings.
MSI (s) (FC:D4): Note: 1: 2262 2: Environment 3: -2147287038
Action ended 17:19:00: RemoveEnvironmentStrings. Return value 1.
MSI (s) (FC:D4): Doing action: RemoveDuplicateFiles
Action start 17:19:00: RemoveDuplicateFiles.
Action ended 17:19:00: RemoveDuplicateFiles. Return value 1.
MSI (s) (FC:D4): Doing action: RemoveFiles
Action start 17:19:00: RemoveFiles.
Action ended 17:19:00: RemoveFiles. Return value 1.
MSI (s) (FC:D4): Doing action: RemoveFolders
Action start 17:19:00: RemoveFolders.
MSI (s) (FC:D4): Note: 1: 2262 2: CreateFolder 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: LockPermissions 3: -2147287038
Action ended 17:19:00: RemoveFolders. Return value 1.
MSI (s) (FC:D4): Doing action: CreateFolders
Action start 17:19:00: CreateFolders.
MSI (s) (FC:D4): Note: 1: 2262 2: CreateFolder 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: LockPermissions 3: -2147287038
Action ended 17:19:00: CreateFolders. Return value 1.
MSI (s) (FC:D4): Doing action: MoveFiles
Action start 17:19:00: MoveFiles.
Action ended 17:19:00: MoveFiles. Return value 1.
MSI (s) (FC:D4): Doing action: InstallFiles
Action start 17:19:00: InstallFiles.
GenerateScript: Copying new files
MSI (s) (FC:D4): Note: 1: 2262 2: LockPermissions 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: Patch 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2205 2: 3: MsiPatchOldAssemblyFile
MSI (s) (FC:D4): Note: 1: 2228 2: 3: MsiPatchOldAssemblyFile 4: SELECT
`MsiPatchOldAssemblyFile`.`Assembly_` FROM `MsiPatchOldAssemblyFile` WHERE
`MsiPatchOldAssemblyFile`.`File_` = ?
MSI (s) (FC:D4): Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2205 2: 3: MsiSFCBypass
MSI (s) (FC:D4): Note: 1: 2228 2: 3: MsiSFCBypass 4: SELECT `File_` FROM
`MsiSFCBypass` WHERE `File_` = ?
MSI (s) (FC:D4): Note: 1: 2262 2: MsiPatchHeaders 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2205 2: 3: SidCache
MSI (s) (FC:D4): Using well known SID for System
MSI (s) (FC:D4): Finished allocating new user SID
Action ended 17:19:00: InstallFiles. Return value 1.
MSI (s) (FC:D4): Doing action: PatchFiles
Action start 17:19:00: PatchFiles.
MSI (s) (FC:D4): Note: 1: 2262 2: Patch 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: Error 3: -2147287038
Action ended 17:19:00: PatchFiles. Return value 1.
MSI (s) (FC:D4): Doing action: DuplicateFiles
Action start 17:19:00: DuplicateFiles.
Action ended 17:19:00: DuplicateFiles. Return value 1.
MSI (s) (FC:D4): Doing action: BindImage
Action start 17:19:00: BindImage.
MSI (s) (FC:D4): Note: 1: 2262 2: BindImage 3: -2147287038
Action ended 17:19:00: BindImage. Return value 1.
MSI (s) (FC:D4): Doing action: CreateShortcuts
Action start 17:19:00: CreateShortcuts.
Action ended 17:19:00: CreateShortcuts. Return value 1.
MSI (s) (FC:D4): Doing action: RegisterClassInfo
Action start 17:19:00: RegisterClassInfo.
MSI (s) (FC:D4): Note: 1: 2262 2: Class 3: -2147287038
Action ended 17:19:00: RegisterClassInfo. Return value 1.
MSI (s) (FC:D4): Doing action: RegisterExtensionInfo
Action start 17:19:00: RegisterExtensionInfo.
MSI (s) (FC:D4): Note: 1: 2262 2: Extension 3: -2147287038
Action ended 17:19:00: RegisterExtensionInfo. Return value 1.
MSI (s) (FC:D4): Doing action: RegisterProgIdInfo
Action start 17:19:00: RegisterProgIdInfo.
MSI (s) (FC:D4): Note: 1: 2262 2: ProgId 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: Class 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: ProgId 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: Extension 3: -2147287038
Action ended 17:19:00: RegisterProgIdInfo. Return value 1.
MSI (s) (FC:D4): Doing action: RegisterMIMEInfo
Action start 17:19:00: RegisterMIMEInfo.
MSI (s) (FC:D4): Note: 1: 2262 2: MIME 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: Extension 3: -2147287038
Action ended 17:19:00: RegisterMIMEInfo. Return value 1.
MSI (s) (FC:D4): Doing action: WriteRegistryValues
Action start 17:19:00: WriteRegistryValues.
GenerateScript: Writing system registry values
MSI (s) (FC:D4): Note: 1: 2262 2: LockPermissions 3: -2147287038
Action ended 17:19:00: WriteRegistryValues. Return value 1.
MSI (s) (FC:D4): Doing action: WriteIniValues
Action start 17:19:00: WriteIniValues.
MSI (s) (FC:D4): Note: 1: 2262 2: IniFile 3: -2147287038
Action ended 17:19:00: WriteIniValues. Return value 1.
MSI (s) (FC:D4): Doing action: WriteEnvironmentStrings
Action start 17:19:00: WriteEnvironmentStrings.
MSI (s) (FC:D4): Note: 1: 2262 2: Environment 3: -2147287038
Action ended 17:19:00: WriteEnvironmentStrings. Return value 1.
MSI (s) (FC:D4): Doing action: RegisterFonts
Action start 17:19:00: RegisterFonts.
MSI (s) (FC:D4): Note: 1: 2262 2: Font 3: -2147287038
Action ended 17:19:00: RegisterFonts. Return value 1.
MSI (s) (FC:D4): Doing action: InstallODBC
Action start 17:19:00: InstallODBC.
MSI (s) (FC:D4): Note: 1: 2711 2: ODBCDriverManager
MSI (s) (FC:D4): Note: 1: 2711 2: ODBCDriverManager64
MSI (s) (FC:D4): Note: 1: 2262 2: ODBCDriver 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: ODBCAttribute 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: ODBCDriver 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: ODBCAttribute 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: ODBCTranslator 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: ODBCTranslator 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: ODBCDataSource 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: ODBCSourceAttribute 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: ODBCDataSource 3: -2147287038
MSI (s) (FC:D4): Note: 1: 2262 2: ODBCSourceAttribute 3: -2147287038
Action ended 17:19:00: InstallODBC. Return value 0.
MSI (s) (FC:D4): Doing action: RegisterTypeLibraries
Action start 17:19:00: RegisterTypeLibraries.
Action ended 17:19:00: RegisterTypeLibraries. Return value 1.
MSI (s) (FC:D4): Doing action: SelfRegModules
Action start 17:19:00: SelfRegModules.
MSI (s) (FC:D4): Note: 1: 2262 2: SelfReg 3: -2147287038
Action ended 17:19:00: SelfRegModules. Return value 1.
MSI (s) (FC:D4): Doing action: RegisterComPlus
Action start 17:19:00: RegisterComPlus.
MSI (s) (FC:D4): Note: 1: 2262 2: Complus 3: -2147287038
Action ended 17:19:00: RegisterComPlus. Return value 1.
MSI (s) (FC:D4): Doing action: InstallServices
Action start 17:19:00: InstallServices.
MSI (s) (FC:D4): Note: 1: 2262 2: ServiceInstall 3: -2147287038
Action ended 17:19:00: InstallServices. Return value 1.
MSI (s) (FC:D4): Doing action: StartServices
Action start 17:19:00: StartServices.
MSI (s) (FC:D4): Note: 1: 2262 2: ServiceControl 3: -2147287038
Action ended 17:19:00: StartServices. Return value 1.
MSI (s) (FC:D4): Doing action: _9F3718B3_8DFD_43D3_BE61_938254DD58F5
Action start 17:19:00: _9F3718B3_8DFD_43D3_BE61_938254DD58F5.
MSI (s) (FC:D4): Not impersonating action for per-machine Win2000 TS
install.
GenerateScript: _9F3718B3_8DFD_43D3_BE61_938254DD58F5
Action ended 17:19:00: _9F3718B3_8DFD_43D3_BE61_938254DD58F5. Return value
1.
MSI (s) (FC:D4): Doing action: _F80C6BF7_CB0C_40BA_8B67_A0AF58ADA20F
Action start 17:19:00: _F80C6BF7_CB0C_40BA_8B67_A0AF58ADA20F.
MSI (s) (FC:D4): Not impersonating action for per-machine Win2000 TS
install.
GenerateScript: _F80C6BF7_CB0C_40BA_8B67_A0AF58ADA20F
Action ended 17:19:00: _F80C6BF7_CB0C_40BA_8B67_A0AF58ADA20F. Return value
1.
MSI (s) (FC:D4): Doing action: _CF3F1B2D_120C_4295_B775_59B04D3DB93D
Action start 17:19:00: _CF3F1B2D_120C_4295_B775_59B04D3DB93D.
MSI (s) (FC:D4): Not impersonating action for per-machine Win2000 TS
install.
GenerateScript: _CF3F1B2D_120C_4295_B775_59B04D3DB93D
--
Paul Bacelar

Phil Wilson said:
Could you post the rest of the log around there? That may just apply to a
particular action.
--
Phil Wilson [MVP Windows Installer]
----
Paul Bacelar said:
Yes, but why my custom actions weren't impersonate with one policy and were
impersonate with another policy.

"AlwaysInstallElevated" policy attribute don't seem involved.

In MSI Log of unsuccessful install, I see this strange line:

"MSI (s) (FC:D4): Not impersonating action for per-machine Win2000 TS
install."

It's a legal situation or TS (Terminal Server) installation isn't
successfully terminated?
--
Paul Bacelar


Phil Wilson said:
Because when the installer service is updating the system from the data in
the MSI tables, the security is mostly controlled by policy rather than by
the user privileges. When the installer calls custom actions it *does*
impersonate the calling user.
--
Phil Wilson
[MVP Windows Installer]
Hi and happy good year,



I use a msi file, generated by a VS.NET deployment project, to
Click to expand...
install
my
components.



My problem is:

My setup.exe is launched by a user having extra rights on the Exchange
Server of domain, extra rights which allows my install procedure, via
"MyServiceName /Service", to request the Exchange Server. But, on a
"Win2000
Server With Final Server" machine into my customer test domain, the
install
process (my service) isn't processed under my initial user context but
under
a "NT AUTHORITY\System" context, account of "Windows Installer" service.
"Windows Installer" service probably refuses to impersonalize my
installation program. I didn't reproduce this behaviour on my test
platform.

The "AlwaysInstallElevated" group policies (user and machine) don't seem
to
influence the "Windows Installer" impersonalization. In brief, Why
"Windows
Installer" doesn't keep the security context of the installation
Click to expand...
program
(setup.exe) and which are the parameters which influence its behaviour
from
the security point of view?



Thank you, for your suggestions.



--
Paul Bacelar



PS: Sorry for my very very bad English ;-{
Click to expand...
Click to expand...
Click to expand...
 
S

Stefan Krueger [MVP]

Did you check help topic "Using Custom Actions on a Terminal Server"?
Quote:
Deferred custom actions run in the context of the local system unless the
action has the msidbCustomActionTypeTSAware attribute. This is true even if
the custom action would normally impersonate the user on a system that was
not a Terminal Server. ...

Note that msidbCustomActionTypeTSAware is only available on Windows Server
2003.

--
Stefan Krueger
Microsoft Windows Installer MVP

Please post your questions in the newsgroup or vist one of these web sites:

Windows Installer FAQ
http://www.msifaq.com - http://www.msifaq.de

InstallSite - Resources for Setup Developers
http://www.installsite.org
http://www.installsite.de (GERMAN)



Paul Bacelar said:
Yes, but why my custom actions weren't impersonate with one policy and were
impersonate with another policy.

"AlwaysInstallElevated" policy attribute don't seem involved.

In MSI Log of unsuccessful install, I see this strange line:

"MSI (s) (FC:D4): Not impersonating action for per-machine Win2000 TS
install."

It's a legal situation or TS (Terminal Server) installation isn't
successfully terminated?
--
Paul Bacelar


Phil Wilson said:
Because when the installer service is updating the system from the data in
the MSI tables, the security is mostly controlled by policy rather than by
the user privileges. When the installer calls custom actions it *does*
impersonate the calling user.
--
Phil Wilson
[MVP Windows Installer]
Paul Bacelar said:
Hi and happy good year,



I use a msi file, generated by a VS.NET deployment project, to install my
components.



My problem is:

My setup.exe is launched by a user having extra rights on the Exchange
Server of domain, extra rights which allows my install procedure, via
"MyServiceName /Service", to request the Exchange Server. But, on a "Win2000
Server With Final Server" machine into my customer test domain, the install
process (my service) isn't processed under my initial user context but under
a "NT AUTHORITY\System" context, account of "Windows Installer" service.
"Windows Installer" service probably refuses to impersonalize my
installation program. I didn't reproduce this behaviour on my test
platform.

The "AlwaysInstallElevated" group policies (user and machine) don't
Click to expand...
seem
to
influence the "Windows Installer" impersonalization. In brief, Why "Windows
Installer" doesn't keep the security context of the installation
Click to expand...
Click to expand...
program
Click to expand...
 
P

Paul Bacelar

Note that msidbCustomActionTypeTSAware is only available on Windows Server
2003.
Click to expand...
That means I can't install my package on Windows2000 TS?

I need impersonation for my service installation. :-((
--
Paul Bacelar

Stefan Krueger said:
Did you check help topic "Using Custom Actions on a Terminal Server"?
Quote:
Deferred custom actions run in the context of the local system unless the
action has the msidbCustomActionTypeTSAware attribute. This is true even if
the custom action would normally impersonate the user on a system that was
not a Terminal Server. ...

Note that msidbCustomActionTypeTSAware is only available on Windows Server
2003.

--
Stefan Krueger
Microsoft Windows Installer MVP

Please post your questions in the newsgroup or vist one of these web sites:

Windows Installer FAQ
http://www.msifaq.com - http://www.msifaq.de

InstallSite - Resources for Setup Developers
http://www.installsite.org
http://www.installsite.de (GERMAN)



Paul Bacelar said:
Yes, but why my custom actions weren't impersonate with one policy and were
impersonate with another policy.

"AlwaysInstallElevated" policy attribute don't seem involved.

In MSI Log of unsuccessful install, I see this strange line:

"MSI (s) (FC:D4): Not impersonating action for per-machine Win2000 TS
install."

It's a legal situation or TS (Terminal Server) installation isn't
successfully terminated?
Click to expand...
data
in
Click to expand...
than
by
the user privileges. When the installer calls custom actions it *does*
impersonate the calling user.
--
Phil Wilson
[MVP Windows Installer]
Hi and happy good year,



I use a msi file, generated by a VS.NET deployment project, to
Click to expand...
install
my
components.



My problem is:

My setup.exe is launched by a user having extra rights on the Exchange
Server of domain, extra rights which allows my install procedure, via
"MyServiceName /Service", to request the Exchange Server. But, on a
"Win2000
Server With Final Server" machine into my customer test domain, the
install
process (my service) isn't processed under my initial user context but
under
a "NT AUTHORITY\System" context, account of "Windows Installer" service.
"Windows Installer" service probably refuses to impersonalize my
installation program. I didn't reproduce this behaviour on my test
platform.

The "AlwaysInstallElevated" group policies (user and machine) don't seem
to
influence the "Windows Installer" impersonalization. In brief, Why
"Windows
Installer" doesn't keep the security context of the installation
Click to expand...
program
(setup.exe) and which are the parameters which influence its behaviour
from
the security point of view?



Thank you, for your suggestions.



--
Paul Bacelar



PS: Sorry for my very very bad English ;-{
Click to expand...
Click to expand...
Click to expand...
 
P

Phil Wilson

That sure looks like the problem from the log - it won't impersonate the custom
actions in that mode, Stefan has it right.
--
Phil Wilson [MVP Windows Installer]
----
Paul Bacelar said:
Note that msidbCustomActionTypeTSAware is only available on Windows Server
2003.
Click to expand...
That means I can't install my package on Windows2000 TS?

I need impersonation for my service installation. :-((
--
Paul Bacelar

Stefan Krueger said:
Did you check help topic "Using Custom Actions on a Terminal Server"?
Quote:
Deferred custom actions run in the context of the local system unless the
action has the msidbCustomActionTypeTSAware attribute. This is true even if
the custom action would normally impersonate the user on a system that was
not a Terminal Server. ...

Note that msidbCustomActionTypeTSAware is only available on Windows Server
2003.

--
Stefan Krueger
Microsoft Windows Installer MVP

Please post your questions in the newsgroup or vist one of these web sites:

Windows Installer FAQ
http://www.msifaq.com - http://www.msifaq.de

InstallSite - Resources for Setup Developers
http://www.installsite.org
http://www.installsite.de (GERMAN)



Paul Bacelar said:
Yes, but why my custom actions weren't impersonate with one policy and were
impersonate with another policy.

"AlwaysInstallElevated" policy attribute don't seem involved.

In MSI Log of unsuccessful install, I see this strange line:

"MSI (s) (FC:D4): Not impersonating action for per-machine Win2000 TS
install."

It's a legal situation or TS (Terminal Server) installation isn't
successfully terminated?
--
Paul Bacelar


"Phil Wilson" <[email protected]> a écrit dans le message de
Because when the installer service is updating the system from the
Click to expand...
data
in
the MSI tables, the security is mostly controlled by policy rather
Click to expand...
than
by
the user privileges. When the installer calls custom actions it *does*
impersonate the calling user.
--
Phil Wilson
[MVP Windows Installer]
Hi and happy good year,



I use a msi file, generated by a VS.NET deployment project, to install
my
components.



My problem is:

My setup.exe is launched by a user having extra rights on the Exchange
Server of domain, extra rights which allows my install procedure, via
"MyServiceName /Service", to request the Exchange Server. But, on a
"Win2000
Server With Final Server" machine into my customer test domain, the
install
process (my service) isn't processed under my initial user context but
under
a "NT AUTHORITY\System" context, account of "Windows Installer" service.
"Windows Installer" service probably refuses to impersonalize my
installation program. I didn't reproduce this behaviour on my test
platform.

The "AlwaysInstallElevated" group policies (user and machine) don't seem
to
influence the "Windows Installer" impersonalization. In brief, Why
"Windows
Installer" doesn't keep the security context of the installation program

(setup.exe) and which are the parameters which influence its behaviour
from
the security point of view?



Thank you, for your suggestions.



--
Paul Bacelar



PS: Sorry for my very very bad English ;-{
Click to expand...
Click to expand...
Click to expand...
 
C

Carolyn Napier [MSFT]

It doesn't mean that you can't install your package on Windows 2000 TS. It just
means that you have to consider a different approach.

The reason for this design is based upon the Terminal Services - Windows
Installer interactions and the limitations imposed by that. The
msidbCustomActionTypeTSAware attribute was added in Windows Server 2003 to help
with this limitation. In essence, the attribute can be considered a "really
impersonate" attribute because the setup author by setting this attribute for
the custom action type indicates an understanding of Terminal Services and knows
that their custom action will interact appropriately. More information on
Terminal Services can be found in MSDN.

For those cases where msidbCustomActionTypeTSAware is not available to use, the
options are:

1) Author the custom action as an immediate custom action instead of deferred.
This will work, but typically the design of custom actions is such that
immediate custom actions do not alter machine state. Undoing changes can also be
difficult.

2) Author the custom action as an immediate custom action that runs after
InstallFinalize in the InstallExecuteSequence. The draw back of this is that
changes made by the custom action cannot be rolled back nor could your custom
action fail the install

3) You could do your own explicit authentication within setup to launch an
impersonated process. (Your action starts out as deferred, but then you obtain
the necessary credentials to launch a new process as the user.)

4.) Rethink your setup and determine if what you're doing isn't actually
installation but instead configuration. If it's configuration, then you should
push configuration to first-boot of the application itself.

Hope this helps,
- Carolyn Napier
Microsoft Windows Installer Team

--
This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.
MSI FAQ:
<http://www.microsoft.com/windows2000/community/centers/management/msi_faq.mspx>

Phil Wilson said:
That sure looks like the problem from the log - it won't impersonate the
custom
actions in that mode, Stefan has it right.
--
Phil Wilson [MVP Windows Installer]
----
Paul Bacelar said:
Note that msidbCustomActionTypeTSAware is only available on Windows Server
2003.
Click to expand...
That means I can't install my package on Windows2000 TS?

I need impersonation for my service installation. :-((
--
Paul Bacelar

Stefan Krueger said:
Did you check help topic "Using Custom Actions on a Terminal Server"?
Quote:
Deferred custom actions run in the context of the local system unless the
action has the msidbCustomActionTypeTSAware attribute. This is true even if
the custom action would normally impersonate the user on a system that was
not a Terminal Server. ...

Note that msidbCustomActionTypeTSAware is only available on Windows Server
2003.

--
Stefan Krueger
Microsoft Windows Installer MVP

Please post your questions in the newsgroup or vist one of these web sites:

Windows Installer FAQ
http://www.msifaq.com - http://www.msifaq.de

InstallSite - Resources for Setup Developers
http://www.installsite.org
http://www.installsite.de (GERMAN)



Yes, but why my custom actions weren't impersonate with one policy and
were
impersonate with another policy.

"AlwaysInstallElevated" policy attribute don't seem involved.

In MSI Log of unsuccessful install, I see this strange line:

"MSI (s) (FC:D4): Not impersonating action for per-machine Win2000 TS
install."

It's a legal situation or TS (Terminal Server) installation isn't
successfully terminated?
--
Paul Bacelar


"Phil Wilson" <[email protected]> a écrit dans le message de
Because when the installer service is updating the system from the data
in
the MSI tables, the security is mostly controlled by policy rather than
by
the user privileges. When the installer calls custom actions it *does*
impersonate the calling user.
--
Phil Wilson
[MVP Windows Installer]
Hi and happy good year,



I use a msi file, generated by a VS.NET deployment project, to install
my
components.



My problem is:

My setup.exe is launched by a user having extra rights on the Exchange
Server of domain, extra rights which allows my install procedure, via
"MyServiceName /Service", to request the Exchange Server. But, on a
"Win2000
Server With Final Server" machine into my customer test domain, the
install
process (my service) isn't processed under my initial user context but
under
a "NT AUTHORITY\System" context, account of "Windows Installer"
service.
"Windows Installer" service probably refuses to impersonalize my
installation program. I didn't reproduce this behaviour on my test
platform.

The "AlwaysInstallElevated" group policies (user and machine) don't
seem
to
influence the "Windows Installer" impersonalization. In brief, Why
"Windows
Installer" doesn't keep the security context of the installation
program

(setup.exe) and which are the parameters which influence its behaviour
from
the security point of view?



Thank you, for your suggestions.



--
Paul Bacelar



PS: Sorry for my very very bad English ;-{
Click to expand...
Click to expand...
Click to expand...
 
P

Phil Wilson

4.) Rethink your setup and determine if what you're doing isn't actually
installation but instead configuration. If it's configuration, then you should
push configuration to first-boot of the application itself.>>>>

Hear Hear!!!! This is something I tell people all the time.

--
Phil Wilson [MVP Windows Installer]
----
Carolyn Napier said:
It doesn't mean that you can't install your package on Windows 2000 TS. It just
means that you have to consider a different approach.

The reason for this design is based upon the Terminal Services - Windows
Installer interactions and the limitations imposed by that. The
msidbCustomActionTypeTSAware attribute was added in Windows Server 2003 to help
with this limitation. In essence, the attribute can be considered a "really
impersonate" attribute because the setup author by setting this attribute for
the custom action type indicates an understanding of Terminal Services and knows
that their custom action will interact appropriately. More information on
Terminal Services can be found in MSDN.

For those cases where msidbCustomActionTypeTSAware is not available to use, the
options are:

1) Author the custom action as an immediate custom action instead of deferred.
This will work, but typically the design of custom actions is such that
immediate custom actions do not alter machine state. Undoing changes can also be
difficult.

2) Author the custom action as an immediate custom action that runs after
InstallFinalize in the InstallExecuteSequence. The draw back of this is that
changes made by the custom action cannot be rolled back nor could your custom
action fail the install

3) You could do your own explicit authentication within setup to launch an
impersonated process. (Your action starts out as deferred, but then you obtain
the necessary credentials to launch a new process as the user.)

4.) Rethink your setup and determine if what you're doing isn't actually
installation but instead configuration. If it's configuration, then you should
push configuration to first-boot of the application itself.

Hope this helps,
- Carolyn Napier
Microsoft Windows Installer Team

--
This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.
MSI FAQ:
Click to expand...
Phil Wilson said:
That sure looks like the problem from the log - it won't impersonate the
custom
actions in that mode, Stefan has it right.
--
Phil Wilson [MVP Windows Installer]
----
Paul Bacelar said:
Note that msidbCustomActionTypeTSAware is only available on Windows Server
2003.
That means I can't install my package on Windows2000 TS?

I need impersonation for my service installation. :-((
--
Paul Bacelar

"Stefan Krueger [MVP]" <[email protected]> a écrit
dans le message de Did you check help topic "Using Custom Actions on a Terminal Server"?
Quote:
Deferred custom actions run in the context of the local system unless the
action has the msidbCustomActionTypeTSAware attribute. This is true even
if
the custom action would normally impersonate the user on a system that was
not a Terminal Server. ...

Note that msidbCustomActionTypeTSAware is only available on Windows Server
2003.

--
Stefan Krueger
Microsoft Windows Installer MVP

Please post your questions in the newsgroup or vist one of these web
sites:

Windows Installer FAQ
http://www.msifaq.com - http://www.msifaq.de

InstallSite - Resources for Setup Developers
http://www.installsite.org
http://www.installsite.de (GERMAN)



Yes, but why my custom actions weren't impersonate with one policy and
were
impersonate with another policy.

"AlwaysInstallElevated" policy attribute don't seem involved.

In MSI Log of unsuccessful install, I see this strange line:

"MSI (s) (FC:D4): Not impersonating action for per-machine Win2000 TS
install."

It's a legal situation or TS (Terminal Server) installation isn't
successfully terminated?
--
Paul Bacelar


"Phil Wilson" <[email protected]> a écrit dans le message de
Because when the installer service is updating the system from the
data
in
the MSI tables, the security is mostly controlled by policy rather
than
by
the user privileges. When the installer calls custom actions it *does*
impersonate the calling user.
--
Phil Wilson
[MVP Windows Installer]
Hi and happy good year,



I use a msi file, generated by a VS.NET deployment project, to
install
my
components.



My problem is:

My setup.exe is launched by a user having extra rights on the
Exchange
Server of domain, extra rights which allows my install procedure,
via
"MyServiceName /Service", to request the Exchange Server. But, on a
"Win2000
Server With Final Server" machine into my customer test domain, the
install
process (my service) isn't processed under my initial user context
but
under
a "NT AUTHORITY\System" context, account of "Windows Installer"
service.
"Windows Installer" service probably refuses to impersonalize my
installation program. I didn't reproduce this behaviour on my test
platform.

The "AlwaysInstallElevated" group policies (user and machine) don't
seem
to
influence the "Windows Installer" impersonalization. In brief, Why
"Windows
Installer" doesn't keep the security context of the installation
program

(setup.exe) and which are the parameters which influence its
behaviour
from
the security point of view?



Thank you, for your suggestions.



--
Paul Bacelar



PS: Sorry for my very very bad English ;-{
Click to expand...
Click to expand...
Click to expand...
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Do I need to specificily set impersonation for a custom action (on non vista machines)? 7
Connect to database after windows impersonation. 1
Impersonation without passing username and password. 2
Impersonation with SQL Server SSPI 3
Weird impersonation issue 4
Mulples threads and impersonation 4
Problem using ASP.Net Impersonation to access UNC share 1
Help with impersonation. 1

Top