Idea Details

UIM E2E_Appmon Support on Windows 10

Last activity 06-13-2019 09:52 AM
Murugesan Ramaiah's profile image
05-28-2018 05:49 AM

Hello,

I see that NimRecorder 6.0 (WInTask 6.0) does support Windows 10. Can we bring the support of Windows 10 in e2e_appmon and e2e_appmon_dev please?

 

This will help us to migrate and run the scripts from Windows 7 to Windows 10


Comments

07-02-2018 08:54 AM

During windows 10 certification, we didn't see need for any registry changes. However, we will review above comments and will add to probe documentation as needed.

06-29-2018 10:05 AM

It seems to have. We saw our error on four workstations that we had upgraded. On each one once we changed the registry setting and rebooted, the error went away. So far it has not come back (one week). You might want to check your registry setting to see if it is 1 or 0. We checked our Windows 7 boxes. They were all 0. So for us across the board that is working. We do not know why the new installs on Windows 10 set the value to 1.

 

Of course your mileage may vary and you always have the option of opening a support case. They should help you now that they are supporting Windows 10.

06-29-2018 10:00 AM

so to clarify, the winsdows 2012 R2 regedit fixed the issue for running e2e on windows 10 workstations?

06-29-2018 09:50 AM

CA gave us a document that was for servers with several things to try. We tried the Windows 2012 R2 server regedit and it worked for us. From our documentation what worked for us:

 

  • Press the Windows key and R to bring up the “Run” interface
  • Type regedit
  • Agree to changing the system settings
  • Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
  • Change the value of the “EnableLUA” key from 1 to 0
  • Reboot the workstation

 

Their documentation:

https://imsva91-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2fcomm.support.ca.com%2fkb%2fe2eappmon%2dreturn%2dcode%2d5%2dwhen%2drunning%2dscript%2fkb000034036&umid=C1CB6818-6F2C-1905-B821-7631A82B19F8&auth=5ab06289d9c3b14f9a77f69d29e7a25870e86301-aeee7070602ca62767fdc54e05d472dec51ed2cc

06-29-2018 09:06 AM

what were the registry changes that were applied?  Is it documented?  Recommended by CA or another one of those learned as you go type fixes?

06-28-2018 02:43 PM

It worked for us after a regedit to our work stations.

06-27-2018 08:37 AM

I believe only release note is updated, not the e2e_appmon or e2e_appmon_dev probe though :-)

I have installed it on Windows 10 workstation and i have the WTBho Class plugin showing as it is not compatible.

06-23-2018 01:09 PM

e2e_appmon probe is now certified with windows 10 platform and release notes is updated .

06-19-2018 12:55 PM

Windows 10 certification for the e2e_appmon probe is already planned and should be available sometime before September 2018. Exact release timeline can be provided around mid-July.

06-19-2018 12:02 PM

what is the target release for windows 10 support?