Sign in
Microsoft.com
 
Windows Server TechCenter
 
 
 
Windows Server TechCenter > Windows Server Forums > Windows Server 2008 R2 Management > RSAT problem connecting to Server 2008 R2
Ask a questionAsk a question
Search Forums:
 

AnswerRSAT problem connecting to Server 2008 R2

  • Wednesday, September 09, 2009 5:35 PMKrisztian M. Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Dear forum members,

    I have to set up a domain member Hyper-V Server 2008 R2 box, so in order to manage that computer remotely, I downloaded the "Remote Server Administration Toolkit for Windows 7". Now the problem comes. The machine I would like to use for the management is not a domain member. When I open "server manager" from "administrative tools" it offers me that I can connect to an other computer instead of the one I'm sitting in front of. In spite the fact that I can connect to a remote machine, I can't use an alternate credential to connect to the server, so finally... I get an access denied message. If anyone had this problem already, please let me know how can I connect to that machine in order not to get an access denied message.

    ps.: I also checked the "scheduled tasks" snap in and it offers me to enter another credential, so I'm a bit confused with this. Why can I use this with my credential and why can't I use the server manager?

    Thank you a lot for your help,
    Chris
    Krisztian M.
     

Answers

  • Thursday, September 10, 2009 9:48 AMMervyn ZhangMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    1
    Sign In to Vote

    Hi Chris,

    I’m afraid you have to join the machine you would like to use for management into Domain to solve this problem.

    In Domain, authentication and authorization are performed on Domain Controller which access AD database to find user information. If the machine is not in Domain, the machine store user account information in local database and only has local user information since authentication and authorization is based on local account database.  It would have no idea of any Domain User and AD has no information of this local account. So the local user cannot pass AD authentication and authorization.

    Thanks.

     

    This posting is provided "AS IS" with no warranties, and confers no rights.
     

All Replies

  • Thursday, September 10, 2009 9:48 AMMervyn ZhangMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    1
    Sign In to Vote

    Hi Chris,

    I’m afraid you have to join the machine you would like to use for management into Domain to solve this problem.

    In Domain, authentication and authorization are performed on Domain Controller which access AD database to find user information. If the machine is not in Domain, the machine store user account information in local database and only has local user information since authentication and authorization is based on local account database.  It would have no idea of any Domain User and AD has no information of this local account. So the local user cannot pass AD authentication and authorization.

    Thanks.

     

    This posting is provided "AS IS" with no warranties, and confers no rights.
     
  • Monday, September 14, 2009 6:44 AMMervyn ZhangMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    Hi,

    Do you need any other assistance? If there is anything we can do for you, please let us know.

    Thanks.

    This posting is provided "AS IS" with no warranties, and confers no rights.
     
  • Tuesday, November 03, 2009 2:29 PMMohsen Almassud Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    you might be able to do a run as. something like this:

    right click the icon while holding on the shift key, and then click on copy path. from cmd type in runas /user:<name of the computer you want to manage>\administrator <paste the path you copied>

    when prompted for a password, enter the administrator's password for the computer you're trying to manage.

    this should work.
    Mohsen