Hi all,
I am beginning to deploy windows 7 in our environment and have run into a snag. We use group policies to deploy our printers, and when a printer is installed, the PendingFileRenameOperations value in hklm\system\currentcontrolset\control\session manager\ . After a printer is deployed, many of our .msi's won't deploy stating that a reboot is pending. However, some msi's don't care and will deploy no matter if this reg value is populated or not. I'm wondering if anyone knows why some msi's work when this value exists and why others won't. I'd like to modify all our msi's to ignore this registry key if possible so that we don't image a machine and wait for multiple reboots before the machine gets all of its software deployed. Thanks
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
It looks like the launch condition table may hold the key. I'll report what I find...
Answered 01/20/2012 by: spidey24
Yellow Belt

Please log in to comment
0
http://itninja.com/question/sequence-question13&mpage=1&key=restart
Answered 01/20/2012 by: GrGrGr
Orange Belt

Please log in to comment
0
After creating or modifying the existing .mst to drop the row for the table:
LaunchCondition: MsiSystemRebootPending<>1

It appears that all the msi's will run even if the pendingfilerenameoperations in the registry exists. Happy days! Thanks!
Answered 01/24/2012 by: spidey24
Yellow Belt

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