BTW, When accessing the unit with MSTSC it did look like the remote desktop and the error 503, when I closed it, so closed the desktop and put me back to my PC.
You have a great weekend since I probably drained your brain over this…I know mine is washed out… Coming from an IT background, I have never seen anything like this before, maybe because after 6 years of being retired… I lost what I knew…:manindifferent:
Bob
Okay, now it is the 4th day and here is the results:
1> Everything appeared to go well with the recovery
2> Ran MSTSC
3> Logged in as Admin
4> Screen pops up with the same message
" 503 Service Unavailable "
There is no way to close that screen without shutting down the remote session.
Do you know what a burn barrel is??? That’s where you burn your trash, cuz where I live they don’t pick it up…
And I still do not understand why WD (Western Digital) hasn’t responded to my 2 cases out there… What happened to customer support… Did they forget who pays their salaries… The end users who purchase their products…
Bob
:robotfrustrated::robotfrustrated::robotfrustrated:
I may have been wasting your time. What version of the recovery are you using?
Avoid using Server Recovery version 1.5.8.31 or earlier for WD Sentinel DX4000 and/or version 1.6.7.22 or earlier for WD Sentinel RX4100 when performing a Server Recovery. When encountering the HTTP 503 error , perform a Server Recovery on the unit using the latest available Server Recovery ISO from WD Support site
The lastest 01-07-03-13
The version it speaks of is nowhere to be found. I looked all over for that in the begining and could only find the one listed above 01_07_03_13 8.5gb and like I stated earlier, the the verification to the md5 is correct.
Bob
Well I emailed some of the few I know at WD and allowed it looks like the certificate patch may not be in the latest firmware update.
Just let it rest a bit and go cut some firewood and fill the kerosene heaters for the next couple of days and we will see what happens after we thaw out.
Ya mean no burn barrel or fire sale… When your out in the middle of nowhere sometimes ya have to look forward to something…
Have a great weekend,
Bob
Oh, btw, I am not where your tush get that cold, I am in SE Arizona, we only get to about 32 in the morning and 60s in the afternoon. I have to say I truley do not feel your pain…
Again, Stay warm
Bob
Update:
Got a note they are looking in to it. Have a great Day
Yes,
They emailed this morning about the USB, nothing to do with the ISO yet.
Thank You for all your input.
Bob
Good Evening Gramps,
Well, so far a miss, I purchased 2 other usb devices to try as per their email suggestion, an 8 gig and a 32 gig, but same result. I am waiting for Sal to call me.
Thanks,
Bob
Update:
Okay, I am up and running, but still an issue with the ISO and the virtualDVD software. I tried 3 different virtual DVD software and none of them could or would allow the ISO to find any of the (4) usb flash drives I purchased. WD stated if it was listed as a local drive it would not find it, some were listed as local and some were listed as removable but neither could be found. I took the usb flash used to setup my first unit (identical to the ones purchased 16gig) and the iso found it (???), I allowed it to create a new flash for recovery and everything was good from then on.
I am going to make an assumption here (right or wrong) the flash drive MUST be created from the NEW ISO ( 1.07.03.13) to overcome the 503 error, the original flash I made did not contain the updated patch.
I also learned (or at least under the impression) you can not use the connector software on 1 PC to access both units (assuming the software is tied to the IP) so I am using MSTSC and running the dashboard from there.
If anything I have posted here appears to be in error, please feel free to correct it and post it.
Thanks,
Bob
Gramps,
By the way, I want to say thanks for all your support and help… but I think the bonfire would have been fun anyway…
Bob
Continued Update:
I have also found the only way to utilize the embedded backup within the WD unit is to install the connector software from the units you want backed up. It appears the only way the WD unit and 2008R2 sees the individual units is through the connector software.
So in conclusion, my first WD unit is the one which I ran the connector software for, the 2nd WD unit will not be utilized to backup only store data, music, videos.
Bob
I started to try to duplicate this with you. Got the new ISO downloaded and started on a flash drive. It has to be bigger than 8gb now. I did have a USB 3.0 32gb that it found, but gave an error. I went into diskmgmt.msc and it was there but “new”. I made a new simple volume and the wizzard worked fine.
I never made it to booting from it yet though.
But you are correct, whatver box you run the connector software from is the one it is “attached” to. BAckups, dashboard, shared folders etc.
FWIW, I am using Win8 and simply double clicking the ISO mounts it has a dvd drive and I could run setup from there. I use MAgic ISO on my win7 box to mount them.
If you still want to play with it, you might try formating the thumbs it did not see as FAT32 vs NTFS to see if anything changes
Glad you are up and going. What you should do is keep all your stuff on box A and use something to copy it to box B for backup 
Thanks for the update. Wd Tech also said to try a win7 or win8 box which should mount the iso without any 3rd party software involved to see if it could then see the usb flash. I know the manual also states it must be USB 2.0 not a USB 3.0 flash drive. I am still at a loss as to why the first unit (Install Wizard ??) found the same USB I had just purchased and the new one would not… Just me and being curious…
Again,
Thanks for being there !!!
Bob
Again, I made a USB 3.0, I have not tried to use it yet LOL
I don’t really think win7 natively mounts ISO’s
If I get around to it I will see if the wizzard cares if the flash is NTFS or FAT32
I think you are correct about Win7 not having a native iso mounter, now that I think about it, Sal did say Win8. I will play some later and try to get some conclusion on the usb flash drives. I tried formatting them both NTFS and FAT32 with neither making any difference in the iso finding them.
I looked all over to give you Kudos, but I could not find any place.
Bob
Shamless reply here LOL. But Kudos is how Microsoft rates me. They need metrics, not success stories.
I helped build the product you love when it works. I want to make sure you have a great experience. It just happens to be running on WD hardware.
I had too look myself. There is a star under/next to my avatar.
Thanks,
Gramps
Kudo’s completed, now MS can give you a raise…
Bob
Don’t ask me why (like my grandchildren do) but I tried again with the changes and now it works, I don’t think I had the port @ 587…
Maybe too long sitting here, need to find a different hobby…
Bob
