I am moving this blog to WordPress. This is the first part of moving my focus and developing an Adelaide Exchange Server and Directory Services User Group in the near future.
Please update your favourites to point to messagingguy.wordpress.com
I’ll continue to replicate content on here for the next few months
Client had an issue after I migrated them from Exchange 2007 to Exchange 2010 where users on Outlook 2007 were being prompted for authentication. Mail flow would work for the user but they were being prompted for authentication from the autodiscover url.
The fix for the was as follows
Set-ClientAccessServer -Identity CASSERVER -AutodiscoverServiceInternalUrihttps://url.domain.com/autodiscover/autodiscover.xml
Set-WebServicesVirtualDirectory -Identity " CASSERVER \EWS (Default Web Site)" -InternalUrl https://url.domain.com/ews/exchange.asmx
Set-OABVirtualDirectory -Identity " CASSERVER \oab (Default Web Site)" -InternalUrl https://url.domain.com/oab
Set-UMVirtualDirectory -Identity " CASSERVER \unifiedmessaging (Default Web Site)" -InternalUrl https://url.domain.com/unifiedmessaging/service.asmx
The final thing to do is to make sure if you are using a proxy server make sure there is an exception in the proxy list for the url of the autodiscover service
Had an issue today at a clients site where they needed another OWA virtual directory for their SharePoint portal. So I created a new Web Site, added an additional IP address to the existing NIC. I then went into the bindings of the Default Web Site and set it to one of the addresses and then set the other site to the other address. Seems simple enough.
I then opened up the EMS and got this error
“Connecting to remote server failed with the following error message: The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the destination computer. The content type is absent or invalid. For more information, see the about_Remote_Troubleshooting Help topic.”
After making sure time was all good between the CAS and the DC I figured out that setting the web site that contained the PowerShell virtual directory to use All Unassigned as it’s binding resolved the issue.
Here is something that came up at a client site today
EXC01 (2k7 CAS/HT) has an Internal Relay receive connector with allowed relay from x.x.x.0/24 – among others
EXC02 (2k10 CAS/HT) is getting errors when trying to route mail to the 2k7 server “451 4.4.0 Primary target IP address responded with: "451 5.7.3 Cannot achieve Exchange Server authentication." Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts”
What needs to be done is to take the new HT out of the relay list.
Why?
Well the way that I set up my relay connectors
AuthMechanism : Tls, ExternalAuthoritative
PermissionGroups : ExchangeServers
So the problem is the ExchangeServers Permission group that screws it all up. The relay connector see new HT as an Exchange server and so it used the relay connected not the default connector. This starts TLS but when the new HT initiates Integrated authenticated it fails because the relay connector does not have that as an Auth method.
This is the same as what is available online here, always nice to have the offline version on you especially when your at a site you cant get ‘net access and are in a bit of a bind.
Excellent article on this issue in Exchange 2010 and points out why sysprep and unique SID’s are so important
By default Outlook 2003 does not encrypt traffic between itself and the Exchange server it connects to.
With the introduction of Exchange 2010 RPC traffic between the Exchange server and Outlook must be encrypted by default.
To get around this with Outlook 2003 clients you must either use Group Policy to enable RPC encryption or disable the requirement for encryption on all Exchange 2010 CAS servers. To do this run the following common in the EMS.
Set-RpcClientAccess –Server CAS1 –EncryptionRequired $False
Without making one of these changes Outlook 2003 clients will not be able to connect to the Exchange 2010 CAS.
http://msexchangeteam.com/archive/2010/01/29/453908.aspx
Here is the lists of fixes it covers:
KBA 972076 lists all the fixes included in this rollup. Here are some of the product improvements and critical bug fixes we'd like to call out:
sc config NetTcpPortSharing start= auto ServerManagerCmd -ip z:\scripts\Exchange-Typical.xml –Restart
The Exchange Team has announced that Exchange 2010 is now available world wide and is also now available as a trial download
http://msexchangeteam.com/archive/2009/11/09/453096.aspx
http://technet.microsoft.com/en-au/evalcenter/dd185495.aspx
Go get some!
I’ll be starting some Exchange 2010 how-to’s when work settles down a little and I have some spare time in the evening.
I was at a clients site during the week helping them out with some Exchange 2003 issues and was talking to them about Exchange 2007/2010 and one of the things that really got them excited was the way that Exchange 2007/2010 deals with resource mailboxes.
This particular client has had no end of troubles with resource mailboxes. This motivated me to post this blog on how things were and how they are now, and most importantly how to set up your resource mailboxes in Exchange 2007/2010.
The Exchange 2003 Way
This is going to be a fairly brief run down on how to set up and configure resource mailboxes in Exchange 2000/2003
Technique 1 – Manual Configuration
Now that we have set up the basic calendar options we have to set up the mailbox to automatically respond to meeting requests.
Technique 2 – Auto Accept Agent
I could write a whole series of posts on seting up, configuring and troubleshooting AAA but instead I will send you to this TechNet article on how to setup and configure AAA.
Basically AAA automates the above process, this is particularly useful if you have a large number of resource mailboxes and the above technique is going to take a long time to get through.
My personal preference is to use Technique 1 where ever possible as I have had the most success with it and minimal additional configuration after the initial setup.
The Exchange 2007/2010 Way
As usual I will go through both the GUI and Powershell way to perform these tasks – use which ever option you are more comfortable with.
The GUI Way
Powershell Method
Type the following into the EMS
set-mailboxcalendarsettings (New-Mailbox -Name 'Board Room Adelaide Office' -Alias 'SABoardRoom' -OrganizationalUnit 'Exchangelabs.local/Exchange Users' -UserPrincipalName 'SABoardRoom@Exchangelabs.local' -SamAccountName 'SABoardRoom' -FirstName 'Board' -Initials '' -LastName 'Room ' -Database 'EXCHANGE2007\First Storage Group\Mailbox Database' -Room) -automateprocessing:AutoAccept
Additional resource settings
These are a few extra command you can add to the Powershell commands and what they do (taken from TechNet here)
AddAdditionalResponse
The AddAdditionalResponse parameter specifies whether additional information would be sent from the resource mailbox when responding to meeting requests.
This parameter is ignored unless the AutomateProcessing parameter is set to AutoAccept.
AdditionalResponse
Use the AdditionalResponse parameter to specify the additional information to be included in responses to meeting requests.
AddNewRequestsTentatively
Set the AddNewRequestsTentatively parameter to $true to have the Calendar Attendant put new calendar items tentatively on the calendar. If the AddNewRequestsTentatively parameter is set to $false, only existing calendar items are updated by the Calendar Attendant.
AddOrganizerToSubject
Use the AddOrganizerToSubject parameter to specify whether the meeting organizer's name will be used as the subject of the meeting request.
This parameter is ignored unless the AutomateProcessing parameter is set to AutoAccept.
AllBookInPolicy
Use the AllBookInPolicy parameter to specify whether to automatically approve in-policy requests from all users.
AllowConflicts
Use the AllowConflicts parameter to specify whether to allow conflicting meeting requests.
AllowRecurringMeetings
Use the AllowRecurringMeetings parameter to specify whether to allow recurring meetings.
AllRequestInPolicy
Use the AllRequestInPolicy parameter to specify whether to allow all users to submit in-policy requests.
These requests will be subject to approval by a resource mailbox delegate unless the AllBookInPolicy parameter is set to $true.
AllRequestOutOfPolicy
Use the AllRequestOutOfPolicy parameter to specify whether to allow all users to submit out-of-policy requests.
Out-of-policy requests are subject to approval by a resource mailbox delegate.
AutomateProcessing
Use the AutomateProcessing parameter to enable or disable calendar processing on the mailbox.
If this parameter is set to None, both resource booking and the Calendar Attendant will be disabled on the mailbox. If set to AutoUpdate, the Calendar Attendant will process meeting requests and responses. If this parameter is set to AutoAccept, resource booking will be enabled on the mailbox.
BookingWindowInDays
Use the BookingWindowInDays parameter to specify the number of days meetings are allowed to be booked in advance.
BookInPolicy
Use the BookInPolicy parameter to specify a list of users who are allowed to submit in-policy meeting requests to the resource mailbox. Any in-policy meeting requests from these users will automatically be approved.
ConflictPercentageAllowed
Use the ConflictPercentageAllowed parameter to set a conflict percentage threshold for recurring meetings. If the percentage of instances of a recurring meeting that conflict with other meetings exceeds this number, the recurring meeting request will be declined.
DefaultReminderTime
Use the DefaultReminderTime parameter to specify the default reminder time for the meeting requests.
DeleteAttachments
Set the DeleteAttachments parameter to $true to remove attachments from all incoming messages.
This parameter is ignored unless the AutomateProcessing parameter is set to AutoAccept.
DeleteComments
Use the DeleteComments parameter to remove any text in the message body of incoming meeting requests.
This parameter is ignored unless the AutomateProcessing parameter is set to AutoAccept.
DeleteNonCalendarItems
Set the DeleteNonCalendarItems parameter to $true to remove all non-calendar items received by the mailbox.
DeleteSubject
Use the DeleteSubject parameter to remove the subject of incoming meeting requests.
This parameter is ignored unless the AutomateProcessing parameter is set to AutoAccept.
DisableReminders
Use the DisableReminders parameter to specify if you want to disable reminders for meetings in the mailbox.
EnableResponseDetails
Set the EnableResponseDetails parameter to $true to include the reasons for accepting or declining a meeting in the response e-mail message.
EnforceSchedulingHorizon
Use the EnforceSchedulingHorizon parameter to specify whether recurring meetings that have an end date beyond the booking window will be rejected.
ForwardRequestsToDelegates
Use the ForwardRequestsToDelegates parameter to specify whether to forward incoming meeting requests to the delegates defined for the mailbox.
IgnoreDefaultScope
The IgnoreDefaultScope parameter instructs the command to ignore the default recipient scope setting for the Exchange Management Shell and use the entire forest as the scope. This allows the command to access Active Directory objects that are not currently in the default scope. Using the IgnoreDefaultScope parameter introduces the following restrictions:
Instance
The Instance parameter enables you to pass an entire object to the command to be processed. It is mainly used in scripts where an entire object must be passed to the command.
MaximumConflictInstances
Use the MaximumConflictInstances parameter to set the maximum number of conflicts allowed for recurring meetings. If the number of instances for a recurring meeting that are in conflict exceeds this number, the recurring meeting request will be declined.
MaximumDurationInMinutes
Use the MaximumDurationInMinutes parameter to specify the maximum duration allowed for incoming meeting requests.
OrganizerInfo
Set the OrganizerInfo parameter to $true to have resource mailboxes send organizer information when a meeting request is declined because of conflicts.
ProcessExternalMeetingMessages
Use the ProcessExternalMeetingMessages parameter to specify whether to process meeting requests originating outside the Exchange organization.
RemoveForwardedMeetingNotifications
If the RemoveForwardedMeetingNotifications parameter is set to $true, meeting forwarding notifications are moved to the Deleted Items folder after they are processed by the Calendar Attendant.
RemoveOldMeetingMessages
If the RemoveOldMeetingMessages parameter is set to $true, the Calendar Attendant removes old and redundant updates and responses.
RemovePrivateProperty
Set the RemovePrivateProperty parameter to $true to clear the private flag for incoming meeting requests.
RequestInPolicy
Use the RequestInPolicy parameter to specify a list of users who are allowed to submit in-policy meeting requests to the resource mailbox. All in-policy meeting requests from these users will be subject to approval by a resource mailbox delegate.
RequestOutOfPolicy
Use the RequestOutOfPolicy parameter to specify a list of users who are allowed to submit out-of-policy requests.
Out-of-policy requests are subject to approval by a resource mailbox delegate.
ResourceDelegates
Use the ResourceDelegates parameter to specify a list of users who are resource mailbox delegates. Resource mailbox delegates can approve or reject requests sent to this resource mailbox.
ScheduleOnlyDuringWorkHours
Use the ScheduleOnlyDuringWorkHours parameter to specify whether to allow meetings to be scheduled outside work hours.
TentativePendingApproval
Set the TentativePendingApproval parameter to $true to mark pending requests as tentative on the calendar. If set to $false, pending requests are marked as free.
That’s it guys. Have fun!
The Exchange Team announced today (http://msexchangeteam.com/archive/2009/10/08/452775.aspx that the Exchange 2010 code is now complete and will be generally available in early November.
Well done guys, Can’t wait to get my grubby little paws on it!
Posts
All Comments
