AV exclusions

This comes up often and I can never find everything in one place. This is a good post with a bunch of info and links.

TFS 2008 to TFS 2010 Install notes

Recently (about 5 minutes ago) I did an upgrade in production of our Team Foundation 2008 server to Team Foundation 2010. I had a dry run that worked well but of course on the real thing I had a couple of issues. Here are some notes.

• TFS requires sysadmin on the new SQL server, it wants to create/drop databases like crazy
• TFS previous to 2010 required sharepoint to be installed, with 2010 it’s just an option, you can add it later.
• To clean up from an earlier install (failed, test run, etc.) you can run this command (see the gotcha at the end!)

C:Program FilesMicrosoft Team Foundation Server 2010Tools>tfsconfig setup /un
install:all

The steps are

1. Install TFS 2010
2. Configure TFS 2010 (this creates databases)
3. Backup your old TFS databases (all of them)
4. Restore your old TFS databases to your new sql instance
5. Run the TFS import command from command line. It should look like this:

C:Program FilesMicrosoft Team Foundation Server 2010Tools>Tfsconfig import /s
qlinstance:serverinstance /collectionName:imported /confirmed

Once you do this, you should be good to go

We had an error when trying to install on production because it kept finding information from the previous one. Apparently the tsconfig /setup uninstall:all doesn’t really uninstall all! There were extended database properties left over that we had to delete manually. Until we did this, we received this error:

• TF30046: The instance information does not match.

There are very useful logfiles located in:

• C:ProgramDataMicrosoftTeam FoundationServer ConfigurationLogs

In order to get visual studio 2005 to connect to TFS 2010, you have to install in this order:

1. Visual studio 2005
2. Tfs plugin for vs 2005
3. Vs 2005 sp1
4. Vs 2005 vista compatibility update (run windows update)
5. Vs 2005 TFS 2010 update
6. Then you enter the full URL in the server name field: http://tfs2010_server:8080/tfs
7. If it tells you that you can’t put in the “/” and such, it means you installed in the wrong order.

In order to get visual studio 2008 to connect to TFS 2010, you have to:

1. Install vs 2008
2. Install vs 2008 sp1
3. Install vs 2008 TFS compatibility pack
4. Enter servername as: http://tfs2010_server:8080/tfs

That’s all I have for now. After all the devs come in and hit this tomorrow I may have some more updates (but I hope not!).

 

 

Advertisement

urlscan issue

I have the following URLscan value:

 

RuleList=DenyUserAgent

 
[DenyUserAgent]
DenyDataSection=AgentStrings
ScanHeaders=User-Agent

[AgentStrings]
Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1
Opera/9.02 (Windows NT 5.1; U; ru)

In the logfiles I am seeing where it is blocking non russian mozillas, like this:

2010-11-05 21:49:23 76.94.140.86 896362 GET /programs/images/t8.jpg Rejected rule+’DenyUserAgent’+triggered User-Agent: mozilla/5.0+(windows;+u;+windows+nt+6.1;+en-us;+rv:1.9.2.3)+gecko/20100401+firefox/3.6.3 mozilla/5.0+(windows

(The logfile truncates after a certain length.) I do not understand why it is blocking this mozilla version with a totally different user agent. ???

Looking for an answer on this one….

.net apps using SQL connections that aren’t closed properly

I already blogged about this partially here, and of course having debug disabled comes into play as well. Anyway, we figured out a problem here at work that is well documented here. It’s a good read and was really helpful for us to figure out how to recode the app.

.net health monitoring

This is a little blurb I use almost everywhere for almost everything that will log all sorts of useful info about a .net app in the application log. It will grab unhandled exceptions as well as application lifetime events (app pool or domain restarts, etc.) This is a really good one to use when your devs won’t add this to the code themselves! It will work (or has for me) straight up in any .net code. All you do is place this in the web.config.

<healthMonitoring enabled="true">

      <eventMappings>

        <clear />

        <!– Log ALL error events –>

        <add name="All Errors" type="System.Web.Management.WebBaseErrorEvent" startEventCode="0" endEventCode="2147483647" />

        <!– Log application startup/shutdown events –>

        <add name="Application Lifetime Events" type="System.Web.Management.WebApplicationLifetimeEvent" startEventCode="0" endEventCode="2147483647"/>

      </eventMappings>

      <rules>

        <clear />

        <add name="Application Events" eventName="Application Lifetime Events" provider="EventLogProvider" profile="Default" minInstances="1" maxLimit="Infinite" minInterval="00:01:00" custom="" />

        <add name="All Errors Default" eventName="All Errors" provider="EventLogProvider" profile="Default" minInstances="1" maxLimit="Infinite" minInterval="00:00:00" />

      </rules>

    </healthMonitoring>

this is just dumb

I had to install the SMTP service on a 2008 server today for the first time, and Microsoft does not make it easy.

1. The SMTP install is under features and not under roles.
2. When you do install SMTP, where do you manage it, you wonder. Thanks to google and this link, I now know that you have to use the IIS6 manager. What??!!