I would like to upgrade a single Windows Server 2012 instance to be a Domain Controller.

The exact context is that I have some console apps that need to be run as administrator at startup. And from testing on a debug server, upgrading a server to be a domain controller allows this. Aside from this, I tried adding a batch file to the StartUp folder and logging in an admin user automatically - but I could not get the scripts to run as admin.

And from testing on a debug server, upgrading a server to be a domain controller allows this. - Erm, wut? Not sure why you would need to run as a DC for this. I really doubt you need to. Knowing nothing else, I suspect it would be a bad idea for you to do this.
– ZoredacheJan 30 at 19:42

4

This sounds like a "worst practice" case for using a Domain Controller. I'd look at figuring out how to make your console apps work on a standalone server or a domain member, not a Domain Controller.
– joeqwertyJan 30 at 19:49

In this case the source code is unlikely to be edited, and there is just a single computer
– Zach SmithJan 30 at 19:52

if you just have the single computer why do you need an AD? If it's just a single server, install hyper-v and deploy the DC to a separate instance.
– Jim BJan 30 at 19:55

A batch file needs to run on startup (automatically), and as admin
– Zach SmithFeb 2 at 7:28

1

That's fine. Set a scheduled task to run at startup, tell it to run as the local administrator. You will need to supply it with the local Administrator password. And you still don't need a domain controller. Do you know how to setup a scheduled task? Do you know the password for the local administrator account? If you can answer yes to both questions then you are all set. And you still don't need a domain controller.
– LarrycFeb 2 at 16:43