Hi folks

Just wondering if somebody was able to deploy and install (or update) MDAC on client pc's without rebooting. Usually only after a reboot the installation finishes with a message like "Installing Control Panel".
Unfortunately to be able to finish the installation in that kind you have to log in with administrative rights what our users don't have.

Thanks for any feedback.
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
CHOOSE NEVER REBOOT IN ADMINISTRATIVE OPTION. THIS IS AVAILABLE IN INSTALLATION EXPERT (WISE PACKAGE STUDIO 5).

GIZ
Answered 11/02/2005 by: gizmolala
Third Degree Blue Belt

Please log in to comment
0
Thanks GIZ

MDAC Setup does not come as an MSI but as a Microsoft Setup.
The problem is not just how to disable the reboot. The installation does some finishing tasks after the reboot (which need administrative rights) so how to get the installation finished without a reboot. (If possible, I guess the reboot is need for file replacement...)
Answered 11/03/2005 by: rpfenninger
Second Degree Green Belt

Please log in to comment
0
Hej rpfenninger,

Check this site from Microsoft.

It says;


If you need to prevent the MDAC setup from restarting the workstation, use this command:

mdac_typ /Q:A /C:"dasetup /Q /N"






http://msdn.microsoft.com/library/default.asp?url=/library/en-us/mdacsdk/htm/wphistory_redistributemdac.asp


Cheers,
Priapus
Answered 12/02/2005 by: Priapus
Orange Belt

Please log in to comment
0
Most installations write their post reboot task in some exe that should be listed in the registry (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce).

If you can find out what it runs then you can proactively run that before the reboot. Alternatively, you may be able to set a scheduled task to kick it off when the system starts up. I use schtasks.exe which ships with Windows XP to automate setting scheduled task to do a lot of admin rights stuff at startup. Once the task is complete, depending on how it's setup, you can delete the task_name.job file so that it doesn't run again. Here is a link for getting schtasks.exe to run under Win2K. Of course, startup scripts in AD could work as well.

This might not be an ideal solution but it might get you started down the right track.

Hope this helps.
Answered 12/02/2005 by: yarborg
Blue Belt

Please log in to comment
0
Hi Priapus

Thanks you very much for this valuable information!
It seems that there is no easy way out of this issue as the original Microsoft documentation says the following (regarding the Silent Setup switch):
Note that this does not eliminate the potential need to restart the workstation

What a pain in the a**

Thanks anyway
Answered 01/11/2006 by: rpfenninger
Second Degree Green Belt

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