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.
The latest version of Dell Server Update Utility (SUU 14.10.00) has been released. The SUU is an application used to help patch Dell PowerEdge servers. It will compare currently installed drivers and firmware with those available on the DVD or mounted iso file.
OpenManage Essentials 2.0 was released on the 8th September 2014. It adds support for 13th Generation servers, enhancements in search and discovery, deployment of iDRAC service modules, enhanced scalability, additional inventory and reporting plus many more features.
Exchange 2013 SP1 was released in February this year providing support for Windows Server 2012 R2. In this blog we’ll run through the installation process.
The demo environment I am using includes a Windows Server 2012 R2 domain controller and a Server 2012 R2 member server.
In the demo environment no previous versions of Exchange have been installed so as part of the installation the Exchange 2013 SP1 we will upgrade the AD Schema, even if you are running Exchange 2013, the installation of SP1 requires a Schema update. Note in this scenario we are going to jump straight to installing Exchange 2013 SP1, with out installing Exchange 2013 first.
Finally before we start, always test in a demo environment before deploying in Production!
The Shellshock vulnerability in Bash (a command line shell) hit the news last week and has the potential to be far more serious than the Heartbleed bug discovered earlier in the year. The Shellshock bug appears to mostly effect Macs, Linux, Unix, and websites based on Apache, although some network hardware may be effected.
There is a very good technical article that Troy Hunt has published which explains the vulnerability in some depth. You can view it here, as well as many other websites which are covering the story so I won’t go into detail, just type Shellshock into your favourite search engine.
Instead below is a list of the major vendors which we and customers use and links to any articles they have regarding Shellshock and their products.
Watchguard and Draytek have confirmed they have no effected products. Microsoft is also uneffected.
Keep checking back as I will update this as more detials from vendors become available.
If you know of any other Vendor statements regarding the ShellShock bug please add a comment below, and I will incorporate it into the post.