A user asked about why fabric.controlup.com is included when testing VDI & DaaS. Other members explain that it is needed for Remote DX and suggest adding the URL to documentation about communication ports used by ControlUp. URLs for EU and US customers are provided. The user acknowledges their error in reading.
Read the entire ‘Understanding the Need for fabric.controlup.com in Testing VDI & DaaS’ thread below:
CUTester.exe: Why is fabric.controlup.com included when testing VDI & DaaS?
As you seen in the screenshot attached the URL fabric.controlup.com is checked even though I want to test VDI & DaaS…
According to documentation the URL is needed for "Access to https://fabric.controlup.com to collect client location and ISP data." in EdgeDX (Physical Endpoint).
What am I missing?
Is it really needed for pure VDI & DaaS?
https://support.controlup.com/docs/remote-dx-overview?highlight=fabric.controlup.com
@member let me check for you
@member its needed for Remote DX not just Edge DX. And as Remote DX is a feature/Addon to Remote DX that is why it is tested
ah… reading error 😄
I read "Remote DX" but brain translated to "Edge DX"… Sorry for that
haha i missed it until i read it a second time, eye just reading what they want
i give out to my kids for that
But maybe it would be nice to add the URL to the following:
https://support.controlup.com/docs/communication-ports-used-by-controlup-hybrid-cloud-eu-customers
https://support.controlup.com/docs/communication-ports-used-by-controlup-hybrid-cloud-us-customers
will make the suggestion
Continue reading and comment on the thread ‘Understanding the Need for fabric.controlup.com in Testing VDI & DaaS’. Not a member? Join Here!
Categories: All Archives, ControlUp for Desktops, ControlUp for VDI