M365 and AZURE Blog: June 2013

Wednesday, June 12, 2013

Install the Exchange 2010 Management Tools on Administrator workstation Command line ( win7 X64)

This article will help to configure Install the Exchange 2010 Management Tools on Administrator workstation windows 7 X64. We will not use GUI option , rather will accomplish the task from command line. Once you get use to install Exchange from command line you will notice , it is a lot easier (-:

First step is to install pre-requisite on the administrator workstation, here is the list

You can install the Exchange 2010 management tools on the following Windows operating systems:

Windows 7
Windows Vista with Service Pack 2 (SP2)
Windows Server 2008 SP2
Windows Server 2008 R2

On the administrator workstation

Click start type and hit enter.

appwiz.cpl

Click on Turn windows features on or off and make sure fallowing futures has been selected.

1. IIS 6 Management Compatibility
2. IIS Metabase and IIS 6 configuration compatibility
3. .Net Framework

After this close the window. Insert Exchange 2010 Sp3 install CD on your workstation or drill down to binaries

Open CMD with administrator privileges

Drill down to Exchange 2010 Sp3 binaries directory

Type fallowing

Setup.com /R:MT

Respectfully,
Oz Casey, Dedeal ( MVP north America)
MCITP (EMA), MCITP (SA)
MCSE 2003, M+, S+, MCDST
Security+, Project +, Server +
http://smtp25.blogspot.com/ (Blog)
http://telnet25.wordpress.com/ (Blog)

Monday, June 10, 2013

Install Active Directory Module Remote Server Administration Windows 7 & 8

We will configure and run PS scripts to manage Active Directory on Win 07 or Win 08 administrator machine and Our Active directory contains least one Win08 R2 domain controller.

Download install proper update for your management computer.

Install KB28972 ( win08 X64)
Install 7887 ( Win07 X64)

Remote Server Administration Tools > Role Administration Tools > AD DS and AD LDS Tools > Active Directory Module for Windows PowerShell

Now we would like to add the PS command into our Profile

Import-Module ActiveDirectory

Open your PS profile

If you do not have one create with this PS command

New-Item -path $profile -type file –force

Copy and paste this PS code in there and save it

$Shell = $Host.UI.RawUI
$Shell.WindowTitle=”E15 PowerWay”
$Shell.BackgroundColor=”Black”
$Shell.ForegroundColor=”White”
$size = $Shell.WindowSize
$size.width=125
$size.height=50
$Shell.WindowSize = $size
$size.width=110
$size.height=300
Import-Module ActiveDirectory
Set-Location C:\admin\Scripts

Adjust the colors and the script folder location based on your preference.

Now we are ready to use AD Module to manage active directory. to see all available cmdlets by typing get-command

Resource:

http://technet.microsoft.com/en-us/library/ee617195.aspx

Tuesday, June 4, 2013

The 'IIS 6 WMI Compatibility' component is required. Install the component, Exchange SP3 Install

Error:
The 'IIS 6 WMI Compatibility' component is required. Install the component via Server Manager.
Click here for help... http://go.microsoft.com/fwlink/?linkid=30939&l=en&v=ExBPA.14&id=0a71c4f6-68de-40f7-94cf-74b73cbda37b

Elapsed Time: 00:00:04

Solution: install missing component via PS

Import-Module ServerManager

Add-WindowsFeature Web-WMI

Step-by-Step Guide for Configuring Windows Server 2012 Domain Controller into existing widows 2008 R2 Forest/Domain with PowerShell

Goal: we will promote our first Windows 2012 domain controller into existing Forest/Domain by using PowerShell installation option. .Please make sure you have tested your application as this will update the schema versions.

http://support.microsoft.com/kb/556086

Forest/Domain name	ZtekZone.com
Applications	Exchange 2010

Step#1

Install Windows 2012 Server and log in log on to server with administer privileges

Step#2

Open PS and rename the Server

Rename-Computer ComputerName

Step#3

Disable IPV6 ( easiest way to use GUI )

PS type

ncpa.cpl

Step#4

Configure Static IP Address ( change the IP address and SM to fit into your scenario)

New-NetIPAddress -IPAddress 10.10.10.101 -InterfaceAlias "Ethernet" -DefaultGateway 10.10.10.1 -AddressFamily IPv4 -PrefixLength 24

Step#5

Set DNS server on the TCP/IP 4 Interface

Add-Computer -DomainName ZtekZone.com

Step#6

You will need to reboot the Server at this point since we re-named the server

ShutDown –r –t 3

After reboot add the server into existing domain

Step#7

Add-Computer –DomainName ZtekZone.com

Step#8

ShutDown –r –t 3

Log back into the server, now server has been added to existing domain , A record for this server has been registered into DNS database, this is just cleaner way of getting ready to promote the server to be the domain controller.

Step#9

Get-windowsfeature AD-Domain-Services

Step#10

install-windowsfeature –Name AD-Domain-Services

Now on the Server C ( root) make folder called scripts and change the directory to there , you need to place the install script

In this directory and below is sample script. You can customize the PS script to fit into your scenario.

Save the script as PS script , give it any name you like, I named this one as…….

“Install_Win2012_domain_Controller.ps1”

Step#11

# You also make sure the site name is correct based on your scenario
# You can change .dit & sysvol, and logs locations based on your install preference
# Credits goes to blogs.technet.com/b/askpfeplat/
# archive/2012/09/06/introducing-the-first-windows-server-2012-domain-controller-part-2-of-2.aspx

Import-Module ADDSDeployment
Install-ADDSDomainController `
-NoGlobalCatalog:$false `
-CreateDnsDelegation:$false `
-CriticalReplicationOnly:$false `
-DatabasePath "C:\Windows\NTDS" `
-DomainName "ZtekZone.com" `
-InstallDns:$true `
-LogPath "C:\Windows\NTDS" `
-NoRebootOnCompletion:$false `
-SiteName "Site-1" `
-SysvolPath "C:\Windows\SYSVOL" `
-Force:$true

# End