Office 365 Email Gone After Forced Logoff
-
@tim_g said in Office 365 Email Gone After Forced Logoff:
@wls-itguy said in Office 365 Email Gone After Forced Logoff:
We had a corporate meeting yesterday and they keep suggesting that we move from our in house exchange system to O365. NO CHANCE IN HELL! For this exact reason.
on-prem exchange... no reason for it whatsoever...
I'm willing to bet it's not up to date.
It is up to date. Also, cost effective is the reason. 3 year life cycle comparison $6600 vs $500. Who would think that hosted/O365 is the better option, EVER!?
Oh, and my shit doesn't disappear randomly every time MS decides to make some jacked up change to its system.
-
@wls-itguy said in Office 365 Email Gone After Forced Logoff:
@tim_g said in Office 365 Email Gone After Forced Logoff:
@wls-itguy said in Office 365 Email Gone After Forced Logoff:
We had a corporate meeting yesterday and they keep suggesting that we move from our in house exchange system to O365. NO CHANCE IN HELL! For this exact reason.
on-prem exchange... no reason for it whatsoever...
I'm willing to bet it's not up to date.
It is up to date. Also, cost effective is the reason. 3 year life cycle comparison $6600 vs $500. Who would think that hosted/O365 is the better option, EVER!?
Oh, and my shit doesn't disappear randomly every time MS decides to make some jacked up change to its system.
How many users and how much data?
-
@tim_g said in Office 365 Email Gone After Forced Logoff:
@wls-itguy said in Office 365 Email Gone After Forced Logoff:
@tim_g said in Office 365 Email Gone After Forced Logoff:
@wls-itguy said in Office 365 Email Gone After Forced Logoff:
We had a corporate meeting yesterday and they keep suggesting that we move from our in house exchange system to O365. NO CHANCE IN HELL! For this exact reason.
on-prem exchange... no reason for it whatsoever...
I'm willing to bet it's not up to date.
It is up to date. Also, cost effective is the reason. 3 year life cycle comparison $6600 vs $500. Who would think that hosted/O365 is the better option, EVER!?
Oh, and my shit doesn't disappear randomly every time MS decides to make some jacked up change to its system.
How many users and how much data?
160 active users and right now about 1.2TB Licensed for 251 users.
-
@wls-itguy said in Office 365 Email Gone After Forced Logoff:
@tim_g said in Office 365 Email Gone After Forced Logoff:
@wls-itguy said in Office 365 Email Gone After Forced Logoff:
@tim_g said in Office 365 Email Gone After Forced Logoff:
@wls-itguy said in Office 365 Email Gone After Forced Logoff:
We had a corporate meeting yesterday and they keep suggesting that we move from our in house exchange system to O365. NO CHANCE IN HELL! For this exact reason.
on-prem exchange... no reason for it whatsoever...
I'm willing to bet it's not up to date.
It is up to date. Also, cost effective is the reason. 3 year life cycle comparison $6600 vs $500. Who would think that hosted/O365 is the better option, EVER!?
Oh, and my shit doesn't disappear randomly every time MS decides to make some jacked up change to its system.
How many users and how much data?
160 active users and right now about 1.2TB Licensed for 251 users.
Exchange 2016? Free hardware? Electricity? Maintenance? Free SW upgrades? Free CAL upgrades? Does it include the Office Suite or does nobody use Office and just use your on-prem Exchange OWA?
We NEVER had stuff disappear randomly, not sure what that's about, someone messing with their licensing maybe... we manage our own licensing though.
-
@wls-itguy said in Office 365 Email Gone After Forced Logoff:
So the discount we get for being a 501c3
Just seen this...
-
@tim_g said in Office 365 Email Gone After Forced Logoff:
We NEVER had stuff disappear randomly, not sure what that's about, someone messing with their licensing maybe... we manage our own licensing though.
So do we, that's often the issue. MS messes with it.
-
@tim_g said in Office 365 Email Gone After Forced Logoff:
@wls-itguy said in Office 365 Email Gone After Forced Logoff:
@tim_g said in Office 365 Email Gone After Forced Logoff:
@wls-itguy said in Office 365 Email Gone After Forced Logoff:
@tim_g said in Office 365 Email Gone After Forced Logoff:
@wls-itguy said in Office 365 Email Gone After Forced Logoff:
We had a corporate meeting yesterday and they keep suggesting that we move from our in house exchange system to O365. NO CHANCE IN HELL! For this exact reason.
on-prem exchange... no reason for it whatsoever...
I'm willing to bet it's not up to date.
It is up to date. Also, cost effective is the reason. 3 year life cycle comparison $6600 vs $500. Who would think that hosted/O365 is the better option, EVER!?
Oh, and my shit doesn't disappear randomly every time MS decides to make some jacked up change to its system.
How many users and how much data?
160 active users and right now about 1.2TB Licensed for 251 users.
Exchange 2016? Free hardware? Electricity? Maintenance? Free SW upgrades? Free CAL upgrades? Does it include the Office Suite or does nobody use Office and just use your on-prem Exchange OWA?
We NEVER had stuff disappear randomly, not sure what that's about, someone messing with their licensing maybe... we manage our own licensing though.
Yes, exchange 2016. Sure there is all those costs but we have servers for other things on campus (File servers, door locking system, etc) so that is already a purchased cost. The digital footprint from the 30TB SAN isn't anything. We buy Office 365 University at $80/4 year subscription for the Faculty and Staff. Students can buy it on their own. And what I use in electricity with a 3 server cluster and a SAN compared to what was used 6 years ago when I got here is chump change.
-
@scottalanmiller said in Office 365 Email Gone After Forced Logoff:
@jaredbusch said in Office 365 Email Gone After Forced Logoff:
As I recall, your O365 accounts were tied to some AD sync server.
This is all the fault of whoever set tings up and never properly disconnected stuff.
Microsoft themselves set that up without permission.
Let's say that I know that's not the case, for very specific reasons you should know already.
MS never sets up your stuff. Especially with AD Sync, considering it has to be installed locally.
-
@psx_defector said in Office 365 Email Gone After Forced Logoff:
MS never sets up your stuff. Especially with AD Sync, considering it has to be installed locally.
MS concierge did it himself. That would be Greg. And yes, it was done locally, without permission. In fact, he was explicitly forbidden to do so.
-
@psx_defector said in Office 365 Email Gone After Forced Logoff:
@scottalanmiller said in Office 365 Email Gone After Forced Logoff:
@jaredbusch said in Office 365 Email Gone After Forced Logoff:
As I recall, your O365 accounts were tied to some AD sync server.
This is all the fault of whoever set tings up and never properly disconnected stuff.
Microsoft themselves set that up without permission.
Let's say that I know that's not the case, for very specific reasons you should know already.
MS never sets up your stuff. Especially with AD Sync, considering it has to be installed locally.
We use AD Sync for O365, and that has nothing to do with licensing.
If I create a new AD user, it gets synced to O365, but is unlicensed until I go in and manually assign an E1 or E3 license.
It's like that by default, and I want to keep it that way... so I don't know if there's a way to assign those licenses on-prem or not. I don't want anything automatically assigned.
-
This is why you don't want old employees getting picked up by MS. Overstepping bounds is a problem.
-
@tim_g said in Office 365 Email Gone After Forced Logoff:
@psx_defector said in Office 365 Email Gone After Forced Logoff:
@scottalanmiller said in Office 365 Email Gone After Forced Logoff:
@jaredbusch said in Office 365 Email Gone After Forced Logoff:
As I recall, your O365 accounts were tied to some AD sync server.
This is all the fault of whoever set tings up and never properly disconnected stuff.
Microsoft themselves set that up without permission.
Let's say that I know that's not the case, for very specific reasons you should know already.
MS never sets up your stuff. Especially with AD Sync, considering it has to be installed locally.
We use AD Sync for O365, and that has nothing to do with licensing.
It's someone bringing up major issues in the past. We used MS concierge service because we knew the people because it was an old employee who, through SW, got invited to work for MS. They did a bunch of stuff they weren't supposed to do and caused a lot of problems.
-
@scottalanmiller said in Office 365 Email Gone After Forced Logoff:
@tim_g said in Office 365 Email Gone After Forced Logoff:
@psx_defector said in Office 365 Email Gone After Forced Logoff:
@scottalanmiller said in Office 365 Email Gone After Forced Logoff:
@jaredbusch said in Office 365 Email Gone After Forced Logoff:
As I recall, your O365 accounts were tied to some AD sync server.
This is all the fault of whoever set tings up and never properly disconnected stuff.
Microsoft themselves set that up without permission.
Let's say that I know that's not the case, for very specific reasons you should know already.
MS never sets up your stuff. Especially with AD Sync, considering it has to be installed locally.
We use AD Sync for O365, and that has nothing to do with licensing.
It's someone bringing up major issues in the past. We used MS concierge service because we knew the people because it was an old employee who, through SW, got invited to work for MS. They did a bunch of stuff they weren't supposed to do and caused a lot of problems.
oh i see.
-
@tim_g said in Office 365 Email Gone After Forced Logoff:
If I create a new AD user, it gets synced to O365, but is unlicensed until I go in and manually assign an E1 or E3 license.
It's like that by default, and I want to keep it that way... so I don't know if there's a way to assign those licenses on-prem or not. I don't want anything automatically assigned.
We've not had the sync for a long time, but the environment is always questionable because MS was never able to get it cleanly separated. but that's absolutely nothing to do with the current situation. That's just people bringing up problems from the past.
All issues this year are 100% licensing, and in no way associated with any past problems.
-
@tim_g said in Office 365 Email Gone After Forced Logoff:
@scottalanmiller said in Office 365 Email Gone After Forced Logoff:
@tim_g said in Office 365 Email Gone After Forced Logoff:
@psx_defector said in Office 365 Email Gone After Forced Logoff:
@scottalanmiller said in Office 365 Email Gone After Forced Logoff:
@jaredbusch said in Office 365 Email Gone After Forced Logoff:
As I recall, your O365 accounts were tied to some AD sync server.
This is all the fault of whoever set tings up and never properly disconnected stuff.
Microsoft themselves set that up without permission.
Let's say that I know that's not the case, for very specific reasons you should know already.
MS never sets up your stuff. Especially with AD Sync, considering it has to be installed locally.
We use AD Sync for O365, and that has nothing to do with licensing.
It's someone bringing up major issues in the past. We used MS concierge service because we knew the people because it was an old employee who, through SW, got invited to work for MS. They did a bunch of stuff they weren't supposed to do and caused a lot of problems.
oh i see.
Yeah, it's how we learned of the concierge program, and we had access to it because of our partner level. Big mistake. We don't trust MS engineering any more, at all. Period.
-
They would also use the concierge program to hand out bad support info. Then blame customers for using bad contact info. AFAIK the entire setup existed just as a way to avoid providing support.
-
@scottalanmiller said in Office 365 Email Gone After Forced Logoff:
They would also use the concierge program to hand out bad support info. Then blame customers for using bad contact info. AFAIK the entire setup existed just as a way to avoid providing support.
Who would do that? Oh, wait
-
@wls-itguy said in Office 365 Email Gone After Forced Logoff:
@scottalanmiller said in Office 365 Email Gone After Forced Logoff:
They would also use the concierge program to hand out bad support info. Then blame customers for using bad contact info. AFAIK the entire setup existed just as a way to avoid providing support.
Who would do that? Oh, wait
We escalated through Chris, too, and he could do nothing to get us to working support back then.
-
@tim_g said in Office 365 Email Gone After Forced Logoff:
@psx_defector said in Office 365 Email Gone After Forced Logoff:
@scottalanmiller said in Office 365 Email Gone After Forced Logoff:
@jaredbusch said in Office 365 Email Gone After Forced Logoff:
As I recall, your O365 accounts were tied to some AD sync server.
This is all the fault of whoever set tings up and never properly disconnected stuff.
Microsoft themselves set that up without permission.
Let's say that I know that's not the case, for very specific reasons you should know already.
MS never sets up your stuff. Especially with AD Sync, considering it has to be installed locally.
We use AD Sync for O365, and that has nothing to do with licensing.
If I create a new AD user, it gets synced to O365, but is unlicensed until I go in and manually assign an E1 or E3 license.
It's like that by default, and I want to keep it that way... so I don't know if there's a way to assign those licenses on-prem or not. I don't want anything automatically assigned.
https://gallery.technet.microsoft.com/office/Assign-Office-365-Licenses-b7385ebe
Anything can be done if you know what to do.
-
@scottalanmiller said in Office 365 Email Gone After Forced Logoff:
@psx_defector said in Office 365 Email Gone After Forced Logoff:
MS never sets up your stuff. Especially with AD Sync, considering it has to be installed locally.
MS concierge did it himself. That would be Greg. And yes, it was done locally, without permission. In fact, he was explicitly forbidden to do so.
Then you should have purged out the objects out of AAD, set them back up correctly, and then hit the gym.
Or you could have just called me.
Of course, out of bounds, blame Microsoft and not the guy you gave permissions to the local equipment.
