quote:

---

Originally posted by Deja-vue
Are you sure?

---

quote:

---

Originally posted by Deja-vue
Good Monday morning to everyone!

And today's Question is:

You are the administrator of your company's network. The network consists of one Windows NT 4.0 domain. You create and implement a security policy that is applied to all Windows 2000 Professional client computers as they are staged and added to the network. You want this security policy to be in effect at all times on all client computers on the network. However, you find out that administrators periodically change security settings on computers when they are troubleshooting or doing maintenance. You want to automate the security analysis and configuration of client computers on the network so that you can track changes to security policy and reapply the original security policy when it has been changed.

What should you do?

A. Use Windows NT System Policy to globally configure the security policy settings on the client computers.

B. Use Windows 2000 Group Policy to globally configure the security policy settings on the client computers.

C. Use the Security and Configuration Analysis tool on the client computers to analyze and configure the security policy.

D. Schedule the Secedit command to run on the client computer, analyze and configure the security policy.
We'll see ya' tomorrow with the Answer.

---

quote:

---

Originally posted by Deja-vue
D was correct!
Normally, if the GPOs that define the environment for the user have not changed from the last time Group Policy was applied, the GPO is skipped and not applied again. In either case, specifying "/ENFORCE" on the command line re-applies the policy even if the GPOs that apply to the computer or user have not changed. An example of the command line in this case is: secedit /refreshpolicy machine_policy /enforce

---

quote:

---

Originally posted by Deja-vue
No need to be sorry,cm2gj..
We are all here to learn!

---