Marek Korczak

Hi, How to troubleshoot UDA from server side? to which logs I should look to determined what goes wrong? I did everything exactly as described above and on other technet websites. MP_Status.log on my MP says: " Mp Status: processing event: SMS_OSDUDA_StateMessageSent_ActionCompleteInfo, for machine: MACHINE " on smsts.log from machine we can see: " Creating user affinity Set authenticator in transport Report Body: <ReportBody><StateMessage MessageTime="20180310140606.000000+000" SerialNumber="1"><Topic ID="DOMAIN/USER:OSDAuto" Type="1600" IDType="0"/><State ID="1" Criticality="0"/><UserParameters Flags="0" Count="2"><Param>DOMAIN/USER|04945F94-E377-46C7-B9E3-81CC0FC319B7</Param><Param>OSDAuto</Param></UserParameters></StateMessage></ReportBody> Successfully submitted the UDA state message for the user(s): DOMAIN/USER with mode 'Auto' " and if we will check primary machine for user / primary user for machine in SCCM console - there is lack of such information assigned to those object. I'm using SCCM CB 1710 Console version: 5.00.8577.1108 Could someone advise what could be the reason why this happened? I checked UDA on Windows7 x64 and Windows10 - the same results.