the script is called from multiple modules in the inventory collector, MaserIE being one of them. if  you want to look in detail, do invcol --extract icconfig.xml determines the run order of the modules. there are 4 tape modules too that probably call that script. I dont think the running of the scripts can be prevented. I highly suggest calling dell and having them escalate your issue to the group that creates the inventory collector.   
Server: M610OS: ESX 4.0 u1OpenManage version:6.2.0.1 A00    The Dell OpenManage daemon dsm_om_shrsvcd does a number of things when it starts. One of the things is an inventory collection. The inventory collection compiles a tool, MaserIE, which enumerates and rescans all ESX storage adapters. However, the way the scan is being done is very inefficient. The following command is executed by MaserIE: for i in `/usr/sbin/esxcfg-scsidevs -A | /bin/awk '{print $1}'` ; do /usr/sbin/esxcfg-rescan $i &> /dev/null ; done At first this seems correct, however, with a large number of iSCSI volumes present, the enumeration rescans the following list:vmhba0vmhba32vmhba32vmhba32vmhba32vmhba32vmhba32vmhba32vmhba32vmhba32vmhba32vmhba32vmhba32vmhba32vmhba32vmhba32vmhba32vmhba32vmhba32vmhba32vmhba32vmhba32vmhba32vmhba32vmhba32vmhba32 Each rescan takes about 30 seconds, so executing this loop will result in a significant delay. A simple solution would be to pipe the output of awk to uniq, but I can't find the line anywhere. Any ideas?
ESX4 server with OMSA 6.2.0.1 takes forever to start