DSIA and Windows 2000

I'll check with the DSIA team and we'll get back to you soon - thanks.

Any updates on this? Thanks in advance!

sorry - I did get a reply - unfortunately not a favorable one for you - it seems that support is dropped for Win2K with OpenManage Inventory Agent - I'm trying to find more information, and if there's a work-around.

Greg

Thanks! Any workarounds you find out about would be great, then maybe I could still use it on those older servers until we're able to replace them ...

I think I might have a potential workaround, is this something you can verify with your DSIA team? Steps noted below ...

-- Download DSIA.msi dated 10/24/2008 from the FTP site.
-- Manually install it on the W2K server, try to stop the service once it's installed, but if it doesn't, the invcol.exe process will eventually fail and the service will stop anyway.
-- Once the service is stopped, download the InvCol_R188301.exe file from the FTP site. This appears to be the next lowest version of InvCol.exe (2.8.0.22 vs. 5.5 on the DSIA.msi install)
-- Replace the invcol.exe on the server with the downloaded one.
-- Run the service again, this time there are no warnings/errors in event viewer.
-- Force server to re-scan for updates in Config Manager control panel. Eventually the dialog box will appear with Dell updates if you have a deployment set up.

It would be convenient to have the older InvCol.exe already in a DSIA.msi, then I could deploy it through Config Mgr instead of installing it manually, which is what I did for this particular install ...

"I think I might have a potential workaround, is this something you can verify with your DSIA team? Steps noted below ...

-- Download DSIA.msi dated 10/24/2008 from the FTP site.
-- Manually install it on the W2K server, try to stop the service once it's installed, but if it doesn't, the invcol.exe process will eventually fail and the service will stop anyway.
-- Once the service is stopped, download the InvCol_R188301.exe file from the FTP site. This appears to be the next lowest version of InvCol.exe (2.8.0.22 vs. 5.5 on the DSIA.msi install)
-- Replace the invcol.exe on the server with the downloaded one.
-- Run the service again, this time there are no warnings/errors in event viewer.
-- Force server to re-scan for updates in Config Manager control panel. Eventually the dialog box will appear with Dell updates if you have a deployment set up.

It would be convenient to have the older InvCol.exe already in a DSIA.msi, then I could deploy it through Config Mgr instead of installing it manually, which is what I did for this particular install ..."

DSIA still supports W2K SP4, but one of inventory components, which is Broadcom NIC here, stops to support it. The error message "OS is not supported" is created by that component. However, other inventory components will still work properly. The invcolexe process will return partial failure in this situation. This error message is just a notification, it does not mean your DSIA or other components have problems. You can still use the latest DSIA, just be aware that it won't detect Broadcom NIC any more, if you have one on your system.

Your above workaround could eliminate the error message, but we don't recommend it. Since the latest invcol.exe within DSIA may include new features, improvement, as well as some bug fixes if we have.

Thanks for the information, good to know that the current version of DSIA still works with W2K. I've imported your most recent Dell catalog into SCUP, and publish the update into SCCM/WSUS, but then when the W2K machines scan for the update, SCCM shows it as compliant, so they do not receive the package so it can be installed. Looks like the applicability and pre-requisite rules show a minimum of W2K SP4, is there something else in the package rule that's preventing it from working on W2K machines?

Looks like the "Windows Version" rule is fine, but the WMI query may have an issue. The query in the package is ...

SELECT * FROM Win32_ComputerSystem WHERE (Manufacturer >= 'Dell' AND Manufacturer

.. and according to the MSDN documentation, the LIKE operator is not available, so the query fails. Is there a substitute query I can use that will work with Windows 2000, then I could use the package there as well?

Most of the Windows 2000 servers I have don't have any DSIA on them. Do I need to install the older version first before upgrading the latest one, or can I just install the latest one and it will still work?

"Thanks for the information, good to know that the current version of DSIA still works with W2K. I've imported your most recent Dell catalog into SCUP, and publish the update into SCCM/WSUS, but then when the W2K machines scan for the update, SCCM shows it as compliant, so they do not receive the package so it can be installed. Looks like the applicability and pre-requisite rules show a minimum of W2K SP4, is there something else in the package rule that's preventing it from working on W2K machines?"

Another rule will be MSI package and its version. The catalog will carry the latest version of DSIA package. If a managed system already has the latest version installed, SCCM will show Compliant.
You can try to remove the previous dsia manually, then start a scan to see whether it shows applicable or not.

P.S. I manually tested upgrade dsia from 10/24/2008 version to the latest one dsia_R229373.msi, which is defined in the latest Dell SDP catalog. Upgrade works.

Also, when I install the DSIA_R229373.msi package on a Windows 2000 server, it installs successfully and starts to run. When it's done running, it gives me a dialog box with an error that says:

===========================================
SASDUPIE.exe - Entry point not found

The procedure entry point RegDeleteKeyExA could not be located in the dynamic link library ADVAPI32.dll
===========================================

Is that related to the Broadcom issue, or is this something else altogether?

"Also, when I install the DSIA_R229373.msi package on a Windows 2000 server, it installs successfully and starts to run. When it's done running, it gives me a dialog box with an error that says:

===========================================
SASDUPIE.exe - Entry point not found

The procedure entry point RegDeleteKeyExA could not be located in the dynamic link library ADVAPI32.dll
===========================================

Is that related to the Broadcom issue, or is this something else altogether?
"

This is NOT a Broadcom issue. But it seems to be the same reason of unsupport Win2K. I need check with SAS team.
Dell has dropped Win2K support, so you may encounter some issues during inventory and update.

"Looks like the "Windows Version" rule is fine, but the WMI query may have an issue. The query in the package is ...

SELECT * FROM Win32_ComputerSystem WHERE (Manufacturer >= 'Dell' AND Manufacturer

.. and according to the MSDN documentation, the LIKE operator is not available, so the query fails. Is there a substitute query I can use that will work with Windows 2000, then I could use the package there as well?"

You are right W2K WMI doesn't support LIKE. We used to take care of it in Dell SDP catalog. Since we dropped W2K support, our engineer doesn't pay more attention to it, I guess.
Technically, there is a workaround. The query could be modified as:
SELECT * FROM Win32_ComputerSystem WHERE (Manufacturer >= 'Dell' AND Manufacturer 'PowerEdge') AND (Model = 'PowerVault') AND (Model

"Most of the Windows 2000 servers I have don't have any DSIA on them. Do I need to install the older version first before upgrading the latest one, or can I just install the latest one and it will still work?"

No need to install an older version. It supports fresh install.