Reboot required after some restriction changes
-
6. července 2007 16:18I would have posted in individual threads, but this issue seems to cover quite a few.
I've found that many changes to profile restrictions, even minor ones, either won't take effect or cause anomalies until a reboot happens.
A couple examples:
I set restrictions on my public profile to allow users to save to desktop, but I hid the C: drive (wrongly assuming that "Hide" meant "Hide" and not "Restrict"). I found that I could not save to the desktop, so I went back to administrator and unhid the C: drive. Back to the public profile, and I still could not save. Later on, after a reboot, I found it was working. The change to the profile did not take hold until the reboot.
Another instance was after I had experimented a bit with removing restrictions and had put everything back to the restrictions I wanted. Somehow, one of my icons was placed wrong, so I went into SteadyState and unlocked the profile. Upon logging into the public profile, I found that all the desktop icons were missing. Again, a reboot fixed this.
I've read through many threads with similar symptoms, and I feel that StreadyState has some problems making changes on the fly. I have a few hundred public machines spread over half of Colorado, so I think I'll be putting out a couple test machines before I do a full implementation.
Všechny reakce
-
6. července 2007 18:23Figured out these problems out...
If you leave the User Profile Hive Cleanup installed, despite what the handbook says, many problems will disappear. It is still a necessary service to have. -
9. července 2007 14:07
As for UPHClean tool, the handbook recommends you uninstalling UPHClean and SCT v1.1 first and then performing a clean installation of SteadyState. In this way, we can avoid any potential conflicts which may cause SteadyState installation failure. After SteadyState is installed successfully, you can then reinstall UPHClean tool if needed.
-
9. července 2007 14:25As I noted above, there were several problems that occurred with SteadyState without the UPHClean tool installed. I followed the directions in the handbook regarding uninstalling the old services. The problems did not resolve until the UPHClean was reinstalled.
If a conflict exists, can we expect to see SteadyState patch or update to handle the profiles better? So far all I see is the return to the days before the UPHClean.
(edit)
Sorry...I did not see at the end you said UPHClean could be reinstalled after. It does seem to be the resolution.
