Lost Access to Azure Windows Instance
-
@Hubtech said:
no idea. i dont play in azure
Likewise. I'm an AWS person. At least in AWS, you can restore back to the last snapshot of the machine you took (assuming you took one). If you do something like give it a bad IP address or it bluescreens, your options are to reboot, restore from backup, or rebuild from scratch.
-
@scottalanmiller said:
@alexntg said:
@scottalanmiller said:
Was already getting LMI on there. But no work arounds on Azure as far as I can tell. If this happens the box is just " lost".
Could you please rephrase that? Were you able to connect to LogMeIn, but couldn't log into the server, or you weren't able to connect via LogMeIn?
The question is about just azure. If you have a Windows server on Azure and ANY tool you are using loses access.... What is the fallback?
Have multiple tools in place. If you're using RDP and that fails, Try connecting via LogMeIn, or vice versa. There's also remote management from another box on the same network. If all 3 fail, there's something bad happening with the machine.
-
@alexntg said:
@scottalanmiller said:
@alexntg said:
@scottalanmiller said:
Was already getting LMI on there. But no work arounds on Azure as far as I can tell. If this happens the box is just " lost".
Could you please rephrase that? Were you able to connect to LogMeIn, but couldn't log into the server, or you weren't able to connect via LogMeIn?
The question is about just azure. If you have a Windows server on Azure and ANY tool you are using loses access.... What is the fallback?
Have multiple tools in place. If you're using RDP and that fails, Try connecting via LogMeIn, or vice versa. There's also remote management from another box on the same network. If all 3 fail, there's something bad happening with the machine.
In this case, LMI wasn't installed yet. And access from other machines on the same network were what was failing.
-
Can't just revert back a DC.
-
@scottalanmiller said:
Can't just revert back a DC.
In that case, it'd be a simple matter of tossing the old DC and spinning up a new one. More of an annoyance than anything else.
-
@alexntg said:
@scottalanmiller said:
Can't just revert back a DC.
In that case, it'd be a simple matter of tossing the old DC and spinning up a new one. More of an annoyance than anything else.
Yes. Mostly stateless. Would be scary if you put all DCs on azure though. Or any live/live system like this where an environmental change might lock out the entire environment.
-
So did this happen to you? or was this a "what if" situation?
-
@scottalanmiller said:
@alexntg said:
@scottalanmiller said:
Can't just revert back a DC.
In that case, it'd be a simple matter of tossing the old DC and spinning up a new one. More of an annoyance than anything else.
Yes. Mostly stateless. Would be scary if you put all DCs on azure though. Or any live/live system like this where an environmental change might lock out the entire environment.
I have my entire environment on AWS, spread across two geographic regions with a site-to-site VPN. Upping it a level would be putting one part on AWS and the other on Azure, with a site-to-site VPN between the two.
-
@Hubtech said:
So did this happen to you? or was this a "what if" situation?
Really happened but while testing. So no bad outcome. So it's a "what if" now.
-
@alexntg said:
@scottalanmiller said:
@alexntg said:
@scottalanmiller said:
Can't just revert back a DC.
In that case, it'd be a simple matter of tossing the old DC and spinning up a new one. More of an annoyance than anything else.
Yes. Mostly stateless. Would be scary if you put all DCs on azure though. Or any live/live system like this where an environmental change might lock out the entire environment.
I have my entire environment on AWS, spread across two geographic regions with a site-to-site VPN. Upping it a level would be putting one part on AWS and the other on Azure, with a site-to-site VPN between the two.
Yes. Having one node in Rackspace would have protected against this.
