Link to home
Start Free TrialLog in
Avatar of Magothytech1
Magothytech1Flag for United States of America

asked on

XP profiles olny load when the everyone group is added to the local administrator group

XP profiles olny load when the everyone group is added to the local administrator group.

If removed the user can still log into the domain but their desktop settings don't appear and many applications like Excel and Word open but with error messages.

Is there an easy solution to resolve this issue?
Avatar of laskovd
laskovd
Flag of Israel image

Hi Magothytech1
1. Any errors on Event Viewer?
2. How You connect clients to Windows SBS 2003? Over SBS ConnectComputer wizard?
http://servername/ 
then connect computer to the network.
3. Xp SP2?
Avatar of Magothytech1

ASKER

There are no errors relating to the profile within the event viewer.

All client systems are XP-PRO with SP2

We simply added each computer by chnaging the old domain name to he new domain name. I wonder if we should have added them back to a workgroup first, then rebooted and readded the client to the new domain.
As it went each client system was already logged in to the existing domain and sitting at the desktop when when shut the old server down and the connected the new server and added each client to the new domain.
Rebooted each and verify the all the drives were mapping okay, no porblems there.  
The only problem began when we removed the local everyone group out of the local administrator group on ech PC. We were trying to make it so the users can not change their settings to much and we wanted to limit the ability to install software locally on each desktop.
ASKER CERTIFIED SOLUTION
Avatar of laskovd
laskovd
Flag of Israel image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Solved: It ended up be a profile rights issue.

Thanks for all the support!