Commented Issue: SP 2013 Slipstreaming December 2012 CU Causes Crash [19289]

I've used this script to install 2010 many times - love it!

I've been trying to use it to install 2013 with many problems. As it turns out most of the errors can be avoided by NOT slipstreaming the December 2012 CU or Language Packs.

Build Specs: Single VM, Windows Server 2012, SQL server 2012, SharePoint 2013

Here are some of the errors:

Script halts on this one:
WARNING: 2013/01/30 13:39:52:665::[4016] MSI(INFO): 'MarshalPatchProperties_PublishP: ERROR:
OcaSetProperty(PublishPatchARPMachine): property name should be no longer than 20 chars'

These two require user intervention:
Event ID 1026
Application: stsadm.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.TypeInitializationException Stack: at Microsoft.SharePoint.StsAdmin.SPStsAdmin.Main(System.String[])

Event ID 1000
Faulting application name: stsadm.exe, version: 15.0.4420.1017, time stamp: 0x50672add
Faulting module name: KERNELBASE.dll, version: 6.2.9200.16451, time stamp: 0x50988aa6
Exception code: 0xe0434352
Fault offset: 0x000000000003811c
Faulting process id: 0xf90
Faulting application start time: 0x01cdff363906abf5
Faulting application path: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\BIN\stsadm.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: 78b7e375-6b29-11e2-93fc-0050568974af
Faulting package full name:

Faulting package-relative application ID:
Comments: ** Comment from web user: vladcatrinescu **

Hi Brian,

Sorry to reopen this, however what the author said it's true. At the moment, there is a known issue with December 2012 CU for SharePoint 2013(not 2010) when slip streaming. It should be avoided. The error you get is in the attachment! It's not an autospinstaller error, however it f***ks up your auto install.