Articles for Microsoft Products

How to extend a data volume in Windows Server

How to extend a data volume in Windows Server

How to use Diskpart.exe to extend a data volume in Windows Server 2003, in Windows XP, and in Windows 2008

You can use the Diskpart.exe utility to manage disks,   partitions, and volumes from a command-line interface. You can use Diskpart.exe   on both Basic disks and Dynamic disks. If an NTFS volume resides on a hardware   RAID 5 container that can add space to the container, you   can extend the NTFS Volume with Diskpart.exe while the disk remains a Basic   disk.
Use the extend command to incorporate unallocated space into an existing volume   while preserving the data.
The following are the requirements for the   extend command:

  • The volume must be formatted with the NTFS file system.
  • For Basic volumes, the unallocated space for the extension must be the next contiguous space on the same disk.
  • For Dynamic Volumes, the unallocated space can be any empty area on any Dynamic disk on the system.
  • Only the extension of data volumes is supported. System or boot volumes may be blocked from being extended, and you may receive the following error:
    Diskpart failed to extend the volume. Please make sure the volume is valid for extending
  • You cannot extend the partition if the system page file is located on the partition.  Move the page file to a partition that you do not want to extend.

To extend a partition or volume, you must first select the   volume to give it the focus, and then you can specify how large to make the   extension. To extend a volume, follow these steps:

  1. At a command prompt, type diskpart.exe.
  2. Type list volume to display the existing volumes on the computer.
  3. Type Select volume volume number where volume number is number of the volume that you want to extend.
  4. Type extend [size=n] [disk=n] [noerr]. The following describes the parameters:
    size=n The space, in megabytes (MB), to add to the current partition. If you do not specify a size, the disk is extended to use all the next contiguous unallocated space.
    disk=n The dynamic disk on which to extend the volume. Space equal to size=n is allocated on the disk. If no disk is specified, the volume is extended on the current disk.
    noerr For scripting only. When an error is thrown, this parameter specifies that Diskpart continue to process commands as if the error did not occur. Without the noerr parameter, an error causes Diskpart to exit with an error code.
  5. Type exit to exit Diskpart.exe.

When the extend command is complete, you should receive a message that states   that Diskpart successfully extended the volume. The new space should be added   to the existing drive while maintaining the data on the volume.
Note In   Windows XP and in  Windows 2000, you cannot use Diskpart.exe to extend a simple volume on a Dynamic disk that was originally created on a Basic disk. You can extend only simple volumes that were created after the disk was upgraded to Dynamic disk. If you try to extend a simple volume on a Dynamic disk that was originally created on a Basic disk, you receive the following error message. This restriction was removed in  Windows Server 2003.

Diskpart failed to extend the volume.   Please make sure the volume is valid for extending
Source link

Microsoft Exchange Links

Microsoft Exchange Links for documentation

Microsoft Exchange 2003

Microsoft Exchange 2007

Microsoft Exchange 2010

Exchange Server 2010 Database Availability Group Installation Step by Step

Exchange 2010 on VMware – Availability and Recovery Options

Exchange Server 2010 Mailbox Server Backup and Recovery

Logging SMTP Protocol Activity in Exchange 2010 and Exchange 2007

 

SMTP Routing in Exchange 2010

Part1  Part2 Part3 Part4

Microsoft Exchange 2013

Exchange 2013 System Requirements

What’s New in Exchange 2013

 

Microsoft Exchange Blogs

http://www.exchange-genie.com/2009/04/database-availability-group-dag-exchange-2010/

 

 

How to convert Physical machine as virtual hard disk

How to convert Physical machine as virtual hard disk

Disk2vhd is a utility that creates VHD (Virtual Hard Disk – Microsoft’s Virtual Machine disk format) versions of physical disks for use in Microsoft Virtual PC or Microsoft Hyper-V virtual machines (VMs). The difference between Disk2vhd and other physical-to-virtual tools is that you can run Disk2vhd on a system that’s online. Disk2vhd uses Windows’ Volume Snapshot capability, introduced in Windows XP, to create consistent point-in-time snapshots of the volumes you want to include in a conversion. You can even have Disk2vhd create the VHDs on local volumes, even ones being converted (though performance is better when the VHD is on a disk different than ones being converted).

Disk2vhd includes command-line options that enable you to script the creation of VHDs. Specify the volumes you want included in a snapshot by drive letter (e.g. c:) or use “*” to include all volumes.

Usage: disk2vhd <[drive: [drive:]…]|[*]> <vhdfile>

Example: disk2vhd * c:\vhd\snapshot.vhd

Download link :- http://download.sysinternals.com/files/Disk2vhd.zip

 

Restoring a Domain Controller Through Reinstallation

Restoring a Domain Controller Through Reinstallation

Applies To: Windows Server 2008, Windows Server 2008 R2

Restoring a domain controller through reinstallation is the same process as creating a new domain controller. It does not involve restoring from backup. This method relies on Active Directory replication to restore a domain controller to a working state, and it is valid only if another healthy domain controller exists in the same domain. This method is normally used on computers that function only as domain controllers.

Restoring through reinstallation is the only method by which a domain controller that is not part of the backup set can be restored. In addition, you might decide to use this method instead of a nonauthoritative restore because backup media is inaccessible or because this method is more convenient. Restoring a domain controller through reinstallation should not be a substitute for regular backup routines.
Continue reading Restoring a Domain Controller Through Reinstallation

Commands and Tools for Managing Windows Server 2008 Server Core

Commands and Tools for Managing Windows Server 2008 Server Core

you have a minimal UI that includes a limited desktop environment for local console management of the server. This minimal interface includes:

  • Windows Logon screen for logging on and logging off
  • Notepad for editing files
  • Regedit for managing the registry
  • Task Manager for managing tasks and starting new tasks
  • Command Prompt for administration via the command line

After you log on to a core-server installation, you have a limited desktop environment with an Administrator command prompt. You can use this command prompt for administration of the server. If you accidentally close the command prompt, you can start a new command prompt by following these steps:
1. Press Ctrl+Shift+Esc to display Task Manager.
2. On the Applications tab, click New Task.
3. In the Create New Task dialog box, type cmd in the Open field and then click OK.

You can start Notepad and Regedit directly from a command prompt by entering notepad.exe orregedit.exe as appropriate. To open Control Panel, type intl.cpl.

 

Here is an overview of key commands and utilities you’ll use for managing server core installations while logged on locally:
Control desk.cpl – View or set display settings.
Control intl.cpl – View or set regional and language options, including formats and the keyboard layout.
Control sysdm.cpl – View or set system properties.
Control timedate.cpl – View or set the date, time, and time zone.
Cscript slmgr.vbs –ato – Activate the operating system.
DiskRaid.exe – Configure software RAID.
ipconfig /all – List information about the computer’s IP address configuration.
NetDom RenameComputer – Set the server’s name and domain membership.
OCList.exe – List roles, role services, and features.
OCSetup.exe – Add or remove roles, role services, and features.
PNPUtil.exe – Install or update hardware device drivers.
Sc query type=driver – List installed device drivers.
Scregedit.wsf – Configure the operating system. Use the /cli parameter to list available configuration areas.
ServerWerOptin.exe – Configure Windows Error Reporting.
SystemInfo – List the system configuration details.
WEVUtil.exe – View and search event logs.
Wmic datafile where name=“FullFilePath” get version – List a file’s version.
Wmic nicconfig index=9 call enabledhcp – Set the computer to use dynamic IP addressing rather than static IP addressing.
Wmic nicconfig index=9 call enablestatic(“IPAddress”), (“SubnetMask”) – Set a computer’s static IP address and network mask.
Wmic nicconfig index=9 call setgateways(“GatewayIPAddress”) – Set or change the default gateway.
Wmic product get name /value “ – List installed MSI applications by name.
Wmic product where name=“Name” call uninstall – Uninstall an MSI application.
Wmic qfe list – List installed updates and hotfixes.
Wusa.exe PatchName.msu /quiet – Apply an update or hotfix to the operating system.

source link :- click here

How to install product key after evaluation expired SCOM

How to install product key after evaluation expired SCOM

How to add a product key to an eval version of System Center 2012 Operations Manager

To set the product key, use the Set-SCOMLicense cmdlet in PowerShell. To use the Set-SCOMLicense cmdlet you need to use elevated permissions. (Run as Administrator).

1. Open PowerShell as an Administrator

2. Load the OperationsManager Module

import-module operationsmanager

3. Connect to your ManagementGroup

SCOMManagementGroupConnection

4. Use Set-SCOMLicense -ProductId “yourlicensekey“
Set-SCOMLicense -ProductId ‘C97A1C5E-6429-4F71-8B2D-3525E237BF62’

5. To check if changes were executed run Get-SCOMManagementGroup | ft skuforlicense, version, timeofexpiration –a

Note: This may require a reboot after running in order to register correctly.

For more information on the Set-SCOMLicense cmdlet see http://technet.microsoft.com/en-us/library/hh920237.aspx

Source link :- http://support.microsoft.com/kb/2699998

How to remove RDP history

How to remove RDP history

To remove entries from the Remote Desktop Connection Computerbox in the Windows Remote Desktop Connection client, start Registry Editor, and then click the following registry key:

HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Default

Entries appear as MRUnumber, and are visible in the right pane. To delete an entry, right-click it, and then click Delete.

Removing Entries in the Mac Remote Desktop Connection Client

To remove entries from the Remote Desktop Connection Computerbox in the Mac Remote Desktop Connection client, delete the Users:Username:Library:Preferences:Microsoft:RDC Client:Recent Servers file.

Notes

The list of all destination connections (including previous connections) are stored in an MRUnumbervalue in the following registry key:

HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Default

Every new connection is given the value of MRU0, and the other values are then sequentially moved down in number. The MRU value can contain a Fully Qualified Domain Name or an IP address of the computer to which you connect. For example:

MRU0 REG_SZ 192.168.16.60
MRU1 REG_SZ computer.domain.com

Disable Shutdown Event Tracker in Windows 2003

Disable Shutdown Event Tracker in Windows 2003
Open Group Policy, then load the group policy you want to apply the change to. Note: On a computer that is not a part of a domain you can set this feature locally by running GPEDIT.MSC from the Run command.

1- Expand Computer Configuration > Administrative Templates > System.

2-Double-click Display Shutdown Event Tracker.

3-Select Disabled.

4-Click OK to close all dialog boxes.

5-If you want the change to take place right now, refresh the GPO by running the following command in a Command Prompt window or from the Run command: gpupdate /force

 

\

How to find windows uptime

How to find windows uptime

Option 1:
1.  Go to “Start” -> “Run“.
2.  Write “CMD” and press on “Enter” key.
3.  Write the command “net statistics server” and press on “Enter” key.
4.  The line that start with “Statistics since …” provides the time that the server uptime.

The command “net stats srv” can be use instead.
Option 2:

Uptime.exe Tool Allows You to Estimate Server Availability with Windows NT 4.0 SP4 or Higher
http://support.microsoft.com/kb/232243