Question : secedit/gpupdate

I think

1-secedit is the same as gpupdate, secedit is w2000 and gpupdate is w2003. Correct?

2-what the default  length of time that the policy reaches the client without enforcing the policy?

3-is secedit/gpupdate used at the server side or client side?

thanks

Answer : secedit/gpupdate

1- When you create or edit the policy the changes are "written immediately" but they do not go into effect right away. If it is a policy that only affects the users of a workstation, you only need to run it on the workstation. So for example if you set a policy to change the desktop wallpaper for all users, running gpupdate  /force on the workstation would update the policy on the workstation, However, having done so, logging on to the server right away would show it hasn't affected the server, or any other machine for that matter until the 5/90 minute time has been reached, or you run GPUpdate on that machine.

2- 5 minutes for the policy to be applied on the domain controller on which you created the policy. The updates on the other DC's is Dependant on the replication time period. If my understanding of replication is correct, by default it occurs every 6 hours if no changes are made, and within 5 minutes after changes are made. Assuming a single hop between DC's this should mean it could take a maximum of 10 minutes for any DC to update. 5 minutes for replication and 5 to enforce. Then of course, the 90 minutes would apply to the remote PC's after their DC was updated.