Verify that both network adapters on the WorkSpace are enabled. For more information, see Required configuration and service components for WorkSpaces. To fix this, you can set up an allow list for the locations where the service components are installed. If the status of the three services is Running, then the services might be blocked by antivirus software. For Startup type, choose Automatic, and then choose Ok. To change the Startup Type, open the context (right-click) menu for the service, and then choose Properties. Verify that the Startup Type for all three services is set to Automatic.If the Status is Stopped for any of these services, open the context (right-click) menu for the service, and then choose Start: Then, open the context (right-click) menu for Services and choose Open. Connect to the WorkSpace using Remote Desktop Connection (RDP).To verify that the required WorkSpaces services are started at the OS level, follow these steps:
WINDOWS 10 ETHERNET STATUS WINDOW STARTUP SOFTWARE
WorkSpaces services in stopped state or blocked by antivirus software Wait a few minutes, and then try again to connect to the WorkSpace. Windows updates or other operating system (OS) activity can delay the boot process, and WorkSpaces health checks might take longer to reflect the actual status. A reboot action also triggers any pending WorkSpaces component updates.
If a reboot command is sent to the WorkSpace from the console or client application, then the WorkSpace might be busy applying updates. Review the following common causes and troubleshooting tips if your Windows WorkSpace is stuck in the starting, rebooting, or stopping status:
0 kommentar(er)
