Hyper-V 2008 VM System State Backup to USB
-
Exactly, I didn't set it up, and I've said I don't want to deal with these systems, yet this job keeps coming back to me.
I get limiting the MSP's hours for the job to try and save cost, but damn it they should have to clean up this mess.
Now I'm not doing anything with SP or the federated services, so if all goes smoothly (export > import) then fine. But these guys suck.
-
PS if anyone wants to know who this MSP is, PM me and I'll let you know.
-
Wait... this is a DC? Why not bring up a new DC on the XS pool and take down the old one. What benefit does moving it and potentially having it blow up have?
-
@coliver said in Hyper-V 2008 VM System State Backup to USB:
Wait... this is a DC? Why not bring up a new DC on the XS pool and take down the old one. What benefit does moving it and potentially having it blow up have?
Simply put we don't have any licensing available to do this, and the MSP is being a little bitch about it.
-
@DustinB3403 said in Hyper-V 2008 VM System State Backup to USB:
This VM is running federated services for o365 as well... so yeah... that's probably why they don't want to touch it again.
More of their mess.
Ouch, we normally recommend not federating with O365 unless there is just no other option, just makes everything so fragile.
-
Are you doing SSO or just password syncing with O365?
-
@coliver SSO...
-
@DustinB3403 said in Hyper-V 2008 VM System State Backup to USB:
@coliver SSO...
There is only one server for SSO? Did those recommendations change recently? In the past Microsoft has recommended 4 servers to accommodate SSO with O365. They are doing it on a DC! That's against best practices and can cause a few non-trivial issues.
-
@coliver said in Hyper-V 2008 VM System State Backup to USB:
@DustinB3403 said in Hyper-V 2008 VM System State Backup to USB:
@coliver SSO...
There is only one server for SSO? Did those recommendations change recently? In the past Microsoft has recommended 4 servers to accommodate SSO with O365. They are doing it on a DC! That's against best practices and can cause a few non-trivial issues.
My understanding is that three servers is fine. Two DCs and one sync/fed server. But four is better.
-
@coliver I know, I wasn't even included in the conversation at the time when we migrated to O365, and I wasn't included in the conversation when they setup Hyper-V.
Nor was I included when they built this VM, or the other reporting VM on Hyper-V to which 16GB of memory and 2 cores assigned to it...
#SweepItLikeAJanitor
