MSTerminalServices.org Forums

Forums Home | FAQ | Search | Profile | Private Messages | Log in/Register/Password

2003r2 32bit Terminal Server not reading group policy

Page 1 of 1
Next:  Microsoft Terminal Services: Error on Terminal Server  
Author Message
scooter




Joined: Feb 19, 2008
Posts: 2



(Msg. 1) Posted: Tue Feb 19, 2008 8:23 pm
Post subject: 2003r2 32bit Terminal Server not reading group policy
Have a 32bit 2003r2 terminal server and installed a 2003r2 64bit server into the domain.

Now, I can no longer edit the Group Policy on the 32bit machine for the OU that controls the Remote TS users. Give me an error stating that Nore will the 32bit Terminal server will no longer read the Group policy in the OU. So TS users have full access. Installed the GroupPolicyEditor and I can open the GP on the 32bit machine, but it still will not read or apply the GP.

Group Policy can be edited on the 64bit machine, but it does not run TS on it.

How can I get the 32bit TS to read and apply the GP for remote TS users?



TIA Sad
Back to top
Send e-mail Login to vote
vera_noest




Joined: May 27, 2007
Posts: 205

Location: Sweden
(Msg. 2) Posted: Wed Feb 20, 2008 5:12 pm
Post subject:
Is the 64bit server a Domain Controller? Are both servers at the same SP level?
You probably updated the .adm template files when you installed the 64bit server. Check their ownership and permissions. Also check the EventLog on the 32bit server for more information. More info here:

Recommendations for managing Group Policy administrative template (.adm) files
Back to top
Send e-mail Login to vote
scooter




Joined: Feb 19, 2008
Posts: 2



(Msg. 3) Posted: Thu Feb 21, 2008 2:52 pm
Post subject: Resolved
Hi

Ended up getting Microsoft Engineers on it. Turns out that on the 64bit and the 32bit server there are different settings needs in LANMAN and LANMANWORKSTATION. The problem was that the EnableSystemSignature and RequireSystemSignature on both machines were not matching and they were not talking to each other via SMB. So, full replication was not being performed and access to each other shared resources were limited.

These are default settings on the 32bit and 64bit NOS. By introducing the 64bit into the 32bit, you would think it would create the trust between the two, but per MS Engineers, it does not and have to manually be changed.

There was also some changes to TCP (TCP & TCPCHIMNEY).

DNS was fine, ADM fine, partial replication was being performed, but, the two server basically did not trust each other in the domain since the settings in LANMAN and LANMANWORKSTATION were not in sync.

Thanks for the help tho. Hope the above helps you save some stress.

THANKS
Back to top
Send e-mail Login to vote
vera_noest




Joined: May 27, 2007
Posts: 205

Location: Sweden
(Msg. 4) Posted: Thu Feb 21, 2008 4:46 pm
Post subject:
OK, I'm glad that your problem is solved, and thanks for sharing the solution with us!
Back to top
Send e-mail Login to vote
Display posts from previous:   
    All times are: Eastern Time (US & Canada) (change) Page 1 of 1

 
 You can post new topics in this forum
You can reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

Looking for more Terminal Services info?

Sign up to the MSTerminalServices.org Monthly Newsletter, written by Terminal Server MVP & Citrix CTP Stefan Vermeulen, containing news, tips, interviews, links of the month and much more. Subscribe today and don't miss a thing!

Become an MSTerminalServices.org member!

Discuss your Terminal Services & Citrix issues with thousands of other SBC experts. Click here to join!

Community Area

Log in | Register