michaelcolson.com » windows server http://www.michaelcolson.com Sat, 06 Mar 2010 14:54:29 +0000 en hourly 1 http://wordpress.org/?v=3.2.1 Older Citrix Clients with Windows Server 2008 http://www.michaelcolson.com/2008/12/16/older-citrix-clients-with-windows-server-2008/ http://www.michaelcolson.com/2008/12/16/older-citrix-clients-with-windows-server-2008/#comments Tue, 16 Dec 2008 15:54:32 +0000 michael http://www.michaelcolson.com/?p=161 In order to get Citrix clients prior to version 11 to function with Citrix XenApp running on Windows Server 2008 you will need to install a hotfix from Microsoft. 

Basically this has to do with the encryption that is used for terminal services licensing having changed its key size from 512 bytes to . . . → Read More: Older Citrix Clients with Windows Server 2008]]> In order to get Citrix clients prior to version 11 to function with Citrix XenApp running on Windows Server 2008 you will need to install a hotfix from Microsoft. 

Basically this has to do with the encryption that is used for terminal services licensing having changed its key size from 512 bytes to 2048 bytes.

Here is the link to the Microsoft Knowledge Base article: http://support.microsoft.com/kb/949914.  Unfortunately this is one of those hotfixes that you have to request from Microsoft.  The good news is that they aren’t making you jump through a lot of hoops to get it.  Mine came right away in an email!

]]> http://www.michaelcolson.com/2008/12/16/older-citrix-clients-with-windows-server-2008/feed/ 0 Windows Server 2008 Server Core Activation http://www.michaelcolson.com/2008/09/12/windows-server-2008-server-core-activation/ http://www.michaelcolson.com/2008/09/12/windows-server-2008-server-core-activation/#comments Fri, 12 Sep 2008 15:13:47 +0000 michael http://www.michaelcolson.com/?p=121 Since there is no graphical interface to enter the product key or activate a copy of the Windows Server 2008 Server Core, there are two simple commands to get the job done.

Logon to the server core console Enter the product key:  cscript C:\windows\system32\slmgr.vbs -ipk PRODUCT-KEY-HERE Activate:  cscript C:\windows\system32\slmgr.vbs -ato ]]> Since there is no graphical interface to enter the product key or activate a copy of the Windows Server 2008 Server Core, there are two simple commands to get the job done.

  1. Logon to the server core console
  2. Enter the product key:  cscript C:\windows\system32\slmgr.vbs -ipk PRODUCT-KEY-HERE
  3. Activate:  cscript C:\windows\system32\slmgr.vbs -ato
]]> http://www.michaelcolson.com/2008/09/12/windows-server-2008-server-core-activation/feed/ 0 Top Ten Causes of Slow Replication with DFS-R http://www.michaelcolson.com/2007/12/19/top-ten-causes-of-slow-replication-with-dfs-r/ http://www.michaelcolson.com/2007/12/19/top-ten-causes-of-slow-replication-with-dfs-r/#comments Wed, 19 Dec 2007 12:37:55 +0000 michael http://www.michaelcolson.com/?p=214 In doing some DFS-R troubleshooting I came across the directory services team blog.  The DS team blog might seem like the place to go for Active Directory insights but they do have a good bit of information around DFS as well.

You can read the full article here, but I’ve listed the top . . . → Read More: Top Ten Causes of Slow Replication with DFS-R]]> In doing some DFS-R troubleshooting I came across the directory services team blog.  The DS team blog might seem like the place to go for Active Directory insights but they do have a good bit of information around DFS as well.

You can read the full article here, but I’ve listed the top ten causes of slow replication below:

  1. Missing Windows Server 2003 Network QFE Hotfixes or Service Pack 2
  2. Missing DFSR Service’s latest binary
  3. Out-of-date Network Card and Storage drivers
  4. DFSR Staging directory is too small for the amount of data being modified
  5. Bandwidth Throttling or Schedule windows are too aggressive
  6. Large amounts of sharing violations
  7. RDC has been disabled over a WAN link
  8. Incompatible Anti-Virus software or other file system filter drivers
  9. File Server Resource Manager (FSRM) configured with quotas/screens that block replication
  10. Un-staged or improperly pre-staged data leading to slow initial replication
]]> http://www.michaelcolson.com/2007/12/19/top-ten-causes-of-slow-replication-with-dfs-r/feed/ 0