We started windows unattended installation by using the URL
http://www.puppetblog.nl/installation/the-foreman-windows-deployment/
Our kick start file looks like
[root@sdin-swt-ct-04 pxelinux.cfg]# cat 01-90-b1-1c-60-de-73
···
#This file was deployed via ‘Windows Kickstart default PXELinux’ template
Supported host/hostgroup parameters:
blacklist = module1, module2
Blacklisted kernel modules
DEFAULT linux
LABEL linux
KERNEL boot/windows-x86_64/wimboot
APPEND initrd=boot/windows-x86_64/bootmgr
ks=http://sdin-swt-ct-04.abccorp.global.abc.com/unattended/provision?token=a3da21ff-889f-41ab-bed2-fc4b25b1a618
network ks.sendmac
IPAPPEND 2
[root@sdin-swt-ct-04 pxelinux.cfg]#
After this we saw that the following files were generated with zero bytes
[root@sdin-swt-ct-04 windows-x86_64]# ls -lrt
total 264368
-rw-r–r--. 1 foreman-proxy foreman-proxy 0 Mar 12 02:11 wimboot
-rw-r–r--. 1 foreman-proxy foreman-proxy 0 Jun 14 19:05 bcd
-rw-r–r--. 1 foreman-proxy foreman-proxy 0 Jun 14 19:23 bootmgr
-rw-r–r--. 1 foreman-proxy foreman-proxy 0 Jun 14 19:38 boot.wim
-rw-r–r--. 1 foreman-proxy foreman-proxy 0 Jun 14 19:38 boot.sdi
We downloaded wimboot from http://ipxe.org/wimboot
http://ipxe.org/wimboot and other files from our legacy pxe server which
is a WIndows Server 2012 R2 machine.
Now once wimboot starts it complains that argument “ks” which is present in
the kick start file is unrecognized argument.
The error received is as below
initrd=boot/windows-x86_64/bootmgr
ks=http://sdin-swt-ct-04.abccorp.global.abc.com/unattended/provision?token=a3da21ff-889f-41ab-bed2-fc4b25b1a618
network ks.sendmac
*unrecognized argument ks = a3da21ff-889f-41ab-bed2-fc4b25b1a618 *
press any key to reboot