Outlook 2003 Service Pack 3 Clients
Issue:
During normal working hours users randomly was unable to access their mailboxes when they launched their Outlook client.

The users were receiving the following Outlook message:

“Unable to open your default e-mail folders. The Microsoft Exchange Server computer is not available. Either there are network problems or the Microsoft Exchange Server computer is down for maintenance.”
It was also reported that some users had issues expanding additional mailboxes. (Delegate Mailboxes )
The following Outlook message appeared.

Or users have issues opening Shared Calendars.

Solution:
http://support.microsoft.com/kb/2299468

With Get-ThrottlingPolicy you can see the value of RCAMaxConcurrency

(Exchange 2010 RTM default value 20) (Exchange 2010 SP1 default value 214748364)

I changed RCAMaxConcurrency to 214748364 and the problem is fixt:

Get-ThrottlingPolicy | set-ThrottlingPolicy -RCAMaxConcurrency 214748364

1. Get a SAN Certificate.

I my case I have the following URL’s registered with the certificate.
webmail.wardvissers.nl
autodiscover.wardvissers.nl
legacy.wardvissers.nl
casarray.wardvissers.local

2. Import the Certificate in to Exchange 2010. 
How to check HERE

3. Create on the Exchange 2010 Server a Client Access Array.
How you must do it I spoke it Configuring Client Access Array. I this case a used casarray.wardvissers.local for the client acces array.

4. Setting the internal & external url’s

Set-ClientAccessServer -Identity ward-ex01 -AutoDiscoverServiceInternalUri https://casarray.wardvissers.local/Autodiscover/Autodiscover.xml

Set-WebServicesVirtualDirectory -Identity “ward-ex01\EWS (Default Web Site)” -InternalUrl https://casarray.wardvissers.local/ews/exchange.asmx -ExternalUrl https:// webmail.wardvissers.nl/ews/exchange.asmx

Set-OABVirtualDirectory -Identity “ward-ex01\oab (Default Web Site)” -InternalUrl http:// casarray.wardvissers.local/oab -ExternalUrl https://webmail.wardvissers.nl/oab

Enable-OutlookAnywhere -Server ward-ex01 -ExternalHostname “webmail.wardvissers.nl” -ClientAuthenticationMethod “Basic”-SSLOffloading:$False

Set-ActiveSyncVirtualDirectory -Identity “ward-ex01\Microsoft-Server-ActiveSync (Default Web Site)” -InternalURL https://casarry.wardvissers.local/Microsoft-Server-Activesync
-ExternalURL https://webmail.wardvissers.nl/Microsoft-Server-Activesync

Set-ECPVirtualDirectory –Identity ward-ex01\ECP (default web site) -InternalURL https://casarry.wardvissers.local/ECP -ExternalURL https://webmail.wardvissers.nl/ECP

5. Configure Exchange 2010 for basic authentication

Set-OwaVirtualDirectory -id ward-ex01\* -BasicAuthentication $true -WindowsAuthentication $true -FormsAuthentication $false

set-WebServicesVirtualDirectory -Identity “ward-ex01\EWS (Default Web Site)” -WindowsAuthentication $true -BasicAuthentication $true

set-EcpVirtualdirectory –Identity ward-ex01\ECP (default web site) -BasicAuthentication $true -WindowsAuthentication $true -FormsAuthentication $false

set-OabVirtualDirectory -Identity “ward-ex01\oab (Default Web Site)” -WindowsAuthentication $true -BasicAuthentication $true

set-ActiveSyncVirtualDirectory -Identity “ward-ex01\Microsoft-Server-ActiveSync (Default Web Site)” -BasicAuthentication $true

6. Import the SAN certificate in to the TMG server.

1. Click Start –> Run –> Type MMC
2. Click File –> add remove Snap-in –> Certificates –> ADD –> Computer account-> Next –> finish-> ok
3. Click Personal –> certificates
4. Right Click certificates –> all task –> import –> next –> select the *.pfx file –> next –> Password –> next –> next –> Finish

7. Publish OWA

1. Publish Exchange Web Client Access

2. Exchange Publishing rule name: OWA 2010

3. Choose Exchange Server 2010 & Outlook Web Access

4. Next ( I have only Single TMG Server)

5. Next

6.Internal Site Name: Client Access Array name. My Case casarray.wardvissers.local

7. Public Name: webmail.wardvissers.nl

8. At this moment I have no Web Listener so we gone create them

9. Weblister Name: HTTPS

10. Next

11. I choise for All Networks (and local host) because the Server has one NIC.

12. Select the Certificate that you just imported.
 

13. Choise for LDAP (Active Directory)

14. SSO Domain name: my case wardvissers.nl (External Domain name)

15. Finish

16. Next

17. Next

18. Next

19. Finish

8. Publish Active Sync

1. Publish Exchange Web Client Access

2. Exchange Publishing rule name: Active Sync 2010

3. Exchange Server 2010 & Exchange ActiveSync

4. Next

5. Next

6. Internal Site name: CasArray name

7. Public Name: I my case webmail.wardvissers.nl

8.Choise the HTTPS web listerner

9. Next

10. Next

11. Finish

Next Time I will publish how to deploy a Legacy Exchange Server 2003 & 2007 with TMG

The List with fixes:
972186 Some functions do not work if you install Security Configuration Wizard on a Windows Server 2008 SP2-based Exchange Server 2007

979046 Attachments are empty when you save them by using OWA after you have applied the update of KB 958881 on an Exchange Server 2007

980038 The Microsoft Exchange System Attendant service crashes intermittently in the Oabgen.dll module on an Exchange Server 2007 server

981602 Event ID: 4999 is frequently generated in a mixed Exchange Server 2007 and Exchange Server 2003 environment

982476 The Imap4.exe process crashes intermittently on an Exchange Server 2007 server

982478 Notes URL links in a plain text message are not clickable when you open this message by using OWA in an Exchange Server 2007 environment

2028675 The MSExchangeFDS.exe process occupies lots of memory if there are thousands of OABs created on an Exchange Server 2007 server

2029086 Some characters of an email message are displayed in an incorrect text size when you access your mailbox by using OWA in Exchange Server 2007

2032216 The Microsoft Exchange Information Store service crashes on an Exchange Server 2007 server when you start it or try to mount certain databases

2121536 Exchange Server 2007 cannot index a message

2201236 The "All Day" field is marked with "No" when you access a meeting request that has a duration time that is more than 24 hours by using a mobile client through ActiveSync in an Exchange Server 2007 environment

2203212 Certain mailboxes cannot be moved from an Exchange Server 2007 server to an Exchange Server 2010 server

2210042 A sub contact folder is still visible after you set the "PR_ATTR_HIDDEN" attribute to "True" in an Exchange Server 2007 environment

2230824 The Microsoft.Exchange.POP3.exe process or the Microsoft.Exchange.Imap4.exe process may crash after you enable protocol logging for POP3 or IMAP4 on an Exchange Server 2007 server

2249814 You receive misleading information when you run the "New-TestCasConnectivityUser.ps1" script on an Exchange Server 2007 server

2263342 "The operation failed" error message in Outlook client when a user sends a recurring meeting request with an email message attachment in an Exchange Server 2007 SP2 environment

2276439 (http://support.microsoft.com/kb/2276439/ ) The Microsoft.Exchange.IMAP4.exe process crashes when an IMAP4 client retrieves a meeting request that includes exception attachments in an Exchange Server 2007 environment

2280234 "Your POP3 server has not responded in 60 seconds." error message when a POP3 client connects to an Exchange Server 2007 Client Access server to access an Exchange Server 2003 mailbox

2282570 "550 5.1.3" NDR message when an Exchange Server 2007 user sends an email message to a recipient

2265306 The Exchange Information Store service stops responding when you perform a search operation on an Exchange Server 2007 mailbox in Outlook

2282746 The "Private" sensitivity status of an occurrence of a recurring meeting request is lost when you edit the occurrence in OWA in an Exchange Server 2007 environment

2286782 The response details are still included in the response email message when you set the "EnableResponseDetails" property to "False" in an Exchange Server 2007 environment

2290105 A shared document cannot be open by using OWA after you install Exchange Server 2007 SP3 on an Exchange Server 2007 server

2290159 The POP3 service crashes on an Exchange Server 2007 server

2344372  You cannot move mailboxes to an Exchange Server 2007 server

2362371 You receive a "Success" response when using the Test-Mailflow command on an invalid or nonexistent external email address in an Exchange Server 2007 environment

2384754 "Unable to identify local server row in Replication state table for this FID" error message when you run the Information Store Integrity Checker tool on an Exchange Server 2007 server

2387915 The ESEBack component does not support ETL tracing on an Exchange Server 2007 server

2388057 The Exchange Transport service crashes on Exchange Server 2007 servers in a mixed Exchange Server 2007 and Exchange Server 2010 environment

2394731 An HTML attachment of a shared mailbox cannot be saved when you set the "BypassOwaHTMLAttachmentFiltering" setting to "True" in an Exchange Server 2007 environment

2424499 Exchange Server 2007 does not support to assign a mailbox with the "Send on behalf" permission of a security group in the EMC or in the EMS

2427297 The created time and the modified time of an attachment are incorrect when you save an email message on an Exchange Server 2007 mailbox

2430674 The "Leave message intact" method in a Folder Assistant rule does not work when you post an item by using OWA in an Exchange Server 2007 environment

Download the hotfix HERE

If your are an Exchange Admin I can recommend the following book Microsoft Exchange Server 2010 Best Practices. It covers SP1. It  contains the following Chapters.

Part I  Preparing for Exchange Server 2010

Chapter 1: Introducing Exchange Server 2010

Chapter 2: Exchange Deployment Projects

Chapter 3: Exchange Environmental Considerations

Part II  Designing Exchange Server 2010

Chapter 4: Client Access in Exchange 2010

Chapter 5: Routing and Transporting

Chapter 6: Mailbox Services

Chapter 7: Edge Transport and Messaging Security

Chapter 8: Automated Message Processing, Compliance, and Archiving

Chapter 9: Unified Messaging

Chapter 10: Federated Delegation

Chapter 11: Designing High Availability

Chapter 12: Backup, Restore, and Disaster Recovery

Chapter 13: Hardware Planning for Exchange Server 2010

Part III  Upgrading to Exchange Server 2010

Chapter 14: Upgrading from Exchange Server 2003 and Exchange Server 2007

Part IV  Deploying and Managing Exchange Server 2010

Chapter 15: Preparing for a Deploying Exchange Server 2010

Chapter 16: Managing Exchange

Chapter 17: Operating and Troubleshooting Exchange Server 2010

This book is also not a preparation guide for Exam 70-662: TS: Microsoft Exchange Server 2010, Configuring, or Exam 70-663: Pro: Designing and Deploying Messaging Solutions with Microsoft Exchange Server 2010, even though when you apply the knowledge and experience covered in this book, it will help you to pass these exams.

2028967 Event ID 3022 is logged and you still cannot replicate a public folder from one Exchange Server 2010 server to another

2251610 The email address of a user is updated unexpectedly after you run the Update-Recipient cmdlet on an Exchange Server 2010 server

978292  An IMAP4 client cannot send an email message that has a large attachment in a mixed Exchange Server 2010 and Exchange Server 2003 environment

982004 Exchange Server 2010 users cannot access the public folder

983549 Exchange Server 2010 removes the sender’s email address from the recipient list in a redirected email message

983492 You cannot view updated content of an Exchange Server 2010 public folder

Download Rollup 1 for Exchange Server 2010 SP1 HERE

Solution is really simple:

1- Browse to "%windir%\system32\" and copy gpedit.msc
2- Browse to "%windir%\syswow64\" and paste gpedit.msc
Now it works again

Well, let us first list the directories that are used in the Exchange web service:

EWS is used for OOF, Scheduling assistance and free+busy Lookup.
OAB provides offline address book download services for client.
Autodiscover is used to provide users with autodiscover service.
EAS provides ActiveSync services to Windows Mobile based devices.
OWA provides outlook web access for users.
ECP provides Exchange control panel feature for Exchange 2010 users only.

Issues that might be resolved using the troubleshooting steps here:

You cannot set the OOF using outlook client, you receive the server not available error.
You cannot view free/busy information for other users.
You cannot use scheduling assistance, also you might receive not free/busy information data retrieved.
You cannot download Offline Address book errors.
You cannot use autodiscover externally.
Certificate mismatch error in autodiscover, users prompted to trust certificate in outlook 2007/2010.

First let us start by settings the right virtual directory configuration required for Exchange 2010 to work correctly:
Configure External and Internal URLs for OWS, ref: http://technet.microsoft.com/en-us/library/bb310763.aspx

You have to configure the internal URL to be the server name. In case you have multiple cas/hub servers configured in a NLB then can use the nlb cluster name for the internal url. 
External URL will be the URL used by users to access webmail e.g. https://webmail.wardvissers.nl/owa 

Configure the autodiscover internal URL, ref: http://technet.microsoft.com/en-us/library/bb201695.aspx

You will use the powershell cmdlet : Set-ClientAccessServer –Identity <CAS Server Name> -AutoDiscoverServiceInternalUri: <Internal URL>, this FQDN must match the URL included in the certificate. If you have NLB cluster then you put the internal name here like nlbek10.wardvissers.local

If you cannot use autodiscover.wardvissers.nl internally (you have a domain name of domain.local and you must use it), you will get a certificate miss match error, you will have to include the internal name in the SAN certificate if you purchase an external SAN certificate. 

You cannot set autodiscover external URL since outlook will try to access https://autodiscover.wardvissers.nl/autodiscover/autodiscover.xml, this behavior is by design and cannot be changed.

Best Practice: Use SAN Certificates

Depending on how you configure the service names in your Exchange deployment, your Exchange server may require a certificate that can represent multiple domain names. Although a wildcard certificate, such as one for *.wardvissers.nl, can resolve this problem, many customers are uncomfortable with the security implications of maintaining a certificate that can be used for any sub-domain. A more secure alternative is to list each of the required domains as SANs in the certificate. By default, this approach is used when certificate requests are generated by Exchange.

Best Practice: Use the Exchange Certificate Wizard to Request Certificates

There are many services in Exchange that use certificates. A common error when requesting certificates is to make the request without including the correct set of service names. The certificate request wizard in the Exchange Management Console will help you include the correct list of names in the certificate request. The wizard lets you specify which services the certificate has to work with and, based on the services selected, includes the names that you must have in the certificate so that it can be used with those services. Run the certificate wizard when you’ve deployed your initial set of Exchange 2010 servers and determined which host names to use for the different services for your deployment.

Which Names you must include when you use a third party SAN certificate, ref http://technet.microsoft.com/en-us/library/dd351044.aspx:
External:
webmail.wardvissers.nl
autodiscover.wardvissers.nl
legacy.wardvissers.nl (If you migrating from 2003 to 2010)
Internal:
autodiscover.wardvissers.local
legacy.wardvissers.local
nlbek10.wardvissers.local(Internal NLB CAS/HUB Cluster)
casarray.wardvissers.local(I use this address for the casarray. It has the same ip as the nlbek10)

1. Click Start, point to Programs, point to Administrative Tools, and then click Internet Services Manager.  
2. Right-click the default Web site, point to New, and then click Virtual Directory.
3. In the Virtual Directory Creation wizard, type IISADMPWD in the Alias box, and then click Next.
    
4. In the Directory box, type c:\windows\system32\inetsrv\iisadmpwd or the location where your hard disk is your default hard disk, and then click Next.
   
5. Verify that only the Read and Run script check boxes are selected, such as the ASP check box, click Next, and then click Finish.
    
6. Verify that the IISADMPWD virtual directory has only basic authentication is set
   
7. If you use Windows 2003/IIS 6.0, verify that the application pool is set to MSExchangeOWAAppPool
    
8. Register the IISpwchg.dll file in the Iisadmpwd directory:
   Click Start, and then click Run.
   In the Open box, type the following, and then press ENTER:
   regsvr32 c:\windows\system32\inetsrv\iisadmpwd\iispwchg.dll
9. Configure the PasswordChangeFlags property in the metabase to make sure that the Password Change functionality is enabled:
   Click Start, and then click Run.
   In the Open box, type cmd, and then press ENTER.
   Locate the C:\Inetpub\Adminscripts directory.
   Type the following command, and then press ENTER:
   cscript.exe adsutil.vbs set w3svc/passwordchangeflags 1

   0: This is the default value. This value indicates that you must use a Secure Sockets Layer (SSL) connection when you change the password.
   1: This value permits password changes on non-secure ports. This value is useful if SSL is not enabled.
   2: This value disables the Password Change functionality.
   4: This value disables the advance notification of password expiration.

10. Do not forget to enable Active Server Pages.
     
    Source http://support.microsoft.com/kb/297121

KB 982639 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 starting with 5 improvements we made to prevent crashes in very unique scenarios.

• KB 980852 The RpcClientAccess process on an Exchange Server 2010 server crashes when you access a mailbox by using a MAPI application
• KB 979801 An error message is generated in Exchange Server 2010 when you use Exchange Troubleshooting Assistant
• KB 980364 The Exchange Transport service on an Exchange Server 2010 server crashes when a certain message is processed
• KB 980353 A MAPI application that is used to access Exchange Server 2010 mailboxes crashes when the application accesses an address book
• KB 979790 An IMAP4 client crashes when accessing an Exchange Server 2010 mailbox

We corrected a few replication issues some of you encountered.

• KB 980149 The Add-MailboxDatabaseCopy command fails when it is used to add a database copy to a Database Availability Group in an Exchange Server 2010 environment
• KB 981961 Event ID 4033 is logged and the Free/Busy replication from an Exchange Server 2003 server to an Exchange Server 2010 server fails
• KB 979921 You cannot replicate a public folder from one Microsoft Exchange Server 2010 server to another, and Event ID 3079 is logged on the target server

Important:
Microsoft Update does not detect Update rollups on Exchange Server 2010 Mailbox servers that are part of a database availability group (DAG).

Download Rollup 4 for Exchange 2010 HERE

The KMS host that is used is very probably a Windows Server 2008 KMS host that cannot standard activate Windows 7 and 2008 R2 machines.

When you do not have Windows Server 2008 R2 KMS host key have then you must have a Volume License agreement so that your request your Windows 7 and Windows 2008 R2 kms keys.

Resolution

Step 1:
-If the KMS host a Windows Server 2003 SP2 machine is you have the update from the KB article KB968915 install and restart the machine.
-If the KMS host a Windows Server 2008 SP2 machine is you have the update from the KB article KB968912 install and start the new machine.
-If the KMS host one Windows Server 2008 R2 machine is you have to install any further update.

Step 2:
You the new KMS host key import now. The commands are as follows:

1. Uninstall KMS license Key on host – slmgr.vbs /upk

2. Install Windows Server 2008 R2 KMS license key – slmgr.vbs /ipk <Your Key>

3. Activate KMS server online: slmgr.vbs /ato

4. Net Stop slsvc

5. Net Start slsvc

The clients can now activate

1. Installing latest DFS Hotfix on servers where Distributed File System (DFS) technologies is installed
2. Dfsutil root export \\domain\namespace path\filename.xml
3. Remove all Namespace Servers
4. Dfsutil root remove \\domain\namespace
5. Dfsutil root adddom \\server\namespace v2
6. Dfsutil root import merge path\filename.xml \\domain\namespace
7. Add all Namespace servers
8. Tuning replication performance in DFSR (especially on Win2008 R2)

Download the beta now at https://connect.microsoft.com/site14/Downloads/DownloadDetails.aspx?DownloadID=8689

MDT 2010 Update 1 provides new capabilities, such as:

· Support for Microsoft Office 2010.

· A new User-driven Installation (UDI) deployment method (formerly known as “Modena”) for Microsoft System Center Configuration Manager 2007. UDI gives information technology (IT) staff control over the deployment experience while empowering users to interact with and customize their operating system deployment through an easy-to-use wizard.

· Improvements to the Deployment Workbench driver import process, detecting each driver’s true supported platforms.

· Many bug fixes and other small improvements.

This release supports the deployment of the Windows® 7; Windows Vista®; Windows XP; Windows Server® 2008 R2; Windows Server 2008; and Windows Server 2003 operating systems. See the Microsoft Deployment Toolkit Documentation Library, which is included with MDT 2010 Update 1, for the complete documentation for this release.

• Verify an application’s compatibility with a new version of the Windows operating system, or a Windows Update, including determining your risk assessment.
• Become involved in the ACT Community, including sharing your risk assessment with other ACT users.
• Test your Web applications and Web sites for compatibility with new releases and security updates to the Windows® Internet Explorer® Internet browser.

Software Requirements:

Download HERE

Knowledge Base Article

Name

Date

Required?

KB974598

“You receive a "Stop 0x0000007E" error on the first restart after you enable Hyper-V on a Windows Server 2008 R2-based computer”

10/1/2009

Yes, if you encounter this error and your server uses a “C-state” (lower power state) that is supported by the processor, but is not supported by Hyper-V.

KB974909

“The network connection of a running Hyper-V virtual machine is lost under heavy outgoing network traffic on a Windows Server 2008 R2-based computer”

10/21/2009

No.

KB975354

“A Hyper-V update rollup package is available for a computer that is running Windows Server 2008 R2”

11/10/2009

Yes, if you are running a backup or restore solution.

KB975530

“Stop error message on an Intel Xeon 5500 series processor-based computer that is running Windows Server 2008 R2 and that has the Hyper-V role installed: "0×00000101 – CLOCK_WATCHDOG_TIMEOUT"

11/20/2009

Yes, if you are running Hyper-V on the affected hardware.

KB974672

“Virtual machines stop responding (hang) during startup and the Vmms.exe process crashes on a Windows Server 2008 R2 computer that has the Hyper-V role installed“

10/14/2009

No.

KB977894

“MS10-010: Vulnerability in Windows Server 2008 Hyper-V could allow denial of service”

2/9/2010

Yes.

KB980856

“Stop error in Windows Server 2008 R2: "0x000000CA PNP_DETECTED_FATAL_ERROR"”

3/12/2010

Yes, if you store VHDs on non-PNP disks.

KB981618

“The computer stops responding or restarts during the Hyper-V Live Migration process in Windows Server 2008 R2” (relates to AMD Errata 383)

3/27/2010

Yes, if you are running Hyper-V on AMD processors.

KB 981836

“Network connectivity for a Windows Server 2003-based Hyper-V virtual machine is lost temporarily in Windows Server 2008 R2”

4/28/2010

Yes, if the server running Hyper-V has a virtual machine that is running Windows Server 2003.

KB981791

“"STOP: 0x0000001a" error message on a computer that has an Intel Westmere processor together with the Hyper-V role installed on Windows Server 2008 or on Windows Server 2008 R2”

5/5/2010

Yes, if you are running Hyper-V on Intel Westmere processors.

Source: http://technet.microsoft.com/en-us/library/ff394763(WS.10).aspx

You can use MAP to inventory the following platforms:

• Windows 7
• Windows Vista
• Windows XP® Professional
• Windows Server 2008 or Windows Server 2008 R2
• Windows Server 2003 or Windows Server 2003 R2
• Windows 2000 Professional or Windows 2000 Server
• VMware ESX
• VMware ESXi
• VMware Server

Reporting
- Identification of currently installed Windows client operating systems, their hardware, and recommendations for migration to Windows 7 and Windows Vista. The tool also reports if desktops have anti-virus and anti-malware programs installed and if the Windows Firewall is turned on.
- Identification of currently installed Windows Server operating systems, their hardware, and recommendations for migration to Windows Server 2008 R2 and Windows Server 2008.
- Identification of currently installed Microsoft Office software and recommendations for migration to Microsoft Office 2007.
- Detailed assessment and reporting of server utilization gathered using the Performance Metrics Wizard.
- Recommendations for server consolidation and virtual machine placement using Hyper-V
- Assessment of client machines, servers, and the technology environment for the implementation of Microsoft Application Virtualization (APP-V)
- Identification of machines where Microsoft SQL Server components are installed.
- Identification of virtual machines, their hosts, and details about each.
- Identification of Windows Server Roles

Hardware Requirements:
- Windows 2003 x86/x64 or Windows 2008 x86/x64
- 1,5 GB (2 GB 2008)

Software Requirements:
- NET Framework 3.5 SP1
- Windows Installer 4.5
- Microsoft Office Word 2007 or Word 2003 SP2
- MIcrosoft Office Excel 2007 or Excel 2003 SP2
- SQL Server 2008 Express Edition, SQL Server 2008, or SQL Server 2005

Download Microsoft Assessment and Planning (MAP) Toolkit HIER

Het overzicht wat er allemaal gefixt is:
"451 4.4.0 DNS Query Failed" status message in an Exchange Server 2007 Edge Transport server

Later updates do not match a calendar item that an Exchange Server 2007 user updates by using Exchange ActiveSync on a mobile device

You receive an "0x800423f0" error message when you perform system state backups on the passive node of Windows Server 2008-based Exchange Server 2007 CCR clusters

An external recipient misses the last occurrence of a recurring meeting request or a recurring appointment that is sent from an Exchange Server 2007 user

The Edgetransport.exe process crash when it process meeting requests in Exchange Server 2007

The subject of a confirmation message is garbled for certain languages when a remote device wipe operation is performed in Exchange Server 2007

The sender address of a forwarded meeting request does not include "on behalf of" as expected in an Exchange Server 2003 organization and an Exchange Server 2007 organization mixed environment

A SSL certificate validation error is generated on an Exchange Server 2007 server when you run any test commands after you run the Test-SystemHealth command

A mailbox that was moved from an Exchange Server 2007 server to an Exchange Server 2010 server cannot be accessed by using Outlook

The Microsoft Exchange Information Store service stops responding on an Exchange Server 2007 server

The synchronization and the reconciliation between Microsoft Office Outlook and a BlackBerry mobile device fails when a mailbox is moved around between two Exchange Server 2007

The Microsoft Exchange Information Store service crashes on a Microsoft Exchange Server 2007 server when a user tries to access a specific calendar item

Read items are marked incorrectly as unread items in an Exchange Server 2007 public folder

A delegate cannot save three settings of Resource Settings for an Exchange Server 2007 resource mailbox in OWA

You receive an error message when you use ExBPA to schedule a scan on an Exchange Server 2007 SP2 server

The store.exe process hangs on an Exchange Server 2007 server

Downloaden doe je HIER

De Onderwerpen:

Exchange
- High Availability in Exchange 2007
- Message Hygiene in Exchange Server 200731
- Using Exchange 2007 for Resource Booking
- Controlling Email Messages using Exchange’s Transport Rules
- Exchange 2007 Mailbox Server Clustering
- Top Tips for Exchange Admins
- Exchange Database Technologies
- Message Classifications in Exchange 2007
- Deploying Exchange 2007 on Windows Server 2008
- Exchange Server Log File Replay
- Configuring Exchange Server 2007 to Support Information Rights Management
- Reporting on Mobile Device Activity Using Exchange 2007 ActiveSync Logs
- Online Exchange Backups
- Optimizing Exchange Server 2007
- Exchange: Recovery Storage Groups
- Exchange E-mail Addresses and the Outlook Address Cache
- Upgrading to Exchange Server 2007
- Goodbye Exchange ExMerge, Hello Export-Mailbox
- Determining MS Exchange Disk Performance
- Upgrading to Exchange Server 2007: Part 2
- Message Tracking in Exchange 2007
- Third Party High Availability and Disaster Recovery Tools for Microsoft Exchange Server
- Exchange Server 2010 – The First Public Beta Version
- Emulating the Exchange 2003 RUS for Out-of-Band Mailbox Provisioning in Exchange 2007
- Using Exchange 2007 Transport Rules to Protect the First Entry in the Address Book
- Cluster Continuous Replication Network Design
- Building an Exchange Server 2007 environment
- An Introduction to Messaging Records Management
- Installing Hyper-V and Beyond
- Restricting Outlook Client Versions in Exchange 2007
- Using Twitter and PowerShell to Find Technical Information and Join a Community
- Update: Exchange Server 2010 Release Candidate
- Exchange backups on Windows Server 2008
- Moving to Office Communications Server 2007 R2
- Monitoring and Scheduling Exchange 2007 Database Online Maintenance
- Exchange 2010 High Availability
- Implementing Cluster Replication – Part 1
- The Active Directory Recycle Bin in Windows Server 2008 R2
- Using Group Policy to Restrict the use of PST Files
- Introduction to Exchange Server 2010
- The Ego and the System Administrator
- Implementing Windows Server 2008 File System Quotas
- Implementing Cluster Continuous Replication, Part 2
- Active Directory Management with PowerShell in Windows Server 2008 R2
- Upgrade Exchange 2003 to Exchange 2010
- Customizing the Outlook Address Book

General Articles
- A SysAdmin’s Guide to Change Management
- A SysAdmin’s Guide to Users
- Change Management – What It Is and Why You Need It
- Manage Stress Before it Kills You
- Hiring System Administrators
- Increase Your Value as a Professional in the Technical Industry
- The Art of Dealing with People

Virtualization
- Virtual Exchange Servers
- Virtualizing Exchange: points for discussion
- Build Your Own Virtualized Test Lab
- A Beginner’s Guide to Virtualizing Exchange Server – Part 1
- A Beginner’s Guide to Virtualizing Exchange Server – Part 2
- Windows Server Virtualisation: Hyper-V, an Introduction
- Increasing the Availability of Virtualized Applications and Services
- Microsoft Hyper-V Networking and Configuration – Part 1

Unified Messaging
- An Introduction to Unified Messaging
- Moving to Office Communications Server 2007 R2

PowerShell
- Managing Exchange 2007 Mailbox Quotas with Windows PowerShell
- So You Thought PowerShell Was Only For Exchange 2007

Downloaden klik op het boek

977633 Certain third-party IMAP4 clients cannot connect to Exchange Server 2003 mailboxes through an Exchange Server 2010 CAS server

979431 The POP3 service crashes when a user connects to a mailbox through the POP3 protocol and the user is migrated from an Exchange Server 2003 server to an Exchange Server 2010 server

979480 Users cannot receive new messages if they access mailboxes that are moved to another Exchange Server 2010 RU1 server by using IMAP4 clients

979563 Exchange Server 2010 Push Notifications does not work

979566 A 0×85010014 error is generated when linked mailbox users try to synchronize their mailboxes with mobile devices in a CAS-CAS proxying scenario in Exchange Server 2010

980261 This fix introduces the supports for Exchange Server 2010 page patching when a "-1022" disk I/O error is generated

980262 Event ID 2156 is logged on a computer that is running Exchange Server 2010

Downloaden van Rollup 2 voor Exchange 2010 doe je HIER.

VMware View Connection Server
• Pentium IV 2.0Ghz processor or higher — dual processors are recommended
• 2GB RAM or higher — 3GB RAM is recommended for deployments of 50 or more View Manager desktops. VMware View connection server can handle 2,000 connections in clear mode and 750 in tunneled mode.
• One or more 10/100Mbps network interface controllers (NIC) — 1Gbps NIC is recommended

Supported Operating Systems
The VMware View Connection Server can be installed on the following 32-bit operating systems:
• Windows Server 2003 R2 Standard Edition with SP2
• Windows Server 2003 Standard Edition with SP2
• Windows Server 2003 R2 Enterprise Edition with SP2
• Windows Server 2003 Enterprise Edition with SP2

VMware View Connection Server Licences:
• VMware View Manager
• VMware View Manager with View Composer
• VMware View Manager with View Composer, and Offline Desktop

Prepare Active Directory en domains

1. Indien er nog een Exchange 2003 Server aanwezig is moet je:
setup /PrepareLegacyExchangePermissions of setup /pl

2. setup /PrepareSchema of setup /ps

3. setup /PrepareAD of setup /p
Onder de OU in domain genoemd Microsoft Exchange Security Groups worden de volgende groepen aangemaakt:
Exchange Organization Management
Exchange Recipient Management
Exchange Server Management
Exchange View-Only Organization Management
Exchange Public Folder Management
Exchange UM Management
Exchange Hygiene Management
Exchange Records Management
Exchange Discovery Management
Exchange Delegated Setup

Legacy Groepen:
Exchange Security Groups OU:
Exchange Organization Management
Exchange Recipient Management
Exchange Server Management
Exchange View-Only Organization Management
Exchange Public Folder Management
Exchange UM Management
Exchange Hygiene Management
Exchange Records Management
Exchange Discovery Management
Exchange Delegated Setup
ExchangeLegacyInterop

4. setup /PrepareDomain of setup /pd

Om naar buiten geen waarschuwing te krijgen dat het SSL certificaat niet vertrouwd wordt er normaal gesproken gewerkt met commerciële vertrouwd SSL certificaat.

Voor de Exchange 2007 & Exchange 2010 worden de volgende volgende URL’s gebruikt:

webmail.wardvissers.nl (MX records,OWA,IMAP/POP3/SMTP en Exchange ActiveSync – plus het is the reverse DNS record voor je statische IP adres)
autodiscover.wardvissers.nl(Voor Autodiscovery)
legacy.wardvissers.nl (Mocht je van Exchange 2003 vanaf komen)
e2k10.wardvissers.local (De Exchange Server interne naam)
e2k10 (De Exchange server NETBIOS naam).

“webmail.wardvissers.nl” is de eerste naam die verschijnt zodra een gebruiker op dit certificaat klikt. En zorgt er voor dat alles extern connect naar de server zonder support voor SAN/UC certificaten.

(SAN is Subject Alternative Name, UC is Unified Communications –Zijn het zelfde).

Het handige is dat dat je een SAN certificaat aanvraag. Met de eerder genoemde url’s.

Stel je hebt maar een certificaat genaamd webmail.wardvissers.nl dan kun je toch alles gebruiken maar daar is een truk voor nodig.

Vereisten:
- Outlook 2007 SP1
- SRV Record ondersteuning bij uw Externe DNS host. Mocht je dat niet hebben dan kun je twee
dingen doen:
1. Andere Domain aanbieder die wel SRV records ondersteund.
2. San Certificaat.
- Commerciële SSL-certificaat
- Split DNS Setup bijvoorbeeld (.local intern & .nl Extern)

DNS configuratie van Autodiscover

1. Verwijder alle host A records die verwijzen naar autodiscover.domain.local

2. Maak een nieuw Service Location (SRV Record aan). Vul de gegevens in zoals afgebeeld op de plaatjes.

3. Webmail.wardvissers.nl moet verwijzen naar de CAS Exchange 2010 server.

Exchange URL aanpassingen door voeren:

1. Get-ExchangeCertificate (Lijst met alle Exchange Certificaten)

2. Enable-exchangecertificate -services IMAP, POP, IIS, SMTP -Thumbprint 02B3E404EF76A0A839365C7489B59B1D1278EDCD (Certificaat Nummer)

3. Zet de volgende URL’s goed:
Set-ClientAccessServer -Identity e2k10 -AutoDiscoverServiceInternalUri https://webmail.wardvissers.nl/Autodiscover/Autodiscover.xml

Set-WebServicesVirtualDirectory -Identity “e2k10\EWS (Default Web Site)” -InternalUrl https://webmail.wardvissers.nl/ews/exchange.asmx

Set-OABVirtualDirectory -Identity “e2k10\oab (Default Web Site)” -InternalUrl https://webmail.wardvissers.nl/oab

Enable-OutlookAnywhere -Server e2k10 -ExternalHostname “webmail.wardvissers.nl” -ClientAuthenticationMethod “Basic”-SSLOffloading:$False

Set-ActiveSyncVirtualDirectory -Identity “e2k10\Microsoft-Server-ActiveSync (Default Web Site)” -ExternalURL https://webmail.wardvissers.nl/Microsoft-Server-Activesync

Set-ECPVirtualDirectory –Identity e2k10\ECP (default web site) -ExternalURL https://webmail.wardvissers.nl/ECP

4. Nu werkt verwijst intern en extern naar het zelfde adres.

5. Er zijn nog wel twee dingen waar je op moet letten:
- Het kan zijn dat je een voor IE een url moeten toevoegend dat lokaal blijft resolven als je via
een proxy server naar buiten toe gaat.
- Op elke CAS/HUB server moet Exchange URL’s toegepast worden naar het NLB CAS Load
Balacing

A Computer that is running Microsoft Exchange Server 2007 that has the Client Access Server (CAS) role installed becomes slow when a user tries to open a folder that contains many items

An appointment is displayed incorrectly as an all-day event if you use a mobile device to synchronize the calendar in Exchange Server 2007

Exchange Server 2007 users intermittently cannot access an Exchange Server 2003 user’s Free/Busy information in Office Outlook 2007

The Microsoft Exchange Server 2007 log or database experiences abnormal growth

When a user sends e-mail messages to a remote domain, some e-mail messages are queued on an Exchange Server 2007 Hub Transport server or Edge server

A new accepted domain that is added does not work in an Exchange Server 2007 organization

EdgeTransport.exe process crashes intermittently on an Exchange Server 2007 server

You receive an NDR you try to send messages through your Microsoft Exchange Server 2007 account

You cannot log on to your mailbox and you receive an error in an Exchange server 2003 and Exchange Server 2007 coexist environment

Event 2104 and event 2147 are continuously logged in an Exchange Server 2007 Cluster Continuous Replication (CCR) environment

Messages that have duplicate message IDs are deleted when they are archived to an Exchange 2007 mailbox

The free/busy information of an Exchange Server 2007 user is not displayed

You receive the warning "Failed to update recipient" when you run the Update-addresslist cmdlet in Exchange Management Shell on Exchange Server 2007

Windows Server 2008 VSS backup plug-in fails to backup Exchange 2007 Service Pack 2 databases that reside on a volume mount point

De complete lijst met wat er gefixt is vind je HIER en downloaden doe je HIER

Wat is nu de EcoShell:
De Virtualization EcoShell biedt een eenvoudige, consistente en geïntegreerde beheer user interface voor het creëren, debuggen en vereenvoudiging van het beheer van Windows PowerShell scripts.
Voor downloads en informatie over het installeren van de Virtualisatie EcoShell, bezoekt u de Virtualisatie EcoShell download pagina.

Meer en meer bedrijven gebruiken Windows PowerShell scripts op verschillende platformen.
De Virtualisatie EcoShell gepositioneerd is voor IT-beheerders, adviseurs, en consultants die alles moeten beheren en terug kerende taken te automatiseren . Gecentraliseerd beheer van servers. De Virtualisatie EcoShell bespaart dagelijks tijd voor beheerders voor het beheer van virtuele omgevingen.

Wat heb je nodig om er gebruik van te kunnen maken.

Windows PowerShell Version 1.0
VMware PowerCLI 4.0
Quest PowerShell Commands for Active Directory Version 1.2
32-Bit  |  64-Bit
Virtualization EcoShell Build 1.2.0.154

Zo ziet de Virtualization EcoShell er uit.

2. Zorg er voor dat de eventuele DHCP role al overgezet is.

2. Kopieer van de 2008 R2 iso de adprep map naar c:\ van de eerste 2003 domain controller.

3. Voer het volgende uit: adprep /forestprep > c:\forestprep.log

 
4. Check domain level

4. Voor nu het volgende uit adprep /domainprep
  
5. Nu kun je de geïnstalleerde Windows 2008 R2 server upgraden tot domain controllers door middel van DC promo te draaien.

6. Draai dcpromo op desbetreffende servers. Gebruik hiervoor een account dat lid van is van de volgende groepen Schema Admins, Enterprise Admins, Domain admins.

7. Zet alle rollen over naar de 2008 R2 domain controllers
7.1 RID Master, PDC Emulator en Infrastructure Masters

7.2 Active Directory Domains and Trust

7.3 Active Directory-schema

De module Active Directory-schema installeren

1. Klik op Start, klik met de rechtermuisknop op Opdrachtprompt en klik vervolgens op Als administrator uitvoeren.

   If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.

2. Typ de volgende opdracht bij de opdrachtprompt en druk vervolgens op ENTER:

   regsvr32 schmmgmt.dll


3. Klik op OK om het dialoogvenster te sluiten waarin wordt bevestigd dat de bewerking is gelukt.

4. Klik in het menu Start op Uitvoeren, typ mmc en klik op OK.

5. Klik in het menu Bestand op Module toevoegen/verwijderen.

6. Klik onder Beschikbare modules op Active Directory-schema, klik op Toevoegen en klik vervolgens op OK

7. En vervolgens doe Change Schema Master

8. Check met het volgende command of alle FSMO rollen netjes zijn omgezet: netdom.exe query fsmo

9. Zo te zien zijn alle rollen netjes omgezet en kan ik win2k3r2x64 gaan demoten.

10. Zorg er voor dat de DHCP scope en overige servers de juiste dns instellingen hebben.

11. Voer dcpromo uit.

12. Nu nog even de win2k3r2x64 server uit het domein halen dan kan daarna de server netjes uitgezet worden.

Je krijgt dan de volgende error:

De standaard driver die VMWare mee levert in VMWare Tools werkt niet binnen een Windows PE image. Wel als Windows een maal geïnstalleerd is.

Oplossing:
Download van de AMD site de NDIS5 driver voor Microsoft Windows Server 2003, Windows XP

PCNET Family Software vind je HIER en de juiste driver voor MDT (WinPE) vind je HIER