Posts Tagged ‘Upgrade’

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

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


  • 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
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 upgraded a IPV500 v2 phone system from Version 9 to 10 and had a phone stuck on 



To perform a reset in the Craft Menu you can try clearing the phones values so that when it establishes DHCP again it’ll point to the PBX (as long as the port its connected to has a route to the PBX).

Reboot the phone and when you see the “Press * to program” screen, press it and try entering the passcode as (CRAFT) 27238#.. Thats the default so it may not work on all phones. If it works, scroll down to “Clear values” and select it.

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

Download the .tgz upgrade file from here

Save your configuration first ( remember this does not save automatically ) and backup a config backup.

If this is a virtual machine do a snapshot / chekpoint

Let’s get started with the upgrade wizard:

NetScaler upgrade wizard

select the location for the firmware file:


Next, verify the licenses you have already installed these will work with the new netscaler and begin the upgrade.\

NetScaler upgrade warning

The upgrade will take down the gui first , then after the netscaler when it says rebooting

Other key things to note – the upgrade has turned back on SSLv3 support on the Gateway vServer…however, it has enabled support for TLSv1.1 and TLSv1.2 which was missing from the 8007.e release. Nice!




The new web interface will look like below

If you see a solid black screen after upgrade you will need to delete your cache or do a CTRL and F5



Double check the SSL Profile on your virtual server make sure it’s set to : ns_default_ssl_profile_frontend

With SSL3 off and TLS 1.2 on , you can check via :

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 an Veeam Backup and Replication Software was upgraded from v8 to 9.5 , to fix an issue with Internal Database

Failed to copy item ‘\\network\Location’ Error: The filename, directory name, or volume label syntax is incorrect

this feature is not supported since version 9, so this might work but the product does not guarrantee this feature would work properly, and unfortunately we do not support features that does not supported by the version you are using.

please see this guide:

it says “You cannot use deduplicating storage appliances, shared folder backup repositories and shared folders as a source for the file copy job.”

This is annoying as it did work with Older Versions , in the end , I have to add \\network\Location\Folder ( extra folder on the end ) for the source folder instead of \\network\Location

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

Find the latest Firmware :

Setup TFTP Server ( Download : )

Copy Bin file to TFTP Directory

3650-SW1#copy tftp flash

3650-SW1#Address or name of remote host []?
3650-SW1#Source filename []? cat3k_caa-universalk9.SPA.03.06.06.E.152-2.E6.bin
3650-SW1#Destination filename [cat3k_caa-universalk9.SPA.03.03.01.SE.150-1.EZ1.bin]?<enter>

3850-SW1#software install file flash:cat3k_caa-universalk9.SPA.03.06.06.E.152-2.E6.bin switch 1-4

The install should ask you to reload which will restart the whole stack ( All Stack members should run the same IOS ) 

If the SSH console disconnects during the install progress you will need to do an Manual Reload Command

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


Was recently trying to update a PS6000 SAN from Firmware upgrade Failure from V5.0.8 to V6.0.7

FYI when trying firmware updates make sure you have the passive controller setup , as this will take the controllers offline during the update.

The error displayed was the type 11 controller is not supported by this firmware

 Upgrade your 5.0.8 to 5.2.x first and than to 6.0.7.

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

MacRDPClient[1]Recently upgraded a 2008 R2 Server to Enterprise from Standard using

 Dism /online /Set-Edition:ServerEnterprise /ProductKey:xxxxx-xxxxx-xxxxx-xxxxx-xxxxx

Wouldn’t work with the customers Volume License Enterprise Key. I used the KMS key which did work and activated using the Volume license key again , however on restart the server could not be remote desktoped in.

I had to run a 


Restart the server and reactivate it using the proper Volume license key. After this , restarting the Remote Desktop Service enabled RDP to work again


You should check in the Computer settings , that the memory is not set to 4GB Usable out of the new memory allowance. If this is the case you will need to do the following

  1. Open the command prompt and change working directory to System32 directory
  2. Type in slmgr.vbs -ckms (this clears and KMS entry you may have)
  3. Type slmgr.vbs -upk (this removes any product key installed)
  4. Type slmgr.vbs -ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx (where the x’s is the new product key you want to use )
  5. Type slmgr.vbs -ato (this activates the server)
  6. Restart Server


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

You can loign to here for upgrade advisor for OnTap Data Upgrades , should have shout home stuff about your drives firmware recommendations 

Drive Firmware

Use to find the current firmware

*> storage show disk -x

To do the disk FW upgrade on the background, check the following is enabled:

options raid.background_disk_fw_update.enable

Disk Firmware Update Location :

Download the .LOD files to \\fascontrollerip\c$\etc\disk_fw

Disk firmware files should have been installed correctly to the system. Within two minutes the system should detect and begin updating any eligible drives.

Shelf Firmware 

Check this setting is enabled

options shelf.fw.ndu.enable



Disk Shelf Update Location :

Download the .SFW files to \\fascontrollerip\c$\etc\shelf_fw


storage download shelf

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