I have faced issues while migrating TFS Server project collection from one server to another, as process is complicated & no easy documentation available for the same. Follow below steps to migrate TFS source Control, Work Items, Reports & SharePoint sites.

So let get started,

1. Open “Team Foundation Server Administration Console” & Stop the TFS project collection which you want to migrate to new server.

2. Now Detach the project Collection as shown below,

3. Now open SQL Management Studio on TFS SQL Server & backup the TFS project collection which you want to migrate,

4. Now open SQL Management Studio on Target SQL Server & restore the backup of TFS Collection DB,

5. Now Open Team Foundation Server Administration Console go to Application Tier, Team Project Collections, click to Attach Collection. Now your restored database will appear here. Sometime you might will face issues with Team Foundation server version so you might need to install TFS 2010 Service Pack 1.

6. Assign Name to project collection & click next

7. Click on Verify.

8. Click on Attach to attach new collection.

9. Click on close to complete the process.

10. Now your TFS project collection DB has been restored & attached to the new TFS server. Now we need to modify our Sharepoint to the new URL. SO open Visual Studio & connect to the restored TFS project & change the SharePoint URL from old to new URL.

 11. Now we need to back & restore SharePoint & Report Server backup

First of all we will backup SharePoint & Report server

1. Go to TFS Server & backup Sharepoint,

stsadm -o backup -url http://mytricks-tfs-01/sites/TestCollection -filename c:\sps.bak

ON SQL Reporting Server

rs -i GetReportsFromServer.rss -s http://mytricks-sql-01/reportserver

you have to download GetReportFromServer.rss before backup of report server & here is the link Download GetReportsFromServer.rss

Now copy backup files to the target server,

To restore backup run below commands,

On TFS server to restore sharepoint run,

stsadm -o restore -url http://mytricks-tfs-02/sites/TestCollection -filename c:\new folder\sps.bak
Go to the new SQL server & download PushReportsToServer.rss from Download PushReportsToServer.rss
Now Open Command prompt & RUN
rs -i PushReportsToServer.rss -s http://mytricks-db-02/reportserver

After restoration don’t forget to process Data Warehouse and Analysis Services Cube on new TFS server..

Apple has released OS X MOuntain Lion 10.8.3 update and below are the feature & fix,

The 10.8.3 update is recommended for all OS X Mountain Lion users and includes features and fixes that improve the stability, compatibility, and security of your Mac, including the following:

The ability to redeem iTunes gift cards in the Mac App Store using your Mac’s built-in camera
Boot Camp support for installing Windows 8
Boot Camp support for Macs with a 3TB hard drive
A fix for an issue that could cause a file URL to quit apps unexpectedly
A fix for an issue that may cause Logic Pro to become unresponsive when using certain plug-ins
A fix for an issue that may cause audio to stutter on 2011 iMacs
Includes Safari 6.0.3

In last post I showed you How to Install Microsoft Lync 2013 Step By Step Now in this post we will learn how to install Microsoft Lync 2013 persistent chat server.

What is Persistent Chat Server->

Persistent Chat previously known as Group Chat in Lync 2010 lets organizations set up topic-based chat rooms that persist over time and can be searched, allowing geographically distributed teams to better collaborate with one another in real time.

In Lync Server 2013, Persistent Chat has had key changes – integrated client experience within the Lync 2013 client, integrated server deployment and administration and management with Lync Server 2013.

Prerequisites for Persistent Chat Server ->

• Microsoft Lync Standard Edition 
• SQL Server 2008 R2

Let get started,

Open Lync Server 2013 Topology Builder & Right Click on Persistent Chat Pools & Selecy new persistent Chat Pools,

Assign name to Persistent Chat Pool & Do not change default Persistent Chat port,

Define the Fully qualified domain name for Chat pool. In my case I am using Single Computer pool..

Define SQL Store,

Define the file store for Chat server,

Here you can see the overview of the persistent chat server. Now publish the topology.

Once you Now publish the topology open Lync Control pane & go to Persistent Chat the new tab in Lync 2013. Click on Persistent Chat policy & edit the Global policy.

In global persistent Chat policy Select “Enable Persistent Chat” & Click OK.

Now click on Category& click on “New”.

Select Service as shown,

Assign name & description to the New Category.

Tick
Enable inivitation
Enable file upload
Enable chat history

And Add members to the chat group.

Now open ”Computer Management” as shown below

Add user in “RTCLocalAdministrators”, who’s going to manage persistent chat,

Now login to the Lync client & click on “Create a Chat Room”,

After creating Chat Group, re-login to the Lync client. Now you can view the newly created Chat group..

Today Microsoft has released Lync 2013 client for Windows Phone 8. Now Lync mobile 2013 supports much waited VOIP , Video calls including desktop sharing  and Call Forward or simultaneously ring calls option over 3G, 4G and WiFi.

Currently Lync 2013 mobile client supports only Windows Phone 8 & there is no support for 7.8.

http://www.windowsphone.com/en-us/store/app/lync-2013/d85d8a57-0f61-4ff3-a0f4-444e131d8491

I am going to cover step by step installation steps of Microsoft Lync 2013. There is no big difference as far as installation is concerned if you compared Lync 2010 with Lync 2013.

In my environment I am using below setup,

1. Active Directory Server with certificate server- Windows 2012 Std Edition

2. Microsoft Lync server Supports only 64 bit operating system & in my case I am using,

Windows 2012 Std Edition

SO you will need two machines to test Lync 2013 in test environment. If you want to use Windows 2008 then you can use Windows 2008 R2 64 bit for Lync 2013.

So let get start,

To Install Lync 2013 front end server there are few prerequisites software needs to be installed on front end server as listed below,

1. IIS

2. MSMQ

3. Windows Identity Foundation 3.5 (Windows 2012)

4. .NET 3.5 framework & .NET Framework 4.5

To install Lync 2013 insert your Lync 2013 DVD OR mount ISO & run setup.exe. Setup will prompt to install “Microsoft Visual C++ 2012 x64″ Click on “Yes” as shown below screen shot

Click on “Install” as below. If you want you change installation location as per your requirement.

Accept Microsoft License Agreement & click on “OK”

Setup will launch a “Deployment Wizard”. Click on “Prepare Active Directory” to prepare active directory schema, forest & domain for our Lync server.

First step is to “Prepare Schema” as shown below.

Click next to start “Schema Preparation” for Lync server.

Click “Finish” to complete schema preparation.

There is no need to “Verify Replication of Schema Partition” as in my setup I am having only one Active directory server.

Now “Prepare Current Forest” for Lync 2013 setup

Click next to “prepare current forest”

Select “Local Domain” & click next.

Click on finish to complete forest preparation.

Now we need to prepare our Active Directory Domain for Lync 2013 as shown below,

So select “Prepare current domain” & click on Run

Click Next.

Click Finish to complete Domain preparation.

As shown below we have prepared our active directory “Schema” & “Domain” for Lync setup.

In my case I am going to install Standard Front end server. SO click on “Prepare first Standard Edition Server”.

Click on “Next” to start setup.

Click Finish to complete the setup.

Now “Install Administrative tools” on front server.

E

Now we need to create DNS records for Lync server under DNS forward lookup zone as shown below,

I have created DNS record for

1. Dialin.mytricks

2. Meet.mytricks.in

3. Admin.mytricks.in

4. Lyncweb.mytricks.in

Also we need to create SRV record for front lync server as shown below.

Now open “Lync Server Topology Builder” to create new Topology for Lync server.

Select “New Topology” & click on OK.

Give any name to your topology & save it.

Assign Primary SIP domain name to your topology.

In my case I don’t have any additional supported SIP domain so I leave it blank.

Assign name to your Lync site & click Next.

Add Lync site details such as City, State & Country & click Next

Click on Finish to open “Front End Wizard”

This wizard will create a Lync Front End pool for your Lync site. Click Next to proceed.

Enter FQDN of your Front end server “fe.mytricks.in” & select “Standard Edition Server” & click Next

Select feature you want to install on your front end server. I am going to install Archiving & Monitoring Server on separate server. Click next to proceed.

Select “Collocate Mediation Server” & click Next. If you want you can install Mediation server on separate server to handle the load as required.

Currently I do not have edge server in my test lab so I have unchecked “Enable an edge pool to be used by the media component of this front end pool”. If you install Edge you select below tab by modifying topology via topology builder.

Click next. Lync front End server will install SQL 2012 Express edition while installing Lync 2013.

Create File Share on your Front End server & provide Full access to below Groups,

RTC Universal Server Admins

RTC Universal Config Replicator

RTCHS Universal Services

RTC Component Universal Services

In my case External Base URL is “lyncweb.mytricks.in”

Office Web Apps Server is must in Lync 2013 to share & view PowerPoint presentation during meetings. Currently I do not OWA server but you can specify the URL which you are planning to use with your OWA server.

Click on Finish to complete the wizard.

Now we need to specify simple URL for “Administrative Acess” as shown below. So right on Lync 2013 Server & click on “Edit Properties”

Specify your Administrative URL & Front End server to install Management Server as shown below.

Now you need to publish your topology. So right on your site->Topology->Publish.

Click “Next” to publish topology.

Select Central Management Server & click “Next”

Click on “Finish”

Now we need to “Install or update Lync server System”. This option will install Lync Server core components such mediation server.

Select “Install Local Configuration Store” & click “RUN”

Click Next as shown below.

Click “Finish” to complete installation of “Local Configuration Store”

Now select “Setup or Remove Lync Server Components” & click “RUN” as shown below.

Click on “next” as shown below.

Click on “Finish” to complete the setup.

Now we need to assign Certificates to Lync front end server. In my case I have installed Certificate Server on my Active Directory Server i.e. ad.mytricks.in

To request certificate from certificate server click on “Request” as shown below.

Click Next to proceed.

Select “Send the request immediately to an online certification authority” & click Next.

Select your CA server as shown below & click “Next”.

Click on “next” as shown below.

Assign friendly name to your certificate request & click Next.

Provide your organization information & click “Next”

Click on “next” as shown below.

If you want to add additional SAN then add it & click next.

Click on “next” as shown below.

Click on “next” as shown below.

Click “Finish” to complete certificate request.

Now we need to assign request certificate to Lync Front End server as shown below.

Click on “next” as shown below.

Click Finish to complete the process.

Now you can see the certificate is assigned to Lync Server. Also you need to repeat the same Certificate Wizard steps shown above for the “OAuthTokenIsuer”

Now click on “Start Services’ to start Lync Services.

Now we have completed Lync 2013 front End server installation. Now we need to Add & enable user for Lync. So open Lync Control Panel->Users->Enable Users as shown below.

Install Lync Basic 2013 on Windows 8 or 7 & login to Lync client as shown below.

You can download Lync Basic Client from below URL

http://download.microsoft.com/download/4/5/3/45367500-0EEB-458F-9BD5-F43778C9F841/lyncentry.exe

In coming post I am going to cover installation of,

Lync Edge Server

Lync Monitoring & Archiving Server

Office Web Apps Server

While working on Microsoft Lync I have faced “Call failed due to network issue” while making audio/video calls to the users. In my environment I have successfully implemented Lync for IM, audio video conference, Auto Attend, voice mail. But calling was the issue in different scenarios.

I was not able to able to make calls due to ” call failed due network issue” in below scenario,
1. if user is connected Lync from home via Internet and other user is in office network

I was able to make calls if,
1. If I connected to the Office network via Remote Access VPN & other users is in office network
2. If both user are connected to Lync server via internet through Lync edge server.

But call fails if both users in the different network i.e. in office or at home

In my network we have five location & user logs in to the Lync server from different five location via site 2 site vpn or from home via Internet.

Below are the network details of five offices,

Server Network – 192.168.1.0/24
Office 1 – 192.168.1.2/24
Office 2 – 192.168.3.0/24
Office 3 – 192.168.4.0/24
Office 4 – 192.168.5.0/24
Office 5 – 192.168.6.0/24

My Microsoft Lync front end server is in the 192.168.1.0/24 network along with my archiving, monitoring, SQL Server & Edge server Internal facing network card.

TO resolve you have to add routes for your internal network on your Lync Edge server,
My Edge server IP’s are
1. Internal
192.168.1.10 Mask 255.255.255.0
No gateway
DNS – Internal DNS server

2. External Facing Network
IP – 10.10.12.10 Mask 255.255.255.0
Gateway – 10.10.12.1
DNS – 4.2.2.2 & 8.8.8.8

My gateway for Internal network traffic for my Edge server is (192.168.1.0/24) is 192.168.1.1 so that it can communicate with the Lync front end server. Same way you need add routes for your other network i.e. offices on your edge server as shown below,

Open Command Prompt on Edge Server & add routes

route add -p 192.168.1.0 mask 255.255.255.0 192.168.1.1
route add -p 192.168.2.0 mask 255.255.255.0 192.168.1.1
route add -p 192.168.3.0 mask 255.255.255.0 192.168.1.1
route add -p 192.168.4.0 mask 255.255.255.0 192.168.1.1
route add -p 192.168.5.0 mask 255.255.255.0 192.168.1.1

Gateway will be the same for all other network traffic. Once you add persistent route restart Edge server & try to make calls.

If you want to search only Lync sip enabled users in Lync search List then here is the answer. By default Lync address book service scans AD for address book & Lync only adds users to its address book if is able to find or normalize to a valid phone number (E.164). The Address Book service uses the normalization rules in company_phone_number_normalization_rules.txt

But in my case I just want to add Microsoft Lync SIP enabled users in Microsoft Lync client search list.

So lets get start,

Download Microsoft Lync Resource Kit from below URL and install it on front end Lync server.
http://www.microsoft.com/en-us/download/details.aspx?id=21165

Navigate to C:\Program Files\Microsoft Lync Server 2010\ResKit & open ABSConfig.exe

Here I am going to include only Lync SIP enabled users in Lync address book, so in “Only include users that have a value for this AD attribute” should be msRTCSIP-PrimaryUserAddress

Click on Apply changes & close the ABS configuration tool. Wait for 0-24 hours to populate the Lync address book & see the results. Or you can refer below guide to manually change the Lync address book download interval.

http://mytricks.in/2012/09/solved-lync-contact-search-not-showing-all-users.html

While working on Microsoft Lync few users reported me that they are not able to view all Lync contacts. Follow below process to solve Lync contact search issue,

1. Open Microsoft Lync management shell & run Update-CsUserReplicatorConfiguration command, This process synchronizes data between Active Directory and the Lync SQL database.

PS C:\> Update-CsUserReplicatorConfiguration -verbose

2. Now run PS C:\> update-csaddressbook -verbose command

Above command trigger the Microsoft Lync Server to synchronize current Active Directory information in the Lync SQL database into the downloadable client and device address book files. (i.e. GalContacts.db & GalContacts.db.idx )

Now Update Lync Clients address book download interval- The address book does not populate itself immediately it takes 0-24 hours to populate the contacts. To change the Lync address book download interval follow below process,

Execute the following command from the Windows Command Prompt to add registry entry (run as an administrator) to change the address book download interval,

reg add HKLM\Software\Policies\Microsoft\Communicator /v GalDownloadInitialDelay /t REG_DWORD /d 0 /f

Now open C:\Users\santosh\AppData\Local\Microsoft\Communicator folder replace Santosh with actual username & delete Lync profile i.e. sip_santosh@mytricks.in OR delete the Lync address book files (i.e. ) i.e. GalContacts.db & GalContacts.db.idx ) from C:\Users\santosh\AppData\Local\Microsoft\Communicator\sip_santosh@mytricks.in (replace sip_santosh@mytricks.in with actual user name.

Close the Lync client completely & sign-in. wait for 5 min & search for the Lync contacts. After login to Lync client you will see the new address book files i.e. GalContacts.db & GalContacts.db.idx downloaded from Lync front end server in your Lync folder.

VirtualBox is a powerful virtualizer for x86 hardware. Its is targeted for server, desktop and embedded use, it is now the only professional-quality virtualization solution that is also Open Source Software. Presently, VirtualBox runs on Windows, Linux, Macintosh, and Solaris hosts and supports a large number of guest operating systems.

Features of VirtualBox are:

Improved Windows 8 support, in particular many 3D-related fixes
Virtual machine descriptions in XML
GUI: VM groups
GUI: expert mode for wizards
GUI: allow to alter some settings during runtime
Support for up to 36 network cards
Resource control: added support for limiting network IO bandwidth
Added possibility to start VMs during system boot on Linux, OS X and Solaris
Added experimental support for Drag’n'drop from the host to Linux guests

Download Location: VirtualBox 4.2.0 RC1

Today I faced issue while publishhing my Microsoft Lync Web Services URL via Microsoft Threat managemtn gateway. Everytime while testing TMG website rule I get The target principal name is incorrect error. You can see the below error in detail, Testing

https://lync.domain.com:443/OWA/

Category: Destination server certificate error Error details: 0×80090322 -

The target principal name is incorrect.

After doing lot of R&D I found the solution. I have found any article in detail but few blogs help me a lot. Actually the issue is with Certificate CN (Common Name) used at Lync FrontEnd server (i.e. Lync External Web Services) & Threat Magement Gateway side (Public Name of the URL which we enter while creating web Publishing rule) You need to import certificate on both Lync Front End (use Lync topology builder to apply the certificate) & TMG server. for example your Lync external web services name is lyncweb.domain.com then common name should lyncweb.domain.com with additional SAN which are you going to use (e.g. dialin.domain.com etc). Also ensure Public name of the URL which you are going to enter while creating web publishing rule should match with Lync external web service else it will not work..

In next article I will cover how to create certificate request for TMG & how to import it on TMG & Lync front end server.