I'm a WMI newb but was wondering of the various benefits and limitations of the following. Running VBS/WMI in asp pages on an IIS server as opposed to VBS/WMI in WSH on local computer to query remote computers.
And using WMI in VB/VB.net apps to enable user input and list boxes etc. as opposed to using WMI/ASP/IIS to achieve the same end. The objective is to enable an admin to select a list of computers through a list box or even a database table, then those computers are queried/managed automatically using WMI. Wondering whether the best route was ASP pages with WMI operations or VB.net app with WMI operations embedded
And using WMI in VB/VB.net apps to enable user input and list boxes etc. as opposed to using WMI/ASP/IIS to achieve the same end. The objective is to enable an admin to select a list of computers through a list box or even a database table, then those computers are queried/managed automatically using WMI. Wondering whether the best route was ASP pages with WMI operations or VB.net app with WMI operations embedded
