In the aftermath of updating Windows 10 a customer was presented with a different looking login screen and had their PIN number rejected. I guessed correctly that the customer's Microsoft account (cloud based) had been set as the new login method. The fix was to use another computer to perform a password recovery at login.live.com. I'm seeing all manner of odd changes and problems after the large Windows 10 updates that have been coming down in 2018 including login issues,
A lawfirm called today about data recovery of a "backup" drive. A site visit revealed the always fatal "click of death" sound emanating from the drive. It soon became clear this was no backup drive but rather the save point for an ongoing project to scan decades of files. Three years of time scanning wasted plus many of the source files had been destroyed creating a liability problem. Lesson: In a small office without a server never target an external or portable drive a
Friday 12-16-2016 10:00 - 2:30
Comcast router configuration
- Setup DHCP (10.1.10.50 - 250)
- Setup the 2.4Ghz and 5.0GHz wireless networks.
Ubiquiti initial setup
- Connected 6 PoE (power over ethernet) power adapters to the
network and the Ubiquiti wireless access points in a test configuration.
- Setup Ubiquiti WiFi management station; configured the primary
and guest SSID names and passwords.
- Created the Ubiquiti cloud account.
Phone system setup
Responded to complaint that FTP access was down
- Began troubleshooting FTP access to the Linux based server
appliance. (Note it had been running 419 days since the last reboot.) - Applied the available updates and rebooted.
- Successfully tested onsite access to the FTP interface. - Discussed and demonstrated Filezilla FTP access and use to onsite personnel. Note - for this occasional client, not under a service contract, their server ran 419 days with zero maintenance
- Recorded the build and patch level of Exchange; performed full backup. - Downloaded Exchange Service Pack 3 upgrade.
- Created test mailbox in order to send and receive test messages. Small messages without attachments were sent and received quickly. Too large messages did not send and receive.
- Increased incoming and outgoing message sizes
- Incoming message limit was 10mb. The outgoing attachment size was limited 20mb and staff was instr
- Began setup of new server and domain based on a Dell R220, a router set to Comcast NAT addresses and a Windows 8.1 Pro- fessional workstation.
- Did the initial setup of Microsoft Server 2012 and began install- ing updates, creating shortcuts to administrative utilities, installing Acrobat, Firefox, etc. - Selected various server roles using Microsoft's wizard and
- Created the domain, setup DNS, DHCP, WINS.
- Created shares, a login scri
- Responded to a complaint that phones were down. Arrived onsite and pinged the in-house PBX at 192.168.16.140 with
no response. Investigated console and found power on but
screen black. Upon reboot, encountered "kernel panic" error preventing Linux startup. The controller bios showed the mirrored drive status as "degraded". Efforts to boot the remaining drive failed (due to universally panned capability of this particular Dell "RAID" controller).
- Booted th
- Checked the server Remote Desktop port and found it moved
from 3391 to 3389.
- Checked the antivirus, firewall and supplemental malware
program (Malwarebytes). Ran Malwarebytes scan.
- Analyzed files, folders and event logs.
- Created document detailing times of accesses, critical
events and the name of the Remote Desktop add-in responsible
for the unauthorized access.
- Changed the server admin account name and password; disabled
Remote Desktop access