New Question

Andrew_Love's profile - activity

2018-03-06 15:13:23 +0300 received badge  Taxonomist
2014-11-26 15:09:34 +0300 received badge  Self-Learner (source)
2014-11-26 15:09:34 +0300 received badge  Teacher (source)
2014-10-31 09:52:04 +0300 received badge  Famous Question (source)
2014-10-20 18:05:37 +0300 received badge  Notable Question (source)
2014-10-20 18:01:58 +0300 answered a question Ubuntu MAAS commissioning of WIN2012R2 boot images

Couple of things to note based on my experiences so far following http://wiki.cloudbase.it/maas with virtual machines rather than physical:

  1. Where the notes say "Note: If you are deploying on a vmware/esxi environment, be sure to change your network adapter type inside your vmx files to e1000e." - This holds true for KVM/Virt too. I suspect all other hypervisors too. The WIndows Server install only seems to work with this adapter type. Anything else and the run_install.ps1 scripts start to throw network connectivity errors.

  2. Similar, any virtual hard disks need to be IDE or SATA otherwise the Windows Server installer will not recognise them. I started off with virtio (KVM/Virt) and hit problems.

Now if I could just get past the "Windows cannot find the Microsoft Software License Terms" error message ...

2014-10-02 22:11:54 +0300 received badge  Popular Question (source)
2014-10-01 19:57:17 +0300 commented answer Ubuntu MAAS commissioning of WIN2012R2 boot images

Ok so I've found the problem. My MAAS controller did not have python-hivex installed. The script /usr/lib/python2.7/dist-packages/provisioningserver/boot/windows.py errored and MAAS fell back to an Ubuntu install instead. Once I installed python-hivex and started teh node it booted into a Windows install.

2014-10-01 18:51:07 +0300 commented answer Ubuntu MAAS commissioning of WIN2012R2 boot images

Which channel are you on? I've made your changes to the naming and I now see Windows "Server 2012 R2" in the release field. How do I switch to using the PXE installer from curtin?

2014-10-01 17:00:52 +0300 commented answer Ubuntu MAAS commissioning of WIN2012R2 boot images

Getting somewhere ... Now in /var/log/maas/maas.log I get: "Error generating the URL of curtin's image file. No image could be found for the given selection: os=windows, arch=amd64, subarch=generic, series=win2012hvr2, purpose=xinstall" I have the following boot images: win2012r2std (amd64, generic, install, release) and win2012r2dc (amd64, generic, install, release) I guess I need to be able to select the correct image

2014-10-01 16:21:25 +0300 commented answer Ubuntu MAAS commissioning of WIN2012R2 boot images

The node is tagged as use-fastpath-installer. I have stopped the node again, edited the node, selected OS=Windows, saved the node, started the node. It boots into Trusty!

2014-09-30 20:37:29 +0300 commented answer Ubuntu MAAS commissioning of WIN2012R2 boot images

Hi Gabriel Many thanks for the clarification. Once I start the node it runs through a provisioning sequence much like the Ubuntu nodes and then waits at a point where its says "Cloud-init v. 0.7.5 finished at ..." Is this as expected?

2014-09-30 18:59:37 +0300 asked a question Ubuntu MAAS commissioning of WIN2012R2 boot images

I followed: http://wiki.cloudbase.it/maas and now have a win2012r2std boot image available in my MAAS cluster.

Viewing the cluster boot image list I only see the INSTALL image whereas Ubuntu Trusty has COMMISIONING, XINSTALL and INSTALL images.

In the MAAS node edit screen I see options to select "Windows" as the OS and "Most recent release" as the Release. However when I commission the node it uses Ubuntu trusty.

How do I commission a win2012r2 node in MAAS?