WD DX4000 Sentinel Recovery Disc

restoring a backup is not a recovery, it is a restore

To start a new box you need to do a recovery. Once it is installed and configured at a clients you start doing backups

Please forgive my choice of words. Since I have not been able to do a
factory reset, my only option has been to use a cleaned backup to get the boxes
usable. While it would be nice to get the factory resets to work, the
restores have giving me usable boxes which I will be able to install at clients
for the purpose of creating backups of critical systems as part of the
support we provide.

Either the 20hr days are getting to me or I may not be as smart as they
tell me I am .

While I can rdp into one of the units I restored I start the connect
program and after it asked for the password, I get a message that it canā€™t
connect to the server? What have I missed?

Well, I quess I cleaned the backup too much and deleted something I shouldnā€™t have. Went back to square 1 and I and connect now.

David P Rimi, CIO
Medical Office Solutions/CompSysGrp
[Deleted - Privacy]

While I rdp into one of the unitsā€¦You should be able to rdp to any of them.
Are just implying that you know what the admin password is?

So from a PC you surf to servername/connect
download and run the connector software, click next whatever and after you enter the password it says cannot connect?

Did you change the servername by removing Cert Services?

Robert has a nice tool for testing stuff

Yes, yes and yes

Do you have any boxes where you have not changed the servername?

Just the one in the field and out in house unit. The ones Iā€™ve been
talking about are the ones that have the restored backup that I may have
mistakenly removed the active Directory and web server iis. Did I slip up ;-(

And that would be a statement yes? Not a Question :slight_smile:

Well, while waiting for the addā€™l drives to arrive, I re-restored the
starting backup deleting only the Clientā€™s users and backuped computers. The
unit is now responding to client connects. I hope your suggestion to direct
connect will allow me to do factory resets

So, after starting over and not deleting the active directory and being
able to connect client PCs, it will not update from 1.7.3.13 to 1.7.6.21 which
the same box did before.

to do a firmware update from file I thinkā€¦
you put the zip file somewhere and from the dashboard point to the zip file.
the C:\wd folder might be a good ā€œsomewhereā€

Iā€™ve gone the route. The boxes I delete too much updated ok. Both the
clients box and the box I restored their backup fail during the update.

FWIW when you do a firmware update from the dashboard the progress bar does not move. If you get a progress bar just wait.

I tried to update 1.7.6.21 to the same and it failed, So I edited the xml file changing all the 21ā€™s to 22ā€™s

It did start and try but I think it failedā€¦

Did step 1
Connected network cable directly to box
Selected factory reset keep data
Got 0x80070570 error as usual

Ok,
Did step 1
Connected network cable from PC directly to box
Selected Factory reset donā€™t delete data
Got the usual 0x8007

in both of the above you said keep data. I assume one was delete data ?
Backup one step and do recreate storage. You have to make a new thumb drive each time.
when it is done post the recovery log file in the c:\wdrecovery folder to a dropbox share and share the link or better yet send the link in a private msg as WD gets all funky when you show drive serial numbers

The status bar went a little past 50% before the error

Iā€™m doing the second choice with will take a lot longer since itā€™s
formatting now.

will send log via private later

Are you referring to the step 2 or 3 or both have to be recreated each
time?

Just the middle step, recreate. There is some file that gets deleted when it runs.
The bottom step recovery has a check mark to skip creating a thumb again which you may skip

Those are the steps I followed. Now Iā€™m redoing with the delete data option. This means I have a looooong wait while it formats. By the wayā€¦just in case I havenā€™t mentioned it, thanks for your help

Let it run overnight. found pc at login screen, logged in nothing on screen box still says recovery started.
while the 1.7.6.21 hash supplied by the WD link matched what I got here itā€™s still not working.

I noticed that the only 1.7.6.21 updates that worked were boxes that had 1.7.5.17. Iā€™m going to try that iso again to see if I get further.