DijitalLee
asked on
Connect to Desktop does not work on XP upgrade PC's
I have several PC's that had Windows 2000 Professional
installed on them. We decided to upgrade them to Windows
XP (upgrade, not clean install). Now, when the users of
those PC's login through the remote workplace, and
attempt to connect to their desktop PC's, they receive an
error message "The local policy of this system does not
allow you to logon interactively." This even happens
when I attempt to logon using the administrator
user/pass. I have looked at the Remote Desktop
configuration on the PC, and it is identical to that of a
PC running a clean install of Windows XP. I even
manually added the user to the list of users allowed to
remote into the machine, but still receive this same
message. Again, this is only happening on machines that
have had a Windows XP upgrade performed on them. Any
suggestions? Anyone else experience this?
installed on them. We decided to upgrade them to Windows
XP (upgrade, not clean install). Now, when the users of
those PC's login through the remote workplace, and
attempt to connect to their desktop PC's, they receive an
error message "The local policy of this system does not
allow you to logon interactively." This even happens
when I attempt to logon using the administrator
user/pass. I have looked at the Remote Desktop
configuration on the PC, and it is identical to that of a
PC running a clean install of Windows XP. I even
manually added the user to the list of users allowed to
remote into the machine, but still receive this same
message. Again, this is only happening on machines that
have had a Windows XP upgrade performed on them. Any
suggestions? Anyone else experience this?
you have to allow users to logon via terminalservices in
local sec pol>local pol>assign userrights> "allow users to logon to terminalserver"
(default: Admins. Add there your User or group)
you could also define a gpo, to push this configuration to multiple computer
local sec pol>local pol>assign userrights> "allow users to logon to terminalserver"
(default: Admins. Add there your User or group)
you could also define a gpo, to push this configuration to multiple computer
DijitalLee,
Did you ever figure out the problem you were having. The comments above are for settting security which I believe you have already done. I am having the same exact problem. XP Pro machines with a clean install.....no problem.....XP Pro machines upgraded from W2K Pro machines cannot connect...even with the admin name and password. My remote user group and local security policies are identical to the machines with a clean install of XP Pro. As you said before...the only differernece I can see is clean install vs. upgrade, which sounds ridiculous but doesn't change the fact that it is the only thing differerent about these machines.
Did you ever figure out the problem you were having. The comments above are for settting security which I believe you have already done. I am having the same exact problem. XP Pro machines with a clean install.....no problem.....XP Pro machines upgraded from W2K Pro machines cannot connect...even with the admin name and password. My remote user group and local security policies are identical to the machines with a clean install of XP Pro. As you said before...the only differernece I can see is clean install vs. upgrade, which sounds ridiculous but doesn't change the fact that it is the only thing differerent about these machines.
ASKER
I have not found a resolution to this as of yet. I posted on the Microsoft newsgroup, and the response I received was that the users must be a member of the local administrative group on the specific PC. This does not work either. Besides the fact that it is not an acceptable solution, since we do not configure our users with administrative privileges on machines.
I'm still trying to figure this out. I don't want to have to do a fresh copy of XP on each PC.
I'm still trying to figure this out. I don't want to have to do a fresh copy of XP on each PC.
ASKER
berni1234,
Does this need to be done on the SBS, or on the local PC? I have already added users to the list allowing them to have remote desktop access. As I mentioned, even the Domain Admin login is not permitted access. This login should definitely have this privilege, yet it still gets denied access.
Does this need to be done on the SBS, or on the local PC? I have already added users to the list allowing them to have remote desktop access. As I mentioned, even the Domain Admin login is not permitted access. This login should definitely have this privilege, yet it still gets denied access.
I hear ya. I have 10 machines done from a windows 2000 upgrade and one machine done with a clean install. And like I said before the one clean install works. This is what I tried tonight (note : this was done ALL remotely)
1. Took out all local user, local admins, remote users, domain remote users....basically everything but the local admin.
(now the ONLY person who could RD in was the administrator)
2. Added my domain user login to the remote desktop users group on the local machine.
(now my user could RD in....but no local admin rights)
Next prob doesn't apply to you, but it does to me...so i'm going to say it anyway
3. Added my domain user login to the admin group on the local machine.
(my user now has local admin rights, but remember he could log in remotely even before I did this step)
And as far as the local security policy "log on locally" goes...well I have the following groups - admins, backup operators, guest, power users, users (have not touched the policy since day one)
As far as what berni1234 said, I have checked that, and I have administrators and remote destop users in there
I will not be onsite until this weekend....so I can't play with the above steps or what berni1234 said on the upgraded machines until then. But if you try to start fresh with the above steps before then....let me know what happens.
1. Took out all local user, local admins, remote users, domain remote users....basically everything but the local admin.
(now the ONLY person who could RD in was the administrator)
2. Added my domain user login to the remote desktop users group on the local machine.
(now my user could RD in....but no local admin rights)
Next prob doesn't apply to you, but it does to me...so i'm going to say it anyway
3. Added my domain user login to the admin group on the local machine.
(my user now has local admin rights, but remember he could log in remotely even before I did this step)
And as far as the local security policy "log on locally" goes...well I have the following groups - admins, backup operators, guest, power users, users (have not touched the policy since day one)
As far as what berni1234 said, I have checked that, and I have administrators and remote destop users in there
I will not be onsite until this weekend....so I can't play with the above steps or what berni1234 said on the upgraded machines until then. But if you try to start fresh with the above steps before then....let me know what happens.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Well berni1234,
If it was up to me...you def get the points...regarding "There is also an option "allow to logon to terminalserver" in AD Users&Computers (User>properties>Terminals
Thanks again!
If it was up to me...you def get the points...regarding "There is also an option "allow to logon to terminalserver" in AD Users&Computers (User>properties>Terminals
Thanks again!
@jimmy
yes, simply create a gpo for admin-remote-desktop and associate it with the ou´s where the computers reside in. or associate it with the whole domain (be carefull, if you associate it with the domain, because it also affects your servers - maybe not all admins should be allowed to logon via rdp to your servers)
regards,
bernhard
yes, simply create a gpo for admin-remote-desktop and associate it with the ou´s where the computers reside in. or associate it with the whole domain (be carefull, if you associate it with the domain, because it also affects your servers - maybe not all admins should be allowed to logon via rdp to your servers)
regards,
bernhard
- Info