Have your normal users got a lot of data to pull from the network compared to admin? For example other programs or scripts? Luke

On 2 Oct 2018, at 13:26, Eigeldinger Simon wrote:

Hi all,

Has someone also had that on win 10 with a normal user? i am using the nvda remote addon. I have my nvda settings hosted on a network share where all users have access to. when i start nvda using my admin account i just need to wait 1-2 seconds until my pc is connected to the other machine. but with a normal user i have 30-40 seconds until nvda beeps and is connected. i have already turned off firewall, turned off antivirus, etc. nothing seems to help. when i start nvda without getting the data off the network, nvda is quick.

the win 7 clients which we also having have no issues at all. we have win 10 enterprise 1803 with all cumulative updates.

Greetings and thanks, Simon

_______________________________________________ Blind-sysadmins mailing list -- blind-sysadmins@lists.hodgsonfamily.org To unsubscribe send an email to blind-sysadmins-leave@lists.hodgsonfamily.org

Hi Simon, Not a solution to your problem, but maybe you could take something I hope. I was having this issue even though I am using account with administrative rights. Just a suggestion, Have you maybe tried using the latest version of NVDA along with the remote addon that just got updated? Another thing I've noticed with the remote addon, it seems to be fussy when it comes to computer names. For company reasons our computer names have dashes or hyphens in them for naming purposes. I noticed if I gave my pc a short name with no hyphens it seems to connect to the clients as soon as I tell them to click the icon on the desktop. I hope the above works for you because out of despearation I have also, 1. Installed NVDA along with addon in to the master image that we are deploying and Configured the settings to connect directly to the machine. I did try the suggestion to have the config on a share but, I was also experiencing long time of delay which caused a lot of frustration. Just a question, do you know perhaps how to switch off the beep on client side? I mean for the users who will connect to the machine, It is really not a nice thing for them to be hearing, especially in corporate environment I think. Kind Regards -----Original Message----- From: Eigeldinger Simon Sent: Tuesday, 02 October 2018 2:27 PM To: blind-sysadmins@lists.hodgsonfamily.org Subject: [Blind-sysadmins] NVDA on Win 10: slow starts when getting the settings from a share Hi all, Has someone also had that on win 10 with a normal user? i am using the nvda remote addon. I have my nvda settings hosted on a network share where all users have access to. when i start nvda using my admin account i just need to wait 1-2 seconds until my pc is connected to the other machine. but with a normal user i have 30-40 seconds until nvda beeps and is connected. i have already turned off firewall, turned off antivirus, etc. nothing seems to help. when i start nvda without getting the data off the network, nvda is quick. the win 7 clients which we also having have no issues at all. we have win 10 enterprise 1803 with all cumulative updates. Greetings and thanks, Simon _______________________________________________ Blind-sysadmins mailing list -- blind-sysadmins@lists.hodgsonfamily.org To unsubscribe send an email to blind-sysadmins-leave@lists.hodgsonfamily.org