As far as I know there is no way to pass variables/environments 
informations directly to wondows (WinPE) without (re)building the image and 
including the configuration in it.

I've found that a simple way could help us without too many hacks.

Actually when we boot up we spawn an IP from the DHCP from our TFTP/Proxy 
server.

The pxe configuration at the moment show something like this:
DEFAULT menu
LABEL menu
     COM32 linux.c32 boot/wimboot
     APPEND initrdfile=boot/windows-x64/bcd,boot/windows-x64/boot.sdi,boot/
windows-x64/boot.wim


Adding at the end of the PXE the variables in a commented way could be a 
good alternative:
DEFAULT menu
LABEL menu
     COM32 linux.c32 boot/wimboot
     APPEND initrdfile=boot/windows-x64/bcd,boot/windows-x64/boot.sdi,boot/
windows-x64/boot.wim

#VAR FOREMANURL "https://myforeman.url.domain.ext";
#VAR AUTOPROVISION "https://myforeman.url.domain.ext
/unattended/provision?token=0000000-0000-0000-0000-0000000000"
#VAR HOSTNAME "MYHATEDWINMACHINE01" 
#VAR DOMAIN "windowsdomain01.local"



After that with a script that will be the same per any installation we will 
contiune the installation.
We'll need a TFTP client (obviously) and a good dose of batch scripting.

I'm not that good on windows and I can use an hand.

With this configuration we will be able to installa machine behind NAT that 
actually could not get the provision configration file.

K.

-- 
You received this message because you are subscribed to the Google Groups 
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to