Exporting a DC/Exchange VM from Hyper-V 2008
-
@JaredBusch said in Exporting a DC/Exchange VM from Hyper-V 2008:
@travisdh1 said in Exporting a DC/Exchange VM from Hyper-V 2008:
@DustinB3403 What's that quote? "Not my circus, not my problem."?
Besides, no email server should loose any email by not being available for an entire day, let alone 6-12 hours. Email is not instant!
Technically, if an email server is offline when a remote server tries to send email to it, that email is never sent and it completely depends on the sending server settings on what happens.
Now, that said, I do not know any email server that does not retry for at least 6 hours by default.
Exactly. In theory an email server could be set not to retry or only to do so for a minute or so. But I've never heard of anyone doing that.
-
@travisdh1 said in Exporting a DC/Exchange VM from Hyper-V 2008:
@DustinB3403 What's that quote? "Not my circus, not my problem."?
You tried it their way, and were proven correct. Besides, no email server should loose any email by not being available for an entire day, let alone 6-12 hours. Email is not instant! If you want instant, you need a different communication channel.
That was my point as well, the concern being that "we" would lose the ability to send / receive sales emails from clients was the original driver for trying approach 1 and 2.
Email being hosted by Microsoft means we should in theory not even need a local exchange server, but we have federated services for SSO.
-
@DustinB3403 said in Exporting a DC/Exchange VM from Hyper-V 2008:
@travisdh1 said in Exporting a DC/Exchange VM from Hyper-V 2008:
@DustinB3403 What's that quote? "Not my circus, not my problem."?
You tried it their way, and were proven correct. Besides, no email server should loose any email by not being available for an entire day, let alone 6-12 hours. Email is not instant! If you want instant, you need a different communication channel.
That was my point as well, the concern being that "we" would lose the ability to send / receive sales emails from clients was the original driver for trying approach 1 and 2.
Email being hosted by Microsoft means we should in theory not even need a local exchange server, but we have federated services for SSO.
If you have Federated services already in place then that makes it ridiculously easy to do SSO with Office 365.
-
@coliver said in Exporting a DC/Exchange VM from Hyper-V 2008:
@DustinB3403 said in Exporting a DC/Exchange VM from Hyper-V 2008:
@travisdh1 said in Exporting a DC/Exchange VM from Hyper-V 2008:
@DustinB3403 What's that quote? "Not my circus, not my problem."?
You tried it their way, and were proven correct. Besides, no email server should loose any email by not being available for an entire day, let alone 6-12 hours. Email is not instant! If you want instant, you need a different communication channel.
That was my point as well, the concern being that "we" would lose the ability to send / receive sales emails from clients was the original driver for trying approach 1 and 2.
Email being hosted by Microsoft means we should in theory not even need a local exchange server, but we have federated services for SSO.
If you have Federated services already in place then that makes it ridiculously easy to do SSO with Office 365.
Yet we're hosting half, and microsoft the other half. And we still have On-site Exchange (when we have an O365 account, and all email is hosted with MS)....
So many things that are setup oddly.
-
@DustinB3403 said in Exporting a DC/Exchange VM from Hyper-V 2008:
@coliver said in Exporting a DC/Exchange VM from Hyper-V 2008:
@DustinB3403 said in Exporting a DC/Exchange VM from Hyper-V 2008:
@travisdh1 said in Exporting a DC/Exchange VM from Hyper-V 2008:
@DustinB3403 What's that quote? "Not my circus, not my problem."?
You tried it their way, and were proven correct. Besides, no email server should loose any email by not being available for an entire day, let alone 6-12 hours. Email is not instant! If you want instant, you need a different communication channel.
That was my point as well, the concern being that "we" would lose the ability to send / receive sales emails from clients was the original driver for trying approach 1 and 2.
Email being hosted by Microsoft means we should in theory not even need a local exchange server, but we have federated services for SSO.
If you have Federated services already in place then that makes it ridiculously easy to do SSO with Office 365.
Yet we're hosting half, and microsoft the other half. And we still have On-site Exchange (when we have an O365 account, and all email is hosted with MS)....
So many things that are setup oddly.
That's really odd... Is all the mail hosted with Exchange Online? Maybe you have some hybrid accounts? Or they are using the Exchange server as a mail gateways?
-
@coliver said in Exporting a DC/Exchange VM from Hyper-V 2008:
@DustinB3403 said in Exporting a DC/Exchange VM from Hyper-V 2008:
@coliver said in Exporting a DC/Exchange VM from Hyper-V 2008:
@DustinB3403 said in Exporting a DC/Exchange VM from Hyper-V 2008:
@travisdh1 said in Exporting a DC/Exchange VM from Hyper-V 2008:
@DustinB3403 What's that quote? "Not my circus, not my problem."?
You tried it their way, and were proven correct. Besides, no email server should loose any email by not being available for an entire day, let alone 6-12 hours. Email is not instant! If you want instant, you need a different communication channel.
That was my point as well, the concern being that "we" would lose the ability to send / receive sales emails from clients was the original driver for trying approach 1 and 2.
Email being hosted by Microsoft means we should in theory not even need a local exchange server, but we have federated services for SSO.
If you have Federated services already in place then that makes it ridiculously easy to do SSO with Office 365.
Yet we're hosting half, and microsoft the other half. And we still have On-site Exchange (when we have an O365 account, and all email is hosted with MS)....
So many things that are setup oddly.
That's really odd... Is all the mail hosted with Exchange Online? Maybe you have some hybrid accounts? Or they are using the Exchange server as a mail gateways?
All of our domain accounts are setup onsite, and migrated to Exchange Online. For OWA access all request are forward back to our on-site server for AD authentication....
. . . .
-
@DustinB3403 said in Exporting a DC/Exchange VM from Hyper-V 2008:
@coliver said in Exporting a DC/Exchange VM from Hyper-V 2008:
@DustinB3403 said in Exporting a DC/Exchange VM from Hyper-V 2008:
@coliver said in Exporting a DC/Exchange VM from Hyper-V 2008:
@DustinB3403 said in Exporting a DC/Exchange VM from Hyper-V 2008:
@travisdh1 said in Exporting a DC/Exchange VM from Hyper-V 2008:
@DustinB3403 What's that quote? "Not my circus, not my problem."?
You tried it their way, and were proven correct. Besides, no email server should loose any email by not being available for an entire day, let alone 6-12 hours. Email is not instant! If you want instant, you need a different communication channel.
That was my point as well, the concern being that "we" would lose the ability to send / receive sales emails from clients was the original driver for trying approach 1 and 2.
Email being hosted by Microsoft means we should in theory not even need a local exchange server, but we have federated services for SSO.
If you have Federated services already in place then that makes it ridiculously easy to do SSO with Office 365.
Yet we're hosting half, and microsoft the other half. And we still have On-site Exchange (when we have an O365 account, and all email is hosted with MS)....
So many things that are setup oddly.
That's really odd... Is all the mail hosted with Exchange Online? Maybe you have some hybrid accounts? Or they are using the Exchange server as a mail gateways?
All of our domain accounts are setup onsite, and migrated to Exchange Online. For OWA access all request are forward back to our on-site server for AD authentication....
. . . .
Right, that's what you do with ADFS, you host the authoritative server for your domain. Just odd you need an onsite exchange server at all.
-
@coliver said in Exporting a DC/Exchange VM from Hyper-V 2008:
@DustinB3403 said in Exporting a DC/Exchange VM from Hyper-V 2008:
@coliver said in Exporting a DC/Exchange VM from Hyper-V 2008:
@DustinB3403 said in Exporting a DC/Exchange VM from Hyper-V 2008:
@coliver said in Exporting a DC/Exchange VM from Hyper-V 2008:
@DustinB3403 said in Exporting a DC/Exchange VM from Hyper-V 2008:
@travisdh1 said in Exporting a DC/Exchange VM from Hyper-V 2008:
@DustinB3403 What's that quote? "Not my circus, not my problem."?
You tried it their way, and were proven correct. Besides, no email server should loose any email by not being available for an entire day, let alone 6-12 hours. Email is not instant! If you want instant, you need a different communication channel.
That was my point as well, the concern being that "we" would lose the ability to send / receive sales emails from clients was the original driver for trying approach 1 and 2.
Email being hosted by Microsoft means we should in theory not even need a local exchange server, but we have federated services for SSO.
If you have Federated services already in place then that makes it ridiculously easy to do SSO with Office 365.
Yet we're hosting half, and microsoft the other half. And we still have On-site Exchange (when we have an O365 account, and all email is hosted with MS)....
So many things that are setup oddly.
That's really odd... Is all the mail hosted with Exchange Online? Maybe you have some hybrid accounts? Or they are using the Exchange server as a mail gateways?
All of our domain accounts are setup onsite, and migrated to Exchange Online. For OWA access all request are forward back to our on-site server for AD authentication....
. . . .
Right, that's what you do with ADFS, you host the authoritative server for your domain. Just odd you need an onsite exchange server at all.
My point is, if we have hosted exchange, why do we need to redirect everyone to an internal server, and then back to Exchange Online..
Seems backwards.
Let people authenticate directly to Exchange online. This hybrid setup just makes things complicated for no gain.
-
@DustinB3403 said in Exporting a DC/Exchange VM from Hyper-V 2008:
@coliver said in Exporting a DC/Exchange VM from Hyper-V 2008:
@DustinB3403 said in Exporting a DC/Exchange VM from Hyper-V 2008:
@coliver said in Exporting a DC/Exchange VM from Hyper-V 2008:
@DustinB3403 said in Exporting a DC/Exchange VM from Hyper-V 2008:
@coliver said in Exporting a DC/Exchange VM from Hyper-V 2008:
@DustinB3403 said in Exporting a DC/Exchange VM from Hyper-V 2008:
@travisdh1 said in Exporting a DC/Exchange VM from Hyper-V 2008:
@DustinB3403 What's that quote? "Not my circus, not my problem."?
You tried it their way, and were proven correct. Besides, no email server should loose any email by not being available for an entire day, let alone 6-12 hours. Email is not instant! If you want instant, you need a different communication channel.
That was my point as well, the concern being that "we" would lose the ability to send / receive sales emails from clients was the original driver for trying approach 1 and 2.
Email being hosted by Microsoft means we should in theory not even need a local exchange server, but we have federated services for SSO.
If you have Federated services already in place then that makes it ridiculously easy to do SSO with Office 365.
Yet we're hosting half, and microsoft the other half. And we still have On-site Exchange (when we have an O365 account, and all email is hosted with MS)....
So many things that are setup oddly.
That's really odd... Is all the mail hosted with Exchange Online? Maybe you have some hybrid accounts? Or they are using the Exchange server as a mail gateways?
All of our domain accounts are setup onsite, and migrated to Exchange Online. For OWA access all request are forward back to our on-site server for AD authentication....
. . . .
Right, that's what you do with ADFS, you host the authoritative server for your domain. Just odd you need an onsite exchange server at all.
My point is, if we have hosted exchange, why do we need to redirect everyone to an internal server, and then back to Exchange Online..
Seems backwards.
Let people authenticate directly to Exchange online. This hybrid setup just makes things complicated for no gain.
For SSO, but you don't need onsite exchange to accomplish that.
-
@coliver said in Exporting a DC/Exchange VM from Hyper-V 2008:
@DustinB3403 said in Exporting a DC/Exchange VM from Hyper-V 2008:
@coliver said in Exporting a DC/Exchange VM from Hyper-V 2008:
@DustinB3403 said in Exporting a DC/Exchange VM from Hyper-V 2008:
@coliver said in Exporting a DC/Exchange VM from Hyper-V 2008:
@DustinB3403 said in Exporting a DC/Exchange VM from Hyper-V 2008:
@coliver said in Exporting a DC/Exchange VM from Hyper-V 2008:
@DustinB3403 said in Exporting a DC/Exchange VM from Hyper-V 2008:
@travisdh1 said in Exporting a DC/Exchange VM from Hyper-V 2008:
@DustinB3403 What's that quote? "Not my circus, not my problem."?
You tried it their way, and were proven correct. Besides, no email server should loose any email by not being available for an entire day, let alone 6-12 hours. Email is not instant! If you want instant, you need a different communication channel.
That was my point as well, the concern being that "we" would lose the ability to send / receive sales emails from clients was the original driver for trying approach 1 and 2.
Email being hosted by Microsoft means we should in theory not even need a local exchange server, but we have federated services for SSO.
If you have Federated services already in place then that makes it ridiculously easy to do SSO with Office 365.
Yet we're hosting half, and microsoft the other half. And we still have On-site Exchange (when we have an O365 account, and all email is hosted with MS)....
So many things that are setup oddly.
That's really odd... Is all the mail hosted with Exchange Online? Maybe you have some hybrid accounts? Or they are using the Exchange server as a mail gateways?
All of our domain accounts are setup onsite, and migrated to Exchange Online. For OWA access all request are forward back to our on-site server for AD authentication....
. . . .
Right, that's what you do with ADFS, you host the authoritative server for your domain. Just odd you need an onsite exchange server at all.
My point is, if we have hosted exchange, why do we need to redirect everyone to an internal server, and then back to Exchange Online..
Seems backwards.
Let people authenticate directly to Exchange online. This hybrid setup just makes things complicated for no gain.
For SSO, but you don't need onsite exchange to accomplish that.
I know
-
@DustinB3403 said in Exporting a DC/Exchange VM from Hyper-V 2008:
@coliver said in Exporting a DC/Exchange VM from Hyper-V 2008:
@DustinB3403 said in Exporting a DC/Exchange VM from Hyper-V 2008:
@coliver said in Exporting a DC/Exchange VM from Hyper-V 2008:
@DustinB3403 said in Exporting a DC/Exchange VM from Hyper-V 2008:
@coliver said in Exporting a DC/Exchange VM from Hyper-V 2008:
@DustinB3403 said in Exporting a DC/Exchange VM from Hyper-V 2008:
@coliver said in Exporting a DC/Exchange VM from Hyper-V 2008:
@DustinB3403 said in Exporting a DC/Exchange VM from Hyper-V 2008:
@travisdh1 said in Exporting a DC/Exchange VM from Hyper-V 2008:
@DustinB3403 What's that quote? "Not my circus, not my problem."?
You tried it their way, and were proven correct. Besides, no email server should loose any email by not being available for an entire day, let alone 6-12 hours. Email is not instant! If you want instant, you need a different communication channel.
That was my point as well, the concern being that "we" would lose the ability to send / receive sales emails from clients was the original driver for trying approach 1 and 2.
Email being hosted by Microsoft means we should in theory not even need a local exchange server, but we have federated services for SSO.
If you have Federated services already in place then that makes it ridiculously easy to do SSO with Office 365.
Yet we're hosting half, and microsoft the other half. And we still have On-site Exchange (when we have an O365 account, and all email is hosted with MS)....
So many things that are setup oddly.
That's really odd... Is all the mail hosted with Exchange Online? Maybe you have some hybrid accounts? Or they are using the Exchange server as a mail gateways?
All of our domain accounts are setup onsite, and migrated to Exchange Online. For OWA access all request are forward back to our on-site server for AD authentication....
. . . .
Right, that's what you do with ADFS, you host the authoritative server for your domain. Just odd you need an onsite exchange server at all.
My point is, if we have hosted exchange, why do we need to redirect everyone to an internal server, and then back to Exchange Online..
Seems backwards.
Let people authenticate directly to Exchange online. This hybrid setup just makes things complicated for no gain.
For SSO, but you don't need onsite exchange to accomplish that.
I know
So really the question is why do you have onsite exchange setup in a hybrid environment? There must be a reason.
-
@coliver said in Exporting a DC/Exchange VM from Hyper-V 2008:
@DustinB3403 said in Exporting a DC/Exchange VM from Hyper-V 2008:
@coliver said in Exporting a DC/Exchange VM from Hyper-V 2008:
@DustinB3403 said in Exporting a DC/Exchange VM from Hyper-V 2008:
@coliver said in Exporting a DC/Exchange VM from Hyper-V 2008:
@DustinB3403 said in Exporting a DC/Exchange VM from Hyper-V 2008:
@coliver said in Exporting a DC/Exchange VM from Hyper-V 2008:
@DustinB3403 said in Exporting a DC/Exchange VM from Hyper-V 2008:
@coliver said in Exporting a DC/Exchange VM from Hyper-V 2008:
@DustinB3403 said in Exporting a DC/Exchange VM from Hyper-V 2008:
@travisdh1 said in Exporting a DC/Exchange VM from Hyper-V 2008:
@DustinB3403 What's that quote? "Not my circus, not my problem."?
You tried it their way, and were proven correct. Besides, no email server should loose any email by not being available for an entire day, let alone 6-12 hours. Email is not instant! If you want instant, you need a different communication channel.
That was my point as well, the concern being that "we" would lose the ability to send / receive sales emails from clients was the original driver for trying approach 1 and 2.
Email being hosted by Microsoft means we should in theory not even need a local exchange server, but we have federated services for SSO.
If you have Federated services already in place then that makes it ridiculously easy to do SSO with Office 365.
Yet we're hosting half, and microsoft the other half. And we still have On-site Exchange (when we have an O365 account, and all email is hosted with MS)....
So many things that are setup oddly.
That's really odd... Is all the mail hosted with Exchange Online? Maybe you have some hybrid accounts? Or they are using the Exchange server as a mail gateways?
All of our domain accounts are setup onsite, and migrated to Exchange Online. For OWA access all request are forward back to our on-site server for AD authentication....
. . . .
Right, that's what you do with ADFS, you host the authoritative server for your domain. Just odd you need an onsite exchange server at all.
My point is, if we have hosted exchange, why do we need to redirect everyone to an internal server, and then back to Exchange Online..
Seems backwards.
Let people authenticate directly to Exchange online. This hybrid setup just makes things complicated for no gain.
For SSO, but you don't need onsite exchange to accomplish that.
I know
So really the question is why do you have onsite exchange setup in a hybrid environment? There must be a reason.
That I do not know. I honestly don't understand why a hybrid environment was decided for.
-
@DustinB3403 said in Exporting a DC/Exchange VM from Hyper-V 2008:
@coliver said in Exporting a DC/Exchange VM from Hyper-V 2008:
@DustinB3403 said in Exporting a DC/Exchange VM from Hyper-V 2008:
@coliver said in Exporting a DC/Exchange VM from Hyper-V 2008:
@DustinB3403 said in Exporting a DC/Exchange VM from Hyper-V 2008:
@coliver said in Exporting a DC/Exchange VM from Hyper-V 2008:
@DustinB3403 said in Exporting a DC/Exchange VM from Hyper-V 2008:
@coliver said in Exporting a DC/Exchange VM from Hyper-V 2008:
@DustinB3403 said in Exporting a DC/Exchange VM from Hyper-V 2008:
@coliver said in Exporting a DC/Exchange VM from Hyper-V 2008:
@DustinB3403 said in Exporting a DC/Exchange VM from Hyper-V 2008:
@travisdh1 said in Exporting a DC/Exchange VM from Hyper-V 2008:
@DustinB3403 What's that quote? "Not my circus, not my problem."?
You tried it their way, and were proven correct. Besides, no email server should loose any email by not being available for an entire day, let alone 6-12 hours. Email is not instant! If you want instant, you need a different communication channel.
That was my point as well, the concern being that "we" would lose the ability to send / receive sales emails from clients was the original driver for trying approach 1 and 2.
Email being hosted by Microsoft means we should in theory not even need a local exchange server, but we have federated services for SSO.
If you have Federated services already in place then that makes it ridiculously easy to do SSO with Office 365.
Yet we're hosting half, and microsoft the other half. And we still have On-site Exchange (when we have an O365 account, and all email is hosted with MS)....
So many things that are setup oddly.
That's really odd... Is all the mail hosted with Exchange Online? Maybe you have some hybrid accounts? Or they are using the Exchange server as a mail gateways?
All of our domain accounts are setup onsite, and migrated to Exchange Online. For OWA access all request are forward back to our on-site server for AD authentication....
. . . .
Right, that's what you do with ADFS, you host the authoritative server for your domain. Just odd you need an onsite exchange server at all.
My point is, if we have hosted exchange, why do we need to redirect everyone to an internal server, and then back to Exchange Online..
Seems backwards.
Let people authenticate directly to Exchange online. This hybrid setup just makes things complicated for no gain.
For SSO, but you don't need onsite exchange to accomplish that.
I know
So really the question is why do you have onsite exchange setup in a hybrid environment? There must be a reason.
That I do not know. I honestly don't understand why a hybrid environment was decided for.
May be worth investigating. It may be there for a good reasons, or it may be something silly like locally hosted calendars (don't ask) that they think can't be moved to Exchange Online.
-
Kind of in the same boat here with the hybrid deployment. Last IT guy coudlnt figure out why the network and servers were becoming unavailable multiple times a day(dude worked here for 1.5 years, didnt do a thing as far as i can tell). So he decided to go O365 and Exchange Online. He paid the money for exchange online, got a hybrid deployment setup, then didnt work here anymore. Didnt migrate anybody to use Exchange Online.
I was then hired, i fixed all the local network issues.
Our Exchange online sub expires next week, really trying to decide whether to renew this sub or not. It is a few thousand dollars to renew. Just doesnt seem worth it since Exchange is locally running without issues. -
@momurda said in Exporting a DC/Exchange VM from Hyper-V 2008:
Kind of in the same boat here with the hybrid deployment. Last IT guy coudlnt figure out why the network and servers were becoming unavailable multiple times a day(dude worked here for 1.5 years, didnt do a thing as far as i can tell). So he decided to go O365 and Exchange Online. He paid the money for exchange online, got a hybrid deployment setup, then didnt work here anymore. Didnt migrate anybody to use Exchange Online.
I was then hired, i fixed all the local network issues.
Our Exchange online sub expires next week, really trying to decide whether to renew this sub or not. It is a few thousand dollars to renew. Just doesnt seem worth it since Exchange is locally running without issues.It could free up the resources that your exchange server is taking up for other things.
-
@momurda said in Exporting a DC/Exchange VM from Hyper-V 2008:
Kind of in the same boat here with the hybrid deployment. Last IT guy coudlnt figure out why the network and servers were becoming unavailable multiple times a day(dude worked here for 1.5 years, didnt do a thing as far as i can tell). So he decided to go O365 and Exchange Online. He paid the money for exchange online, got a hybrid deployment setup, then didnt work here anymore. Didnt migrate anybody to use Exchange Online.
I was then hired, i fixed all the local network issues.
Our Exchange online sub expires next week, really trying to decide whether to renew this sub or not. It is a few thousand dollars to renew. Just doesnt seem worth it since Exchange is locally running without issues.Think about the fact that you need to perform hardware refreshes on that server now where as with hosted exchange it's a flat rate, normalizing costs for you.
-
And patch management and software updates are taken care of for you.
