I'm not seeing a profile manager in the logs folder, however I found this info in the server logs if its any help.Īpr 5 11:41:58 vpp : error ClientStartListening ClientSendAttachNotification failed for client 63659-ath, interface 5 11:42:03 vpp : error ClientSendDictionary to client 63695-ath failed to send header: -1, 32 Broken pipeĪpr 5 11:42:03 vpp : error ClientStartListening ClientSendAttachNotification failed for client 63695-ath, interface 5 11:42:14 vpp : error ClientSendDictionary to client 63768-ath failed to send header: -1, 32 Broken pipeĪpr 5 11:42:14 vpp : error ClientStartListening ClientSendAttachNotification failed for client 63768-ath, interface 5 11:42:28 vpp : error ClientSendDictionary to client 63857-ath failed to send header: -1, 32 Broken pipeĪpr 5 11:42:28 vpp : error ClientStartListening ClientSendAttachNotification failed for client 63857-ath, interface 5 11:42:34 vpp : error ClientSendDictionary to client 63889-ath failed to send header: -1, 32 Broken pipeĪpr 5 11:42:34 vpp : error ClientStartListening ClientSendAttachNotification failed for client 63889-ath, interface 5 11:42:35 vpp : error ClientSendDictionary to client 63911-ath failed to send header: -1, 32 Broken pipeĪpr 5 11:42:35 vpp : error ClientStartListening ClientSendAttachNotification failed for client 63911-ath, interface 5 11:42:37 vpp (): Endpoint has been activated through legacy launch(3) APIs. Once installs the device will show up in profile manager and we set up restrictions and groups etc. We usually hook the devices up to the server and load our wifi profile and blueprint with configurator then after that's done we sign into the enrollment profile via the device.
0 Comments
Leave a Reply. |