<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Msc on BAFM</title><link>https://christian.blog.pakiheim.de/tags/msc/</link><description>Recent content in Msc on BAFM</description><generator>Hugo -- 0.160.1</generator><language>en</language><lastBuildDate>Mon, 16 Feb 2009 15:19:57 +0000</lastBuildDate><atom:link href="https://christian.blog.pakiheim.de/tags/msc/index.xml" rel="self" type="application/rss+xml"/><item><title>Tivoli Storage Manager Client and Microsoft Cluster Services (continued)</title><link>https://christian.blog.pakiheim.de/posts/2009-02-16_tivoli-storage-manager-client-and-microsoft-cluster-services-continued/</link><pubDate>Mon, 16 Feb 2009 15:19:57 +0000</pubDate><guid isPermaLink="false">http://blog.barfoo.org/?p=1859</guid><description>&lt;p&gt;As you might recall &lt;a href="https://christian.blog.pakiheim.de/posts/2009-02-16_tivoli-storage-manager-client-and-microsoft-cluster-services-continued" title="Tivoli Storage Manager Client and Microsoft Cluster Services"&gt;from my first article about this topic&lt;/a&gt;, I had some troubles with the Microsoft Cluster Services and the registration replication. Now, today as we tried switching the TSM-Server for some resources, we ran into this again.&lt;/p&gt;
&lt;p&gt;We were using the service install tool (dsmcutil install scheduler) to set the new password as well as the GUI. Now, as we brought the resource online with the local service manager, everything was honky dory. But as soon as we brought it online using the Cluster Manager, it failed horribly. Why ?&lt;/p&gt;</description></item></channel></rss>