Content Preview: rss
632 days ago
On February 12, 2008 Microsoft will release the Windows Internet Explorer 7 Installation and Availability update to Windows Server Update Services (WSUS). IE 7.0 will be distributed as an Update Rollup package. The update is an installation package that will completely upgrade Windows machines running IE 6.0 to IE 7.0. If you have configured WSUS to "auto-approve" Update Rollup packages, IE 7 will be automatically approved for installation after February 12, 2008 and consequently, you may want to take the actions below to manage how and when this update is installed. You will need to take action if: You use WSUS 3.0 to manage updates in your organization. You have Windows XP Service Pack 2 (SP2)-based computers or Windows Server 2003 Service Pack 1 (SP1)-based computers that have Internet Explorer 6 installed. You do not want to upgrade Internet Explorer 6 machines to Windows Internet Explorer 7 at this time. You have configured WSUS to auto-approve Update ...
632 days ago
Here are a few things to check in your Active Directory before you co-exist Exchange Server 2007 in a Exchange Server 2003 environment. For all your Exchange users and groups, make sure Exchange mailbox alias field does not contain spaces or characters other than a to z (uppercase or lowercase), digits from 0 to 9 , ! , # , $ , % , & , ' , * , + , - , / , = , ? , ^ , _ , ` , { , , } or ~ . One or more periods may be embedded in an alias, but each one of them should be preceded and followed by at least one of the other characters. The @ symbol is not allowed in an alias. For all your Exchange users, make sure the UserPrincipalName (aka Logon name) is "user@domain.com" and not just "user". I have seent that this problem is usually found on users that are created in Active Directory by Cisco Unity. Make sure your display names do not contain leading or trailing white spaces, i.e. the first and last characters in a display name ...
632 days ago
I went ahead to install the mailbox server role on one of the brand new servers commissioned for Exchange Server 2007. The prerequisite checks went OK, and setup began doing the 'real stuff'. Happiness was shortlived, because, towards the end setup showed that it failed. The following error was thrown: An unexpected error has occurred and a Watson dump is being generated: The Exchange server address list service failed to respond. This could be because of an address list or email address policy configuration error. It was running command '$error.Clear(); $count=0; $ExchangeServers = Get-ExchangeServer -DomainController $RoleDomainController; foreach($server in $ExchangeServers) { if(($server.AdminDisplayVersion.Build -gt 641) -and ($server.IsMailboxServer -eq $true)) { $count++; } } if( $count -eq 1) { Set-OrganizationConfig -DomainController $RoleDomainController; }' . I closed the Setup program, and tried to assess what's been done. I could see that Exchange ...633 days ago
After installing Exchange Server 2007 Mailbox server into an Exchange Server 2003 organization, you open Exchange Management Console and navigate to Organization Configuration > Hub Transport > Email Address Policies . You find all the legacy recipient policies that you created in Exchange 2003 over here, but when you try to edit a recipient policy, you get the following error: Unable to edit the specified E-mail address policy. E-mail address policies created with legacy versions of Exchange must be upgraded using the 'Set-EmailAddressPolicy' task, with the Exchange 2007 Recipient Filter specified. So just how do you fix your email address policy? Yup, you will need to use Exchange Management Shell, no matter how much you hate it. First, lets fix the Default policy using the Set-EmailAddressPolicy cmdlet: Set-EmailAddressPolicy "Default Policy" -IncludedRecipients AllRecipients Hit 'Y' when you are asked to confirm the upgrade. If you have ...
