lundi 30 avril 2012 16:01
I work IT at a high school and my group manages about 600 desktops + 500 laptops. We've had TEMP profile login issues for quite some time now, but only in certain locations on desktops only. It hasn't necessarily been a huge problem since we don't use roaming profiles in AD. However, the users' network drive will not map correctly when they get a TEMP login. The local Administrator profile also receives a TEMP on various desktops. The issue started to appear in February.. seemingly out of the blue since no changes were made to the machines or network. It's also random. I will try to provide all relevant information.
I have done every single troubleshooting step short of starting from scratch with a base image. That's not an easy task since we maintain about 20 separate ones. We have 3 schools in the district and we are the only ones seeing the problem. We use separate images from the other two, so it's possible ours is corrupted somehow. The kicker is trying to figure out what's causing it.
This is the message received upon login:
Here is a screenshot of one computer's profile directory:
I finally thought I narrowed down a Symantec process causing the TEMP, but disabling it did nothing to prevent the TEMP during future logins:
Notice the ProfileImagePath on the local administrator account. The S-1-5-21 entry doesn't not contain a .bak, and the imagepath was changed to Administrator.LocalComputerName. This was after the first login upon joining the domain that the TEMP was created. But our master image contains no TEMP, so it seemingly only occurs after joining the domain.
Any help would be greatly appreciated. New problems, such as a missing network and volume icon, have started to disappear from the taskbar. We believe this is related to the TEMP logins.
Toutes les réponses
mercredi 2 mai 2012 08:08Modérateur
Accoring to the event log, I suggest uninstalling the Symantec, then try to log on again.
Also, you may try to delete the administrator's profile and let it automatically created.
TechNet Community Support
- Marqué comme réponse Juke ChouMicrosoft Contingent Staff, Moderator mercredi 23 mai 2012 10:00
mercredi 2 mai 2012 16:16
Are you using a customised Default User, either in the Netlogon folder or on the local machine?
Problems occur if you simply copy the Default User profile like you would back in the NT, 2000 and XP days. You now have to use Sysprep and the CopyProfile component, else you can get the above error.