At that point, make it a thin client which boots from a network image and logs you into a terminal server.
Then you have the hardware and software resources you need for your role wherever you are.
This sounds like a great idea until you have multiple physical sites and dhcp doesn’t span network segments. Or, even if you’re willing to deal with that, employees who work from home. Anything that solves for the second one is almost certainly more complicated than just using vms or containers on remote workstations or a configuration manager on the workstation os and not waste your time on the thin client part
At that point, make it a thin client which boots from a network image and logs you into a terminal server.
Then you have the hardware and software resources you need for your role wherever you are.
This sounds like a great idea until you have multiple physical sites and dhcp doesn’t span network segments. Or, even if you’re willing to deal with that, employees who work from home. Anything that solves for the second one is almost certainly more complicated than just using vms or containers on remote workstations or a configuration manager on the workstation os and not waste your time on the thin client part