Navigation

    • Register
    • Login
    • Search
    • Recent
    • Popular

    Image automatically

    Feature Requests / Feedback
    3
    19
    1340
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • J
      jithinpsk @theopenem_admin last edited by

      @theopenem_admin Apologies for not being clear. I wasn't aware of the feature where we can image without touching the computer. What is that option called?

      Because of the IT security restrictions we cannot enable PXE boot in our classrooms. Currently we boot these devices from USB and image them. It takes a lot of time and effort for this repetitive process.

      Thank you for looking into this.

      1 Reply Last reply Reply Quote 1
      • J
        jithinpsk last edited by jithinpsk

        If somebody is looking at a similar solution, you can use PowerShell to do this. This is not my script, but it works perfectly.

        <#
        
        .Synopsis
            This script will create a ramdisk containing the boot.wim which the computer will boot to on restart. This script will work only on Windows Imaging environment.
        
        .Prerequisites
            - From the Windows PE boot USB, copy boot.wim in the Sources folder to C:\Sources on the target
            - From the Windows PE boot USB, copy the Boot folder to C:\ on the target
        
        .Notes
            Because "bcdedit /bootsequence" is used, the computer should boot back into Windows when restarted if imaging is cancelled.
        
        #>
        
        # Checks that Disk 0 is the boot disk.
        $DISKZERO = Get-Disk 0
        If ($DISKZERO.IsBoot -ne $true) {
        Write-Host "Disk 0 is not the boot disk. Exiting..."
        Exit 999
        }
        else {
        Write-Host "Disk 0 is the boot disk. Proceeding..."
        }
        
        # Create {ramdiskoptions} and configure
        bcdedit -create "{ramdiskoptions}"
        bcdedit /set "{ramdiskoptions}" ramdisksdidevice partition=C:
        bcdedit /set "{ramdiskoptions}" ramdisksdipath \boot\boot.sdi
        
        # Add LiteTouch boot device to OSLOADER
        $Output = bcdedit -create /d "LiteTouch MDT" /application OSLOADER
        
        # Obtain LiteTouch boot device GUID
        $LTGUID = $Output | %{ $_.split(' ')[2] }
        
        # Configure LiteTouch to ramdisk boot
        bcdedit /set $LTGUID device "ramdisk=[C:]\sources\boot.wim,{ramdiskoptions}"
        bcdedit /set $LTGUID osdevice "ramdisk=[C:]\sources\boot.wim,{ramdiskoptions}"
        bcdedit /set $LTGUID systemroot \windows
        bcdedit /set $LTGUID detecthal yes
        bcdedit /set $LTGUID winpe yes
        
        # Adjust for UEFI vs Legacy BIOS types
        if ($env:firmware_type -eq 'UEFI'){
        Write-Host "UEFI boot confirmed."
        bcdedit /set $LTGUID path \windows\system32\boot\winload.efi
        }
        Else {
        Write-Host "Legacy boot confirmed."
        bcdedit /set $LTGUID path \windows\system32\boot\winload.exe
        }
        
        # Force LiteTouch ramdisk on next boot and restart
        bcdedit /bootsequence $LTGUID
        shutdown /r /f /t 0
        
        1 Reply Last reply Reply Quote 0
        • T
          theopenem_admin last edited by

          This is now available in 1.5.0.

          J 1 Reply Last reply Reply Quote 0
          • J
            jithinpsk @theopenem_admin last edited by

            @theopenem_admin how to use this feature? I tried to upload the PXE files and the upload fails.

            41ae2051-a449-49c2-a2a2-f6c6718adbd4-image.png

            1 Reply Last reply Reply Quote 0
            • T
              theopenem_admin last edited by

              To use the new feature you need to upload the boot.sdi and winpe10x64.wim files that were created from wie_build. Don't rename them. Are you able to upload files in other modules? to make sure this isn't an upload setting issue?

              J 1 Reply Last reply Reply Quote 0
              • J
                jithinpsk @theopenem_admin last edited by

                @theopenem_admin I am unable to upload files for any other modules. I checked logs and couldn't find any.

                1 Reply Last reply Reply Quote 0
                • T
                  theopenem_admin last edited by

                  Did you set the upload url in web.config when you installed?

                  J 1 Reply Last reply Reply Quote 0
                  • T
                    theopenem_admin last edited by

                    https://docs.theopenem.com/latest/#/installation/server-installation?id=update-theopenem-webconfig-files

                    1 Reply Last reply Reply Quote 0
                    • J
                      jithinpsk @theopenem_admin last edited by

                      @theopenem_admin my bad! I made a mistake in the IP. Modified it the correct ip now. Do I need to do anything on the server side for it to take effect?

                      1 Reply Last reply Reply Quote 0
                      • T
                        theopenem_admin last edited by

                        no, that's it.

                        J 1 Reply Last reply Reply Quote 0
                        • J
                          jithinpsk @theopenem_admin last edited by

                          @theopenem_admin Thank you.

                          1 Reply Last reply Reply Quote 0