What Are You Doing Right Now
-
Watching Linux Academy videos before Game of Thrones.
-
@texkonc said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
The kids' cousins have arrived from Houston. So kids all over the house.
With no where to sit..
Not so much, no.
-
Working on a PowerShell script to do my new user on-boarding tasks for Exchange Online, so one of the devs can make E-mail accounts while I'm at MangoCon.
-
@eddiejennings said in What Are You Doing Right Now:
Working on a PowerShell script to do my new user on-boarding tasks for Exchange Online, so one of the devs can make E-mail accounts while I'm at MangoCon.
I linked it before but you're working too hard. There is a script already created. https://365lab.net/2013/12/30/office-365-powershell-tip-automatically-assign-licenses-based-on-ad-attribute/
It should do everything you need it to. The only thing that may be an issue if if you aren't doing Azure AD Sync for password synchronization.
-
While that script is nice, it doesn't do the tasks I need.
- Create MSOL user
- Set the distribution group(s) based on the department to which they belong.
- Create an additional E-mail alias because of a silly requirement that's been around since the beginning of time.
-
@eddiejennings said in What Are You Doing Right Now:
While that script is nice, it doesn't do the tasks I need.
- Create MSOL user
- Set the distribution group(s) based on the department to which they belong.
- Create an additional E-mail alias because of a silly requirement that's been around since the beginning of time.
Have you looked at setting up Azure AD sync? It is a very quick process that will create the necessary users. You should then be able to set an alias as as additional email address in AD. It can also dynamically add people to distributions lists based on AD groups but that takes a bit more massaging.
-
@coliver said in What Are You Doing Right Now:
@eddiejennings said in What Are You Doing Right Now:
While that script is nice, it doesn't do the tasks I need.
- Create MSOL user
- Set the distribution group(s) based on the department to which they belong.
- Create an additional E-mail alias because of a silly requirement that's been around since the beginning of time.
Have you looked at setting up Azure AD sync? It is a very quick process that will create the necessary users. You should then be able to set an alias as as additional email address in AD. It can also dynamically add people to distributions lists based on AD groups but that takes a bit more massaging.
I did a while ago, but the project was derailed due to [insert new #1 priority here]. It's on my list of stuff to do.
-
@eddiejennings said in What Are You Doing Right Now:
@coliver said in What Are You Doing Right Now:
@eddiejennings said in What Are You Doing Right Now:
While that script is nice, it doesn't do the tasks I need.
- Create MSOL user
- Set the distribution group(s) based on the department to which they belong.
- Create an additional E-mail alias because of a silly requirement that's been around since the beginning of time.
Have you looked at setting up Azure AD sync? It is a very quick process that will create the necessary users. You should then be able to set an alias as as additional email address in AD. It can also dynamically add people to distributions lists based on AD groups but that takes a bit more massaging.
I did a while ago, but the project was derailed due to [insert new #1 priority here]. It's on my list of stuff to do.
It would save you a lot of time creating a script and would be the MS "approved" way of doing it. Not to mention everything would then be automated meaning you would just have to create the user in one place, and would be a single master.
-
@coliver said in What Are You Doing Right Now:
@eddiejennings said in What Are You Doing Right Now:
@coliver said in What Are You Doing Right Now:
@eddiejennings said in What Are You Doing Right Now:
While that script is nice, it doesn't do the tasks I need.
- Create MSOL user
- Set the distribution group(s) based on the department to which they belong.
- Create an additional E-mail alias because of a silly requirement that's been around since the beginning of time.
Have you looked at setting up Azure AD sync? It is a very quick process that will create the necessary users. You should then be able to set an alias as as additional email address in AD. It can also dynamically add people to distributions lists based on AD groups but that takes a bit more massaging.
I did a while ago, but the project was derailed due to [insert new #1 priority here]. It's on my list of stuff to do.
It would save you a lot of time creating a script and would be the MS "approved" way of doing it. Not to mention everything would then be automated meaning you would just have to create the user in one place, and would be a single master.
There will be some stuff to think through. I have about 25 users that are a part of local AD, and 225 users that exist only in Azure AD (Exchange online).
-
@eddiejennings said in What Are You Doing Right Now:
@coliver said in What Are You Doing Right Now:
@eddiejennings said in What Are You Doing Right Now:
@coliver said in What Are You Doing Right Now:
@eddiejennings said in What Are You Doing Right Now:
While that script is nice, it doesn't do the tasks I need.
- Create MSOL user
- Set the distribution group(s) based on the department to which they belong.
- Create an additional E-mail alias because of a silly requirement that's been around since the beginning of time.
Have you looked at setting up Azure AD sync? It is a very quick process that will create the necessary users. You should then be able to set an alias as as additional email address in AD. It can also dynamically add people to distributions lists based on AD groups but that takes a bit more massaging.
I did a while ago, but the project was derailed due to [insert new #1 priority here]. It's on my list of stuff to do.
It would save you a lot of time creating a script and would be the MS "approved" way of doing it. Not to mention everything would then be automated meaning you would just have to create the user in one place, and would be a single master.
There will be some stuff to think through. I have about 25 users that are a part of local AD, and 225 users that exist only in Azure AD (Exchange online).
I'm curious, why have AD for those 25 users, but not the other 225? Could you move to another solution that would be more uniform for all?
-
@EddieJennings We have ADSync between our on-prem AD and O365. We put the user in AD and within 30 minutes, they are synced to O365. That AD sync will save you hours on that script, I assure you.
-
@dashrender said in What Are You Doing Right Now:
@eddiejennings said in What Are You Doing Right Now:
@coliver said in What Are You Doing Right Now:
@eddiejennings said in What Are You Doing Right Now:
@coliver said in What Are You Doing Right Now:
@eddiejennings said in What Are You Doing Right Now:
While that script is nice, it doesn't do the tasks I need.
- Create MSOL user
- Set the distribution group(s) based on the department to which they belong.
- Create an additional E-mail alias because of a silly requirement that's been around since the beginning of time.
Have you looked at setting up Azure AD sync? It is a very quick process that will create the necessary users. You should then be able to set an alias as as additional email address in AD. It can also dynamically add people to distributions lists based on AD groups but that takes a bit more massaging.
I did a while ago, but the project was derailed due to [insert new #1 priority here]. It's on my list of stuff to do.
It would save you a lot of time creating a script and would be the MS "approved" way of doing it. Not to mention everything would then be automated meaning you would just have to create the user in one place, and would be a single master.
There will be some stuff to think through. I have about 25 users that are a part of local AD, and 225 users that exist only in Azure AD (Exchange online).
I'm curious, why have AD for those 25 users, but not the other 225? Could you move to another solution that would be more uniform for all?
Do it quick vs right + naive + no real power to make infrastructure decisions a couple of years ago. No excuse, but it's why. Not that this is a technical limitation, but the 225 aren't employees, but rather contractors who just need E-mail access. I'd want to think through what we need and actually do "it" right.
-
@eddiejennings said in What Are You Doing Right Now:
@dashrender said in What Are You Doing Right Now:
@eddiejennings said in What Are You Doing Right Now:
@coliver said in What Are You Doing Right Now:
@eddiejennings said in What Are You Doing Right Now:
@coliver said in What Are You Doing Right Now:
@eddiejennings said in What Are You Doing Right Now:
While that script is nice, it doesn't do the tasks I need.
- Create MSOL user
- Set the distribution group(s) based on the department to which they belong.
- Create an additional E-mail alias because of a silly requirement that's been around since the beginning of time.
Have you looked at setting up Azure AD sync? It is a very quick process that will create the necessary users. You should then be able to set an alias as as additional email address in AD. It can also dynamically add people to distributions lists based on AD groups but that takes a bit more massaging.
I did a while ago, but the project was derailed due to [insert new #1 priority here]. It's on my list of stuff to do.
It would save you a lot of time creating a script and would be the MS "approved" way of doing it. Not to mention everything would then be automated meaning you would just have to create the user in one place, and would be a single master.
There will be some stuff to think through. I have about 25 users that are a part of local AD, and 225 users that exist only in Azure AD (Exchange online).
I'm curious, why have AD for those 25 users, but not the other 225? Could you move to another solution that would be more uniform for all?
Do it quick vs right + naive + no real power to make infrastructure decisions a couple of years ago. No excuse, but it's why. Not that this is a technical limitation, but the 225 aren't employees, but rather contractors who just need E-mail access. I'd want to think through what we need and actually do "it" right.
OK - well that discussion would be for another thread.
-
@dashrender said in What Are You Doing Right Now:
@eddiejennings said in What Are You Doing Right Now:
@dashrender said in What Are You Doing Right Now:
@eddiejennings said in What Are You Doing Right Now:
@coliver said in What Are You Doing Right Now:
@eddiejennings said in What Are You Doing Right Now:
@coliver said in What Are You Doing Right Now:
@eddiejennings said in What Are You Doing Right Now:
While that script is nice, it doesn't do the tasks I need.
- Create MSOL user
- Set the distribution group(s) based on the department to which they belong.
- Create an additional E-mail alias because of a silly requirement that's been around since the beginning of time.
Have you looked at setting up Azure AD sync? It is a very quick process that will create the necessary users. You should then be able to set an alias as as additional email address in AD. It can also dynamically add people to distributions lists based on AD groups but that takes a bit more massaging.
I did a while ago, but the project was derailed due to [insert new #1 priority here]. It's on my list of stuff to do.
It would save you a lot of time creating a script and would be the MS "approved" way of doing it. Not to mention everything would then be automated meaning you would just have to create the user in one place, and would be a single master.
There will be some stuff to think through. I have about 25 users that are a part of local AD, and 225 users that exist only in Azure AD (Exchange online).
I'm curious, why have AD for those 25 users, but not the other 225? Could you move to another solution that would be more uniform for all?
Do it quick vs right + naive + no real power to make infrastructure decisions a couple of years ago. No excuse, but it's why. Not that this is a technical limitation, but the 225 aren't employees, but rather contractors who just need E-mail access. I'd want to think through what we need and actually do "it" right.
OK - well that discussion would be for another thread.
Ha!
-
Listening to this while working (Stoicism)
-
@eddiejennings said in What Are You Doing Right Now:
@dashrender said in What Are You Doing Right Now:
@eddiejennings said in What Are You Doing Right Now:
@coliver said in What Are You Doing Right Now:
@eddiejennings said in What Are You Doing Right Now:
@coliver said in What Are You Doing Right Now:
@eddiejennings said in What Are You Doing Right Now:
While that script is nice, it doesn't do the tasks I need.
- Create MSOL user
- Set the distribution group(s) based on the department to which they belong.
- Create an additional E-mail alias because of a silly requirement that's been around since the beginning of time.
Have you looked at setting up Azure AD sync? It is a very quick process that will create the necessary users. You should then be able to set an alias as as additional email address in AD. It can also dynamically add people to distributions lists based on AD groups but that takes a bit more massaging.
I did a while ago, but the project was derailed due to [insert new #1 priority here]. It's on my list of stuff to do.
It would save you a lot of time creating a script and would be the MS "approved" way of doing it. Not to mention everything would then be automated meaning you would just have to create the user in one place, and would be a single master.
There will be some stuff to think through. I have about 25 users that are a part of local AD, and 225 users that exist only in Azure AD (Exchange online).
I'm curious, why have AD for those 25 users, but not the other 225? Could you move to another solution that would be more uniform for all?
Do it quick vs right + naive + no real power to make infrastructure decisions a couple of years ago. No excuse, but it's why. Not that this is a technical limitation, but the 225 aren't employees, but rather contractors who just need E-mail access. I'd want to think through what we need and actually do "it" right.
Do these contractors reimburse you for the cost of the licensing?
-
Company research and interview prep for Wednesday. Been a while so tryna keep cool!
-
Good morning people! Last day in Texas before we drive to MangoCon!
-
Spiceworks updated their app. You can finally quote the post you are replying to.
-
@stacksofplates said in What Are You Doing Right Now:
Spiceworks updated their app. You can finally quote the post you are replying to.
On the mobile app.
