Answered by:
SCCM 2012 Client installation while OSD on Hyper-V Server fails

Question
-
About the Problem:
When I do operating System deployment of Hyper-V Server (the free Standalone Version), the installation ends up looping, while trying to install the .Net 4 Client. But it can't be installed, because the core Version needs another .Net 4 package than GUI Server. So I actually activated the Feature "NetFx3-ServerCore", which should be enough for the client. I can check with "dism /online /get-features" that the feature is enabled. But it still loops.Workaround:
As I did in Beta, I install .net 4 through unattend.xml (http://sccmfaq.wordpress.com/2012/02/12/sccm-2012-rc2-osd-windows-server-2008-r2-sp1-core/ ). I already asked, if there is a MSI switch which can be used in the TS step "Install Windows and ConfigMgr" to suppress the installation of .Net 4, but it doesn't.Wondering, why I have to install .Net 4 through unattend.xml, any suggestion will be welcome. And I looked on the official page (http://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_SupConfigClientReq ), so Hyper-V Server is not on the supported OS list, is it correct that the Hyper-V Server Version is not supported?
- Edited by Martin Wüthrich Sunday, June 17, 2012 1:00 PM
- Moved by Stan White [MSFT]Microsoft employee Friday, June 22, 2012 4:57 PM (From:Configuration Manager 2012 - General)
Sunday, June 17, 2012 12:56 PM
Answers
-
As you say, Hyper-V server doesn't support the installation of the client. The only supported OS versions for the client are on the link you sent.
It's happening because the client can't understand what is happening because it's not supported.
- Marked as answer by Robert Marshall - MVPMVP Thursday, November 22, 2012 10:14 AM
Tuesday, June 19, 2012 8:52 PM
All replies
-
As you say, Hyper-V server doesn't support the installation of the client. The only supported OS versions for the client are on the link you sent.
It's happening because the client can't understand what is happening because it's not supported.
- Marked as answer by Robert Marshall - MVPMVP Thursday, November 22, 2012 10:14 AM
Tuesday, June 19, 2012 8:52 PM -
Have you tried with the skipprereq:dotnetfx40_client_x86_x64.exe install propertie of the sccm client?Tuesday, June 19, 2012 10:00 PM
-
This is not possible while OSD. The skipprereq switch exists only when you use ccmsetup.exe:
About Client Installation Properties in Configuration Manager (http://technet.microsoft.com/en-us/library/gg699356.aspx)Thursday, June 21, 2012 11:07 AM