Wednesday, March 26, 2014

Exchange Server Back Pressure

Back pressure is a resource monitoring feature with Exchange servers which build into Transport service. ( Mailbox Servers ) The idea is to have Exchange Server detect the issues and take necessary action so the messaging servers wont be completely un available.

There are 4 event ID associated with correlating events and actions messaging server would perform.

Figuring out such event can be very usefully when back pressure becomes the issue.

# Explain event descriptions
Write-Host "--------------------------                              ------------------------------"
Write-Host "Event ID 15004 = Resource pressure increased" -Fore Cyan
Write-Host "Event ID 15005 = Resource pressure decreased" -Fore Cyan
Write-Host "Event ID 15006 = Low available disk space" -Fore Yellow
Write-Host "Event ID 15007 = Low available memory" -Fore Yellow
Write-Host "---------------------------                                  ------------------------"

image

To automate the process we have developed PS script. You can download from TechNet scripting library.

image

Special thanks to Benjamin Bohn for taking his time and turning my simple script into great resource script.

Stay tuned until next time.

Best regards,
Oz Casey , Dedeal
MCITP (EMA), MCITP (SA)
MCSE 2003, M+, S+, MCDST
Security+, Project +, Server +
Http://smtp25.blogspot.com (Blog)
Http://telnet25.wordpress.com (Blog)

Saturday, March 22, 2014

Migrate DHCP Service from Windows 2003 onto Windows 2008 R2

We will migrate DHCP Service from windows 2003 DC onto Windows 2008 R2 DC. Just follow the simple steps to get the work done

Environment :

  • Source Server  windows 2003 ( DC,GC) DHCP Installed here server name is = Server
  • Destination Server Windows 2008 R2 ( DC,GC) = We will migrate DHCP Service and all related configurations here
  • Log into Source Server where DHCP is installed
  • Click Start Open Cmd.exe

Netsh dhcp server export c:\temp\dhcp.txt

Make sure temp directory exist if not create one on the C drive….

image

Now log into Target Server

  • Click start
  • In the search type
  • ServerManager.msc
  • Hit enter
  • Click Add Roles

image

image

image

image

image

image

image

image

image

image

image

image

image

image

  • Now you need the file we have created earlier to import into this server
  • I am going to connect the first server and get the file we have created which does have all existing settings for the DHCP server

image

image

I am going to copy the dhcp.txt file onto server1 onto temp directory

Click Start

Type Cmd.exe and hit enter

type following and hit enter

Netsh dhcp server import c:\temp\dhcp.txt

 

image

Now open back to DHCP management

If you refresh all your existed settings are now in this new DHCP Scope

image

Last thing we need to do is to go back and un-install DHCP services from source server, running DHCP from two servers will same scope will be ugly (-:

Log back onto first server

image

image

image

image

image

image

Well done you have completed DHCP migration

Stay tuned until next time.

Best regards,
Oz Casey , Dedeal
MCITP (EMA), MCITP (SA)
MCSE 2003, M+, S+, MCDST
Security+, Project +, Server +
Http://smtp25.blogspot.com (Blog)
Http://telnet25.wordpress.com (Blog)

Wednesday, March 19, 2014

PowerShell to Discover the Holders of Active Directory FSMO Roles

FSMO roles always been one of the most hot topics of every interview I have ever been. Even for Exchange Server interviews. Knowing the FSMO roles makes your job easy and understanding Active Directory for sure keeps your place in Exchange world safer.

If you need refresher for the FSMO Just take a look at this question. Considering having single FOREST if you have 12 domains, how many FSMO roles in total exist ? Id your answer is not 38 then you need the refresher (-: and here id nice summary Why do We Need FSMO Roles

You can quickly Fire up CMD and type

NetDom Query FSMO

image

Or you can open PowerShell

$Domain = Get-ADDomain | select -ExpandProperty Name

image

Get-ADDomain $Domain | fl PDCEmulator,RIDMaster,InfrastructureMaster

image

Or here is the simple script can show you the FSMO roles for your Domain Name Space

http://gallery.technet.microsoft.com/scriptcenter/Find-FSMO-Roles-6950d3c7

image

Stay tuned until next time.

Best regards,
Oz Casey , Dedeal
MCITP (EMA), MCITP (SA)
MCSE 2003, M+, S+, MCDST
Security+, Project +, Server +
Http://smtp25.blogspot.com (Blog)
Http://telnet25.wordpress.com (Blog

Monday, March 10, 2014

The Windows component RSAT-Clustering-CmdInterface isn't installed on this computer and needs to be installed before

 

Installing Exchange 2013 SP1, receiving error “The Windows component RSAT-Clustering-CmdInterface isn't installed on this computer and needs to be installed before”

image

On the problem server open PowerShell with administrator privileges and use following PS command

Install-WindowsFeature RSAT-Clustering-CmdInterface



image


image


Verify ….





Get-WindowsFeature | where-object {$_.Installed -eq $True} | fl name,*RSAT*

 


image


image


image


Stay tuned until next time.


Best regards,
Oz Casey , Dedeal
MCITP (EMA), MCITP (SA)
MCSE 2003, M+, S+, MCDST
Security+, Project +, Server +
Http://smtp25.blogspot.com (Blog)
Http://telnet25.wordpress.com (Blog)