Posts made by CCWTech

@quixoticjeremy said in What Are You Doing Right Now:

@ccwtech said in What Are You Doing Right Now:

Trying to do 3 DR's at once.

1 - Client that I told many times to buy a UPS for their server that has frequent power outages. They had good intentions but never got around to doing it. (They have one now!)
2 - New client that thought they could do it on their own that shared out every drive on the server, every drive on each workstation and got hit by a crypto virus that encrypted virtually every file on every computer (inc Server) that they own
3 - Client that 'moved' his server all by himself (without turning anything off first) - Still trying to figure out this one.

Oh, and keep up with my normal customer calls/tickets.

Wow, just wow. Honestly #2 had me literally laughing (sry you are dealing with all of this).

Yeah, I had to be nice and tell him that doing that is 'generally not best practice'. Didn't want to add insult to injury. I think he got the point.

Sucks right now, but if everyone knew how to do I.T. I'd have to find a different job!

Trying to do 3 DR's at once.

1 - Client that I told many times to buy a UPS for their server that has frequent power outages. They had good intentions but never got around to doing it. (They have one now!)
2 - New client that thought they could do it on their own that shared out every drive on the server, every drive on each workstation and got hit by a crypto virus that encrypted virtually every file on every computer (inc Server) that they own
3 - Client that 'moved' his server all by himself (without turning anything off first) - Still trying to figure out this one.

Oh, and keep up with my normal customer calls/tickets.

Another culprit seems to be Dismhost.exe \Windows\System32\config\Components

@momurda I don't have any backups running during the day. What steps can I look into in order to mitigate the high activity?

When I see C:\system volume information\ (and a string of numbers/letters) I am normally seeing very high hard drive usage. Unfortunately the photo doesn't show high disk usage, but shows the path. What exactly is that? (vs. a traditional file path and file name)

@jt1001001 said in Unable to get time to sync on Server 2012 R2 DC:

are any of your time services running under a domain accoutn instead of Local Service? Sounds like a service does not have permission to update the time

Windows Time is set to run under "Local Service" (not local system account)

@dbeato said in Unable to get time to sync on Server 2012 R2 DC:

@ccwtech I would check again what is the main NTP server on the servers and adjust the Time ZOne on the server.

The time zone is correct and I have tried several different time servers. What I see is that it is contacting the time servers as it should, but no matter what time is on the server it shows a 0 ms offset from the NTP servers.

Is there any test for that? I would imagine the fix is a new motherboard, right?

I put a new CMOS battery in, made sure the time in BIOS was correct. It's now about 30 seconds behind. Seems like it gradually keeps slowing until manually entered again.

I have a client who wants to record from a webcam (audio/video) and be able to edit the video. He has been doing this with Movie Maker but is trying to find a replacement since Movie Maker is no longer supported.

Any suggestions?

I have a client that is remote to me (a little over a thousand miles). They are building a new addition and looking at doing Cat6 cable. I have heard that you really need extensive testing to 'certify' the cable in order to really be cat6. (Under the premise that Cat6 is less forgiving than Cat5e when terminating)

BS or true?

@dbeato But it doesn't. I manually changed it from 7 behind to 2 behind to let it catch up. However I have set the time on this server (to correct time) manually a couple months ago and that is when the company called me and said it's off again.

@hobbit666 I have tried a couple of those.

It's weird to me as it seems like it's able to sync the time, but no matter if it is 7 minutes late or 2 minutes late the server 'thinks' it's off by 0 ms so it doesn't change.

It's just odd.

With the fact that it slowly 'catches up' last night I adjusted the time to be within 2 minutes of current time hoping that it would 'catch up' more quickly. As of this morning it's still at 2 minutes behind, so no joy....

I'm reading that if it is off only by a few minutes it slowly changes the clock to run faster until it 'catches up'.

Check again in the AM and report back.

Goodnight all.

Just using pool.ntp.org now.

Getting this:
The system time has changed to ‎2017‎-‎07‎-‎26T03:59:47.234000000Z from ‎2017‎-‎07‎-‎26T03:59:47.247242200Z.

But it's still 7 minutes behind...

Interesting... this just popped up in the log as well:

Time Provider NtpClient: No valid response has been received from manually configured peer 3.pool.ntp.org,0x8 after 8 attempts to contact it. This peer will be discarded as a time source and NtpClient will attempt to discover a new peer with this DNS name. The error was: The peer is unreachable.

The time provider NtpClient is currently receiving valid time data from 3.pool.ntp.org,0x8 (ntp.m|0x8|0.0.0.0:123->69.50.219.51:123).
The time service is now synchronizing the system time with the time source 3.pool.ntp.org,0x8 (ntp.m|0x8|0.0.0.0:123->69.50.219.51:123).

Result of /sync command.

I can't get into the BIOS right this minute. I am currently remoting into the server and would have to schedule downtime to check. Shouldn't Windows time and BIOS time be the same? (Sync with each other)

UT has the correct time. I am able to Telnet to pool.ntp.org port 123 (I don't get anything on the screen, but it connects via Putty)

From what I have read UT is open from LAN to WAN by default. So I believe so.