Discussion:
TS 2k3 users can log in but only see blue wallpaper?
(too old to reply)
DEVO
2005-11-04 03:02:40 UTC
Permalink
I posted earlier with a different problem, but now i am having the
problem that when users log onto my terminal server 2003 they get to
the logon prompt and can type in their usernames and passwords and it
will begin logging them in but after that it only loads the default
blue wallpaper for them, no icons on the screen and no start menu bar
across the bottom of the screen?? When i log in as the administrator,
it logs me in correctly but this is the only username that does. I
have tried adding users explicitly to the permissions tab for the RDP
5.2 connection but that doesnt help. Any ideas??? used to work fine
last week, now its gone crazy on me.
thanks in advance.
Vera Noest [MVP]
2005-11-04 11:02:48 UTC
Permalink
So what has been changed between last week and now?
Did you install any software? drivers? Windows Update? Made any
configuration changes? Group Policies?

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*
Post by DEVO
I posted earlier with a different problem, but now i am having
the problem that when users log onto my terminal server 2003
they get to the logon prompt and can type in their usernames and
passwords and it will begin logging them in but after that it
only loads the default blue wallpaper for them, no icons on the
screen and no start menu bar across the bottom of the screen??
When i log in as the administrator, it logs me in correctly but
this is the only username that does. I have tried adding users
explicitly to the permissions tab for the RDP 5.2 connection but
that doesnt help. Any ideas??? used to work fine last week,
now its gone crazy on me. thanks in advance.
DEVO
2005-11-04 12:57:33 UTC
Permalink
installed SP1 for server 2003, edited group policies to allow printer
redirection and changed a few other group policies outside of the
terminal services policies that looked like they might help. Plus
someone else removed the RDP 5.2 connection setting from "terminal
services configuration" icon and recreated it. It possibly could have
all started a few weeks ago when that person also installed something
called "secure FTP wrapper" on the server also and that is what started
changing all the group policies???
DEVO
2005-11-04 12:59:13 UTC
Permalink
if it helps any, i can see the user as logged in and active in
"terminal services manager" and if i right click on that logged in user
and send them a message, the message pops up in the middle of their all
blue screen, so they can see that, they just have no icons or start
menu???
Vera Noest [MVP]
2005-11-04 14:42:56 UTC
Permalink
Check the EventLog on the TS. Any errors ther, especially ones about
profile load errors?
Also enable verbose logging of userenv:

221833 - How to enable user environment debug logging in retail
builds of Windows
http://support.microsoft.com/?kbid=221833

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
Post by DEVO
if it helps any, i can see the user as logged in and active in
"terminal services manager" and if i right click on that logged
in user and send them a message, the message pops up in the
middle of their all blue screen, so they can see that, they just
have no icons or start menu???
DEVO
2005-11-04 15:21:40 UTC
Permalink
ok i setup verbose logging of userenv, and tried logging in as a user
who only gets a blue background, it the event viewer shows the
following:
Windows cannot determine the user or computer name. (specified domain
either does not exist or could not be contacted. ) Group Policy
processing aborted.

also:
Windows saved user Orlane\norman registry while an application or
service was still using the registry during log off. The memory used by
the user's registry has not been freed. The registry will be unloaded
when it is no longer in use.
This is often caused by services running as a user account, try
configuring the services to run in the LocalService or NetworkService
account.

??? hope that helps
DEVO
2005-11-04 17:56:45 UTC
Permalink
i removed sp1 and now people can log in again?? sp1 for server 2003 =
SP2 for winXP??
Vera Noest [MVP]
2005-11-04 20:37:00 UTC
Permalink
Post by DEVO
i removed sp1 and now people can log in again?? sp1 for server
2003 = SP2 for winXP??
No, 2003 SP1 does NOT equals XP SP2.
But both contain a number of security enhancements, so if something
was non-default in your setup, SP1 could reveal this.

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
Vera Noest [MVP]
2005-11-04 20:35:02 UTC
Permalink
Could you post the EventID and Source of these Events? That's how
they are searchable.

And please quote the previous content of the thread, makes it much
easier to re-read the thread.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
Post by DEVO
ok i setup verbose logging of userenv, and tried logging in as a
user who only gets a blue background, it the event viewer shows
Windows cannot determine the user or computer name. (specified
domain either does not exist or could not be contacted. ) Group
Policy processing aborted.
Windows saved user Orlane\norman registry while an application
or service was still using the registry during log off. The
memory used by the user's registry has not been freed. The
registry will be unloaded when it is no longer in use.
This is often caused by services running as a user account, try
configuring the services to run in the LocalService or
NetworkService account.
??? hope that helps
Loading...