When accessing a windows program thru remote desktop will it have functionality

When accessing a remote desktop on a mac to use a windows program is this functional and will it slow the mac down or create other vulnerabilities or will it run smoothly?

It will be as smooth as your connection is fast, and it won't affect the Mac adversely

Similar Messages

I am accessing a windows server using remote desktop and I am wondering if I can transfer files by sharing drives?

I am accessing a windows server using remote desktop and I am wondering if I can transfer files by sharing drives?

Probably. You may be able to use Finder > Go > Connect to server to access the server. You may be able to share folders using Remote Desktop too. Whichever one you like the best.

How to enable users to access windows 2012 through remote desktop client on windows XP SP3

Hi I have just installed Windows Server 2012 and trying to give access to the users. The users are on windows XP Pro SP3 remote desktop client (Shell and control version 6.1.7600 with Remote Desktop Protocol 7.0 support).
I have enabled the windows server 2012 remote desktop users through "control panel -> systems and security -> Remote access" for the users. When I try to connect to the windows server as administrator, it is getting connected.
But when I try to connect as other users I get the following message.
"To sign in remotely, you need the right to sign in through Remote Desktop Services. By default members of the Administrators group have this right. If the group you're in does not have the right, or if the right has been removed from the Administrators
group, you need to be granted the right manually."
Is there any other setting to be done to eanble the Remote Desktop for the users.

Hi I have just installed Windows Server 2012 and trying to give access to the users. The users are on windows XP Pro SP3 remote desktop client (Shell and control version 6.1.7600 with Remote Desktop Protocol 7.0 support).
I have enabled the windows server 2012 remote desktop users through "control panel -> systems and security -> Remote access" for the users. When I try to connect to the windows server as administrator, it is getting connected.
But when I try to connect as other users I get the following message.
"To sign in remotely, you need the right to sign in through Remote Desktop Services. By default members of the Administrators group have this right. If the group you're in does not have the right, or if the right has been removed from the Administrators
group, you need to be granted the right manually."
Is there any other setting to be done to eanble the Remote Desktop for the users.
Have you tried adding those users to the "Remote Desktop Users" group? It's in Active Directory Users and Computers and it's a Built-In group. Might want to give that a try ...
- JJ

I cannot access Content Library in iMovie - Content Library doesn't show on the iMovie screen and is greyed out when accessed through "windows" tab at the top. Also unable to update the projects/events (a suggested solution for a similar question).

I cannot access Content Library in iMovie - Content Library doesn't show on the iMovie screen and is greyed out when accessed through "windows" tab at the top. Also unable to update the projects/events (a suggested solution for a similar question). I haven't had this issue before, I have always used the content library on the screen but haven't used this for about a month. How can I make the Content Library available?

Thanks so much! I am backing up the entire computer now with an external hard drive - this should be fine right? And surely if I am backing up the whole computer these projects/videos will be backed up too? I wasn't sure how to do this any other way and I am clearly not great with tech issues. Once this is done and I am sure my projects/videos are safe I will do the delete and reinstall bit. Thanks for taking the time to help

Remote desktop failure. Have bought the app, but connection failed. Have bought the disable adds, but still getting them. What do I write:

Remote desktop failure. Have bought the app, but connection failed. Have bought the disable adds, but still getting them. What do I write:
in the username field, in the port field and in the password fiels and in the domain field and in the field where 3389 is. Have tried my computer username, my Computer password and the name of the network name (domain). Have also tried the network password.

Are you referring to Apple Remote Desktop, Apple's software for managing networked Macs? It sounds to me like you're referring to a remote connect app you purchased for use on your iPhone to connect to a Windows system, and if so you should start by contacting the support resources for the app you purchased, and if you can't get help there try asking in the iPhone forum.
Regards.

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!

Windows 2008 R2 + Remote Desktop Web Access + Single Sign-On + 2 servers

Hi
First sorry for my English. I have got problem with run SSO with RDWeb. I configured everything follow this instructions: http://blogs.msdn.com/b/rds/archive/2009/08/11/introducing-web-single-sign-on-for-remoteapp-and-desktop-connections.aspx
and http://blogs.technet.com/b/mrsnrub/archive/2010/03/22/remote-desktop-services-websso.aspx. After logon to RDWeb web page I click application icon. Then I see dialog box for credentials - SSO not working.
I have got 2 servers with Windows Server 2008 R2 Standard:
Server OL-AP1 with role Remote Desktop Session Host (RDSH) and certificate for digital sign RemoteApps
Server OL-AP04 with ONLY Remote Desktop Web Access (RD Web) with certificate for https
Client PC: Windows 7 SP1 with installing certificate for OL-AP01 witch I used for digital sign RemoteApps
All certificates created by enterprise domain CA - Active Directory Certificate Services (AD CS)

Hi,
Thank you for posting in Windows Server Forum.
Do you have RD Gateway setup in your environment?
Have you configure RD Connection Broker and set the Fully Qualified Domain Name (FQDN) of the RD Connection Broker server in case of RD Connection Broker mode. In RD Session mode, it is set to the FQDN of the RD Web Access server.
Client operating systems must trust the certificate with which the RemoteApp programs are signed. Suggest to install RDP 8.1 for client OS.
Do you have a trusted certificate with a matching name configured on your RDSH server in RD Session Host Configuration? (Means cert must match the name that clients use to connect to it for running the RemoteApp).
Hope it helps!
Thanks.
Dharmesh Solanki

Using windows program with remote access.

I have to work with a complex electronic medical records program (Allscripts) remotely from home on my Mac. The program is not really Mac friendly. It has to run on Java at home and it requires "right click, left click" operations on the pc that I can't figure out how to make work on the Mac. Any suggestions on how this may be able to work?

Any suggestions on how this may be able to work?'
Get a 2 button mouse

Windows 2008 R2 Remote Desktop Services - user profile path not working

Trying to setup remote desktop profiles. We have 1 farm with 2 Windows 2008R2 RD session hosts and a broker server and want the all of the remote user profiles to reside on a dedicated profile server. We've created the user shares but when a remote
user logs in their user profiles is automatically created on the session hosts. Each remote users profile path is specified in AD under the user's Remote Desktop Profile tab.
I've seen posts about creating a GPO to handle roaming profiles but I'm not sure as to where this needs to be created...should it be done on each of the session hosts? Are their any step by step instructions out there on how to achieve this that I just haven't
found yet?
bl

Hi,
Thank you for posting in Windows Server Forum.
Do you have RD Gateway setup in your environment?
Have you configure RD Connection Broker and set the Fully Qualified Domain Name (FQDN) of the RD Connection Broker server in case of RD Connection Broker mode. In RD Session mode, it is set to the FQDN of the RD Web Access server.
Client operating systems must trust the certificate with which the RemoteApp programs are signed. Suggest to install RDP 8.1 for client OS.
Do you have a trusted certificate with a matching name configured on your RDSH server in RD Session Host Configuration? (Means cert must match the name that clients use to connect to it for running the RemoteApp).
Hope it helps!
Thanks.
Dharmesh Solanki

Connecting _from_ a windows machine through remote desktop?

I have a os x server set up so that users can get to it through vpn by logging into a specific account ( lets call it remote_user ). The users are on windows machines, and they get remote desktop running, at which point the problems start. Instead of seeing the remote_user's desktop, they see whatever happens to be on the screen at the time, even the Administrator's account, if that happens to be logged in. Furthermore, these users have full control over even the Administrator's account and are able to do whatever the administrator might be able to do locally. Is this normal behavior or is there something I should be doing otherwise. Thanks in advance!

Further details:
the server is running on a mac mini, the internal interface is the built-in ethernet, the external interface is a usb-ethernet adapter connected directly to a cable modem. on the internal network there is a windows computer which has a program which needs to be run remotely. for this, a vpn connection to the server is established (using the vpn module in the server admin) and then the server is accessed though the virtual network that is created. the server runs wonderfully when left alone. however, when a vpn connection is made, the server lives for about 10 minutes and then freezes up. if no account is logged in on the server, the login window becomes unresponsive. if, for example, the administrator is logged in and is watching the server admin window, the server refreshes and remains that way, in a permanent refresh. if you have a preview window open reading a pdf, you are able to scroll though the pdf. you are, however unable to access any menus in the menu bar, nor start any new programs from the dock. the only way to get things up and running again is to hold down the power button. the last bit of bad news is that even after restart, the only way to get vpn up is to manually shut it down in the server administrator and to start it up again. i hope this can be resolved somehow. thanks in advance!

NULL SID Security Log Event ID 4625 when attempting logon to 2008 R2 Remote Desktop Session Host

This is a new deployment of Server 2008 R2 in a newly created 08 R2 active directory on a newlyt installed 08 R2 RDSH server.
A new generic user is created in AD. That user can log on to the terminal server on the console just fine. But that user cannot logon via RDP. Furthermore, the domain admin credentials also cannot logon via RDP.
When either set of credentials is used, the logon attempt registered in the Windows Security Even Log as a denied attempt with Event ID 4625 reporting a NULL SID.
Troubleshooting: The RDSH has already been disjoined and rejoined to the domain. Also, curious note, there are three ways to save the user account on the RDSH server as a valid user account which has permissions to logon. The one Microsoft recommends is to open computer management and edit the remote desktop users group. When I the accounts here and click apply, they immediately dissapear. Secondly, I can open the computer properties and go to the remote tab. There I find the user accounts added using the previous method are enumerated but not displaying correctly. They show up with the RDSH server name and a question mark. The last way, is to open the Remote Desktop Session Configuration tool and edit the properties of the rdp connection and go to the security tab. This was the only place I could get a user to ‘stick’ but the logon attempts still show a NULL SID and access is denied.
I have scoured every bit of RDS documenation I can find with no luck.
Thanks,
Chris

I am also experiencing this issue.
2008 servers, 2007 exchange on server 2008.
These are fresh servers, fresh AD. Users can log onto domain normally, RDP not working for admin accounts, generating same errors as posted above.
The bigger issue, is that we have a cisco messaging service account that is generating this error on the DC's and the Exchange server as well. The service basically emails users voicemails to their inbox. The user we've created for the cisco service is unable
to authenticate to the exchange server, in turn generating the same errors posted above as well. We can log on to the domain with this account just fine.
Any ideas on this? We have not tried re-adding the servers to the domain.
Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 5/5/2010 9:01:13 AM
Event ID: 4625
Task Category: Logon
Level: Information
Keywords: Audit Failure
User: N/A
Computer: xx.corp
Description:
An account failed to log on.
Subject:
Security ID: NULL SID
   Account Name: -
   Account Domain: -
   Logon ID: 0x0
Logon Type: 3
Account For Which Logon Failed:
   Security ID: NULL SID
   Account Name:
xxxx
   Account Domain:
xxxx
Failure Information:
   Failure Reason: Domain sid inconsistent.
   Status: 0xc000006d
   Sub Status: 0xc000019b
Process Information:
   Caller Process ID: 0x0
   Caller Process Name: -
Network Information:
   Workstation Name: laptop
   Source Network Address: -
   Source Port: -
Detailed Authentication Information:
   Logon Process: NtLmSsp
   Authentication Package: NTLM
   Transited Services: -
   Package Name (NTLM only): -
   Key Length: 0

Another Windows 8.1 Remote Desktop Connection Issue

I want to connect to my PC running Windows 8.1 from my tablet running 8.1. I have allowed RDC in the windows firewall. I open RDC on my tablet and enter my PC computer name, KENSPC, into the Computer field and get "Remote Desktop can't connect to the
remote computer for one of these reasons:
1) Remote access to the server is not enabled
2) The remote computer is turned off
3) The remote computer is not available on the network.
I get the same message when I use the IP address for the PC.
My PC is wired to my router and my tablet is wireless and both use my Microsoft account for credentials. I can ping the PC from the tablet, so I know the tablet can see the PC and I can open files on the PC from the tablet. I have "Allow
Remote Assistance connections to this computer" turned on. And I have, in fact, had HP help via remote assistance. But nothing I do seems to work. The steps as specified in the Helps do not work. Any help would be appreciated.
kenfrantz at outlook dot com

Hi,
According to your description,we need to know the detail edition of your remote PC.
You can use a PC running any edition of Windows XP, Windows Vista, and Windows 7, or a PC running Windows 8, Windows RT, Windows 8.1, or Windows RT 8.1 to initiate a connection.
But the remote PC must be running one of these Windows operating systems:
Windows 8.1 Pro ,Windows 8.1 Enterprise ,Windows 8 Enterprise ,Windows 8 Pro ,Windows 7 Professional ,Windows 7 Enterprise ,Windows 7 Ultimate ,Windows Vista Business ,Windows Vista Ultimate ,Windows Vista Enterprise ,Windows XP Professional.
Also, I would like to share the following article with you:
http://windows.microsoft.com/en-us/windows/remote-desktop-connection-faq#1TC=windows-8
http://www.microsoft.com/en-us/windows/enterprise/products-and-technologies/windows-8-1/compare/default.aspx
Hope this helps.
Regards,
Kelvin Xu
TechNet Community Support

Windows 2012 R2 - Remote Desktop Sessions, RemoteFX, GPU, Blue Screen RemoteFX adaptor

Nvidia GPU GRID K1
Host Server - Dell Power edge R720 128 gig RAM 2 Xeon E5-2640v2 2.0GHz, 20M cache 8c
Windows 2012 R2 full installation – Bios and all hardware with latest updates.
Roles - Hyper V and Remote Desktop Virtualization Host
EPT, GPU, WDDM (latest drivers) compatible for RemoteFX and fully up to date.
I have disabled the video adaptor on the motherboard.
I cannot complete with administrative permissions;
dism /online /enable-feature /featurename:Microsoft-Windows-RemoteFX-EmbeddedVideoCap-Setup-Package
Error: 0x800f080c
Feature name Microsoft-Windows-RemoteFX-EmbeddedVidoCap-Setup-Package is unknown
Question 1 - because video card on motherboard disabled, do I still need to complete this command?
VM’s
**I’m not interested in VDI but more Remote Desktop Sessions and the option to ‘pinch and zoom with Windows 8.1 tablets**
VM1 - Windows 2012 R2 configured as generation 1 that is fully patched.
This VM is able to start up and run until I add the new hardware for the RemoteFX Video adaptor from within the Hyper V settings. When I start the VM the server blue screens. I have tried multiple VM’s with 2012 but same thing
If I created the VM as Generation 2 I am able to start the VM but the RemoteFX adaptor doesn’t appear in the device manager. I have read generation 2 isn’t compatible with RemoteFX.
VM2 – *Testing purposes* - Windows 8.1 Enterprise configured as generation 1 that is fully patched.
This VM I am able to start up and run the VDI after the RemoteFX video adaptor is installed, also the correct adaptor appears in the device manager. This seems to at least work correctly but I cannot pinch and zoom and the experience is poor.
GPU summary within the Hyper V settings state there are 4 physical GPU’s all of which can be used with RemoteFX and that 1 virtual machine are using the GPU (Windows 8.1 enterprise VM)
Firewalls off, latest RDP clients
I have read you should be able to use Windows 2012 R2 and we should be able to use the sessions with pinch and zoom but now and then you come across something that tells me different.
Question 2 – I need this to work with Windows 2012 R2 so we can use Remote Desktop Sessions
and the tablets can use pinch and zoom, anyone tell me what I may be doing wrong?

Hi,
Thank you for posting in Windows Server Forum.
As per my research, you need to run the command although video adapter is disabled on motherboard. If you install the RemoteFX cap driver, the integrated video adapter is disabled while the operating system is running.
For more information you can refer beneath article.
1. RemoteFX (with Hyper-V) is a serious business tool. For games.
2. Configure RemoteFX in Hyper-V running Windows Server 2012 with low end GPU
Hope it helps!
Thanks.
Dharmesh Solanki

After MS13-098 and SecurityAdvisory(2915720), Windows Server 2003 Remote Desktop(TermService) cannot start service

I have trouble with Windows Server 2003 R2 Standard. I installed the KB2893294(MS13-098) patch, and I changed the registry that is suggested actions of Security Advisory(2915720) http://technet.microsoft.com/en-us/security/advisory/2915720
Suggested Actions:
[HKEY_LOCAL_MACHINE\Software\Microsoft\Cryptography\Wintrust\Config]
"EnableCertPaddingCheck"="1"
After rebooting the event viewer(system) says:
Event Type: Error
Event Source: TermService
Event Category: None
Event ID: 1014
User: N/A
Description:
Cannot load illegal module: C:\Windows\system32\rdpwsx.DLL
After I cannot use Remote Desktop Connection from other client.
So I check the all security patches and other hotfixies. I checked the KB2653956 and KB958476.
But TermService do not recover the error.
And then, I delete the "EnableCertPaddingCheck" registry and reboot systems.
TermService have no error. I can use Remote Desktop Connection from other client.
After KB2893294 installed, Remote Desktop Connection cannot use from other client that "EnableCertPaddingCheck" registry set to "1".
Other Windows Server 2008 systems do not effect the KB2893294 patch. But All Windows Server 2003 systems cannot use the Remote Desktop Connections after the KB2893294 patch.

Update on this issue:
The debug team has accepted the issue and has identified it as a regression. Right now they're targeting *June* as the release date for a fix. I'm attempting to educate them that customers don't just install patches the day (or even month) they're
released and that the fix needs to be moved up in priority to give a minimum of 60 days to install the patch before the time-bomb explodes.
In the meantime, a workaround has been provided that will turn off the new functionality. Note that I have not yet had a chance to test this. It entails creating a new DWORD registry entry--UseLegacyPE--and setting it to 1.
HKLM\Software\Microsoft\Windows NT\CurrentVersion\ImageHlp\UseLegacyPE
I will update this thread when I have further information.

Windows 2012 Server Remote Desktop Virtualization + Linux Clients

Hello!
I wonder if anyone could shed a little light on this.
We want to implement a Windows 2012 Server with Remote Desktop Virtualization for our office, which has around 12 users. Our company has its core apps developed in VB6.0, and those apps use MySQL as their database. We want clients to run Linux, which will
have no other function than to connect and to Windows 2012 Server and display the remote session. Users need to work as usual, as they would in a local version of a Windows Desktop.
Can this be done? If yes, is the Standard version of Windows 2012 Server the best to accomplish this?
Thank you!

Hi,
Add to Tim, you need to acquire CALs for every user (About 12 in your case).
Remote Desktop Services Client Access Licenses (RDS CALs)
http://technet.microsoft.com/en-us/library/cc753650.aspx
Client Access Licenses and Management Licenses
http://www.microsoft.com/licensing/about-licensing/client-access-license.aspx
In addition, although AD is recommended, you can run RDS in a workgroup.
Regarding how to setup RDS on a single server, you can refer to the following:
Deploying the RDS Quick Start deployment type in Windows Server 2012 (for Session Virtualization)
http://social.technet.microsoft.com/wiki/contents/articles/10421.deploying-the-rds-quick-start-deployment-type-in-windows-server-2012-for-session-virtualization.aspx
Deploying RDS 2012 Single Server – Session Based deployment
http://ryanmangansitblog.wordpress.com/2013/03/11/deploying-rds-2012-single-server-session-based-deployment/
Please Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
Hope this helps.
Jeremy Wu
TechNet Community Support

When accessing a windows program thru remote desktop will it have functionality

Similar Messages

Maybe you are looking for