Solved

Windows 7 Pro - Remote Desktop Greyed out

Posted on 2014-04-17
8
7,831 Views
Last Modified: 2014-06-17
Hi there .

I've got a Windows 7 Professional PC on an SBS 2011 network. All the other PCs are fine but  this one has all the remote desktop options greyed out. It's on a domain but is the same even when logged in with a local admin account.

How can I turn it on?

I've checked Gpedit.msc (as with http://marktab.net/datamining/2011/07/18/technical-bulletin-windows-7-remote-desktop-options-grayed/) and all settings there are set to 'not configured' I Even tried setting
 "Allow users to connect remotely using Remote Desktop Services" to 'Enabled' but that didn't do anything either.

I've checked regedit.
HKLM\Software\Policies\Microsoft\Windows NT\Terminal Services.  fDenyTSConnections is set to 0

The PC is fully up to date with updates. SFC comes up clean, etc. Local Firewall has been reset to 'default'

In services:
Remote Desktop Configuration
Remote Desktop Services
Remote Desktop Services UserMode Port Redirector
are all set to manual and have started.

I've tried to access using a local admin account, the SBS administrator account and the standard domain users account for the machine (set as local admin). None of which work.

SBS 2011 has the PC mentioned in it's list of computers but is marked as 'offline'

I've tried deleting and reapplying the machine to the domain using https://connect but that didn't fix it either.

All other machine on the network are running OK and the user of the computer in qustion can access other PCs in the office remotely so it appears to be a PC related issue than a user related one.

Anything else I can try?
0
Comment
Question by:Dale303
  • 3
  • 2
  • 2
  • +1
8 Comments
 
LVL 13

Assisted Solution

by:Andy M
Andy M earned 167 total points
ID: 40006949
Usually this would be due to group policy settings - I would run a gpresults on the PC and check through that for any setting relating to it.

You could also try disabling the firewall and see if the SBS box lists it as online.
0
 
LVL 74

Assisted Solution

by:Jeffrey Kane - TechSoEasy
Jeffrey Kane - TechSoEasy earned 167 total points
ID: 40011080
You need to run a Group Policy report on that workstation to see what is causing the settings to be blocked.

Open an elevated CMD prompt and run the following:

gpresult /h gp.html

This will create a nice html report (called gp.html) in whatever directory you ran the command from.  If you need help interpreting it, post the full report back to this question.
0
 

Author Comment

by:Dale303
ID: 40011344
Already done that but the report is still on the machine. Will retrieve it after the Easter break
0
 
LVL 25

Assisted Solution

by:Tony Giangreco
Tony Giangreco earned 166 total points
ID: 40018462
Click Start, Run. Type GPEDIT.MSC and press Enter.

Navigate to:

Computer configuration,  Administrative Templates, Windows Components, Remote Desktop Services, Remote Desktop Session Host, Connections
 
then in the right-pane, double-click the "Allow users to connect remotely using Terminal Services" and set it to "Not configured"

Click OK, restart and test.
0
Enabling OSINT in Activity Based Intelligence

Activity based intelligence (ABI) requires access to all available sources of data. Recorded Future allows analysts to observe structured data on the open, deep, and dark web.

 
LVL 25

Expert Comment

by:Tony Giangreco
ID: 40018469
Before typing in that command, make sure you are logged in as the domain admin.
0
 

Accepted Solution

by:
Dale303 earned 0 total points
ID: 40045894
Hmm. Something's up with the DNS/DHCP on the server. The PC didn't have the same IP address as what the server thought it did for some reason. Set it up with a fixed IP and now it works fine.
0
 
LVL 74

Expert Comment

by:Jeffrey Kane - TechSoEasy
ID: 40054723
Set it up with a fixed IP and now it works fine.

Not quite the best fix, since it will need to be managed manually from now on if things change on the network.  Better to clear up the DHCP problem.

At any rate, glad you have things working.
0
 

Author Closing Comment

by:Dale303
ID: 40138855
Issue resolved myself and was related to DNS, not RDP.
Thanks guys for helping eliminate the other possibilities.
0

Featured Post

IT, Stop Being Called Into Every Meeting

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

Join & Write a Comment

Storage devices are generally used to save the data or sometime transfer the data from one computer system to another system. However, sometimes user accidentally erased their important data from the Storage devices. Users have to know how data reco…
Our Group Policy work started with Small Business Server in 2000. Microsoft gave us an excellent OU and GPO model in subsequent SBS editions that utilized WMI filters, OU linking, and VBS scripts. These are some of experiences plus our spending a lo…
Windows 8 comes with a dramatically different user interface known as Metro. Notably missing from the new interface is a Start button and Start Menu. Many users do not like it, much preferring the interface of earlier versions — Windows 7, Windows X…
With the advent of Windows 10, Microsoft is pushing a Get Windows 10 icon into the notification area (system tray) of qualifying computers. There are many reasons for wanting to remove this icon. This two-part Experts Exchange video Micro Tutorial s…

706 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

Need Help in Real-Time?

Connect with top rated Experts

19 Experts available now in Live!

Get 1:1 Help Now