gbako

Thanks for help guys. I found the issue was you needed more packages installed than just wmi and scripting. I ended up also install the following packages: XML MDAC HTA So I basically installed 5 packages into PE (I used PE 2.1) I doubt all 3 of these were needed, but with them installed wmic works correctly! I'm too lazy to go back right now and figure out which of these 3 packages is actually needed, but I will eventually. But for now, if you install the following 5 packages total under PE2, then wmic.exe will finally work correctly: wmi scripting XML MDAC HTA

The error I get in PE2 (Vista SP1's PE) is: ERROR: Code = 0x80040154 Description = Class not registered Facility = Interface If I use WinPE3 (Win7's PE), the error I get is: ERROR: Description = Invalid class string Thats it. On both,the command I type in at the X:\ prompt is: wmic csproduct I use several other commands via wmic, but they all provide the exact error. Nwo on both PE2 and PE3 I installed the WMI package, so the problem isn't that WMIC is missing. I found an article on technet where people had the same problem with PE3 (Win7's PE), and one person's solution was to take the entire C:\Windows\System32\wbem folder from Windows 7 and copy it into PE3's X:\Windows\System32\Wbem (in other words, overwriting the files in PE with the ones from Win7). I did this trick, and did nothing at all. I don't know what else to do. It's a bit frustrating, as I'm not sure why this is ending up to be such a big deal to install! Thanks for any help guys! George

Thanks, but I've already written several DOS batch files that rely wmic.exe, so I would like to stick with wmic.exe

How does one (successfully) install WMIC into WinPE? I have tried to install wmic into both PE20 (Vista's PE) and PE30 (Win7's PE) with no success. On both versions I found instructions on how to install the WMI package, and on both versions I was successful with this, but even after doing so, wmic does not work. I get error messages when using the app instead of the output I need. I found an article on Technet where somebody has the same problem, and somebody replied a trick to fixing this (for WinPE3) was to copy the entire "c:\windows\system32\wbem" into your PE install, thus overwriting all the files that were in PE. Problem with idea, is that it does not fix anything. If anybody has any ideas, I would greatly appreciate it. It does not matter if there is a solution for WinPE2 or WinPE3, either one is fine with me. What I need WMIC.exe to work for is I need a WinPE CD to boot, and use wmic.exe to determine the type of hardware the system is running on, and then have a script make decisions based on the hardware you just booted on. This seems so simple, but without wmic.exe working, I'm stuck! Thanks guys for any help you might be able to provide. The article for installing a package into PE2 is here: http://technet.microsoft.com/en-us/library/cc709665%28WS.10%29.aspx The article for installing a package into PE3 is here: http://technet.microsoft.com/en-us/library/dd799312%28WS.10%29.aspx Problem is neither one of these articles was helpful, because while they do easily walk you thru the process of installing a package into PE2 or PE3, neither one explains why after you are done, wmic still does not properly work (even though the package install 100% successfully on both versions of PE) George

At my company, the way we prep new user's computers, is we have a sysprepped ghost image of a Windows XP setup that I've created. The process for this is simple. I setup a WinXP install the way we need it, I clone customized Admin profile to the default user. Once all this is done, I simply run sysprep on the machine, and then I created a ghost image. Now all the techs have to do is clone this image onto any of the compatible hardware we have and boot the system. As per the sysprep.inf file, it the machine gets added to our domain, it prompts for a computer name, and then auto logs in, and runs our batch which does a few more tasks. Lastly, the user can log in, with the profile already customized, and they are ready to go. Simply enough. I would like to be able to roll out Windows 7 the same way. Where I can create a master image, and I can sysprep, ghost and then have all of the techs clone that ghost image onto the machines they need prep for a user. How the heck do I do that? All of the information I've found so far just wants to talk about ImageX, and WIM files, and how great WAIK is, and so forth. I understand these tools are valuable, and some/all of them I might have to use, but isn't there a way to do this the way I used to with WinXP and Ghost? I do not need to be able to push out images via the network, I am not interested in Microsoft's deployment tools, I just want to have a ghost image that can be access on a network (or even burned to DVD, etc...) Where any tech can boot a WinPE disk, run ghost, and clone the image onto a computer. Can this still be done? I understand I need a unattend.xml file which replaces the old sysprep.inf file. Everything I found says to use Microsoft SIM to create unattend.xml files. Problem is, that program wants to open a WIM file to create one. Well, since I would prefer to use Ghost, not ImageX to clone the master image, I don't have a WIM file. I can of course create one if needed, I am hoping to avoid having to use ImageX. And help would be greatly appreciated. George