What would be a good example of an exception to the general rule that would justify using logon/logoff script? Use the following as a general rule: to deploy or push a configuration change – apply GPOs or GPP and use the exception to this rule: to collect information from client computers and servers – apply scripts.
The answer should be founded on the organization´s needs, its size and complexity, as well as the experience and technical competence of the network administrators.įor now the good balanced answer to the question above would be that logon scripts should be used to handle those tasks that can’t be done with GPOs. Microsoft does not provide an “official guidance” on whether we should keep using GPOs to perform most of the legacy configuration tasks that were previously performed exclusively by logon scripts.
There is no an easy answer to this question. You know for sure that Group Policy Objects and the newer Group Policy Preferences (GPP) extensions offer the best possible solutions. But if all of your clients have Windows 7, and your servers are running Windows Server 2008 R2, the above question does not constitute a dilemma. With clients that run at least Windows 2000, you have GPOs as an additional option. GPOs are not applied on the client computers with these operating systems. You have to use ADUC if you have client computers with Windows OS older than Windows 2000.
Why would someone choose one method over another?
The first way is to type it in on the “Profile” tab of the user properties dialog in the Active Directory Users and Computers (ADUC), and the second way is to use Group Policy Objects (GPOs) to assign your logon script. There are two ways to set up a Logon script. A login script is a set of instructions that are executed on the client computer when a user logs on.
0 kommentar(er)
