Terminal: 遠端桌面剪貼簿共用無法執行

-

 

公司環境啟用 Windows 2008 Terminal server, 並將剪貼簿功能開啟, 但 user 於遠端連線 terminal 後, 並無法將 local 複製的東西貼到遠端server內.

解決方式：

1. 請先進行下列確認，XP client端的服務確認下列已啟用，在進行測試

開始→執行→輸入「services.msc」開啟系統服務視窗後，依序啟動以下服務：

  • Network DDE DSDM
  • Network DDE
  • ClipBook

 

步驟:

遠端工作階段剪下及貼上

許多 [遠端桌面] 和 [終端機服務] 連線都會提供剪貼簿共用，讓您從遠端工作階段中使用的程式中剪下資訊，並貼到本機電腦 (您目前使用的電腦) 上執行的程式中，反之亦然。

會將從應用程式中剪下或複製的資訊移到 [剪貼簿] 上，並保存在那裡，直到清除 [剪貼簿] 或者剪下或複製另一個資訊為止。

由於本機和遠端電腦共用剪貼簿，您可以從 [遠端桌面連線] 視窗內的文件複製文字或圖形，並貼到本機電腦上的文件中。如需更多關於在遠端桌面工作階段中複製、貼上和使用本機檔案與資料夾的資訊，請參閱在遠端工作階段中存取本機檔案及資料夾。

注意事項

  • 根據網路原則及遠端電腦上執行的 Windows 版本，剪貼簿共用對一些遠端桌面連線可能沒有作用。

1. 確認GPO

image

 

2. 可能狀況

image

Blog Extended Reading

More Information & Reference

1. Cutting and pasting to and from remote sessions
2. Why does my shared clipboard not work? (Part 1)
3. Why does my shared clipboard not work? (Part 2)
4. Windows Server 2008 Terminal Services Web Access (Part 1)


Radiohead22_thumb53

Comments

Post a Comment

Popular posts from this blog

E15 CU3–Update Failed–AD replicated Exceeded the tombstone lifetime.

-
Image
  Exchange 2013 CU3 The naming context is in the process of being removed or is not replicated http://technet.microsoft.com/en-us/library/replication-error-8452-the-naming-context-is-in-the-process-of-being-removed-or-is-not-replicated-from-the-specified-server(v=ws.10).aspx   C:\> REPADMIN /SHOWREPS Root\RDC01 DSA Options: IS_GC Site Options: (none) DSA object GUID: f1694974-47c4-4555-a214-db3c86854aeb DSA invocationID: f1694974-47c4-4555-a214-db3c86854aeb ==== INBOUND NEIGHBORS ====================================== CN=Schema,CN=Configuration,DC=lab7,DC=root     TW\AD02 via RPC         DSA object GUID: bfcc1053-e1da-46fd-8b9d-179c79921331         Last attempt @ 2013-12-19 17:
Read more

202301 - Exchange onpreme - PowerShell Serialization Payload Signing

-
Image
Released: January 2023 Exchange Server Security Updates https://techcommunity.microsoft.com/t5/exchange-team-blog/released-january-2023-exchange-server-security-updates/ba-p/3711808 https://microsoft.github.io/CSS-Exchange/Diagnostics/HealthChecker/SerializedDataSigningCheck/ 1.  Update KB5022143 (Exchange SU) 2. Run latest HealthCherker 3.  PowerShell Serialization Payload Signing https://microsoft.github.io/CSS-Exchange/Diagnostics/HealthChecker/SerializedDataSigningCheck/ Certificate signing of PowerShell serialization payload in Exchange Server https://support.microsoft.com/en-us/topic/certificate-signing-of-powershell-serialization-payload-in-exchange-server-90fbf219-b0dd-4b2c-8a68-9d73b3309eb1 4.  MonitorExchangeAuthCertificate    https://microsoft.github.io/CSS-Exchange/Admin/MonitorExchangeAuthCertificate/ 5.                 New-SettingOverride -Name "EnableSigningVerification" -Component Data -Section EnableSerializationDataSigning -Parameters @("Enabled=true&qu
Read more

E14–Bulk Create Mail Contact & Set-Contact

-
Image
  http://community.office365.com/en-us/w/exchange/579.aspx     Get-Contact | Export-Csv c:\temp\contact.csv Get-MailContact | Export-Csv c:\temp\Mailcontact.csv   [PS] Import-Csv .\Contact_Source.csv | % {New-MailContact -Name $_.Name -DisplayName $_.DisplayName -ExternalEmailAddress $_.ExternalEmailAddress -Alias $_.Alias -PrimarySmtpAddress $_.PrimarySMTPAddress -OrganizationalUnit "Contacts" -WhatIf }   [PS] >$Contacts = Import-Csv .\Contact_final.csv [PS] >$Contacts | foreach {Set-Contact $_.Name -Company $_.Company -Department $_.Department -Office $_.Office -Phone $_.Phone }
Read more