Navigation

    • Register
    • Login
    • Search
    • Recent
    • Popular
    1. Home
    2. sesam
    3. Topics
    S
    • Profile
    • Following 0
    • Followers 0
    • Topics 11
    • Posts 43
    • Best 0
    • Groups 0

    Topics created by sesam

    • S

      Different hardware = Multiple image clients with multiple images
      Support • • sesam

      2
      0
      Votes
      2
      Posts
      392
      Views

      T

      @sesam
      You may have to create A new image, but this doesn't need to be a norm going forwards.

      If you create a Universal Image then you can start collecting driver packages and use that one image for every machine using that OS version/edition (windows 10 pro, windows 10 home, windows 11 pro, etc), at least for Windows.

      to summarize the video:

      Make a VM in Hyper-V (I can't speak to other hypervisors)

      Install the OS on it, using the latest installation media (w10-22h2, w11-23h2)

      Do all the updates
      3.1 do some shinanigans
      3.2 probably you should install TOEC

      Sysprep & generalize it

      Take the image

      Deploy the image to one machine of a given model

      Install all the drivers for it

      Collect the drivers using

      powershell> Export-WindowsDriver -online -destination <URI>

      Put the drivers in a zip file and upload them via the Theopenem web interface as a Filecopy Module configured to unzip and install them as drivers

      On the image, clone the default profile, name it appropriately, and configure it to use that file copy

      Now when you deploy this profile to machines you have a driver package set up for, they can all use the same base image. I have skimmed over a lot of details, the video tutorial linked at the top covers them. There are a lot of caveats like you may need an answer file, and the image will not retain preconfigured network profiles.

      TOEC seems great, my usecase is really annoying so it creates a lot of problems that I don't have time to solve right now, and TOEC is not strictly required for this workflow.

      Next Tuesday is Update Tuesday so either doing this now is a little extra work you don't have time for, or a great test run, because next week you'll be able to re-update that VM (remember to checkpoint before you sysprep) and update the image for every model in one go.

    • S

      PXE-E11: ARP timeout
      Support • • sesam

      5
      0
      Votes
      5
      Posts
      727
      Views

      S

      @sesam ....ok - anyway...it suddenly works ;)!

    • S

      v1.3.2 Install ERROR
      Support • • sesam

      2
      0
      Votes
      2
      Posts
      358
      Views

      T

      Working fine for me, perhaps your download is corrupt.

    • S

      Deploy Image ERROR
      Support • • sesam

      38
      0
      Votes
      38
      Posts
      5079
      Views

      T

      It looks like the multiple efi loaders still isn't quite resolved. I'll look at this again.

    • S

      Imagedownload: An Error has occured
      Support • • sesam

      1
      0
      Votes
      1
      Posts
      232
      Views

      No one has replied

    • S

      Image-Download: Incorrect Login
      Support • • sesam

      6
      0
      Votes
      6
      Posts
      369
      Views

      S

      @theopenem_admin OK - it was a Qwertz and Qwerty bug! Thx

    • S

      Client-Imageupload-Error
      Support • • sesam

      9
      0
      Votes
      9
      Posts
      698
      Views

      T

      Just run that command before you sysprep and you'll be fine.

    • S

      Image preparation
      Support • • sesam

      3
      0
      Votes
      3
      Posts
      468
      Views

      S

      @theopenem_admin OMG: Typo! Sorry and THX!

    • S

      No USB-Boot for Imageupload
      Support • • sesam

      5
      0
      Votes
      5
      Posts
      497
      Views

      S

      Thanks for the quick support! Will be tested as soon as possible!

    • S

      Clientboot.iso Error
      Support • • sesam

      3
      0
      Votes
      3
      Posts
      434
      Views

      S

      Thanks for the tip. I am currently in the test phase of Theopenem and have already set up the server again. Will work through the complete basic installation again in the next.

    • S

      Com-Server not found
      Support • • sesam

      3
      0
      Votes
      3
      Posts
      350
      Views

      S

      ...omg. Just checked again: I had a typo in the Toec.API web.config. Works now. Thank you very much!

      greetings