locked
Update the sctsettings.adm file RRS feed

  • Question

  • I an currently using the shared computer took kit and group policy. What would be the proper procedure to upgrade to SteadyState?

    A quick scan of one of my domain controllers shows the sctsettings.adm file in 7 different locations, 4 of which are replicated out.

    Thanks for any guidence.

    Ed


    Wednesday, August 8, 2007 7:03 PM

Answers

  • Hi Ed,

     

    Actually, we do not need to update the .adm file on the domain controller to apply the SteadyState settings. As the SteadyState relate group policies are not included in the Administrative Templates of a domain controller, we recommend that you perform the following steps to edit and deploy the SteadyState group policies from a Windows XP SP2 client. This is also the way that we configure and apply some new policies included in Windows XP SP2, such as Windows Firewall settings.

     

    1. On your DC, create a group policy that is to contain the Windows Firewall settings.
    2. Logon to a Windows XP SP2 computer which has joined the domain as domain administrator.
    3. Click Start, click Run, type mmc, and then click OK.
    4. On the File menu, click Add/Remove Snap-in.
    5. On the Standalone tab, click Add.
    6. In the Available Standalone Snap-ins list, click Group Policy Object Editor, and then click Add.
    7. In the Select Group Policy Object dialog box, click Browse.
    8. In the “Domains/OUs” tab, select your domain in the “Look in” list box. All the group polices in the domain will be displayed in the bottom list box. If the group policy is for an OU, you can double click the OU item to display group policies applied to the OU.
    9. Select the appropriate group policy that you have created and click OK to edit it.
    10. Import the SCTSettings.adm file and configure the corresponding policy settings.
    11. Close the Group Policy Editor snap-in.
    12. Refresh the group policy on the domain controller and all clients.

     

    After performing the steps above, the new SCTSettings.adm file is copied to the SYSVOL folder of the domain controller, such as sysvol\Domain.local\Policies\{GUID of the policy}\Adm. The group policy folder, including the new SCTSettings.adm file, will be replicated to other domain controllers properly via Active Directory replication.

     

    Please understand that when using the new version of SCTSettings.adm, there is a known issue if the option “Allow only programs in the Program Files and Windows folder to run” is selected. You can refer to the following thread:

     

    http://forums.microsoft.com/WindowsToolsandUtilities/ShowPost.aspx?PostID=1952148&SiteID=69

     

    Regards,

     

     

    Monday, August 13, 2007 9:32 AM

All replies

  • Hi Ed,

     

    As the SteadyState’s design technique is different from Shared Computer Toolkit (SCT), we have to uninstall SCT before the installation of SteadyState.

     

    To learn more information about the new features in SteadyState, please refer to the “What's New” part in the following website:

     

    http://www.microsoft.com/windows/products/winfamily/sharedaccess/default.mspx

     

    To uninstall SCT, you can refer to the website below or the “Performing Preinstallation Task” part in Windows SteadyState Handbook:

     

    Uninstall Shared Computer Toolkit Software

    http://www.microsoft.com/windows/products/winfamily/sharedaccess/install/uninstallsct.mspx

     

    Windows SteadyState Handbook

    http://www.microsoft.com/downloads/details.aspx?FamilyId=D64AF114-336C-4418-BEB7-E074E813B498&displaylang=en

     

    After installing SteadyState, the new version of sctsettings.adm can be found under the following location: C:\Program Files\Windows SteadyState\ADM. Its usage and related information can also be found in the handbook.

     

    For existing group policies that use the old SCTSettings.adm file, it can still work after you upgrade to SteadyState; however, to use the new restrictions included in the new SCTSettings.adm file, you will need to configure new group policies which are based on the new administrative template file.

     

    I hope the above information is useful.

     

    Best Regards,

     

    Friday, August 10, 2007 12:27 PM
  •  

    Thanks, that covers the desktops. I imported the ADM on my management machine which in turn sent it to a Domain Controller. I was wondering how to get the acutal ADM updated on my Domain Controllers.

     

    Ed

    Friday, August 10, 2007 1:38 PM
  • Hi Ed,

     

    Actually, we do not need to update the .adm file on the domain controller to apply the SteadyState settings. As the SteadyState relate group policies are not included in the Administrative Templates of a domain controller, we recommend that you perform the following steps to edit and deploy the SteadyState group policies from a Windows XP SP2 client. This is also the way that we configure and apply some new policies included in Windows XP SP2, such as Windows Firewall settings.

     

    1. On your DC, create a group policy that is to contain the Windows Firewall settings.
    2. Logon to a Windows XP SP2 computer which has joined the domain as domain administrator.
    3. Click Start, click Run, type mmc, and then click OK.
    4. On the File menu, click Add/Remove Snap-in.
    5. On the Standalone tab, click Add.
    6. In the Available Standalone Snap-ins list, click Group Policy Object Editor, and then click Add.
    7. In the Select Group Policy Object dialog box, click Browse.
    8. In the “Domains/OUs” tab, select your domain in the “Look in” list box. All the group polices in the domain will be displayed in the bottom list box. If the group policy is for an OU, you can double click the OU item to display group policies applied to the OU.
    9. Select the appropriate group policy that you have created and click OK to edit it.
    10. Import the SCTSettings.adm file and configure the corresponding policy settings.
    11. Close the Group Policy Editor snap-in.
    12. Refresh the group policy on the domain controller and all clients.

     

    After performing the steps above, the new SCTSettings.adm file is copied to the SYSVOL folder of the domain controller, such as sysvol\Domain.local\Policies\{GUID of the policy}\Adm. The group policy folder, including the new SCTSettings.adm file, will be replicated to other domain controllers properly via Active Directory replication.

     

    Please understand that when using the new version of SCTSettings.adm, there is a known issue if the option “Allow only programs in the Program Files and Windows folder to run” is selected. You can refer to the following thread:

     

    http://forums.microsoft.com/WindowsToolsandUtilities/ShowPost.aspx?PostID=1952148&SiteID=69

     

    Regards,

     

     

    Monday, August 13, 2007 9:32 AM