Reputation
234
Top tag
Next privilege 250 Rep.
View close votes
Badges
8 16
Impact
~42k people reached

  • 0 posts edited
  • 0 helpful flags
  • 36 votes cast
Nov
4
awarded  Notable Question
Jul
2
awarded  Curious
Jan
22
awarded  Notable Question
Mar
19
awarded  Notable Question
Mar
13
awarded  Popular Question
Feb
1
awarded  Popular Question
Dec
11
awarded  Yearling
Oct
24
awarded  Popular Question
Sep
20
awarded  Notable Question
Apr
8
accepted Time sync fails on Hyper-V VM, but succeeds when I log in as a domain user
Apr
8
comment Time sync fails on Hyper-V VM, but succeeds when I log in as a domain user
Thanks Mathieu - this is good information. I'm not responsible for our overall domain - mostly just for this hyper-V server and a couple others. But I'll talk to our main network administrator about it. I'll try running your script to check how far out of sync our machines are.
Apr
8
comment Time sync fails on Hyper-V VM, but succeeds when I log in as a domain user
Thanks Chris - I followed these three steps and it seems to be working now. I'll keep an eye on it to see if it continues to drift...
Apr
5
asked Time sync fails on Hyper-V VM, but succeeds when I log in as a domain user
Mar
20
awarded  Popular Question
Dec
24
awarded  Notable Question
Dec
24
awarded  Popular Question
Nov
30
awarded  Popular Question
Nov
21
awarded  Notable Question
Sep
14
comment Can't access NTFS file after BSOD. Corruption undetectable by chkdsk?
The problem filenames came from cygwin - we were using it to grep through some log files and save the results. I wasn't able to move the files using "move", but Cygwin "mv" did the job. Thanks for the fully-qualified path technique, I'll remember that too.
Sep
14
comment Can't access NTFS file after BSOD. Corruption undetectable by chkdsk?
Thank you! This solved the problem. That would never have occurred to me. I knew COM1, COM2, LPT1 and so on were reserved names, but I didn't realize it would still be reserved if you added an extension such as com1.log.