none
Trying to deploy Windows 10 in lab - Error 429 ActiveX component Can't create object RRS feed

  • Question

  • I am trying to incorporate Bitlocker during my Deployment. 

    This is what the CS.ini looks like:

    [Settings]
    Priority=Default
    Properties=Type,MyCustomProperty
    
    [Default]
    _SMSTSORGNAME=Corp - Build Lab
    UserDataLocation=NONE
    OSInstall=Y
    AdminPassword=P@ssw0rd
    TimeZoneName=W. Europe Standard Time
    
    WSUSServer=http://NLWUSSV02:8530
    SLSHARE=\\REMCORPMIG01\Logs$\%ComputerName%
    SLShareDynamicLogging=\\REMCORPMIG01\Logs$\%ComputerName%
    UDDIR=%ComputerName%
    
    ApplyGPOPack=NO
    
    TimeZoneName=W. Europe Standard Time
    
    JoinDomain=corp.Corpgroup.local
    DomainAdmin=JoinAccount
    DomainAdminDomain=corp.Corpgroup.local
    DomainAdminPassword=P@ssw0rd
    
    BDEInstall = TPM
    BDERecoveryKey = AD
    BDEInstallSuppress=NO
    BDEWaitForEncryption=FALSE
    BDERecoveryKey=AD
    
    
    SkipAdminPassword=YES
    SkipProductKey=YES
    SkipComputerName=YES
    SkipDomainMembership=YES
    SkipUserData=YES
    SkipLocaleSelection=YES
    SkipTaskSequence=NO
    SkipTimeZone=YES
    SkipApplications=YES
    
    SkipSummary=YES
    SkipRoles=YES


    The deployment start, the OS installs and after the first reboot the Task Sequence just stops, no error message.

    The logs show an error but i do not even get the usual HTA page at the end of a deployment with errors

    This is the last lines of the BDD.log

    Validating connection to \\REMCORPMIG01\MDTBuildLab$	LiteTouch	2/4/2016 4:57:12 PM	0 (0x0000)
    SMS Task Sequencer already found on C:\MININT\Tools\X64	LiteTouch	2/4/2016 4:57:12 PM	0 (0x0000)
    Mapping server share: \\REMCORPMIG01\MDTBuildLab$	LiteTouch	2/4/2016 4:57:12 PM	0 (0x0000)
    RUN: regsvr32.exe /s "C:\Users\ADMINI~1\AppData\Local\Temp\Tools\x64\Microsoft.BDD.Utility.dll"	LiteTouch	2/4/2016 4:57:13 PM	0 (0x0000)
    Found Existing UNC Path Y: = \\REMCORPMIG01\MDTBuildLab$	LiteTouch	2/4/2016 4:57:13 PM	0 (0x0000)
    DeployRoot = \\REMCORPMIG01\MDTBuildLab$	LiteTouch	2/4/2016 4:57:13 PM	0 (0x0000)
    FAILURE (Err): 429: CreateObject(Microsoft.BDD.Utility) - ActiveX component can't create object	LiteTouch	2/4/2016 4:57:13 PM	0 (0x0000)

    For the moment the TPM is not activated, it waits for State Restore in the Task Sequence, i have a Bitlocker group folder with Task sequence variable BDEInstallSuppress not equals YES

    In this folder i have a couple of applications using cctk version 3.0 that set a BIOS password, enable TPM and activate it.

    The OS drive was once encrypted so i have ran diskpart and used the clean command already

    Could that be an issue with UAC? 



    Thursday, February 4, 2016 4:23 PM

All replies

  • Why do you think the failure is because of BitLocker? The snippet of your bdd.log doesn't point to anything bitlocker related. If you're going to rely on cctk to set the password and enable tpm that's fine but be sure to disable the part in your task sequence where it tries to pre-provision bitlocker because that will throw an error, one you can ignore but still you'll get a "yellow" screen at the end.

    If the machine you're deploying to previously had bitlocker enabled, you need to first (since you're dealing with Dell) load the BIOS defaults so that it clears TPM and ownership information. You do not need to manually wipe the drive or decrypt it prior running MDT because it'll wipe the drive prior to applying the image.


    If this post is helpful please vote it as Helpful or click Mark for answer.

    Thursday, February 4, 2016 4:37 PM
  • I have loaded the defaults in the BIOS already.

    Maybe it is not Bitlocker related then, i just wanted to provide some info on what i am trying to do at the moment, i have deployed OSes before successfully in this Lab.


    Thursday, February 4, 2016 4:46 PM
  • I'd probably have to see the whole bdd.log to maybe get the context of the error, but some errors can be pretty generic and harder to track down using just the log. Do you have any tasks you've added to the task sequence that run a command line or custom script? It could be something you added.

    If this post is helpful please vote it as Helpful or click Mark for answer.

    Thursday, February 4, 2016 4:56 PM
  • Here is a link to the BDD.log

    https://onedrive.live.com/

    I have a custom script running taken from Johan Arwidmark's book so that should be bullet-proof (ZTICheckforTPM_v2.wsf)

    Thursday, February 4, 2016 5:04 PM
  • I'm still not sure what this is coming from

    FAILURE (Err): 429: CreateObject(Microsoft.BDD.Utility) - ActiveX component can't create object

    But the machine name you're using already exists in AD and thus the machine can't join the domain, so that's one error you're going to have. It's ending pretty abruptly so for any of the tasks you've added, try marking them with "Continue on error" in the options tab of that task. That way at least you can get a better picture of what fails and what works.

    I use conditions so that cctk won't try to run on models other than what are supported.

    On the enable TPM task I set: If none of the conditions are true - SELECT * FROM Win32_Tpm WHERE IsEnabled_InitialValue = True

    It's been working well for me.


    If this post is helpful please vote it as Helpful or click Mark for answer.

    Thursday, February 4, 2016 5:33 PM
  • Thanks Dan for the help.

    I deleted the computer account in AD and tried another deployment.

    This time i deleted my Task Sequence and recreated a new simple Client task.

    I have only added one folder in addition to the default steps, for Bitlocker and checked the Continue on error.

    I am testing the TS on an Optiplex 7010 which supports TPM activation with cctk

    I still get the same problem. BDD logs are available there: https://onedrive.live.com

    Error is: 

    FAILURE (Err):429: CreateObject(Microsoft.BDD.Utility) - ActiveX component can't create object

    Friday, February 5, 2016 9:38 AM
  • What are your IE security settings?

    Logs are very important. https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/ Mention any customizations you have made.

    Friday, February 5, 2016 11:06 AM
    Moderator
  • IE Protected Mode is enabled but cannot find from which policies it is coming from. Could that be the problem?
    Friday, February 5, 2016 12:26 PM
  • Better to tackle one issue at a time

    As for the Active X error, check to see if MDAC/ADO support is enabled in the Windows PE features in MDT. The other thing that can cause that error but shouldn't be the case for you is when you try to run litetouch using a non-Administrator account.

    It looks like the error is popping up when it tries to RUN: regsvr32.exe /s "C:\Users\ADMINI~1\AppData\Local\Temp\Tools\x64\Microsoft.BDD.Utility.dll"

    So may try replacing the file with a clean copy in case it's damaged. If you can get this problem fixed then we can move on to BitLocker. I have it all automated and working fine with Dell systems so I can help you get that working.


    If this post is helpful please vote it as Helpful or click Mark for answer.

    Friday, February 5, 2016 2:45 PM
  • I confirm MDAC/ADO support is enabled.

    LiteTouch is running from the local admin account

    Yes the error is caused by the DLL registration failing:

    RUN: regsvr32.exe /s "C:\Users\ADMINI~1\AppData\Local\Temp\Tools\x86\Microsoft.BDD.Utility.dll"	LiteTouch	2/5/2016 4:17:06 PM	0 (0x0000)
    FindFile(...\Microsoft.BDD.Utility.dll)  Result : 0	LiteTouch	2/5/2016 4:17:06 PM	0 (0x0000)
    Copy File: \\REMCORPMIG01\MDTBuildLab$\Tools\x64\Microsoft.BDD.Utility.dll to C:\Users\ADMINI~1\AppData\Local\Temp\Tools\x64\	LiteTouch	2/5/2016 4:17:06 PM	0 (0x0000)
    RUN: regsvr32.exe /s "C:\Users\ADMINI~1\AppData\Local\Temp\Tools\x64\Microsoft.BDD.Utility.dll"	LiteTouch	2/5/2016 4:17:07 PM	0 (0x0000)
    FAILURE (Err): 429: CreateObject(Microsoft.BDD.Utility) - ActiveX component can't create object	LiteTouch	2/5/2016 4:17:07 PM	0 (0x0000)
    I have copied the 
    Microsoft.BDD.Utility.dll
    Friday, February 5, 2016 3:35 PM
  • I'm not sure if any of this helps - https://msdn.microsoft.com/en-us/library/aa231060(v=vs.60).aspx

    Is this your first and only attempt to deploy Windows? Do you have any other working WIM files that you've been able to deploy? Is there anything different between this and a working task sequence?


    If this post is helpful please vote it as Helpful or click Mark for answer.

    Friday, February 5, 2016 4:10 PM
  • This is not my first attempt to deploy windows i have been using this MDT server for a couple of years, using the Lab to Build images.

    The problem started when i have added the Bitlocker options in my CS.ini which is why i thought it was Bitlocker related at first.

    All i can find online is the fact that this error will pop-up if you run the TS from a non administrator account. But the account logged is the local admin.

    Monday, February 8, 2016 10:07 AM
  • So i confirm the problem appears as soon as i add the Bitlocker parameters in my CS.ini

    BDEInstall = TPM

    BDERecoveryKey = AD

    As soon as i take this option out, the TS finishes

    I have opened a support case with Microsoft

    Tuesday, February 9, 2016 10:13 AM
  • Please be sure to post updates on the problem, it could be of benefit to someone else in the future.

    If this post is helpful please vote it as Helpful or click Mark for answer.

    Tuesday, February 9, 2016 2:07 PM
  • I think i found the issue, since we moved VLANs we had some rules in CS.ini that were checking the clients default gateway. 

    Adding the new gateway seems to fix the issue.

    Monday, February 15, 2016 3:14 PM
  • I think i found the issue, since we moved VLANs we had some rules in CS.ini that were checking the clients default gateway. 

    Adding the new gateway seems to fix the issue.

    Will you file this as a bug on connect? I suspect the MDT team would find it an interesting issue.

    Logs are very important. https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/ Mention any customizations you have made.

    Monday, February 15, 2016 9:35 PM
    Moderator
  • A couple of things:

    1. Verify that the file is not corrupt. Here is an example run from my local machine:

    PS C:\DeploymentShare> get-childitem microsoft.bdd.utility.dll -recurse | get-filehash
    
    Algorithm       Hash                                                                   Path
    ---------       ----                                                                   ----
    SHA256          6989A0FC456ACFF54B6D23FDC7A614167E6DCCB894E531FB243069D9C8DF6488       C:\DeploymentShare\Tools\x64\Microsoft.BDD.Utility.dll
    SHA256          C4ADF2947425BB4DC47F3844A85CB9C6C61E877FDE8B07D2E251B676B99D7199       C:\DeploymentShare\Tools\x86\Microsoft.BDD.Utility.dll
    
    

    2. This might be caused by some over-active Anti-Virus program blocking Microsoft.BDD.Utility.dll from loading. Try performing an install on a *CLEAN* image.

    -k


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    Tuesday, February 16, 2016 10:47 PM
    Moderator
  • I have no Antivirus on the client machine nor on the server.

    PS D:\MDTProduction> get-childitem microsoft.bdd.utility.dll -recurse | get-filehash
    
    Algorithm       Hash                                                                   Path
    ---------       ----                                                                   ----
    SHA256          60CA3D7BBD79C4D609817F6971EE5CBF86B44E4D692586B9B27A3A7C78BBEBB0       D:\MDTProduction\Backup\Tools...
    SHA256          2671C8D08377B6837653F5F2E3349DB1B23AE43091D2DA878410317F5EF32EAF       D:\MDTProduction\Backup\Tools...
    SHA256          6989A0FC456ACFF54B6D23FDC7A614167E6DCCB894E531FB243069D9C8DF6488       D:\MDTProduction\Tools\x64\Mi...
    SHA256          C4ADF2947425BB4DC47F3844A85CB9C6C61E877FDE8B07D2E251B676B99D7199       D:\MDTProduction\Tools\x86\Mi...

    My hash looks the same as yours


    Wednesday, February 17, 2016 11:09 AM