Quantcast
Channel: Remote Desktop Services (Terminal Services) forum
Viewing all 5613 articles
Browse latest View live
↧

RemoteApp RDS2019 - splash screens stuck on client

February 7, 2019, 11:12 am
$
0
0

Hi!

I am testing RDS 2019 with RemoteApp, and I have problems with startup splash screens. Each splash screen creates a button on the client’s taskbar and does not disappear from desktop and taskbar after the appearance of the main window. For example, I run three RemoteApp and I have three splash screens and three program windows on my desktop. And even if I close these windows, the splash screens will still remain on desktop and cannot be closed. This happens only in RemoteApp and does not occur with a remote desktop mode. I tried to recreate an RDS farm again, but it does not help.

This does not happen with all programs (having splash screen), but with many. At the same time, there were no such problems at RDS 2012R2/2016. 

As RDCB and RDSH used Windows Server 2019 with latest cumulative update (2019-01). As clients used Windows 10 1709/1809 with same update.

↧
Search

application permissions not working at all in remote access configuration

April 2, 2020, 6:06 am
$
0
0

I trying to explain my setup, i have a fully functioning and working internal RDWEB with published apps, all permissions are working totally fine. (version 2012R2).

Apps only appear when permissions are given etc. call this Domain A

during this current situation with Covid-19 , we want to share the apps to another domain (call it Domain B), which is currently trusted (oneway) we trust the accounts from Domain B.

So we enabled RDWEB in the firewall, and now a few of us who are testing RDS works ok in Domain B, can see all applications that are published even ones i have taken myself off, if i check on our domain A i don't see the apps, but going to rdweb on domain B i see all the apps and can even access them !! its interesting when browsing to RDWEB from domain B it doesn't ask for credentials etc. 

in IIS on the rdweb server Windows authentication is enabled. i don't understand how it can be displaying all the applications and allowing me to access them (when i click excel for example it does ask for my login and opens excel fine but i have removed my self from the app permissions. i am a domain admin on domain A if this has anything to do with it.

any ideas or suggestions would be gratefully received.

many thanks

Mark

↧
↧

No remote desktop license servers are available to provide license

April 6, 2020, 10:37 pm
$
0
0

I am getting this error on many servers and solution to this is to delete the grace period.

But I have my license activated and license diagnoser does not show anr error. I made changes in group policy and specify the license server name. 

In RD Licensing Manager it is showing Total and Available license but is still showing 0 License has been issued.

Please help me in this.

↧

RDSSH behind RDSGW URL

April 8, 2020, 4:33 am
$
0
0

Hello folks

We have a Setup with two RDS Servers (Windows Server 2019). 1 Server is a Session Host with the Connection Broker, 1 server is the RDS Gateway. If we use mstsc to connect, we have to provide the URL/IP of the gateway (mstsc -> Show Options -> Advanced -> Settings -> Use these RD Gateway server settings...). This is a no-go because it's just to complicated for an enduser to provide this data/information. 

Question: 

can the RDS services be configured so that only the IP/URL of the gateway server must be specified? or is there any other best-practive aproach? it should be easy for an enduser to connect from the internet (without a vpn connection).

thanks

Christian


Christian

↧

Policy Module for company Microsoft Corporation product C50 has denied new license request

April 14, 2020, 12:13 am
$
0
0

Hello.

We get this alert from SCOM, I've been trying to find out what product C50 is but I can't find it anywhere.

"Event ID: 42 -- Description: An error occurred in policy module "Policy Module for company Microsoft Corporation product C50 has denied new license request with error code 1104.".

Any ideas?

↧
↧

Server 2019 BSOD - Terminal Server

April 10, 2020, 2:38 am
$
0
0
Hi, we have a terminal server based on Server 2019 that consists of 10 RD Hosts.We have 300 users. Some users use remoteapp.

We got a blue screen in some of the hosts. There are no extra drivers etc. on the hosts other than printer drivers. Printer drivers have been previously tested on different servers. Memory Dump is listed below. How can we interpret this output?

*                                                                            *
*                        Bugcheck Analysis                                    *
*                                                                            *
*******************************************************************************

CRITICAL_PROCESS_DIED (ef)
        A critical system process died
Arguments:
Arg1: ffff888d8dc2e080, Process object or thread object
Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died.
Arg3: 0000000000000000
Arg4: 0000000000000000

Debugging Details:
------------------

Page 2001e206a too large to be in the dump file.
Page 2001d3369 too large to be in the dump file.

KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING:  17763.1.amd64fre.rs5_release.180914-1434

SYSTEM_MANUFACTURER:  Microsoft Corporation

VIRTUAL_MACHINE:  HyperV

SYSTEM_PRODUCT_NAME:  Virtual Machine

SYSTEM_SKU:  None

SYSTEM_VERSION:  Hyper-V UEFI Release v1.0

BIOS_VENDOR:  Microsoft Corporation

BIOS_VERSION:  Hyper-V UEFI Release v1.0

BIOS_DATE:  11/26/2012

BASEBOARD_MANUFACTURER:  Microsoft Corporation

BASEBOARD_PRODUCT:  Virtual Machine

BASEBOARD_VERSION:  Hyper-V UEFI Release v1.0

DUMP_TYPE:  1

BUGCHECK_P1: ffff888d8dc2e080

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

PROCESS_NAME:  csrss.exe

CRITICAL_PROCESS:  csrss.exe

EXCEPTION_CODE: (HRESULT) 0x8da82080 (2376605824) - <Unable to get error code text>

ERROR_CODE: (NTSTATUS) 0x8da82080 - <Unable to get error code text>

CPU_COUNT: 8

CPU_MHZ: 95a

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 55

CPU_STEPPING: 4

CPU_MICROCODE: 6,55,4,0 (F,M,S,R)  SIG: FFFFFFFF'00000000 (cache) FFFFFFFF'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0xEF

CURRENT_IRQL:  0

ANALYSIS_SESSION_TIME:  04-10-2020 12:32:30.0140

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

EXCEPTION_RECORD:  000000d8d1b3df30 -- (.exr 0xd8d1b3df30)
ExceptionAddress: 00000226f7fab5c0
   ExceptionCode: 00000000
  ExceptionFlags: 00000000
NumberParameters: -776798208
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000022600000000
   Parameter[2]: 0000000000000000
   Parameter[3]: 0000000000000000
   Parameter[4]: 0000022600010000
   Parameter[5]: 00000226fc6f0000
   Parameter[6]: 00000226f7fa0100
   Parameter[7]: 00000226fc06fb18
   Parameter[8]: 000000d8d1b3e040
   Parameter[9]: 000000d8d1b3de10
   Parameter[10]: 00000226f7fab5c0
   Parameter[11]: 0000004400000000
   Parameter[12]: 00000226f7fab5c0
   Parameter[13]: 0000000000000000
   Parameter[14]: 0000000000000000

CONTEXT:  00007ffc74278ca5 -- (.cxr 0x7ffc74278ca5)
rax=441f0f000b720615 rbx=e0814150247c8948 rcx=0fed8548f08b0000
rdx=c38b44000000c284 rsi=cb8b00000090840f rdi=e18108e9c1c3b70f
rip=0b5c6a15ff482024 rsp=ffffffbf007f0000 rbp=00660000f88141ff
 r8=f981c80b00ff0000  r9=8b48217200010000 r10=d1b70f000b5cae05
r11=8b108b4852048d4c r12=4cb60f4610e8c1c1 r13=0f0375c83b440dc2
r14=0b5c82058b48c9b7 r15=548d486a73083b00
iopl=1         ov dn di pl zr na pe cy
cs=4930  ss=5e41  ds=7b8b  es=4938  fs=e38b  gs=5f41             efl=ccc35c41
4930:2024 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from 0000000000000000 to 0b5c6a15ff482024

BAD_STACK_POINTER:  ffffffbf007f0000

STACK_TEXT:  
fffff184`02187c78 fffff802`1ec9fc8d : 00000000`000000ef ffff888d`8dc2e080 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff184`02187c80 fffff802`1ebdcf07 : 00000000`00000000 ffff888d`8dc2e080 00000000`00000000 fffff802`1e5426e4 : nt!PspCatchCriticalBreak+0xfd
fffff184`02187d20 fffff802`1ea9780c : ffff888d`00000000 00000000`00000000 ffff888d`8dc2e080 ffff888d`8dc2e358 : nt!PspTerminateAllThreads+0x146873
fffff184`02187d90 fffff802`1ea99349 : ffffffff`ffffffff fffff184`02187ec0 ffff888d`8dc2e080 000000d8`d1b3d901 : nt!PspTerminateProcess+0xe0
fffff184`02187dd0 fffff802`1e5d8305 : ffff888d`000020ec ffff888d`8da82080 ffff888d`8dc2e080 000000d8`d1b3d940 : nt!NtTerminateProcess+0xa9
fffff184`02187e40 00007ffc`77f5fce4 : 00007ffc`73e983a1 00000226`ffffffff 00000000`00000001 ffffffff`ee1e5d00 : nt!KiSystemServiceCopyEnd+0x25
000000d8`d1b3cfc8 00007ffc`73e983a1 : 00000226`ffffffff 00000000`00000001 ffffffff`ee1e5d00 00000000`0000046c : ntdll!NtTerminateProcess+0x14
000000d8`d1b3cfd0 00007ffc`77f91a68 : 00000226`f7f26640 00007ffc`73e98270 00000226`f7f26658 00007ffc`73cce9dd : CSRSRV!CsrUnhandledExceptionFilter+0x131
000000d8`d1b3d060 00007ffc`77f63400 : 00007ffc`77d17a08 00000000`00000000 00000000`00000000 00007ffc`77ec6a6f : ntdll!LdrpLogFatalUserCallbackException+0x98
000000d8`d1b3d1a0 00007ffc`77f6477f : 00007ffc`7802a000 00007ffc`77ec0000 0000ddc4`001ed000 000000d8`d1b3d750 : ntdll!KiUserCallbackDispatcherHandler+0x20
000000d8`d1b3d1e0 00007ffc`77ec4bef : 000000d8`d1b3d750 00000000`00000000 00007ffc`77d9d0e8 00007ffc`77cf0000 : ntdll!RtlpExecuteHandlerForException+0xf
000000d8`d1b3d210 00007ffc`77f634ee : 000000d8`d1b3df30 00007ffc`74278ca5 00000000`00000000 00007ffc`74263e72 : ntdll!RtlDispatchException+0x40f
000000d8`d1b3d940 00007ffc`77cf7cf6 : ffffffff`00000201 00000226`f7ef1580 0000000c`0000002d 00007ffc`77f06a03 : ntdll!KiUserExceptionDispatch+0x2e
000000d8`d1b3e730 00007ffc`77cf7c76 : 00000000`002e0000 00000000`0000002d 00000000`0000002d 00000001`0000002e : USER32!DefDlgProcWorker+0x66
000000d8`d1b3e7f0 00007ffc`77cfca66 : 00000000`00000000 00000000`00000000 00000000`0000000c 00007ffc`77ed01fe : USER32!DefDlgProcW+0x36
000000d8`d1b3e830 00007ffc`77cfc78c : 00000000`00000008 00007ffc`77f5f4f0 00000000`001301d6 00000000`80000000 : USER32!UserCallWinProcCheckWow+0x266
000000d8`d1b3e9b0 00007ffc`77d17a08 : 000000d8`d1b3eac8 00000000`00000000 00000000`00000000 00000000`00000000 : USER32!DispatchClientMessage+0x9c
000000d8`d1b3ea10 00007ffc`77f63494 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : USER32!_fnNCDESTROY+0x38
000000d8`d1b3ea70 00007ffc`74c41f24 : 00007ffc`77d015df 00000000`00008002 00000000`00000000 00000000`00000000 : ntdll!KiUserCallbackDispatcherContinue
000000d8`d1b3eaf8 00007ffc`77d015df : 00000000`00008002 00000000`00000000 00000000`00000000 000000d8`d1b3ebc8 : win32u!NtUserCreateWindowEx+0x14
000000d8`d1b3eb00 00007ffc`77cff642 : 00000000`000002fc 000000d8`00000001 00000000`00010101 00000000`00010101 : USER32!VerNtUserCreateWindowEx+0x20f
000000d8`d1b3ee90 00007ffc`77d1f19a : 0000439d`851d0a0e ffffffff`0000004b 00000000`00000000 00000000`00000002 : USER32!InternalCreateDialog+0x612
000000d8`d1b3f070 00007ffc`77d63836 : 00000000`00000000 000000d8`d1b3f1d0 000000d8`d1b3f3f0 00000226`f7fb07a0 : USER32!InternalDialogBox+0x106
000000d8`d1b3f0d0 00007ffc`77d62275 : 00000000`00000000 00000000`00000095 00000000`000002f8 00000000`00000032 : USER32!SoftModalMessageBox+0x7e6
000000d8`d1b3f220 00007ffc`77d62fb2 : 00000000`00000000 00000000`00000010 00000000`0000000e 00000000`00000800 : USER32!MessageBoxWorker+0x319
000000d8`d1b3f3d0 00007ffc`73e39726 : 00000000`00000001 00007ffc`73e4a9e0 00007113`625f8fb2 00000000`00000002 : USER32!MessageBoxTimeoutW+0x192
000000d8`d1b3f4d0 00007ffc`73e39bfd : 00000000`00000000 00007ffc`73e4a9e0 00000000`00000000 00000000`00000000 : winsrvext!HardErrorHandler+0x32a
000000d8`d1b3f690 00007ffc`73e3a0ee : 00000226`f7f98f00 00000000`00000001 00000000`00000000 000000d8`d1b3f900 : winsrvext!ProcessHardErrorRequest+0xe9
000000d8`d1b3f700 00007ffc`73e9872d : 00000226`f7ef7db0 00007ffc`77f33a2e 00000000`00000000 000000d8`d1cc0000 : winsrvext!UserHardErrorEx+0x4be
000000d8`d1b3f7c0 00007ffc`73e97ec5 : 00000226`f7ef79f0 00000000`00000000 00000000`00000000 000000d8`d1cc0000 : CSRSRV!QueueHardError+0x1a5
000000d8`d1b3f800 00007ffc`77f2a27f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : CSRSRV!CsrApiRequestThread+0x2525
000000d8`d1b3fc90 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x2f


THREAD_SHA1_HASH_MOD_FUNC:  243502d633fd810f3a77e6153eeed955d23a59af

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  2d5957ffba98cb17c4474657af1391290476cdba

THREAD_SHA1_HASH_MOD:  5255f96f63ab75cf0bb2e1adc18592ee682a40d7

FOLLOWUP_IP: 
ntdll!NtTerminateProcess+14
00007ffc`77f5fce4 c3              ret

FAULT_INSTR_CODE:  c32ecdc3

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  ntdll!NtTerminateProcess+14

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ntdll

IMAGE_NAME:  ntdll.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  125ac1e8

IMAGE_VERSION:  10.0.17763.802

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  14

FAILURE_BUCKET_ID:  0xEF_csrss.exe_BUGCHECK_CRITICAL_PROCESS_8da82080_STACKPTR_ERROR_ntdll!NtTerminateProcess

BUCKET_ID:  0xEF_csrss.exe_BUGCHECK_CRITICAL_PROCESS_8da82080_STACKPTR_ERROR_ntdll!NtTerminateProcess

PRIMARY_PROBLEM_CLASS:  0xEF_csrss.exe_BUGCHECK_CRITICAL_PROCESS_8da82080_STACKPTR_ERROR_ntdll!NtTerminateProcess

TARGET_TIME:  2020-04-07T05:14:52.000Z

OSBUILD:  17763

OSSERVICEPACK:  0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  131216

PRODUCT_TYPE:  3

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 Server TerminalServer DataCenter

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  1996-08-06 18:11:50

BUILDDATESTAMP_STR:  180914-1434

BUILDLAB_STR:  rs5_release

BUILDOSVER_STR:  10.0.17763.1.amd64fre.rs5_release.180914-1434

ANALYSIS_SESSION_ELAPSED_TIME:  d97

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0xef_csrss.exe_bugcheck_critical_process_8da82080_stackptr_error_ntdll!ntterminateprocess

FAILURE_ID_HASH:  {cb1f5d2d-babc-5182-2d49-32f9d8f0ee1e}

Followup:     MachineOwner
---------

0: kd> kL
 # Child-SP          RetAddr           Call Site
00 fffff184`02187c78 fffff802`1ec9fc8d nt!KeBugCheckEx
01 fffff184`02187c80 fffff802`1ebdcf07 nt!PspCatchCriticalBreak+0xfd
02 fffff184`02187d20 fffff802`1ea9780c nt!PspTerminateAllThreads+0x146873
03 fffff184`02187d90 fffff802`1ea99349 nt!PspTerminateProcess+0xe0
04 fffff184`02187dd0 fffff802`1e5d8305 nt!NtTerminateProcess+0xa9
05 fffff184`02187e40 00007ffc`77f5fce4 nt!KiSystemServiceCopyEnd+0x25
06 000000d8`d1b3cfc8 00007ffc`73e983a1 ntdll!NtTerminateProcess+0x14
07 000000d8`d1b3cfd0 00007ffc`77f91a68 CSRSRV!CsrUnhandledExceptionFilter+0x131
08 000000d8`d1b3d060 00007ffc`77f63400 ntdll!LdrpLogFatalUserCallbackException+0x98
09 000000d8`d1b3d1a0 00007ffc`77f6477f ntdll!KiUserCallbackDispatcherHandler+0x20
0a 000000d8`d1b3d1e0 00007ffc`77ec4bef ntdll!RtlpExecuteHandlerForException+0xf
0b 000000d8`d1b3d210 00007ffc`77f634ee ntdll!RtlDispatchException+0x40f
0c 000000d8`d1b3d940 00007ffc`77cf7cf6 ntdll!KiUserExceptionDispatch+0x2e
0d 000000d8`d1b3e730 00007ffc`77cf7c76 USER32!DefDlgProcWorker+0x66
0e 000000d8`d1b3e7f0 00007ffc`77cfca66 USER32!DefDlgProcW+0x36
0f 000000d8`d1b3e830 00007ffc`77cfc78c USER32!UserCallWinProcCheckWow+0x266
10 000000d8`d1b3e9b0 00007ffc`77d17a08 USER32!DispatchClientMessage+0x9c
11 000000d8`d1b3ea10 00007ffc`77f63494 USER32!_fnNCDESTROY+0x38
12 000000d8`d1b3ea70 00007ffc`74c41f24 ntdll!KiUserCallbackDispatcherContinue
13 000000d8`d1b3eaf8 00007ffc`77d015df win32u!NtUserCreateWindowEx+0x14
14 000000d8`d1b3eb00 00007ffc`77cff642 USER32!VerNtUserCreateWindowEx+0x20f
15 000000d8`d1b3ee90 00007ffc`77d1f19a USER32!InternalCreateDialog+0x612
16 000000d8`d1b3f070 00007ffc`77d63836 USER32!InternalDialogBox+0x106
17 000000d8`d1b3f0d0 00007ffc`77d62275 USER32!SoftModalMessageBox+0x7e6
18 000000d8`d1b3f220 00007ffc`77d62fb2 USER32!MessageBoxWorker+0x319
19 000000d8`d1b3f3d0 00007ffc`73e39726 USER32!MessageBoxTimeoutW+0x192
1a 000000d8`d1b3f4d0 00007ffc`73e39bfd winsrvext!HardErrorHandler+0x32a
1b 000000d8`d1b3f690 00007ffc`73e3a0ee winsrvext!ProcessHardErrorRequest+0xe9
1c 000000d8`d1b3f700 00007ffc`73e9872d winsrvext!UserHardErrorEx+0x4be
1d 000000d8`d1b3f7c0 00007ffc`73e97ec5 CSRSRV!QueueHardError+0x1a5
1e 000000d8`d1b3f800 00007ffc`77f2a27f CSRSRV!CsrApiRequestThread+0x2525
1f 000000d8`d1b3fc90 00000000`00000000 ntdll!RtlUserThreadStart+0x2f
0: kd> r
rax=ffff888d8da82080 rbx=ffff888d8dc2e003 rcx=00000000000000ef
rdx=ffff888d8dc2e080 rsi=ffff888d8dc2e080 rdi=ffff888d8dc2e080
rip=fffff8021e5c7050 rsp=fffff18402187c78 rbp=00000000c0000000
 r8=0000000000000000  r9=0000000000000000 r10=7ffffffffffffffc
r11=fffff18402187e38 r12=00007ffc77f63401 r13=00000000c0000005
r14=0000000000000000 r15=00000000c0000005
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00000246
nt!KeBugCheckEx:
fffff802`1e5c7050 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff184`02187c80=00000000000000ef


↧

disable ctrl+n on RDP

March 29, 2020, 5:14 am
$
0
0

hello

i want to disable the option of Ctrl+n (new window) in remote desktop (terminal servers)

how do i do it ?

thanks!

Yan

↧

PublishedApp

April 13, 2020, 10:42 am
$
0
0

Hi there

I am trying to publish an application to my RDS 2019 environment with special settings per user.

I am familiar into how to publish most of the apps but this one comes with a trick.

In the typical RDS desktop environment, each user has their won desktop that when launched, looks at the target command and pulls the property from the registry entry. Something like

users one has on desktop a shortcut that points to "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" in the target but we add /111.

So the shortcut in the Target is something like : "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" /111

Each users will have that shortcut differently:

user 2 "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" /112

user 3 "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" /113

Question here, is: 

How can I publish that shortcut to my users that log into the rds web interface.

Thanks

↧
Search

RDS CALs per user only partially issued

April 6, 2020, 6:40 am
$
0
0

Hello,

We have a new Server 2016 Remote Desktop environment set up (1 broker + 2 TS's).
We installed 50 RDS CALs (per user).

At first none of the CALs were being issued, but the remote desktop connections work fine nonetheless (published apps).
License configuration + License Diagnostics say everything is OK.

So we removed the licenses, reinitialized the database, reinstalled the licenses, reactivated license server.
After that we noticed that about 10% of the connections made had a corresponding CAL issued.
I have no idea why some are issued and most are not. The users for whom the CAL was issued are spread across both TS's.
Eventviewer shows nothing out of the ordinary regarding RDS licensing. License config + diagnostics still say everything is OK.

It also turns out that the grace period is still active when we check through WMI : 110 days left (10 days past since reactivating the licenses).

Any ideas on where to look next ? Thank you.

↧
↧

Remote Desktop licensing

April 21, 2020, 1:31 am
$
0
0

Good day,

I need to get licensing to allow multiple users to connect to my local server simultaneously, i have tried contacting Microsoft support i had no luck can anyone assist if you have purchased a RDP license before, how do i go about doing that? Thank you.

Kind regards 

Sibusiso  

↧

Azure AD Proxy and RDS 2019- Does Set-RDPublishedName script work? (logon attempt failed)

April 22, 2020, 4:16 pm
$
0
0

Well I just wrote a multi-page post here referencing my entire architecture, troubleshooting attempts made, guides read and then got an internal server error when I tried to post it so I'm not going to go through that again, I'll just simplify my question-

Has anyone gotten Azure AD Proxy in pre-authentication mode to work with RDS 2019 in an environment where you alter the published name to prevent certificate warnings due to split domains?

I have everything setup exactly as is described here- https://docs.microsoft.com/en-us/azure/active-directory/manage-apps/application-proxy-integrate-with-remote-desktop-services

Internal address points to an internal DNS record that points to my connection broker/rd gateway server.

This all works fine for the RD Web Access Portal, I can login to the external address, get prompted by azure for login, get to the internal portal without errors, login there and can see my session host collection. When I click that collection though I get"logon attempt failed"

This is using Internet Explorer, with the MsRdpClientShell Class addin enabled.

The gateway works perfectly inside of my network, using the DNS address or the server FQDN (though this way will give cert warnings).

I've tried disabling HTTP redirection on the IIS server on the connection broker. I've set the RAP to allow connections to all resources and when that did not work I specifically added the DNS name to the resource list.

Mostly I just need to know if this is even possible or if Azure AD proxy will not work with the RD Gateway using a changed published address like this.

Thanks!

---

Edit- Also I cannot find any failed connections in the logs, so it doesn't appear as if the connection attempt is actually hitting the broker or gateway


↧

How to stop close runing program when you log off

April 21, 2020, 8:58 am
$
0
0

Hi i need an info, i use windows server 2011 Small business Essentials and i have a problem

when i log off close my program playout wich is playlist software and i,m forced to be loged in 24/7 so other users cannot be loged in when admin is loged so please how to set up to not close my program or exclude.

↧

How to Activate CAL user in Windows 2012 , when we have only Tracking ID instead of Activation key

February 6, 2018, 10:37 am
$
0
0
I have brought Windows server 2012  R2 standard. I have license of 15 CAL for  remote desktop session. but instead of Activation key i only get Tracking ID. Now the Question ishow can i activate the RD service on my server by using the Tracking ID. although my Windows is activated by OEM, also i have valid product key for Windows but no information about CAL.

↧
↧

Do we need IIS to be running for RD Gateway Server ?

April 23, 2020, 6:33 pm
$
0
0

Hi,

We are using RD Gateway Server (Running on Windows 2008R2 Server).  It is only used by End Users to connect to their own Desktop at office.

We would like to find out whether we can disable IIS ?

Thanks

↧

How to install, setup and configure RDP cal license

April 24, 2020, 10:06 am
$
0
0

Hello!

Have bought 2 cals for my Windows server 2012R2, as I then can have 4 connections to my server at the same time. But I can't find any full documentation how to install, setup and configure the RDP so it will work. 

Got the license server installed, and the cals activated and installed, but only 2 can connect. Looks like the 2 I bought isn't working right.

Does anybody have a fully step-by-step to get RDP to work right??

↧
Search

Web Site and RD Gateway Server ?

April 23, 2020, 6:33 pm
$
0
0

Hi,

We are using RD Gateway Server (Running on Windows 2008R2 Server).  It is only used by End Users to connect to their own Desktop at office.

We would like to find out whether we can disable IIS ?

Thanks


↧

RDS Per User Cals - Downgrade 2019 -> 2012

April 15, 2020, 6:32 am
$
0
0

Hi All,

I'm attempting to apply additional Per User Cals to several managed service clients' RDS Servers.

Their RDS Servers are a mix of 2016 and 2012R2.

The Per User Cals procured are 2019 so we need to perform a downgrade.

These were procured via the clients Volume Licencing. 

From initial reading it seems that the CALs should auto downgrade on application, however we are receiving the following upon entering the Agreement and Licencing numbers we recieve:

"The licensing agreement data provided to Microsoft is not valid. Check all the information you provided, make any necessary corrections, and then resubmit your request. If the problem persists, try using a different connection method."

This occurs on completely separate environments. 

On calling VLSC support was advised that, to allow the downgrade to take place , the RDS server would need to be taken out of production and I should have a support agent on a call at the time.

This feels a little excessive. Would value any thoughts or experiences of others performing the above.

Many thanks
Kev

↧
↧

RDS CALs won't Activate

March 30, 2020, 12:43 am
$
0
0

I have Server 2016 Standard with 1 RDS CAL installed and all is working.

I am now having an issue when trying to add 3 additional RDS CALs
I have tried to activate by phone and internet and both are unsuccessful.
It says to check the event logs for more info, but I can’t find any error entries. The activation wizard returns this error code Message Number: 0x13a6 (tried to google without success)

I’m not sure if the issue is due to the CALs being issued for Server 2019 (my Microsoft Partner said they were backwards compatible).

↧

Black Screen on all new Connections, SessionHost has to be rebooted

June 21, 2017, 2:31 am
$
0
0

hi,

we're suffering from session hosts that produce black screen errors in a RDS 2016 farm.

already connected users can mostly work, all new connections end up with a black screen.

to resolve the error the server has to be restarted.

i can say that

- this error appears after error 1534 (Fehler bei der Profilbenachrichtigung des Ereignisses Delete für Komponente {709E2729-F883-441e-A877-ED3CEFC975E6}. Fehlercode: Das System kann die angegebene Datei nicht finden.) starts appearing in the eventviewer.

- upon checking the registry for this SID i end up at "ProfileNotifyHandler Class app id {E10F6C3A-F1AE-4adc-AA9D-2FE65525666E} inprocserver32, C:\Windows\System32\gameux.dll".

- starting explorer.exe per taskmgr does not open an actual explorer window although the process appears in taskmgr

- tskmgr, eventvwr, cmd can be started without problems

- affected users appear as active in RDS management

- no third party security software is installed

- farm is fully patched

- HKLM\Software\Microsoft\WindowsNT\CurrentVersion\ProfileGUID and ProfileList are ok (no old or .bak entries)

looking forward on how to resolve this without  rebooting the server or a permanent fix

thank you

best regards


↧

RDS Licensing Server consolidation

April 23, 2020, 1:38 pm
$
0
0

We've two RDS Licensing Servers.

Server A - Windows Server 2019 acting as a RDS Licensing server with its own License Server ID & installed Windows Server 2012 20 - Per User CAL's

Server B - Windows Server 2016 acting as a RDS Licensing server with its own License Server ID & installed Windows Server 2012 60- Per User CAL's

Can I merge both the servers to one.

I need to move RDS CAL's from Server B to Server A(which has existing RDS CAL's & of course has its own License Server ID) 

Then eventually decommission Server B.

I do understand the process of migrating from one RDS Licensing server to a new server but here I'm talking about consolidating it to one

Thanks


↧
Viewing all 5613 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>