Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 24 Oct 2016 08:07:13 +0000
From:      Matt Churchyard <matt.churchyard@userve.net>
To:        The Doctor <doctor@doctor.nl2k.ab.ca>
Cc:        "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org>
Subject:   RE: Windows 2016 Server
Message-ID:  <33e8e02d845145918591d25196402491@SERVER.ad.usd-group.com>
In-Reply-To: <20161021222342.GA80184@doctor.nl2k.ab.ca>
References:  <20161021183120.GA21232@doctor.nl2k.ab.ca> <20161021190122.GA30602@doctor.nl2k.ab.ca> <alpine.BSF.2.20.1610212216310.22551@z.fncre.vasb> <0406d06f-aa1a-677c-775a-b09a3ebd3073@freebsd.org> <20161021222342.GA80184@doctor.nl2k.ab.ca>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Oct 21, 2016 at 03:21:10PM -0700, Peter Grehan wrote:
> >> [Windows could not parse or process unattend answer file=20
> >> [D:\autounattend.xml] for pass [windowsPE]. The answer file is=20
> >> invalid.]
> >
> > Something is wrong with your autounattend.xml file.
>=20
>   Still working on the 2k16 unattend file. Unfortunately things have=20
> changed from TP5 in a non-obvious way :(
>=20
>   A workaround is to do a GUI install.
>=20
> later,
>=20
> Peter.

> Please explain what you mean by a GUI install.

Not sure if anyone's replied directly to you -

1) Make sure you are running at least 11-RELEASE

2) Use an "off-the-shelf" Windows install CD

3) Add the following to your bhyve command

        -s 29,fbuf,tcp=3D0.0.0.0:5900,w=3D800,h=3D600,wait
        -s 30,xhci,tablet

4) Run bhyve and then use a VNC client to connect and install using the nor=
mal Windows GUI

Matt



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?33e8e02d845145918591d25196402491>