Migrated Hyper-V VM Looking for Old .ISO Path
-
@wirestyle22 said in Migrated Hyper-V VM Looking for Old .ISO Path:
s I've made this might actually be the worst. Sorry guys
Don't worry, maybe next time is us
-
What's weird to me is that MS allowed this migration to happen, left that mount in place to a non UNC location yet didn't copy the ISO over with the VM to ensure it would work once migrated.
Does MS have to do that - of course not, but should they? yeah probably. Otherwise any automated system now has to worry about this part as well.
-
@Dashrender said in Migrated Hyper-V VM Looking for Old .ISO Path:
What's weird to me is that MS allowed this migration to happen, left that mount in place to a non UNC location yet didn't copy the ISO over with the VM to ensure it would work once migrated.
Does MS have to do that - of course not, but should they? yeah probably. Otherwise any automated system now has to worry about this part as well.
It's just a path to the ISO but it doesnt check if it resolves
-
@wirestyle22 said in Migrated Hyper-V VM Looking for Old .ISO Path:
@Dashrender said in Migrated Hyper-V VM Looking for Old .ISO Path:
What's weird to me is that MS allowed this migration to happen, left that mount in place to a non UNC location yet didn't copy the ISO over with the VM to ensure it would work once migrated.
Does MS have to do that - of course not, but should they? yeah probably. Otherwise any automated system now has to worry about this part as well.
It's just a path to the ISO but it doesnt check if it resolves
But it should. That is just lazy design.
-
@DustinB3403 said in Migrated Hyper-V VM Looking for Old .ISO Path:
@wirestyle22 said in Migrated Hyper-V VM Looking for Old .ISO Path:
@Dashrender said in Migrated Hyper-V VM Looking for Old .ISO Path:
What's weird to me is that MS allowed this migration to happen, left that mount in place to a non UNC location yet didn't copy the ISO over with the VM to ensure it would work once migrated.
Does MS have to do that - of course not, but should they? yeah probably. Otherwise any automated system now has to worry about this part as well.
It's just a path to the ISO but it doesnt check if it resolves
But it should. That is just lazy design.
It might do that if you have a network share with an iso in it. In this situation it's local, so i wouldnt expect that to matter.
-
At a minimum it should throw a pop up warning.
"You have an ISO attached to this system, this process will create the mount, but won't replicate the media"
-
@DustinB3403 said in Migrated Hyper-V VM Looking for Old .ISO Path:
At a minimum it should throw a pop up warning.
"You have an ISO attached to this system, this process will create the mount, but won't replicate the media"
Yeah I agree with that. This was an easy fix though, I just derp'd
-
@wirestyle22 said in Migrated Hyper-V VM Looking for Old .ISO Path:
@DustinB3403 said in Migrated Hyper-V VM Looking for Old .ISO Path:
At a minimum it should throw a pop up warning.
"You have an ISO attached to this system, this process will create the mount, but won't replicate the media"
Yeah I agree with that. This was an easy fix though, I just derp'd
Don't feel bad, I derp all of the time. Only way to learn is by doing.
-
With non-local storage I believe it would work without issue.
-
@DustinB3403 said in Migrated Hyper-V VM Looking for Old .ISO Path:
@wirestyle22 said in Migrated Hyper-V VM Looking for Old .ISO Path:
@DustinB3403 said in Migrated Hyper-V VM Looking for Old .ISO Path:
At a minimum it should throw a pop up warning.
"You have an ISO attached to this system, this process will create the mount, but won't replicate the media"
Yeah I agree with that. This was an easy fix though, I just derp'd
Don't feel bad, I derp all of the time. Only way to learn is by doing.
This wasn't even knowledge it was just lack of attention to detail, which is especially bad for me coming from the military. My drill sergeant would be ashamed.
-
@wirestyle22 But your drill sergeant would want you on the team always so do not lose sleep over it
