I believe in Hyper-V!

MicrosoftCategory Archives

Disable IPv6 in Windows Server 2008 R2 all editions

This is old information but can be useful for those who read my blog.

We have three methods to disable IPv6 in Windows Server 2008 R2.

The first method is the fastest;

Open Control Panel –> Network and Sharing Center –> Change adapter settings –> double click on your network adapter –> Properties –> deselect Internet Product Version 6 (TCP/IPv6) –> click OK and Close.

2

If you want to completely disable IPv6 you need to use second and the third methods.

Second method:

– Click Start –> run –> regedit

– Locate the following registry entry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters

– In the details pane click New and then click DWORD (32-bit) Value.

– Type DisabledComponents, and then press ENTER.

– Double-click DisabledComponents, and then type 0xffffffff in Hexadecimal or 4294967295 in Decimal.

Note: The 0xffffffff value or the 4294967295 value disables all IPv6 components except for the IPv6 loopback interface.
http://support.microsoft.com/kb/929852

3

Third method:

Open command prompt and type:

reg add hklm\system\currentcontrolset\services\tcpip6\parameters /v DisabledComponents /t REG_DWORD /d 255 /f

4

Migrate TFS 2010 Project Collection to another TFS 2010 server

If you want to migrate one or more TFS Project Collections from one TFS server to another follow this procedure. Procedure is very important and if you skip any step your will have the problem. For that reason read and follow this article from beginning.

NOTE: You can’t to migrate Team Project only, you need to migrate whole Collection. With this process you migrate Work Items and Source Control only. In my second blog post I’ll write about how to migrate Reports and SharePoint sites. That is more complicated procedure.

Step 1.

Stop Team Project Collection which you want to migrate.

1

Step 2.

Detach Collection.

2

Step 3.

Open your SQL Server Management Studio and backup database which you want to migrate. Before backup I advice to shrink your database (log and data).

3

Step 4.

Copy database on to your new TFS server and restore to SQL server.

4

Step 5.

Open Team Foundation Server Administration Console go to Application Tier >>> Team Project Collections, click to Attach Collection and follow the Wizard.

5

Your restored database will appear.

6
7
8

Team Project Collection is attached but with warnings about Reporting, SharePoint Products and Lab Management. As I mentioned before, you can’t to migrate Reports and SharePoint site easy.

Migrated Team Project Collection is up and running.

9

Step 6.

Check your migrated Project/s.

10

 

That’s It!

The security database on the server does not have a computer account for this workstation trust relationship

Before few days ago I returned snapshot/checkpoint with scvmm and turned on virtual machine, but when I tried to logon with domain user I gave this message, „The security database on the server does not have a computer account for this workstation trust relationship“. I need to mention that snapshot/checkpoint was old only three hours.

image

I logged in with local Administrator account and removed server from the domain and again join to the domain. After restart I logged in with domain account but few services didn’t start. I again restarted server, tried to logon and I gave the same message „The security database on the server does not have a computer account for this workstation trust relationship“.

Solution/Workaround:

You need to do two things.

1. Reapply values in ADSI Edit (adsiedit.msc) or enter new if SPN missing.

    Open adsiedit.msc like on picture below and check settings in servicePrincipalName

image

2. Restart the computer.

3. Login on to your server with local Administrator account.

4. Change domain from FQDN to the short name. In my case ekobit.corp change to ekobit_corp

5. Restart your server and Login as the domain user.

Relax your mind and enjoy Smile.

NOTE: As you might know Winlogon service on Windows 7, Windows Server 2008 and Windows Server 2008 R2 Operating Systems use Kerberos logon. So the Service Principal Names (SPNs) need to be configured properly to support Kerberos Authentication.

Other Reference Articles:

Kerberos Authentication Problems: http://blogs.technet.com/b/askds/archive/2008/05/29/kerberos-authentication-problems-service-principal-name-spn-issues-part-1.aspx

Symptoms when secure channel is broken: http://blogs.technet.com/b/asiasupp/archive/2007/01/18/typical-symptoms-when-secure-channel-is-broken.aspx

Machine Account Password Process: http://blogs.technet.com/b/askds/archive/2009/02/15/test2.aspx