Brand new user profile sees "user profile service service failed the logon. User profile cannot be loaded" over RDP

-

windows server 2008.

server plagued user account stuck @ "please wait system event notification service" during rdp logout , have not quick access hard reboot machine , haven't found way restart these user profiles. (best guess related bug http://support.microsoft.com/kb/2383928#appliesto).

administrator "restart pc" not seem work either, hangs @ same screen or cannot restart because of other profiles stuck in oblivion.

i've tried creating new administrator profiles, reason brand new profiles seeing "user profile service service failed logon. user profile cannot loaded" on rdp" @ logon.  know worked in past.

what can solve either 1 (or both) of these problems on last remaining working remote desktop user login.  have no easy physical access server.

 

 


hi,
 


generally, when user login, check profile in following sequence:
 
1. windows check "hkey_local_machine\software\microsoft\windows nt\currentversion\profilelist\<sid>" see whether there existing profile of user.
a. if registry key exists, check profileimagepath under registry current existing profile.
b. if profile not exist or accessible, windows log user on temp profile.
c. if profile accessible, sync roaming profile local profile.
d. after that, load profile.
 
2. otherwise, if "hkey_local_machine\software\microsoft\windows nt\currentversion\profilelist\<sid>" not exist, means no existing profile user. in situation, behave in way:
a. create local profile based on local default profile.
b. if there roaming profile configured , roaming profile exists, sync roaming profile local profile. after that, load profile.
c. if roaming profile configured no existing roaming profile, local profile directly.
d. upon user logoff, sync local profile central location of roaming profile.
 
if using roaming profile, issue may occur if network path not accessible or if user not have enough permission.
 
create central roaming profile, need set following permission. example, roaming \\server\apps\format\dev\users
a). share permission of share folder "apps", "authenticated user" , "domain users" must granted full control permission
b). ntfs permission of exact parent folder of roaming profile (here, it's users"), "authenticated user" , "domain users" must granted full cotnrol permission
c). other folder of path, example "format" folder here, "authenticated user" , "domain users" must have general read ntfs permission.
 
notice: please make sure server service started on server stores roaming profile.
 
 
meanwhile, find microsoft technet articles describe events above:

 
the user profile service (profsvc) crashes in windows server 2008 or windows vista sp1 systems when service loads or unloads user profiles contain compressed files or folders
http://support.microsoft.com/kb/959125
 
a temporary profile loaded after log on windows vista-based system
http://support.microsoft.com/default.aspx?scid=kb;en-us;947242

 

 

 

 

thanks.



Windows Server  >  Remote Desktop Services (Terminal Services)



Comments

Post a Comment

Popular posts from this blog

some help on Event 540

-
does event 540 me distinguish between user , administrator access?    this event generated ypon successfull logon, logon exactly? successful logon on system?   is there other way log administrator access system using event viewer?   thank valuable response   georges hi,   as far know, cannot distinguish between user , administrator access event 540. more information, please refer to:   event id: 540 http://www.microsoft.com/technet/support/ee/transform.aspx?prodname=windows+operating+system&prodver=5.0&evtid=540&evtsrc=security&lcid=1033   events 528 , 540 http://blogs.msdn.com/b/ericfitz/archive/2004/12/09/279282.aspx   regards, bruce this posting provided "as is" no warranties, , confers no rights. please remember click "mark answer" on post helps you, , click "unmark answer" if marked post not answer question. can beneficial other community members reading thread.
Read more

WMI Repository 4GB limit - Win 2003 Ent Question

-
Image
hi there, i've question size limit on wmi repository (being 4gb). if isn't correct place post this, apologies , can let me know wheere post this? i've come across few servers running citrix have reached limit on wmi repository size , need install ibm director agent hw monitoring. during install getting 'out of disk space' errors entered in mofcomp.log: "(mon apr 02 04:10:36 2012.172843) : error occurred while processing item 4: (mon apr 02 04:10:36 2012.172843) : error number: 0x8004103b, facility: wmi description: out of disk space" when error number http://msdn.microsoft.com/en-us/library/windows/desktop/aa394559%28v=vs.85%29.aspx i see this: wbem_e_out_of_disk_space 2147749947 (0x8004103b) disk out of space or 4 gb limit on wmi repository (cim repository) size reached. windows xp , windows 2000/nt:   disk out of space. i'm wondering if there reason why limit set 4gb or can increase needs be? can't seem find reas
Read more

Event ID 1302 (error 1307) DFS replication service encountered an error while writing to the debug log file

-
Image
hello. we @ step 0 of migration frs dfsr sysvol replication on windows 2008r2 dc. every time run powershell dfsrmig / getmigrationstate says: "unable create dfsr migration log file. error 1307. all domain controllers have migrated global state 'start'. migration has reached consistent state on domain controllers. succeeded." it creates event id 1302 in "dfs replication" event log, explaining error 1307 means: "this security id may not assigned ownder of object ". i already checked space limits, quotas, permissions on c:\windows\debug according microsoft support article unable fix it. although, there new entries added dfsr00095.txt log file despite error. dfsrxxxx file has not been archived .gz format, and, beleive, contains dfsr diagnostics , events. here of latest entries: 20150908 08:47:27.867 11616 sysm  3354 migration::sysvolmigration::getsysvolreadyflag [mig] sysvol ready 20150908 08:47:27.867 11616 sysm   456 migrati
Read more