Can't access SQL after switching server role to domain controller

[Domo]

We're running SQL Server 2008 on Win Server 2008. It's used for testing web solutions we build.

Up until recently it was fine using local accounts, and as there was no need for AD we kept things simple. However, a recent applicaton requires an FQDN.

Subsequently I added the domain controller role - everything appears fine except it's stripped out all the local accounts. Now I can't access my SQL instance via Management Studio.

Any tips? Or is it a re-install job

 

[Domo]

Unable to use the SA account.

I'll go for the re-install. To clarify what the requirements for this additional software. We provide the vendor with a domain name which the installation routine then checks in order to validate. The license file is domain sensitive.

Note, our server is a stand alone machine, it's not connected to anything at all.

What should I do?

 

[Domo]

Thanks for all the advice guys. Since it's a test box I've gone ahead and reloaded the OS. So I'm sat with a new build, all updates complete.

Now I need your advice once more. Please be gentle with me! I'm not a server admin - but a developer. Since I have some IT background I get to do server builds etc. This is the first app I've encountered which is domain sensitive.

At the moment the machine is sat in the default workgroup.

So what do I need to do, so that when this software installs and checks for the domain name xxxxxxx.com it actually exists?

It's a standalone server and there is no requirement for AD.