Cannot start SQl on Hyperv Vm after copy and sysprep

Question

Hi,

I am struggling with an issue, hoping someone has insight into.

First off let me say I am far from an SQL expert.

I have an SQL standalone(2014) on a Windows Server(2019), that I wanted to copy to a new vm so I can do a sandbox test environment for an upgrade on system that uses the SQL, and upgrade the SQL also.

I have exported the HyperV VM, and imported onto a different server, that is not connected to the network.

I can start SQL normally after this, so it is an exact replica, just as a non connected vm. so far so good.

But then I sysprep the server ( sysprep /generalize /oobe /reboot /mode:vm) to be able to rename and put on the network with a new ID, and the SQL services will not start. Neither SQL Server or Server Agent will start.

The machine gets renamed after the sysprep, and I cannot login with SMS or anything,

The errors I get when trying to start the service is 1067.

I was under the impression that after you rename the server, the SQL, should reflect the new name, and I could also rename it if not , but I cannot if I cannot start the service, and not sure how a sysprep affects the renaming process as far as SQL is concerned.

1067 points to log on error so I should have also said I changed the logon creds for the service to the local admin, as that is the only valid one now, and still get the same error, also with local system account

Any help is appreciated.

thanks

Answer 1

The machine gets renamed after the sysprep, and I cannot login with SMS or anything

See Rename a computer that hosts a stand-alone instance of SQL Server