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

Windows server 2019 RDS/remoteapp server certificate problem

$
0
0

Hi,

I have a problem with a certificate, when I want to access to the remote app(untrusted certificate). I have two servers in LB(ts01, ts02, and third server gateway(tsg01). Servers ts01 and ts02 is in LB. Ts01 is the broker.  I found this site https://www.urtech.ca/2013/03/solved-how-to-source-and-install-a-certificate-for-server-2012-rdweb-site-or-any-other-iis-8-site/

I make a request certificate in IIS(but, my mistake on server ts02), I bought 3rd party certificate, and then import on server ts01 in "spider" deployments certificate(all certificate look TRUSTED, and then import this 3rd party certificate in IIS, both server(ts01, ts02), binding od https 443 too. But, when I connect to site https://www.xXXXX.com/RdWeb certificate is still untrusted(self sign certiciate). My question, the error is, that request cert must be on server ts01,or the procedure is completely different?



Remote Desktop Services: Session Shadowing, Not working to shadow different user

$
0
0

We have enabled Remote Desktop Services: Session Shadowing for local server 2012R2 

1.we have edited Groupr policy in Administrative Templates\Windows Components\Remote Desktop Servers\Remote Desktop Session Host\Connections\Set rules for remote control of Remote Desktop Services user sessions

in level--View Session without user’s permission

2.we have enabled roles like 

Remote Desktop Connection Broker
Remote Desktop Licensing.
Remote Desktop Session Host.
Remote Desktop Web Access.

still we are not able to see Collections in Remote Desktop Services,

and session-2 is prompting to give access when we are taking access from session-1 command prompt ----only a popup of some GUI is appearing on session-1 (only for millisecond)

Please help me to resolve this issue

RD Gateway - Local users for RD CAP and RD RAP

$
0
0

Hi,

I'd like to a have a secondary User account (& password) database to allow access through a RD Gateway. (The idea is to make that secondary database dynamic to achieve a Two Factors Authentication).

I tried to use the Local Users group of the RD Gateway itself but I can"t make it work.

I have allowed Local Users group on RD CAP and RD RAP.

On the client, when I unselect "use my RD Gateway credentials for the remote computer, to have a two steps connection, the connection fails and the  logs says 

> The user "<user>@<RD Gateway>", on client computer "xx.xx.xx.xx:port", has initiated an outbound connection. This connection may not be authenticated yet.


OTOH When I select "use my RD Gateway credentials for the remote computer, connection goes well (because domain users are allowed as well at the moment, to make sure that the RD Gateway is functionnal) and the The log says

>The user "<My Domain>\<user>", on client computer "xx.xx.xx.xx", met connection authorization policy requirements and was therefore authorized

Any hints to use the RD Gateway server Local Users for RD CAP and RD RAP ?








How to allow Terminal Server logon scripts to use PowerShell full language mode?

$
0
0

Hello everybody,

At a customer's site there is a PowerShell logon script set for users via GPO. The users log on to Terminal (RDP) Servers. PowerShell seems to be in restricted language mode at least for normal users. However, the logon script must use features not available in PowerShell restricted language mode.

How can we have the logon scripts in full language mode please?


Best Regards, Stefan Falk

RDS Per User Cals - Downgrade 2019 -> 2012

$
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

Difference between "Disconnect session" and "End session" in Sessions Tab of User Properties

$
0
0

Situation 1: Active session limit : 2 minutes, When session limit is reached: Disconnect from session

After two minutes I got a message that "the session will end in 2 minutes, please save save and close all programs".

Situation 1: Active session limit : 2 minutes, When session limit is reached: Disconnect from session

I got the same message as above.

So what is the difference between  "Disconnect session" and "End session"


Thanks and Regards, Radhakrishnan

Trial license for RDS per user

$
0
0

Hi,

I want to use RDS during the trial period, but I am in doubt if I can use it both by device or by user?

I read that the trial works only for device and not per user.

I also read that since 2012 the trial licensing has changed, now you have defined how many will use it.

Thanks.

RDS 2019 collection clipboard redirection text vs file copy

$
0
0

I've setup a RDS infrastructure wit WebAccess, RD Gateway, RD Connection Broker and a RD Session Host.

I've allowed all redirection options except Drives. Both in the RDS collections settings as at the group policy level. |I'm experiencing that it is possible to copy text strings from local to server and the other way around(tested this with word and notepad) but not files copy (example copy the word document). I do not experience this with the standard 3 licensed user Remote desktop enabled 2019 servers.

Is this expected behaviour for full RDS feature?


users unable to login to RDS (user profile service prohibits..)

$
0
0

Hi,

Sometimes we have issues with users unable to login to the RDS collection. Researching this we came to the conclusion the problem is with corrupt profiles on the local RDS server. Sometimes people login with a temp profile, creating a profile folder with only appdata.

The way to fix this issue is cleaning the local profile from all RDS server in the collection and renaming the roaming profile from the fileservers.

Im looking for a script or tool that correctly cleans profiles from RDS servers and also cleans the registry in Profilelist and Profileguid. For now i only found scripts that does one thing and not everything that is needed to clean corrupt ones.

Thanks!

RemoteApp RDS2019 - splash screens stuck on client

$
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.

Remote Desktop - License issue results in 60 minute session time limit

$
0
0

I have 2 machines:

A) Server 2019 Standard

B) Server 2016 Standard

I am not on a domain.

Server-A acts as a licensing server for both Server-A and Server-B

I installed the remote desktop licensing service on Server-A on 18-Mar-2020 and installed per-device CALs for 2012, 2016, and 2019. original install date for the machine running the licensing service is Feb-2019. It is activated and RD Diagnoser "did not identify any problems to report"

I was then able to connect with 10+ clients on either machine simultaneously.

Today, a few weeks later, connecting clients on Server-A (which hosts the licensing server) receive: "there is a problem with your remote desktop license and your session will be disconnected in 60 min"

This error does not appear when connecting to Server-B.

The RD Licensing Manager shows "issued" as 0 for both device and user CALs.

I verified that the local gp on either machine was configured (comp config > admin templates > rds > rd licensing > remote desktop session host > licensing >

1) use specified server is configured on both servers by IP address

2) remote desktop licensing mode is set to device

I rebuilt the licensing database and re-applied the per-device licenses with no effect.

tried deleting a MSLicensing registry key on both server and client with no effect.

there are certificate entries in:

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

...but I have not touched them

Removing UPD's from Session Collection (2016)

$
0
0

Has anyone ever removed UPD's from a Terminal Services Session Collection (2016) before?

I've tested removing the setting in my dev environment and that new users don't get a UPD and existing users no longer mount theirs at login. Besides the obviously profile data now missing, are there any traps that are not obvious?

I have already enabled folder redirection so all users files and folders will remain (outside of appdata), I'm considering moving to FSLogix, anyone else moved from UPD to FSLogix?

https://docs.microsoft.com/en-us/fslogix/install-ht

Our reason is that our AV and security suite keep locking the UPD's after a user logs out and changing our suite is not possible at this point in time.

Thanks

Craig

RDS with Multifactor Authentication that works with Macs?

$
0
0

Hi,

My org currently uses RDS 2012 R2 and we use the "Microsoft Remote Desktop" application for a lot of users to be able to access our environment from Apple and android devices. Words come down that Multi-factor authentication is a priority going forward and I am currently configuring a RDS environment built on Server 2019 that uses the Azure Application Proxy for multi-factor pre-authentication...

But it appears to me that using this method the Microsoft Remote Desktop app doesn't work. It gets a "the remote resource feed is invalid" error when connecting, and the instructions I've found for configuring on-premise RDS integration with Azure say that it only supports Windows 7 and 10, unless using passthrough (which as I understand does not support Multi-Factor Authentication).

I did some quick reading on using NPS for MFA for RDS but I'm not finding much that would make me think it would work with the Mac OS/Android Microsoft Remote Desktop app.

Is there another method for Mac users to connect to RDS and get MFA? Do one of the methods above work with the Microsoft Remote Desktop app? What are other people using to get around this (do you just tell people no Macs allowed?)

Thanks!

application permissions not working at all in remote access configuration

$
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

$
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

$
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

Server 2019 BSOD - Terminal Server

$
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


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

$
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?

Remote Desktop Gateway - Event 304/Error "23005"

$
0
0

Hi,

I am tearing my hair out.  I have a RD Gateway server that is pointing towards a RD Farm.  I cannot connect to it using the Gateway.  I keep getting the the following error in the TerminalServices-Gateway Operational log:

Log Name:      Microsoft-Windows-TerminalServices-Gateway/Operational
Source:        Microsoft-Windows-TerminalServices-Gateway
Date:          10/7/2014 10:56:02 AM
Event ID:      304
Task Category: (3)
Level:         Warning
Keywords:      (16777216)
User:          NETWORK SERVICE
Computer:      XXXXXXXXXXX.wbc.local
Description:
The user "XXXXXX", on client computer "XXX.XXX.XXX.XXX", met connection authorization policy and resource authorization policy requirements, but could not connect to resource "SyteLine.wbc.local". The following error occurred:"23005".
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-TerminalServices-Gateway" Guid="{4D5AE6A1-C7C8-4E6D-B840-4D8080B42E1B}" />
    <EventID>304</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>3</Task>
    <Opcode>44</Opcode>
    <Keywords>0x4000000001000000</Keywords>
    <TimeCreated SystemTime="2014-10-07T15:56:02.952172000Z" />
    <EventRecordID>183</EventRecordID>
    <Correlation />
    <Execution ProcessID="2428" ThreadID="3140" />
    <Channel>Microsoft-Windows-TerminalServices-Gateway/Operational</Channel>
    <Computer>WBC-SLGW-01.wbc.local</Computer>
    <Security UserID="S-1-5-20" />
  </System>
  <UserData>
    <EventInfo xmlns="aag">
      <Username>XXXXXXXXXXXXX</Username>
      <IpAddress>XXX.XXX.XXX.XXX</IpAddress>
      <AuthType>
      </AuthType>
      <Resource>SyteLine.wbc.local</Resource>
      <ErrorCode>23005</ErrorCode>
    </EventInfo>
  </UserData>
</Event>

Any ideas?  Lots of googling has not helped

Thanks


Cloning a RDS that is already part of a collection

$
0
0

Am needing to create a new RDS server due to a larger than normal usage.

Issue I have is the RDS server simply has too many applications to be reloaded from scratch, and if I clone it I get the issue where it is already part of a collection.

Also there is currently too many users live for me to be able to remove the server from the collection and then clone it.

Obviously disabling the NIC, renaming it, sysprep, anything else I can think of isn't working.

Is there a way to clone and remove the collection settings after the server is removed from the domain and renamed?

Thanks.

Jason

Viewing all 25525 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>