Twelfth times the charm. I got this working after stepping a way for a while and looking at it with fresh eyes. It still won't inject as a driver in SCCM, but dism can inject it ok and the ADSI stuff in my pre-execution hook is working again.
The solution is pretty embarrassing. The installation of windows 8.1 that I was using that thought was 64bit, wasn't 64bit. Sorry about that. On Jun 23, 2015, at 9:33 PM, Daniel Ratliff <[email protected]<mailto:[email protected]>> wrote: Any chance you can leverage Orchestrator? -----Original Message----- From: Miller, Todd [[email protected]<mailto:[email protected]>] Sent: Tuesday, June 23, 2015 08:09 PM Eastern Standard Time To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] WinPE 5.0 x64 ADSI Plugin? I have been not having any luck getting Johan’s ADSI plugin for WinPE 5.0 x64 to work. I have it working terrifically in Win PE 5.0 x86. The x64 plugin will import fine onto the SCCM Drivers, but there are errors when attempting to inject it into the boot wim. I AM able to inject it into the boot WIM using DISM, but when I do it that way, the ADSI “stuff” doesn’t work in my scripts. It acts like ADSI is not loaded. Is there something in WinPE 5.0 that makes it so that unsigned drivers don’t load, or is the idea just to get the six DLLs loaded into the right spot? I have verified that the six ADSI DLLs are available in x:\windows\system32 This simple line results in a syntax error – which to me says the DLLs aren’t loading or available or other problem? Set openDS = GetObject("LDAP:") (I need to use ADSI, I am aware of Webservices. There is a bug in the AD parts of Maik’s webservice that prevent me from using them in my environment, and that Webservice is so popular that no one else has released any) (Why not just use x86 then since that is working? I do mainly, but I have run into a problem where Dell T5810 simply will not boot into WinPE 5.0 x86 – it locks up hard – So I have to come up with something for that. I’d switch entirely to WinPE x64, but I can’t get ADSI to work. I am stumped.) ________________________________ Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, then delete it. Thank you. ________________________________ The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. ________________________________ Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, then delete it. Thank you. ________________________________
