SCOM Windows agent failover

Hi experts,
I need some clarification on resource pool.
If i configure 500 agents on to one management server1 and keeping another management server2 for HA. If i create a resource pool and add both MS1 and MS2. Does all 500 agent failover to MS2 if MS1 fails. please clarify
Regards, Pratap

Hi
Windows agents do not use resource pools.
When you push deploy a windows agent from the console, you set its primary management server and it automatically knows of all the other management servers and can fail over to any of them. You can set, via powershell, which MS agents can \ cannot failover
to but not in the console for push agents.
Cheers
Graham
Regards Graham New System Center 2012 Blog! -
http://www.systemcentersolutions.co.uk
View OpsMgr tips and tricks at
http://systemcentersolutions.wordpress.com/

Similar Messages

  • Agent Failover and AD Integration in Operations Manager

    Hi
    I got some queries around SCOM agent failover and AD Integration:
    Does the discovery wizard differentiates between domain-joined and workgroup systems in terms of deploying agent on them?
    Why do we ever need Active Directory Integration with Operations Manager as described here
    http://technet.microsoft.com/en-us/library/hh212922.aspx
    - is it required for non-domain joined Windows systems or any other systems? All the other documents I read are saying that Windows agents can failover to other available MS in resource pool if their currently assigned MS fails and fails back automatically
    as soon as it comes back online.
    Is the automatic failover applicable to agents installed using client push (Discovery Wizard) Or it applies to agents installed manually using MOMAgent.msi?
    Also referred to this article
    http://blogs.technet.com/b/meamcs/archive/2013/05/10/is-ad-integration-or-manual-scom-agents-required-to-allow-automatic-windows-agent-failover-between-multiple-scom-management-servers.aspx
    but doesn’t seems to be having grip on it so far. Request some details on the above points.
    Thanks
    Taranjeet Singh
    zamn

    Hi,
    For the first question, I don't think we can use discovery wizard to install agent on non-domain joined computers. Please refer to the below links for how to deploy SCOM agent to non-domain computers:
    http://blogs.technet.com/b/quenguyen/archive/2011/07/13/monitoring-non-domain-servers-using-scom.aspx
    http://blogs.technet.com/b/stefan_stranger/archive/2012/04/17/monitoring-non-domain-members-with-om-2012.aspx
    For the second question, as we can read from the below link:
      http://blogs.technet.com/b/meamcs/archive/2013/05/10/is-ad-integration-or-manual-scom-agents-required-to-allow-automatic-windows-agent-failover-between-multiple-scom-management-servers.aspx
    SCOM windows agents automatic failover does not require AD integration or PowerShell scripting or Configuration Manager or manual agents installation specially for small to medium environment and agents distribution between different SCOM management servers
    can be accomplished through push agents wizard, and windows agents failover can be simply verified from event viewer.
    Regards,
    Yan Li
    Regards, Yan Li

  • Automatic windows agent fail over in SCOM 2012 / 2012 R2

    Hi All,
    I have a question with respect to SCOM 2012 / 2012 R2 windows agent fail over.
    For example i have only 400 windows agents and i have 2 MS in my environment. So 200 windows agents are managed by MS1 and the rest 200 are managed by the MS2.
    What i want to know is if either of the MS (MS1 or MS2) Shutdown / restart or any thing happens to them, Do the agents automatically fail over to the other MS ? As i have not configured ant thing for this as i don't know.
    So is there any configuration to be done for the above to happen after the deployment of both the management servers is done before discovering the agents or does it automatically understand take the rest 200 agents thinking that the other MS is down ?
    Gautam.75801

    Hi All,
    I have a question with respect to SCOM 2012 / 2012 R2 windows agent fail over.
    For example i have only 400 windows agents and i have 2 MS in my environment. So 200 windows agents are managed by MS1 and the rest 200 are managed by the MS2.
    What i want to know is if either of the MS (MS1 or MS2) Shutdown / restart or any thing happens to them, Do the agents automatically fail over to the other MS ? As i have not configured ant thing for this as i don't know.
    So is there any configuration to be done for the above to happen after the deployment of both the management servers is done before discovering the agents or does it automatically understand take the rest 200 agents thinking that the other MS is down ?
    Gautam.75801
    This happens automagically for Windows agents within a domain that are assigned to a Management Server.  For other scenarios, such as Gateways, the Gateways should be configured for failover between Management Servers, and the agents attached to those
    Gateways should be configured to failover between the Gateways.  Cross platform agents report to a resource pool, so that happens automagically as well.
    To confirm your scenario, simply run the Get-SCOMAgent cmdlet.
    To test you can do the following, assuming first agent in the array isn't a Management Server/Gateway :)
    $SCOMAgents = get-scomagent
    $SCOMAgents[0].PrimaryManagementServerName
    $SCOMAgents[0].GetFailoverManagementServers()
    Supporting article:
    http://blogs.technet.com/b/jimmyharper/archive/2010/07/23/powershell-commands-to-configure-gateway-server-agent-failover.aspx

  • SCOM Agent Failover Issue

    We have SCOM 2012 R2 with two Management server , around 200 agent reports to Ist Management server and 50 to management server 2. Once our management server 1 is down , agent reports to Management server 1 is not moved to MS2 , however agents still
    shows health in MAnagement server 1 itself ? Any idea why?

    Hi 74KMS,
    When an Agent is installed and configured to report to a Management Server, it is automatically configured to fail over to ANY other Management Servers. Failover behavior can be configured
    via PowerShell scripts or AD Integration.  NOTE: Windows agents do NOT report to a resource pool in OpsMgr 2012
    http://blogs.catapultsystems.com/cfuller/archive/2012/06/05/how-does-the-failover-process-work-in-opsmgr-2012-scom-sysctr.aspx
    Faizan

  • How to include SCOM R2 agent in server image (or vmware template)

    Can anybody tell me how to include the SCOM R2 agent in our Windows images/templates?   For the SCCM client, it is as simple as stopping the service on the reference machine, deleting the cert, and capturing.   I can find no good answer on the Internets on whether the SCOM agent has some sort of unique ID that doesn't like being "duplicated".
    Any help would be appreciated.  (I'd rather NOT include scripted tasks or steps that install the agent AFTER an image is deployed).  
    My RMS is configured to auto-accept agent registrations.

    Hi, I'm looking to do the same.  I created a template with the agent installed; however, I still left the server (W2012 R2) in 'workgroup'.  When loading and configuring the agent, I didn't get any error message since the raw server can communicate
    with the management server nor have I received a 'pending approval' on the mgmt server.
    I like the idea of having this pre-configured and ensuring SCOM properly detects and monitors new server additions since checklists are not followed. 
    Thanks.
    Stanley E. Noel Jr

  • Does the SCOM 2012 agent "look back" in the logs before the service was started?

    Does the SCOM 2012 agent "look back" in the logs before the service was started?<o:p></o:p>
    We raised this question to our Microsoft rep back when we migrated to SCOM 2007. We wanted to know if SCOM would alert on errors generated before the Heath Service started. For example, errors
    logged before the service is started on reboot (which is when some critical errors are logged). We also wondered what happens when the service is restarted...would errors during the same window be missed?
    If I remember correctly the MS response was that the agent looks back on startup/restart based on a timestamp of some kind. We did some testing that seemed to confirm this information. I've
    recently encountered several instances of errors generated while the service was stopped (primarily during boot up) where SCOM failed to alert on the error.
    Can anyone confirm how the SCOM 2012 agent deals with errors generated before the service starts on boot and during service restarts?

    I would suspect it's with watermarks as it has been in the past.  What you should look into is if these alerts you were expecting are event based, and if there are rules set to alert for these conditions.  If so, and you don't get an alert,
    then you can bring that up with your msft rep.  However, they should be caught.
    Regards, Blake Email: mengotto<at>hotmail.com Blog: http://discussitnow.wordpress.com/ If my response was helpful, please mark it as so, if it answered your question, then please also mark it accordingly. Thank you.
    There is a watermark. If the agent has been down for a significant period of time, the watermark may not apply, as the log would have rolled - but the entire log will still be processed regardless of what has already been discarded in the log. This may cause
    some problems if a monitor picks up an unhealthy state, and the healthy state log entry has already been flushed. In this case, you need to reset health on that particular monitor, or just flush the cache on the agent to start anew.
    Jonathan Almquist | SCOMskills, LLC (http://scomskills.com)

  • DELETE Windows Agents (agent monitored computers) via Powershell - HOW??

    It's really ridiculous that I have to ask this question, but as the shaft
    has clearly not given the countless scom customers of the world this information in an easy straightforward manner, I will ask the question.
    As bazillions of you have discovered through days of endless googling, there is NO easy way to simply delete windows agents (AGENT MANAGED COMPUTERS) from the scom console via powershell by using something as crazy and far out there as a ............cmdlet
    I could RING the necks of the shaft personnel who have not supplied the countless scom customers with this simple AND VERY NEEDED functionality - this is ground zero functionality, NOWHERE TO BE FOUND.  I did find old 2007 scripts, and scripts that
    just don't work, or poorly documented methods, etc.   
    So I wanted to ask if anyone out there has a straightforward, WORKING solution to do the following:
    completely DELETE windows agents (AGENT MANAGED COMPUTERS) from the scom console using
    powershell AND  a provided text list file of servers   (I.E.  C:\TEMP\serverlist.txt  )
    On behalf of the entire world, thanks in advance.

    There is no need to install anything, these commands will work on any server that has SCOM installed.
    This is a powershell script.
    If you need to use this to read from a text file  with one server per line (let's say C:\temp\agentlist.txt ), what you could do is copy this into a .ps1 file :
    function global:Delete-SCOMAgent([System.String[]] $agentNames)
    $administration = (get-scommanagementgroup).getadministration()
    $agentManagedComputerType = [Microsoft.EnterpriseManagement.Administration.AgentManagedComputer]
    $genericListType = [System.Collections.Generic.List``1]
    $genericList = $genericListType.MakeGenericType($agentManagedComputerType)
    $agentlist = new-object $genericList.FullName
    foreach ($agentName in $agentNames)
    $agent = Get-SCOMAgent -dnshostname $agentname*
    $agentlist.add($agent)
    $genericReadOnlyCollectionType = [System.Collections.ObjectModel.ReadOnlyCollection``1]
    $genericReadOnlyCollection = $genericReadOnlyCollectionType.MakeGenericType($agentManagedComputerType)
    $agentReadOnlyCollection = new-object $genericReadOnlyCollection.FullName @(,$agentList)
    $administration.DeleteAgentManagedComputers($agentReadOnlyCollection)
    $agentlist = Get-Content C:\temp\agentlist.txt foreach ($agent in $agentlist) {
    Delete-SCOMAgent $agent }
    and then run this from a powershell prompt with the command ./nameofthescript.ps1

  • Agent Failover Configuration

    Hello,
    I am trying to configure agent failover. I am using the script provided my Microsoft, see here:
    http://technet.microsoft.com/en-us/library/hh212733.aspx
    This is the script I am using:
    $primaryMS = Get-SCOMManagementServer –Name “Server1.domain.net”
    $failoverMS = Get-SCOMManagementServer –Name “Server2.domain.net”
    $agent = Get-SCOMAgent –Name “Agent.domain.net”
    Set-SCOMParentManagementServer –Agent $agent –PrimaryServer $primaryMS
    Set-SCOMParentManagementServer –Agent $agent –FailoverServer $failoverMS
    I execute the PS1 script, and no errors return, great. However, I go back to my agent, and the Operations Agent is still only listing Server1 as its Reporting Server.
    Is there any way to verify what I just execute, actually worked, other than turning off Server1 to test true failover?
    I am assuming my script works, if it looks wrong, please let me know.
    I am running SCOM 2012 SP1.
    Thanks everyone.

    Glad to see you resovled the issue and thanks for sharing the resolution.
    Niki Han
    TechNet Community Support

  • How to Perform Forced Manual Failover of Availability Group (SQL Server) and WSFC (Windows Server Failover Cluster)

    I have a scenario with the three nodes with server 2012 standard, each running an instance of SQL Server 2012 enterprise, participate in a
    single Windows Server Failover Cluster (WSFC) that spans two data centers.
    If the nodes in the primary data center are unavailable due to data center outage. Then how I can able to access node in the WSFC (Windows Server Failover Cluster) in the secondary disaster recovery data center automatically with some script.
    I want to write script that can be able to check primary data center by pinging some IP after every 5 or 10 minutes.
    If that IP is unable to respond then script can be able to Perform Forced Manual Failover of Availability Group (SQL Server) and WSFC (Windows Server Failover Cluster)
    Can you please guide me for script writing for automatic failover in case of primary datacenter outage?

    please post you question on failover clusters in the cluster forum.  THey will explain how this works and point you at scipts.
    You should also look in the Gallery for cluster management scripts.
    ¯\_(ツ)_/¯

  • How to Perform Forced Manual Failover of Availability Group (SQL Server) and WSFC (Windows Server Failover Cluster) with scrpiting

    I have a scenario with the three nodes with server 2012 standard, each running an instance of SQL Server 2012 enterprise, participate in a
    single Windows Server Failover Cluster (WSFC) that spans two data centers.
    If the nodes in the primary data center are unavailable due to data center outage. Then how I can able to access node in the WSFC (Windows Server Failover Cluster) in the secondary disaster recovery data center automatically with some script.
    I want to write script that can be able to check primary data center by pinging some IP after every 5 or 10 minutes.
    If that IP is unable to respond then script can be able to Perform Forced Manual Failover of Availability Group (SQL Server) and WSFC (Windows Server Failover Cluster)
    Can you please guide me for script writing for automatic failover in case of primary datacenter outage?

    You are trying to implement manually what should be happening automatically in the cluster. If the primary SQL Server becomes unavailable in the data center, it should fail over to the secondary SQL Server automatically.  Is that not working?
    You also might want to run this configuration by some SQL experts.  I am not a SQL expert, but if you have both hosts in the data center in a cluster, there is no need for replication between those two nodes as they would be accessing
    the database from some form of shared storage.  Then it looks like you are trying to implement Always On to the DR site.  I'm not sure you can mix both types of failover in a single configuration.
    FYI, it would make more sense to establish a file share witness in your DR site instead of placing a third node in the data center for Node Majority quorum.
    . : | : . : | : . tim

  • Is there a SCOM install agent for SLES on PPC64?

    Is there a SCOM install agent for SLES on PPC64?
    Trying to install an agent for SCOM on Suse VM units that are hosted on IBM's power 7 hardware.
    While i do see .ppc AIX agent installers I do not see one for SLES on ppc64.
    Has anyone installed SCOM on SLES ppc64 or know of a viable agent for the install?

    To elaborate a bit, Microsoft definitely does not offer an agent for SLES on PowerPC.  Linux has been ported to a lot of different processor chip architectures, which is great.  But Intel x86/x64 is by far the most popular, and it's the only
    chip architecture for which Microsoft supplies an agent for monitoring Linux.  As you noted, there is an agent for AIX on PowerPC, but AIX is a very different operating system from Linux, and the agent for AIX on PPC will not work on Linux on PowerPC.
    I don't see Microsoft doing an agent for Linux on PowerPC.  We would need to see a significant business opportunity for that to change.
    I would note that the source code for the OpsMgr agent for Linux/UNIX is available at
    http://scx.codeplex.com, along with instructions on how to compile and build the agent.  Someone with developer skills in C++, compilers, makefiles, etc. could definitely build an agent for SLES on PowerPC.  For
    example, I'm aware of someone who has built an agent for Linux running on the IBM S/390 (z-Series) chip architecture running as a guest under zOS and has it working with SC 2012 OpsMgr.   But you would be on your own,
    perhaps with help from the community, to make that happen.
    Michael Kelley, Lead Program Manager, Open Source Technology Center

  • Windows 2012 Failover Cluster - File server role (vCO)

    Hi, 
    I wonder if anybody can shed some light on a query i have.
    A windows 2012 failover cluster will be built in AD domain example.uk.  Cluster File server roles will be created and will reside in this domain also.
    We also have a requirement to run a cluster file server role in the child domain off secure.example.uk.  Is this possible? or do the file server roles and related vCO's have to reside in the same domain as the cluster (CNO).
    I know the CNO can be used to create the VCO but could a prestage a VCO in the child domain of secure.example.uk.
    Mark

    Hi Mark,
    By default CNO will create 
    VCO automatically in default domain computer OU, we generally use the
    KISS principle to place the CNO and VCO to the same OU, and as far as I know there no known design document indicate the VCO can be placed in different domain, therefore I suggest you place the CNO and V CO at same OU.
    More information:
    When Creating a New Resource or Role in Windows Server 2012 R2 Failover Cluster, the Network Name Fails to Come Online or Failed to Create Associated Computer Object in Domain
    http://blogs.technet.com/b/askpfeplat/archive/2014/11/17/when-creating-a-new-resource-or-role-in-windows-server-2012-r2-failover-cluster-the-network-name-fails-to-come-online-or-failed-to-create-associated-computer-object-in-domain.aspx
    CNO Blog Series: Increasing Awareness around the Cluster Name Object (CNO)
    http://blogs.technet.com/b/askcore/archive/2012/09/25/cno-blog-series-increasing-awareness-around-the-cluster-name-object-cno.aspx
    How to Create a Cluster in a Restrictive Active Directory Environment
    http://blogs.msdn.com/b/clustering/archive/2012/03/30/10289577.aspx
    Prestage Cluster Computer Objects in Active Directory Domain Services
    https://technet.microsoft.com/en-us/library/dn466519.aspx
    I’m glad to be of help to you!
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • FTP in Windows 2012 Failover Cluster

    Hi,
    Understand that Windows 2012 is having much improved Failover Clustering features,however i have faced issues when i configured FTP in Windows 2012 Failover Cluster.
    1) As per the process configured the shared disk for FTP data path.
    2)Installaed FTP feature in both Nodes of Clustert
    3)Finally created the Generic Service in Cluster Roles for FTP Service.
    After the configuration i found everything working fine but when i try to failover the FTP role found that FTP resource is not moving smoothly. Also i observed that Microsoft FTP service gets in to "starting" mode in the destination Node. To run the FTP
    resource Microsft FTP service should be in Started mode.
    This happens only when we try to failover else it works fine if you start freshly.
    Have any one tried this? Any clue about such issue ?
    Regards:Mahesh

    Hi,
    In earlier versions of Internet Information Services, Microsoft provided generic resource monitor components to support high availability Web server instances by using the Microsoft Clustering infrastructure. However, custom code was needed to fully realize
    the potential of this solution. Also, the generic scripts that Microsoft provided did not satisfy customer needs.
    From IIS 7 to configure IIS in a clustered environment by using Windows Server failover clustering, you have to use a custom (scripting) code to enable such a high availability scenario.
    Note:
    We recommend that administrators carefully evaluate the use of Network Load Balancing (NLB) instead of using failover clustering as the primary and preferred method for improving the scalability and availability of Web applications that have multiple servers
    that are running new IIS (from IIS 7) . One benefit of NLB is that all servers can actively participate in the concurrent handling of incoming HTTP requests. Another benefit is that in an NLB IIS environment, it can be much easier to support rolling updates
    and rollbacks while still providing high availability of Web applications.
    To configure high availability for IIS FTP servers using Failover Clustering:
    Install the Web Server role on all cluster nodes.
    Install the Failover Clustering feature on all cluster nodes and create the cluster.
    Set up a file share that will be used for IIS shared configuration
    Configure the IIS shared configuration on all cluster nodes
    Configure Offline Files for IIS Shared Configuration on all cluster nodes
    Configure the FTP site and specify the location of its content on one cluster node
    Configure high availability for your FTP site by creating a generic script in Failover Cluster Manager
    For more detailed configuration procedure please refer to following MS articles:
    Note: I didn’t find IIS 8 in Windows Server 2012 failover cluster configuration guide, below guide was published for II 7 in Windows server 2008 and Windows Server 2008 R2, but its basis configuration procedures should also apply to Windows Server 2012.
    How to configure FTP 7.5 for IIS 7.0 in a Windows Server 2008 failover cluster
    http://support.microsoft.com/kb/974603
    Configure IIS Network Load Balancing
    http://www.iis.net/learn/web-hosting/configuring-servers-in-the-windows-web-platform/network-load-balancing
    Deploying IIS on a Failover Cluster
    http://blogs.msdn.com/b/clustering/archive/2009/06/01/9674799.aspx
    Hope this helps!
    TechNet Subscriber Support
    If you are
    TechNet Subscription user and have any feedback on our support quality, please send your feedback
    here.
    Lawrence
    TechNet Community Support

  • The lease timeout between avaiability group and the Windows Server Failover Cluster has expired

    Hi,
    I am having some issues where I get a lease timeout from time to time.  I have a Windows 2012 Failover Cluster with 2 nodes and 2 SQL 2012 Always-on Availability Groups.  Both nodes
    are a physical machines and each node is the primary for an AG. 
    From what I understand if
    the HealhCheckTimeout
    is exceeded without the signal exchange the lease is declared 'expired' and the SQL Server resource dll reports that the SQL Server availability group no longer 'looks alive' to the Windows cluster manager.  Here are the properties I have setup
    which are the default settings:
    LeaseTimeout - 20000
    HealthCheckTimeout - 30000
    VerboseLoging - 0>
    FailureConditionLevel – 3
    Here are the events that occur in the Application Event Viewer:
    Event ID 19407:
    The lease between availability group 'AG_NAME' and the Windows Server Failover Cluster has expired. A connectivity issue occurred between the instance of SQL Server and the Windows Server Failover
    Cluster. To determine whether the availability group is failing over correctly, check the corresponding availability group resource in the Windows Server Failover Cluster.
    Event ID 35285:
    The recovery LSN (120881:37533:1) was identified for the database with ID 32. This is an informational message only. No user action is required.
    SQl server logs are too long to post in this box but I can send them if you request.
    The AG is setup to failover automatically but it did not failover.  I am trying to figure out why the lease timed out.  Thanks.

    From what I've been able to find out, this is due to an issue with the procedure sp_server_diagnostics.  It sounds like the cluster is expecting this procedure to regularly log good status "Clean" in the log files, but the procedure is designed not
    to flood the logs with "Clean" messages, so only reports changes, and does not make an entry when the last status was "Clean" and the current status is "Clean".  The result is that the cluster looks to be unresponsive.  However, once it initiates
    the failover, the primary machine responds, since it was never really down, and the failover operation stops.   
    The end result is that there really never is a failover, but the database becomes unavailable for  a few minutes while this is resolved.
    I'm going to try setting the cluster's failure condition level to 2 (instead of 3) and see if that prevents the down time.
    blogs.msdn.com/b/sql_pfe_blog/archive/2013/04/08/sql-2012-alwayson-availability-groups-automatic-failover-doesn-t-occur-or-does-it-a-look-at-the-logs.aspx

  • SCOM 2012 Agent - Best Practices with Base Images

    I've read through the
    SCOM 2012 agent installation methods technet article, as well as how to
    install the SCOM 2012 agent via command line, but don't see any best practices in regards to how to include the SCOM 2012 agent in a base workstation image. My understanding is that the SCOM agent's unique identifier is created at the time of client installation,
    is this correct? I need to ensure that this is a supported configuration before I can recommend it. 
    If it is supported, and it does work the way I think it does, I'm trying to find out a way to strip out the unique information so that a new client GUID will be created after the machine is sysprepped, similar to how the SCCM client should be stripped of
    unique data when preparing a base image. 
    Has anyone successfully included a SCOM 2012 (or 2007 for that matter) agent in their base image?
    Thanks, 
    Joe

    Hi
    It is fine to build the agent into a base image but you then need to have a way to assign the agent to a management group. SCOM does this via AD Integration:
    http://technet.microsoft.com/en-us/library/cc950514.aspx
    http://blogs.msdn.com/b/steverac/archive/2008/03/20/opsmgr-ad-integration-how-it-works.aspx
    http://blogs.technet.com/b/jonathanalmquist/archive/2010/06/14/ad-integration-considerations.aspx
    http://thoughtsonopsmgr.blogspot.co.uk/2010/07/active-directory-ad-integration-when-to.html
    http://technet.microsoft.com/en-us/library/hh212922.aspx
    http://blogs.technet.com/b/momteam/archive/2008/01/02/understanding-how-active-directory-integration-feature-works-in-opsmgr-2007.aspx
    You have to be careful in environments with multiple forests if no trust exists.
    http://blogs.technet.com/b/smsandmom/archive/2008/05/21/opsmgr-2007-how-to-enable-ad-integration-for-an-untrusted-domain.aspx
    http://rburri.wordpress.com/2008/12/03/untrusted-ad-integration-suppress-misleading-runas-alerts/
    You might also want to consider group policy or SCCM as methods for installing agents.
    Cheers
    Graham
    Regards Graham New System Center 2012 Blog! -
    http://www.systemcentersolutions.co.uk
    View OpsMgr tips and tricks at
    http://systemcentersolutions.wordpress.com/

Maybe you are looking for