Customizing single user connection via Windows remote desktop

Hi,
I would like to know if its possible to configure Windows Remote Desktop in a way that if a user is already logged on to a particular computer and another user tries logging in, an error message appears on the screen saying that a user is already
logged on.
I can limit the number of connections to 1 via:
Local Group Policy Editor > Admin Templates > Remote Desktop Services > Remote Desktop Session Host > Connections
However, with this option, the error message that comes up on the screen is the following:
'This computer cant connect to the remote computer, try again or contact the network administrator'.
Is it possible to configure this in a way to let users know why they cant login so they don't think its an IT fault?
We are using Windows 7 on both the clients and the host.
Any advice would be much appreciated..
Thanks,
Seema

Hi Milos,
No its not a server operating system.
The PC that we are connecting to is running Windows 7.
We are connecting to it using Windows Remote Desktop.
Thanks,
Seema
Hi Seema,
As Licensing agreement said, for Windows 7, you can only has one connection on this PC via RDP.
If another user wants to connect this PC via RDP, he will be notified you another user who has already logged in.
Kate Li
TechNet Community Support

Similar Messages

Connection via Windows Remote Desktop

I want to connect my BlackBerry with the BlackBerry Desktop Software which isn't installed on my local machine but on the computer to which I connect via the Windows Remote Desktop (both are Windows XP Professional). It has worked fine with my old Phone and Microsoft ActiveSync but not with my new BlackBerry. Does anybody have any experience with this scenario?
Many Thanks in advance!
Paul.

you are connecting it to local hardware(PC), how will the remote PC know. it's not posible, please install desktop manager on your local PC.
Click on KUDOS to appreciate our efforts and mark the thread RESOLVED if your issue is resolved.

Outlook Sync issue when connecting to server/Outlook via Windows Remote Desktop

I hope someone can help...I connect to my email etc (Outlook that lives on server) via Windows Remote Desktop. The server keeps my email updated automatically between my BB8330 and Outlook. However it does not keep Calendar, Contacts etc updated. I want to be able to "SYNC" in this scenario without loading any software on the server as the BOSS won't allow that. I really want to keep it simple so I actually do it regularly.
PS I need to say that I think I am looking for a Work Around
Message Edited by Newpoint_2 on 06-25-2009 11:35 AM

not possible to do sync through remote desktop, unless you install DTM on the server and plug the BBinto server and remote to server and tell it to sync... which wou.ld defeat the purpose.
if you are the only BB user and you have exchange you can install BES pro for free(only free for 1 user) which will send everything wirelessly

Yosemite 10.10.1 Update - Can no longer connect to Windows Remote Desktop

I use Mac's VPN to create a PPTP VPN connection to our Windows Server at work. I access the Server using the Microsoft Remote Desktop App from the App Store (v 8.0.10). After upgrading to Yosemite, I could get the VPN to connect but could not get the Microsoft App to connect to the Server. I fixed this problem by deleting the VPN Connection and setting it up new from scratch. It worked fine until the 10.10.1 upgrade. Now it no longer works and my previous fix does not work. I also noticed that I totally lose internet connectivity when the VPN is connected - Safari and Outlook Windows app show no internet connection.
Microsoft App error is :
Unable to connect to remote PC. Please provide the fully-qualified name or the IP address of the remote PC, and then try again.
Please help this has broken with both Yosemite updates and now I am up a creek and unable to work remotely.
Thanks,

I've only one hint to you, cause I've mot on Mac-Server.
With 10.7 Apple have switched from Samba (maybe due to licence problems with GPL based stuff) to a own protocol called "XSMB"
This had caused problems with some NAS systems too.
Eventually someone have a glue to solve that, as several users have problems with SMB shares since that.
Lupunus

Windows 8 crashes when trying to connect to a Remote Desktop or a VPN

Hello,
When trying to perform a connection to a remote desktop or a VPN the application crashes (either MSTSC.exe or Explorer.exe). I've noticed this happens when credentials are about to be asked (same happens when trying to access a restricted folder on a network
machine).
Useful PC specs:
- i7 3770k, 16GB Ram, GTX460 (2x-SLI) (Intel HD 4000 on board)
> All latest drivers and Windows updates installed.
> Ran Memory Diagnostic. No errors.
Event Log:
Faulting application name: mstsc.exe, version: 6.2.9200.16384, time stamp: 0x50108ae1
Faulting module name: DUI70.dll, version: 6.2.9200.16384, time stamp: 0x50108e6a
Exception code: 0xc0000005
Fault offset: 0x00000000000027ee
Faulting process ID: 0x994
Faulting application start time: 0x01cdf16f9b46e882
Faulting application path: C:\WINDOWS\system32\mstsc.exe
Faulting module path: C:\WINDOWS\system32\DUI70.dll
Report ID: dadcc27c-5d62-11e2-bf13-bc5ff4390e7a
Faulting package full name:
Faulting package-relative application ID:
WinDbg: (RDP Crash dump with procdump)
Loading unloaded module list
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(994.1118): Access violation - code c0000005 (first/second chance not available)
dui70!DirectUI::Element::_SetValue+0xe:
000007fe`c5be27ee 488b01 mov rax,qword ptr [rcx] ds:00000000`00000000=????????????????
0:000> .ecxr
rax=000007fec5cbbd80 rbx=000000989f3afa28 rcx=0000000000000000
rdx=000007fec5cbbd80 rsi=00000000fffffffd rdi=00000098a3e805b0
rip=000007fec5be27ee rsp=000000989f23a8b0 rbp=0000000000000000
r8=0000000000000001 r9=000000989f3afa28 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=00000098a1d29401
iopl=0 nv up ei pl nz na pe nc
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010200
dui70!DirectUI::Element::_SetValue+0xe:
000007fe`c5be27ee 488b01 mov rax,qword ptr [rcx] ds:00000000`00000000=????????????????
0:000> !analyze -v
* Exception Analysis *
GetPageUrlData failed, server returned HTTP status 404
URL requested: http://watson.microsoft.com/StageOne/mstsc_exe/6_2_9200_16384/50108ae1/dui70_dll/6_2_9200_16384/50108e6a/c0000005/000027ee.htm?Retriage=1
FAULTING_IP:
dui70!DirectUI::Element::_SetValue+e
000007fe`c5be27ee 488b01 mov rax,qword ptr [rcx]
EXCEPTION_RECORD: ffffffffffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 000007fec5be27ee (dui70!DirectUI::Element::_SetValue+0x000000000000000e)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000000
Attempt to read from address 0000000000000000
DEFAULT_BUCKET_ID: NULL_POINTER_READ
PROCESS_NAME: mstsc.exe
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000000
READ_ADDRESS: 0000000000000000
FOLLOWUP_IP:
dui70!DirectUI::Element::_SetValue+e
000007fe`c5be27ee 488b01 mov rax,qword ptr [rcx]
MOD_LIST: <ANALYSIS/>
NTGLOBALFLAG: 0
APPLICATION_VERIFIER_FLAGS: 0
FAULTING_THREAD: 0000000000001118
PRIMARY_PROBLEM_CLASS: NULL_POINTER_READ
BUGCHECK_STR: APPLICATION_FAULT_NULL_POINTER_READ
LAST_CONTROL_TRANSFER: from 000007fec5be7db8 to 000007fec5be27ee
STACK_TEXT:
00000098`9f23a8b0 000007fe`c5be7db8 : 00000098`9f23a950 00000098`00000004 00000098`9f23a954 00000098`9f3afa28 : dui70!DirectUI::Element::_SetValue+0xe
00000098`9f23a930 000007fe`b5378a73 : 00000098`a3f11208 00000098`9f23aa70 000007fe`b5418c58 000007fe`c4dc20f5 : dui70!DirectUI::Element::SetLayoutPos+0x98
00000098`9f23a970 000007fe`b53a5f7e : 00000098`a3f154d0 000007fe`b533bd54 00000098`a3ea80e0 00000000`00000000 : authui!UserList::_OnEnumerationSyncReply+0x689
00000098`9f23af80 000007fe`b5332670 : 00000098`a3f111f0 000007fe`b53212d1 00000098`a3f153a0 00000000`00000001 : authui!CCredDialog::UIJobEvent+0x15e
00000098`9f23afc0 000007fe`b533cf1b : 00000000`00000000 00000000`00000000 00000000`00000000 000007fe`cae3545f : authui!CEnumerationSyncReplyJob::DeferredExecute+0x20
00000098`9f23b000 000007fe`b533cfbc : 00000098`a3f111f0 00000000`00000001 00000000`00000000 00000098`0000029e : authui!CDeferredUIThreadJob::Do+0x37
00000098`9f23b030 000007fe`b53a7f42 : 00000098`a1d29350 00000000`000e0602 00000000`00000002 00000000`000e0602 : authui!CCredentialJobQueue::_ProcessJobs+0x69
00000098`9f23b070 000007fe`b53a7e76 : 00000000`00000000 00000000`00000000 00000000`00008003 00000000`00000000 : authui!CCredDialog::DialogProc+0xa2
00000098`9f23b0d0 000007fe`c86ab3b9 : 00000000`00000001 00000098`9f23b241 00000000`00008003 00000000`00000000 : authui!CCredDialog::s_DialogProc+0x66
00000098`9f23b100 000007fe`c86ab108 : 00000098`9f9522d0 00000000`00000000 00000000`00008003 00000000`00000000 : user32!UserCallDlgProcCheckWow+0x135
00000098`9f23b1d0 000007fe`c86ab02e : 00000000`00000000 00000000`000e0602 00000000`00008003 000007fe`c4dc120b : user32!DefDlgProcWorker+0xb8
00000098`9f23b2a0 000007fe`c869171e : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : user32!DefDlgProcW+0x56
00000098`9f23b2e0 000007fe`c86914d7 : 00000098`9f9522d0 00000098`9f23b4e0 000007f7`f30de800 000007fe`cae31b95 : user32!UserCallWinProcCheckWow+0x13a
00000098`9f23b3a0 000007fe`c86be067 : 00000098`9f9522d0 00000098`9f9522d0 00000098`9f9522d0 00000000`00000001 : user32!DispatchMessageWorker+0x1a7
00000098`9f23b420 000007fe`c86bc641 : 00000098`9f9522d0 00000098`9f9522d0 00000000`00000000 00000000`0000c000 : user32!IsDialogMessageW+0x242
00000098`9f23b4b0 000007fe`c86bb8a3 : 00000000`00000000 00000000`000909fc 000007fe`b53a7e10 00000098`9f3a6cd0 : user32!DialogBox2+0xfc
00000098`9f23b540 000007fe`c86bb936 : 000007fe`b5320000 00000000`000909fc 000007fe`b53a7e10 000007fe`b53a7df8 : user32!InternalDialogBox+0x113
00000098`9f23b5a0 000007fe`c86bbc1b : 00000000`00000000 000007fe`b5320000 00000098`9f3a6cd0 00000098`9f3a6cd0 : user32!DialogBoxIndirectParamAorW+0x56
00000098`9f23b5e0 000007fe`b53a7c91 : 00000000`00000000 00000000`00000000 00000098`9f3a6cd0 00000098`9f3a6cd0 : user32!DialogBoxIndirectParamW+0x1b
00000098`9f23b620 000007fe`b539d0d0 : 00000098`a1d29350 00000000`00000000 00000098`9f3ec310 000007fe`b7d77987 : authui!CCredDialog::Dialog+0x151
00000098`9f23b670 000007fe`b7d6d268 : 10458c33`00000029 00000098`9f23b800 00000098`9f3ebac0 000007fe`b7d6d370 : authui!CCredUI::CredUIPromptForWindowsCredentialsW+0x1dc
00000098`9f23b700 000007fe`b7d6d503 : 00000098`00000003 00000000`00000000 00000098`9f23ba10 00000098`9f3ebac0 : credui!CredUIPromptForWindowsCredentialsWorker+0x310
00000098`9f23b850 000007fe`ac10c4fd : 00000098`9f3ebac0 00000098`9f23baa0 00000098`9f23ba10 00000098`9f23ba28 : credui!CredUIPromptForWindowsCredentialsW+0x17b
00000098`9f23b8f0 000007fe`ac0a0a85 : 00000000`00000000 00000098`00000000 00000000`00000000 00000000`00000000 : mstscax!CTscCredentialsQueryUi::PromptForCredentialsNew+0x159
00000098`9f23b9c0 000007fe`ac09e8e8 : 00000098`9f362f38 00000000`00000000 00000000`00000000 00000098`a0fed860 : mstscax!CTscCredsAssistant::PromptForTsCredentials+0x4e5
00000098`9f23d050 000007fe`ac0a13f7 : 00000098`9f351050 00000000`00000000 00000000`00000000 00000098`a0f24d50 : mstscax!CTscCredsAssistant::AcquireTsCredentials+0x8f4
00000098`9f23d770 000007fe`ac0716fb : 00000098`a0f24d50 00000098`a0f24d50 00000000`00000000 00000000`00000000 : mstscax!CTscCredsAssistant::OnSecurityLayerNegotiationComplete+0x1af
00000098`9f23e000 000007fe`ac179428 : 00000098`00000002 00000098`a0f5fee0 00000098`a0f5fee0 00000000`00000001 : mstscax!CUI::OnSecurityLayerNegotiationComplete+0x11f
00000098`9f23e060 000007fe`ac179594 : 00000098`a0f1c540 00000000`00000000 00000000`00000000 00000000`00000000 : mstscax!CTSThread::RunQueueEvent+0x104
00000098`9f23e0b0 000007fe`ac17baf2 : 00000098`a0f1c540 000007fe`c8691742 00000098`a0f1bf30 00000000`00000000 : mstscax!CTSThread::RunAllQueueEvents+0xcc
00000098`9f23e110 000007fe`ac17bb28 : 00000098`a0f1bf30 00000000`00000000 00000000`00000000 00000000`00000000 : mstscax!CTSThread::OnNotifyThreadEventQueue+0xa6
00000098`9f23e150 000007fe`abefb451 : 00000000`00000000 00000000`00000000 000061f5`6df98991 ffffffff`ffffffff : mstscax!CTSThread::OnNotifyThreadMessage+0x20
00000098`9f23e180 000007fe`c869171e : 000007fe`c8691742 00000000`00000000 00000000`00035090 00000098`9f919f70 : mstscax!PAL_System_Win32_ThreadWndProc+0x19
00000098`9f23e1b0 000007fe`c86914d7 : 00000098`9f94fb70 00000098`9f23e320 000007f7`f30de800 000007fe`abefb438 : user32!UserCallWinProcCheckWow+0x13a
00000098`9f23e270 000007fe`c86bc6c4 : 00000098`9f950eb0 00000098`9f950eb0 00000000`00000001 00000000`0000c000 : user32!DispatchMessageWorker+0x1a7
00000098`9f23e2f0 000007fe`c86bb8a3 : 00000000`00000000 00000000`000909fc 000007f7`f331d518 000007fe`c81931b2 : user32!DialogBox2+0x219
00000098`9f23e380 000007fe`c86bb936 : 000007f7`f32c0000 00000000`000909fc 000007f7`f331d518 00000000`000909fc : user32!InternalDialogBox+0x113
00000098`9f23e3e0 000007fe`c86bbbe9 : 000007f7`f32c0000 00000098`9f23e4e0 00000000`000909fc 00000000`00000000 : user32!DialogBoxIndirectParamAorW+0x56
00000098`9f23e420 000007f7`f331d788 : 00000000`000909fc 00000098`9f23e570 00000098`9f23e4e0 ffffffff`ffffffff : user32!DialogBoxParamW+0x69
00000098`9f23e460 000007f7`f331ce9e : 00000098`a0efedc0 000007f7`f32c7ab0 000007f7`f333b420 00000000`00000000 : mstsc!CDlgBase::CreateModalDialog+0x168
00000098`9f23e500 000007f7`f32e2604 : 00000098`a0efedc0 00000098`9f23ead0 000007f7`f32c7ab0 00000000`00000000 : mstsc!CDlgBase::DoModal+0x12
00000098`9f23e540 000007f7`f32dbd6b : 00000098`9f4ec3e0 00000098`9f4ec3e0 000007f7`f32c7ab0 000007f7`f333b420 : mstsc!CDefaultContWndExt::OnConnectionIssued+0xec
00000098`9f23e9d0 000007f7`f3302bd9 : 000007f7`f32cbb00 000007f7`f32cbb00 00000000`00000000 00000098`a0f1f350 : mstsc!CContainerWnd::StartConnection+0x4d7
00000098`9f23ee70 000007f7`f3301feb : 00000000`000909fc 00000000`00000111 00000000`000c09be 00000000`00000001 : mstsc!CMainDlg::DialogBoxProc+0xbb9
00000098`9f23f1b0 000007fe`c86ab3b9 : 00000000`00000001 00000098`9f23f331 00000000`00000111 00000000`00000000 : mstsc!CMainDlg::StaticDialogBoxProc+0x63
00000098`9f23f1f0 000007fe`c86ab108 : 00000098`9f919f70 00000000`00000000 00000000`00000111 00000000`00000001 : user32!UserCallDlgProcCheckWow+0x135
00000098`9f23f2c0 000007fe`c86ab02e : 00000000`000c09be 00000098`9f23f500 00000000`00000111 000007fe`cae31b95 : user32!DefDlgProcWorker+0xb8
00000098`9f23f390 000007fe`c869171e : 00000000`00000001 00000000`00000000 00000000`00000000 000007fe`c8be1535 : user32!DefDlgProcW+0x56
00000098`9f23f3d0 000007fe`c86d22f9 : 00000000`000c09be 00000000`00000111 00000000`80000000 00000000`00000000 : user32!UserCallWinProcCheckWow+0x13a
00000098`9f23f490 000007fe`c869487a : 00000000`00000000 00000000`00000000 00000000`00000001 00000098`9f919f70 : user32!SendMessageWorker+0xa72
00000098`9f23f540 000007fe`c86bbdd3 : 00000000`00090a12 00000098`9f919f70 00000000`000909fc 00000000`000909fc : user32!SendMessageW+0x10a
00000098`9f23f5a0 000007f7`f3312409 : 00000098`a0ef0080 00000098`a0ef0080 00000000`00000000 00000000`03260475 : user32!IsDialogMessageW+0x40b
00000098`9f23f630 000007f7`f3312a07 : 000007f7`f32c0000 00000098`9f312374 000007f7`f333b420 000007f7`00000000 : mstsc!TSCMain+0x695
00000098`9f23f6e0 000007f7`f33319c9 : 00000098`9f313100 00000000`00000000 00000000`00000000 00000000`00000000 : mstsc!WinMain+0x42f
00000098`9f23f750 000007fe`c8fe167e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : mstsc!ATL::AtlWinModuleTerm+0x375
00000098`9f23f810 000007fe`cae53501 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x1a
00000098`9f23f840 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x1d
STACK_COMMAND: ~0s; .ecxr ; kb
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: dui70!DirectUI::Element::_SetValue+e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dui70
IMAGE_NAME: dui70.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 50108e6a
FAILURE_BUCKET_ID: NULL_POINTER_READ_c0000005_dui70.dll!DirectUI::Element::_SetValue
BUCKET_ID: X64_APPLICATION_FAULT_NULL_POINTER_READ_dui70!DirectUI::Element::_SetValue+e
WATSON_STAGEONE_URL: http://watson.microsoft.com/StageOne/mstsc_exe/6_2_9200_16384/50108ae1/dui70_dll/6_2_9200_16384/50108e6a/c0000005/000027ee.htm?Retriage=1
Followup: MachineOwner
Any ideas what could be the problem and how to resolve this?

Further proof it's something with credentials/authentication. I found a valid workaround, but I think this one's on Microsoft to actually fix.
I opened up Remote Desktop Connection, put in my username and clicked the Save Credentials box. Then I edited all the other settings. Saved the RDP connection to my desktop. Then I edited it with notepad, and added the password value. I found a blog that
provides a program that'll hash the password for you. I used it so I can say its safe:
http://www.remkoweijnen.nl/blog/2007/10/18/how-rdp-passwords-are-encrypted/
I put the hashed password in, saved the file. Then used it to connect and it worked. So by bypassing RDP having to ask for credentials, it didn't crash since it doesn't ask. Kind of inconvenient if you have many computers you have to connect in to. But for
those in a bind this will work for you.
This one worked for me, no update or installation of software before it broke, but had a "wife-poweroutage" (cable taken out) I'm just not in the mood to reinstall for this. But the above fixed it for me. Thank you!

Unable to connect to my home PC from my home Mac using Windows Remote Desktop

i have downloaded from the Microsoft website and also the Application from the App store and both fail to connect. i have connected to my PC using the migration assistant so they are able to recognise each other.
on the Mac:
- downloaded the app and also done the download from MS website - both fail and suggest to check that remote access is enabled.
on the PC:
- have my Ipaddress from "IPConfig"
- have enabled remote access through windows firewall
The PC is on and has a password enabled
Error on App:
"Unable to connect to remote PC. Please verify remote desktop is enabled, the remote pc is turned on and available on the network and try again"
both are connected to the internet and on the same home network. Can anyone please advise to any additional steps as this seems as though this should be really straightforward. as another note i don't have another firewall software interrupting - am just
using windows firewall until i can get this working.

Hi,
Firstly, please refer to the article below to enable remote desktop connection on your Windows 7.
Remote Desktop Connection: frequently asked questions
http://windows.microsoft.com/en-us/windows/remote-desktop-connection-faq#1TC=windows-7
On your Mac, you can download the app here.
https://itunes.apple.com/hk/app/microsoft-remote-desktop/id715768417?mt=12
More information:
Getting Started with Remote Desktop Client on Mac
http://technet.microsoft.com/library/dn473012
Hope this helps.
Jeremy Wu
TechNet Community Support

PXE Boot a client to connect to a Remote Desktop Session Host/Terminal Server Farm via SCCM 2007

Hi all,
we've got a bunch of old desktops which are destined for disposal but i was wondering if we couldn't use them as disk-free clients to connect to our Remote Desktop farm. I did some digging and have managed to put together an iso which will boot
the machine into WinPE and then connect to our farm. However, since it's an iso i have to use either a cd or usb for this to work. (This is pretty much what i did: http://www.iammacgyver.com/2011/02/easy-rdp-60-from-winpe-30-simple-boot.html)
What i want to do is to advertise the boot.wim to the client via SCCM so that it boots via PXE and then picks up the WinPE image and connect to the RD farm. I've imported the boot.wim file into SCCM under Boot Images and created an empty Task Sequence
with the boot.wim as its Boot Image. I then advertised this Task Sequence to a collection which contains the old desktop clients. The machine PXE boots ok and loads up WinPE but rather than launch a remote desktop connection, it trundles through the normal
WinPE stages and once it's finished 'Preparing Network Connections' it simply ends and the client reboots.
Is what i'm trying actually possible?
Can anyone tell me why the ISO works yet pushing the boot.wim out as a Boot Image doesn't? I know the boot.wim file (which is the same one present in the ISO) is ok since the client boots into WinPE fine when PXE booted so why doesn't the remote
desktop session conenction launch? How is booting from the ISO different from booting from the PXE boot.wim file?
Slightly long winded problem so many thanks in advance to anyone who can pass some info my way!

It doesn't work because importing it into ConfigMgr injects binaries and the task sequence engine along with the process to launch the engine thus suppressing whatever you've got configured.
Perhaps you could use a pre start command (pre-execution hook in 2007 parlance) to launch your RDP process though.
Jason | http://blog.configmgrftw.com | @jasonsandys

Cannot log onto windows remote desktop

How can I log into my office's windows remote desktop. I am very new to the Mac and need some help with this. I have downloaded and installed the Windows Remote Desktop Connection, but i dont know how to use it. Do I need to have a different program to get online and not use Safari.
Please keep it simple, I am not a programer, just a program user.

I USE REMOTE DESKTOP TO CONNECT TO A WINDOWS SERVER AT WORK. YOU MUST OBTAIN THE IP ADDRESS OF THE SERVER AND PUT THAT IP ADDRESS INTO THE RDC WHERE IT ASKS COMPUTER. YOU WILL ALSO NEED THE NETWORK USERNAME AND PASSWORD TO GET ON THE SERVER AT WORK. I ALSO BELIEVE THE SERVER AT WORK NEEDS TO BE SET TUP TO ACCEPT REMOTE CONNECTIONS.

Windows Remote Desktop (Mac)

Hello:
I'm trying to use Windows Remote Desktop (Mac) to connect from a Mac (OSX 10.9.5) to a pc (Windows 7 Pro). When both laptops are on the same network I can connect without issue (using the destination pc's IP4 address). However, when they are not on the same
network I get the error message below* (I use the ISP-provided IP address for this connection). I made sure the ISP router port forwarding settings had the open/end ports (which I got from running the necessary CMDs from my destination pc's dos prompt). I
made sure the destination pc firewall settings allowed Remote Desktop connections (public, domain, home/work). What could I be missing? Thanks!
*Error message:
Unable to connect to remote PC. Please verify Remote Desktop is enabled, the remote PC is turned on and available on the network, and then try again.

Hi Andy,
Which version of MRD MAC you are using for your case?
Please use the latest MRD v 8.0.15 and verify.
As you have commented, you check every network scenario. Suggest again to recheck the related setting for IP address, firewall, port, user permission access and other things. You can also refer beneath article for information.
https://technet.microsoft.com/en-us/library/dn473006.aspx
Hope it helps!
Thanks.
Dharmesh Solanki
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Difference between Terminal server connection and MSTSC remote desktop connection

Hi everyone , Wats the main difference between Terminal server connection and MSTSC remote desktop connection? Well both are used to connect a server remotely. right!
Are there any much difference between them?

RDP is a protocol and MSTSC is the RDP client.
In the situation you are referring to, you use MSTSC (RDP Client) in both cases, but when you connect to a client PC (Windows 7, Windows XP, etc) you can only connect if nobody is using that PC at the moment, if you connect to a server you can work along with
some other users. Server OS supports 2 connections by default, if you want more people you need Remote Desktop Services and RDS licenses.
Thanks,
сила в справедливости

I have an Ipad 2 and here is what I am trying to accomplish. On my laptop I connect to a remote desktop connection to access a shared program we use for reporting. How do I set up my Ipad to access this remote server? Thanks for the help.

I have an Ipad 2 and here is what I am trying to accomplish. On my laptop I connect to a remote desktop connection to access a shared program we use for reporting. How do I set up my Ipad to access this remote server? Thanks for the help.

Close ... before going for a specific Cisco app ... lets find out some details:
Host we need more details:
What is your server environment (Windows Server, or Mac OS X Server, or Linux)?
What security is implemented in your environment - as what is restricted (RDP for all or specifc credentials on all machines? Are you part of local admin group to the server you wish to connect)?
Does your environment Support CISCO IPSec connection? If so use Settings> VPN and IPSec tab to enter VPN details, if not then go with above suggestion. IF your restricted to RSA then either built in VPN settings or 3rd party app for RSA would suffice.
Finally, there are many RDP applications out there I use "Mocha RDP Light" (free minimal ads when launched not when connecting).

Connect via Windows Powershell in SCCM 2012 CONSOLE (with PowerShell 4.0 installed)

Hi,
When trying to "Connect via Windows Powershell" in the SCCM 2012 console, I get the message that Powershell 3.0 is not installed... (which actually isn't installed, we have PS4.0 installed). Do we need to install PS3.0 also to get it working
or is there a workaround? Connecting manually to the site via Powershell 4.0 (Get-Psdrive -psprovider CMSITE) works like a charm.
Regards,
WiM

Hi,
I have installed WMF 4.0 on Windows Server 2008 R2 sp1, it works fine.
Please try to use "$PSVersionTable" to confirm Powershell version is 4.0. At first, I forgot to install Microsoft .NET Framework 4.5, then the console gave me the message that Powershell 3.0 is not installed.
Best Regards,
Joyce Li
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Sharing local devices with remote computers like in Windows Remote Desktop

Morning all,
I'm attempting to access my local machine's CD drive on the remote computer across Apple Remote Desktop. It's ubiquitously possible even in the Windows Remote Desktop Client for OS X but for the life of me can't figure out how to share my drive over the network with a remote client.
Any help would be greatly appreciated!
Thanks

By Remote Desktop, I literally meant from the remote computer. So let me rephrase..
After I've enabled CD/DVD sharing, while I'm in Apple Remote Desktop controlling the remote computer, can I access my CD/DVD drive remotely?
Or to be even clearer, could a remote user on that machine access my CD/DVD drive and how?

BI Publisher Desktop install on Windows remote desktop

Hi all,
Is there any way to install BI Publisher Desktop on windows remote desktop (terminal services)?
If I install this currently as one user, the other user can not access (despite having all the correct security settings). The real issue is I think with MS Office because the Add-in is not seen by other users. But I have no idea how to go about solving this issue.
Thanks.
Px.

There is an Oracle support document [468953.1] that suggests that each user run the installer on a shared machine. This advice doesn't actually work as the second user who attempts to install it on a machine will only be presented with the option to uninstall it.
Just today with the help of ProcessMonitor I have figured out how to deliver it to all users. Note that my setup is Office 2003. The below instructions may need alteration for other versions or may not work at all.
After you have installed BI Publisher Desktop copy the TemplateBuilder.dot file found in:
C:\Documents and Settings\[installing_user_name]\Application Data\Microsoft\Word\STARTUP
to
C:\program files\microsoft office\OFFICE11\STARTUP
This will cause the TemplateBuilder word template to launch at startup for all users and deliver the "Oracle BI Publisher" menu item and BIP toolbar.
Hope this helps. If you are using a version of Word other than 2003 and need to modify the procedure please post any required changes on this thread. I would like to assemble a procedure for all supported versions of Word.

Can Photoshop CS4 be deployed on Windows remote desktop server?

I tried installing Photoshop extended CS4 on a Windows Remote Desktop server (Windows 2008 R2 64bit) and it said it requires at least Windows XP or Vista 64bit as the OS requirement. I can either continue or quit. Can someone verify if this product can be deployed in RDS enviroment?
Thanks

Mark:
Thanks for the input. It worked. Interestingly, I first tried installing CS5 but the install just stopped. I then tried CS4 and it installed without trouble. For CS5, I have a downloaded copy of the software; for CS4, I have an actual physical DVD. I may explore this issue further at some later point. For now, having CS4 run is quite sufficient for testing and evaluation.
I realize that using thin clients will impose some amount of performance penalty, but my expectation is that the overall performance will be acceptable for most user tasks most of the time. I take it from your post this has been your experience. I will still provide a stand-alone machine for the small number of projects where the application is taxing the limits of the computer, and any limitations imposed by Remote Desktop are not acceptable.
Certainly, the software needs to be properly licensed, which Adobe is more than happy to provide. Through the thin client approach I hope to eliminate the maintenance and management headache of maintaining multiple, essentially identical, machines. And, I hope to reduce (by some small percentage) power costs.
We'll see how it goes...
Jerry

Customizing single user connection via Windows remote desktop

Similar Messages

Maybe you are looking for