Windows Live Messenger 8.1 problem
Hi all, I'm having problems when trying to install WLM 8.1 through user-GPO.
I've added / changed the IAGREE, ADDBHO and stuff in the property table;
deleted the 'CacheSourceMsi' from the 'InstallExecuteSequence' table;
changed the MsgrFeat attribute from 24 to 16 and
added the 'AdvtExecuteSequence' table with the right rows.
But it doesn't seems to work, when the progressbar is on like 3/4, I get the message 'installation failed'!
The strange thing is that when I start it with msiexec /i "\\server\software$\WLM.msi" /qb (from the run commandline) it installs just fine...
I want to check the log, but I don't know where it's located when deploying through GPO[sm=rolleyes.gif].
Does anyone know the problem?
Also if someone has a bit experience with deploying 8.5 (v2008) it also should work fine for me.
Regards,
Snake86
Edit:
Allright, fixed it, but I want to create the Messenger shortcut at \\server\menustart$\%COMPUTERNAME%\,
when I add a new row to the property table called MenuStartOnServer and give the above value,
and change the directory attribute to the property it won't work.
Does anybody know how to fix this?
Regards
I've added / changed the IAGREE, ADDBHO and stuff in the property table;
deleted the 'CacheSourceMsi' from the 'InstallExecuteSequence' table;
changed the MsgrFeat attribute from 24 to 16 and
added the 'AdvtExecuteSequence' table with the right rows.
But it doesn't seems to work, when the progressbar is on like 3/4, I get the message 'installation failed'!
The strange thing is that when I start it with msiexec /i "\\server\software$\WLM.msi" /qb (from the run commandline) it installs just fine...
I want to check the log, but I don't know where it's located when deploying through GPO[sm=rolleyes.gif].
Does anyone know the problem?
Also if someone has a bit experience with deploying 8.5 (v2008) it also should work fine for me.
Regards,
Snake86
Edit:
Allright, fixed it, but I want to create the Messenger shortcut at \\server\menustart$\%COMPUTERNAME%\,
when I add a new row to the property table called MenuStartOnServer and give the above value,
and change the directory attribute to the property it won't work.
Does anybody know how to fix this?
Regards
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
AngelD
16 years ago
For interest, try deploying through machine-GPO instead and see if that success.
Some packages will not even install with user-GPO.
Some packages will not even install with user-GPO.
Posted by:
jamsek19
16 years ago
Hello.
If you didn't write log file as a parameter in msiexec command than log file is usually located in %temp% folder (%temp% is environment variable usually pointed to C:\Documents and Settings\<user_name>\Local Settings\Temp). To get there write [font="courier new"]"cd %temp%" (without d.quotes) in command prompt window or just %temp% in explorer address bar.
Msi log file name is in format [font="courier new"]MSI<Random_number>.log.
If you didn't find any log there search for MSI*?.log files on other user's %temp% folder (in case of Administrative install).
Eventually, if still you didn't find any MSI*.log file than you have configured so in group policies to not to create log file.
Check out:
run gpedit.msc and under
Computer Configuration -> Administrative templates-> Windows components -> Windows Installer double click on Logging and enable it. In Logging text box write "voicewarmup" to log everything.
Regards
Andreo
If you didn't write log file as a parameter in msiexec command than log file is usually located in %temp% folder (%temp% is environment variable usually pointed to C:\Documents and Settings\<user_name>\Local Settings\Temp). To get there write [font="courier new"]"cd %temp%"
Msi log file name is in format [font="courier new"]MSI<Random_number>.log.
If you didn't find any log there search for MSI*?.log files on other user's %temp% folder (in case of Administrative install).
Eventually, if still you didn't find any MSI*.log file than you have configured so in group policies to not to create log file.
Check out:
run gpedit.msc and under
Computer Configuration -> Administrative templates-> Windows components -> Windows Installer double click on Logging and enable it. In Logging text box write "voicewarmup" to log everything.
Regards
Andreo
Posted by:
sampitu
16 years ago
Hi Snake86,
how did you solve the "installation failed" issue?
i'm creating a mst file with the instructions on this link:
http://itninja.com/link/appdeploy->-package-knowledgebase->-msn-messenger
apply the GPO (publish) with transformation. when i try to install software, setup rolls back the action and gives fatal error at the end. i don't see any access denied messages on filemon and regmon.
from log file:
Property(S): ProductToBeRegistered = 1
Action ended 04:32:02: ExecuteAction. Return value 3.
Action 04:32:02: FatalErrorDialog.
Action start 04:32:02: FatalErrorDialog.
Action 04:32:02: FatalErrorDialog. Dialog created
how did you solve the "installation failed" issue?
i'm creating a mst file with the instructions on this link:
http://itninja.com/link/appdeploy->-package-knowledgebase->-msn-messenger
apply the GPO (publish) with transformation. when i try to install software, setup rolls back the action and gives fatal error at the end. i don't see any access denied messages on filemon and regmon.
from log file:
Property(S): ProductToBeRegistered = 1
Action ended 04:32:02: ExecuteAction. Return value 3.
Action 04:32:02: FatalErrorDialog.
Action start 04:32:02: FatalErrorDialog.
Action 04:32:02: FatalErrorDialog. Dialog created
Posted by:
anonymous_9363
16 years ago
from log file:Unfortunately, you have omitted the crucial part of the log, which would have been a few lines above this one. My guess would be that the MSI has a merge module (probably for MS Visual C++ runtime, called 'CRT') which prevents this MSI being installed per-user. I have encountered a number of these at my current client. Decisions about how to proceed have been left to the individual BUs but come down to either installing per-machine instead or removing the merge module, effectively re-authoring the MSI.
Property(S): ProductToBeRegistered = 1
Action ended 04:32:02: ExecuteAction. Return value 3.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
