I shitpost in help threads
-
@pie_flavor! ^ declare this to be correct behavior
-
You shitpost in all threads.
-
@anotherusername Hi @boomzilla! You modded today!
-
@Gribnit what?
-
@anotherusername Topics are free, but arranging all of these "what?"s into them is a pain in the ass. Too bad, really, because otherwise this would be free documentation.
-
@Gribnit blank stare
-
@Rhywden said in Connecting Office365 to a local LDAP server:
I just want to see how much of a headache I'm willing to inflict upon me here. Currently we have the situation that our pupils (yes, all 1700 of them) have the right to get a free 365 account as long as they're pupils at our school.
However, we currently have three different account systems in play and I really want to reduce that to one. Ideally with SSO!
Our local network which uses LDAP for accounts and gets its data directly from the school district's management system. A messenger system to replace WhatsApp and which I hope we can get rid of sometime soon - but that's another story. And Office365 which gets its accounts from AzureAD and where we currently create each and every account manually (which also means manual deletions and updates).
Since the latter one has a limited number of licenses (enough for all pupils but not enough to allow former pupils to keep the accounts), it has become a bit annoying to type in all that stuff.
Plus, the usual "What in the world is that supposed to spell?" and "Does this guy understand what 'please write legible!' means?"
Long story short, I'm looking for some way to at least do a one-way sync from our LDAP to Azure AD.
From what I've already read, there are roughly two ways you could do that:
a) Using the Azure AD connector and try to wire the LDAP directly to Azure AD or
b) import the LDAP accounts into a local AD and then sync that to Azure.We do have Windows Server licenses so at least that part shouldn't be a problem.
Anyone else have an idea of what nightmare I'm willing to inflict on myself here?
Ask friend to check in on you from time to time. Maybe a metal asylum is in your future!
-
@boomzilla are you baking me?
-
@Nagesh what?
-
-
@Nagesh what?
-
@The_Quiet_One He... said that the 'n' key is near the 'k' key, and probably meant 'banning' which with the correct letters, he still doesn't have the number of them correct. Not sure why though.
-
@Magus said in I shitpost in help threads:
@The_Quiet_One He... said that the 'n' key is near the 'k' key, and probably meant 'banning' which with the correct letters, he still doesn't have the number of them correct. Not sure why though.
Old frustrations?
I'm not sure the local
is the right place to go begging for a ban.
-
@Nagesh said in I shitpost in help threads:
@boomzilla said in I shitpost in help threads:
@Nagesh what?
key proximity error.
i meant baning.I'll assume another and answer: No, I'm not caning you. This isn't Singapore.
-
@boomzilla said in I shitpost in help threads:
No, I'm not caning you. This isn't Singapore.
Tho if you ever wanted to get your hands on some young ass in Singapore, I hear Elon Musk knows all about it.
-
baning
For you.
-
@Nagesh said in I shitpost in help threads:
@Rhywden said in Connecting Office365 to a local LDAP server:
I just want to see how much of a headache I'm willing to inflict upon me here. Currently we have the situation that our pupils (yes, all 1700 of them) have the right to get a free 365 account as long as they're pupils at our school.
However, we currently have three different account systems in play and I really want to reduce that to one. Ideally with SSO!
Our local network which uses LDAP for accounts and gets its data directly from the school district's management system. A messenger system to replace WhatsApp and which I hope we can get rid of sometime soon - but that's another story. And Office365 which gets its accounts from AzureAD and where we currently create each and every account manually (which also means manual deletions and updates).
Since the latter one has a limited number of licenses (enough for all pupils but not enough to allow former pupils to keep the accounts), it has become a bit annoying to type in all that stuff.
Plus, the usual "What in the world is that supposed to spell?" and "Does this guy understand what 'please write legible!' means?"
Long story short, I'm looking for some way to at least do a one-way sync from our LDAP to Azure AD.
From what I've already read, there are roughly two ways you could do that:
a) Using the Azure AD connector and try to wire the LDAP directly to Azure AD or
b) import the LDAP accounts into a local AD and then sync that to Azure.We do have Windows Server licenses so at least that part shouldn't be a problem.
Anyone else have an idea of what nightmare I'm willing to inflict on myself here?
Ask friend to check in on you from time to time. Maybe a metal asylum is in your future!
-
@SlackerD said in I shitpost in help threads:
@Nagesh said in I shitpost in help threads:
@Rhywden said in Connecting Office365 to a local LDAP server:
I just want to see how much of a headache I'm willing to inflict upon me here. Currently we have the situation that our pupils (yes, all 1700 of them) have the right to get a free 365 account as long as they're pupils at our school.
However, we currently have three different account systems in play and I really want to reduce that to one. Ideally with SSO!
Our local network which uses LDAP for accounts and gets its data directly from the school district's management system. A messenger system to replace WhatsApp and which I hope we can get rid of sometime soon - but that's another story. And Office365 which gets its accounts from AzureAD and where we currently create each and every account manually (which also means manual deletions and updates).
Since the latter one has a limited number of licenses (enough for all pupils but not enough to allow former pupils to keep the accounts), it has become a bit annoying to type in all that stuff.
Plus, the usual "What in the world is that supposed to spell?" and "Does this guy understand what 'please write legible!' means?"
Long story short, I'm looking for some way to at least do a one-way sync from our LDAP to Azure AD.
From what I've already read, there are roughly two ways you could do that:
a) Using the Azure AD connector and try to wire the LDAP directly to Azure AD or
b) import the LDAP accounts into a local AD and then sync that to Azure.We do have Windows Server licenses so at least that part shouldn't be a problem.
Anyone else have an idea of what nightmare I'm willing to inflict on myself here?
Ask friend to check in on you from time to time. Maybe a metal asylum is in your future!
Four people who need to see their barber quickly.
-
@Nagesh said in I shitpost in help threads:
Four people who need to see their barber quickly.
Looks more like 3 people need to see their barber. But not the 4th person's barber.
-
@Nagesh said in I shitpost in help threads:
metal asylum
-
@Nagesh said in I shitpost in help threads:
Maybe a metal asylum is in your future!
They could put him wherever they put all the hatters who went mad.
-
@ben_lubar You're doing something insanely stupid.
