Hey steve. The good news is that I implemented your startup fix and it appears to be working. I tested it to make sure that it was whacking it first and it was. Thanks. My question is why does it only happen to 2 out of my 39 PS servers? I also noticed that the 6.0 client is not installed on the PS server, but I'm pretty sure I have it on my desktop that I am using to connect (MSTSC /Console). I'm just trying to get a hold of how to prevent the problem when we build the next server. Thanks! Jim On Mon, Feb 25, 2008 at 2:52 PM, Raffensberger, Stephen D < sraffens@xxxxxxxxxxxxxxxxx> wrote: > This might be due to a Microsoft-induced double whammy that I've noticed: > > > > 1. Ever since NT 3.51, the behavior described by Russell has been > there. It's by design. I'll reserve my comments on the quality of that > particular design. > 2. Ever since the installation of Terminal Server Client 6.0, my > shortcut to "MSTSC /CONSOLE" has been using the above design to whack this > registry key on any Windows 2003 target. If I don't use /CONSOLE, there is > no problem. If I use the MMC snap-in with the console box checked, there is > no problem. > > > > As a workaround, I created a .REG file with the correct domain and made a > shortcut in my Startup folder pointing to regedit /s with the .REG file as > an argument. That way, every time I whack it, I fix it. > > > > Jim - if you reboot and then login with MSTSC /CONSOLE to check, it will > appear that your GPO didn't apply. In fact, it may have and you subsequently > whacked it. > > Steve Raffensberger > CSG Citrix Administrator > Sovereign Bank > Email: sraffens@xxxxxxxxxxxxxxxxx > ------------------------------ > > *From:* thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] *On > Behalf Of *Russell Robertson > *Sent:* Monday, February 25, 2008 1:22 PM > *To:* thin@xxxxxxxxxxxxx > *Subject:* RE: [THIN] Default Domain > > > > Jim > > > > Have you tried logging in via the console with the domain name you want? > We've found that even with registry settings, the last login domain carried > out on the console persists. > > > > Any additional advice on this would be appreciated. > > > > Cheers > > > > Russell > > *Russell Robertson | *Virtual Stream *|* Microsoft, Citrix and VMware > advisers *|* > > > ------------------------------ > > *From:* thin-bounce@xxxxxxxxxxxxx on behalf of Jim Medeiros > *Sent:* Mon 25/02/2008 16:14 > *To:* thin@xxxxxxxxxxxxx > *Subject:* [THIN] Default Domain > > We have just recently added two new servers to our PS 4.0 farm (Win2k3). > During the setup we set the registry defaultdomainname setting > (HKLM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon). However, > every time the server reboots (we set the reboot schedule to once per week) > this registry setting is removed (left blank). > > Using Microsoft's RSoP tool I cannot see any GPO that would be removing > this setting. We even tried creating an .adm file to assign to the local > security policy that will set the Default Domain Name but that only works > when we run it manually (GPUPDATE /Force), it doesn't appear to be applied > when the server reboots. > > Has anyone see this problem or have any ideas how I might be able to > troubleshoot it? > > thank you in advance. > > Jim > > > This message contains information which may be confidential and > privileged. Unless you are the addressee (or authorized to receive for the > addressee), you may not use, copy or disclose to anyone the message or any > information contained in the message. If you have received the message in > error, please advise the sender by reply e-mail, and delete or destroy the > message. Thank you. > -- I'm voting for Ron Paul for President http://www.ronpaul2008.com