I think the key is not to do that *instead* of fixing any underlying cluster issues.

As Sue says, they're not included as part of the install: you have to add them if you want them.

For heaven's sake! How frustrating.

I'm sure that was a bug in a version of SSMS, but I can't remember which one. Try using another version of it?

So you have just two database servers in total, across two datacentres? How are they each part of a 3-node cluster, in that case?

Also make sure you have instant file initialization on so that autogrowth events are as non-disruptive as possible.

Maybe he thinks that if you put it on a server that automatically makes it "Production" :D.

I've never heard of that!  I'm sure you're right.

You have to delete it then re-create it. A less disruptive alternative could be to create a DNS alias for the listener and give that the name you want.

Also Lincoln Burrows is bumping a LOT of very old threads for seemingly no reason :ermm:.

The Google Translate person/bot is at it again on this thread: https://www.sqlservercentral.com/Forums/456434/Can-you-recover-data-from-transaction-log?PageIndex=2 (I reported it so it should have gone now).

Tiny screenshot, sorry.

You're bumping quite a lot of old threads at the moment. Is there a reason?

Can you restart the cluster service (not the servers! The service) and see if that helps?