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.

Fix

Recommended VCT or VIE onnet service
or alternatively Telstra tail can be made premium.

• No Comments

$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”

Import-Module .\MSOnlineBackup.psd1

#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)

• 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

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 

• No Comments

This was due to a misconfiguration on the vsf  

  member 2

      type "JL255A" mac-address xxxxxx

      priority 128

      link 1 2/23-2/24

      link 1 name "I-Link2_1"

      link 2 name "I-Link2_2"

Should of been : 

  member 2

      type "JL255A" mac-address xxxxxxxxx

      priority 128

      link 1 2/23

      link 1 name "I-Link2_1"

      link 2 2/24

      link 2 name "I-Link2_2"

      exit

   port-speed

Commands to run to remove a link from a vsf member : 

no vsf member 2 link 1 2/24

then

vsf member 2 link 2 2/24

• 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

Recently we started getting errors for our Vcenter address which was a subdomain of our main domain which had a proper certificate for the website. Chrome picked this up and then uses HSTS to make sure all subdomains have a valid cert ( Without an easy option to Bypass ) 

However to bypass just type either word below when presented with the error

“thisisunsafe” or “badidea“

• No Comments

Recently on setting up a new internet connection, I ran a speed test via ( speedtest.net ) with produced the following error

Latency Test Error – Could not connect to the test server A firewall could be blocking the connection or the server might be having some issues

Pinging Google DNS Server 8.8.8.8 came up with a sold under 15m response , strange?

I tried playing around with the MTU to no avail either

Turns out this is actually a DNS issue, the local DNS servers had forwarders set to their Old ISP , so change the DNS to the new ISP or Google fixed this!

• No Comments