<?xml version="1.0" encoding="UTF-8"?><rss version="0.92">
<channel>
	<title>INTERRUPT3h.com</title>
	<link>http://blog.interrupt3h.com</link>
	<description>bb's random musings</description>
	<lastBuildDate>Mon, 21 Jun 2010 09:11:43 +0000</lastBuildDate>
	<docs>http://backend.userland.com/rss092</docs>
	<language>en</language>
	<!-- generator="WordPress/3.0.1" -->

	<item>
		<title>Moving shares between SBS 2003 &amp; SBS 2008</title>
		<description><![CDATA[Still migrating the data over for my client, I ran into the usual problem of moving data from one drive to another preserving both NTFS ACLs and share details. The easiest way round this, that I have found, is as follows Issue the following commands from the command prompt on the destination server to copy [...]]]></description>
		<link>http://blog.interrupt3h.com/?p=225</link>
			</item>
	<item>
		<title>Moving lists between SharePoint sites</title>
		<description><![CDATA[Once I&#8217;d overcome the issues with user permissions outlined here I noticed that the companyweb was different to oldcompanyweb. A lot of the metadata was missing, including version history. Turns out that this is quite the problem just using stsadm from the command line. However, I found a great tool called SharePoint Content Deployment Wizard. [...]]]></description>
		<link>http://blog.interrupt3h.com/?p=223</link>
			</item>
	<item>
		<title>SBS 2003 -&gt; SBS 2008 Migration</title>
		<description><![CDATA[Long time no post! Thought I would update my blog with some hints and tips for some problems I hit in a recent client migration from SBS 2003 -> SBS 2008. Following the Microsoft tech document everything went smoothly until I needed to recreate the old companyweb. stsadm -o export -url http://OldCompanyWeb -filename cweb.bak -includeusersecurity [...]]]></description>
		<link>http://blog.interrupt3h.com/?p=220</link>
			</item>
	<item>
		<title>A large amount of memory is committed to applications and processes.</title>
		<description><![CDATA[This is a fairly common alert issued by SBS. The whole alert looks like A large amount of memory is committed to applications and processes. Consistently high memory usage can cause performance problems. To determine which processes and applications are using the most memory, use Task Manager. Monitor the activity of these resources over a [...]]]></description>
		<link>http://blog.interrupt3h.com/?p=204</link>
			</item>
	<item>
		<title>Have you tried re-installing it?</title>
		<description><![CDATA[You know what, I actually think I’ll get a reply from Ed – he is doing a good job of restoring my faith in support, if not Sage as yet. For that we’ll see how they deal with the actual support call when it goes in. Well, to say not well would be an understatement. [...]]]></description>
		<link>http://blog.interrupt3h.com/?p=200</link>
			</item>
	<item>
		<title>Sage &#8211; The End?</title>
		<description><![CDATA[And for the final chapter in the ongoing crusade between firstline Sage Corporate Support and poor little old me? Or alternatively, the final chapter in the ongoing crusade between corporate greed and the poor end user? Thanks, I&#8217;ve put the note on the account you&#8217;ve given. Thanks Ed &#8211; appreciate it. We&#8217;ll see if support [...]]]></description>
		<link>http://blog.interrupt3h.com/?p=177</link>
			</item>
	<item>
		<title>Sage Part III</title>
		<description><![CDATA[Fair play to Ed Tysoe, he follows up on the issues! I want to publically say thanks to him for sticking with the subject. Purchases of ACT! (and other Sage programs) include a 45-day warranty. During this period, you&#8217;re covered for support with everything &#8211; installation, setup, customisation, and more general &#8216;How do I use..?&#8217; [...]]]></description>
		<link>http://blog.interrupt3h.com/?p=169</link>
			</item>
	<item>
		<title>Sage replies!!</title>
		<description><![CDATA[Well they replied, and in the spirit of honesty, please find below their reply and my response to it. I am surprised that I actually got a response &#8211; so thumbs up for that. What I find slightly more concerning is the fact that they just want my details &#8216;so they can look into the [...]]]></description>
		<link>http://blog.interrupt3h.com/?p=158</link>
			</item>
	<item>
		<title>The downside of working for someone else</title>
		<description><![CDATA[Apparently there are &#8216;rules&#8217; about what we can send to our clients. Apparently these &#8216;rules&#8217; prohibit me sending this to my client &#8230; which I think is a crying shame I leave the decision with you Ben. I think we have tried very hard to make you happy with mycompanyname and the services we offer [...]]]></description>
		<link>http://blog.interrupt3h.com/?p=155</link>
			</item>
	<item>
		<title>Sage ACT! Support &#8211; Configuring TAPI</title>
		<description><![CDATA[We use Sage ACT! for some of our CRM duties. It&#8217;s adequate at best but we muddle through. Sage support is a real thing of beauty. Installing ACT! for a new user, and for some reason one of the TAPI interfaces is not showing in the dialer. So, enjoying the benefits of actually purchasing the [...]]]></description>
		<link>http://blog.interrupt3h.com/?p=145</link>
			</item>
</channel>
</rss>
