Exchange services will not start if the 2008 server that exchange is on is the only Domain Controller, it MAY start if there is another DC in the environment
Windows Server 2008 has made TCP/IPv6 the default communication protocol stack over which connections are made by clients connecting to the server that is running Microsoft Exchange. (Exchange is a client of Active Directory)
If you disable or do not configure IPV6 you will have problems communicating with itself.
There are 2 possible solutions to this issue
1. Enable and Configure ipv6 to have a the same address as the IPV4 address Ex “::FFFF:192.168.x.x”
2. Disable IPV6 and modify local “host” file
In this step, %SystemRoot% refers to the local hard disk where the Windows system files are located.
b. Search for the line that contains the term “localhost” by using the CTR+F key combination.
c. Select the whole line and make it a comment by putting a number sign (#) at the beginning and end of the line.
d. Press ENTER and, on the next line, type the following lines to provide the TCP/IPv4 address, hostname, and FQDN name for the Exchange server that is running both the Client Access and Mailbox server roles:
<TCP/IPv4 address> <host name of the computer>
<TCP/IPv4 address> <FQDN of the computer>
e. Click Save, and then close the file. f. Reboot the server
OK not yay ….. its all good until you have to go outside of the built in groups 😉
In case you don’t know “Role Based Access Control” is the new permission model for exchange 2010, it allows you to be granular and specific in your delegation of permissions, which is a great thing but takes a good deal of forethought to get properly configured.
Not for the feint of heart, in fact wouldn’t recommend it unless you have a REAL need it. For most people the defaults(listed on the right) are good enough
The good news is once you do you can simply put your admins into the applicable groups.
So as I’m trying to figure this out here is what I came up with for syntax to give “Site 1 Mail Admins” management permission for users in OU “Site 1”
New-RoleGroup -name “OKC MAIL ADMINS” -Members “Site1 MAIL ADMINS” -Roles “Mail Recipients”, “User options”, “Mail Recipient Creation”, “Mail Enabled Public Folders”, “Distribution Groups”,” –RecipientOrganizationalUnitScope “ex2010/Lab Users/Site 1”
here is the break down
New-rolegroup > the is the RBAC group your creating
-name >(hmm wonder what I should put here…. maybe the name of my new group!)
-Members > can be users or groups, I would highly recommend AD groups
“For better or worse, ExFolders still has the same user interface as PFDAVAdmin, so things will look very familiar. However, there are a few changes I want to highlight.
ExFolders must be run from an Exchange 2010 server – it cannot be run from a workstation as PFDAVAdmin could. It can connect to Exchange 2010 or Exchange 2007, but not older versions.
Remove Item-Level Permissions is gone, because there are no item-level permissions in Exchange 2007 or 2010.
DACL fix functionality is gone. With no WebDAV and no M: drive, non-canonical DACLs should be practically unheard of.
Permissions export format between PFDAVAdmin and ExFolders are compatible.
There are also a few new features:
Folder property imports are now supported. You were able to do folder property exports with PFDAVAdmin, but not imports.
Item property exports are supported – that is, you can export a set of properties from all items in a folder. This feature request has come up again and again for troubleshooting purposes. Item property imports are not supported.
ExFolders supports the new free/busy permissions that were introduced in Exchange 2007 and Outlook 2007.
You can now connect to multiple mailbox stores at the same time, so you can run a batch operation against several mailbox stores or all mailboxes in the org if you need to.”