T
thrillerIT
Hello Everyone,
We have just deployed "wink sp4" via a computer based GPO
on a per site basis. I have 2 questions:
1) If a user interrupts the install by rebooting there
machine, why doesn't the GPO continue the install once the
machine comes back up?
Pleas Note: Even though the GPO didn't continue with the
install, I still saw an instance of the software (in this
case SP4) in the Add/Remove Programs window on the machine
that interrupted the install. I even tried Removing it and
restarting that machine BUT no luck. The GPO did not
continue with the WIN2k SP4 install. HELP!!! (I even tried
the RE-Deploy package option within the GPO, BUT I still
got the same results; NOTHING)
==========================================================
2) How can I prevent machines that installed SP4 manually
from having SP4 re-install on them via the GPO, without
adding them to a group and setting that group DENY rights.
Scenario: Since we are implementing SP4 on a per site
basis, we applied SP4 on one of our satellite sites.
Unfortunately, we did not know that our remote IT group
had installed SP4 manually on all of the computers on that
particular site. When we deployed the GPO, several users
happened to restart their machines. Then we realized that
the GPO SP4 policy was being applied to the machines even
though they already had SP4. I thought when SP4 was
applied via a GPO; the "Update.MSI" file would scan your
machine and verify if SP4 is already installed on that
computer. Is this true? (After that little incident, I'm
assuming that the policy will not install on machines that
have already been installed by that policy previously. Am
I right? (I hope that last sentence made sense.)
Thank you all in advance,
thrillerIT
PS. The first question is more important than the second
once.
We have just deployed "wink sp4" via a computer based GPO
on a per site basis. I have 2 questions:
1) If a user interrupts the install by rebooting there
machine, why doesn't the GPO continue the install once the
machine comes back up?
Pleas Note: Even though the GPO didn't continue with the
install, I still saw an instance of the software (in this
case SP4) in the Add/Remove Programs window on the machine
that interrupted the install. I even tried Removing it and
restarting that machine BUT no luck. The GPO did not
continue with the WIN2k SP4 install. HELP!!! (I even tried
the RE-Deploy package option within the GPO, BUT I still
got the same results; NOTHING)
==========================================================
2) How can I prevent machines that installed SP4 manually
from having SP4 re-install on them via the GPO, without
adding them to a group and setting that group DENY rights.
Scenario: Since we are implementing SP4 on a per site
basis, we applied SP4 on one of our satellite sites.
Unfortunately, we did not know that our remote IT group
had installed SP4 manually on all of the computers on that
particular site. When we deployed the GPO, several users
happened to restart their machines. Then we realized that
the GPO SP4 policy was being applied to the machines even
though they already had SP4. I thought when SP4 was
applied via a GPO; the "Update.MSI" file would scan your
machine and verify if SP4 is already installed on that
computer. Is this true? (After that little incident, I'm
assuming that the policy will not install on machines that
have already been installed by that policy previously. Am
I right? (I hope that last sentence made sense.)
Thank you all in advance,
thrillerIT
PS. The first question is more important than the second
once.