Microsoft Exchange Outlook Web Access - OWA - Can't Log On

I was recently troubleshooting a problem for a client were they couldn't access Outlook Web Access (OWA) from the outside of the network. I turns out the problem was caused by the means of authentication defined in Internet Information Services (IIS) was defined as Windows Integrated Authentication. This allows Windows clients on the Windows domain the ability to login to OWA without a user or password. The authentication is passed to the webserver by Windows. When outside the local network or on a computer not joined to the domain the authentication is not passed.
Solutions:
1. Have the users login using the domainname\username at the login prompt. This is the easiest solution.
2. Using IIS Admin, right click the website properties, click the Directory Security tab, click the Edit button under Anonymous access and authentication control. Add Basic Authentication, click the Edit button and add your Windows domain, and remove the Integrated Windows Authentication check box. There is the warning about passwords being sent in clear text, if that is a concern consider using SSL.

Moving Windows Shares - Windows Server 2000 and 2003

I needed to move user folders from one server to another. I needed to maintain proper file level security permissions, shares, and share permissions. After doing some searching and testing heres how it works.

BACKUP: Use a good backup software. I used Backup Exec. Make sure you back up the file security. What this will do is backup the entire file structure along with the folder / file level permissions but not shares.

RESTORE: Restore the file structure to the new server. In order for this to work properly the folder structure must be in the exact same place. This will put all the files and folders along with their permissions on the new server.

Now that the files and folders have been added to the new server the shares and share permissions need to be migrated.

WARNING: Using Registry Editor incorrectly can cause serious, system-wide problems that may require you to reinstall Windows to correct them. I cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk.

REGEDIT: Open Regedit and drill down to HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Share. With the pointer on the Shares key, right click, and click Export. Name the file with a .reg and put it in a place that you can get to from the other server.

From the new server: Double click the .reg file you created, answer yes to the warnings.

REBOOT: You could restart the server service but I prefer a fresh reboot. The shares with their proper permissions should show up then.

Notes: If you changed the file location you can manually edit the .reg file and correct the paths.