Not monitored state on Operations Manager Agents or Management servers

It is very common to see  agents or management servers in a not monitored state.

Following is a great post by SCOM Engineering Blog which shows out a bunch of reasons for this to happen.

http://blogs.technet.com/b/momteam/archive/2008/03/10/getting-headaches-trying-to-figure-out-why-you-are-seeing-the-not-monitored-state-for-management-servers-or-agents.aspx

Journal Wrap

This is a very informative article about journal wrap which I came across.

Gives out very detailed description on;

• How journal wrap occurs
• How to recover and best recovery methods
• How to avoid

and calculating the number of changes that a given USN journal file can hold and so on.

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

Here goes a detailed description of FRS entries in the Registry

and lastly, Here is another good article describing all about recovering from Journal wrap and burflags!!

Performing Active Directory Health Checks.

AD health Checks..a complex and an inevitable job as a systems engineer and a one shich invloves very careful documentation.(ah! documentation! I Love it! )

I usually have MSP reports and DCDIAG carrying out the task for me but using the tools just is not enough. You should know what to look at and where to look at and prepare your reports effectively.
When large deployments are involved, completing a health check is a time consuming task and leaves  I-need-instant-results folks frustrated.

in the following links you may find some procedures explained and usually comes in handy when it comes to health checks on AD.

http://searchmidmarketsecurity.techtarget.com/tip/How-to-perform-an-Active-Directory-health-check

http://redmondmag.com/Articles/2012/07/01/5-Free-Microsoft-Tools-for-Top-Active-Directory-Health.aspx?Page=1

Configuring Virtual Networks

Here comes another article which is really descriptive..

 

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

Network Configurations for Live Migration

The following technet article will come in handy when you deploy Hyper V clusters which involve Live migrations.

http://technet.microsoft.com/en-us/library/ff428137%28WS.10%29.aspx

Unable to delete agentless systems

I came across this article when i was having a hard time removing my orphaned cluster  from agentless monitoring..
http://opsmgrunleashed.wordpress.com/2007/06/04/unable-to-delete-agentless-systems/

Powershell remoting

Along with Windows server 2008 came powershell, a powerful scripting and an automation platform. With later versions of windows server, powershell came up with improved functionality and gaining raw power and its here to stay. Accept it or prepare to fall back in techie world! :)
In this post I will be sharing my experiences with power shell remote capabilities.okay lets move on.

Powershell remoting allows to run individual commands or to access full powershell sessions on remote systems similar to SSH. Powershell remoting is disabled by default (well…obviously! :P) and needs to be enabled. this is easy on domain joined computers but a bit more complex on workgroups but hey! this aint rocket science!

Enabling Powershell remoting
Fire up an elevated powershell session. (Right Click and run as admin). and run the following cmdlet.

enable-psremoting –force

This will result in enabling WinRm service, setting it to start automatically with the system and creates a firewall rule for incoming connections. –force switch will enable these settings without prompting the user for each step. If the PCs are domain joined, this is all you have to do and you are good to go for remote powershelling.



Workgroup Settings

If the computers you need to do powershell remoting is in a work group, you need a few extra steps as given below.
First, run the  enable-psremoting -force command on an elevated powershell on the computer you want to initiate connections from. So that both ends are now remote enabled!

Configure trustedhost settings on both computers so that they trust each other. The following command, for an example, trusts any computer and is suitable for a setup like a home network. you may replace the “*” with a comma separated list of computer names or IP addresses to restrict access.

Set-Item wsman:\localhost\client\trustedhosts *
on both computers.

Restart the WinRm service for the settings to take effect.

Restart-Service WinRm



Testing Connections
Run the following command on the computer your are connecting from to check what you did was successful. Replace COMPUTER with the name of the remote computer. The command will test if the winrm services is running successfully on the remote computer.

test-wsman COMPUTER

The successful completion of this command ensures WinRm is enabled and computers can connect.



Thats it!! lets run a few commands or start a remote powershell session!!

Run an individual command using invoke-command

invoke-command –computername COMPUTER –scriptblock {COMMAND} –credential USERNAME

Replace COMPUTER with the remote computer name or ip address, COMMAND with the command you want to run and USERNAME with the user name of the remote computer. The following screen cap shows get-host output on a remote computer.



Enabling a powershell session allows you to run multiple commands instead of a single command. You can initiate a remote powershell session using the following command.

enter-pssession –computername COMPUTER –credential USER



Replace COMPUTER and USER with the hostname of the remote computer and the username which you hope to log on with. type exit anytime you wish to log out of the remote session.