Import SBE package

For Lenovo ThinkAgile MX solutions that are not Premier Solutions, importing a Standard SBE package is the method used to update the solution using an SBE package.

1. Essentially, the Standard SBE package must be manually downloaded from the Lenovo ThinkAgile MX updates repository site and copied to a CSV on the Azure Local instance. It can be found as part of the Best Recipe content for those solutions that support updating via the SBE process. The following example shows the MXBR2408 Best Recipe page on the site:

   Figure 1. MXBR2408 Best Recipe
   
   
   Once the SBE package has been downloaded, extract the zip archive, which contains the following 5 files:

   • Lenovo_ThinkAgile_MX_Solution_Builder_Extension_Guide.pdf
   • LenovoSBEReleaseNotes.txt
   • SBE_Discovery_Lenovo.xml
   • SBE_Lenovo_MX<Model><Version>.xml
   • SBE_Lenovo_MX<Model><Version>.zip
2. The last 3 files in the list (file names starting with “SBE_”) are the files that will need to be imported. Microsoft suggests running the following PowerShell command on one of the nodes in the Azure Local instance to create a “Sideload” directory in the proper location:

   New Item C:\ClusterStorage\Infrastructure_1\Shares\SU1_Infrastructure_1\Sideload -ItemType Directory
   

3. Once the directory has been created, copy the 3 extracted files whose names begin with “SBE_” from the downloaded SBE package to the directory.

   Figure 2. SBE_ files in directory
   
   
4. Discover the update package using the following PowerShell command:

   Add-SolutionUpdate -SourceFolder C:\ClusterStorage\Infrastructure_1\Shares\SU1_Infrastructure_1\Sideload
   

5. Verify that the Update service discovers the update package and that it is available to start preparation and installation using the following command:

   Get-SolutionUpdate
   

6. Details about the update can be found in the output of the command, including the State of the update, which should show as “Ready”.

   Figure 3. Get-SolutionUpdate
   
   
7. If you rerun the Get-SolutionUpdateEnvironment command shown above, you should now see the SBE Family name for the update:

   Figure 4. Get-SolutionUpdateEnvironment