Friday, March 26, 2010

Exchange 2007 with 2003 OWA Activesync Error 503

I was receiving this error on our front-end 2003 OWA server, which is connecting to a 2007 mailbox server and has ISA:

HTTP status code: [503]. Verify that the Exchange mailbox Server is working correctly.

I was also receiving this error:

The mailbox server does not allow "Negotiate" authentication to its [exchange] virtual directory. Exchange ActiveSync can only access the server using this authentication scheme.

Users couldnt use their iPhones to connect to Exchange. Indeed Windows authentication and basic authentication were enabled.

I tried everything and ended up rebuilding the Exchange virtual directory by doing:

remove-owavirtualdirectory -identity "server\exchange (default website)"

and recreating it:

New-OWAVirtualDirectory -OwaVersion:Exchange2003or2000 -VirtualDirectoryType Mailboxes -Name "exchange"

Boom.

Tuesday, February 16, 2010

How to Calculate VMware failover capacity

If you are getting insufficient resources to satisfy HA failover messages, check this article out on why and how to fix it. The way they calculate resources is kind of wack.

http://www.vmwarewolf.com/ha-failover-capacity/

Thursday, February 11, 2010

VMware converter with Windows Server 2008 R2

If you try to use vmconverter to import a VM from another virtual center you probably have seen the "unable to determine guest operating system" error.

There is an easy workaround. Change the OS on the VM that you are going to import to Windows 2008 64 BIT. Run the import. Then change it back after the import.

NTP on ESX

I use this document so much that I figured I would post a link to it. I always seem to have issues with my ESX servers losing their time sync via NTP. Here is how to set it up correctly (it will still break) and how to fix it.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1339

Thursday, January 21, 2010

Kill Remote RDP Sessions with Command Line

A great way to kill remote RDP sessions is built into Windows. Do the following:

qwinsta /server:(ServerName)

Write down the session ID

Now to kill it:

rwinsta /server:(servername)

That is it. Works like a charm.

Tuesday, January 12, 2010

SDHolder AD Domain Admin Inherited Permissions

For those of you that have found issues with inherited permissions that you cant seem to get control of, read on. It may be because of the SDHolder object in AD. Here is an excerpt from Microsoft on it.

"Every hour, the Windows 20xx domain controller that holds the primary domain controller (PDC) Flexible Single Master Operation (FSMO) role compares the ACL on all security principals (users, groups, and machine accounts) present for its domain in Active Directory and that are in administrative groups against the ACL on the following object:
CN=AdminSDHolder,CN=System,DC=MyDomain,DC=Com

Replace "DC=MyDomain,DC=Com" in this path with the distinguished name (DN) of your domain.
If the ACL is different, the ACL on the user object is overwritten to reflect the security settings of the AdminSDHolder object (which includes disabling ACL inheritance). This protects these administrative accounts from being modified by unauthorized users if the accounts are moved to a container or organizational unit in which a user has been delegated administrative privilege for the modification of user accounts. Note that when a user is removed from the administrative group, the process is not reversed and must be manually changed."

Tuesday, December 1, 2009

Exchange Top Level Security Permissions

In order to see the top level inherited security permissions in Exchange you have to add the following reg key and restart ESM (Exchange 2003):

Hkey_Current_User/ Software/ Microsoft/ Exchange/ ExAdmin

Create a new Dword Value of "ShowSecurityPage" and give it a value of 1.

Now restart ESM and you will see the security tab at the Exchange org levele