If you host your Azure MFA User Portal outside of your MFA Server e.g. in a DMZ , the User portal server has to speak to this MFA server via SSL using the SDK and also via a certificate. Make sure the SSL of you MFA server is valid. It might be self signed internally on that server ( cannot be from the domain as the DMZ server can’t speak to your domain ) so you need to create a new one and transfer it securely to the User portal and install it on the Trusted Root Authority 

System.Security.Authentication

This certificate cannot be verified up to a trusted certification

• No Comments

Trying to login to the Webportal of GFI Archiver brings up a basic authentication prompt. It should use your signed in credentials to SSO into the App

Recycling the site Application pool in ISS and was then able to login successfully.

• No Comments

Latency Threshold – I would say to start with 50-60 Seconds to avoid any false positives.

Failure Counter threshold –  I would suggest to start with 5-6 for the same reasons.

Admin Notifications – I would suggest to notify via SMS as well, in case email is down. But if you are doing that, you will firstly have to make sure you are syncing the Mobile numbers from AD using the correct AD Attribute in Mimecast(https://community.mimecast.com/docs/DOC-1478). Then you also have to make sure that you set that attribute up to be used as the mobile attribute for SMS notifications in Administration > Account > Account Settings > System Notification Options. Then, you also have to make sure that the admins that need these SMS notifications, subscribe to them. Guidance on subscribing here – https://community.mimecast.com/docs/DOC-2085. Further details on using SMS in Continuity Here – https://community.mimecast.com/docs/DOC-2104.

Affected Group – You have to select a group that covers all users. Otherwise when you get the notification, if you opt to start a Continuity Event from the dashboard, it will only affect the Admin group you have selected.

• No Comments

Upgrade VCenter

In order to ensure protection is not affected when upgrading or replacing a vCenter, the vCenter database should be preserved

Upgrade then make sure Replication all comes back green

Upgrade Hosts

Before Upgrading the Hosts to the latest ESXi , double check the current version of Zerto supports the version you are putting on or you will get the error on Upgrade “VRA unsupported esx version”

Migrate all VM’s to other VPG’s , migrate 6 VM’s at a time

Once VM’s migrated , shutdown VRA and VRAH , restart upgrade host

You can migrated VCC machines to other hosts without effecting replication

https://nolabnoparty.com/en/vsphere-6-7-upgrade-esxi-6-5-to-6-7-pt-3/

• No Comments

Check the below

http://prev.mydomain.com:18681/admin [Running, Access from Work Server]

Steps

1. Restart Prizm Service on your Preview Server is not started

    

2. Check registry on your Workserver

   – Ensure the registry MSH Host contains the correct value in the following format: ‘http://hostname:PortNumber’

   – Ensure the registry PAS Host contains the correct value in the following format:

   ‘hostname:PortNumber’

   Note: The port number should be the same in both registry entries.

    

3. Check the configuration file ‘rendition.cfg’ on your Workserver to ensure that the ‘RenditionEngineAlpha-Preview’ section is pointing to ‘end_point = http://hostname:18681/PCCIS’

    

4. Install the same SSL cert (as used in the Work10 server) into the Preview Server

    

5. Restart the following services (even if it is started) from your Work10 server

   iManage Active MQ
   iManage Micro Services Hub

6. clear Preview Cache manually, please perform the following steps:

   1. Delete all cache from the DOCPREVI user in the correct file server
   NOTE: Delete all content within this folder, do not delete the DOCPREVI folder itself
   2. Delete all Preview cache from the rendition_cache table in the database. To do this, run the following:
   delete from mhgroup.rendition_cache where storage_class = ‘docpreview’

7. Make sure as mentioned above that “Preview Storage” on your DB’s in DB Admin are checked off
8. Check Rendition.cfg configurations
9. Check that the service account can read and write to the preview cache.
10. Reinstalled the Preview server software

Logs

MsOfficeConverter.log in Preview Server:

• No Comments

PreReq

• VM Shapshot
• Backup Registry ( HKEY_LOCAL_MACHINE\SOFTWARE\Interwoven and HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Interwoven ) 
• Backup C:\Program Files\Autonomy\WorkSite\Apache\conf\worksite.conf
• Have your WorkSite Server Serial Number Ready
• Have your .key and .crt files for your Certificate
• Check what iManage Work Server Service user currently runs as

Installation

• Run Installer over the top
• Enter Serial Key and Certificate Files
• Once Installed Reboot Server
• Change the iManage Work Server service to Run as a specified user found in PreReq

• No Comments

Navigate to your imanage webserver Control Center

https://imanage.domain.com/work/web/cc/

Define the user in the group listed as Yes , or click No to allow all user access

• No Comments

• No Comments

Symptoms:

• Hang on Receiving Emails
• Delay or Hang when typing

• Inbox Filer

Symptoms:

• No Comments

Work 9.X

• Middleware logging – > Provides logging on the iManage.dll. Client talks to Server. Use for Login issues, Refiling, displaying folder content
• Integration logging – > Used for logging Office issues. Lost Edits, errors, 0 byte files
• iManext logging – > Extension library. Dialogs and all functions of  WorkSite
• EM logging – > Toolbar not loading, performance issues, filing issues
• FileSite / BulkLoader – > FileSite provides logging for client side filing requests
• Suggested Filing -> Logging to understand why a specific suggestion is made to user or none at all
• WSMapi logging  – > Filing operations using the Inbox filer, Sent Items filer, and filing suggestions or saving attachments
• OffSite –>Performance issues during syncing, errors, and why content is not synched

• No Comments