Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
?
Solved

On 2003 Terminal Server Local User Cannot Logon

Posted on 2011-02-16
3
Medium Priority
?
1,270 Views
Last Modified: 2012-05-11
Windows 2003 terminal server joined to a Windows 2003 AD. By Computer GPO TS is configured to use roaming profiles.  I need to create a new local user. When the local user firsts logon (the logon which creates the profile) the logon fails because the server can not find the roaming profile on the file server. Then it attempts to open the local profile. This fails, so a temporary profile is assigned.  
 Logon Error Messages
These are the attempts made to resolve this issue.
1.  In My Computer properties, copied another profile and assigned permissions to the new local user.  The profile copies successfully, the new user has full control over the copied profile.  

2.  Directly copied another profile and then manually assigned the new user’s permissions.  Full control was the permission given.

3.  Created a share on the terminal server and then in the user’s property assign the local share as the roaming profile path.

How can I get a local user a logged on?
0
Comment
Question by:epmmis
3 Comments
 
LVL 3

Accepted Solution

by:
rxdeath earned 750 total points
ID: 34911957
sounds to me like something isn't correct in ad maybe...is this terminal services?  if so what do you have in the properties box for the user and terminal service profile location...does that place exist and is it accessible?

if you're doing it with gpo's same deal, what is the path, does it exist and hows it's permissions
0
 
LVL 11

Assisted Solution

by:Venugopal N
Venugopal N earned 750 total points
ID: 34913891
Did you check if any domain account present , with the name as you created a local account
0
 

Author Closing Comment

by:epmmis
ID: 34929407
Much to my chagrin, I learn today every thing is working perfectly.
While preparing my response I read the following about the "Set path for Remote Desktop Services Roaming User Profile" policy.

"By default, Remote Desktop Services stores all user profiles locally on the RD Session Host server. You can use this policy setting to specify a network share where user profiles can be centrally stored, allowing a user to access the same profile for sessions on all RD Session Host servers that are configured to use the network share for user profiles.  
If you enable this policy setting, Remote Desktop Services uses the specified path as the root directory for all user profiles. The profiles are contained in subfolders named for the account name of each user."

Then I realized RDP was used for every connection attempt.  Per the above policy, the logon could never succeed due to the roaming profile setting.

<== Solution ==>
Logon at the console.   *sigh* yep it is that simple.
0

Featured Post

Efficient way to get backups off site to Azure

This user guide provides instructions on how to deploy and configure both a StoneFly Scale Out NAS Enterprise Cloud Drive virtual machine and Veeam Cloud Connect in the Microsoft Azure Cloud.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Let's recap what we learned from yesterday's Skyport Systems webinar.
Scripts are great for performing batch jobs against users, however sometimes the GUI is all you need.
This video shows how to use Hyena, from SystemTools Software, to bulk import 100 user accounts from an external text file. View in 1080p for best video quality.
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…

578 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question