Tech Support > Microsoft Windows > No desktop or taskbar displayed for domain user
No desktop or taskbar displayed for domain user
Posted by Library Sysadmin on March 30th, 2006


XP Pro SP2, on a Win2K domain; Group Policy OU set up for the XP machines and
adm files updated to 2003 versions for the OU. If it makes a difference, the
device in question is a Compaq Evo N1020v laptop.

Fresh install of XP SP2 and updates performed on machine, created a System
Restore point, then add machine to domain and OU. Test user logs in and
there is no desktop display, no taskbar. Only the background wallpaper
displays. User can press <CTRL>-<Atl>-<Del> and log off, shut down, change
password, etc. Local administrator can log on and see desktop and taskbar
and work normally.

No error messages/warnings displayed in event log.
No spyware/malware present.

User is in Domain Users security group. Machine is in Domain Computers
security group. Profiles are roaming and cached copies retained on local
machine. On local machine, Domain Users are members of the local Users
security group and Domain Admins are members of the local Administrators
group.

To isolate where problem is:
1. In ADUC, move machine to Computers container and run a System Restore on
the device and make sure Event logs are cleared.
2. Move user to the Users container. User can log in and display desktop
and taskbar as normal.
3. Move user back to OU. User can still log in and see desktop and taskbar.
4. Move machine back to OU. User can no longer see desktop and taskbar.

Delete user and all existing user profile copies; repeat the above steps,
recreating the user. Same results.

This is obviously some machine policy, but I cannot determine which one. We
do utilize the File System security permissions and Software Restriction
group policies. Again, there are no errors in event log at all, let alone
any saying the user does not have permissions or is prevented by policy from
running something.

If anyone has any ideas as to what to look for, I would appreciate it.
Would save a lot of time from ripping the entire machine policy apart and
restoring it one policy at a time to find which one is the culprit.

TIA
Rick


Similar Posts