Learn more about our new Wake on LAN feature in our Remote PC Access documentation. Yes, as long as both Machine Catalogs use the same Wake on LAN connection and the PCs are in the same subnet. While we support having PCs in multiple subnets and using Wake on LAN to power them on, you must have at least one PC powered on in each subnet that can send magic packets so that PCs in that subnet can be woken up.Ĭan PCs wake up PCs in a different Machine Catalog? Host connections are assigned to a specific zone, so you must have a Wake on LAN connection for each zone. Our documentation covers a number of design and operational considerations, but I wanted to answer a few frequently asked questions:Ĭan you use the same Wake on LAN connection with multiple Machine Catalogs?Ĭan you use the same Wake on LAN connection across multiple zones? As always, I recommend you test this out in your test environment or test Machine Catalogs before running it in production. I also have a sample script you can use or modify - at your own risk.
#Wakeonlan tool how to
Details on how to do that are available in our Remote PC Access documentation.
After all, we already have an agent running on the PCs - the VDA - and the machines have direct access to the subnets they are in. With this new Wake on LAN feature, there’s no need to have additional infrastructure in the network to deliver magic packets to figure out how to get magic packets to traverse subnets or to deploy separate agents to the PCs. I’m excited to share that we have a new Wake on LAN feature that is fully standalone and incredibly simple to deploy and configure. In working with our customers, we learned that Remote PC Access needed Wake on LAN capabilities that are easy to use and easy to deploy and configure. In the era of remote work, Citrix Remote PC Access has become a vital tool for IT to securely deliver remote access to physical workstations. Citrix App Delivery and Security Service.
0 kommentar(er)
