Jump to content

szwicker

Member
  • Posts

    35
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by szwicker

  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?
  16. I'm trying to find ways to restrict certain users (local to the machine, not on a domain so no GP) to the point where all they can do is run certain applications I place on their desktop. Other than that, they can't evne go through the START MENU or run windows.exe. Any ideas: Tweaks, reg hacks, alternate shells, etc? Thanks in advance.
  17. Ok, at this point it looks like the installation part is working properly. However, I'm unable to get the TOOLS button to do anything. I click it and nothing happens. I hit ALT-TAB to search for a second windows but there's nothing to be found.
  18. That sounds like it should work. Mbouchard suggested I do this to help figure out what's causing the install progarm to loop like that. While the program is "paused", I can copy down the relevant files and post them to figure out what the issue is. So the exact command is: wscript.echo "...." Is that how I should type the line into my editor?
  19. Question: How would I add a "pause command" to the vb script?
  20. I'm new to VB scripting. What's the proper syntax?
  21. Update: I put the new .vbs file into place. The install appears to work properly at first. It appears to accept the information I typed in, formats the c: drive and then copies over the files and begins the installation. It goes through properly but at the end, it appears to "loop". It seems to reformat the drive and start copying the files to the c: drive all over again.
  22. More questions: First, here's where I'm at , currently: I've copied the folders & files into my winpe folder and created a new image with it, etc. At first, I was getting an error message where the system didn't know what to do with default.hta. I recalled that I hadn't run buildoptionalcomponents.vbs on it yet. I did so and copied in the files along with oc2.bat. The system would start and then reboot. I edited oc2.bat and removed "exit" at the end and tried again. That seemed to work as it brought up the Windows Server Setup screen. I attempt to start the install but one of two events occur: 1. The system reboots without attempting the installation (or so it would appear0. 2. I'd get a script error: c:\n\custom\instos1.vbs. THE SYSTEM CANNOT FIND THE FILE SPECIFIED. Any suggestions?
  23. This looks great! Thanks. Some questions after looking at it: 1. Should I copy the i386 folder from my various installation media into the win2k or winxp folder or should I go one step in and just copy all the files & subfolders from the i386 folder but not the folder itself into the ClientOS\wxp folder? 2. Is there a way for me to populate the CD key info into the field with each selection I make? 3. Would it be difficult to add other selectable options such as: install IIS, etc. 4. What about editing the graphic interfact layout? Would I want to use Frontpage for something like that? Thanks a million.
  24. Sounds great! Can I trouble you to be so generous as to post it?
  25. Hmm, no luck in finding those old posts so far. Just so I'm making myself clear: I don't want to kick off an automated installation. I can already do that well enough. I'm looking for the ability to enter in the machine name, company name, etc at the beginning of installation. I've seen some stuff that alludes to this but it's been poorly documented at best. Also, they are based on having the imaged on a network whereas I'm looking to create a purely self contained CD.
×
×
  • Create New...