ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Lost Access to Azure Windows Instance

    IT Discussion
    cloud computing azure
    3
    25
    6.2k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • ?
      A Former User
      last edited by

      no idea. i dont play in azure

      A 1 Reply Last reply Reply Quote 0
      • S
        scottalanmiller
        last edited by

        I've used Rackspace a ton and some of AWS and Softlayer. Had to round it out.

        1 Reply Last reply Reply Quote 0
        • S
          scottalanmiller
          last edited by

          They each have their nice features. For the SMB, though, Rackspace is the clear winner. Azure and AWS have little accommodations for SMB style use and assume a lot of things that don't turn out to be true in the SMB. They are clouds to be clouds. Rackspace is a cloud with a strong VPS functionality.

          1 Reply Last reply Reply Quote 0
          • A
            alexntg @A Former User
            last edited by

            @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.

            1 Reply Last reply Reply Quote 0
            • A
              alexntg @scottalanmiller
              last edited by

              @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.

              S 1 Reply Last reply Reply Quote 0
              • S
                scottalanmiller @alexntg
                last edited by

                @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.

                1 Reply Last reply Reply Quote 0
                • S
                  scottalanmiller
                  last edited by

                  Can't just revert back a DC.

                  A 1 Reply Last reply Reply Quote 0
                  • A
                    alexntg @scottalanmiller
                    last edited by

                    @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.

                    S 1 Reply Last reply Reply Quote 0
                    • S
                      scottalanmiller @alexntg
                      last edited by

                      @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.

                      A 1 Reply Last reply Reply Quote 0
                      • ?
                        A Former User
                        last edited by

                        So did this happen to you? or was this a "what if" situation?

                        S 1 Reply Last reply Reply Quote 0
                        • A
                          alexntg @scottalanmiller
                          last edited by

                          @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.

                          S 1 Reply Last reply Reply Quote 0
                          • S
                            scottalanmiller @A Former User
                            last edited by

                            @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.

                            1 Reply Last reply Reply Quote 0
                            • S
                              scottalanmiller @alexntg
                              last edited by

                              @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.

                              1 Reply Last reply Reply Quote 0
                              • 1
                              • 2
                              • 2 / 2
                              • First post
                                Last post