As we can download SCOM 2012 RC from Microsoft, I decided to do quick installation in LAB environment. Whole test environment is based on VMware Workstation 8. Deployment of SCOM 2012 will be spread across few servers to separate certain functions (in fact similar to real-life deployments). For SCOM2012 deplyoment I will use following servers:

• lab-dc-01 – Domain Controller – Windows Server 2008 R2
• lab-sql-01 – SQL Server – Windows Server 2008 R2 + SQL Server 2008 R2
• lab-net-01 – SCOM 2012 Management Server – Windows Server 2008 R2 + SCOM 2012 Management Server
• lab-wks-01 – SCOM 2012 Management Console – Windows 7 x64 Ultimate + SCOM 2012 Management Console

This will be mainly screenshot tour through installation phases of SCOM2012.

Here is schematics of the lab:

(more…)

Background image on logon screen os common issue with pre-installed servers, for example from Dell. That makes accessing those systems via Remote Desktop painful and slow (it happenes that serer is shipped to location, racked and stacked, and then whole configuration take place remotely). By default background bitmap from logon screen is sitting in C:\Windows\System32\oobe\info\backgrounds, so you can put your own logon screen background or if you don’t want to have any (just system default) you can follow instructions below and remove background from logon screen.

(more…)

By default when I installed mysql on openSUSE, root password for mysql access was blank. First thing then is to change password as this might pose security issue. First of all login to openSUSE using root account and then:

(more…)

VMware Workstation and GNS3 are two platforms which are very handy to test and evaluate solutions before live implementation. By default each of those platforms is separate, however both have components which allow integration. What that means is that it is possible to have virtual machines hosted on VMware Workstation to communicate with Cisco equipment which is running oin GNS3.

By default VMware Workstation has 10 virtual networks which are named VMnet0, VMnet1, … , VMnet9. Each of those networks can be used as:

• Bridged – virtual network connected seamless way to physical adapter. Virtual machines connected to bridged network will appear in same network as physical adapter connected to computer.
• NAT – VMware will translate virtual network and computers connected to that network and allow communication acting as gateway
• Host-only – network available only for virtual machines connected to it. private network for virtual machines.

Configuration of virtual networks is flexible and can be adjusted easily. Each of virtual networks can be also presented on host computer as network adapter.

In GNS3 environment we have Cloud Node Type which can be configured to communicate with any network adapter installed on the computer on which GNS3 is running

(more…)

Often using VMware Workstation platform we need to quickly create new virtual machine. reasons for that might be different. For example additional machine for our Lab environment or just quick test without affecting other machines we have setup in our virtual environment.

Installing whole operating system with all applications we used to have in our setup might be time consuming process. That is why it is worth to consider creating and using templates to be able quickly generate virtual machines we need.

(more…)