Jump to content
MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. ×

IcemanND

Patron
  • Content Count

    3,252
  • Joined

  • Last visited

  • Donations

    $0.00 

Posts posted by IcemanND

  1. Well went looking and WiMTweak seems to have vanished.  I found other ways to get done what I needed.

    Job changed drastically form when I joined 14 some odd years ago to now.  Had to find ways to do it all without enterprise management tools.  Now everything I do is SCCM/AD/GPO managed. 

  2. USBView shows everything the same for both the 8 and 32 gb drive except size and serial number.

     

    They are both 300 mA devices, which should not be an issue I have a 64gb thumb drive the tools says uses 498 mA and that drive works without issue but is a different flavor of Kingston drive from the other two.

  3. 1. Not sure, not an easy thing to check when booted to WinPE, but I will check that tomorrow, in PE and installed OS.

    2. Both are partitioned using the same diskpart script:

    Sel disk 4

    clean

    create part pri

    sel part 1

    active

    format fs=ntfs quick

    assign

        then the WinPE files are copied over.

    3. No i have not I will attempt that in the morning also.

    4. Never reported by anyone with desktops.

    5. Yes, card reads have never been an issue.

    6. I can try that tomorrow.

     

    Thanks for the suggestions, this has been a fun one to track down.

  4. Ok, so I have a number of 32gb DataTraveler 100 G3 thumbdrives, they boot either WinPE 3 or 4, and using the HKEY_Local_MACHINE\SYSTEM\CurrentControlSet\Control\PEBootRamdiskSourceDrive" to find the assigned driver letter and change it to a fixed letter so we don't accidentally wipe the USB drive if the internal hard drive has no partitions.

     

    So on some laptop machines if the power adapter is plugged in the referenced registry value is not created, even if you use "WPEUTIL UpdateBootInfo" to force the creation of it. If the machine is running off of battery it seems to always work fine, issue comes when the machine has a dead battery and can not be run without the power adapter.

     

    Another interesting thing to note is that I have the same thumbdrive in an 8gb version and this issue does not happen with that drive.

     

    Anyone see this before or have any idea, I've beat my head against it for three days now with no luck.

  5. Did you add anything else to the Updates folder? Your answer file needs to be the first file listed alphabetically. Then all you need to do is run Setup.exe, no switch required. If you put the answer file elsewhere or it is not the first MSP file in the updates folder you need to use the adminfile switch.

  6. There is really no need to inject most drivers into the image. Only drivers you would really need to do this with are boot critical drivers, and I have yet to find any at least for the systems I support.

    I just copy the unpacked drivers into a sub-folder structure of c:\windows\inf then sysprep and capture.

    One caveat, this works best if you are not mixing chipsets, some Intel devices end up with the incorrect AMD driver if it happens to be available.

  7. True, autologon would be needed, he would need it for his initial thoughts also.

    Getting scripts to run as desired can be tricky when done as a service. The Scheduled task at startup is a nice idea though, depends upon what he needs to do and under what user context.

  8. Put the script in the registry run key, write a registry entry somewhere for your countdown. Delete the run key value after reaching zero.

    Or put it in the runonce or runonceex key and rewrite it to the runonce key after each run until the count is zero, again tracking via a registry value.

  9. It doesn't like the default unicode encoding of out-file. It also appears to have a problem with the file being "open" at the same time you are writing to it, though since the default startnet.cmd file only has the one wpeinit line it may not make a difference to you.

    Personally I would replace this:

    Get-Content $cmd | Where {$_ -ne "wpeinit"} | Out-File $cmd
    Write-Output "@echo off" >> $cmd
    Write-Output "echo Inititalizing WinPE ..." >> $cmd
    Write-Output "wpeinit" >> $cmd
    Write-Output "echo Initialized!" >> $cmd
    Write-Output "echo Connecting to Image Server ..." >> $cmd
    Write-Output "net use Z: `"\\SRHS-SUP-FS\Desktop Support\Images`"" >> $cmd
    Write-Output "echo Connected!" >> $cmd
    Write-Output "cd /d Z:\" >> $cmd
    Write-Output "echo Launching GUI Interface ..." >> $cmd
    Write-Output "index.hta" >> $cmd

    With something like this:

    $startnet = Get-Content $cmd | Where {$_ -ne "wpeinit"}
    $startnet += "@echo off"
    $startnet += "echo Inititalizing WinPE ..."
    $startnet += "wpeinit"
    $startnet += "echo Initialized!"
    $startnet += "echo Connecting to Image Server ..."
    $startnet += "net use Z: `"\\SRHS-SUP-FS\Desktop Support\Images`""
    $startnet += "echo Connected!"
    $startnet += "cd /d Z:\"
    $startnet += "echo Launching GUI Interface ..."
    $startnet += "index.hta"
    Out-File -filepath $cmd -InputObject $startnet -Encoding ASCII

×
×
  • Create New...