Unable to connect to an Azure VM (sysprepped image)









up vote
2
down vote

favorite












I created a Server 2008R2 VM in Hyper V, ran Sysprep on it, then uploaded the VHD to Azure via Azcopy.



Then I converted the VHD file into a managed disk, and created a VM from the managed disk.



Now I am unable to RDP to this VM to complete the installation.



I tried running mstsc /admin however this didn't work either.



I installed boot diagnostics and got a picture of the current state, however I'm not sure how to proceed from here.



Is there any way I can connect to it to complete the installation?



screenshot of current VM state (via boot diagnostics)



Thanks.










share|improve this question

















  • 1




    Can you RDP to the original VM you created in Hyper-V? If not, boot it in audit mode, fix it and try again.
    – Michael Hampton
    22 hours ago











  • Hi Michael, can you elaborate on your solution? What does booting into audit mode do?
    – Jon
    22 hours ago










  • Audit mode lets you make changes to a sysprepped system without going through OOBE, as if you hadn't sealed it. You can then reseal it again. Press Ctrl-Shift-F3 at the OOBE screen shown in your screenshot to enter audit mode.
    – Michael Hampton
    22 hours ago















up vote
2
down vote

favorite












I created a Server 2008R2 VM in Hyper V, ran Sysprep on it, then uploaded the VHD to Azure via Azcopy.



Then I converted the VHD file into a managed disk, and created a VM from the managed disk.



Now I am unable to RDP to this VM to complete the installation.



I tried running mstsc /admin however this didn't work either.



I installed boot diagnostics and got a picture of the current state, however I'm not sure how to proceed from here.



Is there any way I can connect to it to complete the installation?



screenshot of current VM state (via boot diagnostics)



Thanks.










share|improve this question

















  • 1




    Can you RDP to the original VM you created in Hyper-V? If not, boot it in audit mode, fix it and try again.
    – Michael Hampton
    22 hours ago











  • Hi Michael, can you elaborate on your solution? What does booting into audit mode do?
    – Jon
    22 hours ago










  • Audit mode lets you make changes to a sysprepped system without going through OOBE, as if you hadn't sealed it. You can then reseal it again. Press Ctrl-Shift-F3 at the OOBE screen shown in your screenshot to enter audit mode.
    – Michael Hampton
    22 hours ago













up vote
2
down vote

favorite









up vote
2
down vote

favorite











I created a Server 2008R2 VM in Hyper V, ran Sysprep on it, then uploaded the VHD to Azure via Azcopy.



Then I converted the VHD file into a managed disk, and created a VM from the managed disk.



Now I am unable to RDP to this VM to complete the installation.



I tried running mstsc /admin however this didn't work either.



I installed boot diagnostics and got a picture of the current state, however I'm not sure how to proceed from here.



Is there any way I can connect to it to complete the installation?



screenshot of current VM state (via boot diagnostics)



Thanks.










share|improve this question













I created a Server 2008R2 VM in Hyper V, ran Sysprep on it, then uploaded the VHD to Azure via Azcopy.



Then I converted the VHD file into a managed disk, and created a VM from the managed disk.



Now I am unable to RDP to this VM to complete the installation.



I tried running mstsc /admin however this didn't work either.



I installed boot diagnostics and got a picture of the current state, however I'm not sure how to proceed from here.



Is there any way I can connect to it to complete the installation?



screenshot of current VM state (via boot diagnostics)



Thanks.







azure sysprep






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked 22 hours ago









Jon

111




111







  • 1




    Can you RDP to the original VM you created in Hyper-V? If not, boot it in audit mode, fix it and try again.
    – Michael Hampton
    22 hours ago











  • Hi Michael, can you elaborate on your solution? What does booting into audit mode do?
    – Jon
    22 hours ago










  • Audit mode lets you make changes to a sysprepped system without going through OOBE, as if you hadn't sealed it. You can then reseal it again. Press Ctrl-Shift-F3 at the OOBE screen shown in your screenshot to enter audit mode.
    – Michael Hampton
    22 hours ago













  • 1




    Can you RDP to the original VM you created in Hyper-V? If not, boot it in audit mode, fix it and try again.
    – Michael Hampton
    22 hours ago











  • Hi Michael, can you elaborate on your solution? What does booting into audit mode do?
    – Jon
    22 hours ago










  • Audit mode lets you make changes to a sysprepped system without going through OOBE, as if you hadn't sealed it. You can then reseal it again. Press Ctrl-Shift-F3 at the OOBE screen shown in your screenshot to enter audit mode.
    – Michael Hampton
    22 hours ago








1




1




Can you RDP to the original VM you created in Hyper-V? If not, boot it in audit mode, fix it and try again.
– Michael Hampton
22 hours ago





Can you RDP to the original VM you created in Hyper-V? If not, boot it in audit mode, fix it and try again.
– Michael Hampton
22 hours ago













Hi Michael, can you elaborate on your solution? What does booting into audit mode do?
– Jon
22 hours ago




Hi Michael, can you elaborate on your solution? What does booting into audit mode do?
– Jon
22 hours ago












Audit mode lets you make changes to a sysprepped system without going through OOBE, as if you hadn't sealed it. You can then reseal it again. Press Ctrl-Shift-F3 at the OOBE screen shown in your screenshot to enter audit mode.
– Michael Hampton
22 hours ago





Audit mode lets you make changes to a sysprepped system without going through OOBE, as if you hadn't sealed it. You can then reseal it again. Press Ctrl-Shift-F3 at the OOBE screen shown in your screenshot to enter audit mode.
– Michael Hampton
22 hours ago











2 Answers
2






active

oldest

votes

















up vote
3
down vote













There's no RDP functionality during the specialize phase of Windows Setup, which is the phase you're seeing in your screenshot upon first boot of your sysprepped VM. You're going to need to use Sysprep with an answer file so that the specialize phase runs unattended.



There's no traditional "console" access to an Azure VM. There's a serial console connection available, but I don't believe you can use it to configure the VM while it's in the specialize phase of Windows Setup.



https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/use-answer-files-with-sysprep






share|improve this answer



























    up vote
    2
    down vote













    You must have missed the step in the process to convert VHD to and Azure Image before deploying. Below is a link to the process.



    https://docs.microsoft.com/en-us/azure/virtual-machines/windows/upload-generalized-managed#generalize-the-source-vm-by-using-sysprep



    At this point you will have to delete VM and disk. Upload sysprep VHD again, this time convert to image then deploy from image.



    Easiest and fastest way to fix issue.






    share|improve this answer




















    • This is true, I missed that step, I actually took the VHD and converted it to a managed disk, and then an imjage,
      – Jon
      19 hours ago










    • However I attempted the steps as per the article, created an image from the generalized VHD, and then and created a VM from the image, which still had a similar problem (wouldn't boot up) ... as per this img imgur.com/tkvpR2C
      – Jon
      19 hours ago










    • actually, the VM resolved itself automatically (after a while) and now I can log on. (Following the steps mentioned above in that article)
      – Jon
      19 hours ago











    Your Answer








    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "2"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader:
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    ,
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );













     

    draft saved


    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f939258%2funable-to-connect-to-an-azure-vm-sysprepped-image%23new-answer', 'question_page');

    );

    Post as a guest






























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    3
    down vote













    There's no RDP functionality during the specialize phase of Windows Setup, which is the phase you're seeing in your screenshot upon first boot of your sysprepped VM. You're going to need to use Sysprep with an answer file so that the specialize phase runs unattended.



    There's no traditional "console" access to an Azure VM. There's a serial console connection available, but I don't believe you can use it to configure the VM while it's in the specialize phase of Windows Setup.



    https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/use-answer-files-with-sysprep






    share|improve this answer
























      up vote
      3
      down vote













      There's no RDP functionality during the specialize phase of Windows Setup, which is the phase you're seeing in your screenshot upon first boot of your sysprepped VM. You're going to need to use Sysprep with an answer file so that the specialize phase runs unattended.



      There's no traditional "console" access to an Azure VM. There's a serial console connection available, but I don't believe you can use it to configure the VM while it's in the specialize phase of Windows Setup.



      https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/use-answer-files-with-sysprep






      share|improve this answer






















        up vote
        3
        down vote










        up vote
        3
        down vote









        There's no RDP functionality during the specialize phase of Windows Setup, which is the phase you're seeing in your screenshot upon first boot of your sysprepped VM. You're going to need to use Sysprep with an answer file so that the specialize phase runs unattended.



        There's no traditional "console" access to an Azure VM. There's a serial console connection available, but I don't believe you can use it to configure the VM while it's in the specialize phase of Windows Setup.



        https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/use-answer-files-with-sysprep






        share|improve this answer












        There's no RDP functionality during the specialize phase of Windows Setup, which is the phase you're seeing in your screenshot upon first boot of your sysprepped VM. You're going to need to use Sysprep with an answer file so that the specialize phase runs unattended.



        There's no traditional "console" access to an Azure VM. There's a serial console connection available, but I don't believe you can use it to configure the VM while it's in the specialize phase of Windows Setup.



        https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/use-answer-files-with-sysprep







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered 22 hours ago









        joeqwerty

        94.3k362147




        94.3k362147






















            up vote
            2
            down vote













            You must have missed the step in the process to convert VHD to and Azure Image before deploying. Below is a link to the process.



            https://docs.microsoft.com/en-us/azure/virtual-machines/windows/upload-generalized-managed#generalize-the-source-vm-by-using-sysprep



            At this point you will have to delete VM and disk. Upload sysprep VHD again, this time convert to image then deploy from image.



            Easiest and fastest way to fix issue.






            share|improve this answer




















            • This is true, I missed that step, I actually took the VHD and converted it to a managed disk, and then an imjage,
              – Jon
              19 hours ago










            • However I attempted the steps as per the article, created an image from the generalized VHD, and then and created a VM from the image, which still had a similar problem (wouldn't boot up) ... as per this img imgur.com/tkvpR2C
              – Jon
              19 hours ago










            • actually, the VM resolved itself automatically (after a while) and now I can log on. (Following the steps mentioned above in that article)
              – Jon
              19 hours ago















            up vote
            2
            down vote













            You must have missed the step in the process to convert VHD to and Azure Image before deploying. Below is a link to the process.



            https://docs.microsoft.com/en-us/azure/virtual-machines/windows/upload-generalized-managed#generalize-the-source-vm-by-using-sysprep



            At this point you will have to delete VM and disk. Upload sysprep VHD again, this time convert to image then deploy from image.



            Easiest and fastest way to fix issue.






            share|improve this answer




















            • This is true, I missed that step, I actually took the VHD and converted it to a managed disk, and then an imjage,
              – Jon
              19 hours ago










            • However I attempted the steps as per the article, created an image from the generalized VHD, and then and created a VM from the image, which still had a similar problem (wouldn't boot up) ... as per this img imgur.com/tkvpR2C
              – Jon
              19 hours ago










            • actually, the VM resolved itself automatically (after a while) and now I can log on. (Following the steps mentioned above in that article)
              – Jon
              19 hours ago













            up vote
            2
            down vote










            up vote
            2
            down vote









            You must have missed the step in the process to convert VHD to and Azure Image before deploying. Below is a link to the process.



            https://docs.microsoft.com/en-us/azure/virtual-machines/windows/upload-generalized-managed#generalize-the-source-vm-by-using-sysprep



            At this point you will have to delete VM and disk. Upload sysprep VHD again, this time convert to image then deploy from image.



            Easiest and fastest way to fix issue.






            share|improve this answer












            You must have missed the step in the process to convert VHD to and Azure Image before deploying. Below is a link to the process.



            https://docs.microsoft.com/en-us/azure/virtual-machines/windows/upload-generalized-managed#generalize-the-source-vm-by-using-sysprep



            At this point you will have to delete VM and disk. Upload sysprep VHD again, this time convert to image then deploy from image.



            Easiest and fastest way to fix issue.







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered 21 hours ago









            Hannel

            2464




            2464











            • This is true, I missed that step, I actually took the VHD and converted it to a managed disk, and then an imjage,
              – Jon
              19 hours ago










            • However I attempted the steps as per the article, created an image from the generalized VHD, and then and created a VM from the image, which still had a similar problem (wouldn't boot up) ... as per this img imgur.com/tkvpR2C
              – Jon
              19 hours ago










            • actually, the VM resolved itself automatically (after a while) and now I can log on. (Following the steps mentioned above in that article)
              – Jon
              19 hours ago

















            • This is true, I missed that step, I actually took the VHD and converted it to a managed disk, and then an imjage,
              – Jon
              19 hours ago










            • However I attempted the steps as per the article, created an image from the generalized VHD, and then and created a VM from the image, which still had a similar problem (wouldn't boot up) ... as per this img imgur.com/tkvpR2C
              – Jon
              19 hours ago










            • actually, the VM resolved itself automatically (after a while) and now I can log on. (Following the steps mentioned above in that article)
              – Jon
              19 hours ago
















            This is true, I missed that step, I actually took the VHD and converted it to a managed disk, and then an imjage,
            – Jon
            19 hours ago




            This is true, I missed that step, I actually took the VHD and converted it to a managed disk, and then an imjage,
            – Jon
            19 hours ago












            However I attempted the steps as per the article, created an image from the generalized VHD, and then and created a VM from the image, which still had a similar problem (wouldn't boot up) ... as per this img imgur.com/tkvpR2C
            – Jon
            19 hours ago




            However I attempted the steps as per the article, created an image from the generalized VHD, and then and created a VM from the image, which still had a similar problem (wouldn't boot up) ... as per this img imgur.com/tkvpR2C
            – Jon
            19 hours ago












            actually, the VM resolved itself automatically (after a while) and now I can log on. (Following the steps mentioned above in that article)
            – Jon
            19 hours ago





            actually, the VM resolved itself automatically (after a while) and now I can log on. (Following the steps mentioned above in that article)
            – Jon
            19 hours ago


















             

            draft saved


            draft discarded















































             


            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f939258%2funable-to-connect-to-an-azure-vm-sysprepped-image%23new-answer', 'question_page');

            );

            Post as a guest














































































            Popular posts from this blog

            Use pre created SQLite database for Android project in kotlin

            Darth Vader #20

            Ondo