I've confirmed our security apps are not blocking it. I will add that the SiteRemote Client Startup type is automatic and Logon is the local System account.
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\ Report Id: 2bd7fe90-82f4-4049-b17c-90de8d66fcf7įaulting package-relative application ID:
Mdmp viewer online code#
NET Runtimeĭescription: The process was terminated due to an unhandled exception.Įxception Info: exception code c0000005, exception address 1005CE0Fįaulting application name: SiteRemoteClientService.exe, version: 1.2.0.193, time stamp: 0x5937e9d1įaulting module name: cpuidsdk.dll, version: 1.1.3.2, time stamp: 0x56961be1įaulting application start time: 0x01d7385414075f10įaulting application path: C:\Program Files (x86)\SiteKiosk\SiteRemote\SiteRemoteClientService.exeįaulting module path: C:\Program Files (x86)\SiteKiosk\SiteRemote\cpuidsdk.dll There are crashes in the application eventviewer for SiteRemoteClientService.exe and. The kiosk can access the SiteRemote server via 8086 by using this PowerShell command.
Mdmp viewer online update#
Re: Sitekiosk not connecting to siteremote after 20H2 update Hopefully, this would help identifying the cause. You can find more about required ports here. Then you will need to check the firewall settings for your computer or company network.
0 kommentar(er)
