I have no clue how you got technical preview. Your Norton av/firewall do proxy server?
If you ping-4 wdsentinel is it correct
do http://server_ip/connect, click connect and then run
See if the correct wizard runs
I have no clue how you got technical preview. Your Norton av/firewall do proxy server?
If you ping-4 wdsentinel is it correct
do http://server_ip/connect, click connect and then run
See if the correct wizard runs
Slammed at work, but I finally got resolve on the issue from a very helpful level 2 tech at WD.
Many thanks to Gramps as usual for helping out here!
The problem was related to a dirty windows file system, and numerous errors in the .net framework configuration…
Fixed some file system errors with sfc /scannow command
Downloaded Microsoft’s .Net repair tool, ran it, and it appeared to fix errors.
In Programs & Features (i.e. add/remove programs), we removed erroneous .net and past connector install remnants
Enabled all relevant .net entries in Windows 10 (there were several options that were somehow disabled)
After doing the above and rebooting, I was finally able to install the client connector software, and now have the workstation joined back to the DX4000!
So if anyone out there has a Windows machine that had a 10 upgrade and then stopped working with the DX4000 Management & Backup features, check your file system for errors, and make sure your .Net files are enabled and in good shape.
Glad you are back in business and thanks for the update!