Here is a quick list of current issues & missing functionality for AutoSPInstaller & SharePoint 2013:
- The following SP2013-only service applications are not yet implemented:
Access Services (the new one for 2013; Access Services 2010 is still supported) - DONE
Machine Translation Service - DONE
PowerPoint Conversion Service Application - DONE
Work Management Service Application - DONE
Workflow Service Application - this will actually automatically be provisioned when you create a Workflow Manager 1.0 / Service Bus farm (separately from AutoSPInstaller) and connect it to your SharePoint farm
"PowerPoint Service Application" throws an error if we try to provision it on 2013; I need to put in a check and/or split out the different 2010 and 2013 “PowerPoint” service apps
Enterprise Search 2013 only really provisions on a single server (admin/crawl/query roles all on one); you can still however go in after the fact and update the topology manually (using PowerShell) to your desired configuration
- There is no support for Office Web Apps 2013 yet (OWA 2013 no longer installs on a SharePoint server; in fact – it’s all on its own)
SSL support for web apps seems to be problematic in Windows Server 2012; still not sure why. For best compatibility you can avoid using https URLs for now. - FIXED
There are issues with doing a fully-offline install on Windows Server 2012, specifically the .Net 3.5.1 feature apparently tries to connect to the Internet even if you specify a local \sxs\ installation source
Cheers
Brian