Force reboot after application install
Our department is trying out application deployment via group policies and we've run into an issue where after a certain application installs (Oracle 9i client) the workstation won't install any other applications defined in the GPO until the workstation restarts. The error message in the event log is "Application failed to be installed because the installation source could not be found." Individually these applications are able to install with no problems from the same installation source.
So is there a solution to the above or do I need to somehow add a force reboot to the policy following the Oracle client install (and how do I do that?)?
Thanks,
Tim
So is there a solution to the above or do I need to somehow add a force reboot to the policy following the Oracle client install (and how do I do that?)?
Thanks,
Tim
0 Comments
[ + ] Show comments
Answers (9)
Please log in to answer
Posted by:
clewster
19 years ago
So is there a solution to the above or do I need to somehow add a force reboot to the policy following the Oracle client install (and how do I do that?)?
You can force a reboot by modifying the MSI package. however one thing i have notaced with a GPO is the software deploys in the order it is added to the GPO. so if you add oracle client as the last application it should work. or if you setup a second policy with oracle client in and stick it at the bottom of the link order then theres no problem fo adding further apps in the future.
hope this helps
Posted by:
trboyden
19 years ago
Thanks Pete,
I've tried re-ordering and putting software in separate policies but I still am unable to get all the software to install on one reboot. The clients will install the first application then error out on all the rest of the software and I have to manually reboot and then it will install the second app then reboot and etc and etc until all the apps are installed. Adding a reboot to the MSI doesn't always get the next application in line to install. Any ideas?
I've tried re-ordering and putting software in separate policies but I still am unable to get all the software to install on one reboot. The clients will install the first application then error out on all the rest of the software and I have to manually reboot and then it will install the second app then reboot and etc and etc until all the apps are installed. Adding a reboot to the MSI doesn't always get the next application in line to install. Any ideas?
Posted by:
clewster
19 years ago
hum............
when we had this problem we managed to swap the packages round to fix it. but if you created a custom MSI file that does not actuly install anything but has a vb script to force the pc to restart that should sort it out. If i get chance ill try make you one and test it out on our test enviroment this week. it would be a handy thing to have anyway.
when we had this problem we managed to swap the packages round to fix it. but if you created a custom MSI file that does not actuly install anything but has a vb script to force the pc to restart that should sort it out. If i get chance ill try make you one and test it out on our test enviroment this week. it would be a handy thing to have anyway.
Posted by:
clewster
19 years ago
[&:]I have tried everything to try get it to restart between apps. It seems MS didn’t think it would be a problem.
Hear is what I have tried and failed with
Tried all the above spread out across more than one policy and it still doesn’t work.
[8|]Here is a few alternative ways of getting the software on;
I know these options are not ideal but I really don’t see what other choice you have besides investing in SMS, Altirs or something like that with the extra functionality.
[:@]Sorry I couldn’t have been more help[:@]
Hear is what I have tried and failed with
- Use the force reboot function in a MSI package – this restarts the computer after the final app is installed even if the one with the option is the 1st app
- Adding a custom MSI file, which calls another file (tried vbs, batch and AutoIT), with a force reboot option. – This just ignores the restart bit.
Tried all the above spread out across more than one policy and it still doesn’t work.
[8|]Here is a few alternative ways of getting the software on;
- Logon script. If you use vbs then you can stick a few reg keys in to check for after the reboot so it doesn’t try installing the same apps again.
- Use groups on your policies and once some policies are installed add the machines to the group to get the rest.
I know these options are not ideal but I really don’t see what other choice you have besides investing in SMS, Altirs or something like that with the extra functionality.
[:@]Sorry I couldn’t have been more help[:@]
Posted by:
Sweede
19 years ago
Hi all
This is strange I have never heard of this problem, there might be some shit in that MSI package something that should have been removed something in registry that is over written and self repaired when restarted.
Clewster wrote: It seems MS didn’t think it would be a problem
I don't think it should either, I have made tons of packages and applied them by GPO, no problem
How is this MSI package made
Sweede ;-)
This is strange I have never heard of this problem, there might be some shit in that MSI package something that should have been removed something in registry that is over written and self repaired when restarted.
Clewster wrote: It seems MS didn’t think it would be a problem
I don't think it should either, I have made tons of packages and applied them by GPO, no problem
How is this MSI package made
Sweede ;-)
Posted by:
clewster
19 years ago
Its when the MSI package is updating system files, or a custom command within it. Its locking out parts of the system files therefore stopping the next installation.
if you install something big that updates system files and then try installing something else after you will get a message something like "a previous installation has not yet complete. Please finish this before installing" and I think this is whats happening with these packages. Its locking some of the system files out.
Suppose a messy way round to fix it would be to script it
if you install something big that updates system files and then try installing something else after you will get a message something like "a previous installation has not yet complete. Please finish this before installing" and I think this is whats happening with these packages. Its locking some of the system files out.
Suppose a messy way round to fix it would be to script it
Posted by:
Sweede
19 years ago
Restarting a service could be a solution, this is what the reboot does
And it can be done from inside the MSI
The Package knowledgebase have som guidelines about installing Oracle 9i client
http://itninja.com/link/chapter-3
sweede;-)
And it can be done from inside the MSI
The Package knowledgebase have som guidelines about installing Oracle 9i client
http://itninja.com/link/chapter-3
sweede;-)
Posted by:
clewster
19 years ago
I never thought of that. Although the only problem is you have go to find out what service you need to restart first.
Also that’s assuming it doesn’t work like the reboot and do it after it’s installed all the packages.
we are moving over to Altiris so we wont have this problem with MSI's soon [:D]
Also that’s assuming it doesn’t work like the reboot and do it after it’s installed all the packages.
we are moving over to Altiris so we wont have this problem with MSI's soon [:D]
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.