Commvault backup and windows server 2008 r2 quiesce error "Failed Unable to quiesce guest file system during snapshot creation"

After getting a new Commvault V11, when tried to backup a windows server 2008 R2, getting "Failed Unable to quiesce guest file system during snapshot creation".



Reason:This issue occurs if there is a conflict between the Microsoft based volume shadow copy services and VMware snapshot provider. 
Fix:
To resolve this issue, use any one Quiescing tool. As VMware snapshot provider is only used for snapshot / Quiesing purposes, this can be disabled.


1. Stop and Disable VMware snapshot provider

2. Start and set VSS to Automatic / Manual

3. Restart Virtual disk service and then  attempt to create a manual Quiesced snapshot. 

F5 BIGIP VE and ESX 6.5, Invalid configuration for device '0' or Failed to connect virtual device 'Ethernet0'

I was receiving "Failed to connect virtual device 'Ethernet0'" and "Invalid configuration for device '0' "error after moved F5 BIGIP VE 13.0.x.x to ESX 6.5 with vcenter 6.5 with distributed switches, and upgraded HW compatibility to version 13.
I searched google and could not find why it was happening.
After I found that the highest VM HW version it support is 10. (https://support.f5.com/csp/article/K69120675)
When you update VM's HW to a higher version, it works with VMware tools to fix any complication,
F5 does not support VMtools to be updated on F5 BIGIP VE. (https://support.f5.com/csp/article/K11744866)

Long story short, here is how I fixed the problem.
1. Turnoff the VM.
2. Download VMX files of the VM to your PC.
3. Go to Edit window the VM, take a screen shot of the nic's setting especially networks they are connected to.
3. Remove all virtual NICs from the VM, and save.
4. Go back to the Edit window again and add NICs, assign correct network. On NIC settings, manually set the MAC address, get the original MAC address from the VMX file you downloaded from the step 2.
5. Turn on the VM.

System Center Updates Publisher (SCUP) 2017 is now avilable

System Center Updates Publisher (SCUP) 2017 is now available

Using SCUP, you can:

• Import updates from external catalogs (non-Microsoft update catalogs). 
• Modify update definitions including applicability, and deployment metadata. 
• Export updates to external catalogs. 
• Publish updates to an update server. 

This release of SCUP adds support for Windows 10 and Windows Server 2016.

Indexing for quicker imports of previously imported catalogs –  Catalog producers can now index their catalogs. This will allow users to more quickly import large catalogs containing few new updates.  

Inclusion of signing certificates within updates catalogs – Catalog producers can now include signing certificates with their updates catalogs.  This enables users to add the certificates to the trusted publishers list during import so that approval prompts will not block publish operations. 

Signature Timestamp – Updates published to a WSUS server will by default have the signature time-stamped.  Note, this functionality requires internet access. If you have upgraded from preview 1 this will not be automatically enabled.  To enable or disable this functionality or configure the timestamp server that is used, see the Advanced page under Options. 

This installer updated my preview 2 (ver 6.0.219.0) version of SCUP 2017 to production version (ver 6.0.278.0)

Announcement is here

Download from here

SCUP 2011 Import: Exception: An error occurred while updating the entries. See the inner exception for details. Updates Publisher xx/xx/xxxx x:xx:xx AM 13 (0x000D)

I was getting error message while updating Dell updates using SCUP 2011


    Import: Skipped import due to no change in creation date for update 56c63df6-5267-44ca-b7d9-78c22b2e9843, title: Intel Unite Protected Guest Access  Plugin Application,3.2.82.42,A00 Updates Publisher 12/26/2017 9:49:19 AM 13 (0x000D)
    Import: Processing XML for package 0dc345fb-52fe-4380-8565-11758a02e64d, length 7397 characters. Updates Publisher 12/26/2017 9:49:19 AM 13 (0x000D)
    Import: Skipped import due to no change in creation date for update 0dc345fb-52fe-4380-8565-11758a02e64d, title: Intel Unite Hub Application Installer,3.1.45.26,A00 Updates Publisher 12/26/2017 9:49:19 AM 13 (0x000D)
    Import: Processing XML for package 56e205cf-16dc-4b63-81d1-a3b748a89c86, length 7364 characters. Updates Publisher 12/26/2017 9:49:19 AM 13 (0x000D)
    Import: Skipped import due to no change in creation date for update 56e205cf-16dc-4b63-81d1-a3b748a89c86, title: Intel Unite Client Application Installer,3.1.45.26,A00 Updates Publisher 12/26/2017 9:49:19 AM 13 (0x000D)
    Import: Processing XML for package 4eaf38b8-b3d8-4596-a6ed-3dd3be80a8d4, length 7525 characters. Updates Publisher 12/26/2017 9:49:19 AM 13 (0x000D)
    Import: Importing new update 4eaf38b8-b3d8-4596-a6ed-3dd3be80a8d4, title: Intel Unite Add-In for Microsoft Outlook,3.2.82.42,A00 Updates Publisher 12/26/2017 9:49:19 AM 13 (0x000D)
    Import: Exception: An error occurred while updating the entries. See the inner exception for details. Updates Publisher 12/26/2017 9:49:19 AM 13 (0x000D)
    Import: Processing XML for package 388a5fae-a141-46d1-8968-6c15501a6a7d, length 7671 characters. Updates Publisher 12/26/2017 9:49:19 AM 13 (0x000D)
    Import: Importing new update 388a5fae-a141-46d1-8968-6c15501a6a7d, title: Intel Unite Plugin for Telemetry for Business Installer,3.2.82.42,A00 Updates Publisher 12/26/2017 9:49:19 AM 13 (0x000D)
    Import: Exception: An error occurred while updating the entries. See the inner exception for details. Updates Publisher 12/26/2017 9:49:19 AM 13 (0x000D)
    Import: Processing XML for package 08cc667b-043d-4afc-89a5-1700560bbbbf, length 4434 characters. Updates Publisher 12/26/2017 9:49:19 AM 13 (0x000D)
    Import: Skipped import due to no change in creation date for update 08cc667b-043d-4afc-89a5-1700560bbbbf, title: Dell OptiPlex 7050 System BIOS,1.6.5 Updates Publisher 12/26/2017 9:49:19 AM 13 (0x000D)

I had 27 of Import: Exception: An error occurred while updating the entries errors and I was scratching my head on this for a few days.
I found a similar problem on https://community.spiceworks.com/topic/1751827-service-pack-3-for-sql-server-2012-breaks-scup-2011-any-suggestions
and
https://social.technet.microsoft.com/Forums/en-US/e8267fe0-9c39-4fdc-8bdc-6b4b471b2e96/scup-fails-importing-of-updates?forum=ConfigMgrCompliance

But I use SQL 2008 so it was not the case.

To fix this problem, there are two options:

1, Get list of all failed updates and delete them individually from the Dell updates, and reimport.

If you miss any failed updates, you will still get the same error!. Delete them all and close SCUP 2011 and open again, and reimport the catalog.

2. Delete the "Dell" folder on the "Updates" and import Dell catalog again.
Warning: You will lose your all of your local information such as "Date Published", "Expired" and "Date Modified" information, if you expired or published and updates.

To delete the "Dell" folder on Updates:
Make a backup of your SCUP DB first (simply do copy and paste of the DB),  SCUP -> Updates -> Overview -> All Software Updates -> Dell. Highlight the "Dell", right click, and delete.


UPDATE: SCUP 2017 production version is now available! and it works much better! http://exchcluster.blogspot.com/2018/04/system-center-updates-publisher-scup.html

That damn event ID 129

I was getting this event id 129 on several server 2012 R2 systems

Log Name:      System

Source:        LSI_SAS

Date:          

Event ID:      129

Task Category: None

Level:         Warning

Keywords:      Classic

User:          N/A

Computer:      

Description:

Reset to device, \Device\RaidPort0, was issued.

and I found this

https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2063346

Changed LSI_SAS to PVSCSI and got:

Log Name:      System

Source:        pvscsi

Date:          

Event ID:      129

Task Category: None

Level:         Warning

Keywords:      Classic

User:          N/A

Computer:      

Description:

Reset to device, \Device\RaidPort0, was issued.

Contacted VMware and they blamed on M$, and told me to upgrade the SAS driver.

Went to broadcom.com site and look for newer driver for "Lsi SAS 3801E", that is what the real name of the "LSI Adaptoer, SAS 3000 series, 8-port with 1068"

https://www.broadcom.com/support/download-search/?pg=&pf=&pn=LSI+SAS+3801E&po=&pa=&dk=

and failed to find any newer drivers for windows 2012 R2, ended up downloading driver for 2008 R2 and replaced it, but still got the event id 129.

Vmware recommended to do https://blogs.technet.microsoft.com/kevinholman/2013/06/21/event-id-129-storachi-reset-to-device-deviceraidport0-was-issued/

but still getting the 129.

Called M$ and they blamed VMware, ended up doing 3way call with VMware and M$, it was fun to hear them blaming each others, and finally they agreed(!) that it was disk system's problem.

Called SAN manufacture and they said there is no error recorded.

Finally I found that event id 129 recorded only when vsphere replication is active.

Called vmware, still was blaming SAN system, and two days later I got this reply:

"I want you to try one more troubleshooting step, which helps to identify and regulate if vSphere Replication is replicating huge data though there are no changes happening on the VM.

This issue is could also be caused by a GuestOS sent unmap command. 

To disable Unmap in the Guest OS:

Using a Windows CMD window on the Host, run the command:

fsutil behavior set DisableDeleteNotify 1

To re-enable the feature, use the following command:

fsutil behavior set DisableDeleteNotify 0

To verify the current setting, use the following command:

fsutil behavior query DisableDeleteNotify

DisableDeleteNotify=0 - indicates the 'Trim and Unmap' feature is on (enabled)

DisableDeleteNotify=1 - indicates the 'Trim and Unmap' feature is off (disabled)

Kindly try the above steps and update the status to us, Awaiting your response."

Tried the solution and the event id 129 is gone, however, if you disable the unmap, you are effectively disabling reclaim function from vSphere, read more about this from: 

https://www.vladan.fr/what-is-vmware-unmap-dead-space-reclamation/

I asked if VMware can make changes so when replication happens the replication process ignore the unmap command. Their answer was "We will surely consider  the inputs suggested by your side which helps us to enhance the product"

Hope this help someone and save their time.

SCCM UEFI OS deployment error 0x80004005

I tried to push Windows 10 through UEFI on SCCM 2016 and got error like this

<![LOG[!sBootDevicePath.empty(), HRESULT=80004005 (e:\qfe\nts\sms\framework\tscore\bootvolume.cpp,34)]LOG]!>

<![LOG[System partition not set]LOG]!>

<![LOG[Unable to find the partition that contains the OS boot loaders. Please ensure the hard disks have been properly partitioned

Unspecified error (Error: 80004005; Source: Windows)]LOG]!>

<![LOG[BootVolume::GetCurrent(pBootVolume), HRESULT=80004005 (e:\qfe\nts\sms\framework\tscore\bootimage.cpp,542)]LOG]!>

The problem was, on "Partition Disk 0 - UEFI" step, I forgot to check "Make this the book disk"

How to create a clustered task to repeat

It is not possible to create a task with single trigger with repeat. In stead, you can created multiple triggers. It is not recommended to add it manually using the gui, when the cluster fail over the manually changed/added triggers will be vanished. Always use powershell to insure multiple triggers stay with the task.

In this example I created a resource specific task (R: is clustered disk 2), this task runs on a node where the R: is active.

$action = New-ScheduledTaskAction -Execute "PowerShell.exe" -Argument "-executionpolicy bypass -file test.ps1" -WorkingDirectory "R:\scripts"
$triggers = @()
$triggers += New-ScheduledTaskTrigger -Daily -At 04:00
$triggers += New-ScheduledTaskTrigger -Daily -At 08:00
$triggers += New-ScheduledTaskTrigger -Daily -At 15:00
$triggers += New-ScheduledTaskTrigger -Daily -At 22:00
Register-ClusteredScheduledTask –Cluster fileClusterServer –TaskName testTask –TaskType ResourceSpecific –Resource "cluster disk 2" –Action $action –Trigger $triggers



The script below is a bit messy but it creates a clustered task that runs on every hour


$action = New-ScheduledTaskAction -Execute "PowerShell.exe" -Argument "-executionpolicy bypass -file test.ps1" -WorkingDirectory "R:\scripts"
$triggers = @()
for ($i=0; $i -le 23; $i++)
{

[string] $j = $i
if ($i -le 9)
{
 $j = "0"+ $j
}
$taksTriggerTime = $j

$taskTime = $j + ":00"

$triggers += New-ScheduledTaskTrigger -Daily -At $taskTime

}   
Register-ClusteredScheduledTask –Cluster fileClusterServer –TaskName testTask –TaskType ResourceSpecific –Resource "cluster disk 2" –Action $action –Trigger $triggers


Note: the resource specific task will run under the system (node), if fail over happens the active node's system account will run the task, folder security will change automagically so you don't have to add all nodes to folder's security tab.
It is not possible to make the task run under some sort of a service account at this point. It runs under only system account.

How to change SCCM reserve disk space for a DP

1) Run SQL query:

select SCR.ID, SCR.Name,SC.NalPath, SCR.Value3 from sc_sysresuse_property SCR join sc_sysresuse SC on SCR.SysResUseID = SC.ID where SCR.name = 'MinFreeSpace' and SC.NALPath like '%%' and SC.RoleTypeID = 3

get SCR_ID

2) Use the returned ID in step 1). Run the below query to update the 'MinFreeSpace' value.
update sc_sysresuse_property set value3 = 'set desired value in MB' where name = 'MinFreeSpace' and ID = ''
Example:
update sc_sysresuse_property set value3 =10240  where name = 'MinFreeSpace' and ID = xxxxxxxxxxxxx

3) Change registry value HKLM\software\Microsoft\SMS\DPreserveddiskspace to match the  number you used on step 2, eg: 10240. 

You don't have to reboot the DP.

Restart the SMS_SITE_Component_Manager service on SCCM site server.

SCOM 2012 r2 console crash after windows patch

After I installed Oct 2016 windows patches
I got this error whenever I tried to open "windows Computers" under "Monitoring"

Application log:
Faulting application name: Microsoft.EnterpriseManagement.Monitoring.Console.exe, version: 7.1.10226.1177, time stamp: 0x5697e092
Faulting module name: ntdll.dll, version: 6.1.7601.23543, time stamp: 0x57d2fde1
Exception code: 0xc000041d
Fault offset: 0x000000000004ef57
Faulting process id: 0x18a0
Faulting application start time: 0x01d228f4261a1d54
Faulting application path: C:\Program Files\Microsoft System Center 2012 R2\Operations Manager\Console\Microsoft.EnterpriseManagement.Monitoring.Console.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 7a5e2e0a-94e7-11e6-ab30-0050569b0035


SCOM console logs:

Problem signature:
  Problem Event Name: APPCRASH
  Application Name: Microsoft.EnterpriseManagement.Monitoring.Console.exe
  Application Version: 7.1.10226.1177
  Application Timestamp: 5697e092
  Fault Module Name: ntdll.dll
  Fault Module Version: 6.1.7601.23543
  Fault Module Timestamp: 57d2fde1
  Exception Code: c0000005
  Exception Offset: 000000000004eef1
  OS Version: 6.1.7601.2.1.0.272.7
  Locale ID: 1033
  Additional Information 1: 383a
  Additional Information 2: 383a5f09f3fd70a29b8be053663a1d2a
  Additional Information 3: 0ebe
  Additional Information 4: 0ebe29effad583805ef4413487a5a75f

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

It seems "October 2016 security monthly quality rollup" is causing the issue
KB3192392 for Windows 8.1 and Server 2012 R2
KB3185332 for Windows server 2012
KB3185330 for Windows server 2008 R2

Remove the KB and restart the SCOM server and it will be fixed.

Clustered task in Windows server 2012 R2 with 0x1 error

I tried to create a clustered task and got 0x1 error, according to M$ it means

0x1: An incorrect function was called or an unknown function was called. (ref: https://support.microsoft.com/en-us/kb/308558)
extra: https://msdn.microsoft.com/en-us/library/windows/desktop/aa383604(v=vs.85).aspx

This is the original script that generated 0x1 error

$action = New-ScheduledTaskAction -Execute "PowerShell.exe" -Argument "runme.ps1" -WorkingDirectory "E:\Shares\scripts"

E: is a clustered disk and I got 0x1 error when I execute the task manually.

Later I found that it has to do with execution policy, so I have changed it to

$action = New-ScheduledTaskAction -Execute "PowerShell.exe" -Argument "-executionpolicy bypass -file runme.ps1" -WorkingDirectory "E:\Shares\scripts"

and it ran without error.


Here is the complete script to create the task
$action = New-ScheduledTaskAction -Execute "PowerShell.exe" -Argument "-executionpolicy bypass -file runme.ps1" -WorkingDirectory "E:\Shares\scripts"
$trigger = New-ScheduledTaskTrigger -Daily -At 3pm
Register-ClusteredScheduledTask –Cluster filesharecluster –TaskName MyResourceSpecificTask –TaskType ResourceSpecific –Resource "cluster disk 2" –Action $action –Trigger $trigger


and this is what the runme.ps1 looks like, as you can see you can run dos command and powershell

dir c:\ | export-csv "e:\shares\scripts\result.csv"

somehow trying to to run bat file also generated 0x1 error, some suggested that the account that runs the task needs to be in "logon as a batch" job in local security policy but I have not tried it yet.

New-RDSessionDeployment : Validation failed for the "RD Connection Broker" parameter

I had this error when I tried to deploy a RDS 2012 R2

PS C:\Users\admin> New-RDSessionDeployment -ConnectionBroker xxx.test.local -SessionHost xxx.test.local
New-RDSessionDeployment : Validation failed for the "RD Connection Broker" parameter.
xxx.test.local      Unable to connect to the server by using Windows PowerShell remoting. Verify that you can
connect to the server.
At line:1 char:1
+ New-RDSessionDeployment -ConnectionBroker xxx.test.local -SessionHost xxx.te ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
    + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,New-RDSessionDeployment


I googled and googled and found no cure...until I tried this...disable IPv6

 

and tried it again, and it worked. Close the current PowerShell and open a new one after you disabled the IPv6.

 

 

 

 





Search query grayed out on in-place hold settings

If you are a domain admin and exchange admin and tried to setup in-place hold setting, you might find the "search query" option is grayed out! You might think "oh no maybe it is the search engine!"
No it is not, you must be a member of "discovery management" group, add your account to be a member of the group, log out form the ECP and log back-in, try to create the in-place hold.

Ok now you done playing with in-place hold and try to delete the in-place hold, and it errors out, and says

Can't remove mailbox search  because there is still at least one mailbox on In-Place Hold.

remove-mailboxsearch will give you the same error, well it has to be disabled first!

Here is a fix:

Set-MailboxSearch   -SourceMailboxes  -InPlaceHoldEnabled $false

If the in-place hold name is "test1" and the last mailbox that are in the in-place hold is "testuser"

Set-MailboxSearch "test1" -SourceMailboxes "testuser" -InPlaceHoldEnabled $false

now remove the in-place hold.

Exchange 2013 disk partition alignment

Visit this page for Exchange 2013 Storage Configuration Options
http://technet.microsoft.com/en-us/library/ee832792(v=exchg.150).aspx


For exchange 2010:
http://exchcluster.blogspot.com/2010/12/disk-partition-alignment-best-practices.html

Trouble shooting exchange 2013 installation problems

1. Errors when you try to install exchange 2013

First,

To fix a problem below, enable IPv6 on the server and DCs, you can disable ipv6 after a successful install.

          if( -not $successfullySetConfigDC)
          {
            Write-ExchangeSetupLog -Error "Unable to set shared config DC.";
          }
        " was run: "Unable to set shared config DC.".

Next..

If you try to install exchange 2013 for the first time and failed, and try again you might see error message below

"Couldn’t attach the data folder 'C:\Program Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\HostController\Data'. Path doesn’t contain old nodes belonging to the system 'Fsis'."


If you try to install using setup.exe, the setup will tell you to use the server recovery mode, it will still fail.

To fix the problem (warning: If you already have Exchange 2010 or older version, do not follow this instruction!, if you follow this instruction it will remove the current exchange server env. as well)

Open ADSI Edit, select and open "Configuration"

Go down to Services, and delete Microsoft Exchange and Microsoft Exchange Autodiscover

Now open "Default naming context"
Delete  Microsoft Exchange Security Groups and Microsoft Exchange Security Objects

On the server that failed to install exchange 2013

Additional steps:
Delete the C:\Program Files\Microsoft\Exchange Server folder and all the contents

Open IIS
and delete
Exchange Back End and Front End websites (it might be default web site, leave it)

Open AD users and Computers

GO under the users and remove
DiscoverySearch Mailbox*
Exchange Online-ApplicationAccount
FederatedEmail.*
Migration.*
*SystemMailbox*
*HealthMailbox*

Open regedit and delete

HKLM\Software\Microsoft\ExchangeServer
HKLM\CurrentControlSet\Services\MSExchange*


And...

If you successfully install the exchange 2013, you might see...



Exception : Microsoft.Exchange.Management.Deployment.ScriptExecutionException: The following error was generated when "$error.Clear();
.
.
blah blah
.
.
                    {
                        $deleteErrorMsg = "Failure cleaning up SearchFoundation Data folder. - " + $dataFolderPath + " - " + $_.Exception.Message;
                        Write-ExchangeSetupLog -Error $deleteErrorMsg;
                    }
                }
            }
        " was run: "Error occurred while uninstalling Search Foundation for Exchange.System.Exception: Cannot determine the product name registry subkey, neither the 'RegistryProductName' application setting nor the 'CERES_REGISTRY_PRODUCT_NAME' environment variable was set
   at Microsoft.Ceres.Common.Utils.Registry.RegistryUtils.get_ProductKeyName()
   at Microsoft.Ceres.Exchange.PostSetup.DeploymentManager.DeleteDataDirectory()
   at Microsoft.Ceres.Exchange.PostSetup.DeploymentManager.Uninstall(String installDirectory, String logFile)
   at CallSite.Target(Closure , CallSite , Type , Object , Object )".


To fix the error (you might see it again when you apply patches) run this from the powershell

$env:CERES_REGISTRY_PRODUCT_NAME = "Search Foundation for Exchange"



And....

When you try to login to ECP or OWA as domain\administrator you might see

WARNING: the object mydomain/Users/Administrator has been corrupted, and it's in an inconsistent state.

The following validation errors happened:

WARNING: Database is mandatory on UserMailbox.

WARNING: Database is mandatory on UserMailbox.

to fix the problem, re-create the mailbox using disable-mailbox and enable-mailbox command.

How to add a domain user to a sudo group in linux

First you must add your linux in to a windows AD, once it is done, login as root or user that is in wheel group.


Execute this command visudo, that will open etc/sudoers file. if you do vi /etc/sudoers vi will give you an permission error. So besure to use visudo without space.


Find a line that looks like this

%wheel     ALL=(ALL)     ALL

put this just below that like (Yes with \\, in linux \ is an escape charator, so we have to put two \ instead of  one \) this...

domain\\username   ALL=(ALL)

example:   If you want to add a user test1 who is in world.com

world\\test1 ALL=(ALL)

and this is an option you can put just behind the line, so it will not ask for a password if you do sudo. a bit of security issue but if you built a test linux machine gotta do lots of sudo, ye it can be your best friend.

NOPASSWD:  ALL

example: world\\test1 ALL=(ALL)  NOPASSWD: ALL


That is all.

Installing Exchange 2013 preview - quick and dirty

What you will need, a domain controller, a windows server 2008 or R2 or 2012 and some pre-req items

I will use an Windows 2008 R2 x64 Enterprise version for this demo.

Download a Exchange server 2013 preview from here : http://www.microsoft.com/exchange/en-us/exchange-preview.aspx

All Exchange 2010 servers in the organization need to be at Exchange 2010 SP3 orlater, and SP3 is not available at this time (2012, July), so if you try to install it on the current Exchange 2010, you won't be able to install it at all.


Pre-req items list

1. Add RSAT-ADDS

On powershell run

Import-Module ServerManager

Add-WindowsFeature RSAT-ADDS

2. Install IIS 7

On powershell run

Import-Module ServerManager\

Add-WindowsFeature Desktop-Experience, NET-Framework, NET-HTTP-Activation, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Web-Server, WAS-Process-Model, Web-Asp-Net, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI


3. Install hotfix 2619234

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


4. Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit.

http://go.microsoft.com/fwlink/?LinkId=238142

5. KB974405

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


6. Microsoft Office 2010 Filter Packs - Version 2.0

http://go.microsoft.com/fwlink/?LinkID=191548

7. Microsoft Office 2010 Filter Packs - Service Pack 1

http://www.microsoft.com/download/en/details.aspx?id=26604



8. Install Windows Media Encoder

http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.LonghornWmvcoreNotInstalled.aspx


9. .Net framework 4.0
http://www.microsoft.com/en-us/download/details.aspx?id=17718

10. .Net framework 4.5

http://msdn.microsoft.com/en-us/library/5a4x27ek(v=VS.110).aspx

11. Windows Management Framework 3.0

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

12. Exchange Server 2013 Preview isn't compatible with Microsoft Visual C++ 11 Beta Redistributable (x64) 11.0.050531. Please uninstall it before you install Exchange 2013 Preview.
Uninstall Microsoft Visual C++ 11 Beta using "programs and feafures"



Installation steps

1. Install all pre-req items, and reboot.

2. Fully patch the new windows 2008 r2 server.

3. Run the exchange-x64.exe, it will ask a place to extract the files.

4. Choose a folder to extract.


5. Go to the folder and execute the setup.exe file

6. On Check for updates, I chose not to check, Next






7. Copying files, Next




8. Introduction screen, Next




9. Accept the license term, Next




10. Error reporting, choose no, and Next




11. On checking required software, Next




12. Installation space and location, Next





13. On Malware protection settings, select Yes to disable it and Next





14. On configure client access server, select , "this client server role will be internet-facing" and fill out the domain information




15. On customer experience improvement program window, click Next.






16. Readiness checks, wait until it finishes its task.





17, Once all check got passed, Next


18, setup will start



19, Installed



If you get "The WS-Management service does not support the request" error when you open the exchange powershell execute the command below on command prompt

%SystemDrive%\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -ir -enable

and reset the  IIS by runnig

IISReset


2013 OWA with new office 2013 logo

First look of OWA 2013

 

Options page

Installed Apps page