Messages - x16wda [ switch to compact view ]

Pages: prev1 ... 3 4 5 6 7 [8] 9 10 11 12 13 ... 173next
36
If there was a password change recently then usually a phone, people don't ever remember to change the password there also. Also go into credentials manager (control panel) and cleat the stuff out. but look at the 4740 security event for the machine name, usually (not always) there's one listed.

For tougher cases you can turn on netlogon logging on the dc (google it, and don't forget to set a size value, 32mb should be fine but i think it's in bytes) and check the log, that can help identify indirect causes, the log is in windows\debug\netlogon.log which is renamed to .bak when it's full.

37
T-Clock / Re: Not working at all
« on: May 31, 2021, 08:28 AM »
Do you have an antivirus/antimalware program where you can whitelist files and/or folders? It honestly should be pretty straightforward unless there is something actively interfering.

38
T-Clock / Re: Not working at all
« on: May 25, 2021, 06:19 AM »
I know we've covered this recently but don't have time to find the other thread. T-Clock Redux works great in Win 10, currently I am on 20H2. My instructions for "installation" are here (it isn't a run-installer kind of install), these are for an older release but the process is exactly the same:

How to set up T-Clock 2010 build 95

1. Copy the entire T-Clock folder (contains Waves, Win32, x64 folders) into Program Files
2. Run clock.exe from the subfolder of the proper bitness
3. Right click and choose T-Clock Properties
4. On the About tab select Start T-Clock when Windows starts
5. On the Clock Text tab, choose Marlett, size 8 neither bold nor italic
6. On the Time Format tab, check Custom Format and set it to hh:nn:ss  POSIX\ndddd mmmm d, yyyy
7. On the Mouse tab, set the Action to Show Calendar and set the tool tip to dddd mmmm d, yyyy

Steps 5-7 are my preferences, replace with whatever you want.

39
Living Room / Re: Interesting "stuff"
« on: May 22, 2021, 10:08 AM »
Fwiw, in my recent experience, there is a lot of ransomware that doesn't give a whit if it's running on a VM. Considering the virtualization of America's businesses, it does not surprise me at all that ransomware doesn't hold back on a VM any more.

But for that - just so everyone knows - best practice is (1) don't link up your VMware to use domain credentials, and (2) don't back your stuff up to permanently connected repositories (like "my backup drive is an iscsi connection to a big disk array") or to a NAS that is linked to the domain. Those things mean that bad guys who acquire domain admin have access to all your assets and can scramble at will. Sending copies offsite is the best.

And worst case your business pays and gets it all back, then you have to fix your external access holes RIGHT AWAY because successful perps often sell your system access to additional bad guys.

And also fwiw, I installed the Russian language on my home PCs after reading this because there's no down side and might be free, albeit iffy, protection.

Edit: and if you do that just remember, Windows-Spacebar lets you switch back to your preferred language when you accidentally switch to Russian.  :D

40
Depending on the Acronis product, some of the boot disks have a separate task (separate from backup/restore) to adjust the O/S for new hardware. If your Acronis boot disk has that, try running it.

And if you have downloaded the drivers for your new hardware, maybe put them all on a USB stick, you can point Acronis to this new group of drivers to make sure it sees what is needed.

Pages: prev1 ... 3 4 5 6 7 [8] 9 10 11 12 13 ... 173next
Go to full version