Just ran into an interesting problem...
Went away for a few days so I shut down my WINXP-MCE machine for that time. THe morning after I returned home I started up the PC to check email and sync my iPod. The login took FOREVER. The desktop appeared but the PC 'appeared non-responsive and no icons popped up in the systray. It 'hung' there so long that I forced a shutdown.
I rebooted later that day after work to a fully functioning PC. Of course, the WHS client showed network status as "yellow", just as I expected it would... However, the reason wasn't because I missed a few days of backups, it was because the previous backup failed. Hmmm?
Turns out, I turned the PC on that morning before the end of the backup period. And the backup that failed was at exactly the time I booted up that morning. The PC 'hung' due to the backup starting immediately during logon.
Suggestion: Force WHS to delay start of a backup until the client has been running for some nominal period of time. Evena delay of five minutes would ahve allowed the PC to startup (login) and start all normal applications and services before bogging it down with a backup. I still wonder if both the backup and login would have completed normally had I just left it go and not forced the shutdown.
CLIENT: 2.13Ghz Core 2 Duo, 1GB RAM, 74GB Raptor (boot)
WHS: 1.7Ghz P4, 512MB RAM, LotsGB Storage
PS: For some reason I cannot post feedback on connect... Even when logged in.
If it ever lets me post feedback there I will add this issue/suggestion.
(NEVERMIND... I just read the email about the pending release of RC and the disabling of new feedback to Connect... WOO HOOOOOO! ---- So anyone have any idea of WHEN RC is going to hit the download page on Connect?)
