<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Confused Amused &#187; x64</title>
	<atom:link href="http://www.confusedamused.com/tags/x64/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.confusedamused.com</link>
	<description></description>
	<lastBuildDate>Tue, 27 Jul 2010 03:03:12 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>OCS2009-DBUpgrade.msi with a 32-bit SQL Server Back-End</title>
		<link>http://www.confusedamused.com/notebook/ocs2009-dbupgrademsi-with-a-32-bit-sql-server-back-end/</link>
		<comments>http://www.confusedamused.com/notebook/ocs2009-dbupgrademsi-with-a-32-bit-sql-server-back-end/#comments</comments>
		<pubDate>Wed, 11 Nov 2009 17:02:20 +0000</pubDate>
		<dc:creator>Tom Pacyk</dc:creator>
				<category><![CDATA[Office Communications Server 2007 R2]]></category>
		<category><![CDATA[2005]]></category>
		<category><![CDATA[2007]]></category>
		<category><![CDATA[OCS]]></category>
		<category><![CDATA[R2]]></category>
		<category><![CDATA[sql]]></category>
		<category><![CDATA[x64]]></category>
		<category><![CDATA[x86]]></category>

		<guid isPermaLink="false">http://www.confusedamused.com/notebook/ocs2009-dbupgrademsi-with-a-32-bit-sql-server-back-end/</guid>
		<description><![CDATA[I wanted to point out a quick note about KB 969834 aka the OCS2009-DBUpgrade.msi file &#8211; The KB article suggests running the package from your Back-End database server, but if you’re running SQL 2005 x86 you’ll be greeted with the following error:  This installation package is not supported by this processor type.  Basically, [...]]]></description>
			<content:encoded><![CDATA[<p><p>I wanted to point out a quick note about <a href="http://support.microsoft.com/kb/969834">KB 969834</a> aka the OCS2009-DBUpgrade.msi file &#8211; The KB article suggests running the package from your Back-End database server, but if you’re running SQL 2005 x86 you’ll be greeted with the following error:</p>  <blockquote>This installation package is not supported by this processor type.</blockquote>  <p>Basically, the MSI needs to be run from an x64 machine so your only option now is to run the update directly from your Front-End server. If you try to launch from there  you might receive this error:</p>  <blockquote>You must install Microsoft SQL Server 2005 Client Tools before you install Microsoft Office Communications Server 2007 R2 (KB969834).</blockquote>  <p>You could try install the SQL Tools and Service Pack updates from installation, but OCS is looking for very specific versions of the SQL tools. The quickest and easiest way is to just use a couple of downloads from the <a href="http://www.microsoft.com/downloads/details.aspx?FamilyID=50b97994-8453-4998-8226-fa42ec403d17&amp;DisplayLang=en">Feature Pack for Microsoft SQL Server 2005 &#8211; February 2007</a>.</p>  <p>You’ll want to download and install the following on your R2 Front-End before running the update:</p> <ul> <li>Microsoft SQL Server 2005 Backward Compatibility Components (x64 package)</li> <li>Microsoft SQL Server 2005 Management Objects Collection (x64 package) </li> </ul>  <p>After running those installers you should be able to run the DB upgrade successfully. Don’t forget – you need to run that MSI from a command line with the poolname (Non-FQDN version) parameter. And if you&#8217;re using Server 2008 be sure open the command prompt as Administrator so it runs with elevated rights. Example:</p>  <pre><code>OCS2009-DBUpgrade.msi POOLNAME=MyFirstPool</code></pre></p>
]]></content:encoded>
			<wfw:commentRss>http://www.confusedamused.com/notebook/ocs2009-dbupgrademsi-with-a-32-bit-sql-server-back-end/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Communicator QoS DSCP Marking on x64 Operating Systems</title>
		<link>http://www.confusedamused.com/notebook/communicator-qos-dscp-marking-on-x64-operating-systems/</link>
		<comments>http://www.confusedamused.com/notebook/communicator-qos-dscp-marking-on-x64-operating-systems/#comments</comments>
		<pubDate>Thu, 27 Aug 2009 20:07:33 +0000</pubDate>
		<dc:creator>Tom Pacyk</dc:creator>
				<category><![CDATA[Office Communications Server 2007]]></category>
		<category><![CDATA[Office Communications Server 2007 R2]]></category>
		<category><![CDATA[communicator]]></category>
		<category><![CDATA[dscp]]></category>
		<category><![CDATA[OCS]]></category>
		<category><![CDATA[qos]]></category>
		<category><![CDATA[x64]]></category>

		<guid isPermaLink="false">http://www.confusedamused.com/?p=491</guid>
		<description><![CDATA[I never did manage to figure this one out. The registry key HKLM\Software\Microsoft\RTC\Transport\QoSEnabled=1 never seemed to take effect on x64 versions of Vista or Windows 7. Wireshark packet traces would show no tags, but x86 clients worked just fine. Turns out the registry key you need to set for this to work is under the [...]]]></description>
			<content:encoded><![CDATA[<p>I never did manage to figure this one out. The registry key HKLM\Software\Microsoft\RTC\Transport\QoSEnabled=1 never seemed to take effect on x64 versions of Vista or Windows 7. Wireshark packet traces would show no tags, but x86 clients worked just fine. Turns out the registry key you need to set for this to work is under the WoW6432Node which makes a ton of sense after seeing it. The DWORD you need to set is this one:</p>

<p><blockquote>
HKLM\Software\WoW6432Node\Microsoft\RTC\Transport\QoSEnabled=1 
</blockquote>
<p>Thanks to <a href="http://blogs.pointbridge.com/Blogs/mcgillen_matt/Pages/Post.aspx?_ID=70#EntryTabs">Matt McGillen</a> for posting this originally.</p></p>
]]></content:encoded>
			<wfw:commentRss>http://www.confusedamused.com/notebook/communicator-qos-dscp-marking-on-x64-operating-systems/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Planning Tool for OCS 2007</title>
		<link>http://www.confusedamused.com/notebook/planning-tool-for-ocs-2007/</link>
		<comments>http://www.confusedamused.com/notebook/planning-tool-for-ocs-2007/#comments</comments>
		<pubDate>Thu, 06 Mar 2008 17:41:52 +0000</pubDate>
		<dc:creator>Tom Pacyk</dc:creator>
				<category><![CDATA[Collaboration]]></category>
		<category><![CDATA[OCS]]></category>
		<category><![CDATA[x64]]></category>

		<guid isPermaLink="false">http://www.confusedamused.com/notebook/planning-tool-for-ocs-2007/</guid>
		<description><![CDATA[On the Microsoft Download Center a new tool popped up today, the Planning Tool for Office Communications Server 2007. It crashes on my x64 Vista installation after a few screens so I&#8217;m starting up an XP VM to try it on. You can download it here: http://www.microsoft.com/downloads/thankyou.aspx?familyId=06793661-cd69-4490-bb4b-e97dd271209d&#38;displayLang=en#
]]></description>
			<content:encoded><![CDATA[<p>On the Microsoft Download Center a new tool popped up today, the Planning Tool for Office Communications Server 2007. It crashes on my x64 Vista installation after a few screens so I&#8217;m starting up an XP VM to try it on. You can download it here: <a title="http://www.microsoft.com/downloads/thankyou.aspx?familyId=06793661-cd69-4490-bb4b-e97dd271209d&amp;displayLang=en#" href="http://www.microsoft.com/downloads/thankyou.aspx?familyId=06793661-cd69-4490-bb4b-e97dd271209d&amp;displayLang=en#">http://www.microsoft.com/downloads/thankyou.aspx?familyId=06793661-cd69-4490-bb4b-e97dd271209d&amp;displayLang=en#</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.confusedamused.com/notebook/planning-tool-for-ocs-2007/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
