![]() + 2378 std::_1::_assoc_state::move() (in Microsoft Remote Desktop Beta) + 56 + 2378 RdCore::Clipboard::A3::RdpFormatDataByteBufferCompletion::GetStatus() (in Microsoft Remote Desktop Beta) + 80 + 2378 RdCore::Clipboard::A3::RdpPlatformClipboard::GetSharedClipboardData(std::_1::weak_ptr) (in Microsoft Remote Desktop Beta) + 860 + 2378 RdCore::Clipboard::A3::A3ClientClipboardController::GetRemoteClipboardData(std::_1::weak_ptr) (in Microsoft Remote Desktop Beta) + 116 + 2378 - (in Microsoft Remote Desktop Beta) + 216 + 2378 thunk for () -> () (in Microsoft Remote Desktop Beta) + 20 ![]() + 2378 _dispatch_call_block_and_release (in libdispatch.dylib) + 32 + 2378 _dispatch_client_callout (in libdispatch.dylib) + 20 + 2378 _dispatch_lane_serial_drain (in libdispatch.dylib) + 668 + 2378 _dispatch_lane_invoke (in libdispatch.dylib) + 392 + 2378 _dispatch_workloop_worker_thread (in libdispatch.dylib) + 648 + 2378 _pthread_wqthread (in libsystem_pthread.dylib) + 288 + 2378 start_wqthread (in libsystem_pthread.dylib) + 8 + 2378 semaphore_wait_trap (in libsystem_kernel.dylib) + 8 Ģ378 Thread_4679931 DispatchQueue_209: (serial) ![]() + 2378 _dispatch_sema4_wait (in libdispatch.dylib) + 28 + 2378 _dispatch_semaphore_wait_slow (in libdispatch.dylib) + 132 + 2378 OS_dispatch_semaphore.wait(wallTimeout:) (in libswiftDispatch.dylib) + 24 + 2378 Promise.block(timeout:) (in Microsoft Remote Desktop Beta) + 736 + 2378 specialized SessionPasteboardItemTextDataProvider.pasteboard(_:item:provideDataForType:) (in Microsoft Remote Desktop Beta) + 392 + 2378 SessionPasteboardItemTextDataProvider.pasteboard(_:item:provideDataForType:) (in Microsoft Remote Desktop Beta) + 96 ![]() + 2378 _CFPasteboardHandleFulfillMessage_block_invoke_2 (in CoreFoundation) + 88 + 2378 _CFRUNLOOP_IS_CALLING_OUT_TO_A_BLOCK_ (in CoreFoundation) + 28 + 2378 _CFRunLoopDoBlocks (in CoreFoundation) + 412 + 2378 _CFRunLoopRun (in CoreFoundation) + 1720 + 2378 CFRunLoopRunSpecific (in CoreFoundation) + 600 + 2378 RunCurrentEventLoopInMode (in HIToolbox) + 292 + 2378 ReceiveNextEventCommon (in HIToolbox) + 564 + 2378 _BlockUntilNextEventMatchingListInModeWithFilter (in HIToolbox) + 72 + 2378 NSApplicationMain (in AppKit) + 1132 + 2378 main (in Microsoft Remote Desktop Beta) + 12 Relevant thread samples (regarding pasteboard): Call graph:Ģ378 Thread_4652551 DispatchQueue_1: -thread (serial) I'm not sure what else I can provide, but the TL DR is I upgraded the active Remote Desktop Connection Broker from 2012R2 to 2016, and after that, macs could not connect to any session host in the deployment, but PCs could connect fine.While using a clipboard manager (CopyQ or CopyLess) and copying from an Azure Virtual Desktop app into any other app it will cause both applications to hang and it's not possible to recover without force quitting Microsoft Remote Desktop. I then saved a snapshot of the connection broker in it's 'upgraded to 2016' state and reverted back to the 2012r2 snapshot, after which, everyone, including mac users, could connect. The other time it can come up is with macs, if you have the admin session box checked in the RDP app.Īfter a bit, it became apparent that only macs were having issues, which explained why I couldn't duplicate the issues even when connecting as users that were reporting issues. When everyone started coming in, there were a lot of issues though - Some getting the message 'The requested session access is denied', which is usually a damaged RDP file that's causing you to try to be connected to the session broker instead of a deployment server. ![]() I then tried to upgrade to 2016 instead of 2019, and while that also took forever, it succeeded, and once I had patched the 2016 connection broker to address the CredSSP issue, I was able to connect fine to several different collections. The other, currently inactive connection broker (you're supposed to remove all but one broker in a HA deployment and then do the in place upgrade) upgraded to 2019 without issue, although it took FOREVER. My Plan was to go from 2012R2 to 2019, then 2019 to 2022, however, one connection broker failed to upgrade to 2019, with the error after rollback indicating some sort of Sysprep issue. I had previously tested upgrading a Remote Desktop installation from 2012R2 all the way to 2022 in a test sandbox environment, which all went well, so I planned to upgrade our production deployment. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |