Using SCOM 2007 R2 to monitor the level of coffee - so cool

http://blog.coretech.dk/opsmgr07/opsmgr-2007-r2-scom-coretech-coffee-monitor-management-pack-0001/

Intro:

This management packs can be used to keep track of the level of coffee in left in the pot.

With this management pack, you will never run dry of, what we all know, is the most important part of a productive environment!

This is mostly made as a proof of concept, as this technique can be transferred to other monitor types. It could be expanded with other types of sensors, like a weight to check the level of coffee instead of a camera, or a thermometer to check the temperature of the coffee.

This is the very first version. It has been tested in test environments.

By default, it will trigger a warning when under 50% is left, and a Critical Alert when under 20% is left.

Please do not hesitate to report any bugs and please send suggestions for the next version you might have.

This was developed by Jakob Gottlieb Svendsen with the help of Kåre Rude Andersen

Windows 2000 with Hyper-V

One requirement from customer is to p2v standalone SQL 2000 on Windows 2000 Advanced Server to Hyper-V and duplicate the image then building the cluster from this... seem to be it can be done.. .. but it's not gonna work at all.....
- server name change (2 new server name -> old server name will be use as db cluster name)
- application reconfiguration -> big problem...

so building new windows 2000 cluster and manually migrate it to new environment

hold on a second...

Check out this link ...

http://www.microsoft.com/windowsserver2008/en/us/hyperv-supported-guest-os.aspx

Hyper-V only support 1 vCPU for Windows 2000 Server
1 vCPU -> should be ok...

BUT the real problem is...

Hyper-V is not support SCSI Controller on Windows 2000 Server so stuck now
-> guest clustering is required SCSI Controller for shared disk... (can be either vhd or pass-through).. but hold on a second.....
What's about iSCSI... yeah... it should work fine ...

But... i would say.. building new cluster environment with Windows Server 2003 should be a better way...SQL Server 2000 Clustering on Windows Server 2003 is not an issue.

guest clustering with pass-through disk -> must be on the difference host...
But Microsoft only support using iSCSI for the guest clustering also

BSOD Intel Xeon 5500 Seires with Windows Server 2008 R2

0x00000101 (parameter1, 0000000000000000, parameter3, 000000000000000c)
CLOCK_WATCHDOG_TIMEOUT
Get the hotfix from here....
http://support.microsoft.com/kb/975530

NetBackup - Bare Metal Restore - Failed to verify backup --rc(%1)

Got some issues to do bare metal restore at one of the customer and find out that the problem is come from valid client
http://seer.entsupport.symantec.com/docs/311920.htm
rc=135..
The production server is still running and they try to restore it to another machine on the same network that i believe it's not gonna work ... hostname and ip address conflict....

Installing SQL Server 2008 on Windows Server 2008 R2

Pre-requisites
- .NET Framework v3.5.1 Features (it will pop up a dialog about required role (Web Server) just accept it
- Components that need to add for Web Server Roles
- Common HTTP Features
- Static Content
- Default Document
- Directory Browsing
- HTTP Errors
- HTTP Redirection
- Application Development
- ASP.NET
- .NET Extensibility
- ASP
- ISAPI Extensions
- ISAPI Filters
- Health and Diagnostics
- HTTP Logging
- Request Monitor
- Security
- Basic Authentication (Optional)
- Windows Authentication
- Client Certificate Mapping Authentication (Optional)
- IIS Client Certificate Mapping Authentication (Optional)
- Request Filtering
- Performance
- Static Content Compression (Optional)
- Dynamic Content Compression (Optional)
- Management Tools
- IIS Management Console
- IIS 6 Management Compatibility (Optional)
- IIS 6 Metabase Compatibility (Optional)
- IIS 6 WMI Compatibility
- IIS 6 Scripting Tools
- IIS 6 Management Console

SQL Server SP 1 is required to run on Windows Server 2008 R2 also.

Windows Firewall with SQL
http://msdn.microsoft.com/en-us/library/cc646023.aspx
Just an idea for the port required
Integration – 135
SRS – 80
Analyses – 1434
SQL - 1433

Slipstream an installation of SQL Server 2008
http://support.microsoft.com/kb/955392

Exchange 2007 LCR with DPM 2007

You need to disable the VSS replica Writer on that LCR DB by registry and restart the services
add the EnableVssWriter key as a DWORD with a value of 0 under
HKLM\Software\Microsoft\Exchange\Replay\Parameters
then restart the Microsoft Exchange Replication Service

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

Shutdown Exchange Server 2007

Especially when you running on domain controller it will take a long time to shutdown and sometime the services have been kill without proper shutdown so it might end up your exchange database is corrupt so use this sequence to do a clean shutdown exchange....

net stop msexchangeadtopology /y
net stop msftesql-exchange /y
net stop msexchangeis /y
net stop msexchangesa /y
net stop iisadmin /y

In case you want to start exchange manually -> use this sequence to start up
net start "World Wide Web Publishing Service"
net start "Microsoft Exchange Information Store"
net start "Microsoft Exchange System Attendant"
net start "Microsoft Search (Exchange)"
net start "Microsoft Exchange Information Store"
net start "Microsoft Exchange Unified Messaging"
net start "Microsoft Exchange Transport Log Search"
net start "Microsoft Exchange Transport"
net start "Microsoft Exchange Service Host"
net start "Microsoft Exchange Search Indexer"
net start "Microsoft Exchange Replication Service"
net start "Microsoft Exchange Mail Submission"
net start "Microsoft Exchange Mailbox Assistants"
net start "Microsoft Exchange File Distribution"
net start "Microsoft Exchange EdgeSync"
net start "Microsoft Exchange Anti-spam Update

Network Teaming with Hyper-V

It's quite old news but yeah now it's already supported by Microsoft.

The thing is you need to Add Hyper-V Role and install all the hot fixes before you install teaming software / drivers. If not it might not working...

Manually add a VM Configuration to Hyper-V

1. Create the link to the xml file
mklink "%systemdrive%\ProgramData\Microsoft\Windows\Hyper-V\Virtual Machines\5A0EAC7A-2079-467B-A95D-7D1368DD6A35.xml" "E:\Virtual Machines\SXXXXXX\5A0EAC7A-2079-467B-A95D-7D1368DD6A35.xml"
2. Grant the Service SID to the xml file
icacls "%systemdrive%\ProgramData\Microsoft\Windows\Hyper-V\Virtual Machines\5A0EAC7A-2079-467B-A95D-7D1368DD6A35.xml" /grant "NT VIRTUAL MACHINE\5A0EAC7A-2079-467B-A95D-7D1368DD6A35":(F) /L
3. Grant the Service SID the all the file
icacls E:\Virtual Machines\SXXXXXX\ /T /grant "NT VIRTUAL MACHINE5A0EAC7A-2079-467B-A95D-7D1368DD6A35":(F)

Quite complicated... maybe create new one with existing disk is a better idea but..be careful about new GUID and mac address also...

Undocument about network properties for Cluster Shared Volumes with Hyper-V R2

Managed to setup Hyper-V R2 cluster on Cluster Shared Volumes with Windows Server 2008 R2 (Server Core) and everything is working fine... BUT... why when using Full Installation having an issues??????? Can't remember exactly the error message but......

DO NOT DISABLE - Client for Microsoft Networks and File and Print Sharing on Heartbeat network.. that's it...

on server core can't find the way to uncheck it so leave it as default.. that's why it's working without any problem...

Not sure that what is the recommend from Microsoft for other clustering i think should uncheck it if you are not using cluster shared volumes...

BTW -> Change the priority of network also
Heartbeat should be the lowest one 1,000

Live Migration -> 1,100

Production -> 10,000

By default if network is used for public it will start with 10,000, Internal start from 1,000
Use Powershell to check the priority

Get-ClusterNetwork | ft Name, Metric, AutoMetric
Name Metric
---- ------
Heartbeat 1000
LiveMigration 1100
Production 10000

Change the metric by using this command.
$cn = Get-ClusterNetwork ""
$cn.Metric =

Cluster Shared Volumes
-> Pass-through disk is not supported
-> GPT Partition is not supported so it the size is limit to 2TB per LUN
*** can't find the link about this anymore but seem to be now GPT already supported...***
-> All the LUNS will mount to C:\ClusterStorage\Volume1, C:\ClusterStorage\Volume2....
-> C:\ClusterStorage can't changed.
-> VolumeXX can be changed -> C:\ClusterStorage\LUN01-VMs
-> DPM 2007 SP1 not supported but DPM 2010 yes..
-> I heard that CA Arcserve Backup already supported.
-> Recommend to separate network for live migration -> tested with cross cable throughput is up to 130MB/sec (1Gbps)

will continue

SCOM 2007 "Unexpected Shutdown" where is it?

By default it's not enabled so you have to create it
New -> Monitor Objects -> Windows Events -> Simple Event Detection -> Manual Reset -> select System Log
- Event ID: 6008
- Event Source: EventLog

But you will get this alert after the server is online again NOT when the server is down the reason why is because this message will write to event log after the windows startup and when SCOM agent detect this message it will forward to SCOM Server.

Server down -> no SCOM agent -> no engine to detect message -> no communication between server and agents

Actually when the server is down you will get alert from SCOM Server about "Management software failed", "Failed to connect to the computer" and if your server running another applications (sql, exchange, etc) you will get alerts from application management pack also...

Another thing is for this 2 alerts ("Management software failed", "Failed to connect to the computer" it will automatic closed when the server is online again. You might not get this alerts if you are running on virtualization platform because when the server reboot it might take less than 1 min.....

SCOM 2007 -> Setup cannot locate the SC database

Check out the SQL Server Configuration Manager to enable "TCP/IP" and "Named Pipes" especially when using remote database and SPN Registration also...

Changed of service name in SCOM 2007 R2

SCOM 2007 SP1 -> SCOM 2007 R2
"OpsMgr SDK Service" -> "System Center Data Access"
"OpsMgr SDK Service" -> "System Center Management Configuration"
"OpsMgr Health Service" -> "System Center Management"

MOMCertImport.exe error: ‘The application failed to initialize properly (0xc0150002). Click OK to terminate the application.

Problem is some .NET components is required.
Open momcertimport.exe with notepad and go to the end of the file you will see this..
assemblyIdentify ........ "Microsoft.VC90.CRT" version="9.0.30729.1"

so you need to get this library install on the server (Microsoft Virtual C++ 2008 SP1)

Microsoft Virtual C++ 2008 SP1 -> 9.0.30729.1
Microsoft Virtual C++ 2008 -> 9.0.21022.8

http://www.microsoft.com/DOWNLOADS/details.aspx?familyid=A5C84275-3B97-4AB7-A40D-3802B2AF5FC2&displaylang=en

Or...
Actually MOMCertImport.exe is just add an entry of certificate to the registry so it can be done manually..
1. Check the serial number of the certificates from Details tab (mmc -> certificates -> computer account)
2. Create new Binary Value "ChannelCertificateSerialNumber" -> HKLM\Software\Microsoft Operations Manager\3.0\Machine Settings but in the "REVERSE" order
Example : serial number is ab 12 cd 34 ef 56 -> enter it as 56 ef 34 cd 12 ab
Then restart health service
R1 -> "OpsMgr Health Service"
R2 -> "System Center Management"

Role-based authorization model for Hyper-V

azman.msc -> C:\ProgramData\Microsoft\Windows\Hyper-V\InitialStore.xml
- Allow Input to Virtual Machine
- Allow Output from Virtual Machine
- Bind External Ethernet Port
- Change Virtual Machine Authorization Scope
- Change VLAN Configuration on Port
- Connect Virtual Switch Port
- Create Internal Ethernet Port
- Create Virtual Machine
- Create Virtual Switch
- Create Virtual Switch Port
- Delete Internal Ethernet Port
- Delete Virtual Machine
- Delete Virtual Switch
- Delete Virtual Switch Port
- Disconnect Virtual Switch Port
- Modify Internal Ethernet Port
- Modify Switch Port Settings
- Modify Switch Settings
- Pause and Restart Virtual Machine
- Read Service Configuration
- Reconfigure Service
- Reconfigure Virtual Machine
- Start Virtual Machine
- Stop Virtual Machine
- Unbind External Ethernet Port
- View External Ethernet Ports
- View Internal Ethernet Ports
- View LAN Endpoints
- View Switch Ports
- View Switches
- View Virtual Machine Configuration
- View Virtual Switch Management Service
- View VLAN Settings

- Don't forget about file permission also....

- Using group from Authorization Manager itself is more secured -> pull the user from AD and grant access but... file permission....
- Using local group -> if someone got local admin access and add himself to appropriate group that's it


News it R2
- Allow Virtual Machine Snapshot