Is there a commandline to add the kms key that you could run in the post-install section of the system package?
It doesn't work with a MAK key either. Also, it doesn't join the machine to the domain or install the rscd agent. The deployment history log shows no errors. Is there somewhere else I can look for more detailed error logging?
I was able to do the 2008 install w/o a key at all (customize the xml file), though I didn't have to add it to a domain.
I got it to join the domain when I created the machine account in an unmanaged OU... Still can't figure out what's wrong with the agent install though. Is the path for RSCD Installer Location in system package type configuration a relative path?
My PXE data store virtual_dir is "provisioning/pxe" so what should my RSCD Installer location be (the samba share is //machine-name/provisioning)?
In the OS definition (Tools | Configurations ) the agent install path is relative to the pxestore share.
So my directory looks like this:
My samba share is \\blapp\pxestore
so my agent install path for windows is:
OK. So mine is AgentInstalls/Winx64 and it's not installing.
I'm still trying to get the release notes for the forthcoming provisioning hotfix, but it sounds like these may both be known problems.
use '\' and not '/' in the location since it's relative to the windows share path. also you have the 2 files in there - 'rscd.iss' and 'rscd.exe' ?
This is a known issue, which we documented a work around for in the 8.0 SP2 tech bulletin:
Installing Microsoft Windows Server 2008 R2 with a Multiple Activation Key
To install Windows Server 2008 R2 with a Multiple Activation Key, leave the License Key field blank on the Computer Settings panel when you create the system package. You can activate the key on the individual target server later or you can customize the unattend.xml file manually to activate the key at install time.
To customize the unattend.xml file to activate the MAK License key:
1 In the system package, click the Unattend Entries tab.
2 In the Additional Unattend Entries area, click Add a new additional Unattend script.
3 In the Generated Unattend area, under pass=specialize, select the Microsoft-Windows-Shell-Setup component.
4 In the Add/Replace XML Component area, select the Add to Selected Node radio button and add this entry:
<ProductKey>MAK Product Key</ProductKey>
Where "MAK Product Key" is the product key you want to activate.
5 Save the system package.
I am trying to follow your steps but when i leave the "License Key field Blank" I recive an error stating that the License Key field is required...
has this been changed i am on 8.0 SP5
I am using 8.0 SP5 and receive the same error leaving "License Key field Blank". the workaround that has been successful has been to create a local property called KEY or whatnot and reference it for the key. Then the "magic" is to leave the property blank yielding a <key></key> in the resulting xml.
Hope that this helps.
We have found that if you use the Volume License version fo the 2008 R2 media is has the activation keys built into it ready for KMS licensing.
I can now leave the key entry blank and it activates fine