that’s so fucking weird :what-the-hell:

  • frogbellyratbone_ [e/em/eir, any]
    ·
    2 years ago

    control panel > system and security > admininistrative tools > event viewer > applications and services logs > microsoft > windows > printservice > operational is print history

    if you didn't have logging enabled i would Rclick operational > property > enable logging

      • AssortedBiscuits [they/them]
        ·
        2 years ago

        MacOS has its own log system. Not sure how useful this would be. The most you would be able to find is what they were trying to print and which printer they were using.

        Depending on how serious you think this is, you can always try to contact your IT department and ask them the print jobs that the suspected printer has, assuming the printer is actually managed by your place of employment. And depending on what has been printed, you can narrow down who was actually using your laptop.

        If nothing else, it creates a paper trail that you can use in case this bites you in the ass later down the road. By far the biggest issue I could see is that it's your own personal device, meaning they can always go, "it's against IT security policy to connect personal devices to the company network, your personal device might have malware this is a security risk blahblahblah."

            • WhyEssEff [she/her]
              hexagon
              ·
              edit-2
              2 years ago

              I think it was generic programming fliers of some sort. I know it's not the union fliers, I know what they look like since I designed them.