I just hit the exact same issue described in (http://www.ibm.com/developerworks/forums/thread.jspa?threadID=461932) but this time on Windows Server 2012 Standard Edition to be installed on x3250M3 4151 (Windows cannot read the <ProductKey> setting from the unattend answer file)
According the ServerProven OS compatibility guide (http://www-03.ibm.com/systems/info/x86servers/serverproven/compat/us/nos/microsoftold.html), the OS is supported:
Test Information For the x3250 M3 (4251,4252)
The following operating system with any service pack or update listed, has been validated and is the minimum required on this system to be considered an IBM supported environment.Updates or service packs equal to or higher within the same NOS release family of the operating system are also supported
Product: Microsoft Windows Server 2012
What am I missing here?
Pinned topic Windows Server 2012 on x3250 M3 with ServerGuide 9.23, <ProductKey> problem
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-12-03T08:42:25Z at 2012-12-03T08:42:25Z by SystemAdmin
Re: Windows Server 2012 on x3250 M3 with ServerGuide 9.23, <ProductKey> problem2012-11-27T03:16:34ZThis is the accepted answer. This is the accepted answer.I'm getting the same error installing it on x240 PureFlex Node.
According to ServerProven, 2012 is compatible with x240
According to ServerGuide, x240 node is supported with 9.23
Its definitely some sort of bug
Duelund 270003VTN61 Post
Re: Windows Server 2012 on x3250 M3 with ServerGuide 9.23, <ProductKey> problem2012-11-27T08:39:18ZThis is the accepted answer. This is the accepted answer.
- SystemAdmin 110000D4XK
ServerGuide 9.23 do not work when installing Windows Server 2012, and no UpgradeXpress with Windows Server 2012 support.
Re: Windows Server 2012 on x3250 M3 with ServerGuide 9.23, <ProductKey> problem2012-12-03T08:42:25ZThis is the accepted answer. This is the accepted answer.Same here with a brand new x3650M4 server with IBM ROK media, I have 3 of these to build this month...
Looks like the problem is no support for OEM software (including IBM OEM software);
This is disappointing