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.
Recently a newly installed Vocus link was running 100mb Down but only 30mb up , multiple back an forths with support showed the link back to vocus was fine , however the speed was still bad.
Finally they told me the answer , the package ordered was not full 100mb up!
Best Effort Internet Access
VBU is delivered to site using Telstra Wholesale Ethernet Access (Fibre) Standard CoS (Class of Service) access tails. Note Standard CoS is 100% EIR (Excess Information Rate) which means, under congestion in the Telstra network, this traffic may be discarded. If the customer requires an Internet Service with continual sustained throughput or other medium to high performance requirements, please use Vocus IP Transit or Enterprise Internet rather than VBU.
Recommended VCT or VIE onnet service
or alternatively Telstra tail can be made premium.
$mon = [System.DayOfWeek]::Monday
$tues = [System.DayOfWeek]::Tuesday
$wed = [System.DayOfWeek]::Wednesday
$thur = [System.DayOfWeek]::Thursday
$fri = [System.DayOfWeek]::Friday
cd “C:\Program Files\Microsoft Azure Recovery Services Agent\bin\Modules\MSOnlineBackup”
#This limits to 10mb during work and 30mb during Non Work hours Mon-Friday
Set-OBMachineSetting -WorkDay $mon, $tue, $wed, $thur, $fri -StartWorkHour “9:00:00” -EndWorkHour “18:00:00” -WorkHourBandwidth (10012*1024) -NonWorkHourBandwidth (30048*1024)
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
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”
Once VM’s migrated , shutdown VRA and VRAH , restart upgrade host
You can migrated VCC machines to other hosts without effecting replication
Check the below
http://prev.mydomain.com:18681/admin [Running, Access from Work Server]
- Restart Prizm Service on your Preview Server is not started
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:
Note: The port number should be the same in both registry entries.
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’
Install the same SSL cert (as used in the Work10 server) into the Preview Server
Restart the following services (even if it is started) from your Work10 server
iManage Active MQ
iManage Micro Services Hub
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’
- Make sure as mentioned above that “Preview Storage” on your DB’s in DB Admin are checked off
- Check Rendition.cfg configurations
- Check that the service account can read and write to the preview cache.
- Reinstalled the Preview server software
MsOfficeConverter.log in Preview Server:
- 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
- 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
Recently we changed the IP and Subnet of an exchange 2016 server. Trying to Open ECP Showed the Error :
Topology Provider coundn’t find the Microsoft Exchange Active Directory Topology service on end point
This is due to the Server Microsoft Exchange Active Directory Topology not starting
The service was not starting because of the new Subnet was not listed in Active Directory Sites and Services which meant Exchange was not sited aware
Add the domain and restart the server
This was due to a misconfiguration on the vsf
type "JL255A" mac-address xxxxxx
link 1 2/23-2/24
link 1 name "I-Link2_1"
link 2 name "I-Link2_2"
Should of been :
type "JL255A" mac-address xxxxxxxxx
link 1 2/23
link 1 name "I-Link2_1"
link 2 2/24
link 2 name "I-Link2_2"
Commands to run to remove a link from a vsf member :
no vsf member 2 link 1 2/24
vsf member 2 link 2 2/24
Navigate to your imanage webserver Control Center
Define the user in the group listed as Yes , or click No to allow all user access