Since my migration to Windows 7 there have still been a few things missing that would be nice to have. One of those is the Exchange System Manager tools. There are ways and methods out there to getting this to work but most will involve uninstalling outlook and reinstalling after you have installed ESM tools.
I have been waiting for the ESM tools for Exchange 2010 to hopefully work with Exchange 2003 but that hasn’t happened either. Although I did find a really quick and easy solution this morning after reading the following posts on TechNet (Exchange System Manager for exchange 2003)
You will need to download the Exchange System Manager for Windows Vista then use something like WinRAR to extract the contents.
You will also need to make sure you already have the RSAT tools installed (Remote Server Admin Tools)
Finally open up a Command Prompt as Administrator. Browse to the directory that contains the ESMVISTA.MSI file. Run the following:
ESMVISTA.MSI /q
Once this is done you should be able to open the “Active Directory and Computers” and edit an Exchange User with all the required email tabs.
We have been having an issue with our HP DL160 G5 servers lately. After a BIOS update (and on one occasion it occurred without any other updates, just a power outage and a reboot) when the server boots the system fans spin at top speed (sounds like a jet engine) and the server screen shows
BMC Updating… Please Do No Shutdown or PowerCycle System!
Read more…
I have been having a problem with my redundant PostgreSQL setup over the last couple of weeks. I run two Postgres servers with a WAL Logging Warm Standby system using pg_standby from 8.3. When the master server is under heavy load and generating a lot of WAL traffic the secondary server has been tripping and going active.
After checking all the logs and putting pg_standby in debug mode there was still no clue as to why this was happening.
Read more…
I have a Ubuntu Virtual Server handling all my mail, recently after an apt-get upgrade I was unable to send email using my Postfix Virtual User setup through Courier and SASL.
I kept getting the following error in my logs:
Aug 18 07:53:53 marvin postfix/smtpd[23938]: warning: SASL authentication
failure: cannot connect to Courier authdaemond: No such file or directory
Aug 18 07:53:53 marvin postfix/smtpd[23938]: warning: localhost[127.0.0.1]:
SASL LOGIN authentication failed: generic failure
After consulting with Google for at least an hour i finally hit upon a page that helped me.
Read more…
Monitoring & analysing your PostgreSQL server logs with PgFouine provides you with a way to see which queries are performing badly and need optimisation. It can also provide insight into busy periods and give some basic query stats such as the number of INSERT, DELETE, UPDATE, and SELECT operations.
Read more…