Agent Fail to Communicate with NS after "Boot To Automation Folder" task

[Sidnei Santana]

Agent Fail to Communicate with NS after "Boot To Automation Folder" task.

Hello, I'm having trouble delivering a Windows 11 24/7 image.
After the "Boot to automation Folder" task, the agent no longer communicates with the NS.

After several configuration attempts, we get the following error:

*WARN Server Connection: Failed to connect to NS server, retrying in a minute, error: Communication profile disallows IP protocols enabled on the connected network adapters (0x8FA30007)

[Sergei Zjaikin]

Please check what IP protocols are enabled in the communication profile for you server

If message is correct then the failure reason is protocol mismatch - for example communication profile is configured to use IPv6 only, but the agent in "Automation Folder" cannot use IPv6. 

It is hard to tell without knowing details about your environment, if IP protocol settings are default in ITMS console and your environment is not IPv6 or IPv4 only then everything should work. If your environment is configured to use IPv4 only or IPv6 only or your server or client machines have IPv4 or IPv6 protocol disabled or removed, then that kind of message is supposed to tell you where the problem is.

[Igor Perevozchikov]

Hi Sidnei Santana!

Sergei already mentioned that need to check what settings are in Communication profile 
Example 


And make sure that your preboot environment has latest Communication profile applied. Check your preboot environments
Example

Best regards,
IP.