D
David Reed
Hi All,
I have a group policy that seems to be causing a restart on some specific
computers. The computers are NOT part of the group (any longer) that the GP
should be applying to, but have been removed from that group. But they
still seem to be acting as if they are. (ie, when the SUS updates are
downloaded, the computers are automatically restarting, and they are test
computers, therefore, the tests aren't completing.).
I -MUST- stop that.
Is there something someone call suggest, a registry entry I can make
somewhere, something, to prevent the SUS updates from re-starting the
computer when the updates are done? Or any other ideas? The one thing I
can't really do is wipe out and reload the computers, because they are being
used in a lab environment.
Thanks,
David
(e-mail address removed)
I have a group policy that seems to be causing a restart on some specific
computers. The computers are NOT part of the group (any longer) that the GP
should be applying to, but have been removed from that group. But they
still seem to be acting as if they are. (ie, when the SUS updates are
downloaded, the computers are automatically restarting, and they are test
computers, therefore, the tests aren't completing.).
I -MUST- stop that.
Is there something someone call suggest, a registry entry I can make
somewhere, something, to prevent the SUS updates from re-starting the
computer when the updates are done? Or any other ideas? The one thing I
can't really do is wipe out and reload the computers, because they are being
used in a lab environment.
Thanks,
David
(e-mail address removed)