Find WWNs in Windows 2012(r2)

To find FibreChannel WWNs in Windows you can type the following powershell commands:

Get-InitiatorPort |Format-Table –AutoSize

or if you only nee the NodeWWN type:

Get-WmiObject -class MSFC_FCAdapterHBAAttributes -namespace „root\WMI“ | ForEach-Object {(($_.NodeWWN) | ForEach-Object {„{0:x}“ -f $_}) -join :“}

Source: https://technet.microsoft.com/de-de/library/hh848671(v=wps.630).aspx

 

 

Exchange 2013 Pre-Requisites on Windows 2012

 

Installing Exchange 2013 on Windows 2012 ne some prerequisites:

To install them we can use Powershell:

 

CAS and Mailbox-Roll:

Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, 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-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation, RSAT-ADDS

If you want to install the Schema-Updates from the Exchange 2013 Server you have to install the RSAT-ADDS feature too.

Else if you want to install the Schema-Updates on a DC you don´t have to install the RSAT-ADDS features on the Exchange Server but it won´t hurt

After successfull install you need to restart the machine.

Then we need some more tools to be installed:

Microsoft Unified Communications Managed API 4.0, Core Runtime 64-Bit:
http://go.microsoft.com/fwlink/p/?linkId=258269

Microsoft Office 2010 Filter Pack (64 Bit):
http://go.microsoft.com/fwlink/p/?linkID=191548

Microsoft Office 2010 Filter Pack SP1 (64 Bit):
http://go.microsoft.com/fwlink/p/?LinkId=254043

VMWare vSphere ESXi 5.1.0 Installation shows “No Network Adapters”

 

If you try to install VMware ESXi 5.1 and get the error “No Network Adpaters” found you possible have disabled them in the BIOS.

On HP Servers Generation 8 press F9 to enter BIOS settings

Check PCI Components if they are enabled or not

Enable the Ethernet Adapters

On HP Servers if they are enabled and you still get the error you have to use the customized HP Installations ISO

This can be found at:

Customize VMware ESXi Images for HP ProLiant Servers:
http://h18004.www1.hp.com/products/servers/software/vmware/esxi-image.html

Installing vCenter 5.1 on Windows 2012 fails with error 2064843076

 

Installation of VMWare vCenter 5.1 (VMware-VIMSetup-all-5.1.0-1235309.iso) on Windows 2012 fails at Microsoft SQL Server Express Edition installation with errorcode 2064843076

This happends when you run the VMware autorun.exe not with elevated Administrator rights.

Just use “run as Administrator” and it will work.

Hyper-V – System Center Virtual Machine Manager 2008 R2 Error 12711, The cluster group could not be found (0x1395)

While trying to Live Migrate a VM on Hyper-V with SCVMM you get the following error:

Error (12711)
VMM cannot complete the WMI operation on server <Hyper-V-Hostname> because of error: [MSCluster_ResourceGroup.Name=“a1e132f2-9f0d-41f3-8cdb-8a6562bf68c2″] The cluster group could not be found.

(The cluster group could not be found (0x1395))

Recommended Action
Resolve the issue and then try the operation again.

This problem comes up because of different VMResourceGroupID´s in the SCVMM Database and Hyper-V Host.

The VM maybe was imported or exported without refreshing the Host in SCVMM or removed from the Cluster and added back again.
If this happen you can do an export of the VM and import it back into the Hyper-V Cluster with SCVMM.

This means a downtime for your VM!

If you need a non-downtime fix you have to change the information on the SQL Database of the SCVMM.

First tpye the following text into powershell on the host running the VM

# Add the SCVMM snapin to the powershell
Add-PSSnapin microsoft.systemcenter.virtualmachinemanager

# Connect to the Hyper-V-server
Get-VMMServer –ComputerName Hyper-V-Server.fqdn.tld

#write the not working VM into the variable $VM
$vm = get-VM -name „problematic-vm.fqdn.tld“

#force a refresh of the vm
refresh-vm -force $vm

you will get the ID of the VM
write this ID down we need it later again

Now you have to change the wrong ID in the SVCMM Database with the right on from the Hyper-V Host

First we have to find the true ID of the VM.

Therefore open the registry-editor on the Hyper-V Host running the VM
goto: \\HKLM\Cluster\Groups\

find the Name of the VM and copy the ID on the left side.

– Now open the SQL Database using Mangement Studio Express

– find the table “dbo.tbl_WLC_VMInstance” in the SCVMM Database.

– find the VM by his name in the table

– goto VMResourceGroupID column

– check the ID in this cell wheter or not the ID in the cell is the same as found in the powershell

– change the ID of the VM in the cell “VMResourceGroupID” to the ID of the registry

– restart the SCVMM console (no server-reboot needed)

– do a refresh of ALL hosts

– try to move the VM again

Attention this fix is not proofen by Microsoft.
Use this at your own risk!!!

thx to workinghardinit

 

EventID 104 MSExchange Search Indexer

 

Sollte der Fehler mit der Event ID 104 auftreten so kann dies an einer nicht angehaengten Datenbank liegen.

Datenbanken die aktuell nicht eingehaengt sind koennen nicht indiziert werden und produzieren den folgenden Fehler.

Fehler bei der Exchange-Suchindizierung beim Aktivieren der Postfachdatenbank <DB Namen> (GUID = <DB-GUID>) nach 1 Versuchen. Der letzte Fehler war: MapiExceptionMdbOffline: Unable to Get Catalog State (hr=0x80004005, ec=1142)
Diagnostic context:
    Lid: 1494    —- Remote Context Beg —-
    Lid: 44215 
    Lid: 60049   StoreEc: 0x8004010F
    Lid: 49469 
    Lid: 65341   StoreEc: 0x8004010F
    Lid: 56125 
    Lid: 47933   StoreEc: 0x8004010F
    Lid: 32829 
    Lid: 49213   StoreEc: 0x8004010F
    Lid: 48573 
    Lid: 64957   StoreEc: 0x8004010F
    Lid: 31321   StoreEc: 0x476    
    Lid: 1750    —- Remote Context End —-
    Lid: 19154   StoreEc: 0x476    
    Lid: 22081   StoreEc: 0x476     . Der nächste Versuch erfolgt nach 10 Minuten.

 

Loesung: entweder Datenbank wieder Mounten oder falls nicht benoetigt Datenbank loeschen.

Ueberpruefung: Um zu testen ob der Fehler danach noch auftritt sind folgende Schritte moeglich:

1. Dienst Neustarten

Stop-Service MSExchangeSearch
Start-Service MSExchangeSearch

2. Exchange Diagnose Test durchfuehren

Test-ExchangeSearch

Updating HP Drives on Smart Array E200 generates 0x81 error

When trying to update the following HP drives to Firmware HPDC (16. Jan 2012) :

DH036ABAA5
DH036BB977
DH072BB978
DH072ABAA6

on a e200 SmartArray controller you will get this error:

[command failure (cmd=0h, err=00h, dlu=081:0h)]

The only way to get out of this circle is to press F8 asap when you see this message.

If your System boots up from this controller you won´t be able to boot until you manage to get into the controller configuration utility with F8 at the right time.

Just enter the controller configuration settings end exit with ESC.
Don´t change any settings.
If you managed this the Server will reboot and comes up with the error:

1719-Slot X Drive Array – A controller failure event occurred prior to this power-up. (Previous lock up code = 0x81)

After this message the server OS boots up again.

The problem is the E200 SmartArray controller which does NOT support onlineupdates of this harddrives.
This problem occurs if you do an onlineupdate under Windows with the HP SUM or HP Servicepack for Proliant.

To fix this you have to do an offline update with the firmware DVD or usb.

error issuing replication 8453 (0x2105) replication access was denied

 

UAC hit once again.

This error happens when your try to run repadmin /syncall in a commmandline with UAC enabled but not elevated.
Even if you are an Domain-Admin.

Solution:
Run the repadmin /syncall command in an elevated commandline.

A general system error occurred/ Ein allgemeiner Systemfehler ist aufgetreten. VMWare ESX VMotion Fehler

 

If you get these error message while trying to migrate a running VM from one VMWare vSphere ESX 4.0 Host to another you have to do as followed:

In the vCenter Logs you can find these messages:

(vmodl.fault.SystemError) {
dynamicType = <unset>,
faultCause = (vmodl.MethodFault) null,
reason = „“,
msg = „A general system error occurred: „,

Ein allgemeiner Systemfehler ist aufgetreten:
Failed to initialize migration at source.
Error 0xbad00a4.
VMotion failed to start due to lack of cpu or memory resources.

1. check VMWare vSphere Build

connect to your ESX Host with putty, login and type: vmware –v

the output shows the version your server is running.
If the Version is

VMware ESX 4.0.0 build-261974

than you have a buggi version and your host needs at least a reboot to migrate VMs successfully again.

Better you upgrade to a newer vSphere version which fixes this problem.

some other build just need some different workarounds:

2. Workarounds

– Reboot machine (shutdown all VMs and move them, then reboot the host)

– connect to ssh console and type:

service mgmt-vmware restart
service vmware-vpxa restart

– check if ping and vmkping is working

nslookup <other-ESX-Hosts>
ping <other-ESX-Hosts>
vmkping <other-ESX-Hosts-kernel-IP>
arping -I vswif0 <other-ESX-Hosts-kernel-IP>

– check if VMKernel Gateway is configured right

– Disable and re-enable Migration on host:

Goto
Host->configuration->advanced settings->migrate
and change option:
migrate.enabled = 0
wait some time and change it back to:
migrate.enabled = 1

Fortigate Webfilter Error

 

If you get an error while browsing the internet saying:

“Web Page Blocked, an error occurred while trying to rate the website using the webfiltering service.

Web filter service error: no response from urlfilter”

then most likely the Fortigate Firewall needs a restart because of a firmware update.

In Fortigate Cluster settings you have to restart all Members of the Fortigate HA-Cluster.