E
EB
Hi everyone, please let me know what you think about this:
This past weekend I spent some time working with group
policies on my home network (2 DC's Win2k server, 3
clients Win2kPro) to try to better understand things as it
relates theory and behaviour-wise. I set-up two policies
and deployed them with no problems, one for SP4 and one
for Office2K. For Office I set it up different ways, I
assigned it to the machine and to test users, and
published to test users successfully. In these instances
when I removed Office from the CP and rebooted the
policies behaved as expected-for assigments Office would
be reinstalled and when you double-clicked the appropriate
icon (the client went to the share that held the Data1.msi
on the server) and after a few moments you were back up
and running. My second policy did not co-operate-when
configured to be assigned to machine for the first time
the policy did indeed install. As a test I uninstalled via
CP and rebooted. This time around, the "Installing Managed
Software..." flashed very briefly and came right up to the
logon screen. My impression was that if the user were to
remove the SP of course the policy would reinstall it.
This does not seem to be the case, when you check machine
properties it still says "SP1". It did work the very first
time but subsequently that is not the case. Upon checking
the registry there were numerous sub-keys with entries
pointing to the share that held the SP files. I removed
these keys (again, this is a test network at home to play
with) and rebooted thinking this would help, it didn't.
What have I missed, has anyone experienced this oddity?
Thanks,
Ed
This past weekend I spent some time working with group
policies on my home network (2 DC's Win2k server, 3
clients Win2kPro) to try to better understand things as it
relates theory and behaviour-wise. I set-up two policies
and deployed them with no problems, one for SP4 and one
for Office2K. For Office I set it up different ways, I
assigned it to the machine and to test users, and
published to test users successfully. In these instances
when I removed Office from the CP and rebooted the
policies behaved as expected-for assigments Office would
be reinstalled and when you double-clicked the appropriate
icon (the client went to the share that held the Data1.msi
on the server) and after a few moments you were back up
and running. My second policy did not co-operate-when
configured to be assigned to machine for the first time
the policy did indeed install. As a test I uninstalled via
CP and rebooted. This time around, the "Installing Managed
Software..." flashed very briefly and came right up to the
logon screen. My impression was that if the user were to
remove the SP of course the policy would reinstall it.
This does not seem to be the case, when you check machine
properties it still says "SP1". It did work the very first
time but subsequently that is not the case. Upon checking
the registry there were numerous sub-keys with entries
pointing to the share that held the SP files. I removed
these keys (again, this is a test network at home to play
with) and rebooted thinking this would help, it didn't.
What have I missed, has anyone experienced this oddity?
Thanks,
Ed