On Thu, Mar 14, 2019 at 2:01 AM Andrew Philp <andrew.ph...@gmail.com> wrote:
> Awesome stuff Lee, have been watching this topic and agree Scott is almost > valuable resource for this project. > > > Many Thanks > > Andrew Philp > T: +447482853508 > > http://uk.linkedin.com/in/andrewphilp > > http://twitter.com/PHIAN01 > > On 13 Mar 2019, at 17:01, Lee Turchin <lturch...@gmail.com> wrote: > > HI All - > > Successfully completed the installation and automation of Windows Server > 2016 DataCenter Desktop Experience. Needed to utilize a customized > unattended.xml.erb and a non-evaluation version of Windows Server 2016. > I must thank Scott McClellan for leading me in the right direction, often, > when I faced some serious blocks and seeming dead ends. > > Thanks Lee! I'm glad you were able to get it working. One final note, for posterity, is that there are two ways to install Windows Server using an evaluation version: - Using a real ISO and the evaluation key. Our unattended.xml.erb includes the evaluation key, so should work out of the 'box' using this ISO. - Using the Evaluation ISO (downloadable from Microsoft). This version ships with a valid product key, so you need to remove the "<ProductKey>" block from our unattended.xml.erb. Since our unattended.xml.erb ships with the evaluation key, that means we can harness node metadata ("productkey") to sub in a real key for a deployment. Scott > Good luck to all. > Questions and answers are welcomed. > > Regards, > Lee > > On Wednesday, February 20, 2019 at 1:53:37 PM UTC-8, Lee Turchin wrote: >> >> Hi, >> >> I have installed Razor Server on a CentOS 7 platform and have followed >> the GitHub instructions to run the installation for Windows Server. In my >> case, I am testing the installation of Windows 2016 Server on a SAN. I have >> gotten to the point where my installation successfully loads the >> microkernel, reboots my blade, and then unpacks the ps1 created boot.wim >> file, attaches to a share, runs the Windows 2016 setup and copies the files >> to the appropriate SAN disk. >> >> However, after the reboot, stage 2 never happens. There is the continual >> loop that unpacks the boot.wim on the next go around. I am using the >> Windows 2016 task and have the correct path selected for tasks. >> >> In the razor documentation, >> https://github.com/puppetlabs/razor-server/wiki/Writing-Tasks, there is >> a statement that says: >> >> Each boot (except for the default boot) must culminate in something akin >> to curl <%= stage_done_url %> before the node reboots. Omitting this will >> cause the node to reboot into the same boot template over and over again. >> >> My questions are: >> >> 1. where should the line 'curl <%= stage_done_url %' go? I need to let >> razor know that stage 1 is completed. >> 2. what edits do I make to the unattended.xml ? >> 3. why does Windows 2016.task show that it is related to the Windows 2008 >> pro engine, when it should be related to the Windows 2010 engine? as in the >> following output from the command 'razor tasks windows/2016 base' >> >> [root@Lee-Centos7 etc]# razor tasks windows/2016 base >> From http://localhost:8150/api/collections/tasks/windows: >> >> name: windows >> description: Microsoft Windows Generic Installer >> os: >> version: 8-pro >> boot_seq: >> 1: boot_wim >> default: boot_local >> >> 4. is there an edit that I can apply to the boot order, for example, in >> 'second-stage.ps1.erb', a file housed in >> the >> /opt/puppetlabs/server/apps/razor-server/share/razor-server/tasks/windows/8pro.task >> directory, that can move the process forward? >> 5. would an upgrade of 'wimboot' be of any help and does this file need >> to be in the Windows/2016 task folder? >> 6. are there any Windows 2016 Server example tasks that I might model my >> own after? for now, it appears that the jump to stage 2 in the windows >> server setup is vital to the success of our project. >> >> >> Thank you, >> >> Lee >> >> >> >> > -- > You received this message because you are subscribed to the Google Groups > "puppet-razor" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-razor+unsubscr...@googlegroups.com. > To post to this group, send email to puppet-razor@googlegroups.com. > Visit this group at https://groups.google.com/group/puppet-razor. > For more options, visit https://groups.google.com/d/optout. > > > -- > You received this message because you are subscribed to the Google Groups > "puppet-razor" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-razor+unsubscr...@googlegroups.com. > To post to this group, send email to puppet-razor@googlegroups.com. > Visit this group at https://groups.google.com/group/puppet-razor. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "puppet-razor" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-razor+unsubscr...@googlegroups.com. To post to this group, send email to puppet-razor@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-razor. For more options, visit https://groups.google.com/d/optout.
