locked
SCTSettings.adm copied from one PC doesn't seem to affect settings on the other. RRS feed

  • Question

  • And here's the kicker, I have seen that it does sometimes. So, what is the best way to copy those settings over for:

    • Workgroup atmosphere
    • Need to have the exact same configuration for all PCs
    • We have automated the user import via batch.

    Correct me if I am wrong here. The SCTSettings.adm controls the Set Computer Restrictions function within the SteadyState GUI. These computer restrictions are what I need to replicate from one master machine.

    Thursday, September 25, 2008 6:31 PM

Answers

  •  

    Hi, for SCTsettings.adm deployment, we usually do this job in AD domain environment. That is the original purpose of SCTsettings.adm. You can refer to the following paragraph in Windows SteadyState handbook.

     

    Windows SteadyState includes a Group Policy template called SCTSettings.adm in the ADM folder commonly located in C:\Program Files\Windows SteadyState. This template reproduces most of the settings included in Windows SteadyState Feature Restrictions tab of the User Settings dialog box, and can be used to deploy restrictions to users who are members of an Active Directory domain.

    Group Policy for a domain can be configured either with the Group Policy Management Console, an add-in tool available for download from Microsoft, or by using the Group Policy Editor built into Active Directory Users and Computers. By adding the SCTSettings.adm template into these tools, you gain access to account restrictions and settings that are appropriate for user accounts on shared computers.

    The SCTSettings.adm Group Policy template included with Windows SteadyState also includes the capability to set idle and mandatory logoff timers, if Windows SteadyState is installed on your computers.

    It is important that you apply these settings only to specific user accounts, so as not to restrict legitimate administrative user accounts on any computers.

       To use Active Directory Users and Computers to manage Windows SteadyState restrictions

    1.    Start Active Directory Users and Computers on a computer running Microsoft Windows Serverä 2003 by clicking Start, and then clicking All Programs.

    2.    Click Administrative Tools. In Active Directory Users and Computers, right-click the organizational unit (OU) for which you want to configure policy, and then click Properties.

    3.    On the Group Policy tab, select the policy you want to modify, and then click Edit.

    4.    Expand User Configuration, right-click the Administrative Templates folder, and then click Add/Remove Templates.

    5.    In the Add/Remove Templates dialog box, click Add and then browse to the location of the SCTSettings.adm template, commonly located in C:\Program Files\Windows SteadyState\ADM.

    6.    Browse the settings in the All Windows SteadyState Restrictions folder and note their similarity to the program and user restrictions settings in Windows SteadyState. Descriptions are given for each setting.

    7.    Make any restrictions changes that you want and then exit Group Policy Editor.

     

    Note: We recommend that you create an OU that stores the shared user accounts in your environment, and that you apply the SCTSettings.adm template to the User Configuration portion of a Group Policy Object linked to this dedicated OU.

    Tuesday, September 30, 2008 4:38 AM

All replies

  •  

    Hi, for SCTsettings.adm deployment, we usually do this job in AD domain environment. That is the original purpose of SCTsettings.adm. You can refer to the following paragraph in Windows SteadyState handbook.

     

    Windows SteadyState includes a Group Policy template called SCTSettings.adm in the ADM folder commonly located in C:\Program Files\Windows SteadyState. This template reproduces most of the settings included in Windows SteadyState Feature Restrictions tab of the User Settings dialog box, and can be used to deploy restrictions to users who are members of an Active Directory domain.

    Group Policy for a domain can be configured either with the Group Policy Management Console, an add-in tool available for download from Microsoft, or by using the Group Policy Editor built into Active Directory Users and Computers. By adding the SCTSettings.adm template into these tools, you gain access to account restrictions and settings that are appropriate for user accounts on shared computers.

    The SCTSettings.adm Group Policy template included with Windows SteadyState also includes the capability to set idle and mandatory logoff timers, if Windows SteadyState is installed on your computers.

    It is important that you apply these settings only to specific user accounts, so as not to restrict legitimate administrative user accounts on any computers.

       To use Active Directory Users and Computers to manage Windows SteadyState restrictions

    1.    Start Active Directory Users and Computers on a computer running Microsoft Windows Serverä 2003 by clicking Start, and then clicking All Programs.

    2.    Click Administrative Tools. In Active Directory Users and Computers, right-click the organizational unit (OU) for which you want to configure policy, and then click Properties.

    3.    On the Group Policy tab, select the policy you want to modify, and then click Edit.

    4.    Expand User Configuration, right-click the Administrative Templates folder, and then click Add/Remove Templates.

    5.    In the Add/Remove Templates dialog box, click Add and then browse to the location of the SCTSettings.adm template, commonly located in C:\Program Files\Windows SteadyState\ADM.

    6.    Browse the settings in the All Windows SteadyState Restrictions folder and note their similarity to the program and user restrictions settings in Windows SteadyState. Descriptions are given for each setting.

    7.    Make any restrictions changes that you want and then exit Group Policy Editor.

     

    Note: We recommend that you create an OU that stores the shared user accounts in your environment, and that you apply the SCTSettings.adm template to the User Configuration portion of a Group Policy Object linked to this dedicated OU.

    Tuesday, September 30, 2008 4:38 AM
  • Hi Sean,

    I appreciate the feedback, but my question really is geared toward non domain environments. Is there any way to capture these settings and reapply them or would I need to start looking toward the registry hacks someone else has posted?

    Many thanks!!

     

    Tuesday, September 30, 2008 11:36 AM