MBSA can be run offline (if the machine being used to scan is not connected to the Internet). If using it in this configuration, it is necessary to ensure the latest updates are used.

• Security update catalog (wsusscn2.cab) is available from http://go.microsoft.com/fwlink/?LinkId=76054.
• Windows Update Redistribution Catalog (wuredist.cab) located at http://update.microsoft.com/redist/wuredist.cab.
• Authorisation catalog (muauth.cab) for Windows Update site access is available from http://go.microsoft.com/fwlink/?LinkId=43266 or by examining the contents of the wuredist.cab file located at http://update.microsoft.com/redist/wuredist.cab.
• Windows Update Agent standalone installers (if not already installed). The latest versions are available by examining the contents of the wuredist.cab file located at http://update.microsoft.com/redist/wuredist.cab.
• For x86-based computers (WindowsUpdateAgent30-x86.exe)
• For x64-based computers (WindowsUpdateAgent30-x64.exe)
• For ia64-based computers (WindowsUpdateAgent30-ia64.exe).

Once you have installed the latest updates, follow the steps below to run the scans.

Create a new text file called ‘computers.txt’ and list the names of the servers to be scanned – as shown in Figure 1 below. This should be saved on the computer being used to run the scan.

Figure 1: Computers.txt file contents

Open a command prompt and navigate to ‘C:\Program Files\Microsoft Baseline Security Analyzer 2’

Run the following command (This assumes that the wsusscn2.cab and the text file ‘computers.txt’ have been saved into the root of the C: drive.:

Mbsacli /catalog c:\wsusscn2.cab /listfile c:\computers.txt /wi /nvc /nd

/wi = show all updates even if not approved on the WSUS server.

/nvc = Do not check for a new version of MBSA.

/nd = Do not download any files from the Microsoft.com web site when scanning.

Wait for the scan to complete.

Open the MBSA console from the Start Menu.

Click ‘View existing security scan report’.

The first and foremost is to “BE PROACTIVE”, as a captain
one needs to be proactive in anticipating the needs of his stakeholders and
that can only be done by cultivating a healthy relationship and which is
possible through more and more interactions. Being a Project Manager one should
not be constrained to the audience he/she needs to report to or work with on
management aspects of the project, but should try to interact with all the
members which also includes the all the Customers Team who has direct or
indirect influence or interest in the project success or failure. This is only
possible if a Project Manager take on or share some responsibilities of the
work which allows to have interaction with the team. There are always areas and
opportunities present in the project which one needs to grab and help, which
helps in becoming part of the team rather than sitting on the top and dictating
others – as its rightly quoted “The way to get started is to quit talking
and begin doing.”

The second is to be with the team, even though they might
not need you. It is very important for the team to see you around which helps
in building their confidence. They know you are there for them and you can be
approached easily. This acts a double edge sword, you get to know the minute
details which will empower you to take right decisions at right time. One
should not be constrained by money but should try to be innovative in
motivating the team members. Team is what makes the Project Manager
complete. You are like a disabled person if your team is not with you.
Apart from time at office the Project Manager should treat his team as his
family and should try to create informal environment to interact with the team
and get to know each other. This could be Dutch movie or dinner party,
celebrating special occasions like birthdays, awards, or small treats at
Barista or even over snacks. This provides a chance to understand the needs of
all team members and their way of working. This way you can prioritize the work
accordingly and take their help in achieving the impossible.

The third one that comes to my mind is being “TRANSPARENT”,
be open with your stakeholders, read A as A and don’t try to hide anything
under the hood. All the stakeholders are interested in making the Project
successful and the ones who are not you should try to use them for critical
reviews. Being transparent both in giving the bad news as well as good news.
This is not an easy thing to do  always but this will help to build your
credibility as a person on whom the stakeholders can reply upon. As
consultants, Project Managers should also become Trusted Advisor to the
customer, and all internal and external stakeholders. This way you get to be
looked upon as a person who is interested in making project success and are not
just constrained by the numbers, data and processes. All that are Project
Managers weapons, which one has mastered well but should not be the focus for
the Manager. Those should be part of your daily routine where as your aim
should be the success of your stakeholders

The next release of BizTalk Server will be BizTalk Server 2010 R2, which will focus on three primary themes:

1. BizTalk On-Premise
2. BizTalk on Azure IaaS 
3. BizTalk on Azure PaaS

1. Seamlessly connect with Azure artifacts, enable hybrid scenarios and access on premise LOB systems from Azure
2. Consume REST services directly in BizTalk, ESB Toolkit part of BizTalk setup
3. On-demand BizTalk Development and Test environments - BizTalk Iaas
4. EAI and EDI Services through BizTalk PaaS

For more details refer BizTalk Server Roadmap:  http://www.microsoft.com/biztalk/en/us/roadmap.aspx

1. The tool has to be exectuted from the BizTalk 2006 R2 machine with OS.
2. Copy the "MSI\Program Files\Schemas" folder and the dependent dlls from the ISO extract.
3. The config file of the tool has been modified appropriately for pointing the location on the dlls (same folder as tool exe).

These steps needs to be performed once you have successfully migrated BizTalk 2006 solution to BizTalk 2010 solution.

• Legacy SQL Adapter is configured to
1. Stored Procedure which has SELECT and INSERT statements.
2. Update Gram INSERT 

Issue # 1

WCF SQL adapter: Need to change to Strongly Typed Stored Procedure in case the default one with DataSets / Array of Datasets is not required. Optional, the issue with this is that the SQL response gets changed completely. In case the migration tool is used since the tool does not give an option of selecting the output type which we otherwise get when we use a WCF Sql Adapter from scratch- Manual Step.

Resolution

The response message schema (Legacy Sql Adapter) is backward compatible with the WCF Adapter. Hence even though the Migration tool generates a brand new schema (multirooted - both for request as
well as response), it does not change the message type of the response message.

[Below change is applicable only in case the legacy response schema is backward compatible which happens only when the response contains a collection - Non-Insert]

A small change needs to be done in the SOAP Header section of the WCF Request/Response Port - Prefix the namespace with 'XML'

Issue # 2

Logical Port Operation name needs to be mapped to Operation name in the Binding Info

Resolution

Issue # 3

The Old schemas and the port types remain with the solution and can be removed if required

Resolution

To be done as per the project requirements and based on other dependencies.

Issue # 4

Create a new physical send port (WCF Custom - Sql Binding) by importing the bindings which have been added under the migration process.

Resolution

Import the bindings (customer one, generated by the tool itself and then make the necessary changes if any)

1. If any Sql response schema is being used in map as a source then ensure that both the "AttributeFormDefault" and "ElementFormDefault" should be set to Unqualified. This is because of a bug in WCF which results in blank
   namespace (xmlns="“) at the individual record level of the response which results in mapping failure.
2. In case any map this involves more than one source or destination schema and if one of those multiple source or destinations schemas is the changed Sql schema, then the migration tool fails to update that map. This has to be done manually.

• Legacy SQL Adapter is configured to
  1. Polling Stored Procedure - SELECT

Issue # 1

The polling schema made available to the solution by Legacy SQL Adapter is backward compatible and hence can be used as it is by the WCF Sql Adapter.

But one issue which still persists and requires manual change (not specific to Migration tool as the issue is with the WCF Adapter) -

Records fetched by WCF Sql Adapter have blank XMLNS with every record unlike the legacy Sql Adapter where there are no such blank namespaces coming along. This results in validation failure wherever the polled schema is being used as a SOURCE SCHEMA.

Resolution

Additionally following 2 changes need to be made: 

1. Need to feed in the "PolledDataAvailableStatement" as it is a mandatory field before the polling operation could start.
2. Marked "UseAmbientTransactions" as false to eliminate the error.
3. For the blank namespace problems - the ElementFormDefault property needs to be set to 'False'

The credit for this goes to Amit Shuka (http://www.linkedin.com/in/shuklaamit)

ADO.NET Entity Framework – Overview

The ADO.NET Entity Framework enables developers to create data access applications by programming against a conceptual application model instead of programming directly against a relational storage schema. The goal is to decrease the amount of code and maintenance required for data-oriented applications. Entity Framework applications provide the following benefits:

· Applications can work in terms of a more application-centric conceptual model, including types with inheritance, complex members, and relationships.

· Applications are freed from hard-coded dependencies on a particular data engine or storage schema.

· Mappings between the conceptual model and the storage-specific schema can change without changing the application code.

· Developers can work with a consistent application object model that can be mapped to various storage schemas, possibly implemented in different database management systems.

· Multiple conceptual models can be mapped to a single storage schema.

· Language-integrated query (LINQ) support provides compile-time syntax validation for queries against a conceptual model.

Getting Started (Entity Framework)

The Entity Framework supports the Entity Data Model (EDM) for defining data at the conceptual level. When using the ADO.NET Entity Data Model Designer, conceptual model, storage model, and mapping information is contained in an .edmx file. The Entity Framework also enables developers to program directly against the data types defined at the conceptual level as common language runtime (CLR) objects. The Entity Framework provides tools to generate an .edmx file and the related CLR objects based on an existing database. This reduces much of the data access code that used to be required to create object-based data application and services, and makes it faster to create object-oriented data applications and services from an existing database. The tools also allow you to build a conceptual model first, and then automatically generate related CLR objects and a supporting database.

Generating Models and Mappings

Entity Framework applications and services are based on model and mapping information that is expressed in three XML-based languages:

· Conceptual schema definition language (CSDL)

· Store schema definition language (SSDL)

· Mapping specification language (MSL)

CSDL represents application data as a set of entities and relationships in a conceptual model, and it is an implementation of Entity Data Model. A storage model is expressed in SSDL and represents the schema of the data store. The mapping between the two models is expressed in MSL.

The CSDL, SSDL, and MSL content for an application can be automatically generated by the ADO.NET Entity Data Model Tools. The Entity Data Model Wizard generates model and mapping information as well as data classes from an existing database. The Entity Data Model Designer (Entity Designer) can then be used to graphically modify model and mapping information.

For our example, we refer to Updategram scenario, which consist of following tables:

· TitlesTitleRaw

· TitlesTitleNameRaw

Refer following steps for generating model and mapping information using Entity Data Model Wizard.

1. Create a Visual C# Class Library project and name it as Titles.Samples.Data.

2. After project is added, Add New Item and select ADO.NET Entity Data Model. Name it as Titles.Model.asmx.

3. In the appearing window, select ‘Generate from database’ and click on the ‘Next’ button. It will open ‘Choose Your Data Connection’ page which allows configuring destination database connection.

4. Select ‘New Connection’ to configure desired connection settings. For our example, we consider Server Name as ‘localhost’, Use Windows Authentication and Database as ‘Staging’. Test the connection and click on the ‘OK’ button.

5. In ‘Choose Your Data Connection’ page, click on the ‘Next’ button to open ‘Choose Your Database Objects’ page. This page allows us to select the desired tables (mentioned in above list) to generate Entity Model and apply corresponding mappings between the selected tables. Also, change Model Namespace to ‘Titles.Sample.Data’, and click on the ‘Finish’ button.

6. Now, the Entity Model ‘Titles.Model.edmx’ is generated with selected tables and their relationships. Save the project.

7. Go to ‘Solution Explorer’, select ‘Titles.Model.edmx’ file and view its properties. In ‘Properties’ pane, empty ‘Custom Tool’ property. It will remove ‘Titles.Model.Designer.cs’ file from the project.

[Note: Our solution targets POCO Entity Classes, and hence we ignore the code generated by ‘Custom Tool’ mentioned in ‘Titles.Model.edmx’ file properties. In the next section, we use ‘ADO.NET POCO Entity Generator’ to generate the required POCO entity classes corresponding to each table in the model.]

Generating POCO Entities using ‘ADO.NET POCO Entity Generator’

POCO stands for Plain-Old CLR Objects. POCO support in Entity Framework 4.0 means that these EntityObject - based types can be replaced with much simpler classes. POCO entity types are not required to inherit from any particular class and do not need attribute to map to the homologous elements in the model. Instead, types and properties in the objects and in the model are associated at runtime simply based on their names.

Adding the POCO template

The POCO Template can provide a good jumpstart by generating POCO classes that correspond to the model instead of the default EntityObject classes.

1. In order to do this, you can right-click on an empty area of the “Titles.Model.edmx” canvas and select ‘Add Code Generation Item…’

2. This will bring up the Add New Item dialog, in which you can choose which Template you wish to use. The POCO Template can normally be found under the Visual C# category.

3. On this screen select “ADO.NET POCO Entity Generator” and type “Titles.tt” as the name of the new item. Then click on the ‘Add’ button.

Understanding how the POCO Template works

When you choose the POCO Template two T4 template files are added to your project. In this case one is called “Titles.Context.tt” and the other is called “Titles.tt”. T4 stands for Text Template Transformation Toolkit, and is a template engine that ships with Visual Studio. The Entity Framework POCO Template leverages T4 to allow you to customize code generation.

Once you have added the POCO template, your project will look like this:

The “Titles.tt” file is responsible for generating a file for each EntityType and ComplexType in the “Titles.Model.edmx” model. “Titles.tt” also generates a file called “Titles.cs”, which contains a FixupCollection<T> class used by the POCO classes to keep the opposite ends of a relationships in sync.

The second template (“Titles.Context.tt”) produces a strongly typed ObjectContext for the “Titles.Model.edmx” model. You use this strongly typed ObjectContext to interact with your database.

Note that each time you edit and save any T4 template the dependent files are regenerated, so you shouldn’t edit the generated files directly, or your changes will be lost. If you wish to modify the generated code, you can modify one or both of these templates.

The primary goal of the POCO template is to produce persistence ignorant entity classes.

However, the strongly typed ObjectContext derives from ObjectContext, which is an Entity Framework class. So this template must live in a project with a reference to the Entity Framework.

By splitting the template into two, one part that generates the Entity Types and Complex Types and one that generates a strongly typed context, it makes it possible not only to have Entities and ComplexType that are persistence ignorant but further to put those classes in an assembly / project that has no persistence aware code in it at all.

Moving entity types to a separate project

1. To continue, add a new Class Library project to the solution called Entities. You can remove the class1.cs file created by default in the new project.

2. Now, in the “Titles.Sample.Data” project, add a project reference to the “Titles.Sample.Entity” Project:

3. Next, move the “Titles.tt” file into the Entities project. To do that, you can simply drag & drop the file into the Entities project in the Solution Explorer window, while you hold the Shift key at the same time.

Editing “Titles.tt”

Fix the link to “Titles.Model.edmx”

The POCO Template’s template files need to be able to read metadata from the EDM model in order to generate the right code. Since we have moved the template, the relative location of the Model has changed; therefore we need to fix the template so its link back to the model is correct again. To do this you can modify a line close to the top of the template from:

string inputFile = @ “Titles.Model.edmx” ;

To:

string inputFile = @ “..\Titles.Sample.Data\Titles.Model.edmx”;

This is simply a relative path from the template’s new location to the Titles.Model.edmx file in the other project.

Replacing ICollection<T> to List<T>

The POCO Template generates entity classes with Navigation Properties which are used to maintain foreign-key relationships. ICollection<T> is used to hold the related entity type. Our approach is to represent entity classes as XSD (generated using XSD.exe), to enable mapping using BizTalk Mapper. Since, ICollection<T> doesn’t support serialization, we replace ICollection<T> with List<T> to maintain this relationship. To do this you can modify “Titles.tt” to reflect the changes in all entity classes. Refer below code snippet for the corresponding changes.

Before Change:

After Change:

Once you’ve done this, Save the template, and this will regenerate the POCO entity classes. You can check that the contents of the file “Titles.cs” under “Titles.tt” has the right contents to verify that the path entered. Also, notice the “Titles.Sample.Entity” project has no reference to the System.Data.Entity (aka the Entity Framework), and is completely persistence ignorant.

Generating XSD representing POCO Entities using XSD.exe

After successfully compiling ‘Titles.Sample.Entity’ project, using XSD.exe generate the Schema (XSD) file representing the entities in ‘Titles.Sample.Entity’ assembly.

1. Open Command Prompt by typing ‘CMD’ in RUN Command.

2. Navigate to ‘Titles.Samples.Entity’ project folder, and run XSD tool by providing the path of ‘Titles.Samples.Entity.dll’. Refer below screenshot:

3. Add the schema files (.xsd) generated as a part of your BizTalk schemas project. The schema generated would look like below.

4. All the schema nodes are separated as individual root nodes. Since our transformations require mapping input data to all these nodes, we group them under a single root node named ‘Titles’.

Now this schema could be used for transforming Titles Canonical message to Titles Entities message, which in runtime will be de-serialized into individual entities and saved into database. We will cover this in next section.

The credit of this approach goes to David Bastow (http://www.linkedin.com/pub/david-bastow/7/60/b7b). 

The credit of this approach's execution goes to Sathish Krishnan (http://www.linkedin.com/in/satykrish).

1. Install Visual Studio Team Explorer

http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=329

2. Install TFS Power Tools

http://visualstudiogallery.msdn.microsoft.com/c255a1e4-04ba-4f68-8f4e-cd473d6b971f

3. Identify list of tasks / groups which need to be synced to TFS, example all task in “Analysis Phase”, deployment task, or whole project as the case may be.

4. Get/grant “Admin Access” from an Administrator/to consultant.

a. Right Click on Project è Team Project Settings => Group Membership

b. Select Project Administrators and click on Properties.

c. Select “Windows User or Group” and click on “Add”.

d. Click on “Add”, Select the User to grant Permissions.

e. Click on “OK” and “OK” on the parent window to apply the settings.

5. Update the Process Template using the “Process Editor”.

6. Based upon the Process template selected during the creation of the TFS Project, use one of the following ZIP:

7. Unzip the selected file and follow the steps below:

a. Open Microsoft Visual Studio 2010.

b. Using Team Explorer connect to the TFS Server.

c. Select Team è Process Editor è Work Item Types è Import WIT

d. Select Team Project Collection and click on “Connect”.

e. Select the right Project to Import to:

f. Select the Path of the Task.XML unzipped in above step.

g. Repeat the steps “a-f” for “Unplanned Task.xml”. You would be able to see a new Work Item Type called “UnPlanned Task”

h. Execute the “Visual Studio Command Prompt (2010)” in “Run as Administrator” mode

i. Update the values of the <TFS Server Collection URL> and <Team Project> in the below command line:

TFSFieldMapping upload /collection:"<TFS Server Collection URL>" /teamproject:"<Team Project>" /mappingfile:MappingFile.xml

j. On the Command Prompt change the directory to location of the Un Zip files

k. Execute the above command with correct values of <TFS Server Collection URL> and <Team Project>.

8. In MPP: All the Resources should be taken from Active Directory, follow the steps below:

9. For the tasks selected in point 1 makes sure that all the resources assigned are Active Directory Users, we cannot have any resources which are not resolved in Active Directory.

10. Go to Team Tab

11. Connect to Team Project.

12. Select the TFS Project

13. You might get this screen, just continue and press “Update”.

14. Make sure you have defined Iteration and Area Path for your TFS Project. This can be done from inside the MS Project itself.

15. Add following new Columns in the MPP which come after connecting to TFS.

a. Iteration Path

b. Area Path

c. Work Item Type

d. Publish and Refresh

e. State (Optional)

16. Click on Add New Column and select è Area Path

17. Click on Add New Column and select è Iteration Path

18. Make sure that Area Path and Iteration Path for the Tasks to be synced have correct values selected:

19. Select “Work Item Type” and set the value as “Task”.

20. For Publish and Refresh select the value as “Yes” against the entire Task that you want to perform sync with TFS.

Possible values for Publish and Refresh are

a. Yes (Publish to TFS)

b. No (Don’t Publish)

c. Refresh Only

When you use Microsoft Project to create parent and child tasks, it assigns parent tasks the rollup of hours that are defined for all its child tasks. Rollup hours are not published to Team Foundation so that the hours are not double-counted in certain reports. The Microsoft Project mapping file attribute, IfSummaryRefreshOnly, suppresses the publication to Team Foundation of the hours that are assigned to summary tasks. You can view the rollup of hours for summary tasks in Office Project but not in Team Foundation.

21. Once all has been setup just go to Team Tab and click “Publish”.

Scrum Task Template.zip