Windows Forum

Ask something
Discussion Locked

TerminalService window blank after logon

0 helpful
3 replies

by kkellerm

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I am running Terminal Services on a W2K AD domain controller. I have followed MS's kb247989 guide and have set the log on locally parameters to allow anyone and everyone rights to log on locally. Whenever a ts user tries to log on to the TS server, they get a blank desktop. However, if I make the ts user a member of administrators, I get a desktop after logging on. The only way I get a desktop is if the ts user is a member of the administrators group. What am I missing? I only have one server and am connecting over a vpn with the ts client.

3 replies

by bfilmfan

First things first, I wouldn't allow authenticated users to log onto a domain controller, but hey it's your environment. I'd set terminal server up as only a member server.

I suspect that since this is a domain controller that the only group with rights on the profile are domain admins.

You will need to create a second profile for the users and grant them rights to this.

LabMice's site has a ton of information on configuring terminal Services that should be able to help you out:
http://labmice.techtarget.com/Terminalsrvcs/default.htm

by kkellerm

I understand about setting up all auth users, however, this is a small shop, 25 users, with only ONE server so I can't make it a member server. I have been to labmice's site and have read thru all of the articles and none address my issue. I have made the changes in ms kb 247989 which changes the policy so why would creating a 2nd policy help?

by sgt_shultz

well, i'd be itching to get physically up to the computer and logon from lan with same username to see if still happens. if so see if this could be you:
Blank Screen or Operating System Cannot Load Profile at Logon
Article ID : 162031
Last Review : June 3, 2003
Revision : 2.0
This article was previously published under Q162031
On this Page
SYMPTOMS
CAUSE
RESOLUTION

SYMPTOMS
When you log on, you receive the following error message:
The operating system was unable to load your profile. Please contact your Network Administrator.(5)
Additionally, the logon dialog box may go away, leaving a blank screen, or wallpaper only, without any taskbar or desktop icons.
CAUSE
The %SystemRoot% folder, and possibly its subfolders, has had READ permission for the Everyone group removed. If the permission has been removed from the %SystemRoot% folder only, you will get the blank screen symptom. If the subfolders do not have the READ permission, you receive the "Cannot load profile" error message.

This error may also occur if "Read" permission has been removed for the root of the system partition.
RESOLUTION
Restore "Read" permissions for the Everyone group to the Windows_folder folder and all its subfolders.

--------------------------------------------------------------------------------

APPLIES TO
? Microsoft Windows 2000 Enterprise Edition
? Microsoft Windows 2000 Enterprise Edition
? Microsoft Windows 2000 Professional Edition
? Microsoft Windows 2000 Enterprise Edition
? Microsoft Windows NT Server 4.0 Enterprise Edition
? Microsoft Windows NT Workstation 4.0 Developer Edition

Top of Page

Keywords: kbnetwork KB162031

This discussion is closed to new replies.