Archive for the ‘Exchange’ Category

Step 1: Prerequisite

· Windows Server 2008 with Service Pack 2 or later or Windows Server 2008 R2 must be used for all servers running Exchange 2010 server roles or management tools

· .NET Framework 3.5 (Windows 2008 feature)

· Windows Remote Management 2.0

· Windows PowerShell v2 (Windows Server 2008 feature)

· Desktop Experience (Windows Server 2008 feature)

· Net. TCP Services started and set automatic (services.msc)

· Disable TCP/IP6 from Registry (if you use tcp/ip4)

· 2007 Office System Converter

· IIS for Client Access Role

· Active Directory Services Remote Management Tools (ServerManagerCmd –i RSAT-ADDS)

Step 2: Migrating from Windows 2003 AD Forest to Windows 2008 AD Forest

· Create user with domain admin, schema admin and enterprise admin role from existing AD

· Log on using new user name

· Run Dcdiag and Netdiag tools

· Bring the AD forest and domains to Windows Server 2003 Functional Level

· Insert Win2k8 Server DVD into Win2k3 DC

· Run following command from Command prompt

· d:sourcesadprepadprep.exe /forestprep where d: is DVD ROM

· d:sourcesadprepadprep.exe /domainprep /gpprep

· d:Setup and select upgrade option to use existing DC

· Transfer FSMO Roles for a new Win2k8 DC with new Hardware

· Make one DC as GC

· Replicate AD database, GPO or wait tomstone to replicate

· Retire Windows 2003 DC

· Run DCPROMO (Uncheck this is last remaining DC)

· Raise new Domain Functional level to Win2k8

Step3: Transition from Exchange 2003 to Exchange 2010

· Bring the Exchange organization to Exchange Native Mode.

· Upgrade all Exchange Servers to Exchange Server 2003 Service Pack 2.

· Upgrade at least one Global Catalog domain controller in each AD site that will house Exchange Server to Windows Server 2003 SP2 or greater.

· Prepare a Windows Server 2008 (RTM or R2) x64 edition server for the first Exchange 2010 server.

· Install the AD LDIFDE tools on the new Exchange 2010 server (to upgrade the
schema by running d:Exchange2010Setup /PrepareSchema or Setup /ps)

· Run d:Exchange2010Setup /PrepareAD /OrganizationName:your_organisation_name from command prompt where D: DVD ROM

· Install any necessary prerequisites (WWW for CAS server role).

· Run setup on the Exchange 2010 server, upgrade the schema, and prepare the forest and domains. (Setup runs all in one step or separate at the command line eg. /mode:install /roles:H,C,M

· Install Client Access Server role servers and configure per 2010 design. Validate functionality.

clip_image001 ServerManagerCmd -i Web-Server

clip_image001[1] ServerManagerCmd -i Web-ISAPI-Ext

clip_image001[2] ServerManagerCmd -i Web-Metabase

clip_image001[3] ServerManagerCmd -i Web-Lgcy-Mgmt-Console

clip_image001[4] ServerManagerCmd -i Web-Basic-Auth

clip_image001[5] ServerManagerCmd -i Web-Digest-Auth

clip_image001[6] ServerManagerCmd -i Web-Windows-Auth

clip_image001[7] ServerManagerCmd -i Web-Dyn-Compression

clip_image001[8] ServerManagerCmd -i NET-HTTP-Activation

clip_image001[9] ServerManagerCmd -I RPC-over-HTTP-proxy

clip_image001[10] ServerManagerCmd –I Web-Server Web-ISAPI-Ext Web-Metabase Web-Lgcy-Mgmt-Console Web-Basic-Auth Web-Digest-Auth Web-Windows-Auth Web-Dyn-Compression NET-HTTP-Activation RPC-over-HTTP-proxy –Restart

· Transfer OWA, ActiveSync, and Outlook Anywhere traffic to new CAS servers.

· Install Hub Transport role and configure per 2010 design (New internal/external SMTP connector)

· Transfer inbound and outbound mail traffic to the HT servers.

· Install mailbox servers and configure Databases (DAG if needed).

· Create public folder replicas on Exchange 2010 servers using Exchange 2010 Public Folder tool.

· Move mailboxes to Exchange Server 2010 using Move Mailbox Wizard or PowerShell.

· Re-home the Offline Address Book (OAB) generation server to Exchange Server 2010.

· Re-home the public folder hierarchy on the new Exchange Server 2010 admin group.

· Transfer all Public Folder Replicas to Exchange Server 2010 Public folder store(s).

· Review and verify Installation log, events, Exchange related Windows services, server roles

· Test Mail Flow, public folder, webmail, outlook config

· Run BPA

· Delete Public and Private Information Stores from Exchange 2003 server(s).

· Delete Routing Group Connectors to Exchange Server 2003.

· Delete Recipient Update Service agreements using ADSIEdit.

· Uninstall all Exchange 2003 servers and remove from domain.

Tools to use:







Exchange Management Console

Further Help:

Microsoft Technet

Keywords: FSMO, Exchange 2010, Exchange 2003, Exchange Server Roles, Windows Server 2008, Windows Server 2003

Important Warning: I am talking about messaging technology. It could be heart of your organization. So Prepare a test lab that simulate your circumstances and fit in your organisation. I created this instruction in a VMware lab environment. Visit TechNet web site to learn more about Exchange 2010 before you deploy in production environment.

DOS/Command Prompt way.

Alle linjer efterfulgt af “enter”

telnet 25
SUBJECT:100% pure testing (dette er emnefeltet) – tryk ENTER to gange derefter
Dette er noget indhold i mailen – ENTER
. (punktum efterfulgt af enter sender mailen – fra ny linje!)

250 2.6.0 <> Queued mail for delivery (Mail er sendt!)

Den klassiske fejl med opsat Exchange 2007/2010 server og eller importeret certifikat.
Dette giver fejlen med “Navnet på sikkerhedscertifikatet er ugyldigt eller svarer ikke til webstedets navn”

Ovenstående link er en god hjælp til løsning på det problem.

Some of you probably wonder how you can simplify the Outlook Web App (OWA) URL on your Exchange 2010 Client Access servers?

With IIS 7.0 at our disposal, it’s much simpler than it was with Exchange 2007 installed on Windows Server 2003. Just like its the case with Exchange 2007 installed on Windows Server 2008, you no longer need to use an IIS redirect HTML file. Instead, you can use the “HTTP Redirect” feature in IIS 7.0.;en-us;883380

How to reset the default virtual directories that are required to provide Outlook Web Access, Exchange ActiveSync, and Outlook Mobile Access services in Exchange Server 2003