Monday, June 30, 2008

Evaluación de vulnerabilidades de Seguridad de Windows

Jeff Jones (http://blogs.technet.com/security/archive/2008/05/15/q1-2008-client-os-vulnerability-scorecard.aspx) escribió un paper sobre las vulnerabilidades de los sistemas operativos, este paper se basa en las estadísiticas y estudios del National Vulnerability Database Version 2.1 de instituto de seguridad NIST de Estados Unidos, los resultados se muestran en el siguiente gráfico.

 

image

En general Windows XP y Windows Vista presentaron menos problemas de seguridad, por ejemplo Windows XP tuvo menos vulnerabilidades que Red Hat WS. El reporte completo puede ser bajado de este link Download the attached paper También puede revisar la base de datos original en la siguiente dirección http://nvd.nist.gov/

 

Saludos,

 

Eduardo Castro

Comunidad Windows Costa Rica - http://mswindowscr.org

Saturday, June 28, 2008

Se lanza el Microsoft Forefront Integration Toolkit para Network Access Protecction

Este acelerador está disponible en http://technet.microsoft.com/en-us/library/cc512112.aspx y permite integrar las características NAP incluídas en Windows 2008 con las caracterísitcas de Antispyware y Antivirus de ForeFront.

 

Slds

 

Eduardo Castro

Comunidad Windows Costa Rica - http://mswindowscr.org

Monday, June 23, 2008

Content Deployment SharePoint

Aquí encontrarán un excelente artículo sobre content deployment con SharePoint (MOSS 2007) http://masteringsharepoint.com/blogs/beagle/archive/2008/06/12/moss-2007-content-deployment-4-of-4.aspx

 

Saludos,

Eduardo Castro

Comunidad Windows Costa Rica - http://mswindowscr.org

Content Deployment SharePoint

Aquí encontrarán un excelente artículo sobre content deployment con SharePoint (MOSS 2007)

 

Saludos,

Eduardo Castro

Comunidad Windows Costa Rica - http://mswindowscr.org

Thursday, June 19, 2008

Cómo instalar el Telnet Client en Windows 2008 y Vista

Por default el cliente de telnet no se instala en Windows 2008 ni en Windows Vista, esto lo hace Microsoft para reducir la superficie de ataque, si desea instalar este cliente se tienen que seguir los siguientes pasos:

Para instalarlo por línea de comando, se hace lo siguiente:

1. Open a command prompt window. Click Start, type cmd in the Start Search box, and then press ENTER.

2. Type the following command:

pkgmgr /iu:"TelnetClient"


También se puede realizar agregando el Feature por el GUI.



 



Saludos,



Eduardo Castro M.



Comunidad Windows Costa Rica http://mswindowscr.org



 



Technorati Tags: ,

Wednesday, June 18, 2008

Limpiar el Cache en Reporting Services

Encontré esta información sobre cómo limpiar el caché en SQL Server Reporting Services.

You can find information about scripting here:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsuiref/htm/cpu_rs_v1_5fxe.asp

You should also look at this:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsprog/htm/rsp_prog_soapapi_script_3249.asp

The flush cache method is here:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsprog/htm/rsp_ref_soapapi_service_ak_22i9.asp

You script will look something like this (not sure this is 100% correct)

Public Sub Main()
    Dim items() As CatalogItem
    items = rs.ListChildren("/", True)

    Dim type as ItemTypeEnum
    Dim item As CatalogItem
    For Each item In items
type = rs.GetItemType(item)
if (type == ItemTypeEnum.Report || type == ItemTypeEnum.LinkedReport)
         rs.FlushCache(item)
    Next item
End Sub

I think I mixed in C# and VB.Net, but hopefully you can get the idea.

 

Saludos,

Eduardo Castro

Comunidad Windows Costa Rica http://mswindowscr.org

Saturday, June 14, 2008

Visión de Data Warehousing de Microsoft

 

SQL Server 2008 Data Warehousing Vision VideoEn este video Ram Ramanatan nos muestra la visión de Microsoft con respecto a SQL Server 2008 Data Warehousing

Watch the video

 

 

Saludos,

Eduardo Castro Martinez

http://mswindowscr.org - Comunidad Windows

Visión de Data Warehousing de Microsoft

 

SQL Server 2008 Data Warehousing Vision VideoEn este video Ram Ramanatan nos muestra la visión de Microsoft con respecto a SQL Server 2008 Data Warehousing

Watch the video

 

 

Saludos,

Eduardo Castro Martinez

http://mswindowscr.org - Comunidad Windows

Microsoft BI en Gartner

Las soluciones de Inteligencia de Negocios de Microsoft está muy bien posicionadas en el Cuadrante Mágico de Gartner.

image

 

Si desean ver el artículo completo lo pueden consultar en http://mediaproducts.gartner.com/reprints/microsoft/vol7/article3/article3.html

 

Saludos,

Eduardo Castro

Comunidad Windows Costa Rica

http://mswindowscr.org

Microsoft Security Development Lifecycle

El Microsoft Security Development Lifecycle es un proceso de aseguramiento de calidad que consiste en los siguientes pasos:

“Microsoft’s Trustworthy Computing initiative is perhaps the most advanced and comprehensive application security program in the industry.”
“Managing Application Security From Beginning To End,” Forrester Research, Inc., August 2007

 

 

 

 

 

 

 

 

Para obtener más información accesa The Microsoft Security Development Lifecycle (SDL): Process Guidance.

Saludos,

Eduardo Castro

Comunidad Windows Costa Rica

http://mswindowscr.org

 

Technorati Tags: ,

Windows Server 2008 Security Guide

La guía de seguridad de Windows Server 2008 ayuda a que las organizaciones crean, mantenga y desplieguen un ambiente de trabajo seguro para servidores Windows 2008. Este Solution Accelerator es gratis y se puede bajar de http://www.microsoft.com/downloads/details.aspx?FamilyID=fb8b981f-227c-4af6-a44b-b115696a80ac&displaylang=en

Esta guía incluye lo siguiente:

 

  • Resumen Ejecutivo. Explica cómo utilizar esta guía.
  • Security Guide. Guías recomendadas para hacer hardening de servidores de distintos roles tales como Active Directory Domain Services (AD DS), DHCP, DNS, Web, File, Print, Active Directory Certificate Services (AD CS), Network Policy and Access Services, y Terminal Services.
  • Recomendaciones de seguridad. Referencia que explica detalladamente los Security Setting Recomendados.
  • Security Settings Workbook..
  • Attack Surface Reference Workbook. Cambios introducidos en los roles de Windows Server 2008.
  • GPOAccelerator. Permite la creación automática de Group Policy objects (GPOs) que son recomendados por esta guía y se baja de aquí click here.

 

Saludos,

Eduardo Castro

Comunidad Windows Costa Rica

http://mswindowscr.org

 

Technorati Tags: ,

Wednesday, June 11, 2008

Lista de dispositivos compatibles con Ready Boost de Windows Vista

Grant Wibson recolectó una lista de los dispositivos compatibles con Ready Boost, esta lista puede ser consultada en http://www.grantgibson.co.uk/misc/readyboost/

Technorati Tags:

Comunidad Windows Costa Rica - http://mswindowscr.org

Desarrollo de para aplicaciones para MOSS

Chris Johnson, ha creado un excelente post sobre las distintas formas de incluir aplicaciones desarrolladas en ASP.NET dentro de MOSS, pueden leerlo en la siguiente dirección http://blogs.msdn.com/cjohnson/archive/2006/09/05/740498.aspx

 

Technorati Tags: ,

 

I have been fortunate enough to have been involved deeply with one of our early Office TAP customer's projects. TAP customers are given access to early builds and betas, along with support from Microsoft, to build a project on. The idea here is that they will be in a position to deploy early on the latest technology and at the same time have a positive impact on Microsoft delivering a quality product to market. TAP customers are key to us taking feedback as we build the product.

In the particular project I am involved with we are building quite an elaborate solution that is built using many of the new features in the 2007 Microsoft Office System. This ranges from the InfoPath embedded in a Win Forms control and on to Microsoft Office SharePoint Server 2007.

Here is a brief list of some of the things we are doing:

  • Building a .Net Win Forms application and embedding InfoPath to do rich offline forms capture in a custom application
  • Custom Visual Studio based Workflows build on Windows Workflow foundation
  • Custom Site Definitions, List Definitions, Timer Jobs deployed as Features via the Solution deployment framework
  • ...

But what I really wanted to concentrate on in this post was talking about what options we considered for building some custom UI that is delivered inside MOSS and the pros and cons of each.

The options we looked at were:

  • Custom built Web Parts
  • A "_layouts" application (see below for what this is)
  • App built using User Controls & Son of SmartPart

The particular component of the application that I want to look at is the UI presentation "engine" i.e. what mechanisms deliver the UI.

Option 1: Custom built Web Parts

With this option you build all your UI using the Web Part framework. Logic etc... can be off in other .Net assemblies or a web service etc... just as you would with any other .Net Application.

Pros:

  • Built using ASP.Net Web Part framework
  • Deployed via Web Part install package or the new Feature/Solution Deployment mechanism
  • SharePoint application provides hosting framework for "putting" these Web Parts on Web Part pages
  • Communications framework for talking with other Web Parts
  • Designed to be highly re-usable across many sites with little effort

Cons:

  • No drag and drop UI for laying out your UI i.e. no design time surface
  • A framework that developers must learn to work within

Summary: A good use of web parts would be where you want to build a widget/mini-application that you can put on many web part pages across many sites.

Option 2: _layouts application

An _layouts application is when you develop an ASP.Net Web Application and deploy it to the c:\program files\common files\microsoft shared\web server extensions\12\template\layouts (what a mouthful!) directory. This is a special directory that gets "virtualized" in each sharepoint site i.e. in each sharepoint site you will have an /_layouts path from the root of the web. E.g. http://servername/sites/sitename/_layouts.

This means you can make your application available under each SharePoint site e.g. http://servername/sites/sitename/_layouts/MyApp/SomePage.aspx

In fact this is how all the SharePoint administration pages are delivered in each site.

Pros:

  • Great way to make your functionality available in every site
  • Easy to develop. It is just like developing a regular ASP.Net web site
  • Context sensitive access to the SharePoint object model. Great for doing work on the site that the user happens to be working in at the time.

Cons:

  • Deployment not managed via Solution deployment mechanism
  • Cant use the ASP.Net master page of the site context as the _layouts application is a separate ASP.Net application

Summary: It is best to use an _layouts based application when you want to extend every site with some functionality such as additional administration pages.

Option 3: User Controls and the Son of SmartPart

The last option is to build your applications UI in ASP.Net User Controls as you would with any other ASP.Net Web Application and then use the Son of SmartPart to deliver those User Controls via a web part.

The Son of SmartPart is a Web Part that is able to "host" an ASP.Net 2.0 User Control :) For more info on this see: http://www.smartpart.info/default.aspx
(if you are wondering who its father is ... that is the SmartPart funnily enough ... and is a Web Part for hosting ASP.Net 1.1 User Controls)

Pros:

  • Simple development experience.
  • You get a design surface to build you UI
  • Deployment reasonably straight forward
  • Can use Web Part connection framework if desired
  • Might be possible to develop these outside of SharePoint first (depending on if they have dependencies to SharePoint).

Cons:

  • Deployment not managed via Solution deployment mechanism Out of the Box (you could build a solution to deploy the Son of Smart Part)
  • Slightly different deployment of User Control files and assemblies (but nothing a .bat file can't fix) during development.

Summary: I think this is a great option when you want to build a rich browser based UI that you only want to use in one (or a couple) of sites. I don't think this is a good option if you want to build a mini-application that you want to include on many sites. A better option in that case might be a Web Part.

Option 4: ASPX pages added to SharePoint Site -- ADDED 15-March-2007 UPDATED 16-November 2007

(Thanks to Michal Gwozdek for emailing me an updated set of steps that work for him)

This option actually was suggested in the comments by a reader.  I thought it was so good i tried it out ... and it works great!  So here it is.

This option allows you to add your ASP.Net application pages into your SharePoint Site.  It also provides for compiling all using the code behind your pages into a DLL.

In a nutshell this option allows you to build your ASP.Net application outside of SharePoint, build it, test it & then add it to SharePoint.  Its great!

Here is how to do it:

1. Install the Visual Studio 2005 Web Application Projects extension.  This gives you the 'old style' web projects in Visual Studio ... so you can compile down to a single DLL etc...

2. START - File - New Project - ASP.NET Web Application - Name it "ItDoesWork"

3. Add reference to Microsoft.Sharepoint

Leave only Microsoft.SharePoint, System, and System.Web

4. In the Solution Explorer create folder "~masterurl" and add masterpage "default.master" inside

5. Replace code behind for the masterpage with:

using System;
using Microsoft.SharePoint;
namespace ItDoesWork._masterurl
{

public partial class _default : System.Web.UI.MasterPage
{

protected void Page_Load(object sender, EventArgs e)
{
}

}

}

6. In the designer, rename ContentPlaceHolder's ID to "PlaceHolderMain"

7. Delete Default.aspx, and add new page - SamplePage.aspx

8. Replace source content with the following:

<%@ Page Language="C#" MasterPageFile="~masterurl/default.master" CodeBehind="SamplePage.aspx.cs" Inherits="ItDoesWork.SamplePage" Title="Untitled Page" meta:webpartpageexpansion="full" meta:progid="SharePoint.WebPartPage.Document" %>

<asp:Content ID="Content5" ContentPlaceHolderID="PlaceHolderMain" runat="server">

Testing Page...

<asp:Label ID="Label1" runat="server" Text="Label"></asp:Label>

</asp:Content>

9. Replace code behind for the page with:

using System;
using Microsoft.SharePoint;

namespace ItDoesWork
{

public partial class SamplePage : System.Web.UI.Page
{

protected void Page_Load(object sender, EventArgs e)
{

Label1.Text = SPContext.Current.Site.Url;

}

}

}

10. Project properties - Build - Output path:

Point it to \BIN folder of our SharePoint Web application. E.g.

C:\Inetpub\wwwroot\wss\VirtualDirectories\moss.litwareinc.com80\bin

You can also manually copy your projects DLL into the \BIN folder each time.

11. Compile your project.

12. Open the web.config file for the SharePoint Web Applicaiton E.g.

C:\Inetpub\wwwroot\wss\VirtualDirectories\moss.litwareinc.com80\web.config

13. Add the following line to the SafeControls section (change to suit your assembly and namespace etc...)

<SafeControl Assembly="ItDoesWork" Namespace="ItDoesWork" TypeName="*" />

14. Change the <trust level="WSS_Minimal" originUrl="" /> line to <trust level="WSS_Medium" originUrl="" />

15. Open your site in SharePoint Designer and drag and drop your SamplePage.aspx page into a folder in your site.

16. Browse to your page E.g.

http://moss.litwareinc.com/TestApp/TestPages.aspx

17. Jackpot! (Hopefully) You should now have your aspx page running in SharePoint.

One of the great things about this option is that you could build your applicaiton outside of SharePoint with any old MasterPage, then deploy to SharePoint and swap out the masterpage string for the correct one.  Thus being able to develop and debug outside of SharePoint and then deploy and test inside SharePoint. 

I can see this option being a favorite for most ASP.Net developers who are used to the integrated/seemless code, build & debug experience.

A note on debugging:  If you want to debug your code once it is running inside SharePoint then all you need to do is attach the Visual Studio debugger to the correct w3wp.exe process (Debug -> Attach to process), set your break points and then hit your page in a browser.

Pros:

  • Simple development experience. Develop outside SharePoint first if desired.
  • You get a design surface to build you UI
  • Deployment reasonably straight forward

Cons:

  • Deployment not managed via Solution deployment mechanism Out of the Box. ( but this might be possible i have not tried it yet)
  • Slightly different deployment of User Control files and assemblies (but nothing a .bat file can't fix) during development.

I really like this option ... coming from an ASP.Net point of view i feel it is a simple option.

 

image

 

In the project that I mentioned at the beginning of the post the following was true:

  • We wanted to surface application UI in one place in SharePoint
  • There was only ever going to be one instance of the application i.e. surfaced via one SharePoint site
  • Lots of different screens in the UI

Can you guess what option we decided on?

Well, it basically boiled down to either building the UI in Web Parts or using the Smart Part method.

In the end it was built using User Controls and the Smart Part because the developers would be more productive building User Controls (they didn't have any prior SharePoint development experience) and we didn't need to re-use any of the application in multiple sites.

So in the end we ended up with a document library to house Web Part pages for each of the UI "Screens". In each of the web part pages we are using the Son of Smart Part to deliver our User Control that delivers that portion of the application.

I am really keen to hear what other options people are using to develop their applications that are delivered inside SharePoint. Feel free to leave comments ...

-Chris.

Updated:  Changed title to include WSS v3 as Patrick rightly points out this is equally as applicable in WSS v3 also.

Posted: Tuesday, September 05, 2006 5:08 PM by chjohn

Webcast sobre preparación de datos para minería en SQL 2008

Para que un modelo de minería de datos sea adecuado y nos dé información correcta es necesario que los datos que lo alimentan esté correctos, en este webcast TechNet Webcast: Preparing Data for Use with SQL Server Data Mining (Level 200) se presentan cosideraciones generales para preparar los modelos de minería de datos.

http://msevents.microsoft.com/cui/WebCastEventDetails.aspx?EventID=1032359357&EventCategory=4&culture=en-US&CountryCode=US

 

Technorati Tags:

Webcast sobre preparación de datos para minería en SQL 2008

Para que un modelo de minería de datos sea adecuado y nos dé información correcta es necesario que los datos que lo alimentan esté correctos, en este webcast TechNet Webcast: Preparing Data for Use with SQL Server Data Mining (Level 200) se presentan cosideraciones generales para preparar los modelos de minería de datos.

http://msevents.microsoft.com/cui/WebCastEventDetails.aspx?EventID=1032359357&EventCategory=4&culture=en-US&CountryCode=US

 

Technorati Tags:

Instalar WSS 3.0 SP1 en Windows Vista

uando se desarrolla para SharePoint es necesario tener instalador WSS 3.0 junto con Visual Studio para que el código compile, normalmente se utilizaba un Servidor para el desarrollo sin embargo ahora el Bamboo Team ha publicado la forma de instalarlo en Windows Vista sin necesidad de tener un servidor, más información en

http://community.bamboosolutions.com/blogs/bambooteamblog/archive/2008/05/21/how-to-install-windows-sharepoint-services-3-0-sp1-on-vista-x64-x86.aspx

The Bamboo Team Blog

Bamboo Solutions is the leading provider of Web Parts and Solution Accelerators for Microsoft SharePoint. The mission of this blog is to connect us with customers and colleagues and foster discussion around the news and issues that affect us all.

How to install Windows SharePoint Services 3.0 SP1 on Vista x64/x86
If you are a developer for SharePoint your best friend has been Virtual PC or VMWare. It’s time to introduce a new friend, Bamboo Nation's SharePointOnVista J

We have put together an installer that allows you to install WSS3.0 SP1 on Vista, both x86 and x64.  This will allow you to develop on your workstation with all the power of a non virtualized environment. You still need VPC and VMWare so don’t feel sorry.

There’s been much discussion about SharePoint being a "bad" development platform. This will remove the objection that you NEED to develop on a Server OS.  I think we all as SharePoint developers have built our “virtualization skills” to a comfortable level now so it’s time to give us a break ;)

So please download the setup helper and try it out. I really want to hear from you about problems you encountered so we can fix them.  Please leave your comments here or we can discuss in this forum. It would be nice to hear about successful installations too J

UPDATE: If you run Windows Vista Home Premium IIS only supports Basic Authentication. Therefore you MUST manually enable Basic Authentication in the IIS management console. 

Current limitations:

  • You must select the Advanced option during install.

  • If you want to run on SQLExpress, manually install it first.  Get it here.

  • You have to manually enable IIS7 with the proper options (explained).

  • Your workstation has to be part of a domain. UPDATE: This is not required.

Here’s how you install it.

First download the installation helper and the correct version of WSS with SP1.

Windows SharePoint Services 3.0 with Service Pack 1

Windows SharePoint Services 3.0 x64 with Service Pack 1

Go here to download our Setup Helper file

Now run the setup helper (WssVista.msi)

image

You will see an UAC prompt select Continue to proceed with the installation.

image

Once the install has completed you will find the SetupLauncher.exe in the install location you selected. If you didn’t change the default option you will see it under the directory ..\Program Files\WssOnVista\Setup

Configuring IIS7

Before we go any further we need to make sure IIS7 is installed with all required options .

Go to Control Panel and click Programs.

Under Program and Features click Turn Windows features on or off.

Under Windows Features select Web Management Tools and World Wide Web Services. Enable at least the following options and choose OK.

Wait until Windows has configured all options.

Installing Windows SharePoint Services 3.0 SP1 on Vista.

After completing the above steps it’s time for the interesting part. Locate SetupLauncher.exe and start it. You will once again see an UAC prompt, select Continue.

image

After the SetupLauncher run, select the WSS installation file Sharepoint.exe, or the MOSS installation file, and click OK.  First, the package will be extracted.

After the files have been extracted the WSS setup program will be started.

The current version only supports the advanced installation option so select that one.

Select Web Front End when asked about Server Type. The database will be created later.

Sit back and relax while SharePoint is being installed, you are running Vista remember ;)

Hopefully you will see the following screen at the end of the installation. If you would get an error during the installation step try to run a Repair.

Leave the checkbox checked and click Close to run the Configuration Wizard.

image

At the second screen select the option to create a new server farm.

image

Specify your database server (e.g. MYLAPTOP\SQLEXPRESS) and account information.

config

image
image

Let the Configuration Wizard do it's work.

image

And you should end up with this screen, congratulations!

image

image

The final result is WSS running on Vista, Enjoy!

/Jonas

Note: Remember that this is a "beta" product tool from Bamboo.  Do not use it for any production work, as well as the usual "backup your system before install this program".  Obviously, running WSS v3 or MOSS on Vista is not a supported environment by MS.  Additional discussion about this tool can be found in this forum.

UPDATE:  If you run Vista Home Premium you have to enable Basic Authentication in IIS, if you don't you will only see a blank page.

Here's how to do it:

Open up IIS management console and Enable Basic Authentication. You have to do this for ALL Web Applications you are creating.

Vista.Home.EnableBasic

Only published comments... May 21 2008, 03:02 PM by Jonas Nilsson

 

Technorati Tags: ,,

Saturday, June 07, 2008

HTTP Monitor HTTP Analyzer

La herramienta HTTPWatch http://httpwatch.com/ se integra con Internet Explorer y permite ver todo el HTML que viaja entre el cliente y el servidor lo cual nos permite hacer análisis y debug del protocolo HTTP y HTTPS.

También está el HTTP Fidder http://www.fiddlertool.com/fiddler/ que permite hacer debug y análisis de HTTP y HTTPs

"Fiddler is a HTTP Debugging Proxy which logs all HTTP traffic between your computer and the Internet. Fiddler allows you to inspect all HTTP Traffic, set breakpoints, and "fiddle" with incoming or outgoing data. Fiddler includes a powerful event-based scripting subsystem, and can be extended using any .NET language."

Technorati Tags:

HTTP Monitor HTTP Analyzer

La herramienta HTTPWatch http://httpwatch.com/ se integra con Internet Explorer y permite ver todo el HTML que viaja entre el cliente y el servidor lo cual nos permite hacer análisis y debug del protocolo HTTP y HTTPS.

Technorati Tags:

Analizador de Protocolos

Una buena herramienta de protocolos es WireShark disponible en http://www.wireshark.org dentro de características incluye soporte para alrededor de 78000 protocolos http://www.wireshark.org/docs/dfref/ captura en línea y análisis offline.

Technorati Tags:

Thursday, June 05, 2008

Cómo crear un cluster simulado en Hyper-V

Si desean crear un laboratorio de clúster dentro de Hyper-V pueden seguir los pasos descritos en este artículo http://blogs.technet.com/pfe-ireland/archive/2008/05/16/how-to-create-a-windows-server-2008-cluster-within-hyper-v-using-simulated-iscsi-storage.aspx

 

How to create a Windows Server 2008 Cluster within Hyper-V using simulated iSCSI storage

Familiar with Virtual Server 2005 and shared disks for creating virtual clusters?  Well its different with Hyper-V.  The shared disk option is no longer available (which I did not know when I started testing).  You have to use iSCSI instead.  Here is a step by step method for creating a fail-over cluster within Hyper-V.  Its a cheap way of setting up a test lab (assuming you don’t have access to Windows Storage server).  In this post I use StarWind to simulate iSCSI storage … its not an endorsement of the product, I just picked it from amongst the crowd.

Windows Server 2008 fail-over clusters support Serial Attached SCSI (SAS), iSCSI and Fibre Channel disks as storage options.  So, how would you go about setting up a virtual Windows Server 2008 test cluster using the new Hyper-V vitalisation product?  The method I am about to outline is a little different to what you might be used to Virtual Server 2005.  The following steps detail how I managed to setup a test cluster using simulated iSCSI storage.  Before beginning it’s worth reviewing this article that outlines the storage options that are available to Hyper-V.  By the end of this post you should have a simple two node cluster up and running using simulated iSCSI storage.

Tools for the job:

  • A Windows Server 2008 server x64 server with the Hyper-V role enabled (I used a Dell Precision 390)
  • One Windows Server 2008 VM to act as a Domain Controller (Clusters must be part of a domain) 
  • Two Windows Server 2008 VMs to act as Cluster Nodes
  • One Windows Server 2003 SP2 VM (or you could use Windows Server 2008 in a Core install to maximise VM performance)
  • iSCSI Target Software: I used Rocket Divisions StarWind product that is available as a 30 day eval and is reasonably priced
  • iSCSI Initiator software (built into Windows Server 2008)

I wont go into how to create a VM but you can find more info from Virtual Guys weblog.

Before I began looking into the iSCSI simulated storage option for my cluster nodes I tried to expose a single VHD to each of my cluster nodes in the hopes that they would share it.  I didn’t get very far and was presented with the following error when powering on the VMs:

Shared VHD

This error is by design (thanks Justin Zarb for point this out) as Windows Server 2008 Hyper-V does not support this sort of storage (see link above for Hyper-V storage options).  The above error is simply a file system error as the VHD “is being used by another process” … should have spotted that :)

SETTING UP THE LAB

Note: I’m assuming that you know how to install Windows Server 2003 and 2008.  I’m also assuming that you know how to install and configure a Window Server 2008 Domain Controller.  If you have any questions leave me a comment and I will see if I can point you in the right direction.

VIRTUAL NETWORK

Create the network with a connection type of “Internal Only”.  I enabled Virtual LAN identification and set the default ID to 2 as this will be my public LAN.  Setting the default to 2 means that if I dont specify a VLAN on subsequent NICs they will be classified as public connections.

VLAN ids:

  • VLAN 2: Public 10.1.1.x/24
  • VLAN 3: Heartbeat 192.168.1.x/24
  • VLAN 4: iSCSI 192.168.2.x/24
SERVER SETUP

Tip: Be sure to rename each network card on the hosts to make identification easier.  If its the public NIC, call it public etc.

Domain Controller: dc01
  • Windows Server 2008 x32 
  • One VHD IDE fixed size disk 10GB
  • 1 x NIC connected to my Virtual Network in VLAN 2

Network settings:

  • IP Addr: 10.1.1.10
  • Mask: 255.255.255.0
  • Gateway: I didn’t bother setting one
  • DNS: 10.1.1.10
Cluster Nodes:
  • Windows Server 2008 x32
  • 1 x VHD IDE fixed size disk 10GB
  • 3  x NICs connected to my Virtual Network in the following VLANs
    • Public card: VLAN 2
    • Heartbeat card: VLAN3
    • iSCSI: VLAN4
Node01

Public NIC: VLAN 2

  • IP Addr: 10.1.1.20
  • Mask: 255.255.255.0
  • Gateway: I didn’t bother setting one
  • DNS: 10.1.1.10

Heartbeat NIC: VLAN 3

  • IP Addr: 192.168.1.4
  • Mask: 255.255.255.0

iSCSI NIC: VLAN 4

  • IP Addr: 192.168.2.4
  • Mask: 255.255.255.0

Note: On all NICs in VLAN 3/4 be sure to disable the Client for Microsoft Networks, disable DNS registration and disable NetBIOS.  Be sure to check your binding order too.   The public NIC should be first.

Node02

Public NIC: VLAN 2

  • IP Addr: 10.1.1.21
  • Mask: 255.255.255.0
  • Gateway: I didn’t bother setting one
  • DNS: 10.1.1.10

Heartbeat NIC: VLAN 3

  • IP Addr: 192.168.1.5
  • Mask: 255.255.255.0

iSCSI NIC: VLAN 4

  • IP Addr: 192.168.2.5
  • Mask: 255.255.255.0

Note: On all NICs in VLAN 3/4 be sure to disable the Client for Microsoft Networks, disable DNS registration and disable NetBIOS.  Be sure to check your binding order too.

iSCSI Target
  • Windows Server 2003 SP2 x32 (see here for notes on W2K3 hosts in Hyper-V)
  • 1 x VHD IDE fixed sized disk 10GB
  • 2 x VHD SCSI fixed sized disks 1GB and 10GB for Cluster disks
  • StarWind iSCSI Target Software
  • 2 x NICs  connected to my Virtual Network in the following VLANs:
    • Public : VLAN 2
    • iSCSI : VLAN 4

Public NIC: VLAN 2

  • IP Addr: 10.1.1.22
  • Mask: 255.255.255.0
  • Gateway: I didn’t bother setting one
  • DNS: 10.1.1.10

iSCSI NIC: VLAN 4

  • IP Addr: 192.168.2.2
  • Mask: 255.255.255.0

Note: On all NICs in VLAN 3/4 be sure to disable the Client for Microsoft Networks, disable DNS registration and disable NetBIOS.  Be sure to check your binding order too.  Make sure you format and assign drive letters to the SCSI VHDs on this VM.

Setting up the Cluster
Configuring the iSCSI target software (Starwind)
  • Install the StarWind software on your iSCSI target VM. 
  • Launch the StarWind management console. 
  • Under the Connections you should see localhost:3260.  Right click on localhost and select Connect.  If I remember correctly the first username and password becomes the default (which you can change later).

Add Connection

  • Right click localhost:3260 and select add Device 
  • Select Disk Bridge Device as the Device type and click next

Add Device

Add Disk

  • Select Asynronous Mode and Allow multiple iSCSI connections (clustering) and click next 
  • Give the disk a friendly name
  • Repeat the steps to add the second disk
Adding disks to the cluster nodes

Each cluster node now needs to be connected to the iSCSI target.  Launch the built in iSCSI initiator and follow the steps below:

  • If prompted to unblock the Microsoft iSCSI service always click Yes otherwise the 3260 port will be blocked. 
  • Click on the Discovery tab and select Add Portal.
  • Enter the IP address for the iSCSI target [192.168.2.2]

Discovery

  • Click the Targets tab and you should now see a list of the disks available on the target

Logon to Target

  • For each disk in the list click Log on and select Automatically restore this connection
  • Click on the Volumes and Devices tab and select AutoConfigure.  You disks should now appear as Devices.
  • Reboot each cluster node as you add the disks.
  • Disks will be offline when you reboot.  Ensure that you bring them online in Disk Management.

When completed (and hosts connected) you should see something like this on the iSCSI target VM.

Final

Installing the Cluster

The new fail-over cluster wizard is quite straight forward and much easier to follow when compared with Windows Server 2003.  There isn't much point in going into too much detail … you’ll find plenty of info on the web.

Here is a step by step guide to installing a two node file cluster in Windows Server 2008.

 

Technorati Tags: ,,

Tuesday, June 03, 2008

PDF IFilter MOSS

El equipo de IFilter de Microsoft publicó el resultado de comparación entre el IFilter de Adobe y el IFilter FoxIT, dicha tabla la muestro a continuación.

Machine : Intel Xeon CPU @ 1.4 GHz (4 hyperthreaded processors)

4.00 GB of RAM

32-bit Win2K3 SP1

Indexer performance set to partly reduced.

FOXIT v1.0 ADOBE v.8

Total # of pdf documents

10917 10917

TOTAL Crawl Time

00:51:26.863 (~ 51 minutes) FOXIT

03:38:00.747 (~ 218 minutes) ADOBE

 

En resume FoxIT es 4.27 más rápido que Adobe, el artículo completo se puede encontrar en http://blogs.msdn.com/ifilter/

Consideraciones de Exchange Server 2003 virtualizado

Cuando se desea virtualizar Exchange Server 2003, el producto recomendado es Virtual Server 2005 R2 SP1, esto para seguir las recomendaciones dadas por Microsoft en el articulo http://support.microsoft.com/kb/320220

Technorati Tags:

SQL Server 2016 Stretch Databases

El SQL Server Stretch Database permite que los datos históricos o de bitácoras puedan ser movidos hacia Azure, específicamente permite mover...