In our environment, we have load balanced web servers. There are times where one server may be having an issue, while the others remain up and running with no issue. If you are unfortunate enough to be balanced to the server having an issue, your experience will be less than desirable. To help troubleshoot these issues we would test each server by adding their IP to our hosts file. This isn’t too much of an issue for our IT staff, but for folks that don’t mess with their hosts file regularly it can be very cumbersome. To resolve this, I wrote a script that will change their hosts file for them based on their selection. It was a fun exercise, and hopefully someone will find it useful!
I recently began writing a script to automate tasks when an employee decides to leave RANDA, I may post it in its entirety at a later date. In doing so, I searched for a way to remove all Office 365 licenses assigned to a user. I could find nothing… So I came up with my own!
In our environment, we are often required to deploy code that is distributed among several servers. This code is usually part of a scheduled task that is run multiple times or continuously throughout the day. While I know there are simpler ways to accomplish this goal, I did not like the way the logging looked. So, I designed this script to make logging a bit more customizable! I’ve made the script easier to reuse by implementing variables for the pertinent information. Keep in mind that you will have to modify the token value to accommodate a different number of nested folders, etc.
In a previous article I discussed my need for instant gratification when it comes to replicating my DC’s. I gave an example of a script that would replicate all the DC’s that are manually programmed into it.
Well, here is a solution that will find the DC’s on its own and then update each DC with its respective partner. A much simpler and elegant solution if I do say so myself!
Microsoft has finally made some improvements to the DHCP server role with its introduction of Windows Server 2012. One of the most exciting changes being the ability to make your DHCP servers highly available!
However, upon our testing of this new feature, we found that it does not like DHCP reservations and would cause our reserved IP’s to be listed as BAD_ADDRESS in the scope. This of course prevented those PC’s from obtaining an IP address, rendering them virtually useless! This issue exists in both Load Balanced and Hot Standby modes.
To assign a user Read-Only access to a mailbox from Exchange is not very intuitive… But it’s not difficult by any means.
At RANDA, like many other organizations, we experienced the dreaded flurry of “Reply All” emails after someone sent an email to a Distribution Group that contained all users. We did not want to restrict access to the distribution group, but needed a solution to stop the onslaught of “Thanks”, “Awesome”, “Insert crude joke here”, etc.
To that end, we implemented a couple of Transport Rules that would strip out the distribution group from the To and CC field and add it to the BCC field. This created a system that would allow Reply All on other groups, but eliminate it on the company wide group. If the user clicks Reply All, the reply only goes to the originating user!