Saves a monumental amount of time, particularly when trying to find if a fee code exists.Microsoft 365 and Office 365 are available in a variety of plans to best meet the needs of your organization. So I made a script that prompts you for login info, logs in, downloads all the codes, and parses each product type into a spreadsheet that you can filter and search easily, along with the links to open each fee code. Particularly when your average tickets solved per day is 30-40. If we get a ticket saying to change 10 codes, at 5 minutes per code on a good day that's a lot of time. I've actually made helpdesk articles internally for some of the tools I've made since they are so helpful: we have an internal tool that uses fee codes, but it's such an old codebase that the list just loads up a giant (16 megabytes, in internet explorer!) html table with links to click on to edit the codes, instead of any kind of api. Went from an hour due to people using the systems that needed the fix to 5 minutes and do something else while it goes. So I made a script where you enter each hostname, and it just uses psexec to copy the files, run the script, and clean up. I had a similar kind of task on my work term for school: remote in, copy files, run batch, clean up. Yeah, and don't forget about tools like psexec and stuff. I've spent pretty much 20 hours since Friday night really sharpening my skills with PowerShell and Flow and Forms with the intent to make several of my customers happy that are wanting just maddening unrealistic turn around times on user account creations (But it's completely justified due to the turn over rate in all the various offices.) And sends a subsequent e-mail letting everyone know it's been done.
Then it delays 30 days and submits a subsequent request to Permanently delete the user which then launches a second desktop flow that simply runs the azure ad remove user command from powershell. I have finally built a flow that takes the details from a form submission, and then requests approval for deletion, disables the account, removes the user from all groups, and then launches a desktop power flow to run PowerShell to convert the mailbox to a shared mailbox, delegate perms to the designated contact, and then create forwarding and auto reply. Just trying to wrap my head around the different commands I would need to use to make this happen and if i'm missing anything.Įdit: Thanks to some of the posts here, and lots of googling and searching MS docs.
Is this what everyone else typically does?Īnd does anyone do this via a powershell script?
Historically we have signed in to the EOC, and selected delete user and converted to shared mailbox and set up automatic replies and mail forwarding. I'm working on an automated script to remove users when terminated, and was wondering what is everyone else's best practices?
0 kommentar(er)
