# SSU Scan Information Scan Info: Version:"2.5.0.15" Date:"03/29/2022" Time:"00:01:27.0665822" # Scanned Hardware Computer: BaseBoard Manufacturer:"LENOVO" BIOS Mode:"UEFI" BIOS Version/Date:"LENOVO N30ET43W (1.26 ) , 11/08/2021 12:00 AM" CD or DVD:"Not Available" Embedded Controller Version:"1.16" Platform Role:"Mobile" Processor:"Intel(R) Core(TM) i7-10850H CPU @ 2.70GHz , GenuineIntel" Secure Boot State:"Off" SMBIOS Version:"3.2" Sound Card:"Realtek High Definition Audio(SST)" Sound Card:"Intel(R) Display Audio" Sound Card:"ThinkPad Thunderbolt 3 Dock USB Audio" System Manufacturer:"LENOVO" System Model:"20TQ003KMB" System SKU:"LENOVO_MT_20TQ_BU_Think_FM_ThinkPad P15v Gen 1" System Type:"x64-based PC" - "Display" Intel ® Graphics Driver Version:"27.20.100.9466" - "Citrix Indirect Display Adapter" Adapter Compatibility:"Citrix Systems Inc." Adapter DAC Type:"Not Available" Adapter RAM:"Not Available" Availability:"Offline" Bits Per Pixel:"Not Available" Caption:"Citrix Indirect Display Adapter" CoInstallers:"oem101.inf,ViddDev_Install.NT,Not Available,Not Available" Color Table Entries:"Not Available" Dedicated Video Memory:"Not Available" Driver:"WUDFRd.sys" Driver Date:"01/23/2019 01:00 AM" Driver Path:"C:\Windows\system32\drivers\WUDFRd.sys" Driver Provider:"Citrix Systems Inc." Driver Version:"12.40.44.247" INF:"oem101.inf" INF Section:"ViddDev_Install.NT" Install Date:"Not Available" Installed Drivers:"Not Available" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"Not Available" Location:"Not Available" Manufacturer:"Citrix Systems Inc." Microsoft DirectX* Version:"DirectX 12" Monochrome:"No" Number of Colors:"Not Available" Number of Video Pages:"Not Available" PNP Device ID:"PCI\VEN_5853&DEV_1003\1&79F5D87&0&03" Power Management Capabilities:"Not Available" Power Management Supported:"Not Available" Refresh Rate - Current:"Not Available" Refresh Rate - Maximum:"Not Available" Refresh Rate - Minimum:"Not Available" Resolution:"Not Available" Scan Mode:"Not Available" Service Name:"WUDFRd" Status:"OK" Video Architecture:"VGA" Video Memory:"Unknown" Video Processor:"Not Available" - "Intel(R) UHD Graphics" Adapter Compatibility:"Intel Corporation" Adapter DAC Type:"Internal" Adapter RAM:"1.00 GB" Availability:"Running or Full Power" Bits Per Pixel:"32" - "Caption":"Intel(R) UHD Graphics" Link:"http://www.intel.com/content/www/us/en/search.html?keyword=UHD+Graphics" CoInstallers:"oem183.inf,iCML_w10_DS,Internal,Intel(R) UHD Graphics Family" Color Table Entries:"4294967296" Dedicated Video Memory:"Not Available" Driver:"igdkmd64.sys" Driver Date:"11/15/2021 01:00 AM" Driver Path:"C:\Windows\system32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igdkmd64.sys" Driver Provider:"Intel Corporation" Driver Version:"30.0.101.1122" INF:"oem183.inf" INF Section:"iCML_w10_DS" Install Date:"Not Available" Installed Drivers:"C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igdumdim64.dll,C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igd10iumd64.dll,C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igd10iumd64.dll,C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igd12umd64.dll" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"Not Available" Location:"PCI bus 0, device 2, function 0" Manufacturer:"Intel Corporation" Microsoft DirectX* Version:"DirectX 12" Monochrome:"No" Number of Colors:"4294967296" Number of Video Pages:"Not Available" PNP Device ID:"PCI\VEN_8086&DEV_9BC4&SUBSYS_22A617AA&REV_05\3&11583659&0&10" Power Management Capabilities:"Not Available" Power Management Supported:"Not Available" Refresh Rate - Current:"60 Hz" Refresh Rate - Maximum:"75 Hz" Refresh Rate - Minimum:"50 Hz" Resolution:"1920 X 1200" Scan Mode:"Noninterlaced" Service Name:"igfx" Status:"OK" Video Architecture:"VGA" Video Memory:"Unknown" Video Processor:"Intel(R) UHD Graphics Family" - "NVIDIA Quadro P620" Adapter Compatibility:"NVIDIA" Adapter DAC Type:"Integrated RAMDAC" Adapter RAM:"4.00 GB" Availability:"Running or Full Power" Bits Per Pixel:"32" Caption:"NVIDIA Quadro P620" CoInstallers:"oem134.inf,Section100,Integrated RAMDAC,Quadro P620" Color Table Entries:"4294967296" Dedicated Video Memory:"Not Available" Driver:"nvlddmkm.sys" Driver Date:"10/20/2021 02:00 AM" Driver Path:"C:\Windows\system32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvlddmkm.sys" Driver Provider:"NVIDIA" Driver Version:"30.0.14.7242" INF:"oem134.inf" INF Section:"Section100" Install Date:"Not Available" Installed Drivers:"C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvldumdx.dll" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"Not Available" Location:"PCI bus 1, device 0, function 0" Manufacturer:"NVIDIA" Microsoft DirectX* Version:"DirectX 12" Monochrome:"No" Number of Colors:"4294967296" Number of Video Pages:"Not Available" PNP Device ID:"PCI\VEN_10DE&DEV_1CBD&SUBSYS_22A617AA&REV_A1\4&330FF97B&0&0008" Power Management Capabilities:"Not Available" Power Management Supported:"Not Available" Refresh Rate - Current:"60 Hz" Refresh Rate - Maximum:"0 Hz" Refresh Rate - Minimum:"Not Available" Resolution:"1920 X 1200" Scan Mode:"Noninterlaced" Service Name:"nvlddmkm" Status:"OK" Video Architecture:"VGA" Video Memory:"Unknown" Video Processor:"Quadro P620" - "Memory" Physical Memory (Available):"5.80 GB" Physical Memory (Installed):"16 GB" Physical Memory (Total):"15.76 GB" - "BANK 2" Capacity:"16 GB" Channel:"ChannelB-DIMM0" Configured Clock Speed:"2933 MHz" Configured Voltage:"1200 millivolts" Data Width:"64 bits" Form Factor:"SODIMM" Interleave Position:"Not Available" Manufacturer:"Ramaxel" Maximum Voltage:"Not Available" Memory Type:"Unknown" Minimum Voltage:"Not Available" Part Number:"RMSA3330MJ78HBF-3200" Serial Number:"12DF4210" Status:"Not Available" Type:"Synchronous" - "Motherboard" Availability:"Running or Full Power" BIOS:"N30ET43W (1.26 ), LENOVO - 1260" Caption:"Motherboard" Chipset:"Not Available" Date:"11/08/2021 01:00 AM" Install Date:"Not Available" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Manufacturer:"LENOVO" Model:"Not Available" Part Number:"Not Available" PNP Device ID:"ACPI\PNP0C01\2&DABA3FF&1" Power Management Capabilities:"Not Available" Power Management Supported:"Not Available" Product:"20TQ003KMB" Serial Number:"L1HF0990047" Status:"OK" Version:"0B98417 WIN" - "Networking" Intel ® Network Connections Install Options:"Not Available" Intel ® Network Connections Version:"Not Available" Intel ® PROSet/Wireless Software Version:"Not Available" - "Bluetooth Device (Personal Area Network) #2" Availability:"Running or Full Power" Caption:"Bluetooth Device (Personal Area Network) #2" CoInstallers:"Not Available" Default IP Gateway:"Not Available" DHCP Enabled:"Yes" DHCP Lease Expires:"Not Available" DHCP Lease Obtained:"Not Available" DHCP Server:"Not Available" Driver:"bthpan.sys" Driver Date:"06/21/2006 12:00 AM" Driver Path:"C:\Windows\system32\drivers\bthpan.sys" Driver Provider:"Microsoft" Driver Version:"10.0.19041.1" Index:"0022" INF:"bthpan.inf" INF Section:"BthPan.Install" Install Date:"Not Available" Installed:"Yes" IP Address:"Not Available" IP Subnet:"Not Available" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"03/28/2022 06:22 PM" Location:"Not Available" MAC Address:"78:2B:46:C3:25:75" Manufacturer:"Microsoft" Media Type: Net Connection ID:"Bluetooth Network Connection 2" NetCfgInstanceId:"{8B502C5F-C7A8-4763-8213-FC4336DE90D9}" Number of VLANs:"0" PNP Device ID:"BTH\MS_BTHPAN\6&258946EF&1&2" Port:"Not Available" Power Management (Low Power):"Not Available" Power Management (Wake On LAN):"Not Available" Power Management (Wake on Magic Packet):"Not Available" Power Management Capabilities:"Not Available" Power Management Supported:"No" Product Type:"Bluetooth Device (Personal Area Network)" Service Name:"BthPan" Status:"Enabled" Team Name:"Not in a team" Temperature: Type:"Ethernet 802.3" - "Service Bindings" Client for Microsoft Networks: File and Printer Sharing for Microsoft Networks: Internet Protocol Version 4 (TCP/IPv4): Internet Protocol Version 6 (TCP/IPv6): Link-Layer Topology Discovery Mapper I/O Driver: Link-Layer Topology Discovery Responder: Microsoft LLDP Protocol Driver: Npcap Packet Driver (NPCAP): - "Fortinet SSL VPN Virtual Ethernet Adapter" Availability:"Running or Full Power" Caption:"Fortinet SSL VPN Virtual Ethernet Adapter" CoInstallers:"Not Available" Default IP Gateway:"Not Available" DHCP Enabled:"Yes" DHCP Lease Expires:"Not Available" DHCP Lease Obtained:"Not Available" DHCP Server:"Not Available" Driver:"ftsvnic.sys" Driver Date:"12/02/2021 12:00 AM" Driver Path:"C:\Windows\system32\drivers\ftsvnic.sys" Driver Provider:"Fortinet" Driver Version:"2021.2.12.0" Index:"0017" INF:"oem27.inf" INF Section:"ftsvnic.ndi" Install Date:"Not Available" Installed:"Yes" IP Address:"Not Available" IP Subnet:"Not Available" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"03/28/2022 06:22 PM" Location:"Not Available" MAC Address:"Not Available" Manufacturer:"Fortinet Inc." Media Type: Net Connection ID:"Ethernet 5" NetCfgInstanceId:"{64DFDC82-5A05-4D45-BB0B-E3B7EB4E2041}" Number of VLANs:"0" PNP Device ID:"ROOT\NET\0002" Port:"Not Available" Power Management (Low Power):"Not Available" Power Management (Wake On LAN):"Not Available" Power Management (Wake on Magic Packet):"Not Available" Power Management Capabilities:"Not Available" Power Management Supported:"No" Product Type:"Fortinet SSL VPN Virtual Ethernet Adapter" Service Name:"ftsvnic" Status:"Device is disabled." Team Name:"Not in a team" Temperature: Type:"Not Available" - "Service Bindings" Client for Microsoft Networks: File and Printer Sharing for Microsoft Networks: FortiClient NDIS 6.3 Packet Filter Driver: Internet Protocol Version 4 (TCP/IPv4): Internet Protocol Version 6 (TCP/IPv6): Link-Layer Topology Discovery Mapper I/O Driver: Link-Layer Topology Discovery Responder: Microsoft LLDP Protocol Driver: Npcap Packet Driver (NPCAP): QoS Packet Scheduler: - "Fortinet Virtual Ethernet Adapter (NDIS 6.30)" Availability:"Running or Full Power" Caption:"Fortinet Virtual Ethernet Adapter (NDIS 6.30)" CoInstallers:"Not Available" Default IP Gateway:"Not Available" DHCP Enabled:"Yes" DHCP Lease Expires:"Not Available" DHCP Lease Obtained:"Not Available" DHCP Server:"Not Available" Driver:"ftvnic.sys" Driver Date:"09/04/2020 12:00 AM" Driver Path:"C:\Windows\system32\drivers\ftvnic.sys" Driver Provider:"Fortinet" Driver Version:"2020.4.9.0" Index:"0016" INF:"oem23.inf" INF Section:"FTNT.ndi" Install Date:"Not Available" Installed:"Yes" IP Address:"Not Available" IP Subnet:"Not Available" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"03/28/2022 06:22 PM" Location:"Not Available" MAC Address:"00:09:0F:FE:00:01" Manufacturer:"Fortinet" Media Type: Net Connection ID:"Ethernet 4" NetCfgInstanceId:"{4A145406-AAC3-4BC2-BC7B-A60F341A01E1}" Number of VLANs:"0" PNP Device ID:"ROOT\NET\0001" Port:"Not Available" Power Management (Low Power):"Not Available" Power Management (Wake On LAN):"Not Available" Power Management (Wake on Magic Packet):"Not Available" Power Management Capabilities:"Not Available" Power Management Supported:"No" Product Type:"Fortinet Virtual Ethernet Adapter (NDIS 6.30)" Service Name:"ft_vnic" Status:"Enabled" Team Name:"Not in a team" Temperature: Type:"Ethernet 802.3" - "Service Bindings" Client for Microsoft Networks: File and Printer Sharing for Microsoft Networks: FortiClient NDIS 6.3 Packet Filter Driver: Internet Protocol Version 4 (TCP/IPv4): Internet Protocol Version 6 (TCP/IPv6): Link-Layer Topology Discovery Mapper I/O Driver: Link-Layer Topology Discovery Responder: Microsoft LLDP Protocol Driver: Npcap Packet Driver (NPCAP): QoS Packet Scheduler: - "Intel(R) Ethernet Connection (11) I219-LM" Availability:"Running or Full Power" - "Caption":"Intel(R) Ethernet Connection (11) I219-LM" Link:"http://www.intel.com/content/www/us/en/search.html?keyword=Ethernet+Connection+(11)+I219+LM" CoInstallers:"Not Available" Default IP Gateway:"Not Available" DHCP Enabled:"Yes" DHCP Lease Expires:"Not Available" DHCP Lease Obtained:"Not Available" DHCP Server:"Not Available" Driver:"e1d68x64.sys" Driver Date:"03/02/2020 12:00 AM" Driver Path:"C:\Windows\system32\DriverStore\FileRepository\e1d68x64.inf_amd64_7b6bb8abbc171f0a\e1d68x64.sys" Driver Provider:"Intel" Driver Version:"12.18.9.20" ETrackID:"Not Available" Index:"0013" INF:"oem19.inf" INF Section:"E0D4C.10.0.1.19H1" Install Date:"Not Available" Installed:"Yes" IP Address:"Not Available" IP Subnet:"Not Available" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"03/28/2022 06:22 PM" Location:"PCI bus 0, device 31, function 6" MAC Address:"54:05:DB:50:B7:94" Manufacturer:"Intel" Media Type: Net Connection ID:"Ethernet" NetCfgInstanceId:"{E8D0EF8B-7FFA-47CA-A352-043FEFE31A9A}" Number of VLANs:"0" NVM Version:"Not Available" Part Number:"FFFFFF-0FF" PNP Device ID:"PCI\VEN_8086&DEV_0D4C&SUBSYS_22B817AA&REV_00\3&11583659&0&FE" Port:"Not Available" Power Management (Low Power):"Active: Yes, Enable: Yes" Power Management (Wake On LAN):"Active: Yes, Enable: No" Power Management (Wake on Magic Packet):"Active: Yes, EnableWakeOnMagicPacketOnly: No" Power Management Capabilities:"Not Available" Power Management Supported:"No" Product Type:"Intel(R) Ethernet Connection (11) I219-LM" Service Name:"e1dexpress" Status:"Enabled" Team Name:"Not in a team" Temperature: Type:"Ethernet 802.3" - "Service Bindings" Client for Microsoft Networks: File and Printer Sharing for Microsoft Networks: FortiClient NDIS 6.3 Packet Filter Driver: Internet Protocol Version 4 (TCP/IPv4): Internet Protocol Version 6 (TCP/IPv6): Link-Layer Topology Discovery Mapper I/O Driver: Link-Layer Topology Discovery Responder: Microsoft LLDP Protocol Driver: Npcap Packet Driver (NPCAP): QoS Packet Scheduler: - "Settings" *FlowControl:Flow Control:"Rx & Tx Enabled (3)" *InterruptModeration:Interrupt Moderation:"Enabled (1)" *IPChecksumOffloadIPv4:IPv4 Checksum Offload:"Rx & Tx Enabled (3)" *JumboPacket:Jumbo Packet:"Disabled (1514)" *LsoV2IPv4:Large Send Offload V2 (IPv4):"Enabled (1)" *LsoV2IPv6:Large Send Offload V2 (IPv6):"Enabled (1)" *NumRssQueues:Maximum Number of RSS Queues:"2 Queues (2)" *PMARPOffload:Protocol ARP Offload:"Enabled (1)" *PMNSOffload:Protocol NS Offload:"Enabled (1)" *PriorityVLANTag:Packet Priority & VLAN:"Packet Priority & VLAN Enabled (3)" *PtpHardwareTimestamp:PTP Hardware Timestamp:"Disabled (0)" *ReceiveBuffers:Receive Buffers:"256 (256)" *RSS:Receive Side Scaling:"Enabled (1)" *RSSProfile:RSS load balancing profile:"ClosestProcessor (1)" *SoftwareTimestamp:Software Timestamp:"Disabled (0)" *SpeedDuplex:Speed & Duplex:"Auto Negotiation (0)" *TCPChecksumOffloadIPv4:TCP Checksum Offload (IPv4):"Rx & Tx Enabled (3)" *TCPChecksumOffloadIPv6:TCP Checksum Offload (IPv6):"Rx & Tx Enabled (3)" *TransmitBuffers:Transmit Buffers:"512 (512)" *UDPChecksumOffloadIPv4:UDP Checksum Offload (IPv4):"Rx & Tx Enabled (3)" *UDPChecksumOffloadIPv6:UDP Checksum Offload (IPv6):"Rx & Tx Enabled (3)" *WakeOnMagicPacket:Wake on Magic Packet:"Enabled (1)" *WakeOnPattern:Wake on Pattern Match:"Enabled (1)" AdaptiveIFS:Adaptive Inter-Frame Spacing:"Disabled (0)" AutoPowerSaveModeEnabled:Link Speed Battery Saver:"Disabled (0)" EEELinkAdvertisement:Energy Efficient Ethernet:"On (1)" EnablePME:Enable PME:"Enabled (1)" ITR:Interrupt Moderation Rate:"Adaptive (65535)" LinkNegotiationProcess:Legacy Switch Compatibility Mode:"Disabled (1)" LogLinkStateEvent:Log Link State Event:"Enabled (51)" MasterSlave:Gigabit Master Slave Mode:"Auto Detect (0)" ReduceSpeedOnPowerDown:Reduce Speed On Power Down:"Enabled (1)" SipsEnabled:System Idle Power Saver:"Disabled (0)" ULPMode:Ultra Low Power Mode:"Enabled (1)" WaitAutoNegComplete:Wait for Link:"Auto Detect (2)" WakeOnLink:Wake on Link Settings:"Disabled (0)" - "Intel(R) Wi-Fi 6 AX201 160MHz" Access Point: Authentication: Availability:"Running or Full Power" - "Caption":"Intel(R) Wi-Fi 6 AX201 160MHz" Link:"http://www.intel.com/content/www/us/en/search.html?keyword=Wi+Fi+6+AX201+160MHz" Channel: Cipher: CoInstallers:"Not Available" Connection Mode: Default IP Gateway:"Not Available" DHCP Enabled:"Yes" DHCP Lease Expires:"Not Available" DHCP Lease Obtained:"Not Available" DHCP Server:"Not Available" Driver:"Netwtw10.sys" Driver Date:"02/01/2022 12:00 AM" Driver Path:"C:\Windows\system32\drivers\Netwtw10.sys" Driver Provider:"Intel" Driver Version:"22.110.1.1" Index:"0001" INF:"oem169.inf" INF Section:"Install_GEN_QSR_HrP_201_AX_2x2_WinT_non_6e" Install Date:"Not Available" Installed:"Yes" IP Address:"Not Available" IP Subnet:"Not Available" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"03/28/2022 06:22 PM" Location:"PCI bus 0, device 20, function 3" MAC Address:"78:2B:46:C3:25:71" Manufacturer:"Intel Corporation" Media Type: Net Connection ID:"Wi-Fi" NetCfgInstanceId:"{09A2A838-AA8A-48A2-A145-975B23801B1B}" Network Name:"Wi-Fi" Network Type: Number of VLANs:"0" PNP Device ID:"PCI\VEN_8086&DEV_06F0&SUBSYS_00708086&REV_00\3&11583659&0&A3" Port:"Not Available" Power Management (Low Power):"Active: Yes, Enable: No" Power Management (Wake On LAN):"Active: Yes, Enable: No" Power Management (Wake on Magic Packet):"Active: Yes, EnableWakeOnMagicPacketOnly: No" Power Management Capabilities:"Not Available" Power Management Supported:"No" Product Type:"Intel(R) Wi-Fi 6 AX201 160MHz" Profile: Radio Type: Receive Rate: Service Name:"Netwtw10" Signal Strength: State:"disconnected" Status:"Enabled" Team Name:"Not in a team" Temperature: Transmit Rate: Type:"Ethernet 802.3" - "Service Bindings" Client for Microsoft Networks: File and Printer Sharing for Microsoft Networks: FortiClient NDIS 6.3 Packet Filter Driver: Internet Protocol Version 4 (TCP/IPv4): Internet Protocol Version 6 (TCP/IPv6): Link-Layer Topology Discovery Mapper I/O Driver: Link-Layer Topology Discovery Responder: Microsoft LLDP Protocol Driver: Npcap Packet Driver (NPCAP): QoS Packet Scheduler: - "Settings" *DeviceSleepOnDisconnect:Sleep on WoWLAN Disconnect:"Disabled (0)" *PacketCoalescing:Packet Coalescing:"Enabled (1)" *PMARPOffload:ARP offload for WoWLAN:"Enabled (1)" *PMNSOffload:NS offload for WoWLAN:"Enabled (1)" *PMWiFiRekeyOffload:GTK rekeying for WoWLAN:"Enabled (1)" *WakeOnMagicPacket:Wake on Magic Packet:"Enabled (1)" *WakeOnPattern:Wake on Pattern Match:"Enabled (1)" BgScanGlobalBlocking:Global BG Scan blocking:"Never (0)" ChannelWidth24:Channel Width for 2.4GHz:"Auto (1)" ChannelWidth52:Channel Width for 5GHz:"Auto (1)" CtsToItself:Mixed Mode Protection:"RTS/CTS Enabled (0)" FatChannelIntolerant:Fat Channel Intolerant:"Disabled (0)" IbssTxPower:Transmit Power:"5. Highest (100)" IEEE11nMode:802.11n/ac/ax Wireless Mode:"4. 802.11ax (3)" MIMOPowerSaveMode:MIMO Power Save Mode:"Auto SMPS (0)" RoamAggressiveness:Roaming Aggressiveness:"3. Medium (2)" RoamingPreferredBandType:Preferred Band:"1. No Preference (0)" ThroughputBoosterEnabled:Throughput Booster:"Disabled (0)" uAPSDSupport:U-APSD support:"Disabled (0)" WirelessMode:802.11a/b/g Wireless Mode:"6. Dual Band 802.11a/b/g (34)" - "Lenovo USB Ethernet" Availability:"Running or Full Power" Caption:"Lenovo USB Ethernet" CoInstallers:"Not Available" Default IP Gateway:"192.9.200.220" DHCP Enabled:"Yes" DHCP Lease Expires:"03/29/2022 11:40 AM" DHCP Lease Obtained:"03/29/2022 10:40 AM" DHCP Server:"192.168.10.26" Driver:"rtump64x64.sys" Driver Date:"09/14/2021 12:00 AM" Driver Path:"C:\Windows\system32\drivers\rtump64x64.sys" Driver Provider:"Realtek" Driver Version:"10.48.914.2021" Index:"0015" INF:"oem34.inf" INF Section:"RTL8153BCx64_S5WOL.ndi.NT" Install Date:"Not Available" Installed:"Yes" IP Address:"192.9.200.66;fe80::c084:6cc2:20a9:b875" IP Subnet:"255.255.255.0;64" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"03/28/2022 06:22 PM" Location:"Port_#0002.Hub_#0006" MAC Address:"08:3A:88:61:48:76" Manufacturer:"Realtek" Media Type: Net Connection ID:"Ethernet 3" NetCfgInstanceId:"{A172F0EE-6CF5-41A6-A61C-6F14C8CF88AE}" Number of VLANs:"0" PNP Device ID:"USB\VID_17EF&PID_3082\101614876" Port:"Not Available" Power Management (Low Power):"Active: Yes, Enable: Yes" Power Management (Wake On LAN):"Active: Yes, Enable: No" Power Management (Wake on Magic Packet):"Active: Yes, EnableWakeOnMagicPacketOnly: No" Power Management Capabilities:"Not Available" Power Management Supported:"No" Product Type:"Lenovo USB Ethernet" Service Name:"rtump64x64" Status:"Enabled" Team Name:"Not in a team" Temperature: Type:"Ethernet 802.3" - "Service Bindings" Client for Microsoft Networks: File and Printer Sharing for Microsoft Networks: FortiClient NDIS 6.3 Packet Filter Driver: Internet Protocol Version 4 (TCP/IPv4): Internet Protocol Version 6 (TCP/IPv6): Link-Layer Topology Discovery Mapper I/O Driver: Link-Layer Topology Discovery Responder: Microsoft LLDP Protocol Driver: Npcap Packet Driver (NPCAP): QoS Packet Scheduler: - "Settings" *EEE:Energy-Efficient Ethernet:"Enabled (1)" *FlowControl:Flow Control:"Rx & Tx Enabled (3)" *IPChecksumOffloadIPv4:IPv4 Checksum Offload:"Rx & Tx Enabled (3)" *JumboPacket:Jumbo Frame:"Disabled (1514)" *LsoV2IPv4:Large Send Offload v2 (IPv4):"Enabled (1)" *LsoV2IPv6:Large Send Offload v2 (IPv6):"Enabled (1)" *ModernStandbyWoLMagicPacket:Modern Standby WoL Magic Packet:"Disabled (0)" *PMARPOffload:ARP Offload:"Enabled (1)" *PMNSOffload:NS Offload:"Enabled (1)" *PriorityVLANTag:Priority & VLAN:"Priority & VLAN Enabled (3)" *SelectiveSuspend:Selective suspend:"Enabled (1)" *SpeedDuplex:Speed & Duplex:"Auto Negotiation (0)" *SSIdleTimeout:SS idle timeout:"5 (5)" *SSIdleTimeoutScreenOff:SS idle timeout(Screen off):"3 (3)" *TCPChecksumOffloadIPv4:TCP Checksum Offload (IPv4):"Rx & Tx Enabled (3)" *TCPChecksumOffloadIPv6:TCP Checksum Offload (IPv6):"Rx & Tx Enabled (3)" *UDPChecksumOffloadIPv4:UDP Checksum Offload (IPv4):"Rx & Tx Enabled (3)" *UDPChecksumOffloadIPv6:UDP Checksum Offload (IPv6):"Rx & Tx Enabled (3)" *WakeOnMagicPacket:Wake on Magic Packet:"Enabled (1)" *WakeOnPattern:Wake on pattern match:"Enabled (1)" AdvancedEEE:Advanced EEE:"Disabled (0)" BatteryModeLinkSpeed:Battery Mode Link Speed:"Not Speed Down (0)" EnableAdaptiveLinkCap:Adaptive Link Speed:"Disabled (0)" EnableExtraPowerSaving:Idle Power Saving:"Enabled (1)" EnableGreenEthernet:Green Ethernet:"Enabled (1)" S5WakeOnLan:Shutdown Wake-On-Lan:"Enabled (1)" WakeOnLinkChange:Wake on link change:"Enabled (1)" WolShutdownLinkSpeed:WOL & Shutdown Link Speed:"10 Mbps First (0)" - "PPPoP WAN Adapter" Availability:"Running or Full Power" Caption:"PPPoP WAN Adapter" CoInstallers:"Not Available" Default IP Gateway:"Not Available" DHCP Enabled:"No" DHCP Lease Expires:"Not Available" DHCP Lease Obtained:"Not Available" DHCP Server:"Not Available" Driver:"pppop64.sys" Driver Date:"03/22/2016 12:00 AM" Driver Path:"C:\Windows\system32\drivers\pppop64.sys" Driver Provider:"Fortinet" Driver Version:"2016.3.22.0" Index:"0018" INF:"oem68.inf" INF Section:"pppop.Ndi.NTamd64" Install Date:"Not Available" Installed:"Yes" IP Address:"Not Available" IP Subnet:"Not Available" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"03/28/2022 06:22 PM" Location:"Not Available" MAC Address:"Not Available" Manufacturer:"Fortinet Inc." Media Type: Net Connection ID:"Local Area Connection" NetCfgInstanceId:"{4DE3CD8B-7C94-4EC5-9638-2B532050E9AB}" Number of VLANs:"0" PNP Device ID:"ROOT\NET\0003" Port:"Not Available" Power Management (Low Power):"Not Available" Power Management (Wake On LAN):"Not Available" Power Management (Wake on Magic Packet):"Not Available" Power Management Capabilities:"Not Available" Power Management Supported:"No" Product Type:"PPPoP WAN Adapter" Service Name:"pppop" Status:"Enabled" Team Name:"Not in a team" Temperature: Type:"Not Available" - "Sophos SSL VPN Adapter" Availability:"Running or Full Power" Caption:"Sophos SSL VPN Adapter" CoInstallers:"Not Available" Default IP Gateway:"Not Available" DHCP Enabled:"Yes" DHCP Lease Expires:"Not Available" DHCP Lease Obtained:"Not Available" DHCP Server:"Not Available" Driver:"tap0901.sys" Driver Date:"05/11/2014 12:00 AM" Driver Path:"C:\Windows\system32\drivers\tap0901.sys" Driver Provider:"Sophos SSL VPN" Driver Version:"9.0.0.21" Index:"0014" INF:"oem69.inf" INF Section:"tap0901.ndi" Install Date:"Not Available" Installed:"Yes" IP Address:"Not Available" IP Subnet:"Not Available" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"03/28/2022 06:22 PM" Location:"Not Available" MAC Address:"00:FF:9D:0C:D5:CD" Manufacturer:"Sophos SSL VPN" Media Type: Net Connection ID:"Ethernet 2" NetCfgInstanceId:"{9D0CD5CD-D279-4C14-B0AB-6A0A9CEC67E3}" Number of VLANs:"0" PNP Device ID:"ROOT\NET\0000" Port:"Not Available" Power Management (Low Power):"Not Available" Power Management (Wake On LAN):"Not Available" Power Management (Wake on Magic Packet):"Not Available" Power Management Capabilities:"Not Available" Power Management Supported:"No" Product Type:"Sophos SSL VPN Adapter" Service Name:"tap0901" Status:"Enabled" Team Name:"Not in a team" Temperature: Type:"Ethernet 802.3" - "Service Bindings" Client for Microsoft Networks: File and Printer Sharing for Microsoft Networks: FortiClient NDIS 6.3 Packet Filter Driver: Internet Protocol Version 4 (TCP/IPv4): Internet Protocol Version 6 (TCP/IPv6): Link-Layer Topology Discovery Mapper I/O Driver: Link-Layer Topology Discovery Responder: Microsoft LLDP Protocol Driver: Npcap Packet Driver (NPCAP): QoS Packet Scheduler: - "Settings" AllowNonAdmin:Non-Admin Access:"Allowed (1)" MediaStatus:Media Status:"Application Controlled (0)" MTU:MTU:"1500 (1500)" - "Operating System" .Net Framework Version:"2.0,3.0,3.5,4.0,4.8" Boot Device:"\Device\HarddiskVolume1" Locale:"United States" OS Manufacturer:"Microsoft Corporation" OS Name:"Microsoft Windows 10 Pro" Other OS Description:"Not Available" Page File:"C:\pagefile.sys" Page File Space:"4.75 GB" Physical Memory (Available):"5.81 GB" Physical Memory (Installed):"16 GB" Physical Memory (Total):"15.76 GB" System Directory:"C:\Windows\system32" Version:"10.0.19044 Build 19044" Virtual Memory (Available):"5.99 GB" Virtual Memory (Total):"20.51 GB" Windows Directory:"C:\Windows" - "Installed Updates" KB2151757:"Microsoft Visual C++ 2010 x86 Redistributable - 10.0.40219 [01/09/2021]" KB2151757:"Microsoft Visual C++ 2010 x64 Redistributable - 10.0.40219 [01/09/2021]" KB2467173:"Microsoft Visual C++ 2010 x64 Redistributable - 10.0.40219 [01/09/2021]" KB2467173:"Microsoft Visual C++ 2010 x86 Redistributable - 10.0.40219 [01/09/2021]" KB2468871:"Microsoft .NET Framework 4 Extended [Not Available]" KB2468871:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2468871v2:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2468871v2:"Microsoft .NET Framework 4 Extended [Not Available]" KB2478063:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2478063:"Microsoft .NET Framework 4 Extended [Not Available]" KB2533523:"Microsoft .NET Framework 4 Extended [Not Available]" KB2533523:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2544514:"Microsoft .NET Framework 4 Extended [Not Available]" KB2544514:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2600211:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2600211:"Microsoft .NET Framework 4 Extended [Not Available]" KB2600217:"Microsoft .NET Framework 4 Extended [Not Available]" KB2600217:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB4562830:"Update [5/4/2021]" KB4570334:"Security Update [11/18/2020]" KB4577586:"Update [5/4/2021]" KB4580325:"Security Update [11/19/2020]" KB4586864:"Security Update [11/19/2020]" KB5000736:"Update [6/1/2021]" KB5003791:"Update [3/3/2022]" KB5005699:"Security Update [9/15/2021]" KB5006753:"Update [11/16/2021]" KB5007273:"Update [12/15/2021]" KB5008876:"Update [1/21/2022]" KB5011352:"Security Update [2/10/2022]" KB5011487:"Security Update [3/9/2022]" KB982573:"Microsoft Visual C++ 2010 x64 Redistributable - 10.0.40219 [01/09/2021]" KB982573:"Microsoft Visual C++ 2010 x86 Redistributable - 10.0.40219 [01/09/2021]" SP1:"Microsoft Visual C++ 2010 x86 Redistributable - 10.0.40219 [Not Available]" SP1:"Microsoft Visual C++ 2010 x64 Redistributable - 10.0.40219 [Not Available]" - "Processor" - "Intel(R) Core(TM) i7-10850H CPU @ 2.70GHz" Architecture:"x64" ATPO:"Not Available" Availability:"Running or Full Power" Caption:"Intel64 Family 6 Model 165 Stepping 2" - "Chipset Name":"Intel(R) Core(TM) i7-10850H CPU @ 2.70GHz" Link:"http://www.intel.com/content/www/us/en/search.html?keyword=Core+i7+10850H+CPU+" CPU Speed:"2.71 GHz" Current Voltage:"8. volts" Driver:"Not Available" Driver Date:"04/21/2009 12:00 AM" Driver Path:"C:\Windows\system32\drivers\intelppm.sys" Driver Provider:"Microsoft" Driver Version:"10.0.19041.546" Ext. Family:"Not Available" Family:"Intel Core™ i7-2760QM" FPO:"Not Available" INF:"cpu.inf" INF Section:"IntelPPM_Inst.NT" Install Date:"Not Available" Last Error Code:"Not Available" Level 1 Cache:"6 x 384 KB" Level 2 Cache:"6 x 1536 KB" Level 3 Cache:"12 MB" Load:"12%" Manufacturer:"GenuineIntel" Model:"165" Name:"Intel(R) Core(TM) i7-10850H CPU @ 2.70GHz" Number of Cores:"6" Number of Cores Enabled:"6" Number of Logical Processors:"12" Part Number:"None" Power Management Capabilities:"Not Available" Power Management Supported:"No" Processor ID:"BFEBFBFF000A0652" Revision:"Not Available" Serial Number:"None" Service Name:"intelppm" Status:"OK" Stepping:"2" Version:"Not Available" - "Storage" - "WDC PC SN730 SDBQNTY-512G-1001" Capablities:"Random Access, Supports Writing" Caption:"WDC PC SN730 SDBQNTY-512G-1001" Cylinder - Total:"62260" Description:"Disk drive" Driver:"Not Available" Driver Date:"06/21/2006 12:00 AM" Driver Version:"10.0.19041.789" Error Code:"Device is working properly" Firmware Revision:"11170101" Heads - Total:"255" Index:"0" INF:"disk.inf" Install Date:"Not Available" Interface Type:"SCSI" Manufacturer:"(Standard disk drives)" Model:"WDC PC SN730 SDBQNTY-512G-1001" Name:"\\.\PHYSICALDRIVE0" Partitions:"4" Physical Sector Size:"4096" PNP Device ID:"SCSI\DISK&VEN_NVME&PROD_WDC_PC_SN730_SDB\5&1E045789&0&000000" Policies:"Read Retention Priority=EqualPriority, Write Retention Priority=EqualPriority, Scalar Prefetch=Not Available, Block Prefetch=Not Available" SCSI Bus:"0" SCSI LUN:"0" SCSI Port:"0" Sectors - Per Track:"63" Sectors - Total:"1000206900" Serial Number:"001B_448B_48BE_CD0F." Size:"476.94 GB" Size – Available:"291.52 GB" Status:"OK" Tracks - Per Cylinder:"255" Tracks - Total:"15876300" - "C:" Availability:"Not Available" Caption:"C:" Compression Method:"Not Compressed" Description:"Local Fixed Disk" File System:"NTFS" Name:"Not Available" Serial Number:"5E3CBE7F" Size:"194.71 GB" Size – Available:"75.27 GB" Status:"Not Available" Volume Dirty:"No" - "D:" Availability:"Not Available" Caption:"D:" Compression Method:"Not Compressed" Description:"Local Fixed Disk" File System:"NTFS" Name:"Stock" Serial Number:"4652E169" Size:"281.63 GB" Size – Available:"216.25 GB" Status:"Not Available" Volume Dirty:"No" ...#SSU#... #Logs#System Messages#Included ------------------------------------------------------------------- The Lenovo Hotkey Client Loader service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.AAD.BrokerPlugin_1000.19041.1023.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Start-up script failed. GPO Name: Sophos_Install GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{AFC88A2F-95CE-45B4-B2E6-64666E7E1CC8}\Machine Script Name: \\francois.int\NETLOGON\Sophos.bat ------------------------------------------------------------------- Start-up script failed. GPO Name: Install_Insight_Discovery_Update GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{F8826B94-387A-4C26-88B5-33F427E144E2}\Machine Script Name: \\francois.int\it-tools\GPO\Scripts\Insight_update.ps1 ------------------------------------------------------------------- Start-up script failed. GPO Name: Teamviewer_15_Full_AF_NEW GPO File System Path: \\francois.int\sysvol\francois.int\Policies\{25374D65-7C82-4D33-B569-C99DAF6618AE}\Machine Script Name: \\francois.int\it-tools\GPO\Install\Teamviewer\V15.20.6\AF\Full.bat ------------------------------------------------------------------- Start-up script failed. GPO Name: ClearFont GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{CE91AB25-4D34-46D8-985C-E7C56341ECC1}\Machine Script Name: \\francois.int\it-tools\GPO\Scripts\ClearFont.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 15:45:00 on ‎28/‎03/‎2022 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The system detected an address conflict for IP address 192.9.200.2 with the system having network hardware address 00-1B-00-32-0A-67. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- Intel(R) Wi-Fi 6 AX201 160MHz : The network adapter has returned an invalid value to the driver. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 16:03:20 on ‎25/‎03/‎2022 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 16:38:03 on ‎24/‎03/‎2022 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Intel(R) Wi-Fi 6 AX201 160MHz : The network adapter has returned an invalid value to the driver. ------------------------------------------------------------------- Intel(R) Wi-Fi 6 AX201 160MHz : The network adapter has returned an invalid value to the driver. ------------------------------------------------------------------- The server {0006F03A-0000-0000-C000-000000000046} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {0006F03A-0000-0000-C000-000000000046} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {0006F03A-0000-0000-C000-000000000046} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 16:48:45 on ‎22/‎03/‎2022 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- Intel(R) Wi-Fi 6 AX201 160MHz : The network adapter has returned an invalid value to the driver. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- The server {2387FADA-8CE7-42C6-BB56-854FBE8BFEA7} did not register with DCOM within the required timeout. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Intel(R) Wi-Fi 6 AX201 160MHz : The network adapter has returned an invalid value to the driver. ------------------------------------------------------------------- Intel(R) Wi-Fi 6 AX201 160MHz : The network adapter has returned an invalid value to the driver. ------------------------------------------------------------------- Intel(R) Wi-Fi 6 AX201 160MHz : The network adapter has returned an invalid value to the driver. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- The Lenovo Hotkey Client Loader service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- The server {F87B28F1-DA9A-4F35-8EC0-800EFCF26B83} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Start-up script failed. GPO Name: Sophos_Install GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{AFC88A2F-95CE-45B4-B2E6-64666E7E1CC8}\Machine Script Name: \\francois.int\NETLOGON\Sophos.bat ------------------------------------------------------------------- Start-up script failed. GPO Name: Install_Insight_Discovery_Update GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{F8826B94-387A-4C26-88B5-33F427E144E2}\Machine Script Name: \\francois.int\it-tools\GPO\Scripts\Insight_update.ps1 ------------------------------------------------------------------- Start-up script failed. GPO Name: Teamviewer_15_Full_AF_NEW GPO File System Path: \\francois.int\sysvol\francois.int\Policies\{25374D65-7C82-4D33-B569-C99DAF6618AE}\Machine Script Name: \\francois.int\it-tools\GPO\Install\Teamviewer\V15.20.6\AF\Full.bat ------------------------------------------------------------------- Start-up script failed. GPO Name: ClearFont GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{CE91AB25-4D34-46D8-985C-E7C56341ECC1}\Machine Script Name: \\francois.int\it-tools\GPO\Scripts\ClearFont.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 09:53:25 on ‎20/‎03/‎2022 was unexpected. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 17:24:17 on ‎19/‎03/‎2022 was unexpected. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Start-up script failed. GPO Name: Sophos_Install GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{AFC88A2F-95CE-45B4-B2E6-64666E7E1CC8}\Machine Script Name: \\francois.int\NETLOGON\Sophos.bat ------------------------------------------------------------------- Start-up script failed. GPO Name: Install_Insight_Discovery_Update GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{F8826B94-387A-4C26-88B5-33F427E144E2}\Machine Script Name: \\francois.int\it-tools\GPO\Scripts\Insight_update.ps1 ------------------------------------------------------------------- Start-up script failed. GPO Name: Teamviewer_15_Full_AF_NEW GPO File System Path: \\francois.int\sysvol\francois.int\Policies\{25374D65-7C82-4D33-B569-C99DAF6618AE}\Machine Script Name: \\francois.int\it-tools\GPO\Install\Teamviewer\V15.20.6\AF\Full.bat ------------------------------------------------------------------- Start-up script failed. GPO Name: ClearFont GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{CE91AB25-4D34-46D8-985C-E7C56341ECC1}\Machine Script Name: \\francois.int\it-tools\GPO\Scripts\ClearFont.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a02:2788:104:13d4::6 with the system having network hardware address 00-11-32-3B-A9-ED. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 15:49:25 on ‎18/‎03/‎2022 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NKSQGP7F2NH-5319275A.WhatsAppDesktop. ------------------------------------------------------------------- Intel(R) Wi-Fi 6 AX201 160MHz : The network adapter has returned an invalid value to the driver. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 16:42:10 on ‎17/‎03/‎2022 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The OpenSSH SSH Server service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x8024CE0A: Lenovo Ltd. - Firmware - 259.0.0.10. ------------------------------------------------------------------- The OpenSSH SSH Server service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The User Energy Server Service queencreek service terminated with the following error: Driver %2 returned invalid ID for a child device (55005300450052005F0045005300520056005F005300560043005F0051005500450045004E0043005200450045004B000000). ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Intel(R) Wi-Fi 6 AX201 160MHz : The network adapter has returned an invalid value to the driver. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the igfxCUIService2.0.0.0 service. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 16:51:13 on ‎14/‎03/‎2022 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- Intel(R) Wi-Fi 6 AX201 160MHz : The network adapter has returned an invalid value to the driver. ------------------------------------------------------------------- Intel(R) Wi-Fi 6 AX201 160MHz : The network adapter has returned an invalid value to the driver. ------------------------------------------------------------------- The OpenSSH SSH Server service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 14:33:13 on ‎11/‎03/‎2022 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The OpenSSH SSH Server service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- Intel(R) Wi-Fi 6 AX201 160MHz : The network adapter has returned an invalid value to the driver. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.AAD.BrokerPlugin_1000.19041.1023.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. ------------------------------------------------------------------- The system detected an address conflict for IP address 192.9.200.92 with the system having network hardware address 5A-83-7C-A4-6A-9A. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Start-up script failed. GPO Name: Sophos_Install GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{AFC88A2F-95CE-45B4-B2E6-64666E7E1CC8}\Machine Script Name: \\francois.int\NETLOGON\Sophos.bat ------------------------------------------------------------------- Start-up script failed. GPO Name: Install_Insight_Discovery_Update GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{F8826B94-387A-4C26-88B5-33F427E144E2}\Machine Script Name: \\francois.int\it-tools\GPO\Scripts\Insight_update.ps1 ------------------------------------------------------------------- Start-up script failed. GPO Name: Teamviewer_15_Full_AF_NEW GPO File System Path: \\francois.int\sysvol\francois.int\Policies\{25374D65-7C82-4D33-B569-C99DAF6618AE}\Machine Script Name: \\francois.int\it-tools\GPO\Install\Teamviewer\V15.20.6\AF\Full.bat ------------------------------------------------------------------- Start-up script failed. GPO Name: ClearFont GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{CE91AB25-4D34-46D8-985C-E7C56341ECC1}\Machine Script Name: \\francois.int\it-tools\GPO\Scripts\ClearFont.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The OpenSSH SSH Server service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Start-up script failed. GPO Name: Sophos_Install GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{AFC88A2F-95CE-45B4-B2E6-64666E7E1CC8}\Machine Script Name: \\francois.int\NETLOGON\Sophos.bat ------------------------------------------------------------------- Start-up script failed. GPO Name: Install_Insight_Discovery_Update GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{F8826B94-387A-4C26-88B5-33F427E144E2}\Machine Script Name: \\francois.int\it-tools\GPO\Scripts\Insight_update.ps1 ------------------------------------------------------------------- Start-up script failed. GPO Name: Teamviewer_15_Full_AF_NEW GPO File System Path: \\francois.int\sysvol\francois.int\Policies\{25374D65-7C82-4D33-B569-C99DAF6618AE}\Machine Script Name: \\francois.int\it-tools\GPO\Install\Teamviewer\V15.20.6\AF\Full.bat ------------------------------------------------------------------- Start-up script failed. GPO Name: ClearFont GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{CE91AB25-4D34-46D8-985C-E7C56341ECC1}\Machine Script Name: \\francois.int\it-tools\GPO\Scripts\ClearFont.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The OpenSSH SSH Server service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The system detected an address conflict for IP address 192.9.200.123 with the system having network hardware address 00-1B-00-32-0A-67. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 16:55:32 on ‎10/‎03/‎2022 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the igfxCUIService2.0.0.0 service. ------------------------------------------------------------------- Cannot zero sectors on disk \\?\PhysicalDrive1. Error code: 15@01010012 ------------------------------------------------------------------- Cannot zero sectors on disk \\?\PhysicalDrive1. Error code: 15@01010012 ------------------------------------------------------------------- The OpenSSH SSH Server service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The OpenSSH SSH Server service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The User Energy Server Service queencreek service terminated with the following error: Driver %2 returned invalid ID for a child device (55005300450052005F0045005300520056005F005300560043005F0051005500450045004E0043005200450045004B000000). ------------------------------------------------------------------- The OpenSSH SSH Server service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Encrypted volume check: Volume information on E: cannot be read. ------------------------------------------------------------------- Cannot zero sectors on disk \\?\PhysicalDrive1. Error code: 15@01010012 ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- The server {2387FADA-8CE7-42C6-BB56-854FBE8BFEA7} did not register with DCOM within the required timeout. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NKSQGP7F2NH-5319275A.WhatsAppDesktop. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- The server {F87B28F1-DA9A-4F35-8EC0-800EFCF26B83} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Start-up script failed. GPO Name: Sophos_Install GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{AFC88A2F-95CE-45B4-B2E6-64666E7E1CC8}\Machine Script Name: \\francois.int\NETLOGON\Sophos.bat ------------------------------------------------------------------- Start-up script failed. GPO Name: Install_Insight_Discovery_Update GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{F8826B94-387A-4C26-88B5-33F427E144E2}\Machine Script Name: \\francois.int\it-tools\GPO\Scripts\Insight_update.ps1 ------------------------------------------------------------------- Start-up script failed. GPO Name: Teamviewer_15_Full_AF_NEW GPO File System Path: \\francois.int\sysvol\francois.int\Policies\{25374D65-7C82-4D33-B569-C99DAF6618AE}\Machine Script Name: \\francois.int\it-tools\GPO\Install\Teamviewer\V15.20.6\AF\Full.bat ------------------------------------------------------------------- Start-up script failed. GPO Name: ClearFont GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{CE91AB25-4D34-46D8-985C-E7C56341ECC1}\Machine Script Name: \\francois.int\it-tools\GPO\Scripts\ClearFont.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The WerSvc service was unable to log on as NT AUTHORITY\SYSTEM with the currently configured password due to the following error: The request is not supported. To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC). ------------------------------------------------------------------- The WerSvc service was unable to log on as NT AUTHORITY\SYSTEM with the currently configured password due to the following error: The security account manager (SAM) or local security authority (LSA) server was in the wrong state to perform the security operation. To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC). ------------------------------------------------------------------- The OpenSSH SSH Server service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The OpenSSH SSH Server service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The User Energy Server Service queencreek service terminated with the following error: Driver %2 returned invalid ID for a child device (55005300450052005F0045005300520056005F005300560043005F0051005500450045004E0043005200450045004B000000). ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {1A1F4206-0688-4E7F-BE03-D82EC69DF9A5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The server {60A90A2F-858D-42AF-8929-82BE9D99E8A1} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {2387FADA-8CE7-42C6-BB56-854FBE8BFEA7} did not register with DCOM within the required timeout. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The server {2387FADA-8CE7-42C6-BB56-854FBE8BFEA7} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Start-up script failed. GPO Name: Sophos_Install GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{AFC88A2F-95CE-45B4-B2E6-64666E7E1CC8}\Machine Script Name: \\francois.int\NETLOGON\Sophos.bat ------------------------------------------------------------------- Start-up script failed. GPO Name: Install_Insight_Discovery_Update GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{F8826B94-387A-4C26-88B5-33F427E144E2}\Machine Script Name: \\francois.int\it-tools\GPO\Scripts\Insight_update.ps1 ------------------------------------------------------------------- Start-up script failed. GPO Name: Teamviewer_15_Full_AF_NEW GPO File System Path: \\francois.int\sysvol\francois.int\Policies\{25374D65-7C82-4D33-B569-C99DAF6618AE}\Machine Script Name: \\francois.int\it-tools\GPO\Install\Teamviewer\V15.20.6\AF\Full.bat ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The OpenSSH SSH Server service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The server {F87B28F1-DA9A-4F35-8EC0-800EFCF26B83} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Start-up script failed. GPO Name: Sophos_Install GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{AFC88A2F-95CE-45B4-B2E6-64666E7E1CC8}\Machine Script Name: \\francois.int\NETLOGON\Sophos.bat ------------------------------------------------------------------- Start-up script failed. GPO Name: Install_Insight_Discovery_Update GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{F8826B94-387A-4C26-88B5-33F427E144E2}\Machine Script Name: \\francois.int\it-tools\GPO\Scripts\Insight_update.ps1 ------------------------------------------------------------------- Start-up script failed. GPO Name: Teamviewer_15_Full_AF_NEW GPO File System Path: \\francois.int\sysvol\francois.int\Policies\{25374D65-7C82-4D33-B569-C99DAF6618AE}\Machine Script Name: \\francois.int\it-tools\GPO\Install\Teamviewer\V15.20.6\AF\Full.bat ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 16:51:50 on ‎23/‎02/‎2022 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 16:52:21 on ‎22/‎02/‎2022 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The User Energy Server Service queencreek service terminated with the following error: Driver %2 returned invalid ID for a child device (55005300450052005F0045005300520056005F005300560043005F0051005500450045004E0043005200450045004B000000). ------------------------------------------------------------------- The OpenSSH SSH Server service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server Microsoft.Windows.Search_1.14.3.19041_neutral_neutral_cw5n1h2txyewy!CortanaUI.AppX49we79s9ab0xp8xpjb6t6g31ep03r71y.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Lenovo Hotkey Client Loader service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The certificate received from the remote server does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The server name we were expecting is updates.vc.logitech.com. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The server name we were expecting is updates.vc.logitech.com. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The server name we were expecting is updates.vc.logitech.com. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The server name we were expecting is datapipeline.logitech.io. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The server name we were expecting is updates.logitech.com. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The server name we were expecting is updates.logitech.com. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The server name we were expecting is updates.logitech.com. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The server name we were expecting is datapipeline.logitech.io. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- The server Microsoft.Windows.ContentDeliveryManager_10.0.19041.1023_neutral_neutral_cw5n1h2txyewy!App.AppXryc2qd338f5728r9gzzazav8206ba77s.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- Unable to bind to the underlying transport for [::]:50128. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine. The data field contains the error number. ------------------------------------------------------------------- The OpenSSH SSH Server service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The Group Policy Client service did not shut down properly after receiving a pre-shutdown control. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- Volume \\?\Volume{6bb4fb12-20fe-48c1-bfc6-be1c65638a5b} (\Device\HarddiskVolume12) needs to be taken offline to perform a Full Chkdsk. Please run "CHKDSK /F" locally via the command line, or run "REPAIR-VOLUME " locally or remotely via PowerShell. ------------------------------------------------------------------- The OpenSSH SSH Server service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The User Energy Server Service queencreek service terminated with the following error: Driver %2 returned invalid ID for a child device (55005300450052005F0045005300520056005F005300560043005F0051005500450045004E0043005200450045004B000000). ------------------------------------------------------------------- Volume \\?\Volume{6bb4fb12-20fe-48c1-bfc6-be1c65638a5b} (\Device\HarddiskVolume22) needs to be taken offline to perform a Full Chkdsk. Please run "CHKDSK /F" locally via the command line, or run "REPAIR-VOLUME " locally or remotely via PowerShell. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NKSQGP7F2NH-5319275A.WhatsAppDesktop. ------------------------------------------------------------------- A fatal error occurred while creating a TLS client credential. The internal error state is 10013. ------------------------------------------------------------------- A fatal error occurred while creating a TLS client credential. The internal error state is 10013. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- A fatal error occurred while creating a TLS client credential. The internal error state is 10013. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {2387FADA-8CE7-42C6-BB56-854FBE8BFEA7} did not register with DCOM within the required timeout. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {F87B28F1-DA9A-4F35-8EC0-800EFCF26B83} did not register with DCOM within the required timeout. ------------------------------------------------------------------- A fatal error occurred while creating a TLS client credential. The internal error state is 10013. ------------------------------------------------------------------- The Lenovo Hotkey Client Loader service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not apply the registry-based policy settings for the Group Policy object LDAP://CN=Machine,cn={7E7F5AAE-1C57-4F6E-BBFC-EF7A1FB6479E},cn=policies,cn=system,DC=francois,DC=int. Group Policy settings will not be resolved until this event is resolved. View the event details for more information on the filename and path that caused the failure. ------------------------------------------------------------------- The server {F87B28F1-DA9A-4F35-8EC0-800EFCF26B83} did not register with DCOM within the required timeout. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Start-up script failed. GPO Name: Sophos_Install GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{AFC88A2F-95CE-45B4-B2E6-64666E7E1CC8}\Machine Script Name: \\francois.int\NETLOGON\Sophos.bat ------------------------------------------------------------------- Start-up script failed. GPO Name: Install_Insight_Discovery_Update GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{F8826B94-387A-4C26-88B5-33F427E144E2}\Machine Script Name: \\francois.int\it-tools\GPO\Scripts\Insight_update.ps1 ------------------------------------------------------------------- Start-up script failed. GPO Name: Teamviewer_15_Full_AF_NEW GPO File System Path: \\francois.int\sysvol\francois.int\Policies\{25374D65-7C82-4D33-B569-C99DAF6618AE}\Machine Script Name: \\francois.int\it-tools\GPO\Install\Teamviewer\V15.20.6\AF\Full.bat ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The MicrosoftSearchInBing service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- The W32Time service terminated with the following error: A system shutdown is in progress. ------------------------------------------------------------------- The time service encountered an error and was forced to shut down. The error was: 0x8007045B: A system shutdown is in progress. ------------------------------------------------------------------- The LanmanServer service terminated with the following error: A system shutdown is in progress. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "782B46C32572" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "782B46C32572" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The DeviceInstall service failed to start due to the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The DeviceInstall service was unable to log on as NT AUTHORITY\SYSTEM with the currently configured password due to the following error: The request is not supported. To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC). ------------------------------------------------------------------- DCOM got error "1069" attempting to start the service LicenseManager with arguments "Unavailable" in order to run the server: {22F5B1DF-7D7A-4D21-97F8-C21AEFBA859C} ------------------------------------------------------------------- The LicenseManager service was unable to log on as NT Authority\LocalService with the currently configured password due to the following error: The request is not supported. To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC). ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The User Energy Server Service queencreek service terminated with the following error: Driver %2 returned invalid ID for a child device (55005300450052005F0045005300520056005F005300560043005F0051005500450045004E0043005200450045004B000000). ------------------------------------------------------------------- The OpenSSH SSH Server service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The Windows Modules Installer service terminated with the following error: The process cannot access the file because it is being used by another process. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A fatal error occurred while creating a TLS client credential. The internal error state is 10013. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {4AA0A5C4-1B9B-4F2E-99D7-99C6AEC83474} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {4AA0A5C4-1B9B-4F2E-99D7-99C6AEC83474} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {4AA0A5C4-1B9B-4F2E-99D7-99C6AEC83474} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {4AA0A5C4-1B9B-4F2E-99D7-99C6AEC83474} did not register with DCOM within the required timeout. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- A fatal error occurred while creating a TLS client credential. The internal error state is 10013. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- A CredSSP authentication to TERMSRV/AFEXDW16-DC01.extern.francois.int failed to negotiate a common protocol version. The remote host offered version 4 which is not permitted by Encryption Oracle Remediation. See https://go.microsoft.com/fwlink/?linkid=866660 for more information. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The Lenovo Hotkey Client Loader service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- A CredSSP authentication to TERMSRV/AFEXDW16-DC01.extern.francois.int failed to negotiate a common protocol version. The remote host offered version 4 which is not permitted by Encryption Oracle Remediation. See https://go.microsoft.com/fwlink/?linkid=866660 for more information. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {5F7F3F7B-1177-4D4B-B1DB-BC6F671B8F25} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- A fatal error occurred while creating a TLS client credential. The internal error state is 10013. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The OpenSSH SSH Server service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The User Energy Server Service queencreek service terminated with the following error: Driver %2 returned invalid ID for a child device (55005300450052005F0045005300520056005F005300560043005F0051005500450045004E0043005200450045004B000000). ------------------------------------------------------------------- The device (fb:d1:57:1a:40:20) is trying to distribute an Identity Resolving Key that is already used by a paired device. The pairing was rejected, if the intent was to pair with this device, you may need to first delete the existing pairing information. ------------------------------------------------------------------- The device (fb:d1:57:1a:40:1f) is trying to distribute an Identity Resolving Key that is already used by a paired device. The pairing was rejected, if the intent was to pair with this device, you may need to first delete the existing pairing information. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {2387FADA-8CE7-42C6-BB56-854FBE8BFEA7} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Lenovo Hotkey Client Loader service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- The server {F87B28F1-DA9A-4F35-8EC0-800EFCF26B83} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Start-up script failed. GPO Name: Sophos_Install GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{AFC88A2F-95CE-45B4-B2E6-64666E7E1CC8}\Machine Script Name: \\francois.int\NETLOGON\Sophos.bat ------------------------------------------------------------------- Start-up script failed. GPO Name: Install_Insight_Discovery_Update GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{F8826B94-387A-4C26-88B5-33F427E144E2}\Machine Script Name: \\francois.int\it-tools\GPO\Scripts\Insight_update.ps1 ------------------------------------------------------------------- Start-up script failed. GPO Name: Teamviewer_15_Full_AF_NEW GPO File System Path: \\francois.int\sysvol\francois.int\Policies\{25374D65-7C82-4D33-B569-C99DAF6618AE}\Machine Script Name: \\francois.int\it-tools\GPO\Install\Teamviewer\V15.20.6\AF\Full.bat ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The User Energy Server Service queencreek service terminated with the following error: Driver %2 returned invalid ID for a child device (55005300450052005F0045005300520056005F005300560043005F0051005500450045004E0043005200450045004B000000). ------------------------------------------------------------------- The OpenSSH SSH Server service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the igfxCUIService2.0.0.0 service. ------------------------------------------------------------------- A CredSSP authentication to TERMSRV/AFEXDW16-DC01.extern.francois.int failed to negotiate a common protocol version. The remote host offered version 4 which is not permitted by Encryption Oracle Remediation. See https://go.microsoft.com/fwlink/?linkid=866660 for more information. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- A fatal error occurred while creating a TLS client credential. The internal error state is 10013. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- A fatal error occurred while creating a TLS client credential. The internal error state is 10013. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- A fatal error occurred while creating a TLS client credential. The internal error state is 10013. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- A CredSSP authentication to TERMSRV/AFEXDW16-DC01.extern.francois.int failed to negotiate a common protocol version. The remote host offered version 4 which is not permitted by Encryption Oracle Remediation. See https://go.microsoft.com/fwlink/?linkid=866660 for more information. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The Lenovo Hotkey Client Loader service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- A CredSSP authentication to TERMSRV/AFEXDW16-DC01.extern.francois.int failed to negotiate a common protocol version. The remote host offered version 4 which is not permitted by Encryption Oracle Remediation. See https://go.microsoft.com/fwlink/?linkid=866660 for more information. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Start-up script failed. GPO Name: Sophos_Install GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{AFC88A2F-95CE-45B4-B2E6-64666E7E1CC8}\Machine Script Name: \\francois.int\NETLOGON\Sophos.bat ------------------------------------------------------------------- Start-up script failed. GPO Name: Install_Insight_Discovery_Update GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{F8826B94-387A-4C26-88B5-33F427E144E2}\Machine Script Name: \\francois.int\it-tools\GPO\Scripts\Insight_update.ps1 ------------------------------------------------------------------- Start-up script failed. GPO Name: Teamviewer_15_Full_AF_NEW GPO File System Path: \\francois.int\sysvol\francois.int\Policies\{25374D65-7C82-4D33-B569-C99DAF6618AE}\Machine Script Name: \\francois.int\it-tools\GPO\Install\Teamviewer\V15.20.6\AF\Full.bat ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The OpenSSH SSH Server service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The Group Policy Client service did not shut down properly after receiving a pre-shutdown control. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Start-up script failed. GPO Name: Sophos_Install GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{AFC88A2F-95CE-45B4-B2E6-64666E7E1CC8}\Machine Script Name: \\francois.int\NETLOGON\Sophos.bat ------------------------------------------------------------------- Start-up script failed. GPO Name: Install_Insight_Discovery_Update GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{F8826B94-387A-4C26-88B5-33F427E144E2}\Machine Script Name: \\francois.int\it-tools\GPO\Scripts\Insight_update.ps1 ------------------------------------------------------------------- Start-up script failed. GPO Name: Teamviewer_15_Full_AF_NEW GPO File System Path: \\francois.int\sysvol\francois.int\Policies\{25374D65-7C82-4D33-B569-C99DAF6618AE}\Machine Script Name: \\francois.int\it-tools\GPO\Install\Teamviewer\V15.20.6\AF\Full.bat ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The OpenSSH SSH Server service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the igfxCUIService2.0.0.0 service. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- A fatal error occurred while creating a TLS client credential. The internal error state is 10013. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Start-up script failed. GPO Name: Sophos_Install GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{AFC88A2F-95CE-45B4-B2E6-64666E7E1CC8}\Machine Script Name: \\francois.int\NETLOGON\Sophos.bat ------------------------------------------------------------------- Start-up script failed. GPO Name: Install_Insight_Discovery_Update GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{F8826B94-387A-4C26-88B5-33F427E144E2}\Machine Script Name: \\francois.int\it-tools\GPO\Scripts\Insight_update.ps1 ------------------------------------------------------------------- Start-up script failed. GPO Name: Teamviewer_15_Full_AF_NEW GPO File System Path: \\francois.int\sysvol\francois.int\Policies\{25374D65-7C82-4D33-B569-C99DAF6618AE}\Machine Script Name: \\francois.int\it-tools\GPO\Install\Teamviewer\V15.20.6\AF\Full.bat ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The Windows Time service terminated with the following error: A system shutdown is in progress. ------------------------------------------------------------------- The time service encountered an error and was forced to shut down. The error was: 0x8007045B: A system shutdown is in progress. ------------------------------------------------------------------- The OpenSSH SSH Server service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The User Energy Server Service queencreek service terminated with the following error: Driver %2 returned invalid ID for a child device (55005300450052005F0045005300520056005F005300560043005F0051005500450045004E0043005200450045004B000000). ------------------------------------------------------------------- The OpenSSH SSH Server service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The Windows Modules Installer service terminated with the following error: The process cannot access the file because it is being used by another process. ------------------------------------------------------------------- A fatal error occurred while creating a TLS client credential. The internal error state is 10013. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The server {2387FADA-8CE7-42C6-BB56-854FBE8BFEA7} did not register with DCOM within the required timeout. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- A CredSSP authentication to TERMSRV/AFEXDW16-DC01.extern.francois.int failed to negotiate a common protocol version. The remote host offered version 4 which is not permitted by Encryption Oracle Remediation. See https://go.microsoft.com/fwlink/?linkid=866660 for more information. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The OpenSSH SSH Server service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server {2387FADA-8CE7-42C6-BB56-854FBE8BFEA7} did not register with DCOM within the required timeout. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the igfxCUIService2.0.0.0 service. ------------------------------------------------------------------- The server {2387FADA-8CE7-42C6-BB56-854FBE8BFEA7} did not register with DCOM within the required timeout. ------------------------------------------------------------------- A fatal error occurred while creating a TLS client credential. The internal error state is 10013. ------------------------------------------------------------------- Bootmgr failed to obtain the BitLocker volume master key from the TPM. ------------------------------------------------------------------- Bootmgr failed to unseal VMK using the TPM ------------------------------------------------------------------- The Windows Time service terminated with the following error: A system shutdown is in progress. ------------------------------------------------------------------- The time service encountered an error and was forced to shut down. The error was: 0x8007045B: A system shutdown is in progress. ------------------------------------------------------------------- Bootmgr failed to obtain the BitLocker volume master key from the TPM. ------------------------------------------------------------------- Bootmgr failed to unseal VMK using the TPM ------------------------------------------------------------------- The previous system shutdown at 10:04:21 on ‎09/‎12/‎2021 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- A CredSSP authentication to TERMSRV/AFEXDW16-DC01.extern.francois.int failed to negotiate a common protocol version. The remote host offered version 4 which is not permitted by Encryption Oracle Remediation. See https://go.microsoft.com/fwlink/?linkid=866660 for more information. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 16:26:09 on ‎08/‎12/‎2021 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Start-up script failed. GPO Name: Sophos_Install GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{AFC88A2F-95CE-45B4-B2E6-64666E7E1CC8}\Machine Script Name: \\francois.int\NETLOGON\Sophos.bat ------------------------------------------------------------------- Start-up script failed. GPO Name: Install_Insight_Discovery_Update GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{F8826B94-387A-4C26-88B5-33F427E144E2}\Machine Script Name: \\francois.int\it-tools\GPO\Scripts\Insight_update.ps1 ------------------------------------------------------------------- Start-up script failed. GPO Name: Teamviewer_15_Full_AF_NEW GPO File System Path: \\francois.int\sysvol\francois.int\Policies\{25374D65-7C82-4D33-B569-C99DAF6618AE}\Machine Script Name: \\francois.int\it-tools\GPO\Install\Teamviewer\V15.20.6\AF\Full.bat ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 16:53:55 on ‎02/‎12/‎2021 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Lenovo Hotkey Client Loader service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {D085A4AB-CAB1-4729-9DF8-FCEEDDBD19E4} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Unable to bind to the underlying transport for [::]:50128. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine. The data field contains the error number. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Start-up script failed. GPO Name: Sophos_Install GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{AFC88A2F-95CE-45B4-B2E6-64666E7E1CC8}\Machine Script Name: \\francois.int\NETLOGON\Sophos.bat ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 20:22:44 on ‎23/‎11/‎2021 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The Lenovo Hotkey Client Loader service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- Intel(R) Wi-Fi 6 AX201 160MHz : Has encountered an internal error and has failed. ------------------------------------------------------------------- Intel(R) Wi-Fi 6 AX201 160MHz : Has determined that the network adapter is not functioning properly. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The server {2387FADA-8CE7-42C6-BB56-854FBE8BFEA7} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a02:2788:104:4f7::8 with the system having network hardware address 00-11-32-3B-A9-ED. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Start-up script failed. GPO Name: Sophos_Install GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{AFC88A2F-95CE-45B4-B2E6-64666E7E1CC8}\Machine Script Name: \\francois.int\NETLOGON\Sophos.bat ------------------------------------------------------------------- Start-up script failed. GPO Name: Install_Insight_Discovery_Update GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{F8826B94-387A-4C26-88B5-33F427E144E2}\Machine Script Name: \\francois.int\it-tools\GPO\Scripts\Insight_update.ps1 ------------------------------------------------------------------- Start-up script failed. GPO Name: Teamviewer_15_Full_AF_NEW GPO File System Path: \\francois.int\sysvol\francois.int\Policies\{25374D65-7C82-4D33-B569-C99DAF6618AE}\Machine Script Name: \\francois.int\it-tools\GPO\Install\Teamviewer\V15.20.6\AF\Full.bat ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The previous system shutdown at 16:50:39 on ‎19/‎11/‎2021 was unexpected. ------------------------------------------------------------------- The Group Policy Client service did not shut down properly after receiving a pre-shutdown control. ------------------------------------------------------------------- The server {2387FADA-8CE7-42C6-BB56-854FBE8BFEA7} did not register with DCOM within the required timeout. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The server windows.immersivecontrolpanel_10.0.2.1000_neutral_neutral_cw5n1h2txyewy!microsoft.windows.immersivecontrolpanel did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {B9B05098-3E30-483F-87F7-027CA78DA287} did not register with DCOM within the required timeout. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The server {2387FADA-8CE7-42C6-BB56-854FBE8BFEA7} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Start-up script failed. GPO Name: Sophos_Install GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{AFC88A2F-95CE-45B4-B2E6-64666E7E1CC8}\Machine Script Name: \\francois.int\NETLOGON\Sophos.bat ------------------------------------------------------------------- Start-up script failed. GPO Name: Install_Insight_Discovery_Update GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{F8826B94-387A-4C26-88B5-33F427E144E2}\Machine Script Name: \\francois.int\it-tools\GPO\Scripts\Insight_update.ps1 ------------------------------------------------------------------- Start-up script failed. GPO Name: Teamviewer_15_Full_AF_NEW GPO File System Path: \\francois.int\sysvol\francois.int\Policies\{25374D65-7C82-4D33-B569-C99DAF6618AE}\Machine Script Name: \\francois.int\it-tools\GPO\Install\Teamviewer\V15.20.6\AF\Full.bat ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 16:40:37 on ‎18/‎11/‎2021 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- Start-up script failed. GPO Name: Sophos_Install GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{AFC88A2F-95CE-45B4-B2E6-64666E7E1CC8}\Machine Script Name: \\francois.int\NETLOGON\Sophos.bat ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 17:11:03 on ‎17/‎11/‎2021 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Start-up script failed. GPO Name: Sophos_Install GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{AFC88A2F-95CE-45B4-B2E6-64666E7E1CC8}\Machine Script Name: \\francois.int\NETLOGON\Sophos.bat ------------------------------------------------------------------- Start-up script failed. GPO Name: Install_Insight_Discovery_Update GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{F8826B94-387A-4C26-88B5-33F427E144E2}\Machine Script Name: \\francois.int\it-tools\GPO\Scripts\Insight_update.ps1 ------------------------------------------------------------------- Start-up script failed. GPO Name: Teamviewer_15_Full_AF_NEW GPO File System Path: \\francois.int\sysvol\francois.int\Policies\{25374D65-7C82-4D33-B569-C99DAF6618AE}\Machine Script Name: \\francois.int\it-tools\GPO\Install\Teamviewer\V15.20.6\AF\Full.bat ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The Windows Time service terminated with the following error: A system shutdown is in progress. ------------------------------------------------------------------- The time service encountered an error and was forced to shut down. The error was: 0x8007045B: A system shutdown is in progress. ------------------------------------------------------------------- The Remote Access Connection Manager service terminated with the following service-specific error: {Virtual Memory Minimum Too Low} Your system is low on virtual memory. Windows is increasing the size of your virtual memory paging file. During this process, memory requests for some applications may be denied. For more information, see Help. ------------------------------------------------------------------- Remote Access Connection Manager failed to start because it could not load one or more communication DLLs. Ensure that your communication hardware is installed and then restart the Remote Access Connection Manager service. If the problem persists, contact the system administrator. There was an unknown error. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 16:57:58 on ‎16/‎11/‎2021 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Start-up script failed. GPO Name: Sophos_Install GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{AFC88A2F-95CE-45B4-B2E6-64666E7E1CC8}\Machine Script Name: \\francois.int\NETLOGON\Sophos.bat ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 16:25:09 on ‎15/‎11/‎2021 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Start-up script failed. GPO Name: Sophos_Install GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{AFC88A2F-95CE-45B4-B2E6-64666E7E1CC8}\Machine Script Name: \\francois.int\NETLOGON\Sophos.bat ------------------------------------------------------------------- Start-up script failed. GPO Name: Install_Insight_Discovery_Update GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{F8826B94-387A-4C26-88B5-33F427E144E2}\Machine Script Name: \\francois.int\it-tools\GPO\Scripts\Insight_update.ps1 ------------------------------------------------------------------- Start-up script failed. GPO Name: Teamviewer_15_Full_AF_NEW GPO File System Path: \\francois.int\sysvol\francois.int\Policies\{25374D65-7C82-4D33-B569-C99DAF6618AE}\Machine Script Name: \\francois.int\it-tools\GPO\Install\Teamviewer\V15.20.6\AF\Full.bat ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 16:54:35 on ‎09/‎11/‎2021 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Start-up script failed. GPO Name: Sophos_Install GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{AFC88A2F-95CE-45B4-B2E6-64666E7E1CC8}\Machine Script Name: \\francois.int\NETLOGON\Sophos.bat ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The OpenSSH SSH Server service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Smart Card Reader 'Alcor Micro USB Smart Card Reader 0' rejected IOCTL 0x313520: Incorrect function. If this error persists, your smart card or reader may not be functioning correctly. Command Header: XX XX XX XX ------------------------------------------------------------------- Start-up script failed. GPO Name: Sophos_Install GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{AFC88A2F-95CE-45B4-B2E6-64666E7E1CC8}\Machine Script Name: \\francois.int\NETLOGON\Sophos.bat ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 16:36:16 on ‎08/‎11/‎2021 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- Start-up script failed. GPO Name: Sophos_Install GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{AFC88A2F-95CE-45B4-B2E6-64666E7E1CC8}\Machine Script Name: \\francois.int\NETLOGON\Sophos.bat ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The User Energy Server Service queencreek service terminated with the following error: Driver %2 returned invalid ID for a child device (55005300450052005F0045005300520056005F005300560043005F0051005500450045004E0043005200450045004B000000). ------------------------------------------------------------------- The OpenSSH SSH Server service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The Group Policy Client service did not shut down properly after receiving a pre-shutdown control. ------------------------------------------------------------------- The server {2387FADA-8CE7-42C6-BB56-854FBE8BFEA7} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Start-up script failed. GPO Name: Sophos_Install GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{AFC88A2F-95CE-45B4-B2E6-64666E7E1CC8}\Machine Script Name: \\francois.int\NETLOGON\Sophos.bat ------------------------------------------------------------------- Start-up script failed. GPO Name: Install_Insight_Discovery_Update GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{F8826B94-387A-4C26-88B5-33F427E144E2}\Machine Script Name: \\francois.int\it-tools\GPO\Scripts\Insight_update.ps1 ------------------------------------------------------------------- Start-up script failed. GPO Name: Teamviewer_15_Full_AF_NEW GPO File System Path: \\francois.int\sysvol\francois.int\Policies\{25374D65-7C82-4D33-B569-C99DAF6618AE}\Machine Script Name: \\francois.int\it-tools\GPO\Install\Teamviewer\V15.20.6\AF\Full.bat ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 17:03:47 on ‎04/‎11/‎2021 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- Start-up script failed. GPO Name: Sophos_Install GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{AFC88A2F-95CE-45B4-B2E6-64666E7E1CC8}\Machine Script Name: \\francois.int\NETLOGON\Sophos.bat ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 13:41:09 on ‎04/‎11/‎2021 was unexpected. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not obtain the name of a domain controller. This could be caused by a name resolution failure. Verify your Domain Name System (DNS) is configured and working correctly. ------------------------------------------------------------------- The processing of Group Policy failed. Windows attempted to read the file \\francois.int\SysVol\francois.int\Policies\{9C3C097E-BD1C-467C-A2E4-10F1F3CACD18}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following: a) Name Resolution/Network Connectivity to the current domain controller. b) File Replication Service Latency (a file created on another domain controller has not replicated to the current domain controller). c) The Distributed File System (DFS) client has been disabled. ------------------------------------------------------------------- The processing of Group Policy failed. Windows attempted to read the file \\francois.int\SysVol\francois.int\Policies\{02F67119-8986-4AA7-895E-279197E7495F}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following: a) Name Resolution/Network Connectivity to the current domain controller. b) File Replication Service Latency (a file created on another domain controller has not replicated to the current domain controller). c) The Distributed File System (DFS) client has been disabled. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Start-up script failed. GPO Name: Sophos_Install GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{AFC88A2F-95CE-45B4-B2E6-64666E7E1CC8}\Machine Script Name: \\francois.int\NETLOGON\Sophos.bat ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 16:54:51 on ‎03/‎11/‎2021 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Start-up script failed. GPO Name: Sophos_Install GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{AFC88A2F-95CE-45B4-B2E6-64666E7E1CC8}\Machine Script Name: \\francois.int\NETLOGON\Sophos.bat ------------------------------------------------------------------- Start-up script failed. GPO Name: Install_Insight_Discovery_Update GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{F8826B94-387A-4C26-88B5-33F427E144E2}\Machine Script Name: \\francois.int\it-tools\GPO\Scripts\Insight_update.ps1 ------------------------------------------------------------------- Start-up script failed. GPO Name: Teamviewer_15_Full_AF_NEW GPO File System Path: \\francois.int\sysvol\francois.int\Policies\{25374D65-7C82-4D33-B569-C99DAF6618AE}\Machine Script Name: \\francois.int\it-tools\GPO\Install\Teamviewer\V15.20.6\AF\Full.bat ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The User Energy Server Service queencreek service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The server {2387FADA-8CE7-42C6-BB56-854FBE8BFEA7} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- Start-up script failed. GPO Name: Sophos_Install GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{AFC88A2F-95CE-45B4-B2E6-64666E7E1CC8}\Machine Script Name: \\francois.int\NETLOGON\Sophos.bat ------------------------------------------------------------------- Start-up script failed. GPO Name: Install_Insight_Discovery_Update GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{F8826B94-387A-4C26-88B5-33F427E144E2}\Machine Script Name: \\francois.int\it-tools\GPO\Scripts\Insight_update.ps1 ------------------------------------------------------------------- Start-up script failed. GPO Name: Teamviewer_15_Full_AF_NEW GPO File System Path: \\francois.int\sysvol\francois.int\Policies\{25374D65-7C82-4D33-B569-C99DAF6618AE}\Machine Script Name: \\francois.int\it-tools\GPO\Install\Teamviewer\V15.20.6\AF\Full.bat ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The OpenSSH SSH Server service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Start-up script failed. GPO Name: Sophos_Install GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{AFC88A2F-95CE-45B4-B2E6-64666E7E1CC8}\Machine Script Name: \\francois.int\NETLOGON\Sophos.bat ------------------------------------------------------------------- Start-up script failed. GPO Name: Install_Insight_Discovery_Update GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{F8826B94-387A-4C26-88B5-33F427E144E2}\Machine Script Name: \\francois.int\it-tools\GPO\Scripts\Insight_update.ps1 ------------------------------------------------------------------- Start-up script failed. GPO Name: Teamviewer_15_Full_AF_NEW GPO File System Path: \\francois.int\sysvol\francois.int\Policies\{25374D65-7C82-4D33-B569-C99DAF6618AE}\Machine Script Name: \\francois.int\it-tools\GPO\Install\Teamviewer\V15.20.6\AF\Full.bat ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a02:2788:104:4f7::3 with the system having network hardware address F0-2F-74-30-DC-01. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 14:00:22 on ‎26/‎10/‎2021 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Windows Audio service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Start-up script failed. GPO Name: Sophos_Install GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{AFC88A2F-95CE-45B4-B2E6-64666E7E1CC8}\Machine Script Name: \\francois.int\NETLOGON\Sophos.bat ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 16:57:30 on ‎25/‎10/‎2021 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- A CredSSP authentication to TERMSRV/AFDW16-DA02.francois.int failed to negotiate a common protocol version. The remote host offered version 4 which is not permitted by Encryption Oracle Remediation. See https://go.microsoft.com/fwlink/?linkid=866660 for more information. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a02:2788:104:4f7::1 with the system having network hardware address F0-2F-74-30-DC-01. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.People_10.2105.4.0_x64__8wekyb3d8bbwe!x4c7a3b7dy2188y46d4ya362y19ac5a5805e5x.AppXv1pa150fssxfwf8qn0j65z3gp1qhwkcs.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Start-up script failed. GPO Name: Sophos_Install GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{AFC88A2F-95CE-45B4-B2E6-64666E7E1CC8}\Machine Script Name: \\francois.int\NETLOGON\Sophos.bat ------------------------------------------------------------------- Start-up script failed. GPO Name: Install_Insight_Discovery_Update GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{F8826B94-387A-4C26-88B5-33F427E144E2}\Machine Script Name: \\francois.int\it-tools\GPO\Scripts\Insight_update.ps1 ------------------------------------------------------------------- Start-up script failed. GPO Name: Teamviewer_15_Full_AF_NEW GPO File System Path: \\francois.int\sysvol\francois.int\Policies\{25374D65-7C82-4D33-B569-C99DAF6618AE}\Machine Script Name: \\francois.int\it-tools\GPO\Install\Teamviewer\V15.20.6\AF\Full.bat ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 16:40:58 on ‎21/‎10/‎2021 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- Start-up script failed. GPO Name: Sophos_Install GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{AFC88A2F-95CE-45B4-B2E6-64666E7E1CC8}\Machine Script Name: \\francois.int\NETLOGON\Sophos.bat ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 16:46:01 on ‎20/‎10/‎2021 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- A CredSSP authentication to TERMSRV/AFEXDW16-DC01.extern.francois.int failed to negotiate a common protocol version. The remote host offered version 4 which is not permitted by Encryption Oracle Remediation. See https://go.microsoft.com/fwlink/?linkid=866660 for more information. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The server {2387FADA-8CE7-42C6-BB56-854FBE8BFEA7} did not register with DCOM within the required timeout. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- The Lenovo Hotkey Client Loader service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {2387FADA-8CE7-42C6-BB56-854FBE8BFEA7} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Start-up script failed. GPO Name: Sophos_Install GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{AFC88A2F-95CE-45B4-B2E6-64666E7E1CC8}\Machine Script Name: \\francois.int\NETLOGON\Sophos.bat ------------------------------------------------------------------- Start-up script failed. GPO Name: Install_Insight_Discovery_Update GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{F8826B94-387A-4C26-88B5-33F427E144E2}\Machine Script Name: \\francois.int\it-tools\GPO\Scripts\Insight_update.ps1 ------------------------------------------------------------------- Start-up script failed. GPO Name: Teamviewer_15_Full_AF_NEW GPO File System Path: \\francois.int\sysvol\francois.int\Policies\{25374D65-7C82-4D33-B569-C99DAF6618AE}\Machine Script Name: \\francois.int\it-tools\GPO\Install\Teamviewer\V15.20.6\AF\Full.bat ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The OpenSSH SSH Server service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The Group Policy Client service did not shut down properly after receiving a pre-shutdown control. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The User Energy Server Service queencreek service terminated with the following error: Driver %2 returned invalid ID for a child device (55005300450052005F0045005300520056005F005300560043005F0051005500450045004E0043005200450045004B000000). ------------------------------------------------------------------- The OpenSSH SSH Server service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Start-up script failed. GPO Name: Sophos_Install GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{AFC88A2F-95CE-45B4-B2E6-64666E7E1CC8}\Machine Script Name: \\francois.int\NETLOGON\Sophos.bat ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The OpenSSH SSH Server service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Start-up script failed. GPO Name: Sophos_Install GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{AFC88A2F-95CE-45B4-B2E6-64666E7E1CC8}\Machine Script Name: \\francois.int\NETLOGON\Sophos.bat ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The OpenSSH SSH Server service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- Start-up script failed. GPO Name: Sophos_Install GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{AFC88A2F-95CE-45B4-B2E6-64666E7E1CC8}\Machine Script Name: \\francois.int\NETLOGON\Sophos.bat ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The OpenSSH SSH Server service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- DCOM was unable to communicate with the computer hqdbsp18 using any of the configured protocols; requested by PID 49f4 (C:\Windows\system32\WindowsPowerShell\v1.0\PowerShell_ISE.exe), while activating CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820}. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- Start-up script failed. GPO Name: Sophos_Install GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{AFC88A2F-95CE-45B4-B2E6-64666E7E1CC8}\Machine Script Name: \\francois.int\NETLOGON\Sophos.bat ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 17:04:31 on ‎11/‎10/‎2021 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Start-up script failed. GPO Name: Sophos_Install GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{AFC88A2F-95CE-45B4-B2E6-64666E7E1CC8}\Machine Script Name: \\francois.int\NETLOGON\Sophos.bat ------------------------------------------------------------------- Start-up script failed. GPO Name: Install_Insight_Discovery_Update GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{F8826B94-387A-4C26-88B5-33F427E144E2}\Machine Script Name: \\francois.int\it-tools\GPO\Scripts\Insight_update.ps1 ------------------------------------------------------------------- Start-up script failed. GPO Name: Teamviewer_15_Full_AF_NEW GPO File System Path: \\francois.int\sysvol\francois.int\Policies\{25374D65-7C82-4D33-B569-C99DAF6618AE}\Machine Script Name: \\francois.int\it-tools\GPO\Install\Teamviewer\V15.20.6\AF\Full.bat ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The previous system shutdown at 08:41:24 on ‎08/‎10/‎2021 was unexpected. ------------------------------------------------------------------- The OpenSSH SSH Server service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The User Energy Server Service queencreek service terminated with the following error: Driver %2 returned invalid ID for a child device (55005300450052005F0045005300520056005F005300560043005F0051005500450045004E0043005200450045004B000000). ------------------------------------------------------------------- The Windows Security Service service did not shut down properly after receiving a pre-shutdown control. ------------------------------------------------------------------- The Group Policy Client service did not shut down properly after receiving a pre-shutdown control. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Start-up script failed. GPO Name: Sophos_Install GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{AFC88A2F-95CE-45B4-B2E6-64666E7E1CC8}\Machine Script Name: \\francois.int\NETLOGON\Sophos.bat ------------------------------------------------------------------- Start-up script failed. GPO Name: Install_Insight_Discovery_Update GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{F8826B94-387A-4C26-88B5-33F427E144E2}\Machine Script Name: \\francois.int\it-tools\GPO\Scripts\Insight_update.ps1 ------------------------------------------------------------------- Start-up script failed. GPO Name: Teamviewer_15_Full_AF_NEW GPO File System Path: \\francois.int\sysvol\francois.int\Policies\{25374D65-7C82-4D33-B569-C99DAF6618AE}\Machine Script Name: \\francois.int\it-tools\GPO\Install\Teamviewer\V15.20.6\AF\Full.bat ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 16:41:39 on ‎07/‎10/‎2021 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\jcs-admin SID (S-1-5-21-2088451773-641421298-666385194-11491) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\jcs-admin SID (S-1-5-21-2088451773-641421298-666385194-11491) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\jcs-admin SID (S-1-5-21-2088451773-641421298-666385194-11491) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\jcs-admin SID (S-1-5-21-2088451773-641421298-666385194-11491) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- Start-up script failed. GPO Name: Sophos_Install GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{AFC88A2F-95CE-45B4-B2E6-64666E7E1CC8}\Machine Script Name: \\francois.int\NETLOGON\Sophos.bat ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 17:10:30 on ‎06/‎10/‎2021 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- The Windows Audio service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- A CredSSP authentication to TERMSRV/AFEXDW16-DC01.extern.francois.int failed to negotiate a common protocol version. The remote host offered version 4 which is not permitted by Encryption Oracle Remediation. See https://go.microsoft.com/fwlink/?linkid=866660 for more information. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not obtain the name of a domain controller. This could be caused by a name resolution failure. Verify your Domain Name System (DNS) is configured and working correctly. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Start-up script failed. GPO Name: Sophos_Install GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{AFC88A2F-95CE-45B4-B2E6-64666E7E1CC8}\Machine Script Name: \\francois.int\NETLOGON\Sophos.bat ------------------------------------------------------------------- Start-up script failed. GPO Name: Install_Insight_Discovery_Update GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{F8826B94-387A-4C26-88B5-33F427E144E2}\Machine Script Name: \\francois.int\it-tools\GPO\Scripts\Insight_update.ps1 ------------------------------------------------------------------- Start-up script failed. GPO Name: Teamviewer_15_Full_AF_NEW GPO File System Path: \\francois.int\sysvol\francois.int\Policies\{25374D65-7C82-4D33-B569-C99DAF6618AE}\Machine Script Name: \\francois.int\it-tools\GPO\Install\Teamviewer\V15.20.6\AF\Full.bat ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 16:21:19 on ‎30/‎09/‎2021 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.22 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.22 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.150.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- Start-up script failed. GPO Name: Sophos_Install GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{AFC88A2F-95CE-45B4-B2E6-64666E7E1CC8}\Machine Script Name: \\francois.int\NETLOGON\Sophos.bat ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The OpenSSH SSH Server service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {2387FADA-8CE7-42C6-BB56-854FBE8BFEA7} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- Start-up script failed. GPO Name: Sophos_Install GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{AFC88A2F-95CE-45B4-B2E6-64666E7E1CC8}\Machine Script Name: \\francois.int\NETLOGON\Sophos.bat ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 17:19:38 on ‎29/‎09/‎2021 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Start-up script failed. GPO Name: Sophos_Install GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{AFC88A2F-95CE-45B4-B2E6-64666E7E1CC8}\Machine Script Name: \\francois.int\NETLOGON\Sophos.bat ------------------------------------------------------------------- Start-up script failed. GPO Name: Install_Insight_Discovery_Update GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{F8826B94-387A-4C26-88B5-33F427E144E2}\Machine Script Name: \\francois.int\it-tools\GPO\Scripts\Insight_update.ps1 ------------------------------------------------------------------- Start-up script failed. GPO Name: Teamviewer_15_Full_AF_NEW GPO File System Path: \\francois.int\sysvol\francois.int\Policies\{25374D65-7C82-4D33-B569-C99DAF6618AE}\Machine Script Name: \\francois.int\it-tools\GPO\Install\Teamviewer\V15.20.6\AF\Full.bat ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The OpenSSH SSH Server service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- Start-up script failed. GPO Name: Sophos_Install GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{AFC88A2F-95CE-45B4-B2E6-64666E7E1CC8}\Machine Script Name: \\francois.int\NETLOGON\Sophos.bat ------------------------------------------------------------------- Start-up script failed. GPO Name: Install_Insight_Discovery_Update GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{F8826B94-387A-4C26-88B5-33F427E144E2}\Machine Script Name: \\francois.int\it-tools\GPO\Scripts\Insight_update.ps1 ------------------------------------------------------------------- Start-up script failed. GPO Name: Teamviewer_15_Full_AF_NEW GPO File System Path: \\francois.int\sysvol\francois.int\Policies\{25374D65-7C82-4D33-B569-C99DAF6618AE}\Machine Script Name: \\francois.int\it-tools\GPO\Install\Teamviewer\V15.20.6\AF\Full.bat ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 16:53:37 on ‎28/‎09/‎2021 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- Start-up script failed. GPO Name: Sophos_Install GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{AFC88A2F-95CE-45B4-B2E6-64666E7E1CC8}\Machine Script Name: \\francois.int\NETLOGON\Sophos.bat ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 09:30:26 on ‎28/‎09/‎2021 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The OpenSSH SSH Server service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed. Windows attempted to read the file \\francois.int\SysVol\francois.int\Policies\{993B581D-0267-4AB1-862B-F0F94C4A8396}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following: a) Name Resolution/Network Connectivity to the current domain controller. b) File Replication Service Latency (a file created on another domain controller has not replicated to the current domain controller). c) The Distributed File System (DFS) client has been disabled. ------------------------------------------------------------------- Start-up script failed. GPO Name: Sophos_Install GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{AFC88A2F-95CE-45B4-B2E6-64666E7E1CC8}\Machine Script Name: \\francois.int\NETLOGON\Sophos.bat ------------------------------------------------------------------- Start-up script failed. GPO Name: Install_Insight_Discovery_Update GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{F8826B94-387A-4C26-88B5-33F427E144E2}\Machine Script Name: \\francois.int\it-tools\GPO\Scripts\Insight_update.ps1 ------------------------------------------------------------------- The processing of Group Policy failed. Windows attempted to read the file \\francois.int\sysvol\francois.int\Policies\{B65C6486-0798-4B69-9C97-1BD7FE16BDD3}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following: a) Name Resolution/Network Connectivity to the current domain controller. b) File Replication Service Latency (a file created on another domain controller has not replicated to the current domain controller). c) The Distributed File System (DFS) client has been disabled. ------------------------------------------------------------------- The OpenSSH SSH Server service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed. Windows attempted to read the file \\francois.int\SysVol\francois.int\Policies\{993B581D-0267-4AB1-862B-F0F94C4A8396}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following: a) Name Resolution/Network Connectivity to the current domain controller. b) File Replication Service Latency (a file created on another domain controller has not replicated to the current domain controller). c) The Distributed File System (DFS) client has been disabled. ------------------------------------------------------------------- Start-up script failed. GPO Name: Sophos_Install GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{AFC88A2F-95CE-45B4-B2E6-64666E7E1CC8}\Machine Script Name: \\francois.int\NETLOGON\Sophos.bat ------------------------------------------------------------------- Start-up script failed. GPO Name: Install_Insight_Discovery_Update GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{F8826B94-387A-4C26-88B5-33F427E144E2}\Machine Script Name: \\francois.int\it-tools\GPO\Scripts\Insight_update.ps1 ------------------------------------------------------------------- The processing of Group Policy failed. Windows attempted to read the file \\francois.int\sysvol\francois.int\Policies\{B65C6486-0798-4B69-9C97-1BD7FE16BDD3}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following: a) Name Resolution/Network Connectivity to the current domain controller. b) File Replication Service Latency (a file created on another domain controller has not replicated to the current domain controller). c) The Distributed File System (DFS) client has been disabled. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 16:10:59 on ‎24/‎09/‎2021 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user AFBO\Sophos_STAS SID (S-1-5-21-2628012577-1381500490-1340114306-1397) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user AFBO\Sophos_STAS SID (S-1-5-21-2628012577-1381500490-1340114306-1397) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user AFBO\Sophos_STAS SID (S-1-5-21-2628012577-1381500490-1340114306-1397) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user AFBO\Sophos_STAS SID (S-1-5-21-2628012577-1381500490-1340114306-1397) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user AFBO\Sophos_STAS SID (S-1-5-21-2628012577-1381500490-1340114306-1397) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user AFBO\Sophos_STAS SID (S-1-5-21-2628012577-1381500490-1340114306-1397) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user AFBO\Sophos_STAS SID (S-1-5-21-2628012577-1381500490-1340114306-1397) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user AFBO\Sophos_STAS SID (S-1-5-21-2628012577-1381500490-1340114306-1397) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user AFBO\Sophos_STAS SID (S-1-5-21-2628012577-1381500490-1340114306-1397) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user AFBO\Sophos_STAS SID (S-1-5-21-2628012577-1381500490-1340114306-1397) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user AFBO\Sophos_STAS SID (S-1-5-21-2628012577-1381500490-1340114306-1397) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user AFBO\Sophos_STAS SID (S-1-5-21-2628012577-1381500490-1340114306-1397) from address 192.168.203.10 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The Intel(R) Audio Service service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The Lenovo Hotkey Client Loader service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {2387FADA-8CE7-42C6-BB56-854FBE8BFEA7} did not register with DCOM within the required timeout. ------------------------------------------------------------------- A CredSSP authentication to TERMSRV/AFEXDW16-DC01.extern.francois.int failed to negotiate a common protocol version. The remote host offered version 4 which is not permitted by Encryption Oracle Remediation. See https://go.microsoft.com/fwlink/?linkid=866660 for more information. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The server {2387FADA-8CE7-42C6-BB56-854FBE8BFEA7} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The server-side authentication level policy does not allow the user FRANCOIS\Sophos_STAS SID (S-1-5-21-2088451773-641421298-666385194-11870) from address 192.168.10.21 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Start-up script failed. GPO Name: Sophos_Install GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{AFC88A2F-95CE-45B4-B2E6-64666E7E1CC8}\Machine Script Name: \\francois.int\NETLOGON\Sophos.bat ------------------------------------------------------------------- Start-up script failed. GPO Name: Install_Insight_Discovery_Update GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{F8826B94-387A-4C26-88B5-33F427E144E2}\Machine Script Name: \\francois.int\it-tools\GPO\Scripts\Insight_update.ps1 ------------------------------------------------------------------- Start-up script failed. GPO Name: Teamviewer_15_Full_AF_NEW GPO File System Path: \\francois.int\sysvol\francois.int\Policies\{25374D65-7C82-4D33-B569-C99DAF6618AE}\Machine Script Name: \\francois.int\it-tools\GPO\Install\Teamviewer\V15.20.6\AF\Full.bat ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The OpenSSH SSH Server service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The Windows Biometric Service service did not shut down properly after receiving a pre-shutdown control. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The User Energy Server Service queencreek service terminated with the following error: Driver %2 returned invalid ID for a child device (55005300450052005F0045005300520056005F005300560043005F0051005500450045004E0043005200450045004B000000). ------------------------------------------------------------------- The OpenSSH SSH Server service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The Windows Modules Installer service terminated with the following error: Illegal operation attempted on a registry key that has been marked for deletion. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server microsoft.windowscommunicationsapps_16005.14326.20206.0_x64__8wekyb3d8bbwe!microsoft.windowslive.calendar.AppXwkn9j84yh1kvnt49k5r8h6y1ecsv09hs.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- The server {2387FADA-8CE7-42C6-BB56-854FBE8BFEA7} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IO operation at logical block address 0x6000 for Disk 1 (PDO name: \Device\00000162) failed due to a hardware error. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {2387FADA-8CE7-42C6-BB56-854FBE8BFEA7} did not register with DCOM within the required timeout. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- Unexpected failure. Error code: 1B1@01010013 ------------------------------------------------------------------- The server {D2B7A809-15DC-40B4-A1E1-C61EA97191DB} did not register with DCOM within the required timeout. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The User Energy Server Service queencreek service terminated with the following error: Driver %2 returned invalid ID for a child device (55005300450052005F0045005300520056005F005300560043005F0051005500450045004E0043005200450045004B000000). ------------------------------------------------------------------- The OpenSSH SSH Server service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- Unexpected failure. Error code: 1B1@01010013 ------------------------------------------------------------------- Unexpected failure. Error code: 1B1@01010013 ------------------------------------------------------------------- Unexpected failure. Error code: 1B1@01010013 ------------------------------------------------------------------- Unexpected failure. Error code: 1B1@01010013 ------------------------------------------------------------------- Unexpected failure. Error code: 1B1@01010013 ------------------------------------------------------------------- Unexpected failure. Error code: 1B1@01010013 ------------------------------------------------------------------- Unexpected failure. Error code: 1B1@01010013 ------------------------------------------------------------------- Unexpected failure. Error code: 1B1@01010013 ------------------------------------------------------------------- Failed to open device \\?\usbstor#disk&ven_usb&prod_flash_disk&rev_1100#fbi1302250514766&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}. Error code: 5@020D0002 ------------------------------------------------------------------- The shadow copies of volume F: were aborted because volume F:, which contains shadow copy storage for this shadow copy, was force dismounted. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The shadow copies of volume F: were aborted because of an IO failure on volume F:. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- The on-access driver failed to determine the name for a file. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Start-up script failed. GPO Name: Sophos_Install GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{AFC88A2F-95CE-45B4-B2E6-64666E7E1CC8}\Machine Script Name: \\francois.int\NETLOGON\Sophos.bat ------------------------------------------------------------------- Start-up script failed. GPO Name: Install_Insight_Discovery_Update GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{F8826B94-387A-4C26-88B5-33F427E144E2}\Machine Script Name: \\francois.int\it-tools\GPO\Scripts\Insight_update.ps1 ------------------------------------------------------------------- Start-up script failed. GPO Name: Teamviewer_15_Full_AF_NEW GPO File System Path: \\francois.int\sysvol\francois.int\Policies\{25374D65-7C82-4D33-B569-C99DAF6618AE}\Machine Script Name: \\francois.int\it-tools\GPO\Install\Teamviewer\V15.20.6\AF\Full.bat ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The previous system shutdown at 08:31:18 on ‎08/‎09/‎2021 was unexpected. ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {2387FADA-8CE7-42C6-BB56-854FBE8BFEA7} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- The server Microsoft.AAD.BrokerPlugin_1000.19041.1023.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.AAD.BrokerPlugin_1000.19041.1023.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {2387FADA-8CE7-42C6-BB56-854FBE8BFEA7} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Lenovo Hotkey Client Loader service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- This computer could not authenticate with \\AFSW16-DC01.francois.int, a Windows domain controller for domain FRANCOIS, and therefore this computer might deny logon requests. This inability to authenticate might be caused by another computer on the same network using the same name or the password for this computer account is not recognized. If this message appears again, contact your system administrator. ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (ec:81:93:33:71:bb) failed. ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (ec:81:93:33:71:bb) failed. ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (ec:81:93:33:71:bb) failed. ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (ec:81:93:33:71:bb) failed. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a02:2788:104:4f7::a with the system having network hardware address 00-11-32-3B-A9-ED. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Start-up script failed. GPO Name: Sophos_Install GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{AFC88A2F-95CE-45B4-B2E6-64666E7E1CC8}\Machine Script Name: \\francois.int\NETLOGON\Sophos.bat ------------------------------------------------------------------- Start-up script failed. GPO Name: Install_Insight_Discovery_Update GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{F8826B94-387A-4C26-88B5-33F427E144E2}\Machine Script Name: \\francois.int\it-tools\GPO\Scripts\Insight_update.ps1 ------------------------------------------------------------------- Start-up script failed. GPO Name: Teamviewer_15_Full_AF_NEW GPO File System Path: \\francois.int\sysvol\francois.int\Policies\{25374D65-7C82-4D33-B569-C99DAF6618AE}\Machine Script Name: \\francois.int\it-tools\GPO\Install\Teamviewer\V15.20.6\AF\Full.bat ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 12:50:18 on ‎06/‎09/‎2021 was unexpected. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain FRANCOIS due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- The Lenovo Hotkey Client Loader service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ------------------------------------------------------------------- Logon script failed. GPO Name: Signature_AF_External_Without_Mobile GPO File System Path: \\francois.int\SysVol\francois.int\Policies\{0EA5BD41-932A-4744-8DDA-CD2C9FFC93F4}\User Script Name: \\francois.int\it-tools\GPO\Scripts\Import_Signature.ps1 ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RasMan service. ...#SSU#... #Logs#Direct-X Diagnostics#Included ------------------ System Information ------------------ Time of this report: 3/29/2022, 10:49:57 Machine name: PC0212 Machine Id: {63A84F97-AE29-4D7B-9E97-78F3ACCA12C4} Operating System: Windows 10 Pro 64-bit (10.0, Build 19044) (19041.vb_release.191206-1406) Language: English (Regional Setting: English) System Manufacturer: LENOVO System Model: 20TQ003KMB BIOS: N30ET43W (1.26 ) (type: UEFI) Processor: Intel(R) Core(TM) i7-10850H CPU @ 2.70GHz (12 CPUs), ~2.7GHz Memory: 16384MB RAM Available OS Memory: 16142MB RAM Page File: 14966MB used, 6038MB available Windows Dir: C:\Windows DirectX Version: DirectX 12 DX Setup Parameters: Not found User DPI Setting: 96 DPI (100 percent) System DPI Setting: 96 DPI (100 percent) DWM DPI Scaling: Disabled Miracast: Available, with HDCP Microsoft Graphics Hybrid: Supported DirectX Database Version: 1.3.5 DxDiag Version: 10.00.19041.0928 64bit Unicode ------------ DxDiag Notes ------------ Display Tab 1: No problems found. Display Tab 2: No problems found. Display Tab 3: No problems found. Display Tab 4: No problems found. Sound Tab 1: No problems found. Input Tab: No problems found. -------------------- DirectX Debug Levels -------------------- Direct3D: 0/4 (retail) DirectDraw: 0/4 (retail) DirectInput: 0/5 (retail) DirectMusic: 0/5 (retail) DirectPlay: 0/9 (retail) DirectSound: 0/5 (retail) DirectShow: 0/6 (retail) --------------- Display Devices --------------- Card name: Intel(R) UHD Graphics Manufacturer: Intel Corporation Chip type: Intel(R) UHD Graphics Family DAC type: Internal Device Type: Full Device (POST) Device Key: Enum\PCI\VEN_8086&DEV_9BC4&SUBSYS_22A617AA&REV_05 Device Status: 0180200A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER] Device Problem Code: No Problem Driver Problem Code: Unknown Display Memory: 8198 MB Dedicated Memory: 128 MB Shared Memory: 8070 MB Current Mode: 1920 x 1200 (32 bit) (60Hz) HDR Support: Not Supported Display Topology: Extend Display Color Space: DXGI_COLOR_SPACE_RGB_FULL_G22_NONE_P709 Color Primaries: Red(0.661133,0.329102), Green(0.297852,0.618164), Blue(0.142578,0.051758), White Point(0.313477,0.329102) Display Luminance: Min Luminance = 0.500000, Max Luminance = 270.000000, MaxFullFrameLuminance = 270.000000 Monitor Name: Generic PnP Monitor Monitor Model: HP Z24i G2 Monitor Id: HPN3481 Native Mode: 1920 x 1200(p) (59.950Hz) Output Type: Displayport External Monitor Capabilities: HDR Not Supported Display Pixel Format: DISPLAYCONFIG_PIXELFORMAT_32BPP Advanced Color: Not Supported Driver Name: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igdumdim64.dll,C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igd10iumd64.dll,C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igd10iumd64.dll,C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igd12umd64.dll Driver File Version: 30.00.0101.1122 (English) Driver Version: 30.0.101.1122 DDI Version: 12 Feature Levels: 12_1,12_0,11_1,11_0,10_1,10_0,9_3,9_2,9_1 Driver Model: WDDM 2.7 Hardware Scheduling: Supported:False Enabled:False Graphics Preemption: Triangle Compute Preemption: Thread Miracast: Supported Detachable GPU: No Hybrid Graphics GPU: Integrated Power P-states: Not Supported Virtualization: Paravirtualization Block List: DISABLE_HWSCH Catalog Attributes: Universal:False Declarative:True Driver Attributes: Final Retail Driver Date/Size: 15/11/21 02:00:00, 1486352 bytes WHQL Logo'd: Yes WHQL Date Stamp: Unknown Device Identifier: {D7B78E66-D884-11CF-7870-C302AAC2D335} Vendor ID: 0x8086 Device ID: 0x9BC4 SubSys ID: 0x22A617AA Revision ID: 0x0005 Driver Strong Name: oem183.inf:5f63e534c1887fe6:iCML_w10_DS:30.0.101.1122:PCI\VEN_8086&DEV_9BC4&SUBSYS_22A617AA Rank Of Driver: 00CF0001 Video Accel: ModeMPEG2_A ModeMPEG2_C ModeWMV9_C ModeVC1_C DXVA2 Modes: DXVA2_ModeMPEG2_VLD DXVA2_ModeMPEG2_IDCT DXVA2_ModeVC1_D2010 {E07EC519-E651-4CD6-AC84-1370CCEEC851} {BCC5DB6D-A2B6-4AF0-ACE4-ADB1F787BC89} DXVA2_ModeWMV9_IDCT DXVA2_ModeVC1_IDCT DXVA2_ModeH264_VLD_NoFGT DXVA2_ModeH264_VLD_Stereo_Progressive_NoFGT DXVA2_ModeH264_VLD_Stereo_NoFGT DXVA2_ModeH264_VLD_Multiview_NoFGT {C528916C-C0AF-4645-8CB2-372B6D4ADC2A} {91CD2D6E-897B-4FA1-B0D7-51DC88010E0A} DXVA2_ModeVP8_VLD {442B942A-B4D9-4940-BC45-A882E5F919F3} {97688186-56A8-4094-B543-FC9DAAA49F4B} {1424D4DC-7CF5-4BB1-9CD7-B63717A72A6B} {C346E8A3-CBED-4D27-87CC-A70EB4DC8C27} {FFC79924-5EAF-4666-A736-06190F281443} {2364D06A-F67F-4186-AED0-62B99E1784F1} {464BDB3C-91C4-4E9B-896F-225496AC4ED6} {28566328-F041-4466-8B14-8F5831E78F8B} {6B4A94DB-54FE-4AE1-9BE4-7A7DAD004600} {8C56EB1E-2B47-466F-8D33-7DBCD63F3DF2} DXVA2_ModeHEVC_VLD_Main {75FC75F7-C589-4A07-A25B-72E03B0383B3} DXVA2_ModeHEVC_VLD_Main10 {07CFAFFB-5A2E-4B99-B62A-E4CA53B6D5AA} DXVA2_ModeVP9_VLD_Profile0 DXVA2_ModeVP9_VLD_10bit_Profile2 {76988A52-DF13-419A-8E64-FFCF4A336CF5} {80A3A7BD-89D8-4497-A2B8-2126AF7E6EB8} {50925B7B-E931-4978-A12A-586630F095F9} {B69C20E0-2508-8790-0305-875499E0A2D0} {49761BEC-4B63-4349-A5FF-87FFDF088466} Deinterlace Caps: {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC3,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC4,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC4,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend D3D9 Overlay: Supported DXVA-HD: Supported DDraw Status: Enabled D3D Status: Enabled AGP Status: Enabled MPO MaxPlanes: 1 MPO Caps: Not Supported MPO Stretch: Not Supported MPO Media Hints: Not Supported MPO Formats: Not Supported PanelFitter Caps: Not Supported PanelFitter Stretch: Not Supported Extension Drivers: Driver Name: C:\Windows\System32\DriverStore\FileRepository\iigd_ext.inf_amd64_bcdfa9eb6a3abda4\iigd_ext.inf Driver Version: 30.0.101.1122 Driver Date: 11/15/2021 Driver Provider: Intel Corporation Catalog Attributes: Universal:False Declarative:True Component Drivers: Driver Name: Unknown Driver Version: Unknown Driver Date: Unknown Driver Provider: Unknown Catalog Attributes: N/A Driver Name: Unknown Driver Version: Unknown Driver Date: Unknown Driver Provider: Unknown Catalog Attributes: N/A Card name: Intel(R) UHD Graphics Manufacturer: Intel Corporation Chip type: Intel(R) UHD Graphics Family DAC type: Internal Device Type: Full Device (POST) Device Key: Enum\PCI\VEN_8086&DEV_9BC4&SUBSYS_22A617AA&REV_05 Device Status: 0180200A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER] Device Problem Code: No Problem Driver Problem Code: Unknown Display Memory: 8198 MB Dedicated Memory: 128 MB Shared Memory: 8070 MB Current Mode: 1920 x 1200 (32 bit) (60Hz) HDR Support: Not Supported Display Topology: Extend Display Color Space: DXGI_COLOR_SPACE_RGB_FULL_G22_NONE_P709 Color Primaries: Red(0.661133,0.329102), Green(0.297852,0.618164), Blue(0.142578,0.051758), White Point(0.313477,0.329102) Display Luminance: Min Luminance = 0.500000, Max Luminance = 270.000000, MaxFullFrameLuminance = 270.000000 Monitor Name: Generic PnP Monitor Monitor Model: HP Z24i G2 Monitor Id: HPN3481 Native Mode: 1920 x 1200(p) (59.950Hz) Output Type: Displayport External Monitor Capabilities: HDR Not Supported Display Pixel Format: DISPLAYCONFIG_PIXELFORMAT_32BPP Advanced Color: Not Supported Driver Name: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igdumdim64.dll,C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igd10iumd64.dll,C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igd10iumd64.dll,C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igd12umd64.dll Driver File Version: 30.00.0101.1122 (English) Driver Version: 30.0.101.1122 DDI Version: 12 Feature Levels: 12_1,12_0,11_1,11_0,10_1,10_0,9_3,9_2,9_1 Driver Model: WDDM 2.7 Hardware Scheduling: Supported:False Enabled:False Graphics Preemption: Triangle Compute Preemption: Thread Miracast: Supported Detachable GPU: No Hybrid Graphics GPU: Integrated Power P-states: Not Supported Virtualization: Paravirtualization Block List: DISABLE_HWSCH Catalog Attributes: Universal:False Declarative:True Driver Attributes: Final Retail Driver Date/Size: 15/11/21 02:00:00, 1486352 bytes WHQL Logo'd: Yes WHQL Date Stamp: Unknown Device Identifier: {D7B78E66-D884-11CF-7870-C302AAC2D335} Vendor ID: 0x8086 Device ID: 0x9BC4 SubSys ID: 0x22A617AA Revision ID: 0x0005 Driver Strong Name: oem183.inf:5f63e534c1887fe6:iCML_w10_DS:30.0.101.1122:PCI\VEN_8086&DEV_9BC4&SUBSYS_22A617AA Rank Of Driver: 00CF0001 Video Accel: ModeMPEG2_A ModeMPEG2_C ModeWMV9_C ModeVC1_C DXVA2 Modes: DXVA2_ModeMPEG2_VLD DXVA2_ModeMPEG2_IDCT DXVA2_ModeVC1_D2010 {E07EC519-E651-4CD6-AC84-1370CCEEC851} {BCC5DB6D-A2B6-4AF0-ACE4-ADB1F787BC89} DXVA2_ModeWMV9_IDCT DXVA2_ModeVC1_IDCT DXVA2_ModeH264_VLD_NoFGT DXVA2_ModeH264_VLD_Stereo_Progressive_NoFGT DXVA2_ModeH264_VLD_Stereo_NoFGT DXVA2_ModeH264_VLD_Multiview_NoFGT {C528916C-C0AF-4645-8CB2-372B6D4ADC2A} {91CD2D6E-897B-4FA1-B0D7-51DC88010E0A} DXVA2_ModeVP8_VLD {442B942A-B4D9-4940-BC45-A882E5F919F3} {97688186-56A8-4094-B543-FC9DAAA49F4B} {1424D4DC-7CF5-4BB1-9CD7-B63717A72A6B} {C346E8A3-CBED-4D27-87CC-A70EB4DC8C27} {FFC79924-5EAF-4666-A736-06190F281443} {2364D06A-F67F-4186-AED0-62B99E1784F1} {464BDB3C-91C4-4E9B-896F-225496AC4ED6} {28566328-F041-4466-8B14-8F5831E78F8B} {6B4A94DB-54FE-4AE1-9BE4-7A7DAD004600} {8C56EB1E-2B47-466F-8D33-7DBCD63F3DF2} DXVA2_ModeHEVC_VLD_Main {75FC75F7-C589-4A07-A25B-72E03B0383B3} DXVA2_ModeHEVC_VLD_Main10 {07CFAFFB-5A2E-4B99-B62A-E4CA53B6D5AA} DXVA2_ModeVP9_VLD_Profile0 DXVA2_ModeVP9_VLD_10bit_Profile2 {76988A52-DF13-419A-8E64-FFCF4A336CF5} {80A3A7BD-89D8-4497-A2B8-2126AF7E6EB8} {50925B7B-E931-4978-A12A-586630F095F9} {B69C20E0-2508-8790-0305-875499E0A2D0} {49761BEC-4B63-4349-A5FF-87FFDF088466} Deinterlace Caps: {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC3,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC4,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC4,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend D3D9 Overlay: Supported DXVA-HD: Supported DDraw Status: Enabled D3D Status: Enabled AGP Status: Enabled MPO MaxPlanes: 1 MPO Caps: Not Supported MPO Stretch: Not Supported MPO Media Hints: Not Supported MPO Formats: Not Supported PanelFitter Caps: Not Supported PanelFitter Stretch: Not Supported Extension Drivers: Driver Name: C:\Windows\System32\DriverStore\FileRepository\iigd_ext.inf_amd64_bcdfa9eb6a3abda4\iigd_ext.inf Driver Version: 30.0.101.1122 Driver Date: 11/15/2021 Driver Provider: Intel Corporation Catalog Attributes: Universal:False Declarative:True Card name: NVIDIA Quadro P620 Manufacturer: NVIDIA Chip type: Quadro P620 DAC type: Integrated RAMDAC Device Type: Render-Only Device Device Key: Enum\PCI\VEN_10DE&DEV_1CBD&SUBSYS_22A617AA&REV_A1 Device Status: 0180200A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER] Device Problem Code: No Problem Driver Problem Code: Unknown Display Memory: 12091 MB Dedicated Memory: 4021 MB Shared Memory: 8070 MB Current Mode: Unknown HDR Support: Unknown Display Topology: Unknown Display Color Space: Unknown Color Primaries: Unknown Display Luminance: Unknown Driver Name: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvldumdx.dll Driver File Version: 30.00.0014.7242 (English) Driver Version: 30.0.14.7242 DDI Version: 12 Feature Levels: 12_1,12_0,11_1,11_0,10_1,10_0,9_3,9_2,9_1 Driver Model: WDDM 2.7 Hardware Scheduling: Supported:True Enabled:False Graphics Preemption: Pixel Compute Preemption: Dispatch Miracast: Not Supported by Graphics driver Detachable GPU: No Hybrid Graphics GPU: Discrete Power P-states: Not Supported Virtualization: Paravirtualization Block List: No Blocks Catalog Attributes: Universal:False Declarative:True Driver Attributes: Final Retail Driver Date/Size: 20/10/21 02:00:00, 1056272 bytes WHQL Logo'd: Yes WHQL Date Stamp: Unknown Device Identifier: Unknown Vendor ID: 0x10DE Device ID: 0x1CBD SubSys ID: 0x22A617AA Revision ID: 0x00A1 Driver Strong Name: oem134.inf:0f066de3703554e8:Section100:30.0.14.7242:pci\ven_10de&dev_1cbd&subsys_22a617aa Rank Of Driver: 00CF0001 Video Accel: Unknown DXVA2 Modes: {86695F12-340E-4F04-9FD3-9253DD327460} DXVA2_ModeMPEG2_VLD {6F3EC719-3735-42CC-8063-65CC3CB36616} DXVA2_ModeVC1_D2010 DXVA2_ModeVC1_VLD {32FCFE3F-DE46-4A49-861B-AC71110649D5} DXVA2_ModeH264_VLD_Stereo_Progressive_NoFGT DXVA2_ModeH264_VLD_Stereo_NoFGT DXVA2_ModeH264_VLD_NoFGT DXVA2_ModeHEVC_VLD_Main DXVA2_ModeHEVC_VLD_Main10 {20BB8B0A-97AA-4571-8E99-64E60606C1A6} {15DF9B21-06C4-47F1-841E-A67C97D7F312} DXVA2_ModeMPEG4pt2_VLD_Simple DXVA2_ModeMPEG4pt2_VLD_AdvSimple_NoGMC {9947EC6F-689B-11DC-A320-0019DBBC4184} {33FCFE41-DE46-4A49-861B-AC71110649D5} DXVA2_ModeVP9_VLD_Profile0 DXVA2_ModeVP9_VLD_10bit_Profile2 {DDA19DC7-93B5-49F5-A9B3-2BDA28A2CE6E} {6AFFD11E-1D96-42B1-A215-93A31F09A53D} {914C84A3-4078-4FA9-984C-E2F262CB5C9C} Deinterlace Caps: n/a D3D9 Overlay: Unknown DXVA-HD: Unknown DDraw Status: Enabled D3D Status: Enabled AGP Status: Enabled MPO MaxPlanes: 0 MPO Caps: Not Supported MPO Stretch: Not Supported MPO Media Hints: Not Supported MPO Formats: Not Supported PanelFitter Caps: Not Supported PanelFitter Stretch: Not Supported Card name: Citrix Indirect Display Adapter Manufacturer: Citrix Systems Inc. Chip type: Unknown DAC type: Unknown Device Type: Display-Only Device Device Key: Enum\PCI\VEN_5853&DEV_1003 Device Status: 0180600A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_REMOVABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER] Device Problem Code: No Problem Driver Problem Code: Unknown Display Memory: 8198 MB Dedicated Memory: 128 MB Shared Memory: 8070 MB Current Mode: Unknown HDR Support: Unknown Display Topology: Unknown Display Color Space: Unknown Color Primaries: Unknown Display Luminance: Unknown Driver Name: c:\windows\system32\drivers\umdf\vidd.dll,c:\windows\system32\drivers\wudfrd.sys Driver File Version: 7.21.0000.0183 (English) Driver Version: 12.40.44.247 DDI Version: 12 Feature Levels: 12_1,12_0,11_1,11_0,10_1,10_0,9_3,9_2,9_1 Driver Model: WDDM 1.3 Hardware Scheduling: Supported:False Enabled:False Graphics Preemption: DMA Compute Preemption: DMA Miracast: Not Supported by Graphics driver Detachable GPU: No Hybrid Graphics GPU: Not Supported Power P-states: Not Supported Virtualization: Not Supported Block List: DISABLE_HWSCH Catalog Attributes: Universal:True Declarative:True Driver Attributes: Final Retail Driver Date/Size: 23/01/19 02:00:00, 85624 bytes WHQL Logo'd: Yes WHQL Date Stamp: Unknown Device Identifier: Unknown Vendor ID: 0x8086 Device ID: 0x9BC4 SubSys ID: 0x22A617AA Revision ID: 0x0005 Driver Strong Name: oem101.inf:467b626d1b5d690c:ViddDev_Install.NT:12.40.44.247:PCI\VEN_5853&DEV_1003 Rank Of Driver: 00FF0000 Video Accel: Unknown DXVA2 Modes: DXVA2_ModeMPEG2_VLD DXVA2_ModeMPEG2_IDCT DXVA2_ModeVC1_D2010 {E07EC519-E651-4CD6-AC84-1370CCEEC851} {BCC5DB6D-A2B6-4AF0-ACE4-ADB1F787BC89} DXVA2_ModeWMV9_IDCT DXVA2_ModeVC1_IDCT DXVA2_ModeH264_VLD_NoFGT DXVA2_ModeH264_VLD_Stereo_Progressive_NoFGT DXVA2_ModeH264_VLD_Stereo_NoFGT DXVA2_ModeH264_VLD_Multiview_NoFGT {C528916C-C0AF-4645-8CB2-372B6D4ADC2A} {91CD2D6E-897B-4FA1-B0D7-51DC88010E0A} DXVA2_ModeVP8_VLD {442B942A-B4D9-4940-BC45-A882E5F919F3} {97688186-56A8-4094-B543-FC9DAAA49F4B} {1424D4DC-7CF5-4BB1-9CD7-B63717A72A6B} {C346E8A3-CBED-4D27-87CC-A70EB4DC8C27} {FFC79924-5EAF-4666-A736-06190F281443} {2364D06A-F67F-4186-AED0-62B99E1784F1} {464BDB3C-91C4-4E9B-896F-225496AC4ED6} {28566328-F041-4466-8B14-8F5831E78F8B} {6B4A94DB-54FE-4AE1-9BE4-7A7DAD004600} {8C56EB1E-2B47-466F-8D33-7DBCD63F3DF2} DXVA2_ModeHEVC_VLD_Main {75FC75F7-C589-4A07-A25B-72E03B0383B3} DXVA2_ModeHEVC_VLD_Main10 {07CFAFFB-5A2E-4B99-B62A-E4CA53B6D5AA} DXVA2_ModeVP9_VLD_Profile0 DXVA2_ModeVP9_VLD_10bit_Profile2 {76988A52-DF13-419A-8E64-FFCF4A336CF5} {80A3A7BD-89D8-4497-A2B8-2126AF7E6EB8} {50925B7B-E931-4978-A12A-586630F095F9} {B69C20E0-2508-8790-0305-875499E0A2D0} {49761BEC-4B63-4349-A5FF-87FFDF088466} Deinterlace Caps: n/a D3D9 Overlay: Unknown DXVA-HD: Unknown DDraw Status: Enabled D3D Status: Enabled AGP Status: Enabled MPO MaxPlanes: 0 MPO Caps: Not Supported MPO Stretch: Not Supported MPO Media Hints: Not Supported MPO Formats: Not Supported PanelFitter Caps: Not Supported PanelFitter Stretch: Not Supported ------------- Sound Devices ------------- Description: Speakers (Realtek(R) Audio) Default Sound Playback: Yes Default Voice Playback: Yes Hardware ID: INTELAUDIO\FUNC_01&VEN_10EC&DEV_0257&SUBSYS_17AA22A4&REV_1000 Manufacturer ID: N/A Product ID: N/A Type: N/A Driver Name: RTKVHD64.sys Driver Version: 6.0.9091.1 (English) Driver Attributes: Final Retail WHQL Logo'd: Yes Date and Size: 28/12/20 02:00:00, 6008928 bytes Other Files: Driver Provider: Realtek Semiconductor Corp. HW Accel Level: Emulation Only Cap Flags: 0xF1F Min/Max Sample Rate: 100, 200000 Static/Strm HW Mix Bufs: 1, 0 Static/Strm HW 3D Bufs: 0, 0 HW Memory: 0 Voice Management: No EAX(tm) 2.0 Listen/Src: No, No I3DL2(tm) Listen/Src: No, No Sensaura(tm) ZoomFX(tm): No --------------------- Sound Capture Devices --------------------- Description: Microphone Array (Realtek(R) Audio) Default Sound Capture: Yes Default Voice Capture: Yes Driver Name: RTKVHD64.sys Driver Version: 6.0.9091.1 (English) Driver Attributes: Final Retail Date and Size: 28/12/20 02:00:00, 6008928 bytes Cap Flags: 0x1 Format Flags: 0xFFFFF --------------------- Video Capture Devices Number of Devices: 4 --------------------- FriendlyName: Integrated Camera Category: Camera SymbolicLink: \\?\usb#vid_13d3&pid_56fb&mi_00#6&3129022c&0&0000#{e5323777-f976-4f5b-9b55-b94699c46e44}\global Location: Front Rotation: 0 Manufacturer: Realtek HardwareID: USB\VID_13D3&PID_56FB&REV_6004&MI_00,USB\VID_13D3&PID_56FB&MI_00 DriverDesc: Integrated Camera DriverProvider: Realtek DriverVersion: 10.0.22000.20214 DriverDateEnglish: 11/1/2021 00:00:00 DriverDateLocalized: 01/11/21 00:00:00 Service: usbvideo Class: Camera DevNodeStatus: 180200A[DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER] ContainerId: {00000000-0000-0000-FFFF-FFFFFFFFFFFF} ProblemCode: No Problem BusReportedDeviceDesc: Integrated Camera Parent: USB\VID_13D3&PID_56FB\0000 DriverProblemDesc: n/a UpperFilters: n/a LowerFilters: WdmCompanionFilter Stack: \Driver\ksthunk,\Driver\usbvideo,\Driver\ACPI,\Driver\usbccgp ContainerCategory: n/a SensorGroupID: {f66fa674-f2be-4d19-98c5-d132329c642f} MFT0: n/a DMFT: {09824200-9A44-4B06-8C74-92D99E09B435} CustomCaptureSource: n/a DependentStillCapture: False EnablePlatformDMFT: True DMFTChain: {09824200-9A44-4B06-8C74-92D99E09B435} EnableDshowRedirection: True FrameServerEnabled: n/a AnalogProviders: n/a ProfileIDs: {B4894D81-62B7-4EEC-8740-80658C4A9D3E},0;{81361B22-700B-4546-A2D4-C52E907BFC27},0 FriendlyName: Logi Webcam C920e Category: Camera SymbolicLink: \\?\usb#vid_046d&pid_08b6&mi_00#d&2a8d8484&0&0000#{e5323777-f976-4f5b-9b55-b94699c46e44}\global Location: n/a Rotation: n/a Manufacturer: Microsoft HardwareID: USB\VID_046D&PID_08B6&REV_0021&MI_00,USB\VID_046D&PID_08B6&MI_00 DriverDesc: USB Video Device DriverProvider: Microsoft DriverVersion: 10.0.19041.1387 DriverDateEnglish: 6/21/2006 00:00:00 DriverDateLocalized: 21/06/06 00:00:00 Service: usbvideo Class: Camera DevNodeStatus: 180200A[DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER] ContainerId: {7172C0E0-4955-5966-8F5D-694E560DA519} ProblemCode: No Problem BusReportedDeviceDesc: Logi Webcam C920e Parent: USB\VID_046D&PID_08B6\C2D91ABF DriverProblemDesc: n/a UpperFilters: n/a LowerFilters: WdmCompanionFilter Stack: \Driver\ksthunk,\Driver\usbvideo,\Driver\usbccgp ContainerCategory: n/a SensorGroupID: n/a MFT0: n/a DMFT: n/a CustomCaptureSource: n/a DependentStillCapture: n/a EnablePlatformDMFT: n/a DMFTChain: n/a EnableDshowRedirection: n/a FrameServerEnabled: n/a AnalogProviders: n/a ProfileIDs: n/a FriendlyName: Integrated IR Camera Category: Sensor SymbolicLink: \\?\usb#vid_13d3&pid_56fb&mi_02#6&3129022c&0&0002#{24e552d7-6523-47f7-a647-d3465bf1f5ca}\global Location: Front Rotation: 0 Manufacturer: Realtek HardwareID: USB\VID_13D3&PID_56FB&REV_6004&MI_02,USB\VID_13D3&PID_56FB&MI_02 DriverDesc: Realtek DMFT - IR DriverProvider: Realtek DriverVersion: 10.0.22000.20214 DriverDateEnglish: 11/1/2021 00:00:00 DriverDateLocalized: 01/11/21 00:00:00 Service: usbvideo Class: Camera DevNodeStatus: 180200A[DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER] ContainerId: {00000000-0000-0000-FFFF-FFFFFFFFFFFF} ProblemCode: No Problem BusReportedDeviceDesc: Integrated IR Camera Parent: USB\VID_13D3&PID_56FB\0000 DriverProblemDesc: n/a UpperFilters: n/a LowerFilters: WdmCompanionFilter Stack: \Driver\ksthunk,\Driver\usbvideo,\Driver\ACPI,\Driver\usbccgp ContainerCategory: n/a SensorGroupID: {f66fa674-f2be-4d19-98c5-d132329c642f} MFT0: n/a DMFT: {09824200-9A44-4B06-8C74-92D99E09B435} CustomCaptureSource: n/a DependentStillCapture: n/a EnablePlatformDMFT: n/a DMFTChain: {09824200-9A44-4B06-8C74-92D99E09B435} EnableDshowRedirection: True FrameServerEnabled: n/a AnalogProviders: n/a ProfileIDs: {B4894D81-62B7-4EEC-8740-80658C4A9D3E},0;{81361B22-700B-4546-A2D4-C52E907BFC27},0 FriendlyName: AvStream Media Device Category: Sensor Group SymbolicLink: \\?\swd#sgdevapi#c5cd3632d9f8224970d84280d69829e275074a9b4ee46439af5ed7c9dbcd11b2#{669c7214-0a88-4311-a7f3-4e79820e33bd}\c5cd3632d9f8224970d84280d69829e275074a9b4ee46439af5ed7c9dbcd11b2 DeviceSymbolicLinks: \\?\USB#VID_13D3&PID_56FB&MI_00#6&3129022c&0&0000#{e5323777-f976-4f5b-9b55-b94699c46e44}\global,\\?\USB#VID_13D3&PID_56FB&MI_02#6&3129022c&0&0002#{24e552d7-6523-47f7-a647-d3465bf1f5ca}\global ProfileIDs: {B4894D81-62B7-4EEC-8740-80658C4A9D3E},0;{81361B22-700B-4546-A2D4-C52E907BFC27},0 ------------------- DirectInput Devices ------------------- Device Name: Mouse Attached: 1 Controller ID: n/a Vendor/Product ID: n/a FF Driver: n/a Device Name: Keyboard Attached: 1 Controller ID: n/a Vendor/Product ID: n/a FF Driver: n/a Device Name: Logitech Download Assistant Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x046D, 0xB015 FF Driver: n/a Device Name: Synaptics HID-Compliant Touch pad Device Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x06CB, 0x000F FF Driver: n/a Device Name: Synaptics HID-Compliant Touch pad Device Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x06CB, 0x000F FF Driver: n/a Device Name: Logitech Download Assistant Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x046D, 0xB350 FF Driver: n/a Device Name: HID-compliant vendor-defined device Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x046D, 0xB350 FF Driver: n/a Device Name: ThinkPad Thunderbolt 3 Dock USB Audio Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x17EF, 0x3083 FF Driver: n/a Poll w/ Interrupt: No ----------- USB Devices ----------- + USB Root Hub (USB 3.0) | Vendor/Product ID: 0x8086, 0x06ED | Matching Device ID: USB\ROOT_HUB30 | Service: USBHUB3 | Driver: USBHUB3.SYS, 9/15/2021 11:00:49, 648016 bytes | +-+ Intel(R) Wireless Bluetooth(R) | | Vendor/Product ID: 0x8087, 0x0026 | | Location: Port_#0014.Hub_#0001 | | Matching Device ID: USB\VID_8087&PID_0026&REV_0002 | | Lower Filters: ibtusb | | Service: BTHUSB | | Driver: ibtusb.sys, 12/21/2021 20:05:08, 6917704 bytes | | Driver: BTHUSB.SYS, 12/15/2021 11:46:59, 110592 bytes | | Driver: bthport.sys, 12/15/2021 11:46:59, 1559552 bytes | | | +-+ Microsoft Bluetooth LE Enumerator | | | Matching Device ID: BTH\MS_BTHLE | | | Service: BthLEEnum | | | Driver: Microsoft.Bluetooth.Legacy.LEEnumerator.sys, 11/19/2020 04:48:32, 106496 bytes | | | | | +-+ Bluetooth LE Device | | | | Location: Bluetooth LE Device | | | | Matching Device ID: BTHLE\GenericDevice | | | | Service: BthLEEnum | | | | Driver: Microsoft.Bluetooth.Legacy.LEEnumerator.sys, 11/19/2020 04:48:32, 106496 bytes | | | | | | | +-+ Bluetooth Low Energy GATT compliant HID device | | | | | Vendor/Product ID: 0x0020, 0x0B35 | | | | | Location: Bluetooth LE Device | | | | | Matching Device ID: BTHLEDevice\{00001812-0000-1000-8000-00805f9b34fb} | | | | | Lower Filters: WUDFRd | | | | | Service: mshidumdf | | | | | Driver: Microsoft.Bluetooth.Profiles.HidOverGatt.dll, 5/4/2021 17:15:14, 194560 bytes | | | | | | | | | +-+ HID Keyboard Device | | | | | | Vendor/Product ID: 0x0020, 0x0B35 | | | | | | Matching Device ID: HID_DEVICE_SYSTEM_KEYBOARD | | | | | | Service: kbdhid | | | | | | Driver: kbdhid.sys, 12/7/2019 11:07:56, 46592 bytes | | | | | | Driver: kbdclass.sys, 12/7/2019 11:07:56, 71480 bytes | | | | | | | | | | +-+ HID-compliant mouse | | | | | | Vendor/Product ID: 0x0020, 0x0B35 | | | | | | Matching Device ID: HID_DEVICE_SYSTEM_MOUSE | | | | | | Service: mouhid | | | | | | Driver: mouhid.sys, 12/7/2019 11:07:56, 35328 bytes | | | | | | Driver: mouclass.sys, 12/7/2019 11:07:56, 67600 bytes | | | | | | +-+ Bluetooth LE Device | | | | Location: Bluetooth LE Device | | | | Matching Device ID: BTHLE\GenericDevice | | | | Service: BthLEEnum | | | | Driver: Microsoft.Bluetooth.Legacy.LEEnumerator.sys, 11/19/2020 04:48:32, 106496 bytes | | | | | | | +-+ Bluetooth Low Energy GATT compliant HID device | | | | | Vendor/Product ID: 0x0020, 0x0B01 | | | | | Location: Bluetooth LE Device | | | | | Matching Device ID: BTHLEDevice\{00001812-0000-1000-8000-00805f9b34fb} | | | | | Lower Filters: WUDFRd | | | | | Service: mshidumdf | | | | | Driver: Microsoft.Bluetooth.Profiles.HidOverGatt.dll, 5/4/2021 17:15:14, 194560 bytes | | | | | | | | | +-+ HID Keyboard Device | | | | | | Vendor/Product ID: 0x0020, 0x0B01 | | | | | | Matching Device ID: HID_DEVICE_SYSTEM_KEYBOARD | | | | | | Service: kbdhid | | | | | | Driver: kbdhid.sys, 12/7/2019 11:07:56, 46592 bytes | | | | | | Driver: kbdclass.sys, 12/7/2019 11:07:56, 71480 bytes | | | | | | | | | | +-+ HID-compliant mouse | | | | | | Vendor/Product ID: 0x0020, 0x0B01 | | | | | | Matching Device ID: HID_DEVICE_SYSTEM_MOUSE | | | | | | Service: mouhid | | | | | | Driver: mouhid.sys, 12/7/2019 11:07:56, 35328 bytes | | | | | | Driver: mouclass.sys, 12/7/2019 11:07:56, 67600 bytes ---------------- Gameport Devices ---------------- ------------ PS/2 Devices ------------ + Standard PS/2 Keyboard | Matching Device ID: *PNP0303 | Service: i8042prt | Driver: i8042prt.sys, 12/7/2019 11:07:56, 118272 bytes | Driver: kbdclass.sys, 12/7/2019 11:07:56, 71480 bytes | + Synaptics Pointing Device | Matching Device ID: ACPI\LEN2070 | Upper Filters: SynTP | Service: i8042prt | Driver: SynTP.sys, 9/27/2021 01:11:14, 804368 bytes | Driver: SynTPEnh.exe, 9/27/2021 01:16:56, 4432912 bytes | Driver: SynTPRes.dll, 9/27/2021 01:19:00, 20188176 bytes | Driver: SynTPCpl.dll, 9/27/2021 01:18:38, 4044816 bytes | Driver: SynTPAPI.dll, 9/27/2021 01:18:22, 326160 bytes | Driver: SynCOM.dll, 9/27/2021 01:17:42, 1113104 bytes | Driver: SynTPHelper.exe, 9/27/2021 01:16:44, 248848 bytes | Driver: mouclass.sys, 12/7/2019 11:07:56, 67600 bytes | Driver: i8042prt.sys, 12/7/2019 11:07:56, 118272 bytes | + HID-compliant mouse | Vendor/Product ID: 0x06CB, 0x000F | Matching Device ID: HID_DEVICE_SYSTEM_MOUSE | Service: mouhid | Driver: mouhid.sys, 12/7/2019 11:07:56, 35328 bytes | Driver: mouclass.sys, 12/7/2019 11:07:56, 67600 bytes ------------------------ Disk & DVD/CD-ROM Drives ------------------------ Drive: C: Free Space: 77.0 GB Total Space: 199.4 GB File System: NTFS Model: WDC PC SN730 SDBQNTY-512G-1001 Drive: D: Free Space: 221.4 GB Total Space: 288.4 GB File System: NTFS Model: WDC PC SN730 SDBQNTY-512G-1001 -------------- System Devices -------------- Name: Intel(R) PCI Express Root Port #8 - 06BF Device ID: PCI\VEN_8086&DEV_06BF&SUBSYS_22A417AA&REV_F0\3&11583659&0&E7 Driver: C:\Windows\system32\DRIVERS\pci.sys, 10.00.19041.1387 (English), 12/15/2021 11:46:59, 469840 bytes Name: PCI Express Downstream Switch Port Device ID: PCI\VEN_8086&DEV_15E7&SUBSYS_22A617AA&REV_06\C725F10005C9A00010 Driver: C:\Windows\system32\DRIVERS\pci.sys, 10.00.19041.1387 (English), 12/15/2021 11:46:59, 469840 bytes Name: PCI Express Downstream Switch Port Device ID: PCI\VEN_8086&DEV_15E7&SUBSYS_22A617AA&REV_06\C725F10005C9A00008 Driver: C:\Windows\system32\DRIVERS\pci.sys, 10.00.19041.1387 (English), 12/15/2021 11:46:59, 469840 bytes Name: PCI Express Downstream Switch Port Device ID: PCI\VEN_8086&DEV_15E7&SUBSYS_22A617AA&REV_06\C725F10005C9A00000 Driver: C:\Windows\system32\DRIVERS\pci.sys, 10.00.19041.1387 (English), 12/15/2021 11:46:59, 469840 bytes Name: NVIDIA Quadro P620 Device ID: PCI\VEN_10DE&DEV_1CBD&SUBSYS_22A617AA&REV_A1\4&330FF97B&0&0008 Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\NVWMI\nvPerfProvider.man, 10/21/2021 00:51:22, 14175 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\NVWMI\nvWmi.mof, 10/21/2021 00:51:22, 147910 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\NVWMI\nvWmi64.exe, 2.36.0000.0000 (English), 11/10/2021 15:01:30, 4450936 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\Display.NvContainer\MessageBus.dll, 1.22.2758.1620 (English), 11/10/2021 15:00:50, 7532672 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\Display.NvContainer\NVDisplay.Container.exe, 1.33.2988.2648 (English), 11/10/2021 15:00:52, 912000 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\Display.NvContainer\NvContainerRecovery.bat, 10/21/2021 00:51:22, 1951 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\Display.NvContainer\dlsargs.xml, 10/21/2021 00:51:22, 396 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\Display.NvContainer\dlsnetparams.csv, 10/21/2021 00:51:22, 60689 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\Display.NvContainer\messagebus_client.conf, 10/21/2021 00:51:22, 57 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\Display.NvContainer\nvgwls.exe, 11/10/2021 15:00:52, 33227904 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\Display.NvContainer\nvtopps.db3, 10/21/2021 00:51:22, 110592 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\Display.NvContainer\plugins\LocalSystem\NvXDCore.dll, 30.00.0014.7242 (English), 11/10/2021 15:00:58, 1833088 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\Display.NvContainer\plugins\LocalSystem\NvcDispCorePlugin.dll, 30.00.0014.7242 (English), 11/10/2021 15:00:54, 521344 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\Display.NvContainer\plugins\LocalSystem\NvcDispWatchdog.dll, 1.33.2988.2648 (English), 11/10/2021 15:00:56, 646272 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\Display.NvContainer\plugins\LocalSystem\_DisplayDriverRAS.dll, 1.10.0000.0000 (English), 11/10/2021 15:00:58, 2616448 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\Display.NvContainer\plugins\LocalSystem\_NvMsgBusBroadcast.dll, 1.33.2988.2648 (English), 11/10/2021 15:01:00, 3160192 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\Display.NvContainer\plugins\LocalSystem\messagebus.conf, 10/21/2021 00:51:22, 57 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\Display.NvContainer\plugins\Session\NvFBCPlugin.dll, 6.14.0014.7242 (English), 11/10/2021 15:01:00, 1372288 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\Display.NvContainer\plugins\Session\_nvppo.dll, 30.00.0014.7242 (English), 11/10/2021 15:01:06, 1607808 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\Display.NvContainer\plugins\Session\_nvtopps.dll, 30.00.0014.7242 (English), 11/10/2021 15:01:06, 12257400 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\Display.NvContainer\plugins\Session\nvprofileupdaterplugin.dll, 30.00.0014.7242 (English), 11/10/2021 15:01:02, 2191488 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\Display.NvContainer\plugins\Session\nvxdsyncplugin.dll, 8.17.0014.7242 (English), 11/10/2021 15:01:02, 1812080 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\Display.NvContainer\plugins\Session\wksServicePlugin.dll, 30.00.0014.7242 (English), 11/10/2021 15:01:04, 618616 bytes Driver: C:\Windows\system32\DRIVERS\NVIDIA Corporation\Drs\dbInstaller.exe, 30.00.0014.7242 (English), 11/10/2021 14:54:54, 728184 bytes Driver: C:\Windows\system32\DRIVERS\NVIDIA Corporation\Drs\nvdrsdb.bin, 10/21/2021 00:51:22, 1799588 bytes Driver: C:\Windows\system32\nvcpl.dll, 8.17.0014.7242 (English), 11/10/2021 14:55:44, 5681280 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nv3dappshext.dll, 6.14.0014.7242 (English), 11/10/2021 14:55:10, 1000072 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nv3dappshextr.dll, 6.14.0014.7242 (English), 11/10/2021 14:55:12, 91280 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvcoproc.bin, 10/21/2021 00:51:22, 9773167 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvcpl.dll, 8.17.0014.7242 (English), 11/10/2021 14:55:44, 5681280 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvdevtools.dll, 30.00.0014.7242 (English), 11/10/2021 14:56:14, 4541048 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvdevtoolsr.dll, 30.00.0014.7242 (English), 11/10/2021 14:56:16, 232568 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvdisps.dll, 30.00.0014.7242 (English), 11/10/2021 14:56:20, 11598456 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvdispsr.dll, 30.00.0014.7242 (English), 11/10/2021 14:56:22, 11318904 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvgames.dll, 30.00.0014.7242 (English), 11/10/2021 14:56:42, 12337272 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvgamesr.dll, 30.00.0014.7242 (English), 11/10/2021 14:56:44, 12541560 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvlicensings.dll, 6.14.0014.7242 (English), 11/10/2021 14:57:24, 4541072 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvlicensingsr.dll, 6.14.0014.7242 (English), 11/10/2021 14:57:28, 290960 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvshext.dll, 1.02.0000.0001 (English), 11/10/2021 14:59:44, 129168 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvsmartmax.dll, 6.14.0010.10003 (English), 11/10/2021 14:59:44, 203904 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvsmartmax64.dll, 6.14.0010.10003 (English), 11/10/2021 14:59:46, 243344 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvsmartmaxapp.exe, 6.14.0010.10003 (English), 11/10/2021 14:59:48, 273536 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvsmartmaxapp64.exe, 6.14.0010.10003 (English), 11/10/2021 14:59:50, 283792 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvsvc64.dll, 30.00.0014.7242 (English), 11/10/2021 14:59:52, 2649216 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvsvcr.dll, 30.00.0014.7242 (English), 11/10/2021 14:59:54, 1767040 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvsvs.dll, 30.00.0014.7242 (English), 11/10/2021 14:59:54, 5058688 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvsvsr.dll, 30.00.0014.7242 (English), 11/10/2021 14:59:56, 1946256 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvui.dll, 8.17.0014.7242 (English), 11/10/2021 15:00:00, 6629504 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvuir.dll, 8.17.0014.7242 (English), 11/10/2021 15:00:04, 2572944 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvvitvs.dll, 30.00.0014.7242 (English), 11/10/2021 15:00:10, 7403136 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvvitvsr.dll, 30.00.0014.7242 (English), 11/10/2021 15:00:10, 4112000 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvwss.dll, 30.00.0014.7242 (English), 11/10/2021 15:00:16, 12073088 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvwssr.dll, 30.00.0014.7242 (English), 11/10/2021 15:00:18, 9345680 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvxdapix.dll, 8.17.0014.7242 (English), 11/10/2021 15:00:20, 9204864 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvxdbat.dll, 8.17.0014.7242 (English), 11/10/2021 15:00:24, 1618576 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvxdplcy.dll, 8.17.0014.7242 (English), 11/10/2021 15:00:30, 1872016 bytes Driver: C:\Windows\system32\lxss\lib\libcuda.so, 10/21/2021 00:51:22, 141464 bytes Driver: C:\Windows\system32\lxss\lib\libcuda.so.1, 10/21/2021 00:51:22, 141464 bytes Driver: C:\Windows\system32\lxss\lib\libcuda.so.1.1, 10/21/2021 00:51:22, 141464 bytes Driver: C:\Windows\system32\lxss\lib\libnvcuvid.so.1, 10/21/2021 00:51:22, 6175952 bytes Driver: C:\Windows\system32\lxss\lib\libnvidia-encode.so.1, 10/21/2021 00:51:22, 424448 bytes Driver: C:\Windows\system32\lxss\lib\libnvidia-ml.so.1, 10/21/2021 00:51:22, 197496 bytes Driver: C:\Windows\system32\lxss\lib\libnvidia-opticalflow.so.1, 10/21/2021 00:51:22, 354816 bytes Driver: C:\Windows\system32\lxss\lib\libnvwgf2umx.so, 10/21/2021 00:51:22, 49668400 bytes Driver: C:\Windows\system32\lxss\lib\nvidia-smi, 10/21/2021 00:51:22, 678392 bytes Driver: C:\Windows\system32\DRIVERS\NVIDIA Corporation\license.txt, 7/12/2021 19:32:32, 28827 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\NvCamera\FreqTransfer32.exe, 11/10/2021 15:01:10, 3700864 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\NvCamera\FreqTransfer64.exe, 11/10/2021 15:01:12, 4000896 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\NvCamera\GreenScreenBG01.jpg, 10/21/2021 00:51:22, 281528 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\NvCamera\GreenScreenBG02.jpg, 10/21/2021 00:51:22, 499736 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\NvCamera\HighresBlender32.exe, 11/10/2021 15:01:12, 3802240 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\NvCamera\HighresBlender64.exe, 11/10/2021 15:01:14, 4098688 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\NvCamera\NvCamera32.dll, 7.01.0774.0783 (English), 11/10/2021 15:01:14, 8055952 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\NvCamera\NvCamera64.dll, 7.01.0774.0783 (English), 11/10/2021 15:01:16, 8699512 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\NvCamera\NvCameraAllowlisting32.dll, 7.01.0774.0783 (English), 11/10/2021 15:01:16, 558200 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\NvCamera\NvCameraAllowlisting64.dll, 7.01.0774.0783 (English), 11/10/2021 15:01:18, 702584 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\NvCamera\NvCameraEnable.exe, 11/10/2021 15:01:20, 370832 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\NvCamera\NvImageConvert32.exe, 11/10/2021 15:01:20, 3705464 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\NvCamera\NvImageConvert64.exe, 11/10/2021 15:01:22, 3984504 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\NvCamera\ReShadeFXC32.exe, 2.00.0000.0000 (English), 11/10/2021 15:01:22, 772216 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\NvCamera\ReShadeFXC64.exe, 2.00.0000.0000 (English), 11/10/2021 15:01:24, 887928 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\NvCamera\ShotWithGeforce518x32.rgba, 10/21/2021 00:51:22, 66304 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\NvCamera\SphericalEquirect32.exe, 11/10/2021 15:01:26, 3674256 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\NvCamera\SphericalEquirect64.exe, 11/10/2021 15:01:26, 3921552 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\NvCamera\Sticker01.png, 10/21/2021 00:51:22, 49695 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\NvCamera\Sticker02.png, 10/21/2021 00:51:22, 474002 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\NvCamera\Sticker03.png, 10/21/2021 00:51:22, 380006 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\NvCamera\Sticker04.png, 10/21/2021 00:51:22, 86881 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\NvCamera\Sticker05.png, 10/21/2021 00:51:22, 59304 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\NvCamera\Sticker06.png, 10/21/2021 00:51:22, 13547 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\NvCamera\Sticker07.png, 10/21/2021 00:51:22, 6342 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\NvCamera\Sticker08.png, 10/21/2021 00:51:22, 96493 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\NvCamera\YAMLFXC32.exe, 11/10/2021 15:01:28, 1764984 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\NvCamera\YAMLFXC64.exe, 11/10/2021 15:01:30, 1932920 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\NvCamera\d3dcompiler_47_32.dll, 6.03.9600.16384 (English), 11/10/2021 15:01:08, 3466872 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\NvCamera\d3dcompiler_47_64.dll, 6.03.9600.16384 (English), 11/10/2021 15:01:10, 4173952 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\NvCamera\filternames.cfg, 10/21/2021 00:51:22, 13976 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\NvCamera\fxtools.cfg, 10/21/2021 00:51:22, 81 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\NvCamera\scratches.jpg, 10/21/2021 00:51:22, 346354 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\NvCamera\tools_licenses.txt, 10/21/2021 00:51:22, 17234 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\NvCamera\ui.tga, 10/21/2021 00:51:22, 120236 bytes Driver: C:\Windows\system32\MCU.exe, 1.01.5204.20580 (English), 11/10/2021 14:55:08, 849040 bytes Driver: C:\Windows\system32\nvdebugdump.exe, 6.14.0014.7242 (English), 11/10/2021 14:56:10, 281720 bytes Driver: C:\Windows\system32\nvidia-smi.exe, 8.17.0014.7242 (English), 11/10/2021 14:56:52, 706168 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvopencl32.dll, 30.00.0014.7242 (English), 11/10/2021 14:58:06, 13500032 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvopencl64.dll, 30.00.0014.7242 (English), 11/10/2021 14:58:12, 15710328 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvcompiler32.dll, 30.00.0014.7242 (English), 11/10/2021 14:55:20, 41371792 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvcompiler64.dll, 30.00.0014.7242 (English), 11/10/2021 14:55:34, 46108800 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvlddmkm.sys, 30.00.0014.7242 (English), 11/10/2021 14:57:16, 37494928 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\libcuda.so.1.1, 10/21/2021 00:51:22, 17688904 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\libcuda_loader.so, 10/21/2021 00:51:22, 141464 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\libnvcuvid.so.1, 10/21/2021 00:51:22, 6175952 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\libnvidia-encode.so.1, 10/21/2021 00:51:22, 424448 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\libnvidia-ml.so.1, 10/21/2021 00:51:22, 1824024 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\libnvidia-ml_loader.so, 10/21/2021 00:51:22, 197496 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\libnvidia-opticalflow.so.1, 10/21/2021 00:51:22, 354816 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\libnvidia-ptxjitcompiler.so.1, 10/21/2021 00:51:22, 11144344 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\libnvwgf2umx.so, 10/21/2021 00:51:22, 49668400 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nv-vk64.json, 10/21/2021 00:51:22, 671 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvDecMFTMjpeg.dll, 30.00.0014.7242 (English), 11/10/2021 14:56:12, 604280 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvDecMFTMjpegx.dll, 30.00.0014.7242 (English), 11/10/2021 14:56:12, 747128 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvEncMFTH264.dll, 30.00.0014.7242 (English), 11/10/2021 14:56:26, 1137280 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvEncMFTH264x.dll, 30.00.0014.7242 (English), 11/10/2021 14:56:28, 1449080 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvEncMFThevc.dll, 30.00.0014.7242 (English), 11/10/2021 14:56:32, 1143416 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvEncMFThevcx.dll, 30.00.0014.7242 (English), 11/10/2021 14:56:32, 1458296 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvcbl64.dll, 30.00.0014.7242 (English), 11/10/2021 14:55:14, 688272 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvcuda32.dll, 30.00.0014.7242 (English), 11/10/2021 14:55:46, 16035456 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvcuda64.dll, 30.00.0014.7242 (English), 11/10/2021 14:55:52, 18506880 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvd3dumx.dll, 30.00.0014.7242 (English), 11/10/2021 14:54:26, 26208944 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvd3dumx_cfg.dll, 30.00.0014.7242 (English), 11/10/2021 14:54:34, 26456752 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvdlistx.dll, 30.00.0014.7242 (English), 11/10/2021 14:54:50, 216128 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvidia-smi, 10/21/2021 00:51:22, 678392 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvldumdx.dll, 30.00.0014.7242 (English), 11/10/2021 14:54:54, 1056272 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvml.dll, 8.17.0014.7242 (English), 11/10/2021 14:57:30, 1121936 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvoglv64.dll, 30.00.0014.7242 (English), 11/10/2021 14:57:54, 44924544 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvoptix.dll, 7.04.0000.0000 (English), 11/10/2021 14:58:26, 233661560 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvptxJitCompiler32.dll, 30.00.0014.7242 (English), 11/10/2021 14:59:08, 7744120 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvptxJitCompiler64.dll, 30.00.0014.7242 (English), 11/10/2021 14:59:12, 8795280 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvrtum64.dll, 30.00.0014.7242 (English), 11/10/2021 14:59:20, 76675728 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvvm64_40_0.dll, 6.14.0011.9000 (English), 11/10/2021 15:00:12, 17700480 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvwgf2umx.dll, 30.00.0014.7242 (English), 11/10/2021 14:55:10, 77954344 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvwgf2umx_cfg.dll, 30.00.0014.7242 (English), 11/10/2021 14:55:34, 78365720 bytes Driver: C:\Windows\system32\NvFBC64.dll, 6.14.0014.7242 (English), 11/10/2021 14:56:40, 2112120 bytes Driver: C:\Windows\system32\NvIFR64.dll, 6.14.0014.7242 (English), 11/10/2021 14:57:08, 1520784 bytes Driver: C:\Windows\system32\NvIFROpenGL.dll, 30.00.0014.7242 (English), 11/10/2021 14:57:10, 676496 bytes Driver: C:\Windows\system32\OpenCL.dll, 3.00.0001.0000 (English), 11/10/2021 15:00:38, 1474688 bytes Driver: C:\Windows\system32\nvEncodeAPI64.dll, 30.00.0014.7242 (English), 11/10/2021 14:56:36, 919160 bytes Driver: C:\Windows\system32\nvapi64.dll, 30.00.0014.7242 (English), 11/10/2021 14:54:14, 7281400 bytes Driver: C:\Windows\system32\nvcuda.dll, 30.00.0014.7242 (English), 11/10/2021 14:56:00, 2925696 bytes Driver: C:\Windows\system32\nvcuvid.dll, 7.17.0014.7242 (English), 11/10/2021 14:56:06, 8854136 bytes Driver: C:\Windows\system32\nvinfo.pb, 10/21/2021 00:51:22, 83362 bytes Driver: C:\Windows\system32\nvml.dll, 8.17.0014.7242 (English), 11/10/2021 14:57:32, 644728 bytes Driver: C:\Windows\system32\nvofapi64.dll, 11/10/2021 14:57:42, 716928 bytes Driver: C:\Windows\system32\vulkan-1-999-0-0-0.dll, 1.02.0198.0001 (English), 2/7/2022 13:47:46, 1323760 bytes Driver: C:\Windows\system32\vulkan-1.dll, 1.02.0198.0001 (English), 2/7/2022 13:47:46, 1323760 bytes Driver: C:\Windows\system32\vulkaninfo-1-999-0-0-0.exe, 1.02.0198.0001 (English), 2/7/2022 13:47:48, 1887392 bytes Driver: C:\Windows\system32\vulkaninfo.exe, 1.02.0198.0001 (English), 2/7/2022 13:47:48, 1887392 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nv-vk32.json, 10/21/2021 00:51:22, 671 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvIccAdvancedColorIdentity.icm, 10/21/2021 00:51:22, 3288 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvd3dum.dll, 30.00.0014.7242 (English), 11/10/2021 14:54:18, 22412848 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvd3dum_cfg.dll, 30.00.0014.7242 (English), 11/10/2021 14:54:42, 22799864 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvdispco64.exe, 1.00.0016.0000 (English), 11/10/2021 14:56:18, 1550456 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvdlist.dll, 30.00.0014.7242 (English), 11/10/2021 14:54:50, 181792 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvldumd.dll, 30.00.0014.7242 (English), 11/10/2021 14:54:52, 880648 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvoglv32.dll, 30.00.0014.7242 (English), 11/10/2021 14:57:44, 33889408 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvwgf2um.dll, 30.00.0014.7242 (English), 11/10/2021 14:54:58, 33609112 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\nvwgf2um_cfg.dll, 30.00.0014.7242 (English), 11/10/2021 14:55:52, 34224736 bytes Driver: C:\Windows\SysWow64\NvFBC.dll, 6.14.0014.7242 (English), 11/10/2021 14:56:38, 1595536 bytes Driver: C:\Windows\SysWow64\NvIFR.dll, 6.14.0014.7242 (English), 11/10/2021 14:57:06, 1171088 bytes Driver: C:\Windows\SysWow64\NvIFROpenGL.dll, 30.00.0014.7242 (English), 11/10/2021 14:57:10, 564368 bytes Driver: C:\Windows\SysWow64\OpenCL.dll, 3.00.0001.0000 (English), 11/10/2021 15:00:34, 1212560 bytes Driver: C:\Windows\SysWow64\nvEncodeAPI.dll, 30.00.0014.7242 (English), 11/10/2021 14:56:34, 750200 bytes Driver: C:\Windows\SysWow64\nvapi.dll, 30.00.0014.7242 (English), 11/10/2021 14:54:10, 6216832 bytes Driver: C:\Windows\SysWow64\nvcuda.dll, 30.00.0014.7242 (English), 11/10/2021 14:55:58, 4987536 bytes Driver: C:\Windows\SysWow64\nvcuvid.dll, 7.17.0014.7242 (English), 11/10/2021 14:56:04, 7920760 bytes Driver: C:\Windows\SysWow64\nvofapi.dll, 11/10/2021 14:57:40, 577152 bytes Driver: C:\Windows\SysWow64\vulkan-1-999-0-0-0.dll, 1.02.0198.0001 (English), 2/7/2022 13:47:44, 1043176 bytes Driver: C:\Windows\SysWow64\vulkan-1.dll, 1.02.0198.0001 (English), 2/7/2022 13:47:44, 1043176 bytes Driver: C:\Windows\SysWow64\vulkaninfo-1-999-0-0-0.exe, 1.02.0198.0001 (English), 2/7/2022 13:47:48, 1464992 bytes Driver: C:\Windows\SysWow64\vulkaninfo.exe, 1.02.0198.0001 (English), 2/7/2022 13:47:48, 1464992 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b5483682397e38df\NvTelemetry64.dll, 14.03.0060.0000 (English), 11/10/2021 14:59:58, 4465048 bytes Name: Intel(R) Thermal Subsystem - 06F9 Device ID: PCI\VEN_8086&DEV_06F9&SUBSYS_22A417AA&REV_00\3&11583659&0&90 Driver: n/a Name: PCI Express Upstream Switch Port Device ID: PCI\VEN_8086&DEV_15E7&SUBSYS_22A617AA&REV_06\UC725F10005C9A00000 Driver: C:\Windows\system32\DRIVERS\pci.sys, 10.00.19041.1387 (English), 12/15/2021 11:46:59, 469840 bytes Name: Intel(R) Serial IO I2C Host Controller - 06E8 Device ID: PCI\VEN_8086&DEV_06E8&SUBSYS_22A417AA&REV_00\3&11583659&0&A8 Driver: C:\Windows\system32\DRIVERS\iaLPSS2i_I2C_CNL.sys, 30.100.1929.0001 (English), 12/7/2019 11:07:47, 177152 bytes Name: Intel(R) Management Engine Interface #1 Device ID: PCI\VEN_8086&DEV_06E0&SUBSYS_22A417AA&REV_00\3&11583659&0&B0 Driver: C:\Windows\System32\DriverStore\FileRepository\heci.inf_amd64_b8b95f256704d781\x64\TeeDriverW10x64.sys, 2120.100.0000.1085 (English), 12/1/2021 17:52:18, 317984 bytes Name: PCI Express Downstream Switch Port Device ID: PCI\VEN_8086&DEV_15EF&SUBSYS_00008086&REV_06\F342D49922C9A00020 Driver: C:\Windows\system32\DRIVERS\pci.sys, 10.00.19041.1387 (English), 12/15/2021 11:46:59, 469840 bytes Name: PCI Express Downstream Switch Port Device ID: PCI\VEN_8086&DEV_15EF&SUBSYS_00008086&REV_06\F342D49922C9A00010 Driver: C:\Windows\system32\DRIVERS\pci.sys, 10.00.19041.1387 (English), 12/15/2021 11:46:59, 469840 bytes Name: Intel(R) UHD Graphics Device ID: PCI\VEN_8086&DEV_9BC4&SUBSYS_22A617AA&REV_05\3&11583659&0&10 Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igdkmd64.sys, 30.00.0101.1122 (English), 11/23/2021 21:34:54, 31102528 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\iglhxs64.vp, 11/23/2021 21:03:14, 5900 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igd10iumd64.dll, 30.00.0101.1122 (English), 11/23/2021 21:35:16, 26977304 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igd11dxva64.dll, 30.00.0101.1122 (English), 11/23/2021 21:35:24, 78035952 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igd12dxva64.dll, 30.00.0101.1122 (English), 11/23/2021 21:35:34, 77726928 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igd12umd64.dll, 30.00.0101.1122 (English), 11/23/2021 21:35:48, 10398384 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igd12um64ldr.dll, 30.00.0101.1122 (English), 11/23/2021 21:35:42, 154264 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igd12um64icl.dll, 11/23/2021 21:35:42, 10672672 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igd12um64xel.dll, 11/23/2021 21:35:44, 10796128 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igdgmm64.dll, 30.00.0101.1122 (English), 11/23/2021 21:36:04, 4056016 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igfxcmrt64.dll, 30.00.0101.1122 (English), 11/23/2021 21:36:16, 224552 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igfx11cmrt64.dll, 30.00.0101.1122 (English), 11/23/2021 21:36:16, 227712 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igdumdim64.dll, 30.00.0101.1122 (English), 11/23/2021 21:36:14, 1486352 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igdail64.dll, 11/23/2021 21:34:52, 202536 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igd9dxva64.dll, 30.00.0101.1122 (English), 11/23/2021 21:35:54, 64426040 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\iga64.dll, 30.00.0101.1122 (English), 11/23/2021 21:35:06, 3010896 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igc64.dll, 30.00.0101.1122 (English), 11/23/2021 21:35:12, 56172440 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\SPIRVDLL.dll, 11/23/2021 21:35:52, 3506488 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\DnnlPlugin.dll, 11/23/2021 21:35:04, 50155800 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\UniversalAdapter64.dll, 11/23/2021 21:37:12, 355936 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\opencl-clang64.dll, 2.00.0009.0000 (English), 11/23/2021 21:37:08, 83482464 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igdfcl64.dll, 30.00.0101.1122 (English), 11/23/2021 21:36:02, 1072192 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igdmd64.dll, 30.00.0101.1122 (English), 11/23/2021 21:36:08, 6300456 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igdml64.dll, 30.00.0101.1122 (English), 11/23/2021 21:36:12, 4355432 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igdde64.dll, 30.00.0101.1122 (English), 11/23/2021 21:35:56, 430680 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igdinfo64.dll, 11/23/2021 21:36:06, 165784 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igdext64.dll, 30.00.0101.1122 (English), 11/23/2021 21:36:00, 301432 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igd10iumd32.dll, 30.00.0101.1122 (English), 11/23/2021 21:35:14, 22637040 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igd11dxva32.dll, 30.00.0101.1122 (English), 11/23/2021 21:35:20, 76646944 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igd12dxva32.dll, 30.00.0101.1122 (English), 11/23/2021 21:35:28, 76354712 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igd12umd32.dll, 30.00.0101.1122 (English), 11/23/2021 21:35:46, 10119688 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igd12um32ldr.dll, 30.00.0101.1122 (English), 11/23/2021 21:35:38, 116160 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igd12um32icl.dll, 11/23/2021 21:35:34, 10178432 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igd12um32xel.dll, 11/23/2021 21:35:40, 10327840 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igdgmm32.dll, 30.00.0101.1122 (English), 11/23/2021 21:36:02, 3184040 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igdumdim32.dll, 30.00.0101.1122 (English), 11/23/2021 21:36:12, 1330200 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igdail32.dll, 11/23/2021 21:34:50, 166696 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igd9dxva32.dll, 30.00.0101.1122 (English), 11/23/2021 21:35:50, 63079168 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igfxcmrt32.dll, 30.00.0101.1122 (English), 11/23/2021 21:36:16, 180976 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igfx11cmrt32.dll, 30.00.0101.1122 (English), 11/23/2021 21:36:14, 182496 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\iga32.dll, 30.00.0101.1122 (English), 11/23/2021 21:35:06, 2412656 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igc32.dll, 30.00.0101.1122 (English), 11/23/2021 21:35:10, 47703872 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\SPIRVDLL32.dll, 11/23/2021 21:35:54, 2715440 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\UniversalAdapter32.dll, 11/23/2021 21:37:10, 295312 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\opencl-clang32.dll, 2.00.0009.0000 (English), 11/23/2021 21:37:04, 61948456 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igdfcl32.dll, 30.00.0101.1122 (English), 11/23/2021 21:34:52, 971104 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igdmd32.dll, 30.00.0101.1122 (English), 11/23/2021 21:36:08, 5135864 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igdml32.dll, 30.00.0101.1122 (English), 11/23/2021 21:36:10, 3173504 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igdde32.dll, 30.00.0101.1122 (English), 11/23/2021 21:35:56, 349616 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igdinfo32.dll, 11/23/2021 21:36:06, 139728 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igdext32.dll, 30.00.0101.1122 (English), 11/23/2021 21:36:00, 244464 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\libigd12umd64.so, 11/23/2021 21:03:16, 4508480 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\libigd12um64icl.so, 11/23/2021 21:03:16, 4650800 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\libigd12um64xel.so, 11/23/2021 21:03:16, 4906688 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\libigc.so, 11/23/2021 21:03:16, 41000880 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\libLLVM-9.so, 11/23/2021 21:03:16, 38562040 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\libigdgmm.so.11, 11/23/2021 21:03:16, 2267744 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\libUniversalAdapter64.so, 11/23/2021 21:03:20, 510032 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\libigdfcl.so, 11/23/2021 21:03:16, 972592 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\libopencl-clang.so.9, 11/23/2021 21:03:20, 80933576 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\libwsl_compute_helper.so, 11/23/2021 21:03:20, 501840 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\iglhxo64.vp, 11/23/2021 21:03:14, 42513 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\iglhxc64.vp, 11/23/2021 21:03:14, 44194 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\iglhxg64.vp, 11/23/2021 21:03:14, 43760 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\iglhxo64_dev.vp, 11/23/2021 21:03:14, 43143 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\iglhxc64_dev.vp, 11/23/2021 21:03:14, 43214 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\iglhxg64_dev.vp, 11/23/2021 21:03:14, 43732 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\iglhxa64.vp, 11/23/2021 21:03:14, 1125 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\iglhxa64.cpa, 11/23/2021 21:03:14, 1376256 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\IntelCpHDCPSvc.exe, 30.00.0101.1122 (English), 11/23/2021 21:35:28, 344584 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\cp_resources.bin, 11/23/2021 21:03:00, 2572396 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\ig9icd64.dll, 30.00.0101.1122 (English), 11/23/2021 21:34:46, 16793384 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\ig9icd32.dll, 30.00.0101.1122 (English), 11/23/2021 21:34:46, 13401440 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\OSSCOPYRIGHT.txt, 11/23/2021 21:03:22, 1372 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igvk64.dll, 30.00.0101.1122 (English), 11/23/2021 21:36:24, 21977336 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igvk64.json, 11/23/2021 21:03:14, 135 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\VulkanRT-EULA.txt, 11/23/2021 21:03:24, 4008 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igvk32.dll, 30.00.0101.1122 (English), 11/23/2021 21:36:22, 19889272 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igvk32.json, 11/23/2021 21:03:14, 135 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\vulkan-1-64.dll, 1.02.0176.0001 (English), 11/23/2021 21:35:56, 1115616 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\vulkaninfo-64.exe, 1.02.0176.0001 (English), 11/23/2021 21:36:00, 1870336 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\vulkan-1-32.dll, 1.02.0176.0001 (English), 11/23/2021 21:35:56, 969208 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\vulkaninfo-32.exe, 1.02.0176.0001 (English), 11/23/2021 21:35:58, 1450008 bytes Driver: C:\Windows\SysWow64\vulkan-1.dll, 1.02.0198.0001 (English), 2/7/2022 13:47:44, 1043176 bytes Driver: C:\Windows\SysWow64\vulkaninfo.exe, 1.02.0198.0001 (English), 2/7/2022 13:47:48, 1464992 bytes Driver: C:\Windows\SysWow64\vulkan-1-999-0-0-0.dll, 1.02.0198.0001 (English), 2/7/2022 13:47:44, 1043176 bytes Driver: C:\Windows\SysWow64\vulkaninfo-1-999-0-0-0.exe, 1.02.0198.0001 (English), 2/7/2022 13:47:48, 1464992 bytes Driver: C:\Windows\system32\vulkan-1.dll, 1.02.0198.0001 (English), 2/7/2022 13:47:46, 1323760 bytes Driver: C:\Windows\system32\vulkaninfo.exe, 1.02.0198.0001 (English), 2/7/2022 13:47:48, 1887392 bytes Driver: C:\Windows\system32\vulkan-1-999-0-0-0.dll, 1.02.0198.0001 (English), 2/7/2022 13:47:46, 1323760 bytes Driver: C:\Windows\system32\vulkaninfo-1-999-0-0-0.exe, 1.02.0198.0001 (English), 2/7/2022 13:47:48, 1887392 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\Intel_OpenCL_ICD32.dll, 2.02.0008.0000 (English), 11/23/2021 21:35:32, 370472 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igdrcl32.dll, 23.20.0101.1122 (English), 11/23/2021 21:35:00, 5138216 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\Intel_OpenCL_ICD64.dll, 2.02.0008.0000 (English), 11/23/2021 21:35:34, 508752 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\ze_loader.dll, 1.05.0004.0000 (English), 11/23/2021 21:36:02, 378136 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\ze_validation_layer.dll, 1.05.0004.0000 (English), 11/23/2021 21:36:04, 148760 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\ze_tracing_layer.dll, 1.05.0004.0000 (English), 11/23/2021 21:36:02, 459032 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\ControlLib.dll, 1.00.0046.0000 (English), 11/23/2021 21:35:00, 464664 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\igdrcl64.dll, 23.20.0101.1122 (English), 11/23/2021 21:35:02, 5830952 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\ze_intel_gpu64.dll, 1.02.0000.0000 (English), 11/23/2021 21:36:00, 4611864 bytes Driver: C:\Windows\SysWow64\OpenCL.dll, 3.00.0001.0000 (English), 11/10/2021 15:00:34, 1212560 bytes Driver: C:\Windows\system32\OpenCL.dll, 3.00.0001.0000 (English), 11/10/2021 15:00:38, 1474688 bytes Driver: C:\Windows\system32\ze_loader.dll, 1.05.0004.0000 (English), 11/23/2021 21:36:02, 378136 bytes Driver: C:\Windows\system32\ze_validation_layer.dll, 1.05.0004.0000 (English), 11/23/2021 21:36:04, 148760 bytes Driver: C:\Windows\system32\ze_tracing_layer.dll, 1.05.0004.0000 (English), 11/23/2021 21:36:02, 459032 bytes Driver: C:\Windows\system32\ControlLib.dll, 1.00.0046.0000 (English), 11/23/2021 21:35:00, 464664 bytes Driver: C:\Windows\SysWow64\libmfxhw32.dll, 21.10.0018.0311 (English), 11/23/2021 21:36:40, 717952 bytes Driver: C:\Windows\SysWow64\mfxplugin32_hw.dll, 21.10.0018.0311 (English), 11/23/2021 21:35:36, 20639032 bytes Driver: C:\Windows\system32\libmfxhw64.dll, 21.12.0028.0359 (English), 2/7/2022 13:48:26, 943472 bytes Driver: C:\Windows\system32\mfxplugin64_hw.dll, 21.10.0018.0311 (English), 11/23/2021 21:35:38, 27897704 bytes Driver: C:\Windows\system32\intel_gfx_api-x64.dll, 21.10.0018.0311 (English), 11/23/2021 21:36:24, 601888 bytes Driver: C:\Windows\system32\libvpl.dll, 2.05.0000.0000 (English), 11/23/2021 21:37:14, 513224 bytes Driver: C:\Windows\SysWow64\intel_gfx_api-x86.dll, 21.10.0018.0311 (English), 11/23/2021 21:36:26, 460888 bytes Driver: C:\Windows\SysWow64\libvpl.dll, 2.05.0000.0000 (English), 11/23/2021 21:37:14, 445440 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\mfxplugin64_hw.dll, 21.10.0018.0311 (English), 11/23/2021 21:35:38, 27897704 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\mfxplugin64_av1e_gacc.dll, 3.11.0005.0020 (English), 11/23/2021 21:36:38, 12606216 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\intel_gfx_api-x64.dll, 21.10.0018.0311 (English), 11/23/2021 21:36:24, 601888 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\mfxplugin32_hw.dll, 21.10.0018.0311 (English), 11/23/2021 21:35:36, 20639032 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\mfxplugin32_av1e_gacc.dll, 3.11.0005.0020 (English), 11/23/2021 21:36:38, 8648608 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\intel_gfx_api-x86.dll, 21.10.0018.0311 (English), 11/23/2021 21:36:26, 460888 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\mfx_mft_h264ve_32.dll, 21.10.0018.0311 (English), 11/23/2021 21:36:50, 2499816 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\mfx_mft_mjpgvd_32.dll, 21.10.0018.0311 (English), 11/23/2021 21:35:40, 2355560 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\mfx_mft_h265ve_32.dll, 21.10.0018.0311 (English), 11/23/2021 21:36:54, 2513584 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\mfx_mft_vp9ve_32.dll, 21.10.0018.0311 (English), 11/23/2021 21:36:58, 2508888 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\mfx_mft_encrypt_32.dll, 21.10.0018.0311 (English), 11/23/2021 21:36:46, 2362744 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\mfx_mft_av1hve_32.dll, 21.10.0018.0311 (English), 11/23/2021 21:36:42, 2509376 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\c_32.cpa, 11/23/2021 21:03:00, 1361159 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\cpa_32.vp, 11/23/2021 21:03:00, 1125 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\dev_32.vp, 11/23/2021 21:03:00, 57143 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\he_32.vp, 11/23/2021 21:03:00, 73957 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\mj_32.vp, 11/23/2021 21:03:20, 69537 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\h265e_32.vp, 11/23/2021 21:03:00, 75625 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\vp9e_32.vp, 11/23/2021 21:03:24, 75152 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\mfx_mft_av1hve_32.vp, 11/23/2021 21:03:20, 75205 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\mfx_mft_h264ve_64.dll, 21.10.0018.0311 (English), 11/23/2021 21:36:52, 3038168 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\mfx_mft_mjpgvd_64.dll, 21.10.0018.0311 (English), 11/23/2021 21:35:42, 2862384 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\mfx_mft_h265ve_64.dll, 21.10.0018.0311 (English), 11/23/2021 21:36:56, 3058040 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\mfx_mft_vp9ve_64.dll, 21.10.0018.0311 (English), 11/23/2021 21:36:58, 3051896 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\mfx_mft_encrypt_64.dll, 21.10.0018.0311 (English), 11/23/2021 21:36:48, 2869896 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\mfx_mft_av1hve_64.dll, 21.10.0018.0311 (English), 11/23/2021 21:36:44, 3053448 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\c_64.cpa, 11/23/2021 21:03:00, 1376256 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\cpa_64.vp, 11/23/2021 21:03:00, 1125 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\dev_64.vp, 11/23/2021 21:03:00, 56359 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\he_64.vp, 11/23/2021 21:03:00, 13067 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\mj_64.vp, 11/23/2021 21:03:20, 12775 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\h265e_64.vp, 11/23/2021 21:03:00, 13691 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\vp9e_64.vp, 11/23/2021 21:03:24, 13506 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\mfx_mft_av1hve_64.vp, 11/23/2021 21:03:20, 13475 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\libmfxhw64.dll, 21.10.0018.0311 (English), 11/23/2021 21:36:36, 29157768 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\libmfxhw32.dll, 21.10.0018.0311 (English), 11/23/2021 21:36:34, 27560032 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_6091bde938afd934\IntelCpHeciSvc.exe, 9.02.0001.0920 (English), 11/23/2021 21:35:30, 521224 bytes Name: Citrix Indirect Display Adapter Device ID: PCI\VEN_5853&DEV_1003\1&79F5D87&0&03 Driver: C:\Windows\system32\DRIVERS\UMDF\vidd.dll, 7.21.0000.0183 (English), 4/14/2020 06:39:38, 85624 bytes Name: Realtek PCIE CardReader Device ID: PCI\VEN_10EC&DEV_525A&SUBSYS_22A417AA&REV_01\00000001004CE00000 Driver: C:\Windows\system32\DRIVERS\RtsPer.sys, 10.00.19042.21344 (English), 2/19/2021 17:49:32, 1366408 bytes Driver: C:\Windows\SysWOW64\RsCRIcon.dll, 1.10.0000.0000 (English), 2/19/2021 17:49:32, 9916296 bytes Name: Intel(R) Active Management Technology - SOL (COM3) Device ID: PCI\VEN_8086&DEV_06E3&SUBSYS_22A417AA&REV_00\3&11583659&0&B3 Driver: n/a Name: Intel(R) SPI (flash) Controller - 06A4 Device ID: PCI\VEN_8086&DEV_06A4&SUBSYS_22A417AA&REV_00\3&11583659&0&FD Driver: n/a Name: Intel(R) LPC Controller (WM490) - 068E Device ID: PCI\VEN_8086&DEV_068E&SUBSYS_22A417AA&REV_00\3&11583659&0&F8 Driver: C:\Windows\system32\DRIVERS\msisadrv.sys, 10.00.19041.1202 (English), 9/15/2021 11:00:49, 20280 bytes Name: Intel(R) Shared SRAM - 06EF Device ID: PCI\VEN_8086&DEV_06EF&SUBSYS_22A417AA&REV_00\3&11583659&0&A2 Driver: n/a Name: Thunderbolt(TM) Controller - 15E8 Device ID: PCI\VEN_8086&DEV_15E8&SUBSYS_22A617AA&REV_06\C725F10005C9A00000 Driver: C:\Windows\system32\DRIVERS\TbtBusDrv.sys, 1.41.1193.0000 (English), 7/14/2021 13:19:10, 2991240 bytes Driver: C:\Windows\system32\DRIVERS\UMDF\TbtFilterDrv.dll, 1.41.1193.0000 (English), 7/14/2021 13:19:14, 283784 bytes Driver: C:\Windows\TbtP2pShortcutService.exe, 1.41.1193.0000 (English), 7/14/2021 13:19:22, 254112 bytes Name: Intel(R) USB 3.1 eXtensible Host Controller - 1.10 (Microsoft) Device ID: PCI\VEN_8086&DEV_15F0&SUBSYS_00008086&REV_06\F342D49922C9A00000 Driver: C:\Windows\system32\DRIVERS\USBXHCI.SYS, 10.00.19041.1566 (English), 3/9/2022 10:40:44, 624976 bytes Driver: C:\Windows\system32\DRIVERS\UMDF\UsbXhciCompanion.dll, 10.00.19041.1566 (English), 3/9/2022 10:40:44, 138976 bytes Name: Intel(R) Ethernet Connection (11) I219-LM Device ID: PCI\VEN_8086&DEV_0D4C&SUBSYS_22B817AA&REV_00\3&11583659&0&FE Driver: C:\Windows\System32\DriverStore\FileRepository\e1d68x64.inf_amd64_7b6bb8abbc171f0a\e1d68x64.sys, 12.18.0009.0020 (English), 2/25/2020 18:34:14, 610536 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\e1d68x64.inf_amd64_7b6bb8abbc171f0a\e1dmsg.dll, 10.00.0911.0001 (English), 2/25/2020 18:34:16, 127720 bytes Name: Intel(R) Dynamic Tuning Processor Participant Device ID: PCI\VEN_8086&DEV_1903&SUBSYS_22A417AA&REV_02\3&11583659&0&20 Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\esif_lf.sys, 8.07.10600.20700 (English), 3/17/2021 16:10:36, 423064 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\dptf_cpu.sys, 8.07.10600.20700 (English), 3/17/2021 16:10:34, 73368 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\esif_uf.exe, 8.07.10600.20700 (English), 3/17/2021 16:10:38, 2301592 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\esif_umdf2.dll, 8.07.10600.20700 (English), 3/17/2021 16:10:38, 1011352 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\Dptf.dll, 8.07.10600.20700 (English), 3/17/2021 16:10:10, 2490008 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\DptfPolicyRfim.dll, 8.07.10600.20700 (English), 3/17/2021 16:10:26, 813720 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\DptfPolicyActive.dll, 8.07.10600.20700 (English), 3/17/2021 16:10:10, 826520 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\DptfPolicyActive2.dll, 8.07.10600.20700 (English), 3/17/2021 16:10:12, 1008808 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\DptfPolicyEnergyPerformanceOptimizer.dll, 8.07.10600.20700 (English), 3/17/2021 16:10:16, 882840 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\DptfPolicyAdaptiveUserPresence.dll, 8.07.10600.20700 (English), 3/17/2021 16:10:14, 1046696 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\DptfPolicyAdaptivePerformance.dll, 8.07.10600.20700 (English), 3/17/2021 16:10:12, 1203368 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\DptfPolicyCritical.dll, 8.07.10600.20700 (English), 3/17/2021 16:10:14, 803992 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\DptfPolicyIntelligentThermalManagement.dll, 8.07.10600.20700 (English), 3/17/2021 16:10:16, 974488 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\DptfPolicyPassive.dll, 8.07.10600.20700 (English), 3/17/2021 16:10:18, 1136296 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\DptfPolicyPassive2.dll, 8.07.10600.20700 (English), 3/17/2021 16:10:18, 1084072 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\DptfPolicyPid.dll, 8.07.10600.20700 (English), 3/17/2021 16:10:20, 983704 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\DptfPolicyPowerBoss.dll, 8.07.10600.20700 (English), 3/17/2021 16:10:22, 1419928 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\DptfPolicyVirtualSensor.dll, 8.07.10600.20700 (English), 3/17/2021 16:10:28, 982168 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\DptfPolicyPowerShare.dll, 8.07.10600.20700 (English), 3/17/2021 16:10:22, 967832 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\DptfPolicyPowerShare2.dll, 8.07.10600.20700 (English), 3/17/2021 16:10:24, 986264 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\DptfPolicySystemConfiguration.dll, 8.07.10600.20700 (English), 3/17/2021 16:10:26, 772248 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\upe_wwan.dll, 8.07.10600.20700 (English), 3/17/2021 16:10:46, 133272 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\upe_wifi.dll, 8.07.10600.20700 (English), 3/17/2021 16:10:46, 67224 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\upe_nvme.dll, 8.07.10600.20700 (English), 3/17/2021 16:10:44, 114840 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\upe_battery.dll, 8.07.10600.20700 (English), 3/17/2021 16:10:42, 71832 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\upe_socwc.dll, 8.07.10600.20700 (English), 3/17/2021 16:10:44, 225432 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\upe_hwpf.dll, 8.07.10600.20700 (English), 3/17/2021 16:10:42, 74392 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\dptf_helper.exe, 8.07.10600.20700 (English), 3/17/2021 16:10:34, 549016 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\esif_cmp.dll, 8.07.10600.20700 (English), 3/17/2021 16:10:36, 138392 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\ipftcs.dll, 8.07.10600.20700 (English), 3/17/2021 16:10:40, 1686408 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\dsp.dv, 3/17/2021 16:01:00, 894845 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\ppm.dv, 3/17/2021 16:01:00, 7608 bytes Name: Intel(R) Serial IO I2C Host Controller - 06E9 Device ID: PCI\VEN_8086&DEV_06E9&SUBSYS_22A417AA&REV_00\3&11583659&0&A9 Driver: C:\Windows\system32\DRIVERS\iaLPSS2i_I2C_CNL.sys, 30.100.1929.0001 (English), 12/7/2019 11:07:47, 177152 bytes Name: Intel(R) USB 3.1 eXtensible Host Controller - 1.10 (Microsoft) Device ID: PCI\VEN_8086&DEV_06ED&SUBSYS_22A417AA&REV_00\3&11583659&0&A0 Driver: C:\Windows\system32\DRIVERS\USBXHCI.SYS, 10.00.19041.1566 (English), 3/9/2022 10:40:44, 624976 bytes Driver: C:\Windows\system32\DRIVERS\UMDF\UsbXhciCompanion.dll, 10.00.19041.1566 (English), 3/9/2022 10:40:44, 138976 bytes Name: Intel(R) USB 3.1 eXtensible Host Controller - 1.10 (Microsoft) Device ID: PCI\VEN_8086&DEV_15E9&SUBSYS_22A617AA&REV_06\C725F10005C9A00000 Driver: C:\Windows\system32\DRIVERS\USBXHCI.SYS, 10.00.19041.1566 (English), 3/9/2022 10:40:44, 624976 bytes Driver: C:\Windows\system32\DRIVERS\UMDF\UsbXhciCompanion.dll, 10.00.19041.1566 (English), 3/9/2022 10:40:44, 138976 bytes Name: Standard NVM Express Controller Device ID: PCI\VEN_15B7&DEV_5006&SUBSYS_500615B7&REV_00\4&5A7B3F&0&00E8 Driver: C:\Windows\system32\DRIVERS\stornvme.sys, 10.00.19041.1566 (English), 3/9/2022 10:40:44, 162128 bytes Name: PCI standard host CPU bridge Device ID: PCI\VEN_8086&DEV_9B54&SUBSYS_22A417AA&REV_02\3&11583659&0&00 Driver: n/a Name: Intel(R) PCIe Controller (x16) - 1901 Device ID: PCI\VEN_8086&DEV_1901&SUBSYS_22A417AA&REV_02\3&11583659&0&08 Driver: C:\Windows\system32\DRIVERS\pci.sys, 10.00.19041.1387 (English), 12/15/2021 11:46:59, 469840 bytes Name: Intel(R) PCI Express Root Port #1 - 06B8 Device ID: PCI\VEN_8086&DEV_06B8&SUBSYS_22A417AA&REV_F0\3&11583659&0&E0 Driver: C:\Windows\system32\DRIVERS\pci.sys, 10.00.19041.1387 (English), 12/15/2021 11:46:59, 469840 bytes Name: Intel(R) PCI Express Root Port #9 - 06B0 Device ID: PCI\VEN_8086&DEV_06B0&SUBSYS_22A417AA&REV_F0\3&11583659&0&E8 Driver: C:\Windows\system32\DRIVERS\pci.sys, 10.00.19041.1387 (English), 12/15/2021 11:46:59, 469840 bytes Name: Synaptics SMBus Driver Device ID: PCI\VEN_8086&DEV_06A3&SUBSYS_22A417AA&REV_00\3&11583659&0&FC Driver: C:\Windows\system32\DRIVERS\Smb_driver_Intel.sys, 19.05.0019.0089 (English), 9/27/2021 01:11:48, 44048 bytes Name: Intel(R) Wi-Fi 6 AX201 160MHz Device ID: PCI\VEN_8086&DEV_06F0&SUBSYS_00708086&REV_00\3&11583659&0&A3 Driver: C:\Windows\system32\DRIVERS\Netwtw10.sys, 22.110.0001.0001 (English), 1/8/2022 21:55:08, 4955248 bytes Driver: C:\Windows\system32\DRIVERS\Netwfw10.dat, 1/8/2022 21:55:08, 45101144 bytes Driver: C:\Windows\system32\IntelIHVRouter08.dll, 22.12100.0000.0001 (English), 1/8/2022 21:55:08, 1622088 bytes Name: Intel(R) Gaussian Mixture Model - 1911 Device ID: PCI\VEN_8086&DEV_1911&SUBSYS_22A417AA&REV_00\3&11583659&0&40 Driver: n/a Name: Intel(R) Smart Sound Technology (Intel(R) SST) Audio Controller Device ID: PCI\VEN_8086&DEV_06C8&SUBSYS_22A417AA&REV_00\3&11583659&0&FB Driver: C:\Windows\System32\DriverStore\FileRepository\intcaudiobus.inf_amd64_6a5bfce36da7fb0f\IntcAudioBus.sys, 10.24.0000.5427 (English), 4/29/2021 04:19:44, 302840 bytes Driver: C:\Windows\system32\DRIVERS\drmk.sys, 10.00.19041.0746 (English), 5/4/2021 17:15:13, 97792 bytes Driver: C:\Windows\system32\DRIVERS\portcls.sys, 10.00.19041.0746 (English), 5/4/2021 17:15:13, 388608 bytes Name: PCI Express Upstream Switch Port Device ID: PCI\VEN_8086&DEV_15EF&SUBSYS_00008086&REV_06\UF342D49922C9A00000 Driver: C:\Windows\system32\DRIVERS\pci.sys, 10.00.19041.1387 (English), 12/15/2021 11:46:59, 469840 bytes ------------------ DirectShow Filters ------------------ DirectShow Filters: WMAudio Decoder DMO,0x00800800,1,1,WMADMOD.DLL,10.00.19041.1288 WMAPro over S/PDIF DMO,0x00600800,1,1,WMADMOD.DLL,10.00.19041.1288 WMSpeech Decoder DMO,0x00600800,1,1,WMSPDMOD.DLL,10.00.19041.0001 MP3 Decoder DMO,0x00600800,1,1,mp3dmod.dll,10.00.19041.0001 Mpeg4s Decoder DMO,0x00800001,1,1,mp4sdecd.dll,10.00.19041.0450 WMV Screen decoder DMO,0x00600800,1,1,wmvsdecd.dll,10.00.19041.0001 WMVideo Decoder DMO,0x00800001,1,1,wmvdecod.dll,10.00.19041.1110 Mpeg43 Decoder DMO,0x00800001,1,1,mp43decd.dll,10.00.19041.1165 Mpeg4 Decoder DMO,0x00800001,1,1,mpg4decd.dll,10.00.19041.1165 Xiph.Org Vorbis Decoder,0x00600000,1,1,dsfVorbisDecoder.dll, DV Muxer,0x00400000,0,0,qdv.dll,10.00.19041.0001 Color Space Converter,0x00400001,1,1,quartz.dll,10.00.19041.0746 WM ASF Reader,0x00400000,0,0,qasf.dll,12.00.19041.0001 AVI Splitter,0x00600000,1,1,quartz.dll,10.00.19041.0746 VGA 16 Color Ditherer,0x00400000,1,1,quartz.dll,10.00.19041.0746 SBE2MediaTypeProfile,0x00200000,0,0,sbe.dll,10.00.19041.0001 Microsoft DTV-DVD Video Decoder,0x005fffff,2,4,msmpeg2vdec.dll,10.00.19041.1566 AC3 Parser Filter,0x00600000,1,1,mpg2splt.ax,10.00.19041.0329 StreamBufferSink,0x00200000,0,0,sbe.dll,10.00.19041.0001 MJPEG Decompressor,0x00600000,1,1,quartz.dll,10.00.19041.0746 MPEG-I Stream Splitter,0x00600000,1,2,quartz.dll,10.00.19041.0746 Xiph.Org FLAC Decoder,0x00600000,1,1,dsfFLACDecoder.dll, SAMI (CC) Parser,0x00400000,1,1,quartz.dll,10.00.19041.0746 VBI Codec,0x00600000,1,4,VBICodec.ax,10.00.19041.0746 MPEG-2 Splitter,0x005fffff,1,0,mpg2splt.ax,10.00.19041.0329 Closed Captions Analysis Filter,0x00200000,2,5,cca.dll,10.00.19041.0001 SBE2FileScan,0x00200000,0,0,sbe.dll,10.00.19041.0001 Microsoft MPEG-2 Video Encoder,0x00200000,1,1,msmpeg2enc.dll,10.00.19041.0001 Internal Script Command Renderer,0x00800001,1,0,quartz.dll,10.00.19041.0746 MPEG Audio Decoder,0x03680001,1,1,quartz.dll,10.00.19041.0746 DV Splitter,0x00600000,1,2,qdv.dll,10.00.19041.0001 Video Mixing Renderer 9,0x00200000,1,0,quartz.dll,10.00.19041.0746 Microsoft MPEG-2 Encoder,0x00200000,2,1,msmpeg2enc.dll,10.00.19041.0001 ACM Wrapper,0x00600000,1,1,quartz.dll,10.00.19041.0746 Video Renderer,0x00800001,1,0,quartz.dll,10.00.19041.0746 MPEG-2 Video Stream Analyzer,0x00200000,0,0,sbe.dll,10.00.19041.0001 Xiph.Org Native FLAC Decoder,0x00600000,0,1,dsfNativeFLACSource.dll, Line 21 Decoder,0x00600000,1,1,, Video Port Manager,0x00600000,2,1,quartz.dll,10.00.19041.0746 Video Renderer,0x00400000,1,0,quartz.dll,10.00.19041.0746 VPS Decoder,0x00200000,0,0,WSTPager.ax,10.00.19041.0001 WM ASF Writer,0x00400000,0,0,qasf.dll,12.00.19041.0001 VBI Surface Allocator,0x00600000,1,1,vbisurf.ax, File writer,0x00200000,1,0,qcap.dll,10.00.19041.0001 Bandicam MPEG-1 Video Decoder,0xff800001,1,1,bdfilters64.dll,1.00.0005.0017 DVD Navigator,0x00200000,0,3,qdvd.dll,10.00.19041.0746 Overlay Mixer2,0x00200000,1,1,, AVI Draw,0x00600064,9,1,quartz.dll,10.00.19041.0746 Microsoft MPEG-2 Audio Encoder,0x00200000,1,1,msmpeg2enc.dll,10.00.19041.0001 WST Pager,0x00200000,1,1,WSTPager.ax,10.00.19041.0001 MPEG-2 Demultiplexer,0x00600000,1,1,mpg2splt.ax,10.00.19041.0329 DV Video Decoder,0x00800000,1,1,qdv.dll,10.00.19041.0001 SampleGrabber,0x00200000,1,1,qedit.dll,10.00.19041.0746 Null Renderer,0x00200000,1,0,qedit.dll,10.00.19041.0746 MPEG-2 Sections and Tables,0x005fffff,1,0,Mpeg2Data.ax,10.00.19041.0001 Microsoft AC3 Encoder,0x00200000,1,1,msac3enc.dll,10.00.19041.0001 Xiph.Org Ogg Demuxer,0x00600000,1,1,dsfOggDemux2.dll, StreamBufferSource,0x00200000,0,0,sbe.dll,10.00.19041.0001 Smart Tee,0x00200000,1,2,qcap.dll,10.00.19041.0001 Overlay Mixer,0x00200000,0,0,, AVI Decompressor,0x00600000,1,1,quartz.dll,10.00.19041.0746 AVI/WAV File Source,0x00400000,0,2,quartz.dll,10.00.19041.0746 Wave Parser,0x00400000,1,1,quartz.dll,10.00.19041.0746 MIDI Parser,0x00400000,1,1,quartz.dll,10.00.19041.0746 Multi-file Parser,0x00400000,1,1,quartz.dll,10.00.19041.0746 File stream renderer,0x00400000,1,1,quartz.dll,10.00.19041.0746 Microsoft DTV-DVD Audio Decoder,0x005fffff,1,1,msmpeg2adec.dll,10.00.19041.0001 StreamBufferSink2,0x00200000,0,0,sbe.dll,10.00.19041.0001 AVI Mux,0x00200000,1,0,qcap.dll,10.00.19041.0001 Bandicam MPEG-1 Audio Decoder,0xff800001,1,1,bdfilters64.dll,1.00.0005.0017 Line 21 Decoder 2,0x00600002,1,1,quartz.dll,10.00.19041.0746 File Source (Async.),0x00400000,0,1,quartz.dll,10.00.19041.0746 File Source (URL),0x00400000,0,1,quartz.dll,10.00.19041.0746 Infinite Pin Tee Filter,0x00200000,1,1,qcap.dll,10.00.19041.0001 Enhanced Video Renderer,0x00200000,1,0,evr.dll,10.00.19041.0546 BDA MPEG2 Transport Information Filter,0x00200000,2,0,psisrndr.ax,10.00.19041.0001 MPEG Video Decoder,0x40000001,1,1,quartz.dll,10.00.19041.0746 WDM Streaming Tee/Splitter Devices: Tee/Sink-to-Sink Converter,0x00200000,1,1,ksproxy.ax,10.00.19041.0746 Video Compressors: WMVideo8 Encoder DMO,0x00600800,1,1,wmvxencd.dll,10.00.19041.0867 WMVideo9 Encoder DMO,0x00600800,1,1,wmvencod.dll,10.00.19041.0001 MSScreen 9 encoder DMO,0x00600800,1,1,wmvsencd.dll,10.00.19041.0001 DV Video Encoder,0x00200000,0,0,qdv.dll,10.00.19041.0001 MJPEG Compressor,0x00200000,0,0,quartz.dll,10.00.19041.0746 Audio Compressors: WM Speech Encoder DMO,0x00600800,1,1,WMSPDMOE.DLL,10.00.19041.0508 WMAudio Encoder DMO,0x00600800,1,1,WMADMOE.DLL,10.00.19041.0508 IMA ADPCM,0x00200000,1,1,quartz.dll,10.00.19041.0746 PCM,0x00200000,1,1,quartz.dll,10.00.19041.0746 Microsoft ADPCM,0x00200000,1,1,quartz.dll,10.00.19041.0746 GSM 6.10,0x00200000,1,1,quartz.dll,10.00.19041.0746 CCITT A-Law,0x00200000,1,1,quartz.dll,10.00.19041.0746 CCITT u-Law,0x00200000,1,1,quartz.dll,10.00.19041.0746 MP2,0x00200000,1,1,quartz.dll,10.00.19041.0746 MPEG Layer-3,0x00200000,1,1,quartz.dll,10.00.19041.0746 Audio Capture Sources: Microphone Array (Realtek(R) Audio),0x00200000,0,0,qcap.dll,10.00.19041.0001 PBDA CP Filters: PBDA DTFilter,0x00600000,1,1,CPFilters.dll,10.00.19041.1566 PBDA ETFilter,0x00200000,0,0,CPFilters.dll,10.00.19041.1566 PBDA PTFilter,0x00200000,0,0,CPFilters.dll,10.00.19041.1566 Midi Renderers: Default MidiOut Device,0x00800000,1,0,quartz.dll,10.00.19041.0746 Microsoft GS Wavetable Synth,0x00200000,1,0,quartz.dll,10.00.19041.0746 WDM Streaming Capture Devices: Logi Webcam C920e,0x00200000,1,1,ksproxy.ax,10.00.19041.0746 ,0x00000000,0,0,, ,0x00000000,0,0,, Realtek HD Audio Mic input with SST,0x00200000,1,3,ksproxy.ax,10.00.19041.0746 ,0x00000000,0,0,, Mic in at rear panel (black),0x00200000,1,1,ksproxy.ax,10.00.19041.0746 ThinkPad Thunderbolt 3 Dock USB Audio Device,0x00200000,2,2,ksproxy.ax,10.00.19041.0746 Integrated Camera,0x00200000,1,1,ksproxy.ax,10.00.19041.0746 WDM Streaming Rendering Devices: Realtek HD Audio 2nd output with SST,0x00200000,2,2,ksproxy.ax,10.00.19041.0746 Realtek HD Audio output with SST,0x00200000,2,2,ksproxy.ax,10.00.19041.0746 ,0x00000000,0,0,, ThinkPad Thunderbolt 3 Dock USB Audio Device,0x00200000,2,2,ksproxy.ax,10.00.19041.0746 ,0x00200000,1,1,, BDA Network Providers: Microsoft ATSC Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.19041.0001 Microsoft DVBC Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.19041.0001 Microsoft DVBS Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.19041.0001 Microsoft DVBT Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.19041.0001 Microsoft Network Provider,0x00200000,0,1,MSNP.ax,10.00.19041.0001 Video Capture Sources: Logi Webcam C920e,0x00200000,1,1,ksproxy.ax,10.00.19041.0746 Integrated Camera,0x00200000,1,1,ksproxy.ax,10.00.19041.0746 Multi-Instance Capable VBI Codecs: VBI Codec,0x00600000,1,4,VBICodec.ax,10.00.19041.0746 BDA Transport Information Renderers: BDA MPEG2 Transport Information Filter,0x00600000,2,0,psisrndr.ax,10.00.19041.0001 MPEG-2 Sections and Tables,0x00600000,1,0,Mpeg2Data.ax,10.00.19041.0001 WDM Streaming Communication Transforms: Tee/Sink-to-Sink Converter,0x00200000,1,1,ksproxy.ax,10.00.19041.0746 Audio Renderers: Speakers (Realtek(R) Audio),0x00200000,1,0,quartz.dll,10.00.19041.0746 Default DirectSound Device,0x00800000,1,0,quartz.dll,10.00.19041.0746 Default WaveOut Device,0x00200000,1,0,quartz.dll,10.00.19041.0746 DirectSound: Speakers (Realtek(R) Audio),0x00200000,1,0,quartz.dll,10.00.19041.0746 ---------------------------- Preferred DirectShow Filters ---------------------------- [HKEY_LOCAL_MACHINE\Software\Microsoft\DirectShow\Preferred] , [, ] MEDIASUBTYPE_DVD_LPCM_AUDIO, Microsoft DTV-DVD Audio Decoder, CLSID_CMPEG2AudDecoderDS MEDIASUBTYPE_MPEG2_AUDIO, Microsoft DTV-DVD Audio Decoder, CLSID_CMPEG2AudDecoderDS MEDIASUBTYPE_MPEG2_VIDEO, Microsoft DTV-DVD Video Decoder, CLSID_CMPEG2VidDecoderDS {78766964-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject {7634706D-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject MEDIASUBTYPE_mp4s, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject {64697678-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject {58564944-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject {5634504D-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject MEDIASUBTYPE_MP4S, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject MEDIASUBTYPE_WMVR, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject MEDIASUBTYPE_WMVP, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject {44495658-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject MEDIASUBTYPE_WMVA, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject MEDIASUBTYPE_mpg4, Mpeg4 Decoder DMO, CLSID_CMpeg4DecMediaObject MEDIASUBTYPE_MPG4, Mpeg4 Decoder DMO, CLSID_CMpeg4DecMediaObject MEDIASUBTYPE_h264, Microsoft DTV-DVD Video Decoder, CLSID_CMPEG2VidDecoderDS MEDIASUBTYPE_H264, Microsoft DTV-DVD Video Decoder, CLSID_CMPEG2VidDecoderDS MEDIASUBTYPE_WMV3, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject MEDIASUBTYPE_mp43, Mpeg43 Decoder DMO, CLSID_CMpeg43DecMediaObject MEDIASUBTYPE_MP43, Mpeg43 Decoder DMO, CLSID_CMpeg43DecMediaObject MEDIASUBTYPE_m4s2, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject MEDIASUBTYPE_WMV2, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject MEDIASUBTYPE_MSS2, WMV Screen decoder DMO, CLSID_CMSSCDecMediaObject MEDIASUBTYPE_M4S2, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject MEDIASUBTYPE_WVP2, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject MEDIASUBTYPE_mp42, Mpeg4 Decoder DMO, CLSID_CMpeg4DecMediaObject MEDIASUBTYPE_MP42, Mpeg4 Decoder DMO, CLSID_CMpeg4DecMediaObject MEDIASUBTYPE_WMV1, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject MEDIASUBTYPE_MSS1, WMV Screen decoder DMO, CLSID_CMSSCDecMediaObject MEDIASUBTYPE_WVC1, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject MEDIASUBTYPE_AVC1, Microsoft DTV-DVD Video Decoder, CLSID_CMPEG2VidDecoderDS MEDIASUBTYPE_MPEG_LOAS, Microsoft DTV-DVD Audio Decoder, CLSID_CMPEG2AudDecoderDS MEDIASUBTYPE_MPEG_ADTS_AAC, Microsoft DTV-DVD Audio Decoder, CLSID_CMPEG2AudDecoderDS MEDIASUBTYPE_WMAUDIO_LOSSLESS, WMAudio Decoder DMO, CLSID_CWMADecMediaObject MEDIASUBTYPE_WMAUDIO3, WMAudio Decoder DMO, CLSID_CWMADecMediaObject WMMEDIASUBTYPE_WMAudioV8, WMAudio Decoder DMO, CLSID_CWMADecMediaObject MEDIASUBTYPE_MSAUDIO1, WMAudio Decoder DMO, CLSID_CWMADecMediaObject MEDIASUBTYPE_RAW_AAC1, Microsoft DTV-DVD Audio Decoder, CLSID_CMPEG2AudDecoderDS WMMEDIASUBTYPE_MP3, MP3 Decoder DMO, CLSID_CMP3DecMediaObject MEDIASUBTYPE_MPEG1Payload, MPEG Video Decoder, CLSID_CMpegVideoCodec MEDIASUBTYPE_MPEG1Packet, MPEG Video Decoder, CLSID_CMpegVideoCodec {6C737664-0000-0010-8000-00AA00389B71}, DV Video Decoder, CLSID_DVVideoCodec {64737664-0000-0010-8000-00AA00389B71}, DV Video Decoder, CLSID_DVVideoCodec {64687664-0000-0010-8000-00AA00389B71}, DV Video Decoder, CLSID_DVVideoCodec MEDIASUBTYPE_MJPG, MJPEG Decompressor, CLSID_MjpegDec {20637664-0000-0010-8000-00AA00389B71}, DV Video Decoder, CLSID_DVVideoCodec MEDIASUBTYPE_MPEG1AudioPayload, MPEG Audio Decoder, CLSID_CMpegAudioCodec WMMEDIASUBTYPE_WMSP2, WMSpeech Decoder DMO, CLSID_CWMSPDecMediaObject WMMEDIASUBTYPE_WMSP1, WMSpeech Decoder DMO, CLSID_CWMSPDecMediaObject --------------------------- Media Foundation File Versions --------------------------- mfcore.dll, 10.00.19041.1586 mfreadwrite.dll, 10.00.19041.0746 mfcaptureengine.dll, 10.00.19041.0906 mfsensorgroup.dll, 10.00.19041.1503 windows.media.dll, 10.00.19041.1566 frameserver.dll, 10.00.19041.1503 frameserverclient.dll, 10.00.19041.1503 --------------------------- Media Foundation Transforms --------------------------- [HKEY_LOCAL_MACHINE\Software\Classes\MediaFoundation\Transforms] : , , , [, ], Video Decoders: Intel� Hardware M-JPEG Decoder MFT, {00C69F81-0524-48C0-A353-4DD9D54F9A6E}, 0x6, 7, mfx_mft_mjpgvd_64.dll, 21.10.0018.0311 NVIDIA MJPEG Video Decoder MFT, {70F36578-2741-454F-B494-E8563DDD1CB4}, 0x4, 8, nvDecMFTMjpegx.dll, 30.00.0014.7242 Intel� Hardware M-JPEG Decoder MFT, {00C69F81-0524-48C0-A353-4DD9D54F9A6E}, 0x6, 7, mfx_mft_mjpgvd_64.dll, 21.10.0018.0311 Microsoft MPEG Video Decoder MFT, {2D709E52-123F-49B5-9CBC-9AF5CDE28FB9}, 0x1, msmpeg2vdec.dll, 10.00.19041.1566 DV Decoder MFT, {404A6DE5-D4D6-4260-9BC7-5A6CBD882432}, 0x1, mfdvdec.dll, 10.00.19041.0001 Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT, 0x1, mp4sdecd.dll, 10.00.19041.0450 Microsoft H264 Video Decoder MFT, CLSID_CMSH264DecoderMFT, 0x1, msmpeg2vdec.dll, 10.00.19041.1566 WMV Screen decoder MFT, CLSID_CMSSCDecMediaObject, 0x1, wmvsdecd.dll, 10.00.19041.0001 WMVideo Decoder MFT, CLSID_CWMVDecMediaObject, 0x1, wmvdecod.dll, 10.00.19041.1110 MJPEG Decoder MFT, {CB17E772-E1CC-4633-8450-5617AF577905}, 0x1, mfmjpegdec.dll, 10.00.19041.1348 Mpeg43 Decoder MFT, CLSID_CMpeg43DecMediaObject, 0x1, mp43decd.dll, 10.00.19041.1165 Mpeg4 Decoder MFT, CLSID_CMpeg4DecMediaObject, 0x1, mpg4decd.dll, 10.00.19041.1165 WebpImageExtension VP9VideoExtensionDecoder HEIFImageExtension Video Encoders: Intel� Quick Sync Video H.264 Encoder MFT, {4BE8D3C0-0515-4A37-AD55-E4BAE19AF471}, 0x4, 7, mfx_mft_h264ve_64.dll, 21.10.0018.0311 NVIDIA H.264 Encoder MFT, {60F44560-5A20-4857-BFEF-D29773CB8040}, 0x4, 8, nvEncMFTH264x.dll, 30.00.0014.7242 NVIDIA HEVC Encoder MFT, {966F107C-8EA2-425D-B822-E4A71BEF01D7}, 0x4, 8, nvEncMFThevcx.dll, 30.00.0014.7242 Intel� Hardware H265 Encoder MFT, {BC10864D-2B34-408F-912A-102B1B867B6C}, 0x4, 7, mfx_mft_h265ve_64.dll, 21.10.0018.0311 Intel� Quick Sync Video H.264 Encoder MFT, {4BE8D3C0-0515-4A37-AD55-E4BAE19AF471}, 0x4, 7, mfx_mft_h264ve_64.dll, 21.10.0018.0311 Intel� Hardware H265 Encoder MFT, {BC10864D-2B34-408F-912A-102B1B867B6C}, 0x4, 7, mfx_mft_h265ve_64.dll, 21.10.0018.0311 H264 Encoder MFT, {6CA50344-051A-4DED-9779-A43305165E35}, 0x1, mfh264enc.dll, 10.00.19041.1566 WMVideo8 Encoder MFT, CLSID_CWMVXEncMediaObject, 0x1, wmvxencd.dll, 10.00.19041.0867 H263 Encoder MFT, {BC47FCFE-98A0-4F27-BB07-698AF24F2B38}, 0x1, mfh263enc.dll, 10.00.19041.0001 WMVideo9 Encoder MFT, CLSID_CWMV9EncMediaObject, 0x1, wmvencod.dll, 10.00.19041.0001 Microsoft MPEG-2 Video Encoder MFT, {E6335F02-80B7-4DC4-ADFA-DFE7210D20D5}, 0x2, msmpeg2enc.dll, 10.00.19041.0001 VP9VideoExtensionEncoder HEIFImageExtension Video Effects: Frame Rate Converter, CLSID_CFrameRateConvertDmo, 0x1, mfvdsp.dll, 10.00.19041.0746 Resizer MFT, CLSID_CResizerDMO, 0x1, vidreszr.dll, 10.00.19041.0867 VideoStabilization MFT, {51571744-7FE4-4FF2-A498-2DC34FF74F1B}, 0x1, MSVideoDSP.dll, 10.00.19041.0746 Color Control, CLSID_CColorControlDmo, 0x1, mfvdsp.dll, 10.00.19041.0746 Color Converter MFT, CLSID_CColorConvertDMO, 0x1, colorcnv.dll, 10.00.19041.1110 Video Processor: Microsoft Video Processor MFT, {88753B26-5B24-49BD-B2E7-0C445C78C982}, 0x1, msvproc.dll, 10.00.19041.1566 Audio Decoders: Microsoft Dolby Digital Plus Decoder MFT, {177C0AFE-900B-48D4-9E4C-57ADD250B3D4}, 0x1, DolbyDecMFT.dll, 10.00.19041.1586 MS AMRNB Decoder MFT, {265011AE-5481-4F77-A295-ABB6FFE8D63E}, 0x1, MSAMRNBDecoder.dll, 10.00.19041.0001 WMAudio Decoder MFT, CLSID_CWMADecMediaObject, 0x1, WMADMOD.DLL, 10.00.19041.1288 Microsoft AAC Audio Decoder MFT, CLSID_CMSAACDecMFT, 0x1, MSAudDecMFT.dll, 10.00.19041.1165 A-law Wrapper MFT, {36CB6E0C-78C1-42B2-9943-846262F31786}, 0x1, mfcore.dll, 10.00.19041.1586 GSM ACM Wrapper MFT, {4A76B469-7B66-4DD4-BA2D-DDF244C766DC}, 0x1, mfcore.dll, 10.00.19041.1586 WMAPro over S/PDIF MFT, CLSID_CWMAudioSpdTxDMO, 0x1, WMADMOD.DLL, 10.00.19041.1288 Microsoft Opus Audio Decoder MFT, {63E17C10-2D43-4C42-8FE3-8D8B63E46A6A}, 0x1, MSOpusDecoder.dll, 10.00.19041.0746 Microsoft FLAC Audio Decoder MFT, {6B0B3E6B-A2C5-4514-8055-AFE8A95242D9}, 0x1, MSFlacDecoder.dll, 10.00.19041.1566 Microsoft MPEG Audio Decoder MFT, {70707B39-B2CA-4015-ABEA-F8447D22D88B}, 0x1, MSAudDecMFT.dll, 10.00.19041.1165 WMSpeech Decoder DMO, CLSID_CWMSPDecMediaObject, 0x1, WMSPDMOD.DLL, 10.00.19041.0001 G711 Wrapper MFT, {92B66080-5E2D-449E-90C4-C41F268E5514}, 0x1, mfcore.dll, 10.00.19041.1586 IMA ADPCM ACM Wrapper MFT, {A16E1BFF-A80D-48AD-AECD-A35C005685FE}, 0x1, mfcore.dll, 10.00.19041.1586 MP3 Decoder MFT, CLSID_CMP3DecMediaObject, 0x1, mp3dmod.dll, 10.00.19041.0001 Microsoft ALAC Audio Decoder MFT, {C0CD7D12-31FC-4BBC-B363-7322EE3E1879}, 0x1, MSAlacDecoder.dll, 10.00.19041.0746 ADPCM ACM Wrapper MFT, {CA34FE0A-5722-43AD-AF23-05F7650257DD}, 0x1, mfcore.dll, 10.00.19041.1586 Dolby TrueHD IEC-61937 converter MFT, {CF5EEEDF-0E92-4B3B-A161-BD0FFE545E4B}, 0x1, mfaudiocnv.dll, 10.00.19041.0746 DTS IEC-61937 converter MFT, {D035E24C-C877-42D7-A795-2A8A339B472F}, 0x1, mfaudiocnv.dll, 10.00.19041.0746 Audio Encoders: LPCM DVD-Audio MFT, {068A8476-9229-4CC0-9D49-2FC699DCD30A}, 0x1, mfaudiocnv.dll, 10.00.19041.0746 MP3 Encoder ACM Wrapper MFT, {11103421-354C-4CCA-A7A3-1AFF9A5B6701}, 0x1, mfcore.dll, 10.00.19041.1586 Microsoft FLAC Audio Encoder MFT, {128509E9-C44E-45DC-95E9-C255B8F466A6}, 0x1, MSFlacEncoder.dll, 10.00.19041.0746 WM Speech Encoder DMO, CLSID_CWMSPEncMediaObject2, 0x1, WMSPDMOE.DLL, 10.00.19041.0508 MS AMRNB Encoder MFT, {2FAE8AFE-04A3-423A-A814-85DB454712B0}, 0x1, MSAMRNBEncoder.dll, 10.00.19041.0001 Microsoft MPEG-2 Audio Encoder MFT, {46A4DD5C-73F8-4304-94DF-308F760974F4}, 0x1, msmpeg2enc.dll, 10.00.19041.0001 WMAudio Encoder MFT, CLSID_CWMAEncMediaObject, 0x1, WMADMOE.DLL, 10.00.19041.0508 Microsoft AAC Audio Encoder MFT, {93AF0C51-2275-45D2-A35B-F2BA21CAED00}, 0x1, mfAACEnc.dll, 10.00.19041.0001 Microsoft ALAC Audio Encoder MFT, {9AB6A28C-748E-4B6A-BFFF-CC443B8E8FB4}, 0x1, MSAlacEncoder.dll, 10.00.19041.0746 Microsoft Dolby Digital Encoder MFT, {AC3315C9-F481-45D7-826C-0B406C1F64B8}, 0x1, msac3enc.dll, 10.00.19041.0001 Audio Effects: AEC, CLSID_CWMAudioAEC, 0x1, mfwmaaec.dll, 10.00.19041.0001 Resampler MFT, CLSID_CResamplerMediaObject, 0x1, resampledmo.dll, 10.00.19041.0001 Multiplexers: Microsoft MPEG2 Multiplexer MFT, {AB300F71-01AB-46D2-AB6C-64906CB03258}, 0x2, mfmpeg2srcsnk.dll, 10.00.19041.1566 Others: Microsoft H264 Video Remux (MPEG2TSToMP4) MFT, {05A47EBB-8BF0-4CBF-AD2F-3B71D75866F5}, 0x1, msmpeg2vdec.dll, 10.00.19041.1566 -------------------------------------------- Media Foundation Enabled Hardware Categories -------------------------------------------- [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows Media Foundation\HardwareMFT] EnableDecoders = 1 EnableEncoders = 1 ------------------------------------- Media Foundation Byte Stream Handlers ------------------------------------- [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows Media Foundation\ByteStreamHandlers] [HKEY_LOCAL_MACHINE\Software\Classes\MediaFoundation\MediaSources\Preferred] , , [, Preferred] .3g2, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .3gp, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .3gp2, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .3gpp, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .aac, {926F41F7-003E-4382-9E84-9E953BE10562}, ADTS Byte Stream Handler, Preferred .ac3, {46031BA1-083F-47D9-8369-23C92BDAB2FF}, AC-3 Byte Stream Handler, Preferred .adt, {926F41F7-003E-4382-9E84-9E953BE10562}, ADTS Byte Stream Handler, Preferred .adts, {926F41F7-003E-4382-9E84-9E953BE10562}, ADTS Byte Stream Handler, Preferred .am?, {EFE6208A-0A2C-49FA-8A01-3768B559B6DA}, MF AMRNB Media Source ByteStreamHandler .amr, {EFE6208A-0A2C-49FA-8A01-3768B559B6DA}, MF AMRNB Media Source ByteStreamHandler, Preferred .asf, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred .avi, {7AFA253E-F823-42F6-A5D9-714BDE467412}, AVI Byte Stream Handler, Preferred .dvr-ms, {A8721937-E2FB-4D7A-A9EE-4EB08C890B6E}, MF SBE Source ByteStreamHandler .dvr-ms, {65964407-A5D8-4060-85B0-1CCD63F768E2}, dvr-ms Byte Stream Handler, Preferred .ec3, {46031BA1-083F-47D9-8369-23C92BDAB2FF}, AC-3 Byte Stream Handler, Preferred .flac, {0E41CFB8-0506-40F4-A516-77CC23642D91}, MF FLAC Media Source ByteStreamHandler, Preferred .m2t, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .m2ts, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .m4a, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .m4v, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .mk3d, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, MKV Byte Stream Handler, Preferred .mka, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, MKV Byte Stream Handler, Preferred .mks, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, MKV Byte Stream Handler, Preferred .mkv, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, MKV Byte Stream Handler, Preferred .mod, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .mov, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .mp2v, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .mp3, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred .mp4, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .mp4v, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .mpa, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred .mpeg, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .mpg, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .mts, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .nsc, {B084785C-DDE0-4D30-8CA8-05A373E185BE}, NSC Byte Stream Handler, Preferred .sami, {7A56C4CB-D678-4188-85A8-BA2EF68FA10D}, SAMI Byte Stream Handler, Preferred .smi, {7A56C4CB-D678-4188-85A8-BA2EF68FA10D}, SAMI Byte Stream Handler, Preferred .tod, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .ts, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .tts, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .uvu, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .vob, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .wav, {42C9B9F5-16FC-47EF-AF22-DA05F7C842E3}, WAV Byte Stream Handler, Preferred .weba, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, WEBM Byte Stream Handler, Preferred .webm, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, WEBM Byte Stream Handler, Preferred .wm, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred .wma, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred .wmv, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred .wtv, {65964407-A5D8-4060-85B0-1CCD63F768E2}, WTV Byte Stream Handler, Preferred audio/3gpp, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred audio/3gpp2, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred audio/aac, {926F41F7-003E-4382-9E84-9E953BE10562}, ADTS Byte Stream Handler, Preferred audio/aacp, {926F41F7-003E-4382-9E84-9E953BE10562}, ADTS Byte Stream Handler, Preferred audio/eac3, {46031BA1-083F-47D9-8369-23C92BDAB2FF}, AC-3 Byte Stream Handler, Preferred audio/flac, {0E41CFB8-0506-40F4-A516-77CC23642D91}, MF FLAC Media Source ByteStreamHandler, Preferred audio/L16, {3FFB3B8C-EB99-472B-8902-E1C1B05F07CF}, LPCM Byte Stream Handler, Preferred audio/mp3, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred audio/mp4, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred audio/MP4A-LATM, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred audio/mpa, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred audio/mpeg, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred audio/mpeg3, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred audio/vnd.dlna.adts, {926F41F7-003E-4382-9E84-9E953BE10562}, ADTS Byte Stream Handler, Preferred audio/vnd.dolby.dd-raw, {46031BA1-083F-47D9-8369-23C92BDAB2FF}, AC-3 Byte Stream Handler, Preferred audio/wav, {42C9B9F5-16FC-47EF-AF22-DA05F7C842E3}, WAV Byte Stream Handler, Preferred audio/webm, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, WEBM Byte Stream Handler, Preferred audio/x-aac, {926F41F7-003E-4382-9E84-9E953BE10562}, ADTS Byte Stream Handler, Preferred audio/x-flac, {0E41CFB8-0506-40F4-A516-77CC23642D91}, MF FLAC Media Source ByteStreamHandler, Preferred audio/x-m4a, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred audio/x-matroska, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, MKV Byte Stream Handler, Preferred audio/x-mp3, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred audio/x-mpeg, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred audio/x-ms-wma, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred audio/x-wav, {42C9B9F5-16FC-47EF-AF22-DA05F7C842E3}, WAV Byte Stream Handler, Preferred video/3gpp, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred video/3gpp2, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred video/avi, {7AFA253E-F823-42F6-A5D9-714BDE467412}, AVI Byte Stream Handler, Preferred video/mp4, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred video/mpeg, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred video/msvideo, {7AFA253E-F823-42F6-A5D9-714BDE467412}, AVI Byte Stream Handler, Preferred video/vnd.dece.mp4, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred video/vnd.dlna.mpeg-tts, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred video/webm, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, WEBM Byte Stream Handler, Preferred video/x-m4v, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred video/x-matroska, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, MKV Byte Stream Handler, Preferred video/x-ms-asf, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred video/x-ms-wm, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred video/x-ms-wmv, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred video/x-msvideo, {7AFA253E-F823-42F6-A5D9-714BDE467412}, AVI Byte Stream Handler, Preferred -------------------------------- Media Foundation Scheme Handlers -------------------------------- [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows Media Foundation\SchemeHandlers] [HKEY_LOCAL_MACHINE\Software\Classes\MediaFoundation\MediaSources\Preferred] , , [, Preferred] file:, {477EC299-1421-4BDD-971F-7CCB933F21AD}, File Scheme Handler, Preferred http:, {44CB442B-9DA9-49DF-B3FD-023777B16E50}, Http Scheme Handler http:, {9EC4B4F9-3029-45AD-947B-344DE2A249E2}, Urlmon Scheme Handler http:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred httpd:, {44CB442B-9DA9-49DF-B3FD-023777B16E50}, Http Scheme Handler, Preferred https:, {37A61C8B-7F8E-4D08-B12B-248D73E9AB4F}, Secure Http Scheme Handler, Preferred httpsd:, {37A61C8B-7F8E-4D08-B12B-248D73E9AB4F}, Secure Http Scheme Handler, Preferred httpt:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred httpu:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred mcast:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred mcrecv:, {FA6D33D4-9405-4BA5-9983-12604AC8E77A}, Miracast Sink Scheme Handler, Preferred mms:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred ms-appdata:, {CFC81939-3886-4ACF-9692-DA58037AE716}, MsAppData Scheme Handler, Preferred ms-appx-web:, {8DB0224B-3D65-4F6F-8E12-BEB4B78B8974}, MsAppxWeb Scheme Handler, Preferred ms-appx:, {8DB0224B-3D65-4F6F-8E12-BEB4B78B8974}, MsAppx Scheme Handler, Preferred ms-winsoundevent:, {F79A6BF9-7415-4CF3-AE10-4559509ABC3C}, Sound Event Scheme Handler, Preferred rtsp:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred rtsps:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred rtspt:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred rtspu:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred sdp:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred ------------------------------------- Preferred Media Foundation Transforms ------------------------------------- [HKEY_LOCAL_MACHINE\Software\Classes\MediaFoundation\Transforms\Preferred] , [, ] {EB27CEC4-163E-4CA3-8B74-8E25F91B517E}, Dolby TrueHD IEC-61937 converter MFT, {CF5EEEDF-0E92-4B3B-A161-BD0FFE545E4B} {E06D802C-DB46-11CF-B4D1-00805F6CBBEA}, Microsoft Dolby Digital Plus Decoder MFT, {177C0AFE-900B-48D4-9E4C-57ADD250B3D4} MFVideoFormat_MPEG2, Microsoft MPEG Video Decoder MFT, {2D709E52-123F-49B5-9CBC-9AF5CDE28FB9} MEDIASUBTYPE_DOLBY_DDPLUS, Microsoft Dolby Digital Plus Decoder MFT, {177C0AFE-900B-48D4-9E4C-57ADD250B3D4} {A61AC364-AD0E-4744-89FF-213CE0DF8804}, DTS IEC-61937 converter MFT, {D035E24C-C877-42D7-A795-2A8A339B472F} {A2E58EB7-0FA9-48BB-A40C-FA0E156D0645}, DTS IEC-61937 converter MFT, {D035E24C-C877-42D7-A795-2A8A339B472F} {7634706D-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT {73616D72-767A-494D-B478-F29D25DC9037}, MS AMRNB Decoder MFT, {265011AE-5481-4F77-A295-ABB6FFE8D63E} MEDIASUBTYPE_mp4s, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT MFVideoFormat_DVSL, DV Decoder MFT, {404A6DE5-D4D6-4260-9BC7-5A6CBD882432} MFVideoFormat_DVSD, DV Decoder MFT, {404A6DE5-D4D6-4260-9BC7-5A6CBD882432} MFVideoFormat_DVHD, DV Decoder MFT, {404A6DE5-D4D6-4260-9BC7-5A6CBD882432} {63616C61-0000-0010-8000-00AA00389B71}, Microsoft ALAC Audio Decoder MFT, {C0CD7D12-31FC-4BBC-B363-7322EE3E1879} MFVideoFormat_MP4V, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT MFVideoFormat_MP4S, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT {53314356-0000-0010-8000-00AA00389B71}, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject MEDIASUBTYPE_WMVR, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject MEDIASUBTYPE_WMVP, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject MFVideoFormat_MJPG, MJPEG Decoder MFT, {CB17E772-E1CC-4633-8450-5617AF577905} MEDIASUBTYPE_WMVA, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject {3F40F4F0-5622-4FF8-B6D8-A17A584BEE5E}, Microsoft H264 Video Decoder MFT, CLSID_CMSH264DecoderMFT MEDIASUBTYPE_mpg4, Mpeg4 Decoder MFT, CLSID_CMpeg4DecMediaObject MEDIASUBTYPE_MPG4, Mpeg4 Decoder MFT, CLSID_CMpeg4DecMediaObject MFVideoFormat_H264, Microsoft H264 Video Decoder MFT, CLSID_CMSH264DecoderMFT MFVideoFormat_WMV3, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject {33363248-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT MEDIASUBTYPE_mp43, Mpeg43 Decoder MFT, CLSID_CMpeg43DecMediaObject MFVideoFormat_MP43, Mpeg43 Decoder MFT, CLSID_CMpeg43DecMediaObject MEDIASUBTYPE_m4s2, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT MFVideoFormat_WMV2, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject MFVideoFormat_MSS2, WMV Screen decoder MFT, CLSID_CMSSCDecMediaObject MFVideoFormat_M4S2, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT MEDIASUBTYPE_WVP2, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject MEDIASUBTYPE_mp42, Mpeg4 Decoder MFT, CLSID_CMpeg4DecMediaObject MEDIASUBTYPE_MP42, Mpeg4 Decoder MFT, CLSID_CMpeg4DecMediaObject MFVideoFormat_WMV1, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject MFVideoFormat_MSS1, WMV Screen decoder MFT, CLSID_CMSSCDecMediaObject MFVideoFormat_MPG1, Microsoft MPEG Video Decoder MFT, {2D709E52-123F-49B5-9CBC-9AF5CDE28FB9} MFVideoFormat_WVC1, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject MFVideoFormat_DVC, DV Decoder MFT, {404A6DE5-D4D6-4260-9BC7-5A6CBD882432} {0000F1AC-0000-0010-8000-00AA00389B71}, Microsoft FLAC Audio Decoder MFT, {6B0B3E6B-A2C5-4514-8055-AFE8A95242D9} {00007361-0000-0010-8000-00AA00389B71}, MS AMRNB Decoder MFT, {265011AE-5481-4F77-A295-ABB6FFE8D63E} {0000704F-0000-0010-8000-00AA00389B71}, Microsoft Opus Audio Decoder MFT, {63E17C10-2D43-4C42-8FE3-8D8B63E46A6A} {00006C61-0000-0010-8000-00AA00389B71}, Microsoft ALAC Audio Decoder MFT, {C0CD7D12-31FC-4BBC-B363-7322EE3E1879} {00002001-0000-0010-8000-00AA00389B71}, DTS IEC-61937 converter MFT, {D035E24C-C877-42D7-A795-2A8A339B472F} {00002000-0000-0010-8000-00AA00389B71}, Microsoft Dolby Digital Plus Decoder MFT, {177C0AFE-900B-48D4-9E4C-57ADD250B3D4} MFAudioFormat_AAC, Microsoft AAC Audio Decoder MFT, CLSID_CMSAACDecMFT MFAudioFormat_ADTS, Microsoft AAC Audio Decoder MFT, CLSID_CMSAACDecMFT MFAudioFormat_WMAudio_Lossless, WMAudio Decoder MFT, CLSID_CWMADecMediaObject MFAudioFormat_WMAudioV9, WMAudio Decoder MFT, CLSID_CWMADecMediaObject MFAudioFormat_WMAudioV8, WMAudio Decoder MFT, CLSID_CWMADecMediaObject MEDIASUBTYPE_MSAUDIO1, WMAudio Decoder MFT, CLSID_CWMADecMediaObject MEDIASUBTYPE_RAW_AAC1, Microsoft AAC Audio Decoder MFT, CLSID_CMSAACDecMFT MFAudioFormat_MP3, MP3 Decoder MFT, CLSID_CMP3DecMediaObject MFAudioFormat_MPEG, Microsoft MPEG Audio Decoder MFT, {70707B39-B2CA-4015-ABEA-F8447D22D88B} {00000031-0000-0010-8000-00AA00389B71}, GSM ACM Wrapper MFT, {4A76B469-7B66-4DD4-BA2D-DDF244C766DC} {00000011-0000-0010-8000-00AA00389B71}, IMA ADPCM ACM Wrapper MFT, {A16E1BFF-A80D-48AD-AECD-A35C005685FE} KSDATAFORMAT_SUBTYPE_MULAW, G711 Wrapper MFT, {92B66080-5E2D-449E-90C4-C41F268E5514} {00000006-0000-0010-8000-00AA00389B71}, A-law Wrapper MFT, {36CB6E0C-78C1-42B2-9943-846262F31786} KSDATAFORMAT_SUBTYPE_ADPCM, ADPCM ACM Wrapper MFT, {CA34FE0A-5722-43AD-AF23-05F7650257DD} WMMEDIASUBTYPE_WMSP2, WMSpeech Decoder DMO, CLSID_CWMSPDecMediaObject MFAudioFormat_MSP1, WMSpeech Decoder DMO, CLSID_CWMSPDecMediaObject ------------------------------------- Disabled Media Foundation Transforms ------------------------------------- [HKEY_LOCAL_MACHINE\Software\Classes\MediaFoundation\Transforms\DoNotUse] ------------------------ Disabled Media Sources ------------------------ [HKEY_LOCAL_MACHINE\Software\Classes\MediaFoundation\MediaSources\DoNotUse] --------------- EVR Power Information --------------- Current Setting: {5C67A112-A4C9-483F-B4A7-1D473BECAFDC} (Quality) Quality Flags: 2576 Enabled: Force throttling Allow half deinterlace Allow scaling Decode Power Usage: 100 Balanced Flags: 1424 Enabled: Force throttling Allow batching Force half deinterlace Force scaling Decode Power Usage: 50 PowerFlags: 1424 Enabled: Force throttling Allow batching Force half deinterlace Force scaling Decode Power Usage: 0 --------------- Diagnostics --------------- Windows Error Reporting: +++ WER0 +++: Fault bucket 1681864897645112787, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: TPHKLOAD.exe P2: 9.1.0.0 P3: 61945b02 P4: ntdll.dll P5: 10.0.19041.1566 P6: 1be73aa8 P7: c000070a P8: 00000000001121bd P9: P10: +++ WER1 +++: Fault bucket , type 0 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: TPHKLOAD.exe P2: 9.1.0.0 P3: 61945b02 P4: ntdll.dll P5: 10.0.19041.1566 P6: 1be73aa8 P7: c000070a P8: 00000000001121bd P9: P10: +++ WER2 +++: Fault bucket 2134040005271802290, type 5 Event Name: BEX64 Response: Not available Cab Id: 0 Problem signature: P1: BarcoClickShareSvc.exe P2: 1.20.0.0 P3: 60d9e155 P4: BarcoClickShareSvc.exe P5: 1.20.0.0 P6: 60d9e155 P7: 0000000000062694 P8: c0000409 P9: 0000000000000005 P10: +++ WER3 +++: Fault bucket , type 0 Event Name: AppHangTransient Response: Not available Cab Id: 0 Problem signature: P1: OUTLOOK.EXE P2: 16.0.14931.20132 P3: 62218fdd P4: unknown P5: unknown P6: unknown P7: unknown P8: P9: P10: +++ WER4 +++: Fault bucket 1819347901194961607, type 5 Event Name: RADAR_PRE_LEAK_64 Response: Not available Cab Id: 0 Problem signature: P1: RemoteDesktopManager64.exe P2: 2022.1.20.0 P3: 10.0.19044.2.0.0 P4: P5: P6: P7: P8: P9: P10: +++ WER5 +++: Fault bucket 1652262761738970112, type 5 Event Name: RADAR_PRE_LEAK_64 Response: Not available Cab Id: 0 Problem signature: P1: chrome.exe P2: 99.0.4844.82 P3: 10.0.19044.2.0.0 P4: P5: P6: P7: P8: P9: P10: +++ WER6 +++: Fault bucket 1746024696940757674, type 5 Event Name: RADAR_PRE_LEAK_64 Response: Not available Cab Id: 0 Problem signature: P1: mmc.exe P2: 10.0.19041.1586 P3: 10.0.19044.2.0.0 P4: P5: P6: P7: P8: P9: P10: +++ WER7 +++: Fault bucket 1681864897645112787, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: TPHKLOAD.exe P2: 9.1.0.0 P3: 61945b02 P4: ntdll.dll P5: 10.0.19041.1566 P6: 1be73aa8 P7: c000070a P8: 00000000001121bd P9: P10: +++ WER8 +++: Fault bucket , type 0 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: TPHKLOAD.exe P2: 9.1.0.0 P3: 61945b02 P4: ntdll.dll P5: 10.0.19041.1566 P6: 1be73aa8 P7: c000070a P8: 00000000001121bd P9: P10: +++ WER9 +++: Fault bucket 2017953742396825743, type 5 Event Name: RADAR_PRE_LEAK_64 Response: Not available Cab Id: 0 Problem signature: P1: explorer.exe P2: 10.0.19041.1586 P3: 10.0.19044.2.0.0 P4: P5: P6: P7: P8: P9: P10: ...#SSU#...