Windows Remote Desktop Connection (mstsc) saves the remote computer name like this:

full address:s:rdsh1.whatever.microsoft.com

But if mstsc is launched via Remote Desktop Web Access, the used rdp files have the following content:

full address:s:rdsh1.whatever.microsoft.com
alternate full address:s:rdsh1.whatever.microsoft.com

If an rdp file contains "alternate full address" then "full address" seems to be ignored completely, even if "alternate full address" cannot be resolved.

What is "alternate full address", what is the difference to "full address" and where is the documentation for these settings?

Thanks for any hints!

Note:
https://docs.microsoft.com/en-us/windows/desktop/api/rdpappcontainerclient/nf-rdpappcontainerclient-iremotedesktopclientsettings-setrdpproperty is not helping since that documentation merely converts the setting name into a sentence ;)

Hello,

I am unable to take remote access from win 10 enterprise professional 64 bit to win 10 machines having the same enterprise professional 64 bit.

Both machines have Version 1809.

Error message: internal error, when trying for remote access through MSTSC

Ping between machines success, no packet loss.

Tried to disable UDP on <g class="gr_ gr_444 gr-alert gr_spell gr_inline_cards gr_disable_anim_appear ContextualSpelling" data-gr-id="444" id="444">regedit</g> and then GPUPDATE /force, still no success.

Microsoft has any KB update for above issue or patch released for above bug issue.

Printing to redirected printers is not working anymore. (It's OK with W2008 R2).

RDP client being W7 (or Wyse ThinOS)

I tried with two different printers : Dymo Labelwriter 450 and Ricoh Aficio SP 4310N PS (and PCl5e).

- The driver is well present on the host side (the redirection occurs well).

- Easy Print disabled (GPO)

When trying to print, the popup message is "Error printing to ....", Then subsequent tries result in popups "Printer is in error state"

The Printservice log says at the end on the error entry   "...Win32 error code returned by the print processor: 50. The request is not supported."

When the RDP client is another W2016 RDSH, then printing to a redirected printer (network printer in that case)  works well.

Hi,

I have RDP licencing setup per user but most of the account logging on are working fine, but are not being assigned a licence. Licence diagnoser says its fine...

Is it because I am still within the trial period?... Although I have installed the licences…?

Satya

We have a Dell TS130 running Windows Server 2016 system which is supposed to server as a Remote Desktop Services server.  It lets two people connect via RDP and then says we have limited connections and all of the connections are in use, try again later.  Considering we have ten licenses something is clearly wrong.  The Remote Desktop Licensing Diagnoser says no problems detected.   4 licenses issued 6 left available. It sees the licenses and it issuing the licenses but only allows two connections at a time.  I spent all day yesterday  on the phone with Dell.  They can't find a problem and sent me to a Microsoft phone number which leads me to this situation.

Microsoft told me on the phone that the service ticket must be initiated online but the URL they directed me to will not allow me to submit a ticket because we don't have a support contract and it will not let me submit a per incident ticket because it says we are an "Azure Client"??  The only Azure connection is a couple of laptops that predate the server.  I'm very frustrated and I wonder if Microsoft can come up with any other ways to piss me off.

If anyone has any helpful suggestions I would appreciate them.

Is there or will Microsoft announce some kind of the API for the Microsoft Azure RemoteApp? 

Thanks.

Error: 

Configuration:

We have few servers on WORKGROUP however i have made single server as RDS License server and on rest all servers did below configuration

<style type="text/css"><!--td {border: 1px solid #ccc;}br {mso-data-placement:same-cell;}--></style>Local group policy on each server
Local Computer Policy -> Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Licensing

"Use the specified RD license servers" = myservername

"Set the Remote Desktop licensing mode" = Per User

Solution that i always apply to fix this by removing the REG Key and reboot the server

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\GracePeriod

We have all the licenses and configuration in place still why we get the error after every 180 days..... What needs to do to avoid this 

Dayanand Gavas

I'm having an issue on a single RDS 2016 server at the moment where the start menu doesn't open.  

I've gone though lots of steps including sfc /scannow  (No errors)   DISM with all the options (No Errors)

I've cleared the Registry in firewall policy\restricted services\configurable\system.

I believe the issue is that I don't have any applications registered in the get-appxpackage at all, it just comes back blanks where as on working machines I get a list of about 15.

I've tried to install the packages by hand using variations of 

Add-AppxPackage -DisableDevelopmentMode -Register C:\Windows\SystemApps\Microsoft.Windows.Cortana_cw5n1h2txyewy\AppxManifest.xml -Verbose 

This returns the following;

Add-AppxPackage : Deployment failed with HRESULT: 0x80073CF6, Package could not be registered.
An internal error occurred with error 0x800705AA. See http://go.microsoft.com/fwlink/?LinkId=235160 for help diagnosing app deployment issues.
NOTE: For additional information, look for [ActivityId] 5597e571-c93a-001c-e6eb-97553ac9d401 in the Event Log or use the command line Get-AppxLog -ActivityID
5597e571-c93a-001c-e6eb-97553ac9d401
At line:1 char:1
+ Add-AppxPackage -DisableDevelopmentMode -Register C:\Windows\SystemAp ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : WriteError: (C:\Windows\Syst...ppxManifest.xml:String) [Add-AppxPackage], IOException
    + FullyQualifiedErrorId : DeploymentError,Microsoft.Windows.Appx.PackageManager.Commands.AddAppxPackageCommand

If I then use Get-AppxLog -ActivityID5597e571-c93a-001c-e6eb-97553ac9d401

Time                      ID           Message
----                      --           -------
20/02/2019 17:22:29       301          The calling process is powershell.exe
20/02/2019 17:22:29       603          Started deployment Register operation on a package with main parameter: AppxManifest.xml and Options: 0. See
                                       http://go.microsoft.com/fwlink/?LinkId=235160 for help diagnosing app deployment issues.
20/02/2019 17:22:29       10002        Creating Resiliency File
                                       C:\ProgramData\Microsoft\Windows\AppRepository\75f29027-c919-4974-89c9-f53bb4413b5f_S-1-5-21-1787921346-3847137862-2124306101-500_1.rslc for
                                       Register Operation on Package Microsoft.Windows.Cortana_1.7.0.14393_neutral_neutral_cw5n1h2txyewy.
20/02/2019 17:22:29       607          Deployment Register operation on package Microsoft.Windows.Cortana_1.7.0.14393_neutral_neutral_cw5n1h2txyewy has been de-queued and is running
                                       for user FISRDS1\Administrator.
20/02/2019 17:22:29       613          Adding uri to the list of Uris: C:\Windows\SystemApps\Microsoft.Windows.Cortana_cw5n1h2txyewy\AppxManifest.xml.
20/02/2019 17:22:29       447          GetFullyQualifiedReference from the String Resource Map for package full name:
                                       Microsoft.Windows.Cortana_1.7.0.14393_neutral_neutral_cw5n1h2txyewy and reference string: Microsoft Corporation failed.
20/02/2019 17:22:29       339          Registration will process the extensions in the following order: windows.visualElements windows.autoPlayContent windows.autoPlayDevice
                                       windows.activatableClass.inProcessServer windows.activatableClass.outOfProcessServer windows.activatableClass.proxyStub
                                       windows.activatableClass.downloadUpload windows.search windows.fileOpenPicker windows.fileSavePicker windows.cachedFileUpdater
                                       windows.appUriHandler windows.shareTarget windows.lockScreenCall windows.personalAssistantLaunch windows.fileTypeAssociation windows.protocol
                                       windows.appointmentsProvider windows.activatableClass.backgroundPlaybackClass windows.backgroundTasks windows.DefaultBackgroundTasks
                                       windows.webAccountProvider windows.userDataAccountsProvider windows.preInstalledConfigTask windows.updateTask windows.appService
                                       windows.appointmentDataProvider windows.contactDataProvider windows.emailDataProvider windows.internal.filePickerExperience
                                       windows.dialProtocol windows.restrictedLaunch windows.accountPictureProvider windows.cameraSettings windows.printTaskSettings
                                       windows.print3DWorkflow windows.activatableClass.collector .
20/02/2019 17:22:29       10000        About to service package Microsoft.Windows.Cortana_1.7.0.14393_neutral_neutral_cw5n1h2txyewy. Setting the package state to disabled returned
                                       with 0x80070490.
20/02/2019 17:22:29       339          Registration will process the extensions in the following order: windows.stateExtension windows.applyDataExtension windows.repositoryExtension
                                       windows.capability windows.MRT windows.visualElements windows.alarm windows.autoPlayContent windows.autoPlayDevice
                                       windows.activatableClass.inProcessServer windows.activatableClass.outOfProcessServer windows.activatableClass.proxyStub
                                       windows.activatableClass.downloadUpload windows.gameExplorer windows.search windows.fileOpenPicker windows.fileSavePicker
                                       windows.cachedFileUpdater windows.appUriHandler windows.shareTarget windows.lockScreenCall windows.personalAssistantLaunch
                                       windows.fileTypeAssociation windows.contentType windows.protocol windows.appointmentsProvider windows.defaultPrograms
                                       windows.activatableClass.backgroundPlaybackClass windows.backgroundTasks windows.DefaultBackgroundTasks windows.webAccountProvider
                                       windows.userDataAccountsProvider windows.preInstalledConfigTask windows.updateTask windows.appService windows.appointmentDataProvider
                                       windows.contactDataProvider windows.emailDataProvider windows.internal.filePickerExperience windows.dialProtocol windows.restrictedLaunch
                                       windows.integrityExtension windows.licensing windows.accountPictureProvider AppSync windows.cameraSettings windows.printTaskSettings
                                       windows.print3DWorkflow windows.DeviceSetupManager windows.activatableClass.collector windows.certificates windows.preCompilationExtension
                                       windows.ntServices windows.wmiProviders windows.iisModules windows.performanceProviders windows.eventProviders windows.runTime
                                       windows.DeviceAccess windows.indexedDB windows.MicrosoftAccountClient.SignOut windows.searchIndexer windows.geolocation windows.userDataAccess
                                       windows.repositoryExtension.remove windows.stateExtension.remove .
20/02/2019 17:22:29       827          Capability parsing started for the package Microsoft.Windows.Cortana_1.7.0.14393_neutral_neutral_cw5n1h2txyewy
20/02/2019 17:22:29       5252         An internal error occurred with error 0x800705AA. See http://go.microsoft.com/fwlink/?LinkId=235160 for help diagnosing app deployment issues.
20/02/2019 17:22:29       306          error 0x800705AA: While processing the request, the system failed to register the windows.stateExtension extension due to the following error:
                                       Insufficient system resources exist to complete the requested service.
                                       .
20/02/2019 17:22:29       316          error 0x800705AA: Cannot register the request because the following error was encountered during the registration of the windows.stateExtension
                                       extension: Insufficient system resources exist to complete the requested service.
                                       .
20/02/2019 17:22:29       5252         An internal error occurred with error 0x80070002. See http://go.microsoft.com/fwlink/?LinkId=235160 for help diagnosing app deployment issues.
20/02/2019 17:22:29       331          error 0x80070002: While reverting the request, the system failed to de-register the windows.stateExtension extension due to the following
                                       error: The system cannot find the file specified.
                                       .
20/02/2019 17:22:29       300          error 0x80073CF6: Cannot register the Microsoft.Windows.Cortana_cw5n1h2txyewy package due to the following error: Package could not be
                                       registered.
                                       .
20/02/2019 17:22:29       605          The last successful state reached was ResolvedDeferredRegistrations. Failure occurred before reaching the next state RegistrationChanged. hr:
                                       0x80073CF6
20/02/2019 17:22:29       339          Registration will process the extensions in the following order: windows.stateExtension windows.applyDataExtension windows.repositoryExtension
                                       windows.capability windows.MRT windows.visualElements windows.alarm windows.autoPlayContent windows.autoPlayDevice
                                       windows.activatableClass.inProcessServer windows.activatableClass.outOfProcessServer windows.activatableClass.proxyStub
                                       windows.activatableClass.downloadUpload windows.gameExplorer windows.search windows.fileOpenPicker windows.fileSavePicker
                                       windows.cachedFileUpdater windows.appUriHandler windows.shareTarget windows.lockScreenCall windows.personalAssistantLaunch
                                       windows.fileTypeAssociation windows.contentType windows.protocol windows.appointmentsProvider windows.defaultPrograms
                                       windows.activatableClass.backgroundPlaybackClass windows.backgroundTasks windows.DefaultBackgroundTasks windows.webAccountProvider
                                       windows.userDataAccountsProvider windows.preInstalledConfigTask windows.updateTask windows.appService windows.appointmentDataProvider
                                       windows.contactDataProvider windows.emailDataProvider windows.internal.filePickerExperience windows.dialProtocol windows.restrictedLaunch
                                       windows.integrityExtension windows.licensing windows.accountPictureProvider AppSync windows.cameraSettings windows.printTaskSettings
                                       windows.print3DWorkflow windows.DeviceSetupManager windows.activatableClass.collector windows.certificates windows.preCompilationExtension
                                       windows.ntServices windows.wmiProviders windows.iisModules windows.performanceProviders windows.eventProviders windows.runTime
                                       windows.DeviceAccess windows.indexedDB windows.MicrosoftAccountClient.SignOut windows.searchIndexer windows.geolocation windows.userDataAccess
                                       windows.repositoryExtension.remove windows.stateExtension.remove .
20/02/2019 17:22:29       339          Registration will process the extensions in the following order: windows.visualElements windows.autoPlayContent windows.autoPlayDevice
                                       windows.activatableClass.inProcessServer windows.activatableClass.outOfProcessServer windows.activatableClass.proxyStub
                                       windows.activatableClass.downloadUpload windows.search windows.fileOpenPicker windows.fileSavePicker windows.cachedFileUpdater
                                       windows.appUriHandler windows.shareTarget windows.lockScreenCall windows.personalAssistantLaunch windows.fileTypeAssociation windows.protocol
                                       windows.appointmentsProvider windows.activatableClass.backgroundPlaybackClass windows.backgroundTasks windows.DefaultBackgroundTasks
                                       windows.webAccountProvider windows.userDataAccountsProvider windows.preInstalledConfigTask windows.updateTask windows.appService
                                       windows.appointmentDataProvider windows.contactDataProvider windows.emailDataProvider windows.internal.filePickerExperience
                                       windows.dialProtocol windows.restrictedLaunch windows.accountPictureProvider windows.cameraSettings windows.printTaskSettings
                                       windows.print3DWorkflow windows.activatableClass.collector .
20/02/2019 17:22:29       10001        Finished servicing package Microsoft.Windows.Cortana_1.7.0.14393_neutral_neutral_cw5n1h2txyewy. Setting the package state to enabled returned
                                       with 0x0.
20/02/2019 17:22:29       401          Deployment Register operation with target volume C: on Package Microsoft.Windows.Cortana_1.7.0.14393_neutral_neutral_cw5n1h2txyewy from:
                                       (AppxManifest.xml)  failed with error 0x80073CF6. See http://go.microsoft.com/fwlink/?LinkId=235160 for help diagnosing app deployment issues.
20/02/2019 17:22:29       404          AppX Deployment operation failed for package Microsoft.Windows.Cortana_1.7.0.14393_neutral_neutral_cw5n1h2txyewy with error 0x80073CF6. The
                                       specific error text for this failure is: An internal error occurred with error 0x800705AA. See http://go.microsoft.com/fwlink/?LinkId=235160
                                       for help diagnosing app deployment issues.

I can't seem to get the system to re-register those applications!

Open to any suggestions?  (Please no, have you restarted the server!)

This happens on all users including local admin and new accounts.  Happens in Safe and Clean Boot.

Thanks.

Dear All,

we have a ADC  server on windows 2012 r2 but its working very slow when i view like task manager,disk management some time get hang and some time working good. kindly suggest how to resolved this issue.

Thanks & Regards

Naved Anjum 

We have Symantec End Point Installed in Servers. We found Event 4625 Which has NULL Event Logs Information found in the Logs 4625.

Can can anyone explains, How do we do the Investigation cause receiving many logs for same with Justification. 

We are in Mid of the Conclusion, and Why is this Event Generated by Whom and How?

Hi all,

Can we do RDP to a Windows Svr 2012R2 Datacenter with TLS services disabled/uninstalled  ??  I have a stand alone VM with no domain.

Is there any possibility to connect to the remote server by setting up a VPN even after disabling TLS services ?

Quick responses appreciated !

Best Regards,

SrujanC.

Hi everyone,

We have customer that has a strange issue. Only few users have this issue and not everyone. Scenario is like this, customer have roaming profiles with folder redirection. They have application that is installed on all rds servers. That application calls another program and to make this work they had to change registry entry for every users under HKCU\software\software name

Now issue here is that when some users log in path to the program changes from S (which is manually configured in registry and it is giving path to the files of program) to C: where the program is installed. My question is, is this windows error of is this the application error. I think that windows registry should not change this automatically or am I wrong? I am not sure what to do because application vendor told us that this is windows issue not application?

I have been having difficulties getting the computer permissions to work by group in the RA Network Resource policy for remote desktop farms in HA mode.  Published app's fail to connect because I cannot find a way to add the HA gateway name to an AD group.  The AD group needs a computer account with the alias name of the connection broker.

I am always forced to use a RD Gateway-managed group or allow users to connect to any network resource in the RA policy.  Either of these are not desirable, we'd like to use a single AD group for this across multiple RDS servers in our farm.

Does anyone know a simple way to add an AD alias "computer" account for the HA Gateway name so I add it to an AD group and use that group in the RA Gateway policy to allow users to connect to published apps on the RDS servers themselves?

I setup a RD Gateway on both Windows server 2016 and Windows server 2019. That should be a strainght forward process following Microsoft doc and multiple other website (https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-deploy-infrastructure).

When I try to connect I received that error message Event Log Windows->TermainServices-Gateway

The user "DOMAIN\Username", on client computer "IP", did not meet connection authorization policy requirements and was therefore not authorized to access the RD Gateway server. The authentication method used was: "NTLM" and connection protocol used: "HTTP". The following error occurred: "23003".

I found many documentation that claim that registering the NPS server (https://docs.microsoft.com/en-us/windows-server/networking/technologies/nps/nps-manage-register) should fix that issue, I register the server. Both are now in the "RAS and IAS Servers" Domain Security Group. But We still received the same error. Can in the past we broke that group effect?

I continue investigating and found the Failed Audit log in the security event log:

I have then found that thread which claim that I should disabled NPS authentifaction

https://social.technet.microsoft.com/Forums/windowsserver/en-US/f49fe666-ac4b-4bf9-a332-928a547cff77/remote-desktop-gateway-denying-connections

I try it but disabling the NPS authentification leave me a bad impression...

Did anyone have a clue why I cannot resolve the domain.

For the testing/debuging purpose and I install The RD Gateway on a AD member server in main network, no other firewall than the windows one.

The only thing I can suspect is that we broke the "RAS and IAS Servers" AD Group in the past.

Everything was working fine until about 2 months ago.

I have a Windows 7 system that I access with Remote Desktop Connection from a Windows 10 system.  One day I found that my user account, which had been given administrator rights quite some time ago, couldn’t log on remotely.  The Windows 7 system was configured for remote access with the setting “Allow connections only from computers running Remote Desktop with Network Level Authentication (more secure)”. When I tried to log on, I got an error stating “The Local Security Authority cannot be contacted”. 

If I configured Windows 7 to “Allow connections from computers running any version of Remote Desktop (less secure)”, then I could log in but I didn’t want to use this less secure setting.

Doing some experimentation, I found that if I enabled the built-in Administrator account, then the Administrator could log in remotely using “Allow connections only from computers running Remote Desktop with Network Level Authentication (more secure)”.

If I created a new standard user called Test.  I found that Test could also could log in remotely using “Allow connections only from computers running Remote Desktop with Network Level Authentication (more secure)”.

If I promoted Test to an administrator, then Test couldn’t remotely log on.  He got the LSA error.  If I demoted my account to a standard user then I could log in remotely using “Allow connections only from computers running Remote Desktop with Network Level Authentication (more secure)”.

When I promoted my account back to an administrator, the logon failed with the LSA error.

All users have valid passwords that are set to never expire and are members of the Remote Desktop Users group.  The only thing that is changing is whether or not the users have administrative privileges.

Is this a permissions issue, or a behavior change cause by an update to Windows 7?

Mark Wilson

Hello!

I need help with the following scenario ... I currently have a Terminal Services server that contains an application, which must be used through a network drive, users access remote desktop media to the server and use the shortcuts of the applications that point to the shared unit, for example, the X :

Now it is required to do the same but through RemoteApps, but when trying to add the path of the applications, from the network unit, I do not or can not, from C: if it does it without problems, but I need to add it to point to the network unit ... how could I do this?

Thank you

I have a 2008 R2 Std Term Server.  Has been having 3 to 5 BSOD per day over the last few days.  

Have tried:

- Remove and reinstall production apps

- Run scans with WebRoot and MBAM (no issues found)

- SFC

- CHKDSK

- Driver Check and Update (Driver Reviver)

- Windows Updates

- Removed all un-needed virtual hardware (CD/DVD, Floppy, etc)

Server is a VMware virtual machine version 8.  Host is a Dell FC430 running ESXi 5.5 (build 2068190).  A second VM (Server 2008 R2 File Server) is running on the host as well, not having any issues.

DMP and MSinfo files available as soon as my account is verified by MS and I can post links for download

Thank you in advance.