Thanks.. yes I am using keyboard, mouse, and monitor on the server at this
time. There is just too much stuff to do that cannot be done otherwise to
not do so. Later when it is all stable I will revert to headless.
I will try your advice next time it freezes up.. provided I can even get
there. Often I cannot even boot into the server in order to do that, so I
have to boot into a disk (either the install disk or the repair disk) to do
a repair or restore from image (provided it has even made one yet).
If I have more trouble I will start a new thread and also file a report on
Connect. I have not mentioned this problem elsewhere. This last reinstall is
working pretty good so far. I have a couple of server backups now, and
manual backups for 2 clients (manual because the auto-backups for all 3
machines all failed last night) - and the 3rd one (also manual) is showing
5% now for about 2 hours - it is for the main machine that has considerably
more stuff on it than the other two).
--
Art (artfudd) Folden
~~~~~~~~~~~~~~~~
"paulfiwhs" wrote in message news:5bed4a9f-fe96-46a6-8ec1-5397816dabe5...
> Hi Art,
>
> if you are running on a server with a keyboard and monitor you can boot
> from the install media and click on the repair option instead of the new
> installation option in the setup wizard
>
> this will launch the windows server native recovery wizard. We are
> replacing that with our own version but you can use it to perform a
> restore. Documentation for windows server recovery also known as the
> windows recovery environment is on technet.
>
> Have you posted the other issues you described anywhere else?
>
> thanks for testing.
>
>
>
