mrbeatnik

Would it be possible for you to modify the Winpeshl.ini in PE to: - Launch wpeinit.exe - Launch your GUI Using the INI file will avoid the startnet.cmd being processed, so should stop any command prompt window from appearing... From there I would just GUI entirely in Autoit

Hi again all... I know this may not be the exact forum for this... it's a WDS question. I'd appreciate if it could be moved to the correct forum if wrong. We used to use RIS. - When we PXE to RIS, we would get a screen to authenticate the user. - Depending on the user, different screens would appear (Maintenance & Troubleshooting etc). WDS seems to be very different in this respect. - The BOOT IMAGES have no authentication. We would like to PXE to WDS, and only show certain BOOT IMAGES depending on the user. We may have ~10 active boot images for development work, but only one production boot image that everyone else should use. Unfortunately everyone sees all boot images and may select the incorrect one. Does anyone know why the (inital) authentication was removed? I preferred the RIS method to authenticate first, and then have various choices. Any ideas? Thanks.

Added in all packages from WinPE_OCs dir. Here is an output of packages now in my wim: Deployment Image Servicing and Management tool Version: 6.1.7000.0 Image Version: 6.1.7000.0 Packages listing: Package Identity : Microsoft-Windows-WinPE-LanguagePack-Package~31bf3856ad364e35~x86~en-US~6.1.7000.0 State : Install Pending Release Type : Language Pack Install Time : Package Identity : Microsoft-Windows-WinPE-Package~31bf3856ad364e35~x86~~6.1.7000.0 State : Install Pending Release Type : Foundation Install Time : Package Identity : WinPE-HTA-Package~31bf3856ad364e35~x86~~6.1.7000.0 State : Install Pending Release Type : Feature Pack Install Time : Package Identity : WinPE-LegacySetup-Package~31bf3856ad364e35~x86~~6.1.7000.0 State : Install Pending Release Type : Feature Pack Install Time : Package Identity : WinPE-MDAC-Package~31bf3856ad364e35~x86~~6.1.7000.0 State : Install Pending Release Type : Feature Pack Install Time : Package Identity : WinPE-Scripting-Package~31bf3856ad364e35~x86~en-US~6.1.7000.0 State : Install Pending Release Type : Language Pack Install Time : Package Identity : WinPE-Scripting-Package~31bf3856ad364e35~x86~~6.1.7000.0 State : Install Pending Release Type : Feature Pack Install Time : Package Identity : WinPE-Setup-Client-Package~31bf3856ad364e35~x86~~6.1.7000.0 State : Install Pending Release Type : Feature Pack Install Time : Package Identity : WinPE-Setup-Package~31bf3856ad364e35~x86~~6.1.7000.0 State : Install Pending Release Type : Feature Pack Install Time : Package Identity : WinPE-Setup-Server-Package~31bf3856ad364e35~x86~~6.1.7000.0 State : Install Pending Release Type : Feature Pack Install Time : Package Identity : WinPE-SRT-Package~31bf3856ad364e35~x86~en-US~6.1.7000.0 State : Install Pending Release Type : Language Pack Install Time : Package Identity : WinPE-SRT-Package~31bf3856ad364e35~x86~~6.1.7000.0 State : Install Pending Release Type : Feature Pack Install Time : Package Identity : WinPE-WDS-Tools-Package~31bf3856ad364e35~x86~en-US~6.1.7000.0 State : Install Pending Release Type : Language Pack Install Time : Package Identity : WinPE-WDS-Tools-Package~31bf3856ad364e35~x86~~6.1.7000.0 State : Install Pending Release Type : Feature Pack Install Time : Package Identity : WinPE-WMI-Package~31bf3856ad364e35~x86~en-US~6.1.7000.0 State : Install Pending Release Type : Language Pack Install Time : Package Identity : WinPE-WMI-Package~31bf3856ad364e35~x86~~6.1.7000.0 State : Install Pending Release Type : Feature Pack Install Time : The operation completed successfully. Still cannot add in dhcpmon.dll through netsh.

None yet! I should really add them all in and work backwards perhaps. Just using the basic boot.wim that would initiate the multicast - just breaking out with shift-F10 and running netsh commands from prompt. Trying to add in helper dll from prompt. I have used a winpe.win from WAIK too which is pretty stripped of course. So I'll try adding all components in and see if that gets me anywhere. In the mean time any thoughts as to what components I should put in? Ideally I want to keep the wim as lean as possible to make a fast boot. Cheers!

Ok, So I can get my result (querying option 12) by running PSEXEC from PE and invoking the netsh dhcp server on another machine (in my test Server 2008 R2 with dhcpmon.dll)... however, PSEXEC is slow to create the service remotely, and I'm unsure what would happen if 10 machines attempt to run PSEXEC on one server before multicast begins... Would still prefer netsh running from Win PE correctly, so I know it's early days from my OP, but if anyone has any suggestions... Thanks.

7 Gb in 5 mins on a Gigabit network (presume 1Gb at server and client). Very nice. I have a XP image just over 5Gb (compressed size) with 1Gb at server, but 100Mb at Client - can take about 20 - 25 mins mcast. Windows 7 (2Gb image) deploys in about 12 mins. Shame we can't upgrade our entire network to 1Gb immediately! Thanks for the info.

Hi Tripredacus.... Just curious, what is your image size? That seems pretty quick! Cheers

Hi all. I'm having trouble querying DHCP server from Windows PE. Specifically I am trying to query the hostname we have stored in option 12 of the reservation in DHCP. I can query it on XP using netsh dhcp server if I copy the dhcpmon.dll file from Server 2003. I just add helper dhcpmon.dll and I can then run netsh dhcp server commands. I think it also works with Windows 7 / Vista if I use the Server 2008 dhcpmon.dll in the same way. I just can't get it to work from Windows PE. For some reason, I can't add the helper. I'm using both Win 7 and Server 2008 R2 boot.wim and the 2008 R2 dhcpmon.dll in my tests. I suspect some other components are missing to be able to add the helper - would anyone have an idea what they could be? Also I have tried using a script that uses dhcpsapi.dll to do the query. Again, this works fine on XP and Win 7 etc, but not on PE. It complains, first, of DSAUTH.dll not being present... I added this in but it couldn't initialise the dll. I couldn't regsvr32 it either. I feel there may be a common component missing for either solution to work. SO... Does anyone either have any ideas of how to resolve one of the above issues, or another way to query option 12 DHCP from PE? Again, using Server 2008 R2 and Windows 7 boot.wim, so that's likely to be PE 2.1/3.0, but I haven't checked the versions. Away from work right now, but if you need some more info will supply it as soon as. Thanks!