This is due to issues with Safari

  • Install Chrome or edge on the mobile device 
  • Change it to the default browser
  • When you try and login, choose ‘Open in Edge\Chrome’ and the authentication will work.

or

 

https://docs.microsoft.com/en-us/answers/questions/93588/ios-14-mailcalendar-multi-factor-authentication-fa.html?childToView=104889#answer-104889

 

27382-screen-shot-2020-09-23-at-112925-am.png

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Fortigate HA commands

Flick Master

*if on vdom : config global

diagnose sys ha reset-uptime

Restart Slave

 get system ha status

exec ha manage 1/0

Fix Synchronisation

diagnose sys ha checksum cluster

diagnose sys ha checksum recalculate

 

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)
  1. Document Forticloud key off the unit
  2. Document the Contract Registration Code off the Forticare license purchases with the usit
  3. Login with a forticloud and register the device to an email address with the company domain. Once done get the device on the internet and make sure fortiguard represents what you see in forticloud. If forticloud is expired out the box contact FortinetSupprt
  4. On the device add the Contract Registration Code here

  5. If the device is in HA the License with the lowest time left will be used
VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Uninstall all Webex Installations then reinstall

If you cannot do this through control panel , Use CCleaner to force remove

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)
#Change Date to when DR Started
$DateTime="2020-11-06 17:00:00.0000"
$FromPath="\\file\path"
#Make sure this folder exists and is empty
$ToPath="\\file\newpath"

#Copy Folder Structure
Get-ChildItem -Path $FromPath -Directory -Recurse | Where { $_.LastWriteTime -ge $DateTime } | Select-Object FullName, @{N="NewPath";E={$_.FullName.Replace($FromPath, $ToPath)}} | ForEach-Object { New-Item -Path $_.NewPath -ItemType "Directory" }
#Copy Files
Get-ChildItem -Path $FromPath -Recurse | Where { $_.LastWriteTime -ge $DateTime } | Select-Object FullName, @{N="NewPath";E={$_.FullName.Replace($FromPath, $ToPath)}} | ForEach-Object { Copy-Item -Path $_.FullName -Destination $_.NewPath }
#zip up
Compress-Archive -Path $ToPath -DestinationPath $ToPath"\Out.zip"
VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

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

{
    “status”: “Failed”,
    “error”: {
        “code”: “ResourceDeploymentFailure”,
        “message”: “The resource operation completed with terminal provisioning state ‘Failed’.”,
        “details”: [
            {
                “code”: “MismatchSqlVmSku”,
                “message”: “The SQL sku provided is ‘Developer’ which does not match the sku installed in the virtual machine ‘Express’. Make sure to provide the correct sku type.”
            }
        ]
    }
}
 
Its because there was an old version of SQL express installed , removing this fixed the issue
VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

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 ) 

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)