• Mr. Natural

    Mr. Natural

    @mr-natural

    Viewing 15 replies - 16 through 30 (of 573 total)
    Author
    Replies
    • I just now installed it on my work pc and no errors to report. I even checked event logs and it was installed successfully with no errors.

      The error reported appears to be related to good old flash player for windows 10.

      It seems like the first question we need to ask folks when they run into issues with the monthly updates is “what anti-malware/anti virus are they using?” It seems to be a common theme over these last several months.

      Red Ruffnsore

      • This reply was modified 4 years, 9 months ago by Mr. Natural.
      2 users thanked author for this post.
    • in reply to: The TRS-80 turns 43 years old #2286014

      I just happen to pull out an old Compaq Presario 486/66 from my basement and looking for a 3 volt coin size battery like the standard 5 volt 2032. I need to use the old solder gun to remove the battery so I want to be sure I have the right battery.

      When I first started in 1996 with the company I am still with there was one fellow that had an original 8086 pc that ran some scientific program on DOS that was tied and locked to the printer attached to the pc. We had to move the pc so I disconnected the printer and as soon as I did that the program would no longer work unless we paid the company for a new key….the company was no longer in business. I have a backup of the entire program still but have never recovered the data.  D’OH

      Red Ruffnsore

    • I’ve been pushing the July updates for the past week or more and no issues to report with any of the July updates.

      Red Ruffnsore

      1 user thanked author for this post.
    • Gee whiz. This can’t be related to all this twitter nonsense, could it?

      “Uh Bill, sorry to bug you but we had to reset your password.”

      Red Ruffnsore

    • Check to see how much free disk space you have.

      Red Ruffnsore

      1 user thanked author for this post.
    • An email from the O365 message center hit my inbox today. Part of the message is shown below. It is a reminder that Microsoft Office 2013 users will no longer be supported on Office 365 cloud services after October 13, 2020.

      It’s the usual initial message all companies release when they prepare to abandon a product. Office 2013 will continue to work, but they are wiping their hands of any future issues that may occur with Office 2013 connecting to O365 cloud services.

      The original statement was released by the message center back in September 2019 but the message was just reissued because it was “prematurely removed”. I don’t know when but it seems a bit of a co-incidence this would be re-released the day after all the Outlook drama.

      message

      Red Ruffnsore

      2 users thanked author for this post.
    • I had no issues updating all servers overnight. Including the .net patches and the IE11 update for 2012r2. This includes 2012r2, 2016, and 2019 servers. All dns servers updated.

      Disclaimer – your mileage may vary.

      Red Ruffnsore

      2 users thanked author for this post.
    • All of our DNS servers are 2012r2. I was able to update and reboot one of them today and the rest of them will be updated after hours this evening. I don’t foresee any issues but if I do I will follow up on this post tomorrow. If you don’t hear back then I would say no issues to report with the DNS server patches.

      All other updates are on hold of course, for now.

      Red Ruffnsore

      3 users thanked author for this post.
    • Nearly everyone has been questioning Microsoft on their “quality control” with the monthly updates for a long time. And I do believe a press statement was released a few months ago from Microsoft stating that they would be improving the testing process.

      I’d like to know how something like this new Outlook issue manages to get released if they have improved quality control with updates as they claim. It sounds like anyone on the monthly channel or who installed the new office updates have been affected. I don’t see how this could occur if there was testing involved before release.

      Someone from Microsoft needs to step up and explain how this Outlook issue got past their “improved quality control”.

      Red Ruffnsore

      2 users thanked author for this post.
    • Same here, that’s what I was thinking. Folks set on monthly channel are getting bit.

      Red Ruffnsore

      1 user thanked author for this post.
    • From a security standpoint, how can you secure an OS with all of these monthly new “features”.

      Red Ruffnsore

      2 users thanked author for this post.
    • I appreciate the info but we have nearly completed the removal of KB4560960 on all windows 10 systems. I don’t think I’ll be pushing that out again so that I can install a patch to fix a patch.

      I count strike 2 for Microsoft. Our windows 10 systems are all still on the April update. I never pushed the May update because of all the uncertainty. My urgency to catch up by rushing the June update cost me.

      I figured from all the uncertainty from the May update they would have resolved whatever the issues were by June. I figured wrong. I gambled and lost. That’s why I don’t like to gamble.

      Red Ruffnsore

      2 users thanked author for this post.
    • in reply to: Patch Lady – printing issues with PCL 5 drivers #2272711

      Final update – today we were up to around 150 Windows 10 systems that received the update. This morning I received 2 reports of print issues. The first was a Ricoh C3505 MPF. The second one was a Dell 2360dn printer.

      I made the mistake of playing around with the print driver on the first pc and created a mess. The second pc I uninstalled the June update for windows 10 and the problem was fixed immediately.

      Despite having 150 pc’s not reporting the issue I immediately approved KB4560960 for REMOVAL and we will be uninstalling this update.

      FYI – this marks the second month our organization has not approved the monthly 1909 and 1903 update. Our windows 10 systems are still on the April update.

      Red Ruffnsore

      1 user thanked author for this post.
    • in reply to: Patch Lady – printing issues with PCL 5 drivers #2272326

      alQamar mentioned something that has been a thorn in my side for a long time. WSD printer drivers. I would say 90% of our network print problems wind up being from a pc using a WSD printer driver. Windows 10 has a nasty habit of installing WSD printer drivers even when I setup a printer manually using the IP address of the printer. As a matter of fact last week I setup a network printer on a pc using the IP address and when I double checked the port settings it was installed with a WSD driver. I was logged into the pc as a domain admin and the computer would not let me change the port settings. It was locked down on WSD. I didn’t have time to reboot or wrestle with it so I moved on knowing we may get a call later on a printer issue.

      Red Ruffnsore

    • in reply to: Patch Lady – printing issues with PCL 5 drivers #2272126

      When I checked Susan’s link I got the impression it was an issue with the new spooler driver that was installed with the update. The only thing that I can think of that may explain why I haven’t seen this is because all of our printers are setup in AD. Print jobs are created by printer ques in AD.

      Red Ruffnsore

    Viewing 15 replies - 16 through 30 (of 573 total)