nope, tried gpresult but that has to be with the user *after* they're logged in...
_____ From: Webb, Brian (Corp) [mailto:[EMAIL PROTECTED] Sent: Friday, September 26, 2008 2:29 PM To: NT System Admin Issues Subject: RE: 2000 Terminal Server in 2003 domain not allowing logon local Did you run a RSOP against the machine with the user want to be able to log in? -Brian _____ From: Erik Goldoff [mailto:[EMAIL PROTECTED] Sent: Friday, September 26, 2008 1:21 PM To: NT System Admin Issues Subject: 2000 Terminal Server in 2003 domain not allowing logon local Weird situation at a client site, they're running 2003 AD, and have a few terminal servers, one of which is still a Windows 2000 sp4 server. Looks like the local security policy of 'log on locally' is being over ridden by a global policy but I don't see it. The effective setting is greyed out empty for non-administrator users, even though the local setting is checked. Anyone run into this before ? The global deny log on local is not defined, so that's not it... Thanks No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.169 / Virus Database: 270.7.2/1690 - Release Date: 9/26/2008 7:35 AM ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
