Installing SP2013 and provisioning UPS does not start the sync however installation of SP2013 manually and using the Configuration wizard seems to work fine.
Sync sits on Starting for a few minutes with error being returned in ULS:
ILM Configuration: Error 'ERR_INVALID_GROUPS'.
UserProfileApplication.SynchronizeMIIS: Failed to configure MIIS pre database, will attempt during next rerun. Exception: System.Configuration.ConfigurationErrorsException: ERR_INVALID_GROUPS at Microsoft.Office.Server.UserProfiles.Synchronization.ILMPostSetupConfiguration.ValidateConfigurationResult(UInt32 result) at Microsoft.Office.Server.UserProfiles.Synchronization.ILMPostSetupConfiguration.ConfigureMiisStage1() at Microsoft.Office.Server.Administration.UserProfileApplication.SetupSynchronizationService(ProfileSynchronizationServiceInstance profileSyncInstance). UserProfileApplication.SynchronizeMIIS: End setup for 'Intranet User Profile'.
Comments: ** Comment from web user: jwolcott **
Sync sits on Starting for a few minutes with error being returned in ULS:
ILM Configuration: Error 'ERR_INVALID_GROUPS'.
UserProfileApplication.SynchronizeMIIS: Failed to configure MIIS pre database, will attempt during next rerun. Exception: System.Configuration.ConfigurationErrorsException: ERR_INVALID_GROUPS at Microsoft.Office.Server.UserProfiles.Synchronization.ILMPostSetupConfiguration.ValidateConfigurationResult(UInt32 result) at Microsoft.Office.Server.UserProfiles.Synchronization.ILMPostSetupConfiguration.ConfigureMiisStage1() at Microsoft.Office.Server.Administration.UserProfileApplication.SetupSynchronizationService(ProfileSynchronizationServiceInstance profileSyncInstance). UserProfileApplication.SynchronizeMIIS: End setup for 'Intranet User Profile'.
Comments: ** Comment from web user: jwolcott **
The issue seems to that the User Profile Synchronization Service is being configured to run as the common name managed account spservice rather than the farm account. The farm account must start the UPS service.
I have run into this problem with both the SP13 version of autospinstaller as well as the codeset 13809.
I could be totally of course here, but, it seems that within the Func: CreateUserProfileServiceApplication of AutoSPInstallerFunctions.ps1 on line 2828 that the UpdateProcessIdentity Function is being called and this is switching the account to the spservice managed account rather than the farm????