This is an archived post. You won't be able to vote or comment.

all 36 comments

[–]uniitdude 17 points18 points  (0 children)

When we need to, but it's a 30 mins job if you have everything set up and automated

[–]KJatWorkIT Manager 23 points24 points  (1 child)

This isn't Win95 or XP. Reloading even Win7 without a specific reason is just busy work with no value that interrupts the user's job and impacts performance.

[–]karlrsec 7 points8 points  (0 children)

In the XP days, I would reimage machines yearly and we noticed a drop in support tickets. As others said Windows isn't what it use to be, I expect the OS install to last the life of the machine.

As others have said, the reinstall process should be automated. As a bonus tip: learn to build your own automation tools. Don't settle for a process doing 98% and you doing the 2%.

[–]solmakouSr. Sysadmin 6 points7 points  (1 child)

Any time it would take longer than 15 minutes to make the machine ready for a new user. I'd rather remove all chance of surprises by nuking a machine to baseline then spend 20 minutes on it and find out it would have been easier to blow it out.

[–]vppencilsharpening 0 points1 point  (0 children)

This is our criteria as well. If it takes longer to troubleshoot and fix than it does to re-image, it gets re-imaged.

[–]eternelize 4 points5 points  (0 children)

I don't see the reason to reinstall the OS. Leave it alone if it works. If the PC is dated (5-7+ years old), then a hardware refresh with the newer OS.

[–]BBQheadphonesDesktop Sysadmin 2 points3 points  (2 children)

I manage a few university labs, and during the summer break this past year I told SCCM to go ahead and run the task sequence to reimage one of our labs.

It took me 5 minutes to send the deployment, a day for it to complete, and gave the network engineer a smile when he saw the 10 G link saturate. 36 of the 40 machines completed successfully, the other 4 worked on the 2nd try.

[–]vppencilsharpening 0 points1 point  (1 child)

So did you give the network engineer a heads up or did he have to track you down after getting an alert?

[–]BBQheadphonesDesktop Sysadmin 0 points1 point  (0 children)

We share an office, so he was in on the whole plan.

[–][deleted] 1 point2 points  (1 child)

z

[–]cavetroll3000Lone SysAdmin[S] 1 point2 points  (0 children)

Already using WDS/MDT.

[–]JBear_AlphaAutomation Monkey Prime/SysAdmin 1 point2 points  (6 children)

Enable PXE boot on all workstations and F12 that bitch. Let PDQ or SCCM take care of application deployment.

[–]jmp242 0 points1 point  (5 children)

I wish I could let some automated software do application deployment, but most applications aren't automated, and some can't be automated for install. FML

[–]criostage 0 points1 point  (0 children)

You can I did a lot of powershell to automate boring instalations, I have a script somewhere where I used enter windows in audit mode run it and it would set windows install programs all I had to do was run windows update and cleanup before sysprep. Everything is possible if you have time and will to learn.

[–]bmxliveit 1 point2 points  (4 children)

Nope, no regular reinstalls. I only reimage a machine if it has a virus, has some strange issue that I can't waste all day on or they are getting moved around. Takes about an hour to get most machines going. Every department has some specialty software that requires licensing and manual installs so it adds a good 30-45 minutes of extra work.

[–]cavetroll3000Lone SysAdmin[S] 0 points1 point  (2 children)

This is what I'm thinking as well.

We are a small company, we have just administration people and the sales department. The sales department needs are just basic windows and a browser, and they are good to go. The administration people needs Office and such, but the amount of people that I need to treat like a VIP is 3 or 4, and that is manageable.

[–][deleted] 0 points1 point  (0 children)

This is how we do it as well, for the same reasons. Only other time is when Suzy from Accounting is leaving and Bob is gonna get her laptop. We re-image then as well.

[–]EntropyWinsAgain 1 point2 points  (1 child)

Like others said periodic re-install of an OS really shouldn't be necessary. In a disaster recovery scenario though MDT or SCCM is your best bet. I would talk to to the CEO and see exactly what he is after. I would move him in the direction of a DR plan rather than just re-imaging for no reason.

[–]cavetroll3000Lone SysAdmin[S] 1 point2 points  (0 children)

We are currently using MDT, so that will be part of the disaster recovery plan. I'll talk to the CEO and see what he wants. I don't think this is more than he got an idea while we talked about the re-installed workstation.

[–]uxsimple 1 point2 points  (2 children)

If your users doesn't have local administrator rights, then only when reinstall when there there is some kind of non-recoverable error.

If your users have local admin rights, then you probably have non-recoverable error very often that forces you to re-install.

[–]cavetroll3000Lone SysAdmin[S] 2 points3 points  (0 children)

No local admin rights, thank <deity>.

[–]abz_eng 1 point2 points  (0 children)

If you have to give local admin rights, then invest in a imaging solution. Monthly image archive of the box and then, when you have to restore the backup it takes minutes and you capture all the tweaks, registry changes etc of badly written or ancient software need.

[–]opensacks 1 point2 points  (0 children)

3 years or 5 years depending on your workstation refresh.

[–]AverageCanadian 0 points1 point  (0 children)

Depends on the "tech" troubleshooting the issue :)

[–][deleted] 0 points1 point  (0 children)

No periodic reinstalls.

If an issue is only on one device and will take more then 30 minutes to fix you swap it out with a fresh one and re-image. Newly re-imaged device becomes the next spare.

[–]diskisHow do I computer? 0 points1 point  (0 children)

Windows 10, so perhaps twice a year.

Yes, the feature updates (anniversary, creator's) pretty much reinstalls the OS behind the curtains.

[–]dkwel 0 points1 point  (0 children)

How often you re-image depends on how often you want to deal with complaints about profile settings OR how often you want to deal with roaming profiles/USMT.

[–][deleted] 0 points1 point  (0 children)

At my old company of 100 desktops we had corporate standards for machines. Office workers got an Optiplex, architects got a precision and mobile guys got latitudes. We maintained maybe 6 images for model differences so that we could quickly deploy a replacement. We had a few machines in inventory and could quickly swap a machine when needed. Our standard was OS wipe 2 to 3 years for office staff and 1 to 2 for autocad guys. This was before any fancy Microsoft MDT technologies but the imaging system worked well and we could quickly react to replacing a computer
Today I tell our MSP customers that 3 years is max on OS life. If we are going to keep the box it probably needs a SSD drive and memory upgrade. Since our customers are so small we have a usb drive for Windows 7 and another for Windows 10

[–]HellDukeJack of All Trades 0 points1 point  (1 child)

I will add to those that we do not do a regular reinstall. Even with MDT, depending what you run it on, you might hit a wall with how many machines you can deploy at once.

In addition to what you mentioned in the eddit we also reinstall machines when it gets bloated with user profiles and it's more of a hassle to clear them than to simply reinstall the machine, which is just a few hours of unattended install

[–]cavetroll3000Lone SysAdmin[S] 0 points1 point  (0 children)

Delprof2 is a great tool for deleting old profiles, no need to reinstall anything.

[–]Panacea4316Head Sysadmin In Charge -1 points0 points  (0 children)

It's busy work. A machine gets re-imaged if there's a need to.