Why not remove the local profile at logoff by tricking the OS into thinking it is a temporary profile? Sent from my Blackberry, which may be an antique but delivers email RELIABLY -----Original Message----- From: Angela Smith <angela_smith9@xxxxxxxxxxx> Sender: thin-bounce@xxxxxxxxxxxxx Date: Wed, 20 Mar 2013 16:42:23 To: thin@xxxxxxxxxxxxx<thin@xxxxxxxxxxxxx> Reply-To: thin@xxxxxxxxxxxxx Subject: [THIN] Strange Local Profile issue Hi I'm having a terrible day today.. We do not use roaming profiles in our environment. We use local profiles only which are deleted every night via batch file. We use GPO to redirect specific parts of the profile to the users Personal network share. When user logs in for the 1st time and launch the application it works fine. If the user closes his apps and tries to relaunch the same application from the same server then they get the following error: Windows cannot log you on because your profile cannot be Loaded. Check that you are connected to the network, or that your network is functioning correctly. If this problem persists, contact your network administrator. DETAIL - Incorrect function I have the same issue on 2 different Windows 2003 servers that I did testing on. Therefore there is no issue with default user profile on either server. Its possible there is a policy setting which is causing this. If I delete the local profile then user can login and start an application. Issue is simply opening existing local profiles.. Im not 100% if profile is being unloaded correctly. There are no errors in event log except the following: Event ID 1500 Windows cannot log you on because your profile cannot be Loaded. Check that you are connected to the network, or that your network is functioning correctly. If this problem persists, contact your network administrator. DETAIL - Incorrect function Has anyone seen such behavior? Any assistance appreciated Ang