Installing Windows Server 2008 R2 on a Macbook Pro (using Bootcamp)

September 10, 2011

A couple of quick tips (or reminders for me) when installing Windows Server 2008 R2 on a Macbook Pro Bootcamp partition:

1. Follow the steps detailed in the Bootcamp Installation & Setup guide.
2. Have the Bootcamp Drivers for windows saved to a removable drive for immediate installation following the completion of the OS installation process.
3. If you forget to install the Bootcamp Drivers for windows on the initial login you will need a USB keyboard to log into windows.
4. If you need to connect to a wireless network ensure that you enable the windows feature “Wireless LAN Service”

Thanks it!

Advertisements

Enable remote desktop connectivity on Windows Server 2008 R2

August 31, 2011

A quick note to those who have hit the same block when trying to enable remote desktop connectivity in a Windows Server 2008 R2 environment.

Ensure that the following windows services are started:

  • DNS Client
  • Function Discovery Resource Publication
  • SSDP Discovery
  • UPnP

Ensure that the computer is configured to allow remote desktop connections (under System Properties -> “Remote” tab.)

Ensure that under “Advanced sharing settings”, “Turn on network discovery” on option is selected. This property widow can be opened by clicking on the windows start button and searching for “advanced”.

That’s it!


“Terminal Server Has Exceeded the Maximum Number of Allowed Connections”

November 13, 2010

Here are some handy one line commands to assist you when you encounter this situation.

Look up session id:

query session /server:<server name or ip>

Terminate a terminal service session:

reset session [session Id] /server:<server name or ip>

BizTalk Server 2010 RTM date announced

September 25, 2010

BizTalk Server 2010 has been released to manufacturing and will be available for purchase starting October 1st, 2010.

Read more about it here: http://blogs.msdn.com/b/biztalk_server_team_blog/archive/2010/09/22/biztalk-server-2010-released-for-manufacturing.aspx


BizTalk transformation operations: Inline C# is bad

April 28, 2010

When BizTalk Server performs XML transform operations on fairly large messages in a receive port, in a send port, or in XLANG, XSL transforms load the whole message in memory..

To resolve this issue, use one of the following methods:

  • Decrease the number of messages that BizTalk Server processes at the same time.
  • Reduce the size of the XML message that is being transformed.

The System.Policy.Security.Evidence object is often used in transforms and can consume much memory. Whenever a map contains a scripting functoid that uses inline C# (or any other inline language), the assembly is created in memory. The System.Policy.Security.Evidence object uses the object of the actual calling assembly. This situation creates a rooted object that is not deleted until the BizTalk service is restarted.

Most of the default BizTalk functoids are implemented as inline script. These items can cause System.Byte[] objects to collect in memory. To minimize memory consumption, we recommend that you put any map that uses these functoids into a small assembly. Then, reference that assembly. Use the following chart to determine which functoids use inline script and which functoids do not use inline script.

In the second column, “Yes” means that this functoid is implemented as inline script, and that it will cause System.Byte[] objects to collect in memory. “No” means that this functoid is not implemented as inline script, and that it will not cause System.Byte[] objects to collect in memory.Collapse this tableExpand this tableFunctoids Inline script?

Functoids Inline script?
All String Functoids Yes
All Mathematical Functoids Yes
All Logical Functoids except IsNil Yes
Logical IsNil Functoid No
All Date/Time Functoids Yes
All Conversion Functoids Yes
All Scientific Functoids Yes
All Cumulative Functoids Yes
All Database Functoids No
Advanced Functoids Inline script?
Looping Functoid No
Value Mapping Flattening Functoid No
Assert Functoid No
Table Extractor Functoid No
Table Looping Functoid No
Scripting Functoid with Inline C# Yes
Scripting Functoid with Inline JScript.NET Yes
Scripting Functoid with Inline Visual Basic .NET Yes
Scripting Functoid with Inline XSLT No
Scripting Functoid with Inline XSLT Call Template No
Scripting Functoid calling External Assembly No
Nil Value Functoid No
Value Mapping Functoid No
Mass Copy Functoid No
Iteration Functoid No
Index Functoid No
Record Count Functoid No

This is an excerpt from Microsoft KB article 918643. For further information follow this link.


Creating an XSLT data envelope using XML CDATA sections

February 10, 2010

Just noting this technique down for future reference.

Creating an envelope document using an XML CDATA section:

<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:msxsl="urn:schemas-microsoft-com:xslt" xmlns:var="http://schemas.microsoft.com/BizTalk/2003/var" exclude-result-prefixes="msxsl var userCSharp" version="1.0"  xmlns:ns0="http://tempuri.com/GenericEnvelope"  xmlns:userCSharp="http://schemas.microsoft.com/BizTalk/2003/userCSharp">
  <xsl:output omit-xml-declaration="yes" method="xml" version="1.0" />
  <xsl:template match="/">
    <ns0:Envelope>
      <xsl:attribute name="DocType">
      </xsl:attribute>
<xsl:element name="ns0:Payload">
		<xsl:text disable-output-escaping="yes">&lt;![CDATA[</xsl:text> 
			 <xsl:copy-of select="./@* | ./*"/> 
		<xsl:text disable-output-escaping="yes">]]&gt;</xsl:text> 
      </xsl:element>
    </ns0:Envelope>
  </xsl:template>
</xsl:stylesheet>

Extractng a message from an XML envelope CDATA section:

<?xml version="1.0" encoding="UTF-16"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:msxsl="urn:schemas-microsoft-com:xslt" xmlns:var="http://schemas.microsoft.com/BizTalk/2003/var" exclude-result-prefixes="msxsl var userCSharp" version="1.0" xmlns:ns0="http://tempuri.com/GenericEnvelope" xmlns:userCSharp="http://schemas.microsoft.com/BizTalk/2003/userCSharp">
  <xsl:output omit-xml-declaration="yes" method="xml" version="1.0" />
  <xsl:template match="/">
		<xsl:copy> 
			<xsl:value-of select="//*[local-name()='Payload']" disable-output-escaping="yes"/> 
	  </xsl:copy> 
  </xsl:template>
</xsl:stylesheet>

HOW DO I? Identify which running process to attach to

November 5, 2009

Great tip from Michael. Use the command line to query the Task List of running processes to find which BizTalk PID to attach to.

Simply type the following command into a DOS command window:


tasklist /svc /fi "imagename eq btsntsvc.exe"

This is a handy tip for BizTalk developers working in environments which use more than one host instance.