HUB configuration failed via DNS TXT record

[FLuo0]

1.Able to configure HUB successfully via URI.

2.Organization info as below link:

serverUrl=https://server.scit.net/IntelUnite/api&orgId=561063E5-15F6-46FA-81EB-AC2280C2482E&orgName=AD

3.Able to positive result via executing "nslookup -qt=txt uniteservice" command (attached screenshot for reference)

4.Detail infor:

HUB OS: Win10

Intel Unite APP version: 4.0.1185.49

Enterprise Server: Windows server 2016

AD server: Windows server 2016

SQL server: SQL server 2016

Could you please help with this? Thank you very much~

[Leonardo_C_Intel]

Hello FLuo0 Thank you for posting in the Intel Community. Please walk me trough the steps recreate the behavior that you are facing in order to get a detail description of the error. Hope this helps. Regards, Leonardo C. Intel Customer Support Technician Under Contract to Intel Corporation

[FLuo0]

Hi Leo_C,

Thank you for quick response. My steps as below:

1. Create a AD server
2. Add the hub and server to the domain
3. Follow the Intel unite 4.0 deployment guide_v1.0 to configure server
4. Launch Intel unite APP hub and got an 0x000053B error.

Refer to the guide, Occurring 0x00005B error is because Keys or values in DNS TXT record missing. But double checked DNS manager and it is there. Tried to execute command "nslookup -qt=txt uniteserver" on hub and verified DNS TXT is valid.

[Leonardo_C_Intel]

Hello FLuo0 This behavior seem to be related to the missing provisioning of the HUB for Intel Unite® , please try the steps for Intel Unite® 4.0 - When Launching a 4.0 Unite Hub, this Message Displays: 0x0053B required key to run Intel unite app is missing (https://www.intel.com/content/www/us/en/support/articles/000031167/software/software-applications.html). Let me know the outcome. Hope this helps. Regards, Leonardo C. Intel Customer Support Technician Under Contract to Intel Corporation

[Leonardo_C_Intel]

Hello FLuo0 Have you tried the steps provided? Regards, Leonardo C. Intel Customer Support Technician Under Contract to Intel Corporation

[Leonardo_C_Intel]

Hello FLuo0 I haven’t heard back from you, I am going to close this request If you have more questions please do not hesitate in replying back. Regards, Leonardo C. Intel Customer Support Technician Under Contract to Intel Corporation

[AVeto]

Since the 4.0 Administrative Guide does not elaborate on this, the info on the landing page URL (../IntelUnite/admin/landing) is not in the same format needed for the DNS TXT record entry. The orgId and orgName are referenced within the URL, but you will need to change the formatting. It will need to have the following format:

SERVICEURL=https://<fqdn>/IntelUnite/api|orgId=<orgId>|orgName=<orgName>

So for example, using the information that you provided above, the correct entry would be as follows:

SERVICEURL=https://server.scit.net/IntelUnite/api|orgId=561063E5-15F6-46FA-81EB-AC2280C2482E|orgName=AD

Hope this helps.