On top of confirmed WiFi failures (previously reported and diagnosed) I faced more "fun" recently. Kala & I have commissioned an update of some lower level rooms at Blodgett. This is one of the only spots in this home that we have not touched; there and the kitchen (for obvious $$$ reasons)... it's just 3 rooms plus stairway but held a lot of our computer gear. Big workstations (including MLC's game setup), and my server (Win7) for images, other media, DVR system with remote access, terrestrial broadcast TV packet grabbing, IoT central, automated backup systems, local & remote FLAC music streaming, whole house printing services from any device, and much more, was in the basement and needed relocation during construction. With some trepidation, but forever technically brave, I tore down the lower level systems and networks and furniture and moved the 20TB raided server and associated peripherals to my study. To my glee it all came back up without error; I tested at a cursory depth before heading to the Nest for a weekend with friends. All good... hear you 5 X 5.
Yet, the next day, I installed KB4480970 security update from MS and all secured network file access began to fail. It is only this clear now as the server updates tend to come in massive Windows blobs of stuff. Given the near simultaneity of the move, the update, and the WiFi configuration bullshit, I thought it was me in some way. I dove again for a night or more on Win security settings and regained access to some files from some platforms, but not my Win10 audio station driving my primary headphone audio system! I took a breath and left for the mountains without full access and repair. Returning and diving again on forums, blogs and the like I discovered a similar problem described by folks installing the above-named update. WTF... how can MS crash their own security mechanisms in an update. I rolled back from the subject update today and all is recovered - yet, I need to mitigate the security damage I wrought (setting file level accesses to Everyone/Guest) to regain access before the shit-storm. MLC suggests Linux for the media server but what a day that would bring... I'm getting closer to that - or cloud services replacing everything, but that would be expensive in the LT. How can a non-tech person handle any of this shit is beyond me... why we need to put up with this is also beyond me.
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.