Unable to Install on SCCM R2

Please login to the system as administrator or use Run as option and run as an administrator for running the installer. Let me know this solves the issue.

Thanks,
Sumanth

Each time I have tried it is with a Domain Administrator account.

- Ensure the version of WAIK installed is the same version that installed with SP1.
- Your Site Server - was this a fresh install of Configmgr 2007, or is this an upgraded version from SMS 2003 to ConfigMgr 2007?

Can you send me the log files? greg_ramsey@dell.com

This is a brand new installation of SCCM 2007. We started with SP1 as it is a standalone install and added R2. R2 does not modify WAIK so it is the same version installed with SP1, that is WAIK 1.1. Log files are on their way.

Check your log file for the string "Site Code :" (without quotes) to make sure the site code is getting discovered properly. If it is not, then there is some reason why the installer is not finding the registry entries containing the SCCM site info. Check around the same area to see if anything is logged about not finding the site code (although that should have shown an error).

I tried again with the same result. This time it did find the registry key as I expected. The problem is that the errors are occuring before it even does the registry checks. It still is showing the error below.

3/10/2009 1:16:32 PM :: The MOF compiler flagged the MOF file as bad. The file is located at C:\WINDOWS\system32\wbem\mof\bad\PowerEdgeDeployment.mof

It is able to find the site code. See below.

3/9/2009 3:00:55 PM :: GetSafeRegistryStringValue: Trying standard .NET call to registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Identification\Site Code
3/9/2009 3:00:55 PM :: GetSafeRegistryStringValue: Value returned = 'LAB'

There is an error however when it is looking up the UI Installation Directory.

3/9/2009 3:00:55 PM :: GetSafeRegistryStringValue: Trying standard .NET call to registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Setup\UI Installation Directory
3/9/2009 3:00:55 PM :: GetSafeRegistryStringValue: Registry key not found.
3/9/2009 3:00:55 PM :: GetSafeRegistryStringValue: Could not access the registry key (32-bit machine):HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Setup\UI Installation Directory

I checked and this key is blank right now. There is an entry for UI Installation Directory under HKLM\SOFTWARE\ConfigMgr\Setup that points to the AdminUI folder under my Config Manager installation. I can try copying this key information into the location that it is looking. Please note that Config Manager is currently running with no errors right now and we have done nothing to modify the registry on this machine at this point. I have no problems making the change as the server is not currently in production but it seems that there may be some discrepencies between installations. Clearly the UI Installation Directory key does not always reside where the DPP installation is looking. Not sure if this is a result of installing SCCM R2 or what.

can you forward (or post) the PoweredgeDeployment.mof that it reports marked as bad ?

When you install a site server, the "UI Installation Directory" key will be blank, so that is expected.

What may be happening is either
(1) the site code is not getting injected into the MOF file properly (look in the MOF file for "REPLACESITECODE" and if found, that's the problem)
or
(2) something is preventing WBEM from properly adding the WMI class information. You might try looking in the wmiprov.log file to see if there are any further details about the error. See this for more info: http://msdn.microsoft.com/en-us/library/aa394564(VS.85).aspx

I can see the lines that it is erroring on in the mof file. These and the lines just before them are posted below.

[ CommandLine("smsswd.exe /run:%1 cscript OemDeployment.vbs auto DellSrv"),
VariablePrefix("DellSrv"),
ActionCategory("Dell Deployment,1,91"),
ActionUI{"..\\XmlStorage\\Extensions\\bin\\Deployment\\Dell\\PowerEdge\\PowerEdgeDeployment.dll", "Microsoft.ConfigurationManagement.OemDeployment.Dell.PowerEdge", "DellPowerEdgeDeploymentCustomAction", "DellPowerEdgeDeploymentCustomActionOptions"},
ActionName{"..\\XmlStorage\\Extensions\\bin\\Deployment\\Dell\\PowerEdge\\PowerEdgeDeployment.dll", "Microsoft.ConfigurationManagement.OemDeployment.Dell.PowerEdge.Properties.Resources", "DellPowerEdgeDeploymentCustomAction"}
]

class Dell_PowerEdgeDeployment : SMS_TaskSequence_Action // specifies a unique name for this item, derived from the base action class.
{
[TaskSequencePackage, CommandLineArg(1)]
string PackageID;

[VariableName("DellSrvPassword"), Secret]
string TaskPassword;

[VariableName("DellSrvLogPassword"), Secret]
string LogPathPassword;

[VariableName("DellSrvControlValues")]
string ControlValues;

[VariableName("DellSrvClientActions")]
string ClientActions;

string SupportedEnvironment = "WinPEandFullOS";

};

I checked the poweredgedeployment.mof file for "REPLACESITECODE" and could not find anything for that. It does appear to be picking up the site code as it shows as LAB in several lines. The full contents of the MOF file are too long for the message board so I will just post where the site code shows up.

// SMS Root Storage
instance of __Namespace
{
Name = "SMS";
};

#pragma namespace("\\\\.\\root\\SMS")


// SMS Database name for this machine
instance of __Namespace
{
Name = "site_LAB";
};

#pragma namespace("\\\\.\\root\\SMS\\site_LAB")

#pragma classflags("forceupdate")


I looked in the wmiprov.log file but could not find anything that relates to the times that I have tried running the installer. The only error I can see has been happening since the server was built (see below).

(Fri Mar 06 15:16:38 2009.276859) : WDM call returned error: 4200
(Fri Mar 06 16:14:30 2009.3749656) : Received Event

I did find an error within the mofcomp.log file that corresponds with the last time I tried running the install. That error is below.

(Tue Mar 10 13:16:32 2009.335070828) : Parsing MOF file: C:\WINDOWS\system32\WBEM\MOF\PowerEdgeDeployment.mof
(Tue Mar 10 13:16:32 2009.335070937) : An error occurred while creating object 3 defined on lines 37 - 56:
(Tue Mar 10 13:16:32 2009.335070953) : 0X80041002 (Tue Mar 10 13:16:32 2009.335070953) : Class, instance, or property 'SMS_TaskSequence_Action' was not found.

This appears to be the root of the issue but I am not sure how to fix this.

The line:

Class, instance, or property 'SMS_TaskSequence_Action' was not found

tells me that something in WMI is not set up correctly so that the appropriate WMI classes can be added for SCCM. Basically, the installer adds new WMI classes into your SCCM site structure so that the task sequence editor can know about and use the new task steps. The problem that appears to be happening is that the installer expects to find the "root\SMS\site_LAB" namespace, and within that the "SMS_TaskSequence_Step\SMS_TaskSequence_Action" class and then insert the new WMI class based on this MOF file, which derives from the SMS_TaskSequenceAction class.

If you've installed a site server, then this namespace and class should exist without a doubt. If WMI is not finding the class, then there are a couple of possible reasons:

(1) The class does not exist - this would mean you're not on the site server itself and trying to install, or that the installation of SCCM is toast
(2) The account you're using to install does not have sufficient permissions in WMI to see the namespace, so I would recommend installing as admin

If neither of the above apply, the next thing I would try is to look in WMI via something like WMI CIM Studio and verify the namespace and class exists.
You can get WMI CIM Studio at: http://www.microsoft.com/downloads/details.aspx?FamilyID=6430f853-1120-48db-8cc5-f2abdc3ed314&DisplayLang=en

I am using Domain Admin rights on the site server during the install. SCCM seems to be running with no issues. There are no errors being indicated in either the Event Viewer of the machine or the Configuration Manager Component Status.

I downloaded and ran the WMI CIM Studio. I did find the root\SMS\site_LAB namespace but did not find the SMS_TaskSequence_Step\SMS_TaskSequence_Action class. In fact there is not a single SMS_ class in the entire namespace and I would expect there to be several. I did a search within the namespace and got no results. I went all the way back to the root namespace to see if the class was misplaced in another namespace and again got no results. I would figure that this would be causing me major issues in SCCM but so far it has not. I have been able to run task sequences, inventories, full OS deployments, etc. from SCCM with no issues. I am about to setup a separate lab environment to see if another installation will resolve the issue.

One more quick question? Is this app supported in a virtual environment? I would assume that it is but I am just checking to make sure.

Virtual environment shouldn't make a difference.

It is really odd that you don't see the WMI classes in the namespace but SCCM is working correctly. Did you use the same account when installing SCCM? This is an x86 machine right? (so no x64 redirection or other issues).

This is an x86 machine and I am using the same Domain Admin account for everything. I am setting up the separate lab machine today and will let you know what I find.