Mixing
Unable to connect to an Azure VM (sysprepped image)
Clash Royale CLAN TAG#URR8PPP
up vote
1
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.
azure sysprep
asked 2 hours ago
Jon
61
add a comment |Â
up vote
1
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.
azure sysprep
asked 2 hours ago
Jon
61
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♦
2 hours ago
Hi Michael, can you elaborate on your solution? What does booting into audit mode do?
– Jon
2 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♦
2 hours ago
add a comment |Â
up vote
1
down vote
favorite
up vote
1
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.
azure sysprep
asked 2 hours ago
Jon
61
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
azure sysprep
asked 2 hours ago
Jon
61
asked 2 hours ago
Jon
61
asked 2 hours ago
Jon
61
asked 2 hours ago
Jon
61
asked 2 hours ago
Jon
61
61
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♦
2 hours ago
Hi Michael, can you elaborate on your solution? What does booting into audit mode do?
– Jon
2 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♦
2 hours ago
add a comment |Â
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♦
2 hours ago
Hi Michael, can you elaborate on your solution? What does booting into audit mode do?
– Jon
2 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♦
2 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♦
2 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♦
2 hours ago
Hi Michael, can you elaborate on your solution? What does booting into audit mode do?
– Jon
2 hours ago
Hi Michael, can you elaborate on your solution? What does booting into audit mode do?
– Jon
2 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♦
2 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♦
2 hours ago
add a comment |Â
2 Answers
2
active
oldest
votes
up vote
2
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
answered 1 hour ago
joeqwerty
94.3k362147
add a comment |Â
up vote
1
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.
answered 48 mins ago
Hannel
2164
add a comment |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
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
answered 1 hour ago
joeqwerty
94.3k362147
add a comment |Â
up vote
2
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
answered 1 hour ago
joeqwerty
94.3k362147
add a comment |Â
up vote
2
down vote
up vote
2
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
answered 1 hour ago
joeqwerty
94.3k362147
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
answered 1 hour ago
joeqwerty
94.3k362147
answered 1 hour ago
joeqwerty
94.3k362147
answered 1 hour ago
joeqwerty
94.3k362147
answered 1 hour ago
joeqwerty
94.3k362147
94.3k362147
add a comment |Â
add a comment |Â
up vote
1
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.
answered 48 mins ago
Hannel
2164
add a comment |Â
up vote
1
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.
answered 48 mins ago
Hannel
2164
add a comment |Â
up vote
1
down vote
up vote
1
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.
answered 48 mins ago
Hannel
2164
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.
answered 48 mins ago
Hannel
2164
answered 48 mins ago
Hannel
2164
answered 48 mins ago
Hannel
2164
answered 48 mins ago
Hannel
2164
2164
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
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
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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♦
2 hours ago
Hi Michael, can you elaborate on your solution? What does booting into audit mode do?
– Jon
2 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♦
2 hours ago