sGorges

I found the solution to this myself incase anyone else is interested. I added the "Networking-MPSSVC-Svc_neutral" component to the specialize pass of my answer file and set all of the "???_EnableFirewall" settings to "False" and the $admin share(s) are now available.

I have been trying to enable the $admin share (\\computername\C$) and have not found any information on how to enbale file/print sharing in the unattended answer file. Has anyone been able to find this or get the $admin shares to work? Also if anyone knows how to enable remote registry I am attempting to get that to work as well. Thanks in advance!

Is there someone else with WinPE 3.0 boot media that can boot it up and check their registry (HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\ACPI_HAL\0000) and see if they have anything other than "acpiapic" in the "HardwareID" value? If so I would really like to see your PE build script. Any help is greatly appreciated!

That is pretty much the same code I use and what I am attempting to do, but with my WinPE 3.0 boot media it always returns "acpiapic". If I open regedit and browse to that key and the value is "acpiapic" so my script/code is working correctly but WinPE is not detecting it correctly.

I am having an issue detecting the ACPI HAL using WinPE 3.0. In the old (xp) version I was able to detect the machine HAL by looking at the following Registry key (HKEY_LOCAL_MACHINE\System\CurrentControlSet\Enum\Root\ACPI_HAL\0000) and then reading the "HardwareID" value. On a multiprocessor machine using old PE boot media this would read as "acpiapic_mp" but with my new WinPE 3 boot media this value is "acpiapic" which is a uniprocessor. Can anyone else confirm this or am I missing something from my PE build? I might add that I have quite a bit of experience with the old PE build process but I am still new to the new PE 3.0 way of doing things. Thanks in advance!!