AD Photo Edit comes in two editions: Free Edition is completely free for any number of users at any number of locations Bulk Edition costs $59 for a single site license and $130 for an enterprise license

Use the below link for downloading the free version

http://www.cjwdev.co.uk/Software/ADPhotoEdit/Info.html

Here I am explaning how to get the Users mailbox size,deleted items size and item count size in the exchange management shell.

Get-MailboxDatabase | Get-MailboxStatistics |ft displayname,totaldeleteditemsize,itemcount

1) First we need to check the Domain fuctional level -On the Windows Server 2003 Domain Controller, run Active Directory User and Computers snap-in by clicking on Start > Administrative Tools > Active Directory User and Computers

If you have Windows 2000 Active Directory domain controllers then choose Windows 2000 native, if you do not have any Windows 2000 Active Directory domain controllers and all of your domain controllers are Windows Server 2003, then choose Windows Server 20003. I don’t have any Windows 2000 Active Directory domain controllers, so using the drop down list, I will select Windows Server 2003 and then click the Raise button.

2) Prepare Cureent Windows 2003 active directory

• Before you can have a 2008 server domain controller in your existing 2003 domain, we will need to prepare both the Forest Level and the Domain level, this is done by running the following commands on the Windows Server 2003 Domain Controller.
• Insert the Windows Server 2008 DVD inside the Windows Server 2003 DVD Drive

Open Command Prompt, this is done by Clicking on Start > Run > type CMD > click OK
Type D:\sources\adprep\adprep /forestprep (Where D: is the drive of your Windows 2008 DVD)

After Forest preparation is completed successfully, run the Domain preparation command

Inside CMD, type D:\sources\adprep\adprep /domainprep (Where D: is the drive of your Windows 2008 DVD)

Although adprep /domainprep will update the domain-wide information, you can still run the last command adprep /domainprep /gpprep

Courtsey

http://www.elmajdal.net/Win2k8/Migrating_Active_Directory_Domain_Controller_from_Windows_Server_2003_to_Windows_Server_2008.aspx

Second  step

Setting Up an Additional Domain Controller With Windows Server 2008

1. Now that Windows Server 2003 Active Directory has been prepared for Windows Server 2008 Domain Controllers, its time to Set Up an Additional Domain Controller With Windows Server 2008 and set it as a Global Catalog. If you already have an additional Windows Server 2008 domain controller and you want to check if it is a Global Catalog or not, then check my article Setting a Windows Server 2008 Domain Controller as a Global Catalog

See the website courtsey:http://www.elmajdal.net/Win2k8/Setting_Up_an_Additional_Domain_Controller_With_Windows_Server_2008.aspx

Third step

Setting a Windows Server 2008 Domain Controller as a Global Catalog

To set an additional Domain Controller as a Global Catalog Server, follow the below steps:

1. Open Active Directory Sites and Services, click Start > Administrative Tools > then click Active Directory Sites and Services
2. From the left side pane, expand Sites > Default-First-Site-Name ( If you have renamed the Site name, then this name will reflect your Site name) > Servers > Domain Controllers
3. Now expand the Windows Server 2008 that you want to set as a Global Catalog and right Click its NTDS Settings then click on Properties
4. Under the General Tab, there is a check box beside Global Catalog, if it is unselected then this means that this Domain Controller is not a Global Catalog, if you do want to set it as a Global Catalog server, then select this checkbox and click on Apply then OK. The process it takes the Global Catalog to replicate itself throughout the forest takes time depending on your Active Directory infrastructure.

Courtsey:http://www.elmajdal.net/Win2k8/Setting_a_Windows_Server_2008_Domain_Controller_as_a_Global_Catalog.aspx

Fourth Step

Transferring FSMO Roles in Windows Server 2008

The five FSMO roles are:

1. Schema Master
2. Domain Naming Master
3. Infrastructure Master
4. Relative ID (RID) Master
5. PDC Emulator

The FSMO roles are going to be transferred, using the following three MMC snap-ins :

• Active Directory Schema snap-in : Will be used to transfer the Schema Master role
• Active Directory Domains and Trusts snap-in : Will be used to transfer the Domain Naming Master role
• Active Directory Users and Computers snap-in : Will be used to transfer the RID Master, PDC Emulator, and Infrastructure Master roles

Courtsey:http://www.elmajdal.net/win2k8/Transferring_FSMO_Roles_in_Windows_Server_2008.aspx

Caution: After you upgrade Exchange 2010 to a newer service pack, you can’t uninstall the service pack to revert to the previous version. If you uninstall the service pack, you remove Exchange from the server.

You should upgrade your Exchange 2010 server roles in the following order:

1. Client Access
2. Hub Transport
3. Unified Messaging
4. Mailbox

The Edge Transport server role can be upgraded at any time. However, we recommend upgrading the Edge Transport server role either before or after all other server roles are upgraded.

Prerequisites

• Ensure that any server on which      you plan to install the service pack meets the system requirements. For      more information about system requirements, see Exchange      2010 System Requirements.

Permissions

To perform the following procedures, the account you use must be a member of the Delegated Setup management role group or the Organization Management management role group.

To apply an Exchange 2010 service pack to an Exchange 2010 server that has the Edge Transport server role installed, the account you use must be a member of the local Administrators group on that computer.

To upgrade a computer that has only the Exchange management tools installed, you must log on using an account that’s a member of the local Administrators group on that computer.

If you haven’t yet prepared the schema for Exchange 2010 SP1, the account you use to upgrade the server must be a member of the Schema Admins group and the Enterprise Admins group. This requirement also applies if you’re installing Exchange 2010 SP2 and haven’t yet prepared the schema for it. For more information, see Prepare Active Directory and Domains

Upgrade load balanced Client Access array members

If your organization uses a load balanced array of Client Access servers, see the following guidance about how to upgrade your Client Access servers from one version of Exchange 2010 to another, for example, from Exchange 2010 RTM to Exchange 2010 SP1. If you have an array of Client Access servers that you need to upgrade from one version to another, use the following steps.

1. Determine the number of Client Access server array members that can be offline at one time without negatively impacting service. For example, if you have six Client Access servers in a load balanced array and have designed your load balancing solution to handle three simultaneous failures, you can have three Client Access server array members offline.
2. To continue with the example, disable new connections to the three servers and allow for the existing connections to end. After all connections have been terminated, remove those servers from your load balancing pool.
3. Upgrade those three servers to the target version. Verify that the upgrade was successful.
4. Add the upgraded servers back into the load balanced array.
5. Prepare to remove the servers that have not been upgraded from the load balanced array by disabling new connections.
6. Confirm all the connections to the servers identified in step 5 have been terminated, and then remove those servers from the load balanced array.
7. Upgrade the second batch of servers to the target version of the software. Verify that the upgrade was successful.
8. Add the most recently upgraded servers back into the array.

Upgrade database availability group members

When you apply an Exchange 2010 service pack to a database availability group (DAG) member, you need to consider and plan for some specific issues. Before applying an Exchange 2010 service pack to any DAG members, consider the following:

• Upgrade only passive servers      Before applying the service pack to a DAG member, move all active mailbox      database copies off the server to be upgraded and configure the server to      be blocked from activation. If the server to be upgraded currently holds      the primary Active Manager role, move the role to another DAG member prior      to performing the upgrade. You can determine which DAG member holds the      primary Active Manager role by running Get-DatabaseAvailabilityGroup      -Status | Format-List PrimaryActiveManager.
• Place server in maintenance mode      Before applying the service pack to any DAG member, you may want to adjust      monitoring applications that are in use so that the server doesn’t      generate alerts or alarms during the upgrade. For example, if you’re using      Microsoft System Center Operations Manager 2007 to monitor your DAG      members, you should put the DAG member to be upgraded in maintenance mode      prior to performing the upgrade. If you’re not using System Center      Operations Manager 2007, you can use StartDagServerMaintenance.ps1      to put the DAG member in maintenance mode. After the upgrade is complete,      you can use StopDagServerMaintenance.ps1      to take the server out of maintenance mode.
• Stop any processes that might      interfere with the upgrade Stop any      scheduled tasks or other processes running on the DAG member or within      that DAG that could adversely affect the DAG member being upgraded or the      upgrade process.
• Verify the DAG is healthy      Before applying the service pack to any DAG member, we recommend that you      verify the health of the DAG and its mailbox database copies. A healthy      DAG will pass MAPI connectivity tests to all active databases in the DAG,      will have mailbox database copies with a copy queue length and replay      queue length that’s very low, if not 0, as well as a copy status and      content index state of Healthy.
• Be aware of other implications of      the upgrade A DAG member running an older      version of Exchange 2010 can move its active databases to a DAG member      running a newer version of Exchange 2010, but not the reverse. After a DAG      member has been upgraded to a newer Exchange 2010 service pack, its active      database copies can’t be moved to another DAG member running the RTM      version or an older service pack.

Run the following scripts and commands on the DAG member being upgraded to prepare for the service pack.

1. Verify the health and status of the DAG by saving the following commands as a Windows PowerShell script (.ps1) file.

Copy Code

(Get-DatabaseAvailabilityGroup -Identity (Get-MailboxServer -Identity $env:computername).DatabaseAvailabilityGroup).Servers | Test-MapiConnectivity | Sort Database | Format-Table -AutoSize

Get-MailboxDatabase | Sort Name | Get-MailboxDatabaseCopyStatus | Format-Table -AutoSize

function CopyCount

{

$DatabaseList = Get-MailboxDatabase | Sort Name

$DatabaseList | % {

$Results = $_ | Get-MailboxDatabaseCopyStatus

$Good = $Results | where { ($_.Status -eq ”Mounted”) -or ($_.Status -eq “Healthy”) }

$_ | add-member NoteProperty ”CopiesTotal” $Results.Count

$_ | add-member NoteProperty ”CopiesFailed” ($Results.Count-$Good.Count)

}

$DatabaseList | sort copiesfailed -Descending | ft name,copiesTotal,copiesFailed -AutoSize

}

CopyCount

1. Perform a server switchover by running the following command.

Copy Code

Move-ActiveMailboxDatabase -Server

1. Prevent the DAG member from becoming a failover target by running the following command.

Copy Code

Set-MailboxServer -DatabaseCopyAutoActivationPolicy:Blocked

1. If necessary, move the primary Active Manager role to another DAG member by running the following command.

Copy Code

Cluster group “cluster group” /move

1. Install the Exchange 2010 service pack. For details, see “Install the Exchange 2010 service pack” later in this topic.
2. Enable the upgraded DAG member to become a failover target by running the following command.

Copy Code

Set-MailboxServer -DatabaseCopyAutoActivationPolicy:Value

Where Value is either IntrasiteOnly or Unrestricted.

1. Repeat steps 1–6 on each DAG member until the service pack has been applied to every DAG member.

For more information, see the following topics:

• Perform a      Server Switchover
• Move-ActiveMailboxDatabase
• Set-MailboxServer
• Understanding      Mailbox Database Copies

Install the Exchange 2010 service pack

When installing a new Exchange 2010 service pack on multiple Exchange 2010 servers within an organization, we recommend that you first upgrade your Client Access servers. In an organization that has multiple Active Directory sites that use multiple Client Access servers in a proxy situation, you must upgrade the Internet-facing Client Access servers before upgrading Client Access servers that aren’t Internet-facing. Then, we recommend you install the Hub Transport, Unified Messaging, and Mailbox server roles.

The Edge Transport server role can be upgraded at any time. However, we recommend upgrading the Edge Transport server role either before or after all other server roles are upgraded.

1. Insert the Exchange 2010 SP1 or Exchange 2010 SP2 DVD into the DVD drive. When the AutoPlay dialog box appears, click Run Setup.exe under Install or run program. If the AutoPlay dialog box doesn’t appear, navigate to the root of the DVD and double-click Setup.exe. Alternatively, browse to the location of your Exchange 2010 installation files and double-click Setup.exe.
2. On the Start page, click Install Microsoft Exchange Server Upgrade to begin the installation.

1. The Introduction page begins the process of installing Exchange into your organization. It will guide you through the installation. Click Next to continue.
2. On the License Agreement page, review the software license terms. If you agree to the terms, select I accept the terms in the license agreement, and then click Next.
3. On the Readiness Checks page, view the status to determine if the organization and server role prerequisite checks completed successfully. If they haven’t completed successfully, you must resolve any reported errors before you can install Exchange 2010. You don’t need to exit Setup when resolving some of the prerequisite errors. After resolving a reported error, click Retry to run the prerequisite check. Be sure to also review any warnings reported. If all readiness checks have completed successfully, click Upgrade to install the service pack.
4. On the Completion page, click Finish.

Use unattended setup to install the Exchange 2010 service pack

1. Insert the Exchange 2010 SP1 or Exchange 2010 SP2 DVD into the DVD drive, and then at the command prompt, navigate to the DVD drive or navigate to the network location of the Exchange 2010 installation files.
2. At the command prompt, run the following command.

Error Message “The ‘IIS 6 WMI Compatibility’ component is required” During Exchange 2010 SP2 Upgrade

While attempting to upgrade an Exchange Server 2010 Client Access server to Service Pack 2 you may encounter the following error message.

The ‘IIS 6 WMI Compatibility’ component is required. Install the component via Server Manager

This error occurs because a new feature of Exchange 2010 SP2 called Outlook Web App Mini requires that IIS component to be installed on Client Access servers.

You can install the component manually by opening a PowerShell window and running the following commands.

PS C:\> Import-Module servermanager

PS C:\> Add-WindowsFeature Web-WMI

Success Restart Needed Exit Code Feature Result
------- -------------- --------- --------------
True    No             Success   {IIS 6 WMI Compatibility}

Click Retry on the Readiness Checks dialog box above, or if you’ve already cancelled the installation simply start it again.

You can also avoid the error by installing the Service Pack 2 upgrade from the command line. Open a command prompt and navigate to the folder where the Exchange 2010 SP2 files have been extracted, and run the following command:

C:\Admin\ex2010sp2>setup /mode:upgrade /installwindowscomponents

This will automatically install the required components for you when the upgrade process runs.

Copy Code

Setup.com /M:Upgrade /InstallWindowsComponents

There are two ways to take a CAS array member our of the NLB cluster:

• Issue a Stop command to the server
• Issue a Drainstop command to the server

The difference between the two is that Stop will immediately stop the server regardless of who is currently connected to it, while Drainstop will put the server in a state where it will not accept new connections but will continue serving existing connections until they disconnect.

For urgent updates a Stop command may be necessary, but for planned maintenance a Drainstop has the least potential impact on active client connections to the CAS array.

To issue a Drainstop launch Network Load Balancing Manager, right-click on the desired server, choose Control Host and then Drainstop.

When the server has no more active connections it will be in a stopped state.

Right click the server and choose Properties. Set the default state of the server to Stopped. This will prevent it from automatically starting and accepting client connections after any reboots that the updates require, to allow you time to verify the updates were successful first before rejoining the NLB cluster

Stop Conflicting Services

The Client Access Server role is often installed on the same server as the Hub Transport server role, even when deployed as a CAS array.

Hub Transport servers often run additional applications such as antivirus and anti-spam software that hooks into the Exchange Server services. These can cause conflicts with Exchange Server updates, for example if a third party application tries to automatically restart a service that it depends on that has been stopped by the update process.

Forefront is one example of this, so for servers running Forefront Protection for Exchange those services can be stopped using FSUtility.

C:\> fsutility /disable

Disabling Monitoring

If the CAS array members are monitored using SCOM or another system this should also be disabled, or placed into maintenance mode before the update is performed. This prevents unnecessary alarms in the monitoring system due to stopped services or server restarts, and also prevents the monitoring agent from trying to perform any automatic remediation such as restarting services.

Backing Up the Server

Some organizations will require an ad-hoc backup be run of at least one CAS array member before updates are applied. Others will be happy to rely on the latest scheduled backup instead. And some will even be satisfied that multiple CAS array members exist and so if a bad update puts one of them out of action there is no outage to end users, and the server can simply be manually reinstalled.

Updating the Server

Install the update following the procedure for that update type.

Update rollups come in the form of a .MSP file (Windows Installer Patch) that is applied to the server. Simply double-click the file or launch it from a command line window.

Service packs are a complete reissue of the Exchange Server setup files and are installed by running setup in upgrade mode, which can be run in either graphical or command line mode.

C:\> setup /m:upgrade

Both update rollups and service packs can take some time to install, so plan a large window of time for these updates.

Verifying the Update

After the update has completed, and if necessary the server rebooted, you should check the server’s health before placing it back into production in the CAS array.

Event Logs – look for error or warning events that have started since the update was applied.

Setup Logs – service packs write a complete setup log file to C:\ExchangeSetupLogs

Services – check the Exchange services are running (or at least those that you expect to be running, some such as IMAP and POP will be stopped if you have not explicitly enabled them)

[PS] C:\>get-service *exchange*

Status   Name               DisplayName

——   —-               ———–

Running  MSExchangeAB       Microsoft Exchange Address Book

Running  MSExchangeADTop… Microsoft Exchange Active Directory…

Running  MSExchangeAntis… Microsoft Exchange Anti-spam Update

Running  MSExchangeEdgeSync Microsoft Exchange EdgeSync

Running  MSExchangeFBA      Microsoft Exchange Forms-Based Auth…

Running  MSExchangeFDS      Microsoft Exchange File Distribution

Stopped  MSExchangeImap4    Microsoft Exchange IMAP4

Running  MSExchangeMailb… Microsoft Exchange Mailbox Replication

Stopped  MSExchangeMonit… Microsoft Exchange Monitoring

Stopped  MSExchangePop3     Microsoft Exchange POP3

Running  MSExchangeProte… Microsoft Exchange Protected Servic…

Running  MSExchangeRPC      Microsoft Exchange RPC Client Access

Running  MSExchangeServi… Microsoft Exchange Service Host

Running  MSExchangeTrans… Microsoft Exchange Transport

Running  MSExchangeTrans… Microsoft Exchange Transport Log Se…

Stopped  msftesql-Exchange  Microsoft Search  (Exchange)

Running  vmickvpexchange    Hyper-V Data Exchange Service

Returning the Server to Production

If the update was successful and the server healthy then it can be placed back into production.

Re-enable services such as Forefront Protection for Exchange.

C:\> fsutility /enable

Start the server in the NLB cluster.

Rename the User Profile folder using Windows Explorer

• Logon to an admin account that is not the account being renamed.
• Open the Documents and Settings folder, by typing this in Start, Run dialog:

%systemdrive%\Documents and Settings

• The list of folders will be displayed. Select the corresponding folder of the  user account that you want to rename.

Example

%SystemDrive%\Documents and Settings\OldUsername

becomes

%SystemDrive%\Documents and Settings\NewUsername

Next step is to notify the system that the user profile path has changed.

Changing the ProfileImagePath value in the registry

ProfileImagePath registry value

The ProfileList registry key contains some sub-keys, which are nothing but the list of User Account Security  Identifiers (SID). Each of the SID represents an Account. The key is located  here:

HKEY_LOCAL_MACHINE \ SOFTWARE\ Microsoft\ Windows NT \ CurrentVersion \ ProfileList

Identify the SID for your User account, and change the Profile path

• To know the SID for your user account, you may use the  script sidlist.vbs
• Download the script and run it.  (The User Account names and SIDs will be listed in a log file, and opened  automatically.)
• Note down the SID for  your account.
• Then, in the Registry Editor, select the correct SID that belongs to your  user account.
• In the right-pane, double-click the ProfileImagePath value and change  the profile path. ( The ProfileImagePath stores the full path  of the User account home folder. )

Close Registry Editor, and restart Windows. See if you’re able to logon to  that user profile successfully. Additionally, to verify if the path has been  changed successfully, type SET in the Command Prompt. In case you find any  abnormal behavior when running an application, you may undo the above  procedure.

To identify the user’s profile path by the user SID

1. Use the Getsid tool from the Windows Server Resource Kit to obtain the SID. At a command prompt, use the following syntax:
   getsid \\ComputerName UserName \\ComputerName UserName

   For example:

   getsid \\windowsxp joedoe \\windowsxp joedoe

   The results look something like this:

   = The SID for account WINDOWSXP\joedoe is S-1-5-21-1708537768-1993962763-1957994488-1003
2. After you obtain the user SID, start Registry Editor (Regedit.exe or Regedt32.exe), and then select the user SID under the following registry key:
   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList

How to enable scripting in your browser

This website is giving very useful information  for finding the lost iPhone by using mobileme features.

A problem has been found with the Outlook clients after applying the RU4 update. Microsoft made a change in the RU4 release to make deleted public folders recoverable. However, there was a side effect to that change. According to an Exchange team blog post, “Outlook and Exchange are not correctly processing the folder move and copy operations causing the folder contents to appear to be deleted.”

The items within a copied folder do not get copied over to the new location. However, they are not wholly lost. Instead, they can be recovered from the “recoverable items” folder (previously known as the “dumpster”), according to the Exchange team. Still, those IT organizations with the RU4 problems likely will face much grief having to track the displaced data.

Microsoft recommends that customers defer applying the RU4 release. However, if RU4 has already been installed in a computing environment, then IT pros should contact Microsoft Customer Support to obtain an Interim Update. The reference for this Interim Update is “KB 2581545,” but Microsoft’s blog noted that a live link to that Knowledge Base article isn’t available yet, so Customer Support is the only way to get the Interim Update for now.

Microsoft plans to issue a fix for the RU4 issue in Exchange 2010 SP1 in the next Update Rollup 5, which is scheduled for availability sometime in August. This fix will prevent content loss at the target location when folders are moved or copied. Microsoft’s Exchange team is also working with the Outlook client development team on the issue.

Microsoft’s blog post claimed that “a small number of customers” have reported the problem. Some responses by customers in Microsoft’s blog post even indicated that there were no apparent problems after installing RU4. However, other comments in the blog expressed dismay, such as “I wish I could send the bill for my time back to MS for this.”

All versions of the Outlook client are affected by the RU4 issue, according to the blog comments, although Outlook Web App and Exchange Web Services are not affected by this flaw. Exchange 2007 SP3 RU4 is not affected, according to Microsoft’s blog.

Those receiving the Interim Update from Microsoft will need to install it “on all CAS and Mailbox servers that have SP1 RU4 installed,” according to Ross Smith IV of Microsoft.

Fix:

Follow the procedure below to repair original boot.ini file

1. Firstly arrange a Bootable Windows XP setup CD.
2. Boot from bootable Windows XP setup CD and press R to enter recovery console which allows to restore the corrupted boot.ini file to original.
3. Now enter your administrative username and password, when you get the command prompt type the following command “bootcfg /rebuild” (without double quotes) and press Enter.
4. Bootcfg utility on the Windows XP setup CD will scan your drives for any Windows XP installations and then display the results which you can select to repair the corresponding boot.ini file.
5. The first prompt asks to Add installation to boot list? (Yes/No/All).  type “Y” (without double quotes) and press enter.
6. The next prompt asks to Enter Load Identifier ” This is nothing but the name of the operation system which appears at the time of Booting ” :type Windows XP Professional or Windows XP Home Edition or simply Windows XP and press Enter.
7. Now it will ask to Enter OS Load options: type /Fastdetect and press Enter.
8. Take the Windows XP bootable CD out from the tray and Type exit and then press Enter to restart your PC.