Hi ALL,[:D]

After going to:

1) Setup Editor >> Product [TAB] >> selecting Properties
creating SetReboot property with FORCE value


2) In MSI Script created "Custom Action" with the following:
Action Name: Reboot
propert: SetReboot
value: FORCE
in loctaion tab: Placed it after InstallFinalize with the condition: Not installed

the package never asks to reboot the PC, any idea??
is my condition (Not installed) ok or need to set NO condition at all?

Thanks for your HELP....!! [;)]
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
The case of 'Installed' is vital. It needs to be as shown - Installed. Anything else will be ignored, as a verbose log of the install would have shown you. The case of the operators e.g. NOT and so on doesn't matter, but I tend to capitalise them.

Also, use the REBOOT property instead of SetReboot. I wouldn't recommend keeping it in the property table, as it's not conditioned, meaning that the package will reboot on repairs, patches and so on.
Answered 07/21/2010 by: VBScab
Red Belt

Please log in to comment
0
Thanks VBScab for your reply. i did what you suggested but still no Reboot done after the package finished.
Any other ideas??

Thanks .
Answered 07/21/2010 by: Netrock
Orange Senior Belt

Please log in to comment
0
...and the log told you....?
Answered 07/21/2010 by: VBScab
Red Belt

Please log in to comment
0
thanks for your reply. do I have to enable log file in command line section in WISE or it gets created by default, because i do not see any log files.
Answered 07/21/2010 by: Netrock
Orange Senior Belt

Please log in to comment
0
msiexec /i [path_to_and_name_of_MSI] /l*v %temp%\whatever.log [other arguments]
Answered 07/21/2010 by: VBScab
Red Belt

Please log in to comment
0
Hi, [;)]

I am having a difficult time to enable "Verbose logging for my MSI package in Wise".
the step i took:
In Distribution panel i selected Command Line, click on ADD, in command line details i have 6 tabs in general tab i entered the name, in the command line box i entered:
msiexec /i [path_to_and_name_of_MSI] /l*v %temp%\whatever.log but it goes back to the default which is: msiexec.exe /I [MSIFILENAME] /L*V "%temp%\whatever.log"

do not know what i am doing wrong?? [:o]
Any Help really appreciated. Thank you in advance
Answered 07/22/2010 by: Netrock
Orange Senior Belt

Please log in to comment
0
Sorry, I should have been clearer.

Remove the command line from the WSI/MSI. I meant you to run the 'MSIExec...[etc]' from a DOS command prompt on the target machine.
Answered 07/22/2010 by: VBScab
Red Belt

Please log in to comment
0
Thanks for the quick reply.
I also found this:

How to Enable Windows Installer Logging
(From Microsoft Knowledge Base Article – 223300)
Windows Installer can use logging to help assist in troubleshooting issues with installing software
packages. This logging is enabled by adding keys and values to the registry. After the entries have
been added and enabled, you can retry the problem installation and Windows Installer will track
the progress and post it to the Temp folder. The new log's file name is random, but begins with
the letters "MSI" and end with a .log extension.
To locate the Temp folder location:
type the following in the address field of Windows Explorer: %temp%
or
type the following at a command prompt: cd %temp%
Open the registry with Regedt32.exe and create the following path and keys:
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer
Reg_SZ: Logging
Value: voicewarmup
The letters in the value field can be in any order. Each letter turns on a different logging mode.
Each letter's actual function is as follows for MSI version 1.1:
v - Verbose output
o - Out-of-disk-space messages
i - Status messages
c - Initial UI parameters
e - All error messages
w - Non-fatal warnings
a - Start up of actions
r - Action-specific records
m - Out-of-memory or fatal exit information
u - User requests
p - Terminal properties
+ - Append to existing file
! - Flush each line to the log
"*" - Wildcard, log all information except for the v option. To include the v option, specify "/l*v".
NOTE: This should be used only for troubleshooting purposes and should not be left on because it
will have adverse effects on system performance and disk space. Each time you use the
Add/Remove Programs tool in Control Panel, a new MSI*.log file is created.
Answered 07/22/2010 by: Netrock
Orange Senior Belt

Please log in to comment
0
That - as you can see from the location - is actually a machine-based Group Policy. The problems with using it are a) it's an all-or-nothing setting, meaning that you get logs for ALL Windows Installer activity, including advertising, and that you have to remember to turn it off and b) you have no control over the name or location of the log file (logs get written to %SystemRoot%\TEMP, prefixed 'MSI' and with a random alphanumeric name. That makes finding the relevant log harder than it needs to be.

If you're deploying with GP, this of course is your only choice but, from a command line, the '/l' argument is preferable.
Answered 07/22/2010 by: VBScab
Red Belt

Please log in to comment
0
You are right. I did what you have asked from cmd got the log file. I looked for "reboot: saw the following lines:

"MSI (s) (2C:D8) [0:28:20:140]: Skipping action: ScheduleReboot (condition is false)"
....................................
...................................
....................................

"Property(S): Reboot = FORCE"

any idea why reboot is not working, it says condition is false but the condition is set to force as you can see..!! [8|]
Answered 07/22/2010 by: Netrock
Orange Senior Belt

Please log in to comment
0
A common misunderstanding...

Take a look in MSDN at the notes about the ScheduleReboot action. While that page is loading, you'll find a condition on the ScheduleReboot action in the ExecuteDeferred sequence. It is THAT condition which resolves to False.
Answered 07/22/2010 by: VBScab
Red Belt

Please log in to comment
0
Hi VBScab,
yeah i see THAT "ScheduleReboot" you are right. Big Thanks for clearing this.
I set the condition for "Reboot" (with FORCE value) to "INSTALLED" but the log says condition is False.

any idea? maybe set it to "Not Installed" ( which really does not make any....!!!)
what do you think...?[8|]
Answered 07/22/2010 by: Netrock
Orange Senior Belt

Please log in to comment
0
Changed the Condition for Reboot to "NOT Installed" ran the PKG still No GOOOO!!!!![&o]

Checked the log here it is.....

MSI (s) (FC:28) [00:04:15:140]: Doing action: REBOOT
Action 00:04:15: REBOOT.
Action start 00:04:15: REBOOT.
Action ended 00:04:15: REBOOT. Return value 1.
MSI (s) (FC:28) [10:04:15:156]: Doing action: InstallFinalize
Action 00:04:15: InstallFinalize.
Action start 00:04:15: InstallFinalize.

So WHY is not Doing it??[8|]
Answered 07/22/2010 by: Netrock
Orange Senior Belt

Please log in to comment
0
Hang on...what REBOOT action is that? REBOOT is a property, not an action.
Answered 07/22/2010 by: VBScab
Red Belt

Please log in to comment
0
Also, MSDN says in the following link that :

"The ForceReboot action must come between InstallInitialize and InstallFinalize in the action sequence of the InstallExecuteSequence table."

http://msdn.microsoft.com/en-us/library/aa368607(v=VS.85).aspx
Answered 07/22/2010 by: Netrock
Orange Senior Belt

Please log in to comment
0
But this line get generated from " Set Property Reboot". Because when i changed the condition from Installed to not installed the log changed as you can see...

I am very much in the CONFUSED STATS now....!!!???!!???!! [8|]
Answered 07/22/2010 by: Netrock
Orange Senior Belt

Please log in to comment
0
That action is called ForceReboot, not REBOOT. So, if that's where you want to get to, include the ForceReboot action and condition it with 'NOT Installed'.
Answered 07/23/2010 by: VBScab
Red Belt

Please log in to comment
0
Property table:
REBOOT = Force
RebootYesNo = Yes

Logging is easy to remember:
HKLM\SOFTWARE\Policies\Microsoft\Windows\Installer
logging (REG_SZ) = voicewarmup
Stop the Installer service
Answered 07/23/2010 by: bertman
Senior Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity