Extending Basic Disks on windows server 2003 using DISKPART.exe does not work.
To extend the basic disk with 3rd party tool using EXTPART. ExtPart is a small tool developed by dell Industries and which helps to extend disk on windows 2003 servers as follows
Usage:

extpart [volume size]

volume - the volume to extend. e.g. f:, g:, etc (only basic volumes)

size - the size in megabytes by which to extend the volume.

Example:

To extend the g: volume by 1 GB (1024 MB) use the following command:

extpart g: 1024

Download Link: http://www.dell.com/support/drivers/in/en/19/driverdetails?driverid=R64398

1. Log out of the Citrix online Plug-in on the Win 7 machine and log back on as the citrix user account. Launch the WinWord application.
2. Use the Citrix online plug-in to log on as the domain\citrix user
   1. Click the Citrix online Plug-in icon and click Notepad to launch the application
3. Log on to the XenAppServer machine as the CitrixAdmin user, log on to the Web Interface using the CitrixAdmin account through Internet Explorer and launch the Notepad application
4. Switch to the win 7 virtual machine
5. Log on to the win 7 virtual machine as the CitrixAdmin user
6. Click Start > Internet Explorer and navigate to the Web Interface site athttp://xenappservername/citrix/xenapp.
7. Log on to the Web Interface as the CitrixAdmin user.
8. Launch the Notepad application.An error appears. The load evaluator that was created and applied to XenAppServer is reporting a full load and is no longer accepting connections.
9. Log off of the Web Interface and close Internet Explorer.

Enables system administrators to view and evaluate individual users' usage and experience with Microsoft Exchange Server.

Use the Microsoft Exchange Server User Monitor to gather real-time data to better understand current client usage patterns, and to plan for future work. Administrators can view several items, including IP addresses used by clients, versions and modes of Microsoft Office Outlook, and resources such as CPU usage, server-side processor latency, and total latency for network and processing. Works with Microsoft Exchange Server 2000, 2003, 2007 and 2010.

Source: http://www.microsoft.com/en-us/download/details.aspx?id=11461

Additionally exchange servers can be monitored trough built-in performance tools such as Performance Monitor and Performance Troubleshooter under EMC Toolbox.

Also PowerShell can be used to obtain e.g. top 10 users that are most actively using Exchange Server:

Get-StoreUsageStatistics -Database Database1 | Sort-Object TimeInserver -Descending | Select-Object -First 10 | ft -AutoSize

Get-StoreUsageStatistics -Server Server1 | Sort-Object TimeInserver -Descending | Select-Object -First 10 | ft -AutoSize

try www. Kanbanflow.com

you can measure your Resource productivity with out paying a single penny

There can be a number of reasons why the IMA Service appears not to have started, including the following:

• IMA Service load time

• IMA Service subsystem

• Missing Temp directory

• Print spooler service

• ODBC configuration

• Roaming Profile

• Another server with an identical NetBIOS name on the same network

IMA Service Load Time

If the Service Control Manager reports that the IMA Service could not be started, but the service eventually starts, ignore the error message.

The Service Control Manager has a timeout of six minutes. The IMA Service can take longer than six minutes to start if the load on the database exceeds the capabilities of the database hardware or if the network has high-latency.

IMA Service Subsystem

Examine the following Windows Registry setting:
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\IMA\Runtime\CurrentlyLoadingPlugin

If there is no value specified in the CurrentlyLoadingPlugin portion of the above Windows Registry entry, then either the IMA Service could not connect to the data store or the local host cache is missing or corrupt.

If a CurrentlyLoadingPlugin value is specified, the IMA Service made a connection to the data store and the value displayed is the name of the IMA Service subsystem that failed to load.

Missing Temp Directory

If administrators see an “IMA Service Failed” error message with an error code of 2147483649 when starting the MetaFrame XP Presentation Server, the local system account might be missing a Temp directory which is required for the IMA Service to run.

To gain further insight into the situation, change the IMA Service startup account to the local administrator and restart the server. If the IMA Service is successful in starting under the local administrator’s account, then it is likely that a missing Temp directory for the local system account is causing the situation.

If the Temp directory is not present, then manually create one as <roor directory>\Temp. For example:
C:\Winnt\Temp

Also, verify that the TMP and TEMP system environment variables point to the temporary directory. Restart the server to restart the IMA Service.

Print Spooler Service

When the MetaFrame XP Presentation Server attempts to start the IMA Service, the “Setup Could Not Start The IMA Service” error message appears. This error shows that the IMA Service is not starting, possibly because the print spooler service is not running or was configured incorrectly. In addition, the following error messages appear in the Event Viewer:

• Failed to load plugin MfPrintSs.dll with error 80000001h

• Failed to load initial plugins with error 80000001h

• The Independent Management Architecture service terminated with service-specific error

The error occurs because the print spooler service:

• Has stopped

• Is disabled

• Is not configured to run under the Local System Account

To correct this error, verify that the print spooler service was started in the context of system rather than in the context of a user. A print spooler service that is not running or has been configured incorrectly might cause the printing subsystem to fail to load.

To resolve the situation, stop and start the print spooler service, making sure that it is configured to run under the Local System Account. Then, try to start the IMA Service.

ODBC Configuration

1. Verify that the Microsoft SQL Server or Oracle server is online.

2. Verify the name of the DSN file that the IMA Service is using by looking at the following key in the Windows Registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\IMA\DataSourceName.

3. Attempt to connect to the database using the DSN file with an ODBC test utility such as Oracle ODBC Test or SQL Server ODBC Test.

4. Verify that the correct user name and password are being used for database connectivity.

5. Change the user name and password using the DSMAINT CONFIG command, if needed using dsmaint config /user:username /pwd:password /dsn:dsnfilename

6. Enable ODBC Tracing for further troubleshooting.

Roaming Profile

When the MetaFrame XP Presentation Server attempts to start the IMA Service, the “Setup Could Not Start The IMA Service” error message appears. In the event viewe,r you might see the following error: IMA_RESULT_INVALID_MESSAGE or other events related to the IMA Service not being able to start.

Verify the size of the roaming profile, especially if it is crossing a WAN. Also watch for error messages related to not being able to load the profile. Test with a local user profile or one that is smaller in size.

Another server with an identical NetBIOS name on the same network

Verify that there is not another server on the network with the same NetBIOS name on the network. If the CurrentlyLoadingPlugin has the ImaLicSs.dll listed, this might be an indication of this condition. Another symptom of ImaLicSs.dll is from the MetaFrame XP SP4 Readme:

“106. The IMA Service failed to start because of license group corruption in the data store.

Note: This fix prevents corruption in the data store but it does not correct any corruption that may already exist. You need to check for corruptions present in the data store and correct them using the appropriate tools.

Procedure to find out WWN information from ILO:

Log on to ILO and open remote console. Reboot the box by clicking ctrl-alt-del tab as marked in the screen shot.

Press F11 when you see the below screen followed by any key to view option ROM Messages

Keep pressing Ctrl+e when you see below screen to enter Emulex BIOS Utility.

You will get the below screen where you can enter the choice either 1 or 2 to get WWN details of the server.

In this case choice 1 has been selected and below are the WWN details.

Connect the SSP image like below or copy the SSP pakage on the Server

Click Apply

Run the Setup from the %drive%hp/swpakages/Setup.exe

Click on Start inventory

Build inventory from the location of %drive%hp/swpakages

Select local host for checking installation check list

A similar screen will appear when you have software inventory

Uncheck the option listed below

Then click on install

Once after the installation – Reboot the server and monitor the reboot process from ILO