Rambles of Ev

Microsoft Exchange Server hardware virtualization is so popular that it seems as if everyone is moving their entire infrastructure to a virtual server environment. That being the case, I want to discuss some of the issues you may encounter when virtualizing Exchange 2007 mailbox servers.

(more…)

Finally found the solution to fix the “An error occured during a call to Windows Management Instrumentation ID no: 8004100e Exchange System Manager” error. It worked beautifully. I can now fully utilise Message Tracking on my Windows 2000 Exchange server.
I have to give full credit to Luke Edson at http://www.mrtweak.com/exchange-ser…install-script/
In essence, it incompases the solution given by Danielp ealier, but goes a little further. Just run this script:

(more…)

Windows system key combinations

(more…)

This file is used for the “Unknown” devices in a Windows VirtualBox machine. Its the SATA drivers that is missing.

Original Article

So I fought this problem all day long. My Windows XP VMWare image was running like crap. I started to poke around. The first thing I did was to bring up the task manager. Sure enough, my virtual CPU was pegged at around 55-60% when the vm was doing nothing. This is not good!

(more…)

Run the SBSBackup wiz and make your selections as close as possible to what you want (or not, doesn’t really matter what is selected at this point) then fire up NTBackup. Programs, accesories, backup. Cancel the NTBackup wiz (if
it starts in wiz mode, default), go to the backup page and from the ‘job’ menu ‘load selections’. The SBSBackup wiz creates a selection file, Small Business Backup Script.bks in C:\Program files\Microsoft Windows Small Business Server\backup, it is this file you wish to load. Adjust the
selections in NTBackup and save the file.

How to fix Server Error in ‘yourApp’ Application

We get asked about this so much it deserves to be shown here. This error doesn’t mean a lot except that your site is broken. That’s not much help to you figuring out why its broken.

The error page does actually tell you exactly what you need to do to proceed, but for some reason, people don’t read it or think that they should not follow these directions. I remember the first time I ran into this error, and I didn’t follow the directions, so you aren’t alone if that describes you..
Server Error in ‘yourApp’ Application
Step 1:

* Open the web.config file of your application.
* Find ‘customErrors mode=”RemoteOnly” ‘.

Step 2:

Replace “RemoteOnly” with “Off”.
*** It is very important that you use capital “O” and lower case “ff”, as the web.config file is case sensitive, and if you get that wrong, you will continue to get the same error, even if you managed to fix the original error.
Step 3:

Run your application again, and you should now see a different error with the stack trace. This is the same way you would see the error if it was running on your own computer.

For a corrupted Index file, please perform the following steps to try to resolve this issue:

(more…)

From here

1. Stop the default IIS web site.
2. DO NOT SHUTDOWN IIS.
3. Delete both SQL Server 2005 Report Server databases.
4. In Control Panel, click on the Change button for the pertinent SQL Server 2005 install instance.
5. Continue to select Report Server and the option to remove it.
6. Reinstall Reporting Services by running the installer on the SQL Server 2005 disc.
7. Once setup is complete, launch the Reporting Services Configuration tool with the Configuration Tools menu in your Start menu.
8. Fix any red-X items in the list.
9. You should be good to go!

Original article here.

You can make the server execute a script at shutdown time by using the Group Policy Editor, which is an MMC (Microsoft Management Console) snap-in.  I will explain how to use the Group Policy Editor shortly, but first, we need to create the batch file that will shut down the Exchange services.

(more…)