Jump to content

Zaker

Member
  • Posts

    77
  • Joined

  • Last visited

  • Donations

    $0.00 

About Zaker

Zaker's Achievements

0

Reputation

  1. Can someone please advise me how to set my PE v1.2 boot disk to attach to the network at 100FD. No changes have been made to this section of PE and I believe the CD boots at AUTO/AUTO. Thanks in advance.
  2. Each Exchange server is part of a 2 node cluster, but if we need to rebuild a server in a cluster, instead of building it from scratch, I want to have a hot-standby, rename it, pass it over to the Exchange team to save time. That link you sent doesnt really solve the issue of IIS reflecting the new server name after renaming the server. CHEERS!
  3. Greetings. We use an unattended build for our Exchange servers. We only install the base OS and a few utils, then the Exchange team installs Exchange. One of the components we install during the build is IIS. The issue, we would like to have a hot standby server sitting there ready to replace a failed Exchange server, rename the hot standby, and pass the server over to the Exchange team. IIS is one component that does not handle the rename very well. IIS holds onto the old server name and server is no good to Exchange team. Is there a util or way to properly rename the server so that IIS uses the new name? Thanks in advance.
  4. I found out more info... Rebuilding the server is an option now as well if thats the best route. The 2 existing drives are 74GB 10K RPM, RAID1 The 4 new drives are 74GB 15K RPM If I create another array and extended partition (D drive), would you think the new drives can run at 15K RPM? If it helps, its an IBM x3850.
  5. Thanks to both the people who replied...much appreciated. You brought up some great points that I will use to shoot down their request. I will be either creating a D drive for them, or rebuilding the affected servers. Cheers!
  6. Greetings. Windows Server 2003 Enterprise x86 w/SP2 Currently built using 2 x 73GB drives RAID1. Customer wants to add 4 73GB drives and expand C drive to fill entire space. Can diskpart do this? Any advise greatly appreciated. Thanks.
  7. I will put something together, but to be honest, the help file for PE you get after installing BDD2007 is really accurate. I created very basic scripts to execute each command. To add drivers you just isue peimg /inf= and add in whatever you need. Too easy after following the doc. If you have any specific questions in the meantime fire away...
  8. kool, any idea what driver? The server has a Broadcom and an Intel, but I am guessing its not these.
  9. I have my customized PE2.0 boot cd. On a server, I have VMWARE 1.0.2 Server installed. I create a new VM, it boots to my PE2.0 CD no problem, but does not get network support. I have fussed with all network settings in VMWARE, but I can't get my PE2.0 CD to boot and have network access. Is this a PE issue where I need to install a driver for VMWARE onto my CD? Or a VMWARE issue not supporting PE2.0. Any solutions or suggestions would be greatly appreciated. FYI, if I can boot to my PE CD, map to share on network, I will load my custom 2003 build into a VM session. CHEERS!
  10. I search my mounted image of PE2.0 x86 for b57* and found this result. Nothing like what you posted. b57nd60x.sys.mui netb57vx.inf_f53680c1\b57nd60x.sys x86_netb57vx.inf.resources_31bf3856ad364e35_6.0.6000.16386_en-us_ea863d28228619ac\b57nd60x.sys.mui Thanks for your help Jazkal.
  11. Mounted CD, did a search on b57*, found a lot of files and folder related to the b57nd60x driver and associated files. I renamed ALL of them with a .bak extension. PEIMG /INF=b57win32.inf c:\winpe_x86\mount\windows No problems there. I booted to CD and it failed to load any driver for the Broadcom. Ran regedit, searched for Broadcom, found nothing. Jazkal, I appreciate your inout, but unless I renamed more than I should have, it didnt work. I feel like I am so close, but not close enough. Need to have this working yesterday of course...
  12. DEVCON rocks, I love it and will be messing with it tons. BUT it also sidetracked me huge... Pleading here... I used peing /inf and it ADDS the driver to the PE image, but still uses the driver it always had, the driver that does not work well with the Broadcom card. I want to REPLACE the driver totally on the PE image so it uses the one I provide. Maybe I can mount the image and delete the driver that comes with the PE image ? Then run peimg /inf ? Any idea how I can try this to test other drivers?
  13. I added the b57win32 drivers to my winpe_x86 source via PEIMG /INF= I booted to the cd, opened regedit and searched for Broadcom. It only lists the b57nd60x drivers. No mention about the ones I baked in. You thought it would overwrite what was in the base image, I dont see that it did. How can I tell exactly which driver winpe is using, and can I change that on the fly. Using DRVLOAD or something? I am running out of options.
  14. ok...so after many frustrating attempts at getting this Broadcom card to go at full speed. I tried drvload all morning and that didnt make a difference. I will create a new bootcd trying different version of Broadcom drivers. There has to be something in that driver that is wacked though as I verified that it is on the network at 100FD..but the copy of the OS takes 4 hours. Thanks again...
  15. Thanks for your reply Mats. Found out more...had the switch port set to Auto/Auto to match what I think PE2.0 was set to. PE booted and got online at 100MB FD, so its not network speed. I switched the network cable from the onboard Broadcom card, to the Intel Pro card, and BOOM, speed was awesome again. i forgot to mention that there is a dual port Broadcom, and a dual port Intel Pro card in each server. We only use 1 port to build each server for other reasons. So the Intel card worked great, its the Broadcom performance that sucks. How do I ensure that PE uses a different driver for the Broadcom card. I issued DRVLOAD <path to x64 driver> , and the driver loaded without issues. But I do not think it switched over to this driver, just loaded it. Can i replace the driver that PE uses and use the x64 version. It is PE2.0 x86, but it loaded the x64 driver, and that driver worked great with my PE2.0 x64. I hope this is not too confusing....any ideas? Thanks.


×
×
  • Create New...