MTNMN51

I think that you need to use the GUEST local account to accomplish this. You will probably need to enable it first.

Hello RET, When you say that you are using a special RIS driver, are you referring to Broadcom's monolithic driver? I had problems in the past with the II's and these links were helpful. To download the driver: http://www.broadcom.com/support/ethernet_nic/netxtremeii.php These links also have information about the NetXtreme II's: http://readlist.com/lists/mail.activedir.o...ir/2/10279.html http://www.911cd.net/forums//lofiversion/i...php?t18963.html http://www.911cd.net/forums//index.php?sho...mp;#entry130306 https://www-304.ibm.com/jct01004c/systems/s...randind=5000020 Hope this helps.

I'm not sure if it works for WinPE 2.0, but I use the HP SmartStart Scripting Toolkit Win32 Edition driver update utility to keep my WinPe 2005 image up to date with the latest drivers. The version that I have has all the drivers from PSP 7.70, so is very current. The nice thing is that once you run the utility to update your WinPE image, you're covered for all the HP hardware. I hope that helps.

I believe that model has the Broadcom NetXtreme II card and that you probably need to use the monolithic drivers provided by Broadcom. http://www.broadcom.com/support/ethernet_nic/netxtremeii.php http://www.broadcom.com/docs/driver_downlo...eadme-2.6.2.txt I haven't played with WinPE 2.0 yet, so don't know whether is supports the "virtual bus device" architecture. But I suspect it doesn't. If it doesn't, then I believe these drivers should work for you.

Thanks! I assume that you mean that the BIOS clock was actually changes after exiting WinPE. Unfortunately, ADS 1.1 is very specific in its requirement for WinPE 2005. However, when I get a chance, I'll attempt to create a WinPE 2.0 repository. The documentation for ADS was written prior to the release of WinPE 2.0, so it is entirely possible that it will work. Again, thanks for your help!

Thanks for your response! But, I need a solution that actually resets the BIOS clock so that after exiting the WinPE and rebooting into the ADS Deployment Agent, the time is already set. If I could find a way to synchronize the time as the ADS Deployment Agent loads, that would work as well. The DA uses Kerberos, so it fails if the time is not close to that of the ADS server. I tried setting an NTP server in my DHCP settings, but it appears that the DA doesn't pick that up when it loads.

As a matter of fact, I did RTFM. ;-D I read the HP Toolkit Users Guide as well as doing numerous searches. However, there is no utility that I could find that allows setting the BIOS time from WinPE. I find it odd that I can change the BIOS time from DOS or any version of Windows using the "net time" command, but it is disabled in WinPE. I really need to be able to synchronize my BIOS time from a Windows PE session, so hopefully someone knows a way to do it natively, or knows of a utility that can do it. After doing some additional searches, I just found this post on TechNet: Matt Davis -- MSFT (Moderator): Q: WinPe Changes: Thank you very much. And what are the limitations? Is it true that for example the net time command like net time /set does not work anymore because of the new limits? Net time works fine in older versions of winpe and fails in pe2005 A: Yes, net time will not work in WinPE 2005. This actually should not have worked previously. It is a limitation of WinPE that was supposed to be in-place in the past. I sure hope there is a hack that will help me get around this limitation. By disabling this ability, M$ just created another hurdle, rather than making life easier.

Can anyone help me? I just recently started using Windows PE 2005 in order to automate hardware configuration on the front end of our ADS deployment process. We previously used DOS boot floppies to set the time, configure the RAID settings, and to set the boot order. However, HP has stopped support for the DOS utilities in the Smartstart Scripting Toolkit. So, I am trying to replace the functionality that we had with the DOS utilities with the utilities that HP provides for use with WinPE. Setting the time is critical before booting the ADS Deployment Agent. It uses Kerberos authentication, so the image will never deploy if the time is not close to that of the ADS controller. My problem is that when I set the time in WinPE using net time \\servername /set /y it correctly sets the time within the WinPE session. However, when I reboot, I can see that the clock has not been reset. I don't understand why it would be different under WinPE. Does anyone know how to reset the system clock permanently from WinPE? Thanks in advance for any help that you can provide.

Can anyone help me? I just recently started using Windows PE 2005 in order to automate hardware configuration on the front end of our ADS deployment process. We previously used DOS boot floppies to set the time, configure the RAID settings, and to set the boot order. However, HP has stopped support for the DOS utilities in the Smartstart Scripting Toolkit. So, I am trying to replace the functionality that we had with the DOS utilities with the utilities that HP provides for use with WinPE. Setting the time is critical before booting the ADS Deployment Agent. It uses Kerberos authentication, so the image will never deploy if the time is not close to that of the ADS controller. My problem is that when I set the time in WinPE using net time \\servername /set /y it correctly sets the time within the WinPE session. However, when I reboot, I can see that the clock has not been reset. I don't understand why it would be different under WinPE. Does anyone know how to reset the system clock permanently from WinPE? Thanks in advance for any help that you can provide.