Microsoft Windows Server 2008 R2 and Exchange 2010

Windows Server 2008 R2 builds on the award-winning foundation of Windows Server 2008, expanding existing technology and adding new features to enable IT professionals to increase the reliability and flexibility of their server infrastructures. New virtualization tools, Web resources, management enhancements, and exciting Windows 7 integration help save time, reduce costs, and provide a platform for a dynamic and efficiently managed data center. Powerful tools such as Internet Information Services (IIS) version 7.5, updated Server Manager and Hyper-V platforms and Windows PowerShell version 2.0 combine to give customers greater control, increased efficiency and the ability to react to front-line business needs faster than ever before......

Tuesday, January 10, 2012

Useful Power Shell Command in Exchange 2010


Find Which Exchange 2010 CAS Server a Client Connects To
Get-LogonStatistics -Server BLEXCHMBX01 |ft username, clientname, clientversion
(clientname gives you the CAS)

or for a user:
Get-LogonStatistics -Identity yfaruqe | Sort-Object "LastAccessTime" |  ft  username, clientname, *last*

Use the Shell to update a mailbox database copy
This example shows how to seed a copy of a database named DB1 on MBX1.
Update-MailboxDatabaseCopy -Identity DB1\MBX1
This example shows how to seed a copy of a database named DB1 on MBX1 using MBX2 as the source Mailbox server for the seed.
Update-MailboxDatabaseCopy -Identity DB1\MBX1 -SourceServer MBX2
This example shows how to seed a copy of a database named DB1 on MBX1 without seeding the content index catalog.
Update-MailboxDatabaseCopy -Identity DB1\MBX1 -DatabaseOnly
This example shows how to seed the content index catalog for the copy of a database named DB1 on MBX1 without seeding the database file.
Update-MailboxDatabaseCopy -Identity DB1\MBX1 -CatalogOnly

How to Rebuild the Full-Text Index Catalog

Database Copy Automatic Activation Policy is also an option for blocking the automatic activation
Get-MailboxServer BLEXCHMBX03 | Fl Name, DatabaseCopyAutoActivationPolicy
OR
Get-MailboxDatabaseCopyStatus -Server BLEXCHMBX03 | FL DatabaseName, ActivationSuspended

Quickly View the Current Mailbox Size, Message Count, and Last Logon
Syntax
Get-MailboxStatistics -Identity 'Identity' [-Archive <$true|$false>] [-DomainContoller DomainController]
[-IncludeMoveHistory <$ true|$false>] [-IncludeMoveReport <$true|$false>]
Get-MailboxStatistics -Server 'Server' | -Database 'Database' [-DomainContoller DomainController]
Usage
Get-MailboxStatistics -Server 'corpsvr127'
Get-MailboxStatistics -Database 'Engineering Primary'


How to Find Exchange Server 2010 Mailboxes without Storage Quotas
[PS] C:\>get-mailbox | where {$_.UseDatabaseQuotaDefaults -eq $False}

Name        Alias                ServerName       ProhibitSendQuota
----       -----                ----------       -----------------
DiscoverySearchMailbox... DiscoverySearchMa... ex2              50 GB (53,687,091,200 bytes)
Carole.Malik              Carole.Malik         ex2              unlimited
Davina.Nsiah              Davina.Nsiah         ex2              5.371 GB (5,767,168,000 bytes)
Helen.Cail                Helen.Cail           ex2              4.688 GB (5,033,164,800 bytes)
Jas.Mahal                 Jas.Mahal            ex2              unlimited
Lorraine.Oza              Lorraine.Oza         ex2              unlimited
Oliver.Loffler            Oliver.Loffler       ex2              4.688 GB (5,033,164,800 bytes)

The output above shows that some mailboxes have no quotas, whereas others have custom storage quotas applied. To see the full details of the storage quotas configured on these mailboxes use the following command in the Exchange Management Shell.
[PS] C:\>get-mailbox | where {$_.UseDatabaseQuotaDefaults -eq $False} | ft name,prohibit*,issue*


However if you want to see a list of users mailbox sizes then you will need to use PowerShell.
Get-MailboxServer | Get-MailboxStatistics | select displayname,itemcount,totalitemsize | Conver
tTo-HTML | Out-File D:\Test.htm

See Mailbox Statics of a particular Database
Get-MailboxStatistics -Database 'MDB06'| select displayname,itemcount,totalitemsize

Get-MailboxStatistics -Server BLEXCHMBX02 |Sort-Object -Property TotalItemSize -Descending |Select-Object -property DisplayName,@{N="ItemCount";E={$_.ItemCount}},@{N="TotalItemSize";E={$_.TotalItemSize.value.ToMB()}},@{N="deletedItemCount";E={$_.deletedItemCount}},@{N="TotalDeletedItemSize";E={$_.TotalDeletedItemSize}},@{N="Database";E={$_.Database}} |Export-CSV -Path c:\Notice\MailboxReport.csv -NoTypeInformation

To View the statistics in MB
Get-MailboxStatistics -Database MDB06 |Sort-Object -Property TotalItemSize -Descending |Select-Object -property DisplayName,@{N="ItemCount";E={$_.ItemCount}},@{N="TotalItemSize";E={$_.TotalItemSize.value.ToMB()}},@{N="deletedItemCount";E={$_.deletedItemCount}},@{N="TotalDeletedItemSize";E={$_.TotalDeletedItemSize.value.ToMB()}},@{N="Database";E={$_.Database}} |Export-CSV -Path D:\MDB06.csv -NoTypeInformation
Check Exchange Database Size:


Get-MailboxDatabase -Status | select ServerName,Name,DatabaseSize

ServerName                              Name                                    DatabaseSize
----------                              ----                                    ------------
XXEXCHMBX01                             MDB01                                   107.4 GB (115,301,482,496 bytes)
XXEXCHMBX01                             MDB02                                   119.9 GB (128,723,779,584 bytes)
XXEXCHMBX01                             MDB03                                   115 GB (123,488,763,904 bytes)
XXEXCHMBX02                             MDB04                                   112.5 GB (120,804,409,344 bytes)
XXEXCHMBX02                             MDB05                                   103.1 GB (110,738,079,744 bytes)
XXEXCHMBX02                             MDB06                                   179.4 GB (192,610,893,824 bytes)


Exchange 2010 Find Database White Space
Get-MailboxDatabase -Status | Select-Object Server,Name,AvailableNewMailboxSpace

Server                                  Name                                    AvailableNewMailboxSpace
------                                  ----                                    ------------------------
XXEXCHMBX01                             MDB01                                   17.59 MB (18,448,384 bytes)
XXEXCHMBX01                             MDB02                                   121 MB (126,844,928 bytes)
XXEXCHMBX01                             MDB03                                   110 MB (115,343,360 bytes)
XXEXCHMBX02                             MDB04                                   44.81 MB (46,989,312 bytes)
XXEXCHMBX02                             MDB05                                   29.09 MB (30,507,008 bytes)
XXEXCHMBX02                             MDB06                                   15.86 GB (17,031,495,680 bytes)

Get-MailboxDatabase MDB06 -Status | FL AvailableNewMailboxSpace

Set Quota of Retention Item
Set-MailboxDatabase -Identity MDB03 -RecoverableItemsWarningQuota 20GB -RecoverableItemsQuota 30GB

Get Recoverable Items Folder Statistics
The Recoverable Items folder contains items deleted by Microsoft Outlook and Microsoft Office Outlook Web App users or by the Mailbox Assistant
Get-MailboxFolderStatistics -Identity "Sanjoy Saha" -FolderScope RecoverableItems | Format-List

Get-MailboxFolderStatistics -Identity "Nizar El-Assaad" -FolderScope RecoverableItems | Format-Table Name,FolderPath,ItemsInFolder,FolderAndSubfolderSize

Get-MailboxFolderStatistics -Identity "Maruf Ahmed" -FolderScope RecoverableItems | Format-Tabl
e Name,FolderPath,ItemsInFolder,FolderAndSubfolderSize

Name                          FolderPath                                    ItemsInFolder FolderAndSubfolderSize
----                          ----------                                    ------------- ----------------------
Recoverable Items             /Recoverable Items                                     2043 1.332 GB (1,430,546,505 by...
Deletions                     /Deletions                                             6619 1.315 GB (1,412,322,237 by...
Purges                        /Purges                                                   0 0 B (0 bytes)
Versions                      /Versions                                                 0 0 B (0 bytes)


To display the user's alias formatted in a table together with the user's Exchange 2010 server name and telephone extension, type:

 Get-Mailbox | Format-Table ServerName,@{e={$_.SamAccountName};Label="User Alias"},@{Expression="Extensions";Label="Telephone numbers

Sunday, January 1, 2012

Installing Update Rollups on Exchange 2010 Database Availability Group Members


It's relatively straightforward to install Microsoft Exchange Server 2010 update rollups on a server that's a member of a database availability group (DAG).

Microsoft Update offers released update rollups to Mailbox servers that are part of DAG. However, Microsoft recommends that we should download the update rollups from the Microsoft Download Center and then install them manually. When we install an update rollup on a server that's a DAG member, several services will be stopped during the installation, including all Exchange services and the Windows Cluster service.

The general process for installing update rollups on a DAG member is as follows:

  • Suspend activation for the databases on the server being updated.
  • Perform a server switchover so that all databases on the server are passive copies. During the switchover process, there will be a brief interruption in service for the mailboxes hosted on the active databases.
  • Install the update rollup.
  • Resume activation for the databases on the updated server.
  • Perform database switchovers as needed, or rebalance the DAG by using the RedistributeActiveDatabases.ps1 script.

Install a Update Rollup on a Database Availability Group Member

To update all DAG members, perform the following procedures on each DAG member, one at a time.

Suspend activation for the database copies on the server being updated

Run the following command in the Exchange Management Shell:

Get-MailboxDatabaseCopyStatus -Server <Server> | Suspend-MailboxDatabaseCopy -ActivationOnly -Confirm:$False -SuspendComment "Install update rollup for Exchange 2010"



Perform a server switchover on the server being updated

  1. In the console tree of the Exchanger Management Console (EMC), navigate to Server Configuration > Mailbox.
  2. In the result pane, select the Mailbox server you want.
  3. In the action pane, select Switchover Server.
  4. In Switchover server database copies, do one of the following:
    • Accept the default setting of Automatically choose a target server (in which case, the system automatically selects the best Mailbox server for each database being switched over), and then click OK.
    • Click Use the specified server as the target for switchover, click Browse to select a Mailbox server, and then click OK.



Install the update rollup

  1. Close all Exchange management tools.
  2. Right-click the Exchange update rollup file (.msp file) you downloaded, and then select Apply.
  3. On the Welcome page, click Next.
  4. On the License Terms page, review the license terms, select I accept the License Terms, and then click Next.
  5. On the Completion page, click Finish.

Resume activation for the databases on the updated server

Run the following command in the Shell:

Get-MailboxDatabaseCopyStatus -Server <Server> | Resume-MailboxDatabaseCopy



Perform database switchovers as needed

  1. In the console tree of the EMC, navigate to Organization Configuration > Mailbox.
  2. In the result pane, click the Database Management tab, and then click the mailbox database whose copy you want to activate.
  3. In the action pane, click Activate a Database Copy.
  4. On the Activate a Database Copy page, click Browse to select the server you updated.
  5. Select the desired setting for the automatic database mount dial setting on the selected server.
  6. Click Move to activate the selected passive copy of the database to the updated server.
  7. On the Completion page, review the following, and then click Finish to close the wizard:
    • A status of Completed indicates that the wizard completed the task successfully.
    • A status of Failed indicates that the task wasn't completed. If the task fails, review the summary for an explanation, and then click Back to make any configuration changes.

    Sunday, September 18, 2011

    Software RAID on WIndows 2003

    This series of articles will show how to set up software RAID on a Windows Server 2003 system. Before you do anything with your disks, make sure you have a good backup. Please read our terms of use. We will start with one Basic drive, create a RAID1 set on a new drive we install, remove the first drive, and recover from the second. We wrote up an article over seven years ago here about Windows Server software RAID, and it is definately time to provide an update. First off, we have a single 12 gig drive running in Basic mode:

    Monday, May 16, 2011

    Exchange 2010 Migration Transition Plan


    Exchange 2010 High Level Deployment Plan

    • Assess Current Infrastructure
    • Upgrade Requirements
    • Built Exchange 2010 Servers
    • AD Preparation
    • Installation
    • Front End Configuration
    • Back End Configuration
    • Testing
    • Migration
    • Post migration
    • Uninstall Exchange 2003

    Assess Current Infrastructure

    • Very first step of Exchange migration is Assessment of current Exchange AD environment.
    • You run ExBPA, EXPA, ADMAP and anaylyse the report & fix any issue reported.
    • Below are some of the questions you may ask yur customer.
    • How many exchange servers are currently running?
    • Are they all 2003 SP2 ? 64bit OS or 32 bit OS?
    • Exchange server STD or ENT version? Clustered or stand alone?
    • How many Databases? How many users? Avarage Mailbox sizes?
    • Any journalling / archiving features?
    • What kind of back up? daily or weekly ?Incremental or full ?
    • What is current DR plan ?
    • What are current HA features in Exchange?
    • What are exchage security and monitoring softwares in use?
    • Are they using EDGE, ISA or TMG servers
    • Do they have BES servers ? What version ?
    • How many BB users?
    • Are they using Active Sync, Outlook anywhere, OWA etc…
    • With Exchange 2010 and 2007 heavily rely on DC servers, so it is also essential to get more idea about AD env.
    • How many DCs? How many GCs? Version of OS ? 64 Bit or 32 bit?
    • How many Sites?
    • Is there any windows 2000 DC still in network?

    For out test lets assume that we have below infrastruture.

    • —  2 Windows 2003 R2 GC
    • —  2 Windows 2008 R2 GC
    • —  4 Exchange 2003 servers Clustered.
    • 2 Front End Exchange 2003 servers
    • —  1 BES 5.0.1 server
    • —  2 ISA server (DMZ)
    • —  All servers are in one site and same subnet
    • —  Clients are running Outlook 2007 and 2010



    Upgrade Requirements

    • Next step is to talk with client and setup expections for exhange 2010 and ask client that what kind of HA and DR features they are looking for with Exchange 2010 infrastrcuture?
    • Are they looking for Standalong Exchange 2010 servers?
    • 2 Server DAG same site?
    • 3 servers DAG streched in diffrerent site?
    • 4  Server DAG with Automatic Datacenter failover ?
    • Do they want to combine Hub/CAS/Mailbox roles or separate it?
    • If they have ISA servers for web publishing , do they want ot migrate to TMG servers?
    • What kind of SLA we are looking for in DR situation?
    • Do they want to provide more mailbox space with Ex2010?
    • Do they want to go for complience and archiving features ?
    • Run EXPDA and Exchange 2010 mailbox caculator and size your exchange servers..

    For our scope, below is the requirment, we would like to go forward with..

    • —  3 Exchange 2010 servers with single DAG
    • —  Hub/CAS/MBX role combined
    • —  2 Exchange 2010 servers at main site
    • —  1 Exchange 2010 server at remote site
    • —  Single DAG Active Passive
    • —  FSW on DC/BES

    Built Exchange 2010 servers
    This is the phase where you order your servers if you are planning to deploy physical servers
    Or Provision VM based on Exchange roles sizing calculation.
    With our scope, we will follow below path…—

    • Create 2 New VMs in site1 and 1 in site2
    • —  Create disk arrays
    • —  Install Windows 2008 R2 SP1
    • —  Install other Windows Update
    • —  Make a part of MigrationX.com domain
    • —  Install Exchange 2010 filter pack
    • —  Install IIS role and dot net framework 3.5 feature from server manager
    • —  Teaming of Network adapter (optional)
    • —  Assign static IPs

    AD Preparation for Ex 2010

    • —  Run ExBPA on Exchange 2003 server and analyze results
    • —  Resolve issue reported in ExBPA
    • —  Run below commands on one of the VM which has Ex2010SP1 setup files extracted.
    • —  Setup /pl
    • —  Setup /ps
    • —  Setup /p
    • —  Setup /pd

    5. Installation Exchange 2010

    • —  Extract Ex2010Sp1 setup and click setup.exe
    • —  Click on Automatically install all windows role and features necessary for ex2010 setup
    • —  Write mail.migrationx.com as external name space
    • —  Install Hub/Mailbox/CAS role
    • —  Install Forefront protection for Exchange
    • —  Install CA role into one of DC

    6. Front end Config : Pre Migration

    • Now we will start configuring those exchange 2010 servers, based on our reqirments.
    • Create CSR for SAN cert
    • —  Get SAN cert from Internal CA
    • —  Import SAN cert thru IIS
    • Create CAS array
    • —  Configure F5 HLB
    • — —  DNS changes for legacy owa url
    • —  Configure OWA redirection for Ex2003 users
    • —  Open ports from Ex2010 servers to firewall
    • —  Replace internal owa with mail.migrationx.com
    • —  Configure autodiscover uri parameter to point to HLB on CAS
    • —  Configure ISA server web publishing rules
    • —  ISA rules switch over

    Back end Config of Ex 2010

    • —  Delete default Exchange 2010 DBs
    • —  Create and configure new DB into Ex2010
    • —  Create DAG /FSW
    • —  Create DAG network and Static routes
    • —  Add member server and DB copy into DAG
    • —  Create Public folder database
    • —  Create test mailboxes into Ex2003 and 2010
    • —  Configure retention policies and tags
    • —  Install Backup and testing
    • —  Create Receive connector for SMTP relay

    Testing of Ex 2010 Environment

    • —  Connectivity test with CAS array
    • —  MAPI tests with Outlook 2003/2007/2010
    • —  OWA OA EAS BB test
    • —  DAG Replication test
    • —  Changes on BES server and testing
    • —  Backup restore testing
    • —  Test SMTP relay applications
    • —  Test mailbox moves
    • —  Test inbound out bound mail flow and connectivity
    • —  Test BB device email connectivity, address lookup and calendar sync after migration
    • —  Test internal external mail flow

    Migration : Move mailboxes

    • —  Pilot migration
    • —  Tier 1 Mailbox move
    • —  Resolve mailbox migration related issues
    • —  Tier 2 mailbox move
    • —  Special mailbox move
    • —  Room mailbox move and convert into Resource mailbox
    • —  Final mailbox move

    Post Migration

    • —  Create Send connectors on Ex2010
    • —  Configure TLS and change cost
    • —  Email cutover
    • —  Delete Internet connector on Ex2003
    • —  Update Default email address policy
    • —  Move replica of public folders to Ex2010
    • —  Delete Ex2003 Public folders

    Uninstall Exchange 2003

    • — Temporary shutdown services on Ex 2003 servers
    • Temporary Shut down Ex 2003 severs
    • —  Resolve any issue related to Exchange 2003
    • —  Remove Recipient Update services from Ex2003
    • —  Remove Interop routing group
    • —  Dismount and delete Ex 2003 DBs
    • —  Uninstall Exchange 2003
    • —  Shut down Windows 2003 servers

    Thursday, November 4, 2010

    Benefits of Upgrading to Microsoft Exchange Server 2010

    Cross-Premises Email Routing
    Microsoft cites the example of a school that wishes to use on-premises email for staff and an externally hosted service for students. We have deployed Exchange in many schools that would love to do exactly that, as well as some large enterprises that want to retain highly available, mission critical mail services in one system and move non-critical users onto a cheaper platform elsewhere.
    Enhanced Disclaimers
    Immediately solves the problem of customers wanting to include links, images, or dynamically generate their disclaimers using AD attributes and have had to turn to third party commerical options to do this.
    Moderated Transport
    This feature solves the problem of protecting distribution lists from inappropriate use without totally blocking them off from important emails.
    Reduced IOPS
    Improvements to the Extensible Storage Engine (ESE) have reduced disk IOPS requirements by as much as 70% from Exchange Server 2007, making Exchange storage sizing a much simpler and less costly exercise. In a discussion with Microsoft they sketched out a storage layout of single 1TB SATA II disks (without RAID) each hosting a single database for hundreds (or thousands) of users.
    High Availability
    The enhancements to high availability (now being called “continuous availability”) are nothing short of spectacular, with Database Availability Groups (DAG) providing per-database failover capabilities, making failover scenarios more efficient and easier to plan for



    Seamless Mailbox Moves
    With MAPI connectivity abstracted to the Client Access Server layer mailbox moves on the backend database can occur without interrupting client connectivity. Obviously this makes scheduling of any mailbox move scenario a much easier task.

    New Features in Microsoft Exchange Server 2010
    Microsoft Exchange Server 2010 brings a new and rich set of technologies, features, and services to the Exchange Server product line. The following is a list of the new features and functionality that are included in Exchange 2010 and it provides important information to use when you're upgrading, migrating, deploying, and administering Exchange 2010 in your organization.
    Outlook Web Access (OWA) support for Multiple Browsers
    Support for different browsers such as Firefox,Safari, Internet Explorer and more.
    Improved Storage Reliability
    New ability to run Exchange reliably without dealing with Windows clustering, RAID arrays, or fancy Enterprise-class disk. It will be cheap to save or restore/ recover data and quick too.
    Mail Tips
    Mail Tips is a program which tells you about the possible mistakes you are going to do by sending an email to someone whom you don't intend to. Mail Tips helps you by warning you in advance and giving you tips.
    Conversation View
    Users can now view threaded conversations under one single node when exchanging messages.
    Sharing
    This is another feature that allows to share a lot of things effectively. Exchange Server 2010 has twonew  main properties to share:
    • Calendar Sharing. You can share calendars to federated users by OWA.
    • Contact Sharing. You can share contacts very easily now.
    Voice Mail Preview
    Users will now have a text preview of your voice mail messages.
    Exchange Control Panel (ECP)
    Get self serviced tasks that before required  administrators intervention.
    Critical Security
    Microsoft has gone over the typical or traditional security benchmarks and have fancied some really cool features in Exchange server programs. If you lead an organization, you will be happy to know that Microsoft has introduced features like:
    • Mobile Device Block/Allow List. Block/unblock specific devices only, helping you to have a secure way of hardware monitoring.
    • Protected voice mail.  You can now actually protect voice mail and track them and restrict them not to go outside the organization anyhow.
    • Outlook protection rules. Automatically triggers Outlook to apply an RMS template to a message before it is sent.
    Distribution Group Management
    Create, modify and access different distribution groups according to your choices and likings. That will help a better precision in teaming with the right kind of people under a single roof which will automatically increase effectiveness than reaching out to specific people individually.
    Backing up Exchange Server with DPM 2010
    Now you can back up all of your Exchange Server 2003 through 2010 with Data Protection Manager 2010. See DPM 2010 New Features.
    Others
    SATA support now involving I/O optimization, JDBO support, incoming voice mail reception and multi-mailbox search 




    Wednesday, September 22, 2010

    Unbeatable virtualization solutions from Microsoft

    Microsoft virtualization offerings span from the desktop to the datacenter and into the cloud. Regardless of where you plan to use Microsoft virtualization, we provide comprehensive and customer-centric solutions that give you more choice, flexibility, integration and cost savings than VMware.

    Microsoft virtualization for the Datacenter

    In the datacenter, Microsoft provides many capabilities that VMware does not and cannot offer.
    This chart compares VMware vSphere 4 core features with Microsoft Windows Server 2008 R2 Hyper-V and System Center Management core features. As you can see, Microsoft is ahead in many of the areas required for a robust desktop to datacenter virtualization and management solution.


    Microsoft virtualization for the Desktop

    Microsoft provides more comprehensive, flexible virtualization solutions than VMware for desktop virtualization.
    The chart below will clarify some of the feature differences between Microsoft and VMware’s desktop virtualization offerings. Notice that Microsoft’s solution is more scalable and flexible, while offering integrated management for both virtual desktops and physical computers.


    Microsoft virtualization solutions for the Cloud

    Microsoft provides comprehensive cloud computing solutions that traverse the entire stack - from public to private to hosted cloud infrastructures.
    The chart below will clarify some of the capability differences between Microsoft and VMware’s cloud offerings. Notice that Microsoft’s cloud solution has better management, more choices for cloud deployments, and free solution accelerator toolkits.



    DHCP and WINS server Migration

    The following steps  will explain how to Export the DHCP database from a server that is running Microsoft Windows Server 2003 or Windows Server 2008 To move a DHCP database and configuration from a server that is running Windows Server 2003 or Windows Server 2008 to another server that is running Windows Server 2008.

    Step: 1 - Export the DHCP database
    1. Log on to the source DHCP server by using an account that is a member of the local Administrators group.
    2. Click Start, click Run, type cmd in the Open box, and then click OK.
    3. Type netsh dhcp server export C:\dhcp.txt all , and then press ENTER.
    Note: You must have local administrator permissions to export the data.
    Configure the DHCP server service on the server that is running Windows Server 2008
    1. Click Start, click Administrative Tools, click Server Manager. If needed acknowledge User Account Control.
    2. In Roles Summary click Add Roles, click Next, check DHCP server, and then click Next.

    Step:2 - Import the DHCP database
    1. Log on as a user who is an explicit member of the local Administrators group.
    2. Copy the exported DHCP database file to the local hard disk of the Windows Server 2008-based computer.
    3. Verify that the DHCP service is started on the Windows Server 2008-based computer.
    4. Click Start, click Run, type cmd in the Open box, and then click OK.
    5. At the command prompt, type netsh dhcp server import c:\ dhcp.txt all , and then press ENTER, where c:\ dhcp.txt is the full path and file name of the database file that you copied to the server.
    Note: When you try to export a DHCP database from a Windows 2000/2003 domain controller to a Windows Server 2008 member server of the domain, you may receive the following error message:

    Error initializing and reading the service configuration – Access Denied

    Note You must have local administrator permissions to import the data.
    6.To resolve this issue, add the Windows Server 2008 DHCP server computer to the DHCP Admins group at the Enterprise level and redo steps 4 & 5.
    7. If the “access is denied” error message occurs after you add the Windows Server 2008 DCHP server computer to the DHCP Admins group at the Enterprise level that is mentioned in step 6, verify that the user account that is currently used to import belongs to the local Administrators group. If the account does not belong to this group, add the account to that group, or log on as a local administrator to complete the import and redo steps 4 & 5.

    Step:3 - Authorize the DHCP server
    1. Click Start, point to All Programs, point to Administrative Tools, and then click DHCP.
    Note You must be logged on to the server by using an account that is a member of the Administrators group. In an Active Directory domain, you must be logged on to the server by using an account that is a member of the Enterprise Administrators group.
    2.In the console tree of the DHCP snap-in, expand the new DHCP server. If there is a red arrow in the lower-right corner of the server object, the server has not yet been authorized.
    3.Right-click the server object, and then click Authorize.
    4.After several moments, right-click the server again, and then click Refresh. A green arrow indicates that the DHCP server is authorized.

    If you still get error when you run netsh export/import  follow this tip
    you needed to delete any settings you created when you installed DHCP the first time (in DHCP under the server options area) on you new Windows Server 2008 DC.


    How to Migrate WINS:

    1. On the Windows Server 2003 WINS server, if it has any replication partners, stop them. Remove replication partners from the list of WINS replication partners
    2. Stop the WINS server on the Windows 2003 Server and on the target Windows Server 2008 computer. To do this, type the following: net stop wins
    3. Copy the Wins.mdb file (in %systemroot%\System32\Wins folder) from the source to the WINS folder on Windows Server 2008 server
    4. Start WINS on the target Windows Server 2008 server. Type the following:  net start wins
    5. Take the source Windows 2003 server offline
    6. On the target Windows Server 2008 server, use the WINS service to add any existing WINS servers as replication partners