Very Computer

Platform: NT 4.0 w/ sp6a,
                SMS 2.0 w/ sp3
                 SQL 7.0 w/ sp3
                 MMC 1.2

I've created a custom made MMC for the helpdesk personnel to use.  I can run it on the sms server but when I send that file to other NT workstations, they are unable to run it.  I even go there and log on to their workstations with the SMSAdmin account and it doesn't work. The message that I get is : "Snap in failed to initialize...Name: not available...CLSID: {3AD39FC4-EFD6-11D0-BDCF-00A0C909FDDY}"

Again, I can run this custom msc file on the actual SMS server w/o any problems. I've checked the WBEM Permissions and everything is correct.  Also did a check on the COM components (dcomcnfg.exe) to make sure that "Enable Distributed COM for this computer" is checked.  As far as permissions, I'm using a full SMS Admin and Domain Admin account so that's definitely not a problem there.    The NT 4.0 workstation that i'm testing this on is running sp6a with ie 5.5 and MMC 1.2.  Any ideas would be greatly appreciated.  

Sounds like you haven't installed the SMS Admin console (and therefore the MMC snap-in for SMS) on the machines your helpdesk personnel are using.  Unlike the NT MMC snap-ins, the SMS Snap-ins do not ship with Windows.  So you need to run the SMS setup once on each machine to be used, to ensure all required snap-ins have been installed and registered.

  Platform: NT 4.0 w/ sp6a,
                  SMS 2.0 w/ sp3
                   SQL 7.0 w/ sp3
                   MMC 1.2

  I've created a custom made MMC for the helpdesk personnel to use.  I can run it on the sms server but when I send that file to other NT workstations, they are unable to run it.  I even go there and log on to their workstations with the SMSAdmin account and it doesn't work. The message that I get is : "Snap in failed to initialize...Name: not available...CLSID: {3AD39FC4-EFD6-11D0-BDCF-00A0C909FDDY}"

  Again, I can run this custom msc file on the actual SMS server w/o any problems. I've checked the WBEM Permissions and everything is correct.  Also did a check on the COM components (dcomcnfg.exe) to make sure that "Enable Distributed COM for this computer" is checked.  As far as permissions, I'm using a full SMS Admin and Domain Admin account so that's definitely not a problem there.    The NT 4.0 workstation that i'm testing this on is running sp6a with ie 5.5 and MMC 1.2.  Any ideas would be greatly appreciated.  

I forgot the simplest thing!!  That was the resolution.  Thanks a bunch.

  Sounds like you haven't installed the SMS Admin console (and therefore the MMC snap-in for SMS) on the machines your helpdesk personnel are using.  Unlike the NT MMC snap-ins, the SMS Snap-ins do not ship with Windows.  So you need to run the SMS setup once on each machine to be used, to ensure all required snap-ins have been installed and registered.

    Platform: NT 4.0 w/ sp6a,
                    SMS 2.0 w/ sp3
                     SQL 7.0 w/ sp3
                     MMC 1.2

    I've created a custom made MMC for the helpdesk personnel to use.  I can run it on the sms server but when I send that file to other NT workstations, they are unable to run it.  I even go there and log on to their workstations with the SMSAdmin account and it doesn't work. The message that I get is : "Snap in failed to initialize...Name: not available...CLSID: {3AD39FC4-EFD6-11D0-BDCF-00A0C909FDDY}"

    Again, I can run this custom msc file on the actual SMS server w/o any problems. I've checked the WBEM Permissions and everything is correct.  Also did a check on the COM components (dcomcnfg.exe) to make sure that "Enable Distributed COM for this computer" is checked.  As far as permissions, I'm using a full SMS Admin and Domain Admin account so that's definitely not a problem there.    The NT 4.0 workstation that i'm testing this on is running sp6a with ie 5.5 and MMC 1.2.  Any ideas would be greatly appreciated.