As part of extending my pervious post (Renaming SharePoint 2010 Search Service Database Name) I’m planning to provide a walkthrough practice for changing the Database names for FAST Search for SharePoint 2010 (FS4SP). I will start this post by listing the FS4SP Databases, then walking through the practice of renaming these databases.

 

FAST Search for SharePoint 2010 Databases:

FS4SP mainly deals with 2 Search Service Application (SSA) - FAST Search Content SSA & FAST Search Query SSA – which consist of 3 databases each as following:

• FAST Search Content SSA Databases:
• Content SSA Administration Database
• Content SSA Crawl Store Database
• Content SSA Property Store Database

 

• FAST Search Query SSA Databases:
• Query SSA Administration Database
• Query SSA Crawl Store Database
• Query SSA Property Store Database

 

 

Renaming FAST Search for SharePoint 2010 Databases:

 

Renaming Content SSA Databases

Modifying the Crawl Store Databases for the FAST Content SSA can be edited using the Farm Search Administration page in the Central Administration as following:

1. Go to Central Administration Home >> General Application Settings >> Farm Search Administration
2. Click Modify Topology for the FAST Content SSA.
3. In the Databases Section click the Crawl Database >> Edit Properties
4. Rename the Database Name as needed (Ex: Remove the GUID from the Database Name) and click OK.
5. The changes on the Topology will be in Pending Changes State. Click Apply Topology Changes to confirm these changes.

 

Note: The FAST Content SSA Property Store Database is not shown in the Central Administration.

 

Modifying the Administration and Property Store Databases for the FAST Content SSA can be edited using PowerShell as following:

1. Login as Farm Administrator on the SharePoint 2010 Application Server 2010.
2. Start >> All Programs >> Microsoft SharePoint 2010 Products >> SharePoint 2010 Management Shell >> Run as Administrator.
3. To Rename the FAST Content SSA Administration Database use the following script:

$ContentSSA = Get-SPEnterpriseSearchServiceApplication –identity "[FAST Content SSA Name]"

$ContentSSA.Pause()

$ContentSSA | Set-SPEnterpriseSearchServiceApplication -DatabaseName "[New FAST Content SSA DB Name]" –DatabaseServer "[DB Server Name]"

$ContentSSA.Resume()

4. To Rename the FAST Content SSA Property Store Database use the following script to get the Property Store Database GUID:

Get-spdatabase

5. Then run this script to rename the Property Store:

$ContentSSA = Get-SPEnterpriseSearchServiceApplication –identity "[FAST Content SSA Name]"

$ContentSSA.Pause()

Set-SPEnterpriseSearchPropertyDatabase –Identity "[Property Store Database GUID]" -SearchApplication $ContentSSA -DatabaseName "[New FAST Content Property Store DB Name]" -DatabaseServer "[DB Server Name]"

$ContentSSA.Resume()

 

 

Renaming Query SSA Databases

Modifying the Crawl and Property Store Databases for the FAST Query SSA can be edited using the Farm Search Administration page in the Central Administration as following:

1. Go to Central Administration Home >> General Application Settings >> Farm Search Administration
2. Click Modify Topology for the FAST Query SSA.
3. In the Databases Section click the Crawl Database >> Edit Properties
4. Rename the Database Name as needed (Ex: Remove the GUID from the Database Name) and click OK.
5. In the Databases Section click the Property Database >> Edit Properties
6. Rename the Database Name as needed (Ex: Remove the GUID from the Database Name) and click OK.
7. The changes on the Topology will be in Pending Changes State. Click Apply Topology Changes to confirm these changes.

 

Modifying the Administration Databases for the FAST Query SSA can be edited using PowerShell as following:

1. Login as Farm Administrator on the SharePoint 2010 Application Server 2010.
2. Start >> All Programs >> Microsoft SharePoint 2010 Products >> SharePoint 2010 Management Shell >> Run as Administrator.
3. To Rename the FAST Query SSA Administration Database use the following script:

$QuerySSA = Get-SPEnterpriseSearchServiceApplication –identity "[FAST Query SSA Name]"

$QuerySSA .Pause()

$QuerySSA | Set-SPEnterpriseSearchServiceApplication -DatabaseName "[New FAST Query SSA DB Name]" –DatabaseServer "[DB Server Name]"

$QuerySSA .Resume()

 

 

Hope you find it useful.

 

 

This post is cross posting about Microsoft Egyptian Top Applications for both Windows 8 devices and Windows Phone Devices that was selected as Applications of the Month for August 2013, with application description, and URL from where you can download these great applications:

 

Windows 8 Devices Applications:

كتابنا

هذا التطبيق يتيح لك الإستماع إلى محتوى صوتى عن طريق شبكة الإنترنت، أو تحميله و الإستماع إليه لاحقا. من خلال موقع منصة.

عن المحتوى:بين التقليد والحداثة كان لدينا .. الوقت يتحرك لرسم درسا في تاريخ البشرية الماضية، والعمل الحالي، ومستقبل مفعم بالأمل والرجاء .. تغيير الأدوات اللازمة لإبقاء هذا الكتاب في كل مشهد .. انه كتابنا.

Download now

Taree2y

تقدم موبينيل "طريئي" كأول والتطبيق الأكثر تطوراً لمعلومات المرور والطرق في القاهرة ولاحقاً في محافظات آخرى

Download now

Fun2Learn

يركز التطبيق على تعليم الاطفال كيفية كتابة الأبجدية العربية والأرقام.

التطبيق يستهدف الأطفال من سن (3 – 5) سنوات من خلال واجهات و شخصيات كرتونية مميزة  
Fun2Learn.....
يحفز الاطفال "باستخدام أصوات مرحة" عن طريق قصة توجه الطفل خلال أقسام التطبيق المختلفة.
بالإضافة إلى ذلك، فإن التطبيق يهتم بتعليم الطفل أساسيات تهجئة الحروف والأرقام من خلال صور كرتونية معبرة تظهر بصورة تلقائية مع كل حرف.
Fun2Learn.....
يقدم متعة تعلم الأبجدية والأرقام مع الكثير من المرح

Download now

Windows 8 Devices Applications:

Zoboon

Zoboon is a mobile rewards program designed just for you. It’s a smart, easy and fun way to turn your everyday shopping into great rewards and perks.
Next time you're at your favorite cafe, dining out with friends or shopping, you'll be collecting points that you can redeem for amazing rewards.
Level-up to a Silver or Gold customer at your top stores and enjoy even more points and exclusive advantages.
We are currently live in Cairo, Egypt. Have you got Zoboon app on your Windows phone yet?

Download now

Yallakora

تطبيق ياللاكورة... كل أخبار الكرة علي جهازك
يتيح تطبيق ويندوز فون من ياللاكورة لكل عشاق الكرة الحصول على أخر أخبار الرياضة العربية والعالمية بكل ما تتمتع به أخبار ياللاكورة من مصداقية وسرعة وشمولية إلى جانب مواعيد ونتائج مباريات الدوريات العربية والعالمية.
مواعيد ونتائج المباريات
في هذا الجزء يمكنك أن تتابع مواعيد مباريات الكرة في مصر وحول العالم اليوم وغدا والتعرف على نتائج

Download now

Otlob

This product is brought to you by Otlob.com
With Otlob , you can order breakfast, lunch and dinner on-the-go. Otlob puts all the restaurants of Egypt right in the palm of your hand. Browsing and ordering your favorite food has never been easier. No need to wait on the phone, listen to upselling or even turn on a computer. Ordering your next meal is just a few taps away without uttering a single word.

Download now

EGYPTAIR

Welcome aboard the EGYPTAIR App.
With EGYPTAIR mobile application, planning for your journey is even faster and more convenient
Flight booking:
Booking a flight becomes even quicker and more convenient whilst on the move. You can also have the flight options sorted conveniently by lowest price, departure time or shortest flight duration.

Download now

Enjoy this list of Egyptian Windows 8 and Windows Phone Applications, I will keep the blog updated with the latest top Applications.

 

 

Reference:

http://blogs.msdn.com/b/egtechtalk/archive/2013/09/08/learn-more-about-top-egyptian-apps-download-and-rate-apps-of-the-month.aspx

As one of the common scenarios for Disaster Recovery using Hyper-V Replica is to replicate System Center Virtual Machine Manager (SCVMM) Virtual Machine (VM) while utilize SQL Server 2012 Always-On to replicate the SCVMM DB, however when SCVMM is implemented as high available (SCVMM Cluster), then some points should be considered to allow safe failover to replica datacenter without issues, in this blog post I will cover these points as follow:

VMM Cluster Quorum:

To able to cluster SCVMM VMs you will need to implement guest clustering, however if you decide to use shared disk quorum (which is the default supported quorum) then this will be blocking point to replicate SCVMM VMs using hyper-V Replica, so you should use File Share Witness (FSW) Quorum, which is working and supported for SCVMM cluster, in that case it is better to host this FSW at 3^rd datacenter.

VMM Cluster IP Address Resource:

The second point that need to be considered is the IP Addresses for both SCVMM Server and SCVMM Cluster Resource, VM IP Address can be injected easily from VM Failover IP Address properties when Hyper-V Replica is configured, however in case of failover if you just inject the VM IP Address to assign IP Address for SCVMM VM from replica site then VM will start and will able to login to domain but SCVMM Cluster will fail because IP Address resource is configured with IP Address from primary datacenter, and the work around I used to overcome this issue is to add another IP Address resource in SCVMM cluster as shown in the below screenshot.

Then configure Cluster Name resources for SCVMM cluster to depend on IP Address resource from primary datacenter “OR” IP Address resource from replica datacenter as shown in the below screenshot.

Then you need to test the replication using “Planned Failover” and remember to Failover SQL Always-On availability group as well to make the SQL instance at replica site as the active one.

Finally as a conclusion, it is very easy to replicate SCVMM 2012 Clustered VMs using Hyper-V Replica and SQL Always-On to Disaster Recovery replica datacenter and have it fully functional safely in less than one hour.

 

Introduction

A very powerful integration capability is available between SharePoint 2013 and SharePoint 2010/2013, where SharePoint 2010 can still consume service applications from SharePoint 2013 , in this post I will walk you through a step by step guide on how to consume managed meta data service applications resides in SharePoint 2013 from a site resides in SharePoint 2010 farm ,

you can still use the same steps to consume any other service application to achieve cross farm service application, and this post is also applicable if you want to perform the integration between two SP2013 farms.

• In this sample I assume both farms resides on the same domain.
• The steps below can still work between two SP2013 farms as well.

 

 

1 -Exchange Trust Certificates between farms

An administrator of the consuming farm (SP2010) must provide two trust certificates to the administrator of the publishing farm

• Root Certificate
• Security token service (STS) Certificate

Administrator of publishing farm (SP2013) must provide one trust certificate to the consuming farm (SP2010)

• Root Certificate

 

To export Certificates from Consuming Farm

a-To export the root certificate from the consuming farm

in PowerShell run the following commands:

$rootCert = (Get-SPCertificateAuthority).RootCertificate

$rootCert.Export("Cert") | Set-Content "C:\ConsumingFarmRoot.cer" -Encoding byte

 

b-To export the STS certificate from the consuming farm

$stsCert = (Get-SPSecurityTokenServiceConfig).LocalLoginProvider.SigningCertificate

$stsCert.Export("Cert") | Set-Content "C:\ConsumingFarmSTS.cer" -Encoding byte

under C: drive:

 

 

To export the root certificate from the publishing farm

$rootCert = (Get-SPCertificateAuthority).RootCertificate

$rootCert.Export("Cert") | Set-Content "C:\PublishingFarmRoot.cer" -Encoding byte

• Copy the root certificate and the STS certificate from the server in the consuming farm to the server in the publishing farm.
• Copy the root certificate from the server in the publishing farm to a server in the consuming farm

 

 

2-Managing trust certificates by using Central Administration

Certificates must be imported on both consuming farm and publishing farm as the following:

 

a-Establish trust on Publishing farm (SP2013)

• open CA -- Security -- manage trusts -- from ribbon click new ,

• Since this is a publishing farm we need to import the root certificate and STS certificate extracted from the consuming farm SP2010

a new trust will appear

 

 

b-Establish trust on Consuming farm SP2010

• CA - under security -- manage trusts - from ribbon select New

• since this is a consuming farm you will import only the root certificate of the publishing farm SP2013.

• a new trust will appear :

 

 

3-On the publishing farm, publish the service application

On the publishing farm (SP2013) on which the service application is located, an administrator must explicitly publish the service application. Service applications that are not explicitly published are available to the local farm only

• From CA -- Manage Service Application -- select the service you wish to publish (Managed metadata service application) then select publish from the ribbon

 

• make sure to check publish this service application to other farms

 

Information URL : this is an optional info where you can for instance create a page within SharePoint 2013 and place its link here, so admins will read more info about this service application

Important: Copy the Published URL , we are going to use it in the consuming farm later on

urn:schemas-microsoft-com:sharepoint:service:63f708f6c0284e4ba8f54ef14c604e4e#authority=urn:uuid:237032cbe6f84d279136cc24a6

360514&authority=https://2013-sp:32844/Topology/topology.svc

 

4-Set the permission to the appropriate service applications

You must give the consuming farm permission to the Application Discovery and Load Balancing Service Application on the publishing farm

After doing this, give the consuming farm permission to the published service applications that it will be consuming

• on the consuming farm , you need to get the Farm ID by running the following command:

Get-SPFarm | Select Id

copy the Consuming farm ID : 1ccfc7f5-b62a-4404-962c-359371d2cd60

• On a server in the publishing farm, open CA - manage service applications - select Application discovery service application then from ribbon select permissions

paste the consuming farm ID you extracted previously, then click check names

add the consuming farm ID and grant it full control then press OK

Tip : Or you can optionally use the PowerShell command to achieve the same to above:

$security=Get-SPTopologyServiceApplication | Get-SPServiceApplicationSecurity

$claimprovider=(Get-SPClaimProvider System).ClaimProvider

$principal=New-SPClaimsPrincipal -ClaimType "http://schemas.microsoft.com/sharepoint/2009/08/claims/farmid" -ClaimProvider $claimprovider -ClaimValue 1ccfc7f5-b62a-4404-962c-359371d2cd60

where 1ccfc7f5-b62a-4404-962c-359371d2cd60 is the <consumingfarmid> i extracted from the previous step.

Grant-SPObjectSecurity -Identity $security -Principal $principal -Rights "Full Control"

Get-SPTopologyServiceApplication | Set-SPServiceApplicationSecurity -ObjectSecurity $security

 

 

5-Do the same steps with the service application you wish to publish (managed meta data)

add the consuming farm ID and grant it full the required permissions in my case full access to term store is granted

 

 

 

On the consuming farm, connect to the remote service application

After the publishing farm has published the service application, an administrator of the consuming farm can connect to that service application from the consuming farm if the address of the specific service application is known

now from consuming farm (SP2010) you can connect to a service application that has been shared by the publishing farm (SP2013) by providing the address of the farm's discovery service or the address of the service application.

to do so from the consuming farm open CA - manage service application - from ribbon select connect

Place the connection info for the service application extracted from the publishing farm (managed meta data service application)

urn:schemas-microsoft-com:sharepoint:service:63f708f6c0284e4ba8f54ef14c604e4e#authority=urn:uuid:237032cbe6f84

d279136cc24a6360514&authority=https://2013-sp:32844/Topology/topology.svc

then click Ok

Important: the server time (clock) should be synchronized to be the time on both consuming and publishing farm or else a consuming farm wont be able to reach the publishing farm service due to The security timestamp is invalid between servers.

select the service application , make sure to be added to default proxy group ,then click ok

 

 

now it will appear in the list of service application of the consuming farm (SP2010)

 

 

 

6-Add the shared service application to a Web application proxy group on the consuming farm

An administrator must associate the new service application connection with a local Web application on the consuming farm

in the consuming farm (SP2010) open CA - under service Applications click configure service applications association make sure the new proxy is added to the default group and assigned to the desired web application

 

 

 

7-Validate your work

Open a site within SharePoint 2010 , create a custom list , from ribbon create column

make sure managed Metadata is selected:

scroll down , you should see now the term sets from SP2013 :)

 

 

Additional Scenarios

Note: in some scenarios you might need to allow server to server authentication , if your case is one of the below you need then to configure server to server authentication otherwise you are done, no need to perform any additional steps

• Follow a document on a Team Sites web application when a user’s personal site is located on a My Sites web application. The Team Sites web application makes a request of the My Sites web application on behalf of the user.
• Create or reply to a site feed post for a site that is located on a Team Sites web application but performed through the user’s My Site Newsfeed on the My Sites web application. The My Sites web application will make a request of the Team Sites web application on behalf of the user to write the post or the reply.
• A User Profile Service application task to repopulate the feed cache has to read from the personal site or team site. If the User Profile Service application is running in a different farm, the User Profile Service application sends a request to the My Sites web application or Team Sites web application to read the user or site feed data into the cache

if you need to extend to achieve one of the above scenarios follow the steps in this post then you will be done :) http://technet.microsoft.com/en-us/library/jj992595.aspx