paulsharman

i agree on that one , i have some logs to send off today , so im sure it is now being treated as a bug

no , thats my concern , im sure it should use the APE , or that means UDT is not fit for use as part of observability and APEs

Hi Thanks for the link , i can run tests from the APE which sits on the correct network and domain, the same tests dont work from the main polling engine , I have been advised that UDT does not poll DCs from the APEs but infact polls from the main polling engine. what i can see is this now makes UDT unscalable across large…

I have the same situation, is this correct that additional pollers will resolve this. I have one main poller but now need to monitor additional partners, so could a poler at each partner site solve this Thanks thanks

thanks for the update, glad this one is being looked into as its a vital feature Thanks paul

Hi yes This got resolved as above with a temp eval licence, until asset transfer is complete. Paul

Thanks I have now had an eval licence and this fixed the issue. The reason it was showing as down was I had already installed APE over 6 months ago, with full licence, when APE is installed it also has a scalability engine that shows in licence manager that had expired. This meant the second APE could not have a default…

Thank You

Thank you all for the advice, each remote site will be large so will need to go with APE at each site. Another question is could we install IP monitor on each APE ? One remote site would like to use up monitor , but I can see this having the same IP or erlapping issues if installed on the main poller ? Thanks