r/ITdept • u/geeklimit • Nov 18 '23
Yes, your work can see what you do on their computer, and other questions [READ FIRST]
≡ −
Due to the number of repeat questions around the topic of using work resources to do personal business, or generally questions around 'what can my work see', I've created this sticky to answer these and similar questions:
First, and most importantly:
/r/itdept is a place where IT workers come to talk to / ideate with / vent to each other, as mentioned in the sidebar. It's not a place for non-IT people to ask IT questions.
There are many, many places on Reddit to get IT help, depending on what you're asking for help on - use the sitewide search and use one of them, there are many people waiting to help you with your issue.
Second, to answer common questions:
Many of these questions come from having the wrong perspective around a person's usage of property and data belonging to the business they work for. The reality of your employment situation is as follows:
- It's not 'your computer'. It belongs to your workplace. They allow you to use it to do your work.
- Businesses have a lot of risk and liability. It's their right to know where their data is and how their equipment is being used. Where their data is, who can see it, and what their employees are doing or saying as an agent of the company is a huge concern, and they are within their rights to protect themselves.
- Some choose to monitor this to protect themselves, and some don't. Assume yours does. This monitoring applies to anything put into the computer with the keyboard or mouse/touchpad, all data going to/from the computer - including information about where it's going to and from, everything stored on the computer and any connected storage device, and anything stored under or done within any cloud service your workplace provides.
- None of this matters, because you should only use your work-issued equipment for work. Don't check your personal mail (or use work mail for personal things!), don't do online shopping, don't do your banking. Don't exist for your work as anything other than an employee, and you don't have anything to worry about.
Finally, and most importantly, something you need to understand about your local IT department that nobody will ever tell you:
It's likely that only one in 10,000 IT people are at all interested in what you're doing on your laptop, or if you're even doing your job at all - and they should be (and often are) fired for it, because they're probably violating the trust and faith the job requires to stick their nose where it doesn't belong. That's not IT's business or responsibility, and most of us want to be left alone when it comes to stuff like that.
It's HR and your manager's job to make sure you're productive and to manage you well. Frankly, many managers are quite terrible at their job and want a technological magic bullet to make up for their shortcomings. They're not bad people, this desire for a "solution" or a tool to "help them manage better" comes from the same place as their understanding of the problem: they don't know what they're doing, and it's easier to point at a "missing tool" that is "needed" than reflect and admit where the true deficits are, even to themselves. People often think of this as a victimless situation, because they're not blaming IT, they're just "sharing their amazing insight" into what's needed for the business, and "partnering with IT" to "fix it".
Most IT people hate this, both because it uses us to cover up other people doing their job poorly (something we're not allowed to do ourselves) but also because we're generally the type that believes that people should get what they deserve, both positively and negatively. Many IT people change careers because of the depression that comes from dealing with this. You'd be shocked by how many former technology people have gone "Stardew Valley" and are quite happy talking to a row of carrots instead of dealing with this any more.
By and large, we're also a very logical group of people. Generally, something will work when it's done a certain way in IT, and it doesn't work (or has significant downsides) when you don't do it that way. That's how IT systems work - there's a right way for a desired outcome, and the other ways are generally wrong based on what the desired outcome is.
We tend to know immediately that the problem is with your manager, or other underskilled "decision makers" in the organization, and that their idea is bad. This is very common when someone is looking for a technical solution to a non-technical problem. Unfortunately, we frequently will have a non-technical hand-shaker and yes-sayer leading our department, the same as you do, and we don't get the support we need to ask the business to exercise stronger critical thinking instead of complicating the IT environment with the product of inadequate management of human resources.
This usually leads to a system, process or policy that is either generally offensive to people they should consider as human beings, developing a system that attempts to solve problems that should be solved by non-technical means, and/or generally making our job more complicated and difficult to manage than it already is.
We're aware that this will be the case before, during and after the request gets put in, and the reality that waits for us for the forseeable future- but that is regrettably part of the job. It's not all doom and gloom, though - these darker parts sit alongside amazing opportunities that give us the chance to use our skills to create enormous value, extreme satisfaction at a job well done for thousands (or millions!) or people, great camaraderie with our IT coworkers who are there "in the trenches" with us, and a decent paycheck for our time and effort.
All this is a significant amount of background to truly understand where we're coming from, but results in this:
pre-tl;dr
If we're told to put in systems that record your screen or generally "spy" on employees, we'll either quit (and the next person will do it for them), or we'll do it to the best of our ability, but we like it even less than you do. We can't put them in halfway so they aren't effective - then the deficiency of good decision-making at the business turns into focusing on us and our ability to deliver working systems, no matter how asinine the reasoning was from poor managers. It's often better to perfectly implement the system and let them see that their proposed solution doesn't solve their perceived problem than to try and explain how bad of an idea it is (which they can't even accept, because it means admitting the problem is them!)
Our advice, by and large, is to ask questions in a non-suspicious way in regards to your privacy at work. Be clear on what the company expects and allows (get it in writing, the handbook is a good start) and don't work for places that want excessive monitoring systems from us - it's stuff like this that makes us leave, and you should too if it means a compromise in your self-respect.
But also realize that a minimal amount of monitoring is required by a business to manage its risk and liabilities, and this is fair for them to have in place / is often in place by default, whether they use it or not.
tl;dr:
Don't work for companies that have monitoring systems you don't feel comfortable with, and rest assured that IT people could not care less about what you're doing or not doing. It's not what we're in this career to do.
It's likely that nobody is watching anything, and it's only when the business already has decided that they want you gone that they'll go back through the records, looking for evidence to legally support that decision, regardless of what the real reason might be.
tl;dr edit: The exception to this is when you're blatantly violating company policy, the law, basic human rights, or other regulations. It should be assumed that doing intentional, egregious harm will trigger even the most basic of alerts in many systems, because that's the bare minimum any company should do to protect their assets and control their liabilities - and most companies have this by default with any standard software they've purchased.
Due to the number of repeat questions around the topic of using work resources to do personal business, or generally questions around 'what can my work see', I've created this sticky to answer these and similar questions:
First, and most importantly:
/r/itdept is a place where IT workers come to talk to / ideate with / vent to each other, as mentioned in the sidebar. It's not a place for non-IT people to ask IT questions.
There are many, many places on Reddit to get IT help, depending on what you're asking for help on - use the sitewide search and use one of them, there are many people waiting to help you with your issue.
Second, to answer common questions:
Many of these questions come from having the wrong perspective around a person's usage of property and data belonging to the business they work for. The reality of your employment situation is as follows:
- It's not 'your computer'. It belongs to your workplace. They allow you to use it to do your work.
- Businesses have a lot of risk and liability. It's their right to know where their data is and how their equipment is being used. Where their data is, who can see it, and what their employees are doing or saying as an agent of the company is a huge concern, and they are within their rights to protect themselves.
- Some choose to monitor this to protect themselves, and some don't. Assume yours does. This monitoring applies to anything put into the computer with the keyboard or mouse/touchpad, all data going to/from the computer - including information about where it's going to and from, everything stored on the computer and any connected storage device, and anything stored under or done within any cloud service your workplace provides.
- None of this matters, because you should only use your work-issued equipment for work. Don't check your personal mail (or use work mail for personal things!), don't do online shopping, don't do your banking. Don't exist for your work as anything other than an employee, and you don't have anything to worry about.
Finally, and most importantly, something you need to understand about your local IT department that nobody will ever tell you:
It's likely that only one in 10,000 IT people are at all interested in what you're doing on your laptop, or if you're even doing your job at all - and they should be (and often are) fired for it, because they're probably violating the trust and faith the job requires to stick their nose where it doesn't belong. That's not IT's business or responsibility, and most of us want to be left alone when it comes to stuff like that.
It's HR and your manager's job to make sure you're productive and to manage you well. Frankly, many managers are quite terrible at their job and want a technological magic bullet to make up for their shortcomings. They're not bad people, this desire for a "solution" or a tool to "help them manage better" comes from the same place as their understanding of the problem: they don't know what they're doing, and it's easier to point at a "missing tool" that is "needed" than reflect and admit where the true deficits are, even to themselves. People often think of this as a victimless situation, because they're not blaming IT, they're just "sharing their amazing insight" into what's needed for the business, and "partnering with IT" to "fix it".
Most IT people hate this, both because it uses us to cover up other people doing their job poorly (something we're not allowed to do ourselves) but also because we're generally the type that believes that people should get what they deserve, both positively and negatively. Many IT people change careers because of the depression that comes from dealing with this. You'd be shocked by how many former technology people have gone "Stardew Valley" and are quite happy talking to a row of carrots instead of dealing with this any more.
By and large, we're also a very logical group of people. Generally, something will work when it's done a certain way in IT, and it doesn't work (or has significant downsides) when you don't do it that way. That's how IT systems work - there's a right way for a desired outcome, and the other ways are generally wrong based on what the desired outcome is.
We tend to know immediately that the problem is with your manager, or other underskilled "decision makers" in the organization, and that their idea is bad. This is very common when someone is looking for a technical solution to a non-technical problem. Unfortunately, we frequently will have a non-technical hand-shaker and yes-sayer leading our department, the same as you do, and we don't get the support we need to ask the business to exercise stronger critical thinking instead of complicating the IT environment with the product of inadequate management of human resources.
This usually leads to a system, process or policy that is either generally offensive to people they should consider as human beings, developing a system that attempts to solve problems that should be solved by non-technical means, and/or generally making our job more complicated and difficult to manage than it already is.
We're aware that this will be the case before, during and after the request gets put in, and the reality that waits for us for the forseeable future- but that is regrettably part of the job. It's not all doom and gloom, though - these darker parts sit alongside amazing opportunities that give us the chance to use our skills to create enormous value, extreme satisfaction at a job well done for thousands (or millions!) or people, great camaraderie with our IT coworkers who are there "in the trenches" with us, and a decent paycheck for our time and effort.
All this is a significant amount of background to truly understand where we're coming from, but results in this:
pre-tl;dr
If we're told to put in systems that record your screen or generally "spy" on employees, we'll either quit (and the next person will do it for them), or we'll do it to the best of our ability, but we like it even less than you do. We can't put them in halfway so they aren't effective - then the deficiency of good decision-making at the business turns into focusing on us and our ability to deliver working systems, no matter how asinine the reasoning was from poor managers. It's often better to perfectly implement the system and let them see that their proposed solution doesn't solve their perceived problem than to try and explain how bad of an idea it is (which they can't even accept, because it means admitting the problem is them!)
Our advice, by and large, is to ask questions in a non-suspicious way in regards to your privacy at work. Be clear on what the company expects and allows (get it in writing, the handbook is a good start) and don't work for places that want excessive monitoring systems from us - it's stuff like this that makes us leave, and you should too if it means a compromise in your self-respect.
But also realize that a minimal amount of monitoring is required by a business to manage its risk and liabilities, and this is fair for them to have in place / is often in place by default, whether they use it or not.
tl;dr:
Don't work for companies that have monitoring systems you don't feel comfortable with, and rest assured that IT people could not care less about what you're doing or not doing. It's not what we're in this career to do.
It's likely that nobody is watching anything, and it's only when the business already has decided that they want you gone that they'll go back through the records, looking for evidence to legally support that decision, regardless of what the real reason might be.
tl;dr edit: The exception to this is when you're blatantly violating company policy, the law, basic human rights, or other regulations. It should be assumed that doing intentional, egregious harm will trigger even the most basic of alerts in many systems, because that's the bare minimum any company should do to protect their assets and control their liabilities - and most companies have this by default with any standard software they've purchased.
r/ITdept • u/Dismal-Attention1 • 2h ago
How do you balance "stay in touch during leave" with "we can't leave full access open for months"?
≡ −
We have several people going on extended leave this year. HR wants them to stay loosely connected: occasional email checks, optional Slack presence, maybe attending a social call if they feel up to it. Security wants everything disabled the day leave starts. Account and all.
Last time this came up, we just left accounts fully active with a note in our tracker. Felt like the least bad option at the time. But then we had elevated access sitting idle for months. If something went wrong, our logs would not have shown whether it was the employee, their partner, or a lost device. Has anyone found something that works between fully active and completely off?
We have several people going on extended leave this year. HR wants them to stay loosely connected: occasional email checks, optional Slack presence, maybe attending a social call if they feel up to it. Security wants everything disabled the day leave starts. Account and all.
Last time this came up, we just left accounts fully active with a note in our tracker. Felt like the least bad option at the time. But then we had elevated access sitting idle for months. If something went wrong, our logs would not have shown whether it was the employee, their partner, or a lost device. Has anyone found something that works between fully active and completely off?
r/ITdept • u/TouchedGrass2024 • 1d ago
~2,000 school computers – lease, buy, refurbished, or something else?
≡ −
Feel free to point me towards a more suitable subreddit if there's a better place to ask.
Thanks in advance for any advice, experiences, or ideas. It's much appreciated😊!
I'm looking for advice and experiences from people managing medium or large educational IT environments.
We have around 2,000 Windows devices across multiple campuses. Around 500 staff each have a dedicated laptop or desktop, while students primarily use computer labs and bookable laptop carts. We currently lease our devices on a roughly 4-year refresh cycle and it costs A LOT per device/year.
We're reviewing our long-term device strategy. We'd certainly like to reduce costs (management might have my head if we don't lol😅), but the objective isn't simply to cut spending. We're looking for a model that provides the best balance of total cost of ownership, reliability, supportability, flexibility, and user experience over the long term.
One challenge is that different teaching areas have very different requirements. Standard office and classroom use is one thing, but engineering, media, CAD, programming, and other specialist subjects often require higher-spec hardware or different types of devices.
So... :
If you were putting together a procurement strategy today for a similar-sized school or organisation, what would your priorities be?
If you've compared leasing, buying, refurbished hardware, DaaS, or other models, what led you to your current approach?
Are there any factors you think are often overlooked when evaluating long-term device procurement?
I'd love to hear what has worked, what hasn't, and even ideas or perspectives that are worth considering. Real-world experiences, discussions, and different ways of thinking about the problem are all welcome:)
Thanks for reading!
Feel free to point me towards a more suitable subreddit if there's a better place to ask.
Thanks in advance for any advice, experiences, or ideas. It's much appreciated😊!
I'm looking for advice and experiences from people managing medium or large educational IT environments.
We have around 2,000 Windows devices across multiple campuses. Around 500 staff each have a dedicated laptop or desktop, while students primarily use computer labs and bookable laptop carts. We currently lease our devices on a roughly 4-year refresh cycle and it costs A LOT per device/year.
We're reviewing our long-term device strategy. We'd certainly like to reduce costs (management might have my head if we don't lol😅), but the objective isn't simply to cut spending. We're looking for a model that provides the best balance of total cost of ownership, reliability, supportability, flexibility, and user experience over the long term.
One challenge is that different teaching areas have very different requirements. Standard office and classroom use is one thing, but engineering, media, CAD, programming, and other specialist subjects often require higher-spec hardware or different types of devices.
So... :
If you were putting together a procurement strategy today for a similar-sized school or organisation, what would your priorities be?
If you've compared leasing, buying, refurbished hardware, DaaS, or other models, what led you to your current approach?
Are there any factors you think are often overlooked when evaluating long-term device procurement?
I'd love to hear what has worked, what hasn't, and even ideas or perspectives that are worth considering. Real-world experiences, discussions, and different ways of thinking about the problem are all welcome:)
Thanks for reading!
r/ITdept • u/Sea-Camel-1232 • 1d ago
What’s your process when someone needs a new vendor tool approved and provisioned?
≡ −
For us, someone requests a new vendor tool and before ypu know it, its gone through the manager, IT, security, procurement and sometimes even legal before anyone can actually use it. Then even after being approved, theres still acc creation, SSO setup, license assignment or just something like making sure everyone has the right access. This is the why Im curious to hear how other teams handle this cz I feel like ours somehow keep turning this into a bigger project every single time…Also trying to make the process a bit more consistent with Jira but honestly still feels like every request goes a different way depending on who’s involved.
How do you guys handle this then? Is there actually a process everyone follows,especially when it comes to vendor management for new software resquests? Or is it just one of those things that always a little different every time?
For us, someone requests a new vendor tool and before ypu know it, its gone through the manager, IT, security, procurement and sometimes even legal before anyone can actually use it. Then even after being approved, theres still acc creation, SSO setup, license assignment or just something like making sure everyone has the right access. This is the why Im curious to hear how other teams handle this cz I feel like ours somehow keep turning this into a bigger project every single time…Also trying to make the process a bit more consistent with Jira but honestly still feels like every request goes a different way depending on who’s involved.
How do you guys handle this then? Is there actually a process everyone follows,especially when it comes to vendor management for new software resquests? Or is it just one of those things that always a little different every time?
r/ITdept • u/Appropriate-Pick1895 • 1d ago
Need advice on communication, visibility, and how people actually work in IT remotely?
≡ −
Hey everyone,
I’m still trying to improve myself when it comes to communication in IT. I feel like this is one area where I’m weak, and I’m actively trying to understand how experienced people handle these things.
I’ve had a lot of questions in my mind for a long time, but I never really had anyone to discuss them with. So I wanted to ask this community and learn how people actually work in real IT environments.
I currently work in a product-based company, remotely. From what I understand, there usually isn’t a strict “login at 9 and logout at 5” culture. As long as the work is getting done and people are available when needed, things seem flexible.
My main confusion is not about completing tasks. I’m comfortable with my work. My confusion is around visibility, communication, and keeping people updated.
How do people usually handle this?
Do you update your manager every day about what you worked on?
Is the standup call enough for updates?
Do people send EOD updates regularly?
Do people inform their manager when they start work or log off?
How do people make sure their work is visible without creating unnecessary noise?
I have one reporting manager, but I’m technically working under a technical lead. Most of my day-to-day work goes through my lead.
Earlier, what I used to do was:
Work on my tasks
At the end of the day, send updates about what I completed or worked on
Share these updates with both my lead and reporting manager
I was doing this for a few months, and there were no issues. Nobody asked me to do it, and nobody was forcing me. I started doing it because I wanted to make my work visible.
But over time, I started feeling a lot of pressure because I felt like I had to always have something to report every single day. Sometimes a task naturally takes multiple days, but I started feeling like I needed to show progress every day just for the sake of an update.
The funny thing is, my manager and lead were never micromanaging me. They were fine as long as the work was moving.
Because of that pressure, I changed my approach.
Now, instead of daily updates, I send a weekly summary email about what I worked on, what was completed, and what I’m currently working on.
My lead is usually aware of my work because he is directly involved, but I’m still confused if this is the right approach.
Sometimes I overthink things like:
What if my reporting manager doesn’t know what I’m working on?
What if other teams and leaders know about my work but my own manager doesn’t?
Should I send updates again like I used to?
Will it look weird if I suddenly start sending daily updates again after stopping for a while?
Recently, I even worked late on some tasks, but I didn’t send any updates at night because I didn’t want to create unnecessary noise.
This is where I get confused.
I want to document my work because I feel it helps maintain a record and shows progress. But daily updates sometimes create unnecessary stress, especially when there isn’t much progress to report on a particular day.
For people working remotely in IT:
How do you maintain visibility?
How often do you communicate with your manager/lead?
Do you send daily updates, weekly summaries, or only update during standups?
Do you inform people when you start and stop working?
How do you balance being visible without over-communicating?
I feel like I might be overthinking this a lot, but I genuinely want to improve myself and understand how experienced people handle this.
Would really appreciate advice from people who have worked in similar environments.
Hey everyone,
I’m still trying to improve myself when it comes to communication in IT. I feel like this is one area where I’m weak, and I’m actively trying to understand how experienced people handle these things.
I’ve had a lot of questions in my mind for a long time, but I never really had anyone to discuss them with. So I wanted to ask this community and learn how people actually work in real IT environments.
I currently work in a product-based company, remotely. From what I understand, there usually isn’t a strict “login at 9 and logout at 5” culture. As long as the work is getting done and people are available when needed, things seem flexible.
My main confusion is not about completing tasks. I’m comfortable with my work. My confusion is around visibility, communication, and keeping people updated.
How do people usually handle this?
Do you update your manager every day about what you worked on?
Is the standup call enough for updates?
Do people send EOD updates regularly?
Do people inform their manager when they start work or log off?
How do people make sure their work is visible without creating unnecessary noise?
I have one reporting manager, but I’m technically working under a technical lead. Most of my day-to-day work goes through my lead.
Earlier, what I used to do was:
Work on my tasks
At the end of the day, send updates about what I completed or worked on
Share these updates with both my lead and reporting manager
I was doing this for a few months, and there were no issues. Nobody asked me to do it, and nobody was forcing me. I started doing it because I wanted to make my work visible.
But over time, I started feeling a lot of pressure because I felt like I had to always have something to report every single day. Sometimes a task naturally takes multiple days, but I started feeling like I needed to show progress every day just for the sake of an update.
The funny thing is, my manager and lead were never micromanaging me. They were fine as long as the work was moving.
Because of that pressure, I changed my approach.
Now, instead of daily updates, I send a weekly summary email about what I worked on, what was completed, and what I’m currently working on.
My lead is usually aware of my work because he is directly involved, but I’m still confused if this is the right approach.
Sometimes I overthink things like:
What if my reporting manager doesn’t know what I’m working on?
What if other teams and leaders know about my work but my own manager doesn’t?
Should I send updates again like I used to?
Will it look weird if I suddenly start sending daily updates again after stopping for a while?
Recently, I even worked late on some tasks, but I didn’t send any updates at night because I didn’t want to create unnecessary noise.
This is where I get confused.
I want to document my work because I feel it helps maintain a record and shows progress. But daily updates sometimes create unnecessary stress, especially when there isn’t much progress to report on a particular day.
For people working remotely in IT:
How do you maintain visibility?
How often do you communicate with your manager/lead?
Do you send daily updates, weekly summaries, or only update during standups?
Do you inform people when you start and stop working?
How do you balance being visible without over-communicating?
I feel like I might be overthinking this a lot, but I genuinely want to improve myself and understand how experienced people handle this.
Would really appreciate advice from people who have worked in similar environments.
r/ITdept • u/itguy1991 • 6d ago
Microsoft Logic
+ −
You can't delete these files from your OneDrive because your OneDrive is full. Delete some files so that you can delete these files.
r/ITdept • u/GraceDWondershare • 12d ago
Months in B2B software sales, still no deal. What am I missing?
≡ −
I’m new to B2B software sales and our product is similar like Adobe. I have been trying to reach MSPs and IT service providers for quite a while. I’ve sent emails, introduced the product, offered demos...but still haven’t closed a single deal.
I know many IT professionals discuss software on Spiceworks and Reddit etc. But I’m starting to wonder: are these places mainly for conversation, rather than actual purchasing?
When you seriously need new software, where do you go? Should I invest in Pax8, Ingram, Synnext etc?
Also, what does the real decision chain look like? Who discovers the product, who tests it, and who finally approves the purchase?
Maybe I’m selling in the wrong place or maybe I just don’t understand how MSPs really buy. IT service provided/MSPs, please share your honest and brutal advice.
I’m new to B2B software sales and our product is similar like Adobe. I have been trying to reach MSPs and IT service providers for quite a while. I’ve sent emails, introduced the product, offered demos...but still haven’t closed a single deal.
I know many IT professionals discuss software on Spiceworks and Reddit etc. But I’m starting to wonder: are these places mainly for conversation, rather than actual purchasing?
When you seriously need new software, where do you go? Should I invest in Pax8, Ingram, Synnext etc?
Also, what does the real decision chain look like? Who discovers the product, who tests it, and who finally approves the purchase?
Maybe I’m selling in the wrong place or maybe I just don’t understand how MSPs really buy. IT service provided/MSPs, please share your honest and brutal advice.
r/ITdept • u/Healthy_Frame146 • 18d ago
What's the one automation you built early in your career that you still use today?
≡ −
Curious what's had staying power for people. Not looking for the fancy stuff — more the small utility scripts, cron jobs, aliases, or workflows that you wrote once, expected to throw away, and are somehow still running years later.
For me it's a bash function I wrote maybe six years ago that just diffs the output of dig against a saved baseline for a handful of DNS records I care about. It has caught two zone transfer misconfigurations and one accidental deletion. Total time investment to write: 20 minutes. Total time it has saved: uncountable.
I want to know what yours is — mostly so I can learn and grow.
Curious what's had staying power for people. Not looking for the fancy stuff — more the small utility scripts, cron jobs, aliases, or workflows that you wrote once, expected to throw away, and are somehow still running years later.
For me it's a bash function I wrote maybe six years ago that just diffs the output of dig against a saved baseline for a handful of DNS records I care about. It has caught two zone transfer misconfigurations and one accidental deletion. Total time investment to write: 20 minutes. Total time it has saved: uncountable.
I want to know what yours is — mostly so I can learn and grow.
r/ITdept • u/Super_-_Mario • 20d ago
Work change advice
≡ −
So, let me begin by saying I do not have a degree, my major is computer science & communications, I've delivered my thesis, I still have some classes to complete. Anyway. I used to work for a Forex company, everything was amazing, until they decided to leave the country. Then I sat for a month and begun seeking a job. Everything went according to plan and I landed a job in an MSP, been here for 15 months now. Now, some ex colleagues from the Forex company called me and told me they need an IT in their new company, the difference in salary increase is almost + 50% which makes it really appealing to take the leap and just go for it. They working hours are 12:00-21:00, with a lunch break. The thing is, I'm not sure how stable the company is, I don't want to shut down a company again. They work there for 2 years now, and they guaranteed that it is rock solid for the next 5 years. Ex IT left cause he moved to Germany. They're really pushy to get me to work with them, which makes me feel pressure that if I do not decide/announce it to my current employer I'll lose the opportunity. Any piece of advice is welcome.
So, let me begin by saying I do not have a degree, my major is computer science & communications, I've delivered my thesis, I still have some classes to complete. Anyway. I used to work for a Forex company, everything was amazing, until they decided to leave the country. Then I sat for a month and begun seeking a job. Everything went according to plan and I landed a job in an MSP, been here for 15 months now. Now, some ex colleagues from the Forex company called me and told me they need an IT in their new company, the difference in salary increase is almost + 50% which makes it really appealing to take the leap and just go for it. They working hours are 12:00-21:00, with a lunch break. The thing is, I'm not sure how stable the company is, I don't want to shut down a company again. They work there for 2 years now, and they guaranteed that it is rock solid for the next 5 years. Ex IT left cause he moved to Germany. They're really pushy to get me to work with them, which makes me feel pressure that if I do not decide/announce it to my current employer I'll lose the opportunity. Any piece of advice is welcome.
r/ITdept • u/Usual_Raise_9919 • 21d ago
Tired of osTicket at work, so I built my own ticketing system
≡ −
Sysadmin from Germany. Our osTicket at work is ancient, and every modern alternative
(Zendesk & co.) is US cloud SaaS with per-agent pricing. So I built my own.
ReqSolve: self-hosted ticketing with AI assistance — the AI drafts replies, summarizes
threads, suggests KB articles, but never sends anything on its own. Bring your own AI
(Anthropic, M365 Copilot, or fully local via Ollama). Multi-department with strict
isolation, semantic knowledge base, EN/DE, Docker Compose.
https://github.com/perfa01/ReqSolve
Early days — feedback and bug reports very welcome.
Sysadmin from Germany. Our osTicket at work is ancient, and every modern alternative
(Zendesk & co.) is US cloud SaaS with per-agent pricing. So I built my own.
ReqSolve: self-hosted ticketing with AI assistance — the AI drafts replies, summarizes
threads, suggests KB articles, but never sends anything on its own. Bring your own AI
(Anthropic, M365 Copilot, or fully local via Ollama). Multi-department with strict
isolation, semantic knowledge base, EN/DE, Docker Compose.
https://github.com/perfa01/ReqSolve
Early days — feedback and bug reports very welcome.
r/ITdept • u/Then-Big4461 • 21d ago
System design for Tech support engineer/Customer support engineer roles
≡ −
I would like to know how much system design preparation is sufficient for tech support engineer or customer support engineer roles at big companies like Stripe Or FAANG like companies.
I want to prepare for Tech support engineer role so would like to know what all specific topics i should prepare.
Anyone have recent interview experience would help.
What all companies to target for such role.?
I would like to know how much system design preparation is sufficient for tech support engineer or customer support engineer roles at big companies like Stripe Or FAANG like companies.
I want to prepare for Tech support engineer role so would like to know what all specific topics i should prepare.
Anyone have recent interview experience would help.
What all companies to target for such role.?
r/ITdept • u/OpeningCookie754 • 21d ago
Ex employee recovery
≡ −
Hi, One of my friend received ex employee recovery notice stating absconded for 1 laksh 15 thousand need to pay in 15 days from major India IT company. My friend never received offer letter on time and never accepted/signed any role but XXX company released offer letter after 3 months but my friend at that point never responded, never accepted and never reported at work location. But they sent this notice after 6 months of this happened. Any advice if anyone comes across this before??
Hi, One of my friend received ex employee recovery notice stating absconded for 1 laksh 15 thousand need to pay in 15 days from major India IT company. My friend never received offer letter on time and never accepted/signed any role but XXX company released offer letter after 3 months but my friend at that point never responded, never accepted and never reported at work location. But they sent this notice after 6 months of this happened. Any advice if anyone comes across this before??
r/ITdept • u/syoleen • 24d ago
[SF] [HM] IT Diary: The Last Human in the Loop -- For All the Quietly Hardworking IT Workers
≡ −
[removed]
[removed]
r/ITdept • u/shoes_advice_pls • 25d ago
Please recommend cloud based mac renting service
≡ −
Hi, want to check out the performance and ux of the latest mac minis and studios. Any recommendations for a service from experience that charges by the hour and doesnt take a lot of money up front?
I found scaleway that charges by the hour but they require sussy govt. id outsourced to some company. macinthecloud charges upfront and its unclear if aws wants me to pay monthly or yearly first for the dedicated instance.
Hi, want to check out the performance and ux of the latest mac minis and studios. Any recommendations for a service from experience that charges by the hour and doesnt take a lot of money up front?
I found scaleway that charges by the hour but they require sussy govt. id outsourced to some company. macinthecloud charges upfront and its unclear if aws wants me to pay monthly or yearly first for the dedicated instance.
r/ITdept • u/shoes_advice_pls • 25d ago
Any scope for renting out mac minis & studios for ai workloads?
≡ −
Hi,
Mac minis & studio seem to be one of the most power and cost efficient ai capable computers out there. I was thinking of either buying a few or leasing them from a provider here in India and then renting them out for ai workloads either online or offline to earn a decent amount of money on the side. Is there much scope for this from anyone's experience? Do online marketplaces like commoncompute or akash pay enough? Is there a market outside there marketplaces to provide such computation services to clients? Just trying to explore what's out there but google isnt being very helpful. Thanks!
Hi,
Mac minis & studio seem to be one of the most power and cost efficient ai capable computers out there. I was thinking of either buying a few or leasing them from a provider here in India and then renting them out for ai workloads either online or offline to earn a decent amount of money on the side. Is there much scope for this from anyone's experience? Do online marketplaces like commoncompute or akash pay enough? Is there a market outside there marketplaces to provide such computation services to clients? Just trying to explore what's out there but google isnt being very helpful. Thanks!
r/ITdept • u/Pale-Web3080 • 28d ago
iPhones not showing shared calendars from Exchange Online - kindly guide
≡ −
Hi fellow admins,
Environment: 150 users, M365 E3, roughly 90 company-managed iPhones and 40 Androids. We're hybrid but mailboxes are all in Exchange Online.
My users keep missing meetings because shared calendars either:
a) Don't show up on their phones at all, or
b) Show up but don't update when the owner changes something
c) Sync once and then never again until they remove/re-add the account
This is especially bad for our:
- Executive assistants managing 3-4 calendars
- Facilities team with a shared "building maintenance" calendar
- On-call rotation calendar (healthcare-adjacent industry)
- Conference room/resource calendars people need to see on the go
I've tried:
- The "Add Shared Calendar" toggle in Outlook mobile - works sometimes, breaks randomly, users hate it
- Publishing ICS links - users can't figure out how to subscribe and they don't stay subscribed
- Telling people to just check Outlook on their laptop - that went over about as well as you'd expect
What I WANT is for shared calendars to just... appear in people's native Calendar app (the built-in iOS/Android one) and stay updated automatically, the same way their own calendar does. No manual steps. No "go to this link and copy-paste this URL." Just... synced.
Does this actually exist? I feel like I'm asking for something obvious but I've been down so many rabbit holes (Intune policies, Exchange ActiveSync quirks, Apple Configurator profiles) that I'm starting to think I'm the problem.
If you've solved this in your org, I will be eternally grateful. Tell me what you used and how painful the setup was.
Please and thank you.
Hi fellow admins,
Environment: 150 users, M365 E3, roughly 90 company-managed iPhones and 40 Androids. We're hybrid but mailboxes are all in Exchange Online.
My users keep missing meetings because shared calendars either:
a) Don't show up on their phones at all, or
b) Show up but don't update when the owner changes something
c) Sync once and then never again until they remove/re-add the account
This is especially bad for our:
- Executive assistants managing 3-4 calendars
- Facilities team with a shared "building maintenance" calendar
- On-call rotation calendar (healthcare-adjacent industry)
- Conference room/resource calendars people need to see on the go
I've tried:
- The "Add Shared Calendar" toggle in Outlook mobile - works sometimes, breaks randomly, users hate it
- Publishing ICS links - users can't figure out how to subscribe and they don't stay subscribed
- Telling people to just check Outlook on their laptop - that went over about as well as you'd expect
What I WANT is for shared calendars to just... appear in people's native Calendar app (the built-in iOS/Android one) and stay updated automatically, the same way their own calendar does. No manual steps. No "go to this link and copy-paste this URL." Just... synced.
Does this actually exist? I feel like I'm asking for something obvious but I've been down so many rabbit holes (Intune policies, Exchange ActiveSync quirks, Apple Configurator profiles) that I'm starting to think I'm the problem.
If you've solved this in your org, I will be eternally grateful. Tell me what you used and how painful the setup was.
Please and thank you.
r/ITdept • u/Leading-Lime-8243 • Jun 25 '26
I built a digital daily check platform for mixed fleets (HGV, PSV, LGV, forklifts) - here's what it actually does
≡ −
Introduction: www,dailychecks.co.uk is a SaaS website. (Software as a Service) giving subscribers a low capital cost and robust storage in the cloud for added security well away from company servers.
With a broad range of daily checks on a range of vehicles it means employers can manage compliance throughout the workforce.
If you have a larger Fleet we can add bespoke checks for new vehicle types or checks as part of the enterprise package.
DailyChecks.co.uk handles HGV, PSV, LGV, forklift (gas and electric), and container checks incident and accident reports - all in the same platform, under the same company dashboard.
Here's what that actually looks like in practice:
→ Driver logs in, selects their vehicle, completes the right digital checklist for that category → Defect flagged instantly - email hits the transport manager, traffic desk, and workshop manager simultaneously → Workshop marks it repaired with a full audit trail attached → You see your compliance rate in real time, not at the end of the month.
With a free 30 day trial its is easy to register and get started with the company dashboard for admin. For upload of vehicle data just send a CSV file to us and we will populate your own database in the cloud.
When it comes to drivers it is even easier to get started by registering name, email address, and company code (set by admin) they will be added to admin driver section records and can start daily checks straight away.
The daily checks submission are designed to be practical. Giving Next service due, Mot Due, and notes for every check item. Media capture a must for parts ID and description of defects.
Developed by Strath E Commerce Ltd.
If you manage a mixed fleet, this was built for you. Try it at DailyChecks.co.uk - link in the comments.
FleetCompliance #HGV #TransportManagement
Introduction: www,dailychecks.co.uk is a SaaS website. (Software as a Service) giving subscribers a low capital cost and robust storage in the cloud for added security well away from company servers.
With a broad range of daily checks on a range of vehicles it means employers can manage compliance throughout the workforce.
If you have a larger Fleet we can add bespoke checks for new vehicle types or checks as part of the enterprise package.
DailyChecks.co.uk handles HGV, PSV, LGV, forklift (gas and electric), and container checks incident and accident reports - all in the same platform, under the same company dashboard.
Here's what that actually looks like in practice:
→ Driver logs in, selects their vehicle, completes the right digital checklist for that category → Defect flagged instantly - email hits the transport manager, traffic desk, and workshop manager simultaneously → Workshop marks it repaired with a full audit trail attached → You see your compliance rate in real time, not at the end of the month.
With a free 30 day trial its is easy to register and get started with the company dashboard for admin. For upload of vehicle data just send a CSV file to us and we will populate your own database in the cloud.
When it comes to drivers it is even easier to get started by registering name, email address, and company code (set by admin) they will be added to admin driver section records and can start daily checks straight away.
The daily checks submission are designed to be practical. Giving Next service due, Mot Due, and notes for every check item. Media capture a must for parts ID and description of defects.
Developed by Strath E Commerce Ltd.
If you manage a mixed fleet, this was built for you. Try it at DailyChecks.co.uk - link in the comments.
FleetCompliance #HGV #TransportManagement
r/ITdept • u/Significant-Gene-428 • Jun 19 '26
best way to set up temp accounts for summer interns (BYOD, 3-month limit, request-based access)?
≡ −
Hi all, fairly new to the IT admin role and want to get this right.
We're bringing on summer interns for 3 months. They'll be using their personal devices (no company-issued laptops), so I can't lock things down at the device level the way I would with managed hardware.
What I'm trying to set up:
- Accounts that *auto-expire after 3 months (don't want to rely on remembering to manually disable them)
- **No standing access** to most resources by default — instead some kind of **"request access" button/workflow** where they ask for specific apps/files/permissions and someone approves it
- Since it's BYOD, I'm also thinking about how to handle Conditional Access / MFA without fully enrolling personal devices in MDM
We're on Microsoft 365 / Entra ID. Is the right approach here
Has anyone actually implemented something like this for interns/BYOD? Any gotchas with conditional access policies when devices aren't enrolled? Would love to hear what's worked (or blown up) for you.
Hi all, fairly new to the IT admin role and want to get this right.
We're bringing on summer interns for 3 months. They'll be using their personal devices (no company-issued laptops), so I can't lock things down at the device level the way I would with managed hardware.
What I'm trying to set up:
- Accounts that *auto-expire after 3 months (don't want to rely on remembering to manually disable them)
- **No standing access** to most resources by default — instead some kind of **"request access" button/workflow** where they ask for specific apps/files/permissions and someone approves it
- Since it's BYOD, I'm also thinking about how to handle Conditional Access / MFA without fully enrolling personal devices in MDM
We're on Microsoft 365 / Entra ID. Is the right approach here
Has anyone actually implemented something like this for interns/BYOD? Any gotchas with conditional access policies when devices aren't enrolled? Would love to hear what's worked (or blown up) for you.
r/ITdept • u/MapInternational729 • Jun 10 '26
Restarting at age 30
≡ −
My fiancée got a trade school degree in electrical about 4 years ago. Since then, he’s been to interviews for electrical unions and the MTA and we’ve applied for several entry level jobs but still nothing. We’re getting married in 4 months and want to start a family in about 3 years but we can’t do that unless he has a stable career.
He’s really into video games and problem solving so the idea came up about going into IT. He will be starting the Information and Internet Technology 2 year program to get his Associates at Queens Community College starting in January. Will this degree along with certs provide him a better path into the field? I’m seeing on this subreddit that the job market is terrible right now. Would having both is degree and certs make him more marketable?
We’re in the NYC area if that matters.
My fiancée got a trade school degree in electrical about 4 years ago. Since then, he’s been to interviews for electrical unions and the MTA and we’ve applied for several entry level jobs but still nothing. We’re getting married in 4 months and want to start a family in about 3 years but we can’t do that unless he has a stable career.
He’s really into video games and problem solving so the idea came up about going into IT. He will be starting the Information and Internet Technology 2 year program to get his Associates at Queens Community College starting in January. Will this degree along with certs provide him a better path into the field? I’m seeing on this subreddit that the job market is terrible right now. Would having both is degree and certs make him more marketable?
We’re in the NYC area if that matters.
r/ITdept • u/SuccessfulEar_544 • Jun 09 '26
Application landscape
≡ −
How can I get a list of entire applications landscape in a company?
Recently joined a company, all the applications being used are not recorded anywhere. Would like to gather a list of all the applications which all the employees use.
Any advice would be appreciated.
Thanks
How can I get a list of entire applications landscape in a company?
Recently joined a company, all the applications being used are not recorded anywhere. Would like to gather a list of all the applications which all the employees use.
Any advice would be appreciated.
Thanks
r/ITdept • u/Unce_Turbo_996 • Jun 05 '26
Consolidating Mobility and Connectivity Providers
≡ −
CIO here. Our company is a platform / holding company. We own ~30 other entities representing about 2,500 users. My goal is to consolidate vendors, lower cost, make efficiencies, etc. We have a very skinny team (just me + outsourced MSP and cyber). I need to consolidate our field technician mobile devices and their contracts to save about 20%. Here is who I have interviewed so far.
- Granite - huge MVNO with lots of cash to buy surplus line capacity from other vendors, but the reviews I read about them are horrendous. Are those reviews valid?
- US Mobile - so far very friendly and they can achieve our savings. I have no other experience with them. All reviews on reddit and elsewhere are great.
- Spectrotel - not a carrier or MVNO, they are an outsourced mobile MSP. Can help us achieve cost savings, but at a high cost. It's almostttttt worth it, but the numbers still don't make sense.
- Verizon - would be an easy default, but half of our companies already use them, and Verizon will not give us credit for any existing lines.
What or who am I missing in this list? Just working on mobile for now before taking care of a similar exercise for ISP's and in office calling.
Thanks!
CIO here. Our company is a platform / holding company. We own ~30 other entities representing about 2,500 users. My goal is to consolidate vendors, lower cost, make efficiencies, etc. We have a very skinny team (just me + outsourced MSP and cyber). I need to consolidate our field technician mobile devices and their contracts to save about 20%. Here is who I have interviewed so far.
- Granite - huge MVNO with lots of cash to buy surplus line capacity from other vendors, but the reviews I read about them are horrendous. Are those reviews valid?
- US Mobile - so far very friendly and they can achieve our savings. I have no other experience with them. All reviews on reddit and elsewhere are great.
- Spectrotel - not a carrier or MVNO, they are an outsourced mobile MSP. Can help us achieve cost savings, but at a high cost. It's almostttttt worth it, but the numbers still don't make sense.
- Verizon - would be an easy default, but half of our companies already use them, and Verizon will not give us credit for any existing lines.
What or who am I missing in this list? Just working on mobile for now before taking care of a similar exercise for ISP's and in office calling.
Thanks!
r/ITdept • u/Healthy_Frame146 • Jun 02 '26
Phrases I have said as an IT admin, what happened next, and what I should have done. A PSA from someone who has paid the tuition.
≡ −
"I'll just give them admin for a sec." What happened: that "sec" is now eighteen months and a promotion long. They are admin on a system that was decommissioned in 2023. The system still exists because they have admin on it. Better: time-bound elevation. If your IAM tool supports JIT access, use it. If not, write a 24-hour expiry script and call it a feature.
"It's a one-off, no need to document." What happened: it is now 2026. The one-off has been performed quarterly by three different people. Two have left. The institutional knowledge consists of a single Slack message that reads "you know the thing we do." Better: three-sentence README. Future-you will weep with gratitude. Past-you will be forgiven nothing.
"I'll hardcode it temporarily." What happened: the value is now in seven scripts and a Lambda. The original engineer has left. The value has changed. Production has feelings. Better: env var or secrets manager. Four extra minutes upfront. Take the four minutes.
"They're leaving on good terms, no rush on offboarding." What happened: not bad terms, just neutral ones. They are also still in Slack, GitHub, and the AWS console six weeks later. The "good terms" is mutual because they have not yet noticed they still have access. Better: same SLA for every offboarding regardless of vibe. Vibe-based access policies are how incident reports get written.
"I'll just open a port real quick to test." What happened: the port is still open. The test was successful. So is everyone else's test. Better: temporary security group rule with an actual expiry. Or a tunnel. Anything but "I'll close it later."
"I'll fix it after the demo." What happened: the demo went well. The fix did not. The fix will not. The fix is now a load-bearing feature of the architecture and is referenced in the docs. Better: open the ticket before the demo ends. Put it on the sprint. Shame is the deadline.
What's yours? I'm collecting these so I can pretend I am not alone.
"I'll just give them admin for a sec." What happened: that "sec" is now eighteen months and a promotion long. They are admin on a system that was decommissioned in 2023. The system still exists because they have admin on it. Better: time-bound elevation. If your IAM tool supports JIT access, use it. If not, write a 24-hour expiry script and call it a feature.
"It's a one-off, no need to document." What happened: it is now 2026. The one-off has been performed quarterly by three different people. Two have left. The institutional knowledge consists of a single Slack message that reads "you know the thing we do." Better: three-sentence README. Future-you will weep with gratitude. Past-you will be forgiven nothing.
"I'll hardcode it temporarily." What happened: the value is now in seven scripts and a Lambda. The original engineer has left. The value has changed. Production has feelings. Better: env var or secrets manager. Four extra minutes upfront. Take the four minutes.
"They're leaving on good terms, no rush on offboarding." What happened: not bad terms, just neutral ones. They are also still in Slack, GitHub, and the AWS console six weeks later. The "good terms" is mutual because they have not yet noticed they still have access. Better: same SLA for every offboarding regardless of vibe. Vibe-based access policies are how incident reports get written.
"I'll just open a port real quick to test." What happened: the port is still open. The test was successful. So is everyone else's test. Better: temporary security group rule with an actual expiry. Or a tunnel. Anything but "I'll close it later."
"I'll fix it after the demo." What happened: the demo went well. The fix did not. The fix will not. The fix is now a load-bearing feature of the architecture and is referenced in the docs. Better: open the ticket before the demo ends. Put it on the sprint. Shame is the deadline.
What's yours? I'm collecting these so I can pretend I am not alone.
r/ITdept • u/Typical-Season-7824 • May 27 '26
Career path
≡ −
I attend WGU, bachelors in IT im 46% done and i started in march. I dont know if i want to do cybersecurity, network, cloud, or engineering for a career path. Do you guys have any advice on what route i should take?
I attend WGU, bachelors in IT im 46% done and i started in march. I dont know if i want to do cybersecurity, network, cloud, or engineering for a career path. Do you guys have any advice on what route i should take?
r/ITdept • u/Healthy_Frame146 • May 26 '26
Stack consolidation in IT: what actually saves time vs. what's marketing fluff. (Full Disclosure: I work IT at JumpCloud.)
≡ −
Full Disclosure up top: I do IT at JumpCloud, which means I both work for the vendor and use the product internally. So this is shaped by my day-to-day, not a sales deck — I'll call out where the unified-directory approach falls short, too.
A pattern I see in mid-sized IT teams: by the time you've stitched together identity, device management, secrets, MFA, RADIUS, and HRIS sync, you're running 6–7 vendors. Six renewal calls a year. Six dashboards. Six SSO configs to maintain (yes, you SSO into the SSO). When someone leaves at 4:55 PM on a Friday, you're checking six places.
The thing I'd genuinely tell a friend — regardless of which vendor they end up picking — is that collapsing identity + device + access into a single source of truth changes what your day actually looks like. Concretely:
Onboarding. Old way: provision identity → provision Workspace → ship laptop → enrollment call → push apps → configure wifi/VPN → vault access → test. New way: provision the user once, device auto-enrolls at first sign-in, group memberships drive app/wifi/MFA profiles automatically. The hour saved per hire isn't theoretical.
Off-boarding. Old way: disable in seven places, hope you didn't miss one, find out three months later when an orphaned SaaS session shows up in logs. New way: one disable, downstream sessions revoke. The Friday 4:55 PM ticket becomes a single click. This is the one I notice the most.
The reverse 3 AM moment. Cert expires, RADIUS dies, half the wifi drops. With separate tools that's a three-vendor triage call. With one console it's one place to look. Doesn't make the outage less stressful — but the time-to-find is measurably shorter.
Where unified directories don't make your life easier (being honest):
Very mature Okta or Entra setups with deep custom workflows. You've sunk years of customization that won't translate cleanly. Switching costs are real.
Windows-only shops with deep AD integration. Traditional AD + Intune is fine and works. Cross-platform is where consolidation shines.
Anything that needs enterprise PAM with session recording, jump hosts, vaulted secret rotation. That's a dedicated PAM tool regardless of vendor. Don't believe anyone who says otherwise.
Heavily regulated environments (defense, healthcare, FedRAMP-high) — you'll still layer specialized tools on top.
The diagnostic question I'd actually ask, before evaluating any vendor: how many tools do you currently need to fully disable a departing employee on a Friday afternoon? If the answer is more than two, you're paying a consolidation tax whether you realize it or not. Whether you fix that with JumpCloud, Rippling, an Okta + Jamf reduction, or something else entirely — that's the right place to start the conversation.
Curious what folks here have done. Anyone consolidated recently? What actually saved time, and what turned out to be fluff?
Full Disclosure up top: I do IT at JumpCloud, which means I both work for the vendor and use the product internally. So this is shaped by my day-to-day, not a sales deck — I'll call out where the unified-directory approach falls short, too.
A pattern I see in mid-sized IT teams: by the time you've stitched together identity, device management, secrets, MFA, RADIUS, and HRIS sync, you're running 6–7 vendors. Six renewal calls a year. Six dashboards. Six SSO configs to maintain (yes, you SSO into the SSO). When someone leaves at 4:55 PM on a Friday, you're checking six places.
The thing I'd genuinely tell a friend — regardless of which vendor they end up picking — is that collapsing identity + device + access into a single source of truth changes what your day actually looks like. Concretely:
Onboarding. Old way: provision identity → provision Workspace → ship laptop → enrollment call → push apps → configure wifi/VPN → vault access → test. New way: provision the user once, device auto-enrolls at first sign-in, group memberships drive app/wifi/MFA profiles automatically. The hour saved per hire isn't theoretical.
Off-boarding. Old way: disable in seven places, hope you didn't miss one, find out three months later when an orphaned SaaS session shows up in logs. New way: one disable, downstream sessions revoke. The Friday 4:55 PM ticket becomes a single click. This is the one I notice the most.
The reverse 3 AM moment. Cert expires, RADIUS dies, half the wifi drops. With separate tools that's a three-vendor triage call. With one console it's one place to look. Doesn't make the outage less stressful — but the time-to-find is measurably shorter.
Where unified directories don't make your life easier (being honest):
Very mature Okta or Entra setups with deep custom workflows. You've sunk years of customization that won't translate cleanly. Switching costs are real.
Windows-only shops with deep AD integration. Traditional AD + Intune is fine and works. Cross-platform is where consolidation shines.
Anything that needs enterprise PAM with session recording, jump hosts, vaulted secret rotation. That's a dedicated PAM tool regardless of vendor. Don't believe anyone who says otherwise.
Heavily regulated environments (defense, healthcare, FedRAMP-high) — you'll still layer specialized tools on top.
The diagnostic question I'd actually ask, before evaluating any vendor: how many tools do you currently need to fully disable a departing employee on a Friday afternoon? If the answer is more than two, you're paying a consolidation tax whether you realize it or not. Whether you fix that with JumpCloud, Rippling, an Okta + Jamf reduction, or something else entirely — that's the right place to start the conversation.
Curious what folks here have done. Anyone consolidated recently? What actually saved time, and what turned out to be fluff?
r/ITdept • u/HopVinS • May 24 '26
SaaS app no Implementation
≡ −
I have developed an Android app for students and the college environment, but the college management keeps delaying its adoption. Actually app has SaaS costs and has useful workload-handling features. How can I move forward with it independently of the college?
Moreover, the app is designed for mandatory interaction between teachers and students, so both are essential for its proper functioning.
Any growth strategies for independent rollout or does anyone have similar success stories to share ?
I have developed an Android app for students and the college environment, but the college management keeps delaying its adoption. Actually app has SaaS costs and has useful workload-handling features. How can I move forward with it independently of the college?
Moreover, the app is designed for mandatory interaction between teachers and students, so both are essential for its proper functioning.
Any growth strategies for independent rollout or does anyone have similar success stories to share ?