|
|
| CyberDude 2002-07-22, 2:06 pm |
| You have already set up the above mentioned policy and it has been in effect for a few weeks. If you want to change its settings and want the new policy to be in effect immediatley, would you use the secedit machine refresh or the secedit user refresh?
I think it is the user but am not 100% sure. | |
| Johnny5Alive 2002-07-22, 2:13 pm |
| Depends if your policy is targeting Users or computers.
Normally, for password policy, you would apply to Domain level and target Users, so use : "user_refresh" | |
| Slinky 2002-07-22, 9:47 pm |
| Well according to the Windows 2000 Server help files, "secedit /refreshpolicy user policy" refreshes the settings for the user currently logged in. And the "machine policy" does the local machine. I always use the "machine policy" and it seems to work, even for security setting such as passwords. It wouldn't hurt to do both of them if you aren't sure. Just a matter of changing a couple of words.  | |
| mikop 2002-07-22, 10:49 pm |
| nt. | |
|
| IF you think about the way win apply these policy!
Computer will be applied when the PC bootup, user applied when user logged on so for me password policy will take effect with secedit machine_policy! | |
| CyberDude 2002-07-23, 5:04 am |
| After I posted, I had a rethink aswell. Guyda sounds reasonable as local policies are part of the computer config in a GPO.
I took an online test and had a question about this, but they had it as user config. | |
| jeff_j_black 2002-07-23, 9:31 am |
| I remember this by the phrase: passwords protect the machine, not the user. | |
| CyberDude 2002-07-23, 11:59 am |
| Nice one Jeff, may I use that too?  | |
| jeff_j_black 2002-07-23, 3:21 pm |
| It's all yours buddy! | |
| Slinky 2002-07-23, 6:38 pm |
| quote:
Originally posted by jeff_j_black
I remember this by the phrase: passwords protect the machine, not the user.
That could be debatable. I personally see it the other way around more, but thats just me. |
|
|
|