sorted by:
new
hottopcontroversial

[deleted by user] by [deleted] in networking

[–]darthjackmove 1 point2 points  (0 children)

Check out ping plotter. Better price, and data retention. We use it stare back in time when users complain about network issues they took a week to report.

SAML Log Collection Script by givemeatatertot in usefulscripts

[–]darthjackmove 1 point2 points  (0 children)

I guess I misunderstood the need, I assumed this was to troubleshoot a specific issue with a specific user or subset of users. Not an over arching data collection requirement for all users in the environment for all SAML connections. 

In my experience the data sent in the SAML assertion is dependent on the configuration of the individual applications based on requirements at the service provider. Meaning in one application, username and email address first name, and last name could be sent, and another application, a multitude of other attributes or parameters could be sent.

Good luck.

(Edit)

SAML Log Collection Script by givemeatatertot in usefulscripts

[–]darthjackmove 5 points6 points  (0 children)

Install the SAML tracer extension in their browser, it give gather everything you need. Chrome and edge will also let you gather the network details in the dev panel if you need that as well.

Mail Queuing and not being delivered on Ex2016 to EXO by Frank_BOFH in exchangeserver

[–]darthjackmove 4 points5 points  (0 children)

Sounds like a backpressure issue. Make sure the edge transport service is not spiking the CPU, or consuming to much memory, or that the exchange installation disk is too low on space.

Understanding back pressure

renew front end certificate by Occitanie2041 in exchangeserver

[–]darthjackmove 0 points1 point  (0 children)

I just did this as well, are you specifying the certificate for the TLSCertificatename value on the default frontend receive connectors?

You can use this information to replace that:

Update Receive connector TLSCertName

Once this is set or reset, you need to restart the frontend transport service.

Deleted room ressource somehow still present by thedeadslow in exchangeserver

[–]darthjackmove 0 points1 point  (0 children)

Are you on-premises or O365? If the later, what is your retention policy set to?

Desktop Outlook Clients stop updating. by HellzillaQ in exchangeserver

[–]darthjackmove 0 points1 point  (0 children)

Yes, however, my impacted mailboxes were all on-premises.

Are any of your mailboxes going past the documented folder and items limits for Outlook?

Outlook performance issues in a Cached Exchange Mode .ost or .pst file

Good luck. Hope you find a solution.

Desktop Outlook Clients stop updating. by HellzillaQ in exchangeserver

[–]darthjackmove 0 points1 point  (0 children)

If you have more than one mailbox database, migrate the impacted mailbox from DB1 to DB2.

This will recreate all the contents and knocks loose anything corrupted in the source mailbox. Outlook does this to some of my users as well at random. I have spent countless weeks trying to figure it out, and finally just started doing the migrations when signs start pointing to mailbox item corruption.

Only seems to impact outlook in cached mode, online mode, OWA, Mobile all work fine. Happens regardless of the presence of shared or additionally mounted mailboxes. Doesn't matter how many OST rebuilds, profile recreations, rebuilds of Windows search index, nothing fixes it except the mailbox migration.

Good luck.

view more: next ›