Stratuscaster

Member
  • Content count

    31
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Stratuscaster

  1. In our environment, localboot is done by not hitting F12 to PXEBOOT - so there was no need. That, and we boot to PXELINUX first - that provides a localboot option.
  2. The working BOOTMGR I have is version 6.0.6000.16386. The non-working BOOTMGR is version 6.0.6001.18000. The solution was found in this thread: http://www.msfn.org/board/index.php?showtopic=114711&hl=
  3. Problem solved. The BOOTMGR.EXE in the latest WAIK is the culprit. Using the BOOTMGR.EXE from a previous WAIK displays the menu items correctly.
  4. When I do this, every menu item that shows in the Windows Boot Manager is named "Ramdisk options". Thoughts? Problem solved. Found in another thread here - the BOOTMGR.EXE from the latest WAIK is the culprit. Using the BOOTMGR.EXE from the older WAIK displays the menu items correctly. The working BOOTMGR I have is version 6.0.6000.16386. The non-working BOOTMGR is version 6.0.6001.18000.
  5. Thank the Lord I found this thread - was beating my head against the wall trying to figure out this issue. The working BOOTMGR I have is version 6.0.6000.16386. The non-working BOOTMGR is version 6.0.6001.18000.
  6. When I do this, every menu item that shows in the Windows Boot Manager is named "Ramdisk options". Thoughts?
  7. Has anyone gone any further with this? I'm experiencing the same issue - every menu entry in the Windows Boot Manager that is created in the BCD reads "Ramdisk options" - using the "BCDedit /store *path*\TFTPRoot\Boot\BCD /set {guid} description "WinPe1"" command changes nothing. The enum shows this description has been changed for the GUID entry, but that description never shows. The booting of the different WIMs works fine - but a user doesn't know what WIM he is selecting since each name is the same. Using EasyBCD or VistaBootPro doesn't seem to offer a way to change it either - it's not a matter of "not knowing the syntax."
  8. In our shop, we've modified the script to run a CMD file that includes the specific switch for that image, rather then reference the image itself. Yes, it's an extra step to create that CMD for each image, but we require that degree of control.
  9. I have in my HTA app that launches Ghost a button that does this: wpeutil reboot
  10. Did you add anything to the COMMENT field in the PROPERTIES of the shortcut that you created?
  11. Thanks for the reply - we've got it up and running.
  12. I have a need to change the CD-ROM letter to accommodate an image we are deploying that uses letters C, D, and E. We also have network shares to pull images from, and those are assigned J, K, L, and M. There are 3 other shares for tools and log reports - I, T, and W. So I need something to relocate the CD-ROM drive on a system (and there could be 2 of them) - to other drive letters. I tried your setup and while it ran, it couldn't determine any CD-ROM drive letter. Then I tried WreX's setup, but was unsure where and how exactly the pieces would be executed.
  13. Wondering just how I'd call this or where to implement it - that "echo list volume" has to run under DISKPART, doesn't it?
  14. How does one know what letter(s) the CD (and other) drives were assigned? I have to accomodate not only multiple HDD partitions on a system, but multiple network shares, too.
  15. You can create a VBS script launched from your startnet.bat to read the IP address (among other things) and store it into a variable. We use a sysinfo.cmd file to launch the sysinfo.vbs file, which in turn grabs the info and pipes it to a setenv.cmd file and runs it - both files are in x:\windows\system32. You can use an IF statement in your startnet.cmd to compare that IP variable and act accordingly (launch a file, run a script, map a drive, etc.) REM *** sysinfo.cmd *** cscript.exe //nologo x:\windows\system32\sysinfo.vbs >x:\windows\system32\setenv.cmd x:\windows\system32\setenv.cmd REM *** sysinfo.vbs *** dim count,t,ipchar,ip,lab,cnt REM *** Get IP Address and Filter Link local IPv6 *** On Error Resume Next Set objWMIService = GetObject("winmgmts:\\" & "." & "\root\CIMV2") Set colItems = objWMIService.ExecQuery("SELECT * FROM Win32_NetworkAdapterConfiguration", "WQL", &h10 + &h20) For Each objItem In colItems strIPAddress = Join(objItem.IPAddress, ",") Next count=1 do while(ipchar<>",") ipchar=mid(strIPAddress,count,1) count=count+1 if ipchar<>"," then ip=ip & ipchar Loop WScript.Echo "SET IP=" & ip REM *** Determine which lab menu to load *** REM *** LAB1 = 10.10.16.x - 10.10.31.x LAB2 = 10.10.32.x - 10.10.47.x count=1 cnt=0 ipchar="" lab="" do while(ipchar<>",") ipchar=mid(strIPAddress,count,1) if ipchar="." then cnt=cnt+1 count=count+1 if cnt=2 and ipchar<>"." then lab=lab & ipchar loop if lab<32 then Wscript.Echo "SET LAB=" & "LAB1" else WScript.Echo "SET LAB=" & "LAB2" REM *** code placed in startnet.cmd *** set LAB=UNKNOWN call x:\windows\system32\sysinfo.cmd GOTO %LAB% :LAB1 REM *** launch the HTA and pass the IP variable to be displayed on screen *** mshta.exe "i:\wizards\lab1.hta" "%IP%" goto END :LAB2 REM *** launch the HTA and pass the IP variable to be displayed on screen *** mshta.exe "i:\wizards\lab2.hta" "%IP%" goto END :UNKNOWN x:\Programs\nu2menu\nu2menu.exe :END We just completed a setup that does this very thing. If the third octet of the IP is <32, it launches the hta for one lab, and if it's >=32, it launches the hta for another lab. If it's neither, or an error occurs, a 'default' nu2menu is loaded. Our setup is fairly deep and uses PXE rather than off the CD, but the basic steps should still apply. Hope this helps.