Uninstall all Webex Installations then reinstall
If you cannot do this through control panel , Use CCleaner to force remove
loading...
loading...
Uninstall all Webex Installations then reinstall
If you cannot do this through control panel , Use CCleaner to force remove
I got deployment failed when trying to change a SQL servers License from Express to Developer.
I checked the Server and it had developer license installed on SQL
Looking at the JSON
Recently trying to setup a user to be able to access IRM documents out of a SharePoint library , and when opening the documents from the browser , an error would appear
access denied contact your administrator
I tested and the user could protect documents themselves showing the IRM platform was working. I tested setting up a test AD user and getting them to sign into that and still would open in login in a ‘Modern Authentication” login loop.
In the end a fix was to download the file before opening it ( Instead of clicking from the browser )
You cannot open PDF files directly to Adobe Reader due to Adobe not releasing their API to Intunes SDK
Workaround :
Error Details
=============
An error of type E_PARSE was caused in line 17 of the file . Error message: syntax error, unexpected ‘class’ (T_CLASS)
Upgrade PHP Version to latest
When trying to open up a DMG file on MAC Osx Catalina , the error showed “no mountable file systems”
This is due to a correct DMG , recopy the files
Had a user trying to reauthenticate her Iphone Mail , however after clicking approve on the App , it would just wait on the below screen ( it should refresh after receiving the push approval and go back to Mail )
Tried rebooting and re-adding the Mail account to no avail
1) Upgrading all Apps and Iphone IOS version resolved it
2) If you kill the mail app then go to settings and update the password there it works, happens every few weeks for me
3)
I’ve found that the native iOS mail app will go into an endless loop unless you tap on the top-right to go back to Settings, then it will complete the sign in process:
Probe status code mismatch. Received status code is different from expected 200-399.
Make sure if you have multiple subdomains you create a “HTTPS Setting” for each site along with a custom “Health Prope” to assign
Unlike WAF v2 , the v1 product does not have custom rules for blocking IP , so you will need to do this at the IIS Level still
When the WAF forwards the request it tags on “x-forwarded-for” to the HTTP header and leaves the c-ip ( client IP ) the same
By Default IIS will check IP Address Domain and Restrictions list on the site and block the c-ip ( client IP ) using this list.
Enabling Proxy Mode ( In IIS 8 and up ) means it will also adhere to the x-forwarded-for , but you will need to add the Subnet of the WAF ( as it picks a different IP each time ) to the allow list as well or the Health probe won’t be able to make sure the site is UP