Difference between revisions of "Avoid Downloading content in the Baremetal OS Deployment site when downloading Fixlets and Tasks using the Air-Gap.exe tool"

From RiceFamily Wiki
Jump to: navigation, search
(Created page with "The process to download and import updated content into an Air-Gapped IEM environment is fairly simple. The basic are as follows ... * Generate an XML file that contains the...")
 
 
Line 9: Line 9:
  
 
In testing this process, I found that the XML file is very simple to modify so that we can exclude any sites we wish.  It should be child's play to create the XML file and remove the Baremetal OS Deployment site references, gather the data for the remaining sites, and import it into IEM.  This way the Baremetal OS Deployment site is only updated when we have had a chance to test the latest version of the content using another site (oddly, this will be in the Production IEM site since it is not Air-Gapped!)
 
In testing this process, I found that the XML file is very simple to modify so that we can exclude any sites we wish.  It should be child's play to create the XML file and remove the Baremetal OS Deployment site references, gather the data for the remaining sites, and import it into IEM.  This way the Baremetal OS Deployment site is only updated when we have had a chance to test the latest version of the content using another site (oddly, this will be in the Production IEM site since it is not Air-Gapped!)
 +
 +
[[Category:IBM Endpoint Manager]]
 +
[[Category:IEM]]
 +
[[Category:Air-Gap]]

Latest revision as of 17:35, 13 February 2015

The process to download and import updated content into an Air-Gapped IEM environment is fairly simple.

The basic are as follows ...

  • Generate an XML file that contains the sites you are subscribed to and their current versions.
  • Transport the XML file to a machine with Internet access.
  • Gather the data from IBM.
  • Transport the data to the IEM Server.
  • Import the Data into IEM.

In testing this process, I found that the XML file is very simple to modify so that we can exclude any sites we wish. It should be child's play to create the XML file and remove the Baremetal OS Deployment site references, gather the data for the remaining sites, and import it into IEM. This way the Baremetal OS Deployment site is only updated when we have had a chance to test the latest version of the content using another site (oddly, this will be in the Production IEM site since it is not Air-Gapped!)