can't login into console session remotely on Server 2008 machine

i've just upgraded a Server 2003 machine to Server 2008 x86. everything seems to have gone smoothly but for some reason i can't log into the console session via remote desktop. i am able to do this on all the other servers, whether 2003 or 2008, using the "mstsc /v:servername /admin" command.

i'm stumped. i've just finished the upgrade so i can't imagine it's any third-party software. the only thing that's on there is SyncBack and the Promise WebPAM RAID controller utility. other than this oddity everything seems to be working fine.

i'm hoping someone else has encountered this and has a solution.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

B HCommented:
what's the error message?
what if you use just "mstsc /admin"
(then fill in the server name and hit connect)
WALKERMACYADMINI.T. ManagerAuthor Commented:
there's no error message. it logs in fine, but it creates another session instead of using the current console session, which usually has something going on that i need to keep track of when i'm not in the server room.

i won't be able to test anything else out until tomorrow.
B HCommented:
do you have it set to only allow one connection per username?  you might want to do that, or it will create a new session for you
Protecting & Securing Your Critical Data

Considering 93 percent of companies file for bankruptcy within 12 months of a disaster that blocked access to their data for 10 days or more, planning for the worst is just smart business. Learn how Acronis Backup integrates security at every stage

The new version of RDP doesn't allow the "/console" switch. The new switch is "/admin"
WALKERMACYADMINI.T. ManagerAuthor Commented:
yes, that's what i'm using. i stated that in my question.
Ahh, sorry, I'm a moron. Have you checked to see if you are using the latest version of RDP? Or yu can try changing the /damin back to /console to see if that works.

Also try saving the RDP settings file onte your dsektop (or anywhere else that's easy to access), and then edit it in notepad. Make sure that it has the following line:
connect to console:i:1
Isn't it suppose to be mstsc /v [server] -console ?
WALKERMACYADMINI.T. ManagerAuthor Commented:
i always use "mstsc /v:servername /admin" and it always works, until this particular machine. it works with this machine, even, it just doesn't log into the console session. my admin workstation is Win 7 Pro, which has the newest version of RDP available (6.1.7600). the ones on the servers are also 6.1, at least, as they are all Server 2008 or 2008 R2.

the issue isn't my command, the issue is something in the server settings. i only have this problem with this server and it's also the only Server 2008 machine that's x86. i think it's forcing a new session with each login rather than allowing an existing session to be logged into, but i don't know why it would be doing that when none of the other Server 2008 machines do that. i'm just hoping someone else has encountered this same issue and knows how to fix it, otherwise i have to do a clean install, and i'd rather avoid that if i can. however, i suspect it's some kind of buggy behavior resulting from upgrading a Server 2003 installation instead of doing a clean install.
After the update, maybe the right didn't copy right?
Reviewing the right might help ?  Look in "advanced system settings"
WALKERMACYADMINI.T. ManagerAuthor Commented:
i just ended up doing a clean install. this is going to be a domain controller and needs to be perfectly functional. since it wasn't doing much but running SyncBack, it was worth the extra time to make sure it's in good working order.

i can log into the console session remotely now with no problems. must have been some weirdness with doing an upgrade of a Server 2003 install.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.