Scan to Email via 365 - Now blocked

[tsbservice]

Re: Scan to Email via 365 - Now blocked

Oh I bet your service team loves that. Nothing like re-inventing the wheel in front of a new customer.
Sales may get them, but service keeps them.

I have a line for that....:
" The salesperson mis-spoke, and I cannot speak to what someone else has told you. However, I can address the issue now that I know what we are dealing with "

TRANSLATION: Sales undersold you now I get to deal with it.

Man you seems to be full of right one liners.
I like that bring us some more

[mojorolla]

Re: Scan to Email via 365 - Now blocked

Man you seems to be full of right one liners.
I like that bring us some more

I can fix anything that doesn't have tits or tires. If it has tits or tires and belongs to someone else, leave it alone!

Error Code :Chairokey Interface Error. There was a problem with the person in the chair operating the keyboard.

If I take a call for dirty slit glass or paper reload, I tell the customer what happened then say " We call this a job security call "

I have a very deep voice and am constantly told "you should be on the radio". I always smile and reply "as long as I don't have a face for radio, I'll take that as a compliment"

[slimslob]

Re: Scan to Email via 365 - Now blocked

There was a problem with the person in the chair operating the keyboard.

Reminds of a sign I saw on the door to the IT department State Farm Insurance Southern California Data Processing center. "The problem exists between the back of the chair and the keyboard."

[rthonpm]

Re: Scan to Email via 365 - Now blocked

Back in my Lanier days, I used to frequently enter the fix in the service history as 'DFU' as in dumb f*cking user. If asked by the customer, I'd say the problem turned out to be a device to DFU interface issue.

I covered for another tech on my team and when he got back and had to revisit a couple of the same customers he had to call me and ask why there were so many document feeder unit issues. I had to explain to him what I was really putting down as the fix.

Sent from my BlackBerry using Tapatalk

[techandtrader]

Re: Scan to Email via 365 - Now blocked

Yammer retiring support for TLS 1.0\1.1

This message post is a reminder of the ongoing progress of retiring TLS 1.0 and TLS 1.1 protocols in Microsoft 365. As previously communicated (MC126199 in Dec 2017, MC128929 in Feb 2018, MC186827 in July 2019, MC218794 in July 2020 and MC240160 in February 2021), we are moving all our online services to Transport Layer Security (TLS) 1.2+ to provide best in class encryption, and to ensure our services is more secure by default. The changes to enforce TLS1.2+ in our service started on October 15, 2020 and will continue to propagate through all Microsoft 365 environments for the next few months. If you have not taken steps to prepare for this change, your connectivity to Microsoft 365 might be impacted. Yammer recently made a change to a certificate to ensure we support default ciphers. To view which ciphers www.yammer.com supports, please visit SSL Report How this affects your organization: Any applications that call Microsoft 365 APIs over TLS 1.0 or TLS 1.1 will need to be updated to use TLS 1.2. The .NET 4.5 framework defaults to TLS 1.1. What you can do to prepare: For information on updating the .NET configuration, please visit How to enable TLS 1.2 on clients For information regarding the deprecation of TLS 1.0 and 1.1 in Office 365, which includes Yammer, please visit Preparing for TLS 1.2 in Office 365 and Office 365 GCC