I’ve been working a lot with Exchange 2013 recently so will be focusing my next few posts on some PowerShell I have used and found useful to help me setup an Exchange 2013 environment for a new company.
In this post I will look at the process I used to bulk create Contacts.
In this post we’ll look at how to use PowerShell to reduce the size of the WinSxS folder in Windows Server 2012 R2.
A customer has a very quick SSD based server at a cloud provider, but although it is SSD based it only has a tiny 40GB C:, which is a very small footprint for the OS, a couple of apps and logs files. So i was asked to take a look and see what i could do to make a bit of room.
The WinSxS folder contains the files for all the Windows Features you can install in the default operating system. Each time you run a windows update files in the WinSxS folder get update and the size will continue to grow.
Since Windows Server 2012 Microsoft have made it very easy to tidy the WinSxS folder up. They introduced a new feature called “Features on Demand”. Rather than the WinSxS containing all the binaries for all the features you could possibly install on the server, “Features on Demand” allows you to remove the files for features you aren’t using.
If at a later date you want to install a feature you have removed from the WinSxS folder you’ll need to specify a location for the source files.
Following on from 2013’s success, 2014 was a busy blogging year, with 66 posts, 560,000 views and visitors from 218 countries! The OxfordSBSGuy.com blog has gone from strength to strength, there was no major redesign this year but subtle tweaks here and there to make it better. For a hobbyist blog its edging ever closer to the 1,000,000 views mark which is insane!
Looking forward to 2015, I intend to work on some Sophos Certifications while trying to find time for a few more Microsoft exams. I didn’t get around to the SBS migration to Windows / Exchange 2013 last year, but with a number of clients now on the cusp of migrating I’ll be looking at that sooner rather than later! The surprising success if 2014 was my PowerShell posts, these have been hugely popular and enjoyable to write so expect more this year.
In this article we’ll look at using Get-ADComputer and Set-ADComputer to list computer accounts which haven’t logged in for xx days, and then automatically disable them.
In part 1 we looked at how to use Get-ADComputer to list computers by name and sort them by their last logon date with the premise that we can use the information to remove historic computer accounts from the domain.
Now we know the computer accounts we want to work with we will look at modifying the PowerShell command to automatically disable them.
Here is another quick Exchange PowerShell post on distribution groups, in it we will look at how to check and modify a particular setting.
A client recently got in touch after a suspect email was sent to all staff in a particular distribution group. Usually only staff can send emails to distribution groups because you need to be authenticated, so I had a quick check of the distribution group’s settings to see what was going on.