Discussion Locked

Best time to disrupt users, and when to do so?

0 helpful
2 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

When is the best time to disrupt users from their routine and make broad changes?

I'm a newly-appointed SA, and I've jumped into an environment where half the people run with Administrative privileges on the domain. This is obviously problematic for me, but it's also something which can not be fixed in one fell swoop, as there is a lot of single-use, special-use proprietary software on the network which (just as often as not) does not aid itself to a multiuser environment. I really need to get this fixed, but in order to do so, we're talking about a couple hundred pissed off people at a time. I'm currently already operating in a "scramble to fix this or that problem, and hope for a moment to work on a project" mode due to how the network was left for me, and I have experience with such changes on (much) smaller networks and know how disruptive a seemingly "small" change can be, and I don't relish the eventuality of such an event!

We've also got a fairly large building project going where a large percentage of the users will be moving to another facility, and I thought then might be the best time to attempt such a change; things are already disrupted, so what's one more thing, right? I know some people in my position would be tempted to blame it on an external force outside my control, or blame such a change on the move, but I'm not so sure I want to do that.

So, whether it's a large hardware upgrade, workstation upgrade, move from workstations to thin clients - when, and how, is the best way to do it?

I'd appreciate any and all of your thoughts on the matter.

2 replies

by jaqui

When setting up the network in the new building you can put the changes into affect for both locations.

I would tell them that these changes are to improve the network security, which is now a wan with the two offices so it had to be tightened.
[ we know it isn't always a wan, but they won't ;) ]

since you'll have to get new processes in place for smooth operations with the two locations you can make a test network to get everything working and just copy the configuration changes when the move happens.

by charliespencer

If you work for a company that's driven by it's monthly sales numbers, the worst time is the last week of the month when they're rushing to make the monthly quota. If you work for a financial firm, the first and / or last weeks of the month are often bad because of monthly financial reporting.

I always aim for evenings if possible. They're better than early mornings because if something goes wrong you've got a lot more time to fix it or put it back the way it was. If that time slot isn't possible, there's always weekends <>.

For those single-use proprietary apps, line up your support resources before you make any changes. If these are third-party apps, contact the vendors and run your suggested changes by them. Determine their support hours so you aren't making changes when support is unavailable. If the app is used by multiple people, try to get one of them to work with you and determine the effects of the changes before you unleash them on all the users.

This discussion is closed to new replies.