Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
cloudappliance/1901/upgrade-guide [2019_06_13 11:53] zimcloudappliance/1901/upgrade-guide [2019_06_13 12:15] zim
Line 57: Line 57:
 </code> </code>
  
-Since some customers would prefer to stay on the last patch of our previous release 1901 is different repo, which will need to be used.+Install the Enterprise repo with the following command.
 <code> <code>
 yum install https://download.storagemadeeasy.com/sme-repo-release-latest.rpm yum install https://download.storagemadeeasy.com/sme-repo-release-latest.rpm
Line 68: Line 68:
 </code> </code>
  
-After the update has completed, the 1901 repo should be removed.  This will prevent the appliance from upgrading to future releases if other patching is performed.+After the update has completed, the installed repos should be removed.  This will prevent the appliance from upgrading to future releases if other patching is performed.
 <code> <code>
 yum erase sme-repo-release -y yum erase sme-repo-release -y
 +yum erase sme-earlyaccessrepo -y
 </code> </code>
  
Line 79: Line 80:
 reboot reboot
 </code> </code>
-<WRAP center round important 60%>+<WRAP center round important 100%>
 Customers using SME’s AD Proxy program to communicate with their LDAP system may experience a problem when trying to import users manually.  When the problem occurs an error message saying “AD proxy: Active Directory Unknown error”  will be displayed.  This problem will only occur if the File Fabric has been upgraded from an older version to v1808 or v1901. The problem can be resolved by reentering the LDAP Base DN on the org. admin’s Auth Systems setup page. Customers using SME’s AD Proxy program to communicate with their LDAP system may experience a problem when trying to import users manually.  When the problem occurs an error message saying “AD proxy: Active Directory Unknown error”  will be displayed.  This problem will only occur if the File Fabric has been upgraded from an older version to v1808 or v1901. The problem can be resolved by reentering the LDAP Base DN on the org. admin’s Auth Systems setup page.
 </WRAP> </WRAP>