Java MSI won't deploy on certain workstations?
Hi guys,
I'm looking for some help with deploying java through an MSI package with Group Policy. I've already spent hours learing how to do it and modifying the package so it installs the IE plug-in at the same time. I've had it work on at least a few machines. As soon as they get the GP update through normal means, they install the Java MSI upon the next restart.
I've run into at least one workstation that would not install the software. If I tried gpupdate /force, it would prompt me that a part of the policy wanted to perform a restart. If I agreed, it still did not install the software upon restarting. When I checked RSOP.MSC, it gave me a similar message. I tried restarting three times and it would not install on it's own. Manually installing the package worked fine, but I definitely don't want to have to go around doing that manually. [:'(]
Can anyone suggest where I can start my search as to why this didn't work like possibly going through the offending workstation's event log? Any help would be greatly appreciated.
I'm looking for some help with deploying java through an MSI package with Group Policy. I've already spent hours learing how to do it and modifying the package so it installs the IE plug-in at the same time. I've had it work on at least a few machines. As soon as they get the GP update through normal means, they install the Java MSI upon the next restart.
I've run into at least one workstation that would not install the software. If I tried gpupdate /force, it would prompt me that a part of the policy wanted to perform a restart. If I agreed, it still did not install the software upon restarting. When I checked RSOP.MSC, it gave me a similar message. I tried restarting three times and it would not install on it's own. Manually installing the package worked fine, but I definitely don't want to have to go around doing that manually. [:'(]
Can anyone suggest where I can start my search as to why this didn't work like possibly going through the offending workstation's event log? Any help would be greatly appreciated.
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
jamsek19
17 years ago
I had the same problems and found out the cause of them:
On Win XP or newer OS it is possible that you do not have configured "Always wait for the network at computer startup and logon" in domain or local group policy (use gpedit.msc -> Computer Configuration -> Administrative Templates -> System -> Logon).
This means that at computer startup login is done from so called "cached domain login" not from real domain login and therefore group policy for software installation will never be reached - Assigned Installation GPO is done just at reboot after login into domain.
If you set this parameter in group policy login is slower, because computer real login into domain - login go to the domain controler to get login info, otherwise login info is get from cached login info which is on local computer. On Windows 2000 and older I didn't have those problems - Win2000 do not know for cached domain login.
Best Regards
Andreo
On Win XP or newer OS it is possible that you do not have configured "Always wait for the network at computer startup and logon" in domain or local group policy (use gpedit.msc -> Computer Configuration -> Administrative Templates -> System -> Logon).
This means that at computer startup login is done from so called "cached domain login" not from real domain login and therefore group policy for software installation will never be reached - Assigned Installation GPO is done just at reboot after login into domain.
If you set this parameter in group policy login is slower, because computer real login into domain - login go to the domain controler to get login info, otherwise login info is get from cached login info which is on local computer. On Windows 2000 and older I didn't have those problems - Win2000 do not know for cached domain login.
Best Regards
Andreo
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
