Exchange 2007 Recreate OWA Virtual Directories

Another issue from the new Exchange 2007 environment: permissions problems in terms of OWA setups. Basically every time one would go to our webmail OWA site, it would give a 404 error, or sometimes it would go through to authenticate but then say the session has timed out. Not good.

The quickest way to fix this is to just recreate the virtual directories. Here’s the low down on how to do just that:

1.) On your exchange server, open up the PowerShell command
2.) Type Get-OwaVirtualDirectory. This will list all of the virtual directories on any of the exchange servers currently in your domain.
3.) Type Remove-OwaVirtualDirectory -identity “owa (Default Web Site)”. This will remove the OWA directory in about 10 to 30 seconds.
4.) Type New-OwaVirtualDirectory -OwaVersion “Exchange2007” -Name “owa (Default Web Site)”. This will create the Virtual Directory again.

If you get an error saying that the IIS Virtual Directory can not be created at line:1 char:24, go into your Exchange Management Console. Under Server Configuration/Client Access make sure that Outlook Anywhere Enabled is set to FALSE for the server you’re trying to recreate the directory.

I found out on our second server that I really don’t need to type with capital letters. and since i’m lazy, i stopped typing with capital letters. thank you!

Exchange 2007 OWA Service Unavailable

Working where I do gives me the opportunity to work with the latest and greatest of technologies.  Exchange 2007 is, in my opinion, a huge improvement over 2003 in terms of speed.  However, it moved too far away from the familiar GUI (like vista did), and therefore some usability has suffered.

Because Exchange 2007 requires 64 bit processors (or at the very least an Intel processor that emulates 64 bit technology), Windows Server 2003 X64 is needed. This means that Exchange will use up as much RAM as it wants to (10 out of 12GB on our server). It also means that .net 1 and .net 1.1 DO NOT work well with it. There are scripts that enable IIS to support 32 bit processes, but who wants to muck up the works with 32 bit and 64 bit processes fighting for resources?

If you accidentally install the Windows update hotfix .net 1.1 on your exchange server (I know I did), then it will automatically convert your nice 64 bit Exchange server into a 32bit mixed-mode Exchange server. Which might not be bad, except for the fact that IIS doesn’t like to mix modes. And that takes me to the point of all this writing – IIS does NOT like 32bit and 64bit.

When the hotfix made Exchange go into mixed-mode, IIS freaked out and stopped supporting OWA (outlook web access). It hosted a site called “Service Unavailable”. Not very creative. And through lots of searching, I came upon a set of instructions that is quite easy and works every time I replicate the issue.

1.) Uninstall Hotfix 1.1. If you really need .net 1 support, you’ll have to look elsewhere. .net2 works just fine. It’ll ask you to reboot the server, which sucks.
2.) Uninstall .net 1.0. Read above if you really require .net 1 support.
3.) On your exchange server, run this from the command line: “%SYSTEMROOT%\Microsoft.NET\Framework64\v2.0.50727\aspnet_regiis.exe -i”
If you get an error indicating that IIS is in 32 bit mode, go to step 4, otherwise go to step 5.
4.) ONLY TYPE THIS IF YOU GOT AN ERROR. “cscript c:\inetpub\adminscripts\adsutil.vbs SET /w3svc/AppPools/Enable32BitAppOnWin64 False”
This will make it so you are in a pure 64Bit environment again. After a couple minutes, go to Step 3 and run that command again (it will pass this time).
5.) Restart IIS. Check your OWA or Exchange web access.

Disable Folder Redirection Synchronization

I came across this issue when we had an employee with a personal computer (that turned into a work computer) leave the company. I had to remove all the work applications and put the computer back to the state it was before we applied all the group policies and such to it.

As a side before we start, I know that I could just reformat the machine and then reinstall the drivers. But that just takes too long. Uninstalling 4 applications, removing the computer from the domain, and performing a few other tasks takes about 15 minutes to accomplish.

Here’s how to disable folder redirection with My Documents synchronization:
1.) Open MMC (Start >> Run >> MMC)
2.) Control M to add a module
3.) Alt D to add the snap-in module
4.) Navigate to Group Policy Object Editor (or a similar name)
5.) Click Add, and then finish (you’ll want it to be on the local machine anyway)
6.) Click Close, then OK
7.) Navigate to Local Computer Policy >> User Configuration >> Administrative Templates >> Network
8.) Disable Synchronize all offline files when loggin on, logging off, and before suspend.
9.) Reboot

Cisco VPN CSGina.dll Failed To Load

Here’s the full error:
The Login User Interface DLL CSGina.dll failed to load. Contact your system administrator to replace the DLL, or restore the original DLL.

This happens when you uninstall, and sometimes install, the Cisco VPN client. Cisco VPN client adds a registry key that disables fast user switching and loads the client before booting into Windows.

The fix below requires editing your registry files. If you have no idea what a registry file is, you probably shouldn’t be editing them. If you edit incorrectly your computer may refuse to boot. Here’s the quick fix:

1.) Reboot the machine
2.) Press F8 to load up the boot options menu for Windows
3.) Select Safe Mode and then select your Windows Installation
4.) After Windows loads into safe mode, it’ll ask if you want to continue working in Safe Mode. Select Yes.
5.) Start >> Run >> “regedit” (without the quotes). Press Enter.
6.) Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\Winlogon
7.) Look for the GinaDLL Key
8.) Select and delete this key. DO NOT delete the entire Winlogon folder of keys.
9.) Close Regedit and reboot the machine

***EDIT***
This is actually the most popular post on it.thelibrarie.com! Awesome!

Linux Show Hard Drive Lifetime Specs

This is a pretty cool tool I came across while doing research for another topic. Basically if you run Linux you can run this tool.

1.) sudo smartctl -a /dev/sda (or in my case it’s hda)

And that’s it. If it gives you an error, try running sudo smartctl by itself. If it says it requires tools to be installed, you can use apt-get install smartmontools.

This will give you all the details as reported by the SMART hardware system built into all newer drives. Total hours in use, power cycles, temperature, recovered errors, failures. Some of the data can be a little bit off (my initial reading of HD temperature was 705757226C) but overall it’s pretty neat.

Ubuntu Broadcom BCM4318 802.11g Laptop Wireless Driver

A fresh install of Ubuntu 7.04 or 7.10 will yield quite a few drivers built in. I’m actually impressed that most of the devices on my laptop work right out of the box (so to speak). Not complaining about Windows too much, but I’m constantly drawn towards Linux because of the support given via hundreds of thousands of individual peoples. Have an issue? Probably it’s been well documented and there are fixes available. If not, someone can most likely help you out. Want to make changes to your OS? Want free software and free support? Linux.

Now that the rant is over with, here’s an issue I came across while installing 7.04 AND 7.10 on my laptop (actually Windows had this issue too, but it’s much easier to find driver support on that side). The problem was my built-in Broadcom wireless 54G card (BCM4318 is the model). I didn’t want to use ndiswrapper to solve this one. I wanted a linux native driver.

BCM43xx Auto Install Driver

This is a debian package script that will install the Linux Native driver. Double click, install, reboot. If the wireless doesn’t work, you may have the wrong Broadcom card installed, or you will have to use ndiswrapper.

EDIT 08042008
Ubuntu 8.04 and beyond actually has built-in support for the Broadcom Card (not quite as good as the NDIS wrapper, but it will connect at 54mbps and has fairly decent range). You can go to System, Administration, Hardware Drivers. It should then be listed as one of the available to use.

Ubuntu Startup Screen Blank Issue

That’s the best description I could come up with. Basically I installed Ubuntu 7.10 on my laptop (Compaq V5000 CTO). After a series of simple updates, I no longer had the booting Ubuntu screen with the progress loading bar. Basically the Grub boot menu will load, but then the screen goes blank for roughly 2 to 3 minutes. Then the login screen for Ubuntu will finally load. After a series of quick google searches, I finally came across the answer:

It’s a resolution issue.

Here’s the fix:
1.) Open up Terminal
2.) CD to /etc/
3.) Nano usplash.conf
4.) Change the resolutions to 1024×768
5.) Save the file
6.) sudo update-initramfs -u -k `uname -r`

It looks like this is an issue mostly found on ATI based computers. So if you have an nVidia based video card, you probably won’t be able to fix this using the above technique (correct me if I’m wrong). After the fix, the boot time went from 2 to 3 minutes down to less than 30 seconds. I’d say that’s a pretty good bug fix.

EDIT 08042008
I’m pretty sure since 804 came out this is no longer an issue.

Ramblings Of An IT Person