Jump to content

szwicker

Member
  • Posts

    35
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

About szwicker

szwicker's Achievements

0

Reputation

  1. Hi, I apologize in advance if this has already been addressed (probably has) but I couldn't find the proper verbiage to search for. Basically, I create the LAB deployment point (Distribution$) and then I generate the litetouch WIM and boot to it. Everything is cool. It is already pointing to "\\server\distribution$" etc and the user is ready to go. When I create any other deployment points such as NETWORK, etc, I don't get the same result. When I boot to the litetouch WIM, it forces the user to enter the deployment point and defaults to: "x:\boot" or something along those lines (I don't have the screen in front of me). My question: How/where can I configure that info so it's pre-populated with the proper target. Taking it a step further, can I also pre-answer some of the other questions further so the user won't have to decide between domain & workgroup, admin credentials, and possibly even pre-populating the OU. Thanks a million! - Seth
  2. I've used the BDD 2007 Workbench to create my Litetouch installer images, etc. Now I want to use that with a bootable USB drive. I've seen some writeups but they just advise how to create a generic bootable PE. I created the USB based deploypoint "c:\media$" and I've updated the files in there. How do I go from that to a functioning USB drive? Thanks in advance!
  3. I've been stopped early on. It keeps telling me that I need to enable asp.net web server extensions in IIS which I believe I've done...
  4. Thanks for the info. I wasn't sure how non-compatible hardware would react. Would it bomb or install but not behave any differently, etc. I
  5. I'm trying to get a greater idea of what processor would/should work with x64 in terms of hardware compatibility. I recently purchased a Dell 9100 dual core 2.8. I installed Windows 2003 x64 on it and (so far) it has worked like a charm. Is that a 64 bit compatible chip that's taking advantage of the new OS or is it just behaving in the same fashion as the standard 32 bit OS would and I'm seeing what I want to see, etc. Also, in my other workstation, I have a P4 Intel Extreme 3.2. Would this processor be a suitable candidate for x64? Any clarification is greatly appreciated. Thanks!
  6. I found them to be extremely convoluted but I'll give them a 2nd look.
  7. I know there are numerous posts around here explaining the steps to one part of the equation or another but they're all over the place, now and things have gotten convoluted, etc. So, I'm looking to boot to PXE, and have it use the new method of loadking the ISO image to RAM and running PE from there, etc. Can anyone help out by posting the steps? Thanks a million!
  8. I'm trying to create a new .adm file that will allow me to set the Windows XP search back to the Windows 2000 interface as well as hide that language bar that always pops up by default. There are a few others but these two will get me started on the path to learning the rest. I know that there are.reg hacks for them but I'd rather control it domainwide with an .adm file. Thanks in advance...
  9. You should be able to change your IP without a problem. The Server should be running DNS and looking to itself as a DNS server. If so, then you can make the IP change and then reboot. If need be, go into the DNS tool and make sure that the servername points to the new IP address. If it still has the old one, change it manually.
  10. I'm about to build a new system from the ground up to work with a Sony LCD HDTV. Can anyone recomend some good hardware, namely what capture and/or video card, etc? Motherboard, sound card, drives, etc? Thanks a million!
  11. Perhaps you would want separate HD's. One to hold the OS & programs w/ a separate one for your data with some sort of stripe set to also boost speed.
  12. Well, that conclusively settles it. Thanks for the swift responses, everyone.
  13. When we install XP, it copies a bunch of files to the C drive, reboots and starts the "dos part" of the installation from the C drive. When we're in PE, we use winnt32.exe with the /noreboot switch, can we manually (or scripted) run the next stage of the installation rather than reboot? Does my question make sense or do I come off like a babbling id***?
  14. I've been experimenting with attempting to boot WinPE from my USB flashdrive on a Dell Optiplex 280. The attempt always fails when it's done loading. I beleive this to be somewhat ofa driver issue. The strange part is that I can't seem to find the SATA drivers for the Optiplex 280. It's as if they've completely integrated it with the standard IDE plane. Any suggestions?
  15. I know that if you attempt to use Nuhi Winlite to modify the WinPE install files directly, it will tell you to take a hike...BUT what if we were to use Winlite to modify the XP files adding drivers etc. Then I could recompile WinPE using those updated XP files, etc. Worth an effort?
×
×
  • Create New...