Wrong time/date and WHS's reaction RRS feed

  • General discussion

  • I did some search but weren't able to find any threads regarding this behaviour, I wonder if I'm the only one who encountered this: Today, I tried to log on and WHS said my time and date were incorrect and I cannot logon before I have not corrected this manually in safe mode! What is this? What programer had this strange idea of forcing me to attach a screen, mouse and keyborad to my server and reboot it in safe mode just to set up the time? Does this have deeper meaning? Especially as I could do I simple reboot and set the time and date in the BIOS, much easier. But _why_ does WHS want a user to do these steps of reattaching the devices, rebooting, safe mode and another rebooting? Why can't it use a time server to update its time? Or simply set the time via RDP?
    Friday, April 6, 2007 6:09 PM

All replies

  • Hi, my problem is not exactly the same as this one, but as it came up as I was typing in my Subject as a related topic, I am continuing in this thread.

    My date and time in WHS is wrong. It was wrong in beta 2, and I had seen a post which stated changing it caused the poster to have to go through setup all over again, so I decided to wait until the next release and see if it was fixed. Well, I have now successfully installed WHS CTP and the Date/Time is still off. It is off by about a day and a half. It is connected to the Network, has proper connectivity, yet is still wrong. I don't wish to try changing this until I hear from somebody about this, as I am not exactly sure how I should go about it, especially after reading the post before mine. If anyone knows about this, please advice me what course of action to correct this issue. Thank you very much for your time and attention,



    Friday, April 20, 2007 1:25 AM