I recently ran into an issue at work where users were having some difficulty changing their passwords via OWA. We just rolled out Exchange and are setting new users up, so it’s pretty important that they be able to reset their passwords after initial setup.
It turns out that OWA can have some difficulty with the Minimum Password Age policy on domain controllers. By default, this is set to one day. Users attempting to change their passwords on the same day that their Exchange accounts were created will be greeted with an error stating “The password supplied does not meet the minimum security requirements. Please contact technical support for your organization if you need help.”
You can read a bit more about the issue in the links below:
Earlier today I was attempting to install the Active Directory Management Gateway service on a new Server 2003 domain controller and I was rewarded with an error stating:
Setup cannot continue because one or more prerequisites
required to install KB968934 failed.
Oh, what fun. Fortunately for me, some kind folks over at Microsoft’s Technet forums had the answer. There are two hotfixes that need to be installed on a Server 2003 SP2 machine before the AD Management Gateway Service can be installed:
I found that downloading these can be a pain. KB969166 requires a Microsoft download manager and KB969429 will only show a 64-bit download if you’re on a 64-bit machine. You must download it from a 32-bit machine if you’re applying it to a 32-bit server. Also, be prepared to restart your server for KB969429.
I recently ran into an issue with the GroupWise 7 client crashing on a new terminal server running Server 2008 R2. The error I received was “This application has requested the Runtime to terminate it in an unusual way.”
Some searching through Novell’s site revealed that this is a known issue with the GroupWise client not playing well with DEP. Sure enough, adding an exception for the GroupWise client in the DEP configuration resolved the issue. For those who are unsure how to do this:
- Right-click on Computer and select Properties.
- Click the Advanced System Settings link.
- Click the Advanced tab.
- Click the Settings button under the Performance section.
- Click the Data Execution Prevention tab.
- Click the Add button under the exceptions list.
- Navigate to the grpwise.exe executable and click the Open button.
- Click the OK button on each dialog to save your changes.
Earlier today I was trying to download a VM from one of our ESX datastores using the Datastore Browser. Unfortunately, the vSphere Client kept crashing with the error “VpxClient has encountered a user-defined breakpoint” after I chose the destination folder. Some quick research turned up a thread on the VMware Community site which highlights the cause: Datastore browser – user-defined breakpoint
…If you close the VI Client and re-open it as administrator the problem appears to go away…
It appears that VMware is not fully finished preparing the vSphere client for UAC elevation, which is pretty sad, considering Vista shipped with UAC over four and a half years ago. It’s unfortunate to see a company as forward thinking as VMware let their client stagnate so much.
A while back I did some experimentation with IPv6 on my Cisco 2611xm. I was using a tunnel provided by Hurricane Electric, which worked well, but I had no firewall and that made me a bit nervous. A little while after I got things set up, I procured a Cisco ASA5505 with a 50 client license via eBay. My hope was that I could use the ASA for the firewall and the router to terminate the tunnel. As it turns out, this would have required a second IP address, because the ASA is not able to pass Protocol 41 traffic.
In my last post I described my experience with upgrading from VirtualCenter 2.5 to vCenter4. Here I’ll be describing the process of upgrading the host machines via a couple of different methods as well as my process for getting the VMs upgraded to the latest verision of VMware’s virtual hardware.
Last week I started our migration from VMWare’s VI3 to vSphere. There are many improvements to the load balancing capabilities as well as the management capabilities. The storage engine has been greatly improved as well. Storage vMotion is available in the GUI without a plugin and thin provisioning is finally available, which is a huge boon and reason enough to make the move on its own. Most of this process can be completed with no downtime for the virtual machines.
I was given a project, recently, that involved creating a spreadsheet to list storage capacities and free space. One thing I wasn’t sure of, was how to format the values.
A bit of searching on the internet for formatting KB MB, etc. came up with a post by Ajay on http://www.eggheadcafe.com which suggested pasting the following code into the current worksheet’s private module:
Private Sub Worksh5eet_Change(ByVal Target As Range)
If Not Intersect(Target, Range("C:C")) Is Nothing Then
If Target.Value < 1000 Then
Target.NumberFormat = "0 B"
ElseIf Target.Value < 999500 Then
Target.NumberFormat = "0.000, KB"
ElseIf Target.Value < 999500000 Then
Target.NumberFormat = "0.000,, MB"
ElseIf Target.Value < 999500000000# Then
Target.NumberFormat = "0.000,,, GB"
Target.NumberFormat = "0.000,,,, TB"
I had some trouble with the macro and eventually abandoned it, but it did give me some ideas. The actual formats were good and I ended up using them later. The criteria for setting the formatting was spot on as well. After thinking about it for a while, I decided to look into Excel’s conditional formatting feature. There are premade rules for changing the cell color, etc., but it turns out that it’s capable of quite a bit more.
If you’re a systems administrator and run Vista, you might have run into some trouble with the server 2003 administration tools package (adminpack). Well, there’s good news for you. Remote administration is now built into the Vista operating system.
Firstly, you should be running service pack 1. I believe the tools are available for the original release of Vista, but I haven’t delved into it.
You’ll need to download the updated RSAT pack from Microsoft:
Microsoft Remote Server Administration Tools for Windows Vista…
Go to the control panel and open “Programs and Features”.
Click on “Turn Windows features on or off.
Find and enable “Remote Server Administration Tools”.
Once you hit OK, your system will spend about 5-10 minutes configuring itself for remote administration and the “Administrative Tools” menu should be populated.
I recently ran into an issue where a WSH script was calling an external executable and returning an exit code of 0 even though there had been an error running the external executable. The problem is that I was relying on
oExec.StdOut.ReadAll() to block the script until the command had finished processing. The
ReadAll() method functions synchronously, so if the executable had been writing to StdOut, I would have been right. Unfortunately, I was neglecting the StdErr stream. So, not only did I miss the errors that the executable threw, the script didn’t block on the executable’s output, so I returned the exit code before the executable had actually finished running. The lesson here is to always think about StdErr no matter what you’re trying to accomplish.