<div>
Check the security of the GP you created and make sure the new terminal server has Read and Apply, or is a member of a group that has Read and Apply.<br />
<br />

</div>


Check the security of the GP you created and make sure the new terminal server has Read and Apply, or is a member of a group that has Read and Apply.



<div>
I deleted the &quot;c:\winnt\system32\Group Policy&quot; folder from the terminal and rebooted and that seems to have resolved the problem.<br />
<br />
Thanks,<br />
Dana
</div>


I deleted the "c:\winnt\system32\Group Policy" folder from the terminal and rebooted and that seems to have resolved the problem.

Thanks,
Dana

<div>
danakee <br />
<br />
Welcome, glad to help<br />
Cheers<br />
<br />
JamesDS
</div>


danakee

Welcome, glad to help
Cheers

JamesDS

<div>
<div class="content wysiwyg-content">
We have recently installed Windows 2000 with terminal services (application mode) into a domain in our test lab. &nbsp;The domain has a Group Policy Object called Terminal Servers which contains the newly created terminal server. &nbsp;Upon initial install the GPO's were applied properly. &nbsp;We then ran sysprep on the terminal server. &nbsp;After rebooting from sysprep and completing the setup, which rejoined the server to the domain, we moved the server to the GPO called Terminal Servers and to our surprise it will not apply the policies for that group .<br />
<br />
Are we missing any steps that might need to be taken in order to sucessfully ghost a terminal server?<br />
<br />
Is there any additional steps that need to be taken in order to apply those policies?<br />
<br />
Did we miss a step in running sysprep?<br />
<br />
Any help would be appreciated.<br />
<br />

</div>
</div>


We have recently installed Windows 2000 with terminal services (application mode) into a domain in our test lab.  The domain has a Group Policy Object called Terminal Servers which contains the newly created terminal server.  Upon initial install the GPO's were applied properly.  We then ran sysprep on the terminal server.  After rebooting from sysprep and completing the setup, which rejoined the server to the domain, we moved the server to the GPO called Terminal Servers and to our surprise it will not apply the policies for that group .

Are we missing any steps that might need to be taken in order to sucessfully ghost a terminal server?

Is there any additional steps that need to be taken in order to apply those policies?

Did we miss a step in running sysprep?

Any help would be appreciated.



Group Policies not applying after sysprep

Windows 2000 is an operating system for use on both client and server computers. It is the successor to Windows NT 4.0, and is the last version of Microsoft Windows to display the "Windows NT" designation. Four editions of Windows 2000 were released (Professional, Server, Advanced Server, and Datacenter Server) that shared a core set of features, including many system utilities such as the Microsoft Management Console. All versions of the operating system support NTFS 3.0, Encrypting File System, as well as basic and dynamic disk storage. The Windows 2000 Server family includes support for Active Directory services, Distributed File System and fault-redundant storage volumes.