I thank you for your suggestion. I've read this article: It is relevant to the previous error that I had already encountered when trying to deploy the RDS role on that server. And I fixed it by adding the Logon as a service rights to NETWORK, NETWORK SERVICE and SERVICE in a GPO. Before doing that I had the error mentioned in that article.
Now I'm on the next error! I still have a 2003 DC in that domain and thus cannot raise the AD level. I'm wondering if there is another permission missing due to this 2003 legacy, but don't know which one. Regards, Jean-Christian Chevalier On 10.12.2014 16:07, J- P wrote: > You should raise your AD level since you have 2012 DC's > http://www.smallbusinesstech.net/more-complicated-instructions/windows/fixing-windows-internal-database-installation-error-on-windows-server-2012 > > > > Jean-Paul Natola > > > > > Date: Wed, 10 Dec 2014 10:51:16 +0100 > > From: [email protected] > > To: [email protected] > > Subject: [NTSysADM] Event ID 5601 source MSSQL$MICROSOFT##WID when > > deploying RDS role on Windows > Server 2012 R2 > > > > Good Morning, > > > > I'm installing the Remote Desktop Services role on a Windows Server 2012 R2 > > (French version). I'm > > doing the quick start deployment type, for session base desktops. > > > > The installation fails and I find the following event id in the system log: > > Event ID: 5601 > > Source: MSSQL$MICROSOFT##WID > > Text: Impossible de forcer la régénération de la clé principale du service > > tel que demandé par > > l'option de démarrage -F. Erreur 33094. > > Text translation: Unable to force the regeneration of the main key of the > > service as requested by > > the startup option -F. Error 33094. > > > > I would appreciate any guidance in solving this, as I can't find anything > > about this in Google. > > > > This is a new Server 2012 R2, running in a 2003 Active Directory domain. > > This 2012 R2 is also a DC. > > > > Jean-Christian > > > > > >
