Project announce: wimaging-ng; provision windows with foreman

Hello Foreman - users,

I recently forked Dmitry Kireev's wimaging[1] to a new project I call wimaging-ng[2].

Abstract:
wimaging-ng a set of scripts to prepare WIM images and templates for Foreman to provision Windows hosts.
Except for the boot process official Microsoft deployment tools are used; most notably dism.exe.
All relevant configuration files like unattend.xml are rendered by Foreman and downloaded at build time.

I have wimaging-ng currently in production deploying Windows 8.1/2012r2. I tested it with a variety of different
hardware at my disposal. The Config files I use for Windows8.1/WinPE are supplied.

Feel free to try it out!
Please open bugs and RFEs directly in GitHub[3].

Also, I am happy to assist; you can reach me on Gitter if you are near CEST or mail me directly (though I prefer to open
issues).

Features include:

  • Linux style installation using http:// or ftp:// installation media
  • No extra servers like WDS needed - all relevant settings can be configured in Foreman directly
  • Official Mircosoft utilities are used for all relevant setup stages making it easy to add (future) operating systems
  • Driver installation during build time
  • Support for localization settings (like time zone, locale, UI language)
  • Optional domain join including target OU
  • Optional local user creation
  • Support for Foreman's root password using Base64 encoding
  • Optional software installation and user tasks at the end of the build (like installing puppet ect)

For those of you who know wimaging, the main differences include the removal of SMB server, adding the rewriting the
Foreman templates (and adding them), support for root_pass, overall streamlining, revamp of the docs.

Ultimately, I think this will be merged back to wimaging again given Dmitry's and my time.

Caveats
Currently, I've not tested Windows 7; and most likely will never test 32bit arch. Later, Windows 10/2016 will be
integrated. Also, since we are dealing with propitiatory software, a lot of things like locating the correct drivers
need to be done manually. People familiar with WDS basically know this procedure.

[1] https://github.com/kireevco/wimaging
[2] https://github.com/helge000/wimaging-ng
[3] https://github.com/helge000/wimaging-ng/issues

··· -- Daniel Helgenberger m box bewegtbild GmbH

P: +49/30/2408781-22
F: +49/30/2408781-10

ACKERSTR. 19
D-10115 BERLIN

www.m-box.de www.monkeymen.tv

Geschäftsführer: Martin Retschitzegger / Michaela Göllner
Handeslregister: Amtsgericht Charlottenburg / HRB 112767

>
> Hello Foreman - users,
>
> I recently forked Dmitry Kireev's wimaging[1] to a new project I call
wimaging-ng[2].
>
> Abstract:
> wimaging-ng a set of scripts to prepare WIM images and templates for
Foreman to provision Windows hosts.
> Except for the boot process official Microsoft deployment tools are used;
most notably dism.exe.
> All relevant configuration files like unattend.xml are rendered by
Foreman and downloaded at build time.

That's great! If you like, you are very welcome to join one of our
community demo to the feature (5-10 minutes).

Thanks,
Ohad
>
> I have wimaging-ng currently in production deploying Windows 8.1/2012r2.
I tested it with a variety of different
> hardware at my disposal. The Config files I use for Windows8.1/WinPE are
supplied.
>
> Feel free to try it out!
> Please open bugs and RFEs directly in GitHub[3].
>
> Also, I am happy to assist; you can reach me on Gitter if you are near
CEST or mail me directly (though I prefer to open
> issues).
>
> Features include:
> - Linux style installation using http:// or ftp:// installation media
> - No extra servers like WDS needed - all relevant settings can be
configured in Foreman directly
> - Official Mircosoft utilities are used for all relevant setup stages
making it easy to add (future) operating systems
> - Driver installation during build time
> - Support for localization settings (like time zone, locale, UI language)
> - Optional domain join including target OU
> - Optional local user creation
> - Support for Foreman's root password using Base64 encoding
> - Optional software installation and user tasks at the end of the build
(like installing puppet ect)
>
> For those of you who know wimaging, the main differences include the
removal of SMB server, adding the rewriting the
> Foreman templates (and adding them), support for root_pass, overall
streamlining, revamp of the docs.
>
> Ultimately, I think this will be merged back to wimaging again given
Dmitry's and my time.
>
> Caveats
> Currently, I've not tested Windows 7; and most likely will never test
32bit arch. Later, Windows 10/2016 will be
> integrated. Also, since we are dealing with propitiatory software, a lot
of things like locating the correct drivers
> need to be done manually. People familiar with WDS basically know this
procedure.
>
>
> [1] https://github.com/kireevco/wimaging
> [2] https://github.com/helge000/wimaging-ng
> [3] https://github.com/helge000/wimaging-ng/issues
> –
> Daniel Helgenberger
> m box bewegtbild GmbH
>
> P: +49/30/2408781-22
> F: +49/30/2408781-10
>
> ACKERSTR. 19
> D-10115 BERLIN
>
>
> www.m-box.de www.monkeymen.tv
>
> Geschäftsführer: Martin Retschitzegger / Michaela Göllner
> Handeslregister: Amtsgericht Charlottenburg / HRB 112767
>
> –
> You received this message because you are subscribed to the Google Groups
"Foreman users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.

··· On Oct 5, 2015 13:42, "Daniel Helgenberger" wrote: > To post to this group, send email to foreman-users@googlegroups.com. > Visit this group at http://groups.google.com/group/foreman-users. > For more options, visit https://groups.google.com/d/optout.

Daniel, thanks for interest in my project. I appreciate your contribution!

We've merged changes back to wimaging, I hope we can cobine our forces and
build a nice opensource WDS alternative.

··· On Monday, October 5, 2015 at 1:42:13 PM UTC+3, Daniel Helgenberger wrote: > > Hello Foreman - users, > > I recently forked Dmitry Kireev's wimaging[1] to a new project I call > wimaging-ng[2]. > > Abstract: > wimaging-ng a set of scripts to prepare WIM images and templates for > Foreman to provision Windows hosts. > Except for the boot process official Microsoft deployment tools are used; > most notably `dism.exe`. > All relevant configuration files like `unattend.xml` are rendered by > Foreman and downloaded at build time. > > I have wimaging-ng currently in production deploying Windows 8.1/2012r2. I > tested it with a variety of different > hardware at my disposal. The Config files I use for Windows8.1/WinPE are > supplied. > > Feel free to try it out! > Please open bugs and RFEs directly in GitHub[3]. > > Also, I am happy to assist; you can reach me on Gitter if you are near > CEST or mail me directly (though I prefer to open > issues). > > Features include: > - Linux style installation using `http://` or `ftp://` installation media > - No extra servers like WDS needed - all relevant settings can be > configured in Foreman directly > - Official Mircosoft utilities are used for all relevant setup stages > making it easy to add (future) operating systems > - Driver installation during build time > - Support for localization settings (like time zone, locale, UI language) > - Optional domain join including target OU > - Optional local user creation > - Support for Foreman's root password using Base64 encoding > - Optional software installation and user tasks at the end of the build > (like installing puppet ect) > > For those of you who know wimaging, the main differences include the > removal of SMB server, adding the rewriting the > Foreman templates (and adding them), support for root_pass, overall > streamlining, revamp of the docs. > > Ultimately, I think this will be merged back to wimaging again given > Dmitry's and my time. > > Caveats > Currently, I've not tested Windows 7; and most likely will never test > 32bit arch. Later, Windows 10/2016 will be > integrated. Also, since we are dealing with propitiatory software, a lot > of things like locating the correct drivers > need to be done manually. People familiar with WDS basically know this > procedure. > > > [1] https://github.com/kireevco/wimaging > [2] https://github.com/helge000/wimaging-ng > [3] https://github.com/helge000/wimaging-ng/issues > -- > Daniel Helgenberger > m box bewegtbild GmbH > > P: +49/30/2408781-22 > F: +49/30/2408781-10 > > ACKERSTR. 19 > D-10115 BERLIN > > > www.m-box.de www.monkeymen.tv > > Geschäftsführer: Martin Retschitzegger / Michaela Göllner > Handeslregister: Amtsgericht Charlottenburg / HRB 112767 >

This is fantastic! I managed to kludge something together with Clonezilla,
but I've never been happy with it. I can't wait to give this a try.

I searched and can't find anywhere. How do you manage installation reboots
without pxe booting boot.wim every time due to host not built yet?

Thanks,

··· On Monday, October 5, 2015 at 6:42:13 AM UTC-4, Daniel Helgenberger wrote: > > Hello Foreman - users, > > I recently forked Dmitry Kireev's wimaging[1] to a new project I call > wimaging-ng[2]. > > Abstract: > wimaging-ng a set of scripts to prepare WIM images and templates for > Foreman to provision Windows hosts. > Except for the boot process official Microsoft deployment tools are used; > most notably `dism.exe`. > All relevant configuration files like `unattend.xml` are rendered by > Foreman and downloaded at build time. > > I have wimaging-ng currently in production deploying Windows 8.1/2012r2. I > tested it with a variety of different > hardware at my disposal. The Config files I use for Windows8.1/WinPE are > supplied. > > Feel free to try it out! > Please open bugs and RFEs directly in GitHub[3]. > > Also, I am happy to assist; you can reach me on Gitter if you are near > CEST or mail me directly (though I prefer to open > issues). > > Features include: > - Linux style installation using `http://` or `ftp://` installation media > - No extra servers like WDS needed - all relevant settings can be > configured in Foreman directly > - Official Mircosoft utilities are used for all relevant setup stages > making it easy to add (future) operating systems > - Driver installation during build time > - Support for localization settings (like time zone, locale, UI language) > - Optional domain join including target OU > - Optional local user creation > - Support for Foreman's root password using Base64 encoding > - Optional software installation and user tasks at the end of the build > (like installing puppet ect) > > For those of you who know wimaging, the main differences include the > removal of SMB server, adding the rewriting the > Foreman templates (and adding them), support for root_pass, overall > streamlining, revamp of the docs. > > Ultimately, I think this will be merged back to wimaging again given > Dmitry's and my time. > > Caveats > Currently, I've not tested Windows 7; and most likely will never test > 32bit arch. Later, Windows 10/2016 will be > integrated. Also, since we are dealing with propitiatory software, a lot > of things like locating the correct drivers > need to be done manually. People familiar with WDS basically know this > procedure. > > > [1] https://github.com/kireevco/wimaging > [2] https://github.com/helge000/wimaging-ng > [3] https://github.com/helge000/wimaging-ng/issues > -- > Daniel Helgenberger > m box bewegtbild GmbH > > P: +49/30/2408781-22 > F: +49/30/2408781-10 > > ACKERSTR. 19 > D-10115 BERLIN > > > www.m-box.de www.monkeymen.tv > > Geschäftsführer: Martin Retschitzegger / Michaela Göllner > Handeslregister: Amtsgericht Charlottenburg / HRB 112767 >

Hi Daniel,

I noticed in the config file that Server 2012 and Server 2012 R2 were
"TODO". Does this mean they do not yet work?

Best,
Ryan

··· On Monday, October 5, 2015 at 3:42:13 AM UTC-7, Daniel Helgenberger wrote: > > Hello Foreman - users, > > I recently forked Dmitry Kireev's wimaging[1] to a new project I call > wimaging-ng[2]. > > Abstract: > wimaging-ng a set of scripts to prepare WIM images and templates for > Foreman to provision Windows hosts. > Except for the boot process official Microsoft deployment tools are used; > most notably `dism.exe`. > All relevant configuration files like `unattend.xml` are rendered by > Foreman and downloaded at build time. > > I have wimaging-ng currently in production deploying Windows 8.1/2012r2. I > tested it with a variety of different > hardware at my disposal. The Config files I use for Windows8.1/WinPE are > supplied. > > Feel free to try it out! > Please open bugs and RFEs directly in GitHub[3]. > > Also, I am happy to assist; you can reach me on Gitter if you are near > CEST or mail me directly (though I prefer to open > issues). > > Features include: > - Linux style installation using `http://` or `ftp://` installation media > - No extra servers like WDS needed - all relevant settings can be > configured in Foreman directly > - Official Mircosoft utilities are used for all relevant setup stages > making it easy to add (future) operating systems > - Driver installation during build time > - Support for localization settings (like time zone, locale, UI language) > - Optional domain join including target OU > - Optional local user creation > - Support for Foreman's root password using Base64 encoding > - Optional software installation and user tasks at the end of the build > (like installing puppet ect) > > For those of you who know wimaging, the main differences include the > removal of SMB server, adding the rewriting the > Foreman templates (and adding them), support for root_pass, overall > streamlining, revamp of the docs. > > Ultimately, I think this will be merged back to wimaging again given > Dmitry's and my time. > > Caveats > Currently, I've not tested Windows 7; and most likely will never test > 32bit arch. Later, Windows 10/2016 will be > integrated. Also, since we are dealing with propitiatory software, a lot > of things like locating the correct drivers > need to be done manually. People familiar with WDS basically know this > procedure. > > > [1] https://github.com/kireevco/wimaging > [2] https://github.com/helge000/wimaging-ng > [3] https://github.com/helge000/wimaging-ng/issues > -- > Daniel Helgenberger > m box bewegtbild GmbH > > P: +49/30/2408781-22 > F: +49/30/2408781-10 > > ACKERSTR. 19 > D-10115 BERLIN > > > www.m-box.de www.monkeymen.tv > > Geschäftsführer: Martin Retschitzegger / Michaela Göllner > Handeslregister: Amtsgericht Charlottenburg / HRB 112767 >

>>
>> Hello Foreman - users,
>>
>> I recently forked Dmitry Kireev's wimaging[1] to a new project I call
> wimaging-ng[2].
>>
>> Abstract:
>> wimaging-ng a set of scripts to prepare WIM images and templates for
> Foreman to provision Windows hosts.
>> Except for the boot process official Microsoft deployment tools are used;
> most notably dism.exe.
>> All relevant configuration files like unattend.xml are rendered by
> Foreman and downloaded at build time.
>
> That's great! If you like, you are very welcome to join one of our
> community demo to the feature (5-10 minutes).

Sure! The next one would be Thursday I think?

Since This would be my first hangout, are there any more info than [1]?
Esp.: Witch time zone is the hangout? I suppose the presentation is done live?
If so, I think I can only do feature rundown as host building takes time.
Maybe a deep dive would be better since setting is up is can still be rather time consuming?

[1] Current Sprint Information - Foreman

Cheers, Daniel

··· On 05.10.2015 15:49, Ohad Levy wrote: > On Oct 5, 2015 13:42, "Daniel Helgenberger" wrote:

Thanks,
Ohad

I have wimaging-ng currently in production deploying Windows 8.1/2012r2.
I tested it with a variety of different
hardware at my disposal. The Config files I use for Windows8.1/WinPE are
supplied.

Feel free to try it out!
Please open bugs and RFEs directly in GitHub[3].

Also, I am happy to assist; you can reach me on Gitter if you are near
CEST or mail me directly (though I prefer to open
issues).

Features include:

  • Linux style installation using http:// or ftp:// installation media
  • No extra servers like WDS needed - all relevant settings can be
    configured in Foreman directly
  • Official Mircosoft utilities are used for all relevant setup stages
    making it easy to add (future) operating systems
  • Driver installation during build time
  • Support for localization settings (like time zone, locale, UI language)
  • Optional domain join including target OU
  • Optional local user creation
  • Support for Foreman’s root password using Base64 encoding
  • Optional software installation and user tasks at the end of the build
    (like installing puppet ect)

For those of you who know wimaging, the main differences include the
removal of SMB server, adding the rewriting the
Foreman templates (and adding them), support for root_pass, overall
streamlining, revamp of the docs.

Ultimately, I think this will be merged back to wimaging again given
Dmitry’s and my time.

Caveats
Currently, I’ve not tested Windows 7; and most likely will never test
32bit arch. Later, Windows 10/2016 will be
integrated. Also, since we are dealing with propitiatory software, a lot
of things like locating the correct drivers
need to be done manually. People familiar with WDS basically know this
procedure.

[1] https://github.com/kireevco/wimaging
[2] https://github.com/helge000/wimaging-ng
[3] https://github.com/helge000/wimaging-ng/issues

Daniel Helgenberger
m box bewegtbild GmbH

P: +49/30/2408781-22
F: +49/30/2408781-10

ACKERSTR. 19
D-10115 BERLIN

www.m-box.de www.monkeymen.tv

Geschäftsführer: Martin Retschitzegger / Michaela Göllner
Handeslregister: Amtsgericht Charlottenburg / HRB 112767


You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.


Daniel Helgenberger
Schivelbeiner Str. 46
10439 Berlin

Dmitry, Daniel and I are organising a deep-dive on what he's been
working on [1] - would you like to join us on the live stream for
discussion etc? I think it would be great to have both of you there.

Cheers,
Greg

[1] https://plus.google.com/b/102496134326414788199/events/cjhrcccmk92g5k30jnojenolqqc

··· On 11 November 2015 at 08:42, Dmitry Kireev wrote: > Daniel, thanks for interest in my project. I appreciate your contribution! > > We've merged changes back to wimaging, I hope we can cobine our forces and > build a nice opensource WDS alternative.

>> That's great! If you like, you are very welcome to join one of our
>> community demo to the feature (5-10 minutes).
>
> Sure! The next one would be Thursday I think?

Correct! As Ohad says, you're more than welcome.

> Since This would be my first hangout, are there any more info than [1]?
> Esp.: Witch time zone is the hangout? I suppose the presentation is done live?

It is done live, yes. I'm in Europe/London, and it shows as 2pm for
me. I just saw the links on the Sprint Info page were still pointing
to the last demo - they shoud be correct now. If that works for you,
feel free to add yourself to the agenda.

> If so, I think I can only do feature rundown as host building takes time.
> Maybe a deep dive would be better since setting is up is can still be rather time consuming?

I'll be happy to organise a deep dive with you instead (or even as well :P)

> [1] Current Sprint Information - Foreman

Indeed, that's all of it. If you have any questions, feel free to get
in touch on IRC (I'm gwmngilfen in #theforeman) and we can go through
your concerns (and update the page after, it's all useful info). We
usually get presenters on 15mins before to do sound checks and such
like - so you'll have a chance to be sure everthing is working.

Cheers,
Greg

··· On 6 October 2015 at 10:44, Daniel Helgenberger wrote:

>>> That's great! If you like, you are very welcome to join one of our
>>> community demo to the feature (5-10 minutes).
>>
>> Sure! The next one would be Thursday I think?
>
> Correct! As Ohad says, you're more than welcome.
>
>> Since This would be my first hangout, are there any more info than [1]?
>> Esp.: Witch time zone is the hangout? I suppose the presentation is done live?
>
Greg, first of all, thanks for the assistance! I'm a noob to hangouts - please be a little patient with me :slight_smile:

I could not find you on #foreman and my office hours are over so I just drop a mail:

> It is done live, yes. I'm in Europe/London, and it shows as 2pm for
> me. I just saw the links on the Sprint Info page were still pointing
> to the last demo - they shoud be correct now. If that works for you,
> feel free to add yourself to the agenda.
>
>> If so, I think I can only do feature rundown as host building takes time.
>> Maybe a deep dive would be better since setting is up is can still be rather time consuming?
>
> I'll be happy to organise a deep dive with you instead (or even as well :P)
I can do both; a shot demo on community and deep dive.

I think I can boil the stuff down and show how to get started and create basic foreman templates; though I do no think
there is time for a full provision cycle. You think this will do?

Right now I have a devel system with ovirt/foreman but I will put it in production at the end of the month and would
rather do the deep dive before that.
>
>> [1] Current Sprint Information - Foreman
>
> Indeed, that's all of it. If you have any questions, feel free to get
> in touch on IRC (I'm gwmngilfen in #theforeman) and we can go through
> your concerns (and update the page after, it's all useful info). We
> usually get presenters on 15mins before to do sound checks and such
> like - so you'll have a chance to be sure everthing is working.

Great! So I suppose I share my screen and start talking when it's my turn? My notebook runs fedora; is this fine for
hangouts or should I do the whole thing form inside a VM?

Thanks!

··· On 06.10.2015 12:27, Greg Sutcliffe wrote: > On 6 October 2015 at 10:44, Daniel Helgenberger wrote:

Cheers,
Greg


Daniel Helgenberger
Schivelbeiner Str. 46
10439 Berlin

> Greg, first of all, thanks for the assistance! I'm a noob to hangouts - please be a little patient with me :slight_smile:
>
> I could not find you on #foreman and my office hours are over so I just drop a mail:

My pleasure. You did find me, but I was unfortunately afk at the time.
I'll be around all day today if you want to get me there.

> I think I can boil the stuff down and show how to get started and create basic foreman templates; though I do no think
> there is time for a full provision cycle. You think this will do?

That sounds fine. We usually try to stick to 5-10mins max for demo
items, as there are usually plenty to get through, so a quick
show'n'tell of the plugin is ideal.

> Right now I have a devel system with ovirt/foreman but I will put it in production at the end of the month and would
> rather do the deep dive before that.

I think we can schedule something, Let's get the demo out of the way first.

> Great! So I suppose I share my screen and start talking when it's my turn? My notebook runs fedora; is this fine for
> hangouts or should I do the whole thing form inside a VM?

Fedora should work fine, you'll just need the Google plugin for your
browser. If you want to do a test call with me today or tomorrow, I'm
happy to do that.

Greg

··· On 6 October 2015 at 17:58, Daniel Helgenberger wrote: