UNSOLVED

kwacky1

updated

17 years ago

K

kwacky1

5 Posts

0

23497

August 13th, 2009 21:00

Problems installing DDP

Hi there,

I have succesfully installed DDP in our test enviroment, and now that it's time to install the DDP on our production SCCM server I'm getting the following error.

--- excerpt from Windows installer Log file ---
InstallShield 13:32:41: Invoking script function InstallSccmObjects
1: Value of '_ADMINUI_OEM_FOLDER_' = E:\SMS\AdminUI\XmlStorage\Extensions\bin\Deployment\Dell\PowerEdge\
1:
1:
1: ######################################################################
1:
1: Processing Configuration Manager objects.
1:
1: ======================================================================
1:
1: Support directory: E:\SMS\AdminUI\XmlStorage\Extensions\bin\Deployment\Dell\PowerEdge\setup
1: Found 16 XML file(s) to process.
1: Current directory: E:\SMS\AdminUI\XmlStorage\Extensions\bin\Deployment\Dell\PowerEdge\setup
1: Processing file (0 of 16)
1: Percent complete: 0
1: StatusText in XML: Installing custom classes into WMI
Action 13:32:41: InstallSccmComponents. Installing custom classes into WMI
1: Processing XML file: E:\SMS\AdminUI\XmlStorage\Extensions\bin\Deployment\Dell\PowerEdge\setup\Install_000_MOF.xml
1: Failure while processing SCCM objects. Return value = 1001
1: ======================================================
1: 14/08/2009 1:32:41 PM :: configFile parameter was: E:\SMS\AdminUI\XmlStorage\Extensions\bin\Deployment\Dell\PowerEdge\setup\Install_000_MOF.xml
1: ===[ RETURN CODE = 1001 ]===
-----

Any ideas?
  • kwacky1

    5 Posts

    526

    0

    Posted August 13th, 2009 22:00

    Ok, I found the DDP was looking for the MOF files in E:\SMS\XmlStorage... instead of E:\SMS\AdminUI\XmlStorage

    I manually copied the MOF's there and the install almost worked.
    I also had to manually create E:\SMS\XmlStorage\Other
  • kwacky1

    5 Posts

    526

    0

    Posted August 13th, 2009 22:00

    Post Install I also had to move the E:\SMS\XmlStorage\Extensions\Actions and E:\SMS\XmlStorage\Actions to E:\SMS\AdminUi....

    btw.. Yes HKLM\Software\Microsoft\SMS\Setup\UI Installation Directory is set to E:\SMS\AdminUI

    Here's what _Install.log has to say

    ---
    14/08/2009 2:04:56 PM :: GetSafeRegistryStringValue: Trying standard .NET call to registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Setup\UI Installation Directory
    14/08/2009 2:04:56 PM :: GetSafeRegistryStringValue: Value returned = 'E:\SMS'
    ---
  • DELL-Greg R

    118 Posts

    526

    0

    Posted August 14th, 2009 07:00

    so, you confirmed that U Installation directory is set to e:\sms\adminui . . . but the log says it queried the registry, and it regurned e:\sms ??

    I've installed this a few times, and have never had to move files around to get it working - so I'd like to understand the scenario to see if we can reproduce it.
  • kwacky1

    5 Posts

    526

    0

    Posted August 16th, 2009 15:00

    Well, take an SMS 2.0 installation, upgrade it to SMS 2003 and then add SCCM 2007.. I think the only sevrice pack we've skipped along the way was SMS 2003 SP3.

    But in actual fact, take a 64bit machine with a 64bit OS and forget to change UI Installation under HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\SMS\Setup