• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 548
  • Last Modified:

Profile Problem

You have been logged on with a temporary profile.  you cannot access your files and files created in this profile will be deleter when you log off.
0
SheilaG
Asked:
SheilaG
  • 7
  • 5
  • 2
1 Solution
 
jonahzonaCommented:
This isn't a very descriptive problem. This happens with Windows XP Pro if you are forced to change your password while logging in.

Can we get some more specifics? OS? Domain? Roaming Profiles? Etc...
0
 
ajpowell74Commented:
What OS are you using?
Does this error occur only when you log onto the machine, or if anyone else logs on?
0
 
SheilaGAuthor Commented:
Windows 7 Pro on a Windows Server 2008.  The entire message when logging on to the network is You have been logged on with a temporary profile.  You cannot access you files and files created in this profile will be deleted when you log off.  To fix this log off and try logging on later.  Done that but still no luck.  Sheila
0
Evaluating UTMs? Here's what you need to know!

Evaluating a UTM appliance and vendor can prove to be an overwhelming exercise.  How can you make sure that you're getting the security that your organization needs without breaking the bank? Check out our UTM Buyer's Guide for more information on what you should be looking for!

 
SheilaGAuthor Commented:
I will chek using another profile and get back to you.  
0
 
jonahzonaCommented:
Sounds like you may have not specified the proper path to the profile in AD for that user, the file doesn't exist or they may not have permissions to it.

Check those three things first.
0
 
SheilaGAuthor Commented:
Just logged on the machine with another user's log on info -- not an admin.  No problem logging in.  All workers here have roaming profiles.  
0
 
SheilaGAuthor Commented:
This just happened.  I had to wipe out her computer -- infected with a rogue virus.  I totally wiped it out and reinstalled everything.  Her profile was usable yesterday on another machine.
0
 
ajpowell74Commented:
And now it's happening no matter where she logs on?
Does her profile have a trailing slash at the end?
(I.E. \\server\share\user.name or \\server\share\user.name\)

It's possible that you're going to have to re-create the profile if it's just the one user that's affected.
0
 
SheilaGAuthor Commented:
Yes, but I am going to try doing it in the profile on the server.  She can't log on anywhere right now, but others can log on her machine so that's not the proflem.  No trailing slash.  
0
 
ajpowell74Commented:
You can try this on the local machine first:

{Caveat: *Always* make a backup of any registry keys you are modifying. If you don't export the key you're working on, and things go haywire, that's all on you. ;) }

1. Log on to the system by using an administrative user account other than the user account that is experiencing the problem.

2. Back up all data in the current user’s profile folder if the profile folder still exists, and then delete the profile folder. By default, the profile resides in the following location:
%SystemDrive%\Users\UserName

3. Click Start, type regedit in the Start Search box, and then press ENTER. If you are prompted for an administrator password or for confirmation, type your password, or click Continue.

4. Locate the following registry subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList

5. Under the ProfileList subkey, delete the subkey that is named SID.bak. (meen some folder which terminates or has .bak)

Note SID is a placeholder for the security identifier (SID) of the user account that is experiencing the problem. The SID.bak subkey should contain a ProfileImagePath registry entry that points to the original profile folder of the user account that is experiencing the problem.

6. Exit Registry Editor.
7. Log off the system.
8. Log on to the system again.

After you log on to the system, the profile folder is re-created.

I will work on digging up more information on re-creating the profile at the server level and post here.
0
 
SheilaGAuthor Commented:
Belive it or not I have already done that but there isn't anysubkey named SID.bat or anything with a .bat extension.  
0
 
ajpowell74Commented:
Do you mean .bak? :)
0
 
SheilaGAuthor Commented:
Sorry, .bat.
0
 
ajpowell74Commented:
Since it doesn't sound like it's a local profile corrupting the roaming profile, I think this page will be helpful for you:
http://technet.microsoft.com/en-us/library/bb726990.aspx

In particular I would recommend the sections for -
Copying an Existing Profile to a New User Account
and
Copying or Restoring a Profile

I think that you're going to have to take the server-side profile, copy it to a new path (possibly by just copying the folder, adding the .v2 extension to it) and then assigning the new folder as the profile for her in her AD account, and adjusting the folder permissions so that her account can access it.

You may also have to "seed" the new profile folder locally to a machine for the first time that she logs in to ensure that the mapping is correct.
0

Featured Post

Firewall Management 201 with Professor Wool

In this whiteboard video, Professor Wool highlights the challenges, benefits and trade-offs of utilizing zero-touch automation for security policy change management. Watch and Learn!

  • 7
  • 5
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now