Growth Hacking with Internet based Channels

I compiled this information long time ago for a friend. I found it in one of the folder eating dust. So here you go, hope it helps someone somewhere. You will find lot more information about recent advancements in this field but this could be a good start to understand Growth Hacking.

_________________________________________________________________________________________

Growth Hacking is a marketing technique which aims to attract users at a relatively low cost and primarily by means of technological integration.

Objectives of Growth Hacking:

  1. Increase traffic to website
  2. To increase awareness about the Brand and their products
  3. Generate revenue through online sales.
  4. Build and Manage Online Reputation of the brand

 Phased Approach:

Assumption: SEO is in place for the website. If not execute SEO project of all your marketing assets.

Phase 1: Infrastructure Development (5-10 days) Objectives:

  • Get ready to roll.

Activities:

  • Social Media Accounts Setup, Design and Optimization
  • Advertising Accounts Creation and Setup
  • Content Strategy Planning

Phase 2: Brand Communication and Awareness (3-4 Months) Objectives

  • Communicating the brand – content strategy
  • Reaching out to masses – advertising
  • Generating Email Database – contests
  • Reviews by Bloggers/News/Third Party Content creators- Outreach

Activities

  • Social Media Buzz: A launch campaign
  • Promotions by – Facebook Ads
  • Organic Efforts – Twitter outreach
  • Newsletter Campaigns: Once a week All subscribers who have subscribed/using the app. To ensure that they use the app on regular note.
  • Email BroadCasts via Affiliates: Based on target geography, mass mailers can be planned.
  • Advertising for app promotions
    • YouTube ads
    • Adwords for Apps promotions
    • iAds
    • Other mobile ads via portals like InMobi, StartApp etc.

Phase 3: Roadmap for Remaining 6-8 Months

A detailed analysis of Phase 2 to understand the response rates from various channels. The successful and not-so-successful campaigns will be evaluated. The budgets and roadmap will then be planned for remaining months.

Budget : Estimate budget per phase depending upon response to previous phase.

Channels for outreach

Social Media Channels:

  • Facebook
  • Twitter
  • LinkedIn
  • Youtube
  • Quora
  • Reddit
  • Or any industry specific community/Search Engines

Other Channels

  • Newsletters
  • Bloggers Outreach

Advertisement Channel

  • Facebook Ads
  • Twitter Promoted Tweets

Infrastructure Setup:

  1. Accounts Creation: We set-up client accounts, select the best available Vanity urls.
  2. Design: We do the complete Social Media branding by designing the Facebook Time Line Cover Image, Facebook Profiles, Twitter background, Twitter Cover Image, LinkedIn Cover Image and banners. All designs remain in line with current branding of clients.
  3. Optimization: Optimize the profiles with keywords and meta-description

Daily Activities as part of Growth Hacking Project:

  • Promotional posts about the new products or solutions on Facebook, Twitter.
  • How TO’ photo posts to make Fans understand the amazing products.
  • Humor and Comics
  • Infographics
  • News and Updates in the App development
  • Stories about solutions built using Electrohms products. This should go to the blog as well.
  • Discounts and offers and benefits of using your services etc will be posted.
  • Answering Queries: Projection of the brand as the expert in this field. All the online queries of fans/followers or potential customers will be answered via same social media platform. Even questions are not related to the products, providing answer and linking it back to Electrohms website will help create outlinks for site, reputation and projection as solution provider.
  • Start various open ended discussions. Discussions on different social media  platforms will be initiated to engage users, make them participate, and provide useful solutions to other fellow users.
  • Campaigns: We will run various campaigns. E.g. Solve the challenge where solutions will require to use Client’s products and submit entries online. These can just be the brain teasers for the current/potential customers to engage with the brand.
  • Paid Promotions Management: Profiling and behavior of customers online will help yield more results out of paid online promotions. Facebook Ads are essential for buzz creation and lead generation. A well-targeted Ad to ‘Zebra’ customers can definitely yield the desired result. We will create, manage and optimize your Facebook adverts to increase your reach. Content and the nature of the ads will be focused to yield maximum ROI. Similarly Forums asking questions about buying suitable products of type produced by client will help get more leads. Creating the online community around client’s products through proactively helping potential customers make decisions or solve their problems will be a huge return from this activity.
  • Tracking Leads: We will create database of all leads, potential customers and track the keywords related to Client & their products by using social media tools like Raven Tool and HootSuite. The potential users will be redirected to your website, Facebook and twitter page
  • Twitter:
    • Answering Users: Followers will appreciate your services, seek help etc. Answer to retweets, @mention, messages and replies on twitter to build a personal connect and provide solutions to the users.
    • Trends mapping: Based on your industry, we will map the trends on twitter, to keep your followers updated regarding the services and help you provide. This can be done by searching with the help of keywords related to the subject.
    • User redirect to your site: Closely monitor the users online who are in search of similar App services. They will be answered or re-directed to your website/facebook page. This can be done using HootSuite, Raven tools.
  • Best Timings: On the basis of opening rates, we will choose the best time to schedule tweets. We use http://www.tweriod.com/ to check the best timings depending upon the target demographic segment.
  • Bloggers Outreach: Tech Bloggers, Innovation and Creativity bloggers and other popular bloggers will be contacted to write reviews and spread the word. By providing them a trial version of the app for one month, we can ask them to write reviews about it.
  • SEO We will have to do Search Engine Optimization for the website. SEO helps in improving the visibility of a website on search engines. It includes process of highly ranking a website in search results which will drive more traffic, leads and purchases. It includes the following steps – · Finding the right keywords · Ranking highly for those keywords · Converting visitors into buyers
  • Email Marketing: The database created from various technics explained above will be used for Email Marketing. Email Marketing helps in lead nurturing. We can send bi-monthly newsletter informing them about the products, applications of products, any case studies, offers etc.

Design VM deployments by leveraging availability sets, fault domains, and update domains in Azure

Termininologies to know

  • Availability Set
  • Fault Domains
  • Update Domains
  • Availability Zones
  • Scale Sets

Things to read about

  • defaults and limits for FD & UD
  • How to create global highly available application?
  • How to create application which will not be impacted by Azure induced  unplanned/planned downtimes?

Relevant Blogs:

Videos:

 

Creating Sharepoint 2013/2016 Farm infrastructure in Azure from scratch using mix of Manual and Infrastructure-as-Code approach

I wanted to very briefly list down the steps to create the SP farm from scratch (without using existing ARM template for farm from GitHub) which will include manual steps using portal and also ARM template built during the process.

Following Diagram helps visualize HA SP farm. But one that I have created is just a subset of this for the purposes of developement farm. You can follow HA SP farm topology for production farm.

sharepoint-ha

I have kept it crisp assuming you are aware about the Azure and Sharepoint concepts:

  1. Login to Azure portal
  2. Go to Resources, search for virtual network
  3. Create New Virtual network
  4. Create Three Subnets
    1. BackendSubnet
    2. AppSubnet
    3. FrontEndSubnet
  5. Create Three NSG
    1. BackendNSG
    2. AppNSG
    3. FrontEndNSG
  6. Create 1 SQL server Virtual machine and add to BackendSubnet & apply BackendNSG to it
    1. Use SQL server image for this
  7. Generate ARM template from above virtual machine
  8. Create one more DB server using ARM template generated above. Should be added to same subnet.
  9. Create a Virtual Load Balancer and add above created DB servers to the LB.
  10. Create a DB cluster of above two DB servers by configuring SQL servers on each server. Remember the name given to cluster.
  11. Create 1 App server Virtual machine and add to AppSubnet & apply AppNSG to it
    1. Use Windows server 2016 data center image
  12. Generate ARM template from above app server virtual machine
  13. Create One more VM using same template as app server and add it to AppSubnet and apply AppNSG
  14. Create two more VM using same template as app server and add it to FrontEndSubnet and apply FrontEndNSG
  15. Create Load Balancer in AppSubnet and configure both app servers as resource pool
  16. Create PIP in FrontEndSubnet
  17. Create NIC in FrontEndSubnet
  18. Apply PIP to NIC in FrontEndSubnet
  19. Create LoadBalancer in FrontEndSubnet
  20. Apply NIC to Loadbalancer in FrontEndSubnet
  21. Not install SP in One of the VM in FrontEndSubnet and create a farm “mgd-sp2016”. Use DB cluster name as Database for SP Farm.
  22. Keep installing SP in each remaining VM except DB VMs and add them to the farm “mgd-sp2016” farm created in previous step. Configure WFE and App servers with respective roles
  23. Review and Verify SP farm by creating web applications, site collections, user access, service applications hosted in SP app servers.
  24. Create Availability sets for VMs in each subnet.
  25. Refactor NSG rules, monitoring settings, access settings etc. in SP farm.
  26. Setup dashboard for infrastructure monitoring for the farm resources for availability, health, billing, performance etc.

Comparison of Serverless Capabilities of Azure, AWS and Google Cloud

Serverless architecture is catching up. All three Azure, AWS and Google Cloud provide serverless offerings. Since each of these Companies keep changing these Offerings, I will try to keep up. But as of 8/21/2018, following are the offerings.
azure AWS GC
Sr.No. Service Azure AWS Google Cloud
1 Database CosmosDB Amazon Simple Storage Services Cloud Storage
Cloud Firestore
BigQuery
2 Execution Functions AWS Lambda Cloud functions
Azure Container Instances App Engine
Virtual Kubelets
App Service
Azure Service Fabric Mesh
3 Messaging Event Grid Amazon SNS Cloud Pub/Sub
Service Bus Amazon SQS
4 Workflow Orchestration Logic Apps AWS State Functions
5 Analytics Stream Analytics Amazon Kinesis Cloud Dataflow
6 Intelligence BotService Cloud ML Engine
Cognitive Services
7 Development Visual Studio
Visual Code
8 DevOps VSTS AWS Code Pipeline
AWS Code Build

Azure Architect Certification (70-735) – Preparation Series

Here is official link for latest information on this exam.

Following is my take on this exam.

Which skills are evaluated:

“It takes considerable knowledge just to realize the extent of your own ignorance.”

Simply put, this certification will evaluate your knowledge about in-depth understanding of all Azure features and capability to analyze, decide and prove the choices you will have to make while implementing infrastructure and applications in cloud.

Do not worry about development aspect of applications.

Opinions about passing rate:

According to one of the MVP who spoke at SPSNYC2018, passing rate is around 50% so be prepared to work hard.

How this Certification Helps:

Once you study all the syllabus, you should be able to make architectural decisions about accurate selection of cloud service or configurations for any type of application. Basically, you will be calling shots about which Azure feature to use and how to use it, to meet your requirements.

Plus, possibly improved paycheck.

What is this series about?

I am studying for Azure Architect certification myself. So, everything I am studying I am documenting it in this blog series.

So, Let’s Start:

As of 7/31/2018, following is the approved syllabus for the exam. Each link will take you to the specific blog on that topic.

It is very important to understand the composition of this syllabus for effective preparation. So spend some time just understanding the syllabus.

Content:

Design Compute Infrastructure (20-25%)

Design solutions using virtual machines (VMs)

  • Design VM deployments by leveraging availability sets, fault domains, and update domains in Azure;
  • use web app for containers;
  • design VM Scale Sets;
  • design for compute-intensive tasks using Azure Batch and Azure Batch AI;
  • define a migration strategy from cloud services;
  • determine when to use reserved instances;
  • design for VMs in a DevTest Lab environment (including formulas, images, artifacts, claiming and un-claiming VMs);
  • determine when to use Accelerated Networking;
  • recommend use of Azure Backup and Azure Site Recovery including support for Linux in Azure Backup and integrating Azure Backup in the VM creation process;
  • recommend when to use availability zones

Design solutions for serverless computing

  • Use Azure Functions to implement event-driven actions;
  • design data storage solutions for serverless computing;
  • design for serverless computing using Azure Container Instances;
  • design application solutions by using Azure Logic Apps, Azure Functions, or both;
  • determine when to use API management service;
  • design event routing solutions using Azure Event Grid;
  • design solutions that integrate stream processing and bot messaging

Design microservices-based solutions

  • Determine when a container-based solution is appropriate;
  • determine when container-orchestration is appropriate;
  • determine when Azure Service Fabric (ASF) is appropriate;
  • determine when Azure Functions is appropriate;
  • determine when to use API management service;
  • determine when Web API is appropriate;
  • determine which platform is appropriate for container orchestration;
  • consider migrating existing assets versus cloud native deployment;
  • design lifecycle management strategies

Design web applications

  • Design Azure App Service Web Apps;
  • design custom web API;
  • secure Web API;
  • design Web Apps for scalability and performance;
  • design for high availability using Azure Web Apps in multiple regions;
  • determine which App service plan to use;
  • design Web Apps for business continuity;
  • determine when to use Azure App Service Isolated;
  • design for API apps;
  • determine when to use API management service;
  • determine when to use Web Apps on Linux;
  • determine when to use a CDN;
  • determine when to use a cache, including Azure Redis cache

Create compute-intensive applications

  • Design high-performance computing (HPC) and other compute-intensive applications using Azure Services;
  • determine when to use Azure Batch;
  • design stateless components to accommodate scale;
  • design lifecycle strategy for Azure Batch;
  • design solution that implement low priority batching and job task counting

Design Data Implementation (15-20%)

Design for Azure Storage solutions

  • Determine when to use Azure Blob Storage, blob tiers (hot, cool, archive), Azure Files, disks, Azure Data Box, Azure Storage Service Encryption, and Azure StorSimple

Design for Azure Data Services

  • Determine when to use Azure Data Catalog, Azure Data Factory, Azure SQL Data Warehouse, Azure Data Lake Analytics, Azure Analysis Services, and Azure HDInsight

Design for relational database storage

  • Determine when to use Azure SQL Database and SQL Server Stretch Database;
  • design for scalability and features;
  • determine when to use Azure Database for MySQL and Azure Database for PostgreSQL;
  • design for HA/DR, geo-replication;
  • design a backup and recovery strategy;
  • design optimization strategies for Azure SQL Data Warehouse columnar storage

Design for NoSQL storage

  • Determine when to use Azure Redis Cache, Azure Table Storage, Azure Data Lake, Azure Search, Time Series Insights;
  • design pipelines for managing recurring jobs

Design for CosmosDB storage

  • Determine when to use MongoDB API, Azure Cosmos DB SQL API, Graph API, Azure Tables API;
  • design for cost, performance, data consistency, availability, and business continuity

Design Networking Implementation (15-20%)

Design Azure virtual networks

  • Design solutions that use Azure networking services: design for load balancing using Azure Load Balancer and Azure Traffic Manager;
  • define DNS, DHCP, and IP strategies;
  • determine when to use Azure Application Gateway;
  • determine when to use virtual network (VNet) service endpoints;
  • determine when to use multi-node application gateways, Traffic Manager and load balancers

Design external connectivity for Azure Virtual Networks

  • Determine when to use Azure VPN, Azure ExpressRoute and Virtual Network Peering architecture and design;
  • determine when to use User Defined Routes (UDRs);
  • determine when to use VPN gateway site-to-site failover for ExpressRoute;
  • determine when to use the Container Networking Interface (CNI) plugin;
  • design solutions that use Global VNet Peering

Design security strategies

  • Determine when to use network virtual appliances;
  • design a perimeter network (DMZ);
  • determine when to use a Web Application Firewall (WAF), Network Security Group (NSG), and virtual network service tunneling;
  • organize resources by designing solutions that use service tags

Design connectivity for hybrid applications

  • Design connectivity to on-premises data from Azure applications using Azure Relay Service, Azure Data Management Gateway for Data Factory, Azure On-Premises Data Gateway, Hybrid Connections, or Azure Web App’s virtual private network (VPN) capability;
  • identify constraints for connectivity with VPN;
  • identify options for joining VMs to domains

Design Security and Identity Solutions (20-25%)

Design an identity solution

  • Design AD Connect synchronization;
  • design federated identities using Active Directory Federation Services (AD FS);
  • design solutions for Multi-Factor Authentication (MFA);
  • design an architecture using Active Directory on-premises and Azure Active Directory (AAD);
  • determine when to use Azure AD Domain Services; design security for Mobile Apps using AAD

Secure resources by using identity providers

  • Design solutions that use external or consumer identity providers such as Microsoft account, Facebook, Google, and Yahoo;
  • determine when to use Azure AD B2C and Azure AD B2B;
  • design mobile apps using AAD B2C or AAD B2B

Design a data security solution

  • Design data security solutions for Azure services;
  • determine when to use Azure Storage encryption, Azure Disk Encryption, Azure SQL Database security capabilities, and Azure Key Vault;
  • design for protecting secrets in ARM templates using Azure Key Vault;
  • design for protecting application secrets using Azure Key Vault;
  • design a solution for managing certificates using Azure Key Vault;
  • design solutions that use Azure AD Managed Service Identity

Design a mechanism of governance and policies for administering Azure resources

  • Determine when to use Azure RBAC standard roles and custom roles;
  • define an Azure RBAC strategy;
  • determine when to use Azure resource policies;
  • determine when to use Azure AD Privileged Identity Management;
  • design solutions that use Azure AD Managed Service Identity;
  • determine when to use HSM-backed keys

Manage security risks by using an appropriate security solution

  • Identify, assess, and mitigate security risks by using Azure Security Center, Operations Management Suite Security and Audit solutions, and other services;
  • determine when to use Azure AD Identity Protection;
  • determine when to use Advanced Threat Detection;
  • determine an appropriate endpoint protection strategy

Design Solutions by using Platform Services (10-15%)

Design for Artificial Intelligence Services

  • Determine when to use the appropriate Cognitive Services, Azure Bot Service, Azure Machine Learning, and other categories that fall under cognitive AI

Design for IoT

  • Determine when to use Azure Stream Analytics, Azure IoT Hubs, Azure Event Hubs, real-time analytics, Azure Time Series Insights, Azure IoT Edge, Azure Notification Hubs, Event Grid, and other services that fall under IoT

Design messaging solution architectures

  • Design a messaging architecture;
  • determine when to use Azure Storage Queues, Azure Service Bus, Azure Event Hubs, Azure Event Grid, Azure Relay, Azure Functions, and Azure Logic Apps;
  • design a push notification strategy for Mobile Apps;
  • design for performance and scale

Design for media service solutions

  • Define solutions using Azure Media Services, video indexer, video API, computer vision API, preview, and other media related services;
  • design solutions that use file-based encoding or Azure Media Analytics

Design for Operations (10-15%)

Design an application monitoring and alerting strategy

  • Determine the appropriate Microsoft products and services for monitoring applications on Azure;
  • define solutions for analyzing logs and enabling alerts using Azure Log Analytics;
  • define solutions for analyzing performance metrics and enabling alerts using Azure Monitor;
  • define a solution for monitoring applications and enabling alerts using Application Insights

Design a platform monitoring and alerting strategy

  • Determine the appropriate Microsoft products and services for monitoring Azure platform solutions;
  • define a monitoring solution using Azure Health, Azure Advisor, and Activity Log;
  • define a monitoring solution for Azure Networks using Log Analytics and Network Watcher service;
  • monitor security with Azure Security Center;
  • design TCP connections

Design an operations automation strategy

  • Determine when to use Azure Automation, Chef, Puppet, PowerShell, Azure Automation (DSC), Event Grid, and Azure Logic Apps;
  • define a strategy for auto-scaling;
  • define a strategy for enabling periodic processes and tasks;
  • define an update management strategy

 

SharePoint Online Workflows – Options, Migration and Limitations

Available Workflow Options

  1. Out-of-Box Workflows

SharePoint Online offers number of workflows that are ready for usage. Availability of these workflows will depend on plan.

  • Approval – route documents or items for approval/rejection
  • Three-State Approval – track issues, tasks, or projects through three states/phases
  • Feedback – route a document or item to receive feedback on it
  • Disposition – manage expiration/retention of documents (related to records management)
  1. SharePoint Designer Workflows

SharePoint Designer provides you with a rich feature set that addresses many of the requirement categories listed above. SP Designer Workflows will provide you the basic loop, branching and actions and other lookups and http service call tasks to achieve more complex workflows than Out-of-box workflows. You can migrate (save as template and then upload to SPO solutions) the SPD workflows in SP online.

  1. Flow

Flow is a new workflow app that lets you interact with data within SharePoint and numerous other apps from within the Office 365 apps family and outside. There are plenty of templates available. Also, MS Flow can be extended with custom service endpoints, webhooks/azure functions (i.e. serverless computing services. etc) and queuing systems for more complex logic blocks and data processing which can invoked using connectors/http triggers from flow.

  1. Nintex
  • Nintex workflows are available in SharePoint Online using third party Office 365 app, Nintex. Nintex provides in-browser rich user interface to build and use workflows. It offers intelligent, conditional workflow logic and actions that let you model processes same as real world.

Workflow Migration from SP2010/2013

You can migrate a workflow definition by deploying/developing the workflow to your SharePoint Online site. Individual instances of workflows cannot be migrated, either to the cloud or from one on-premise system to another. However, some third party tools claim to be able to migrate the workflow instances to online (This will be explored in future).

SharePoint On-Premise Workflow Type Can be migrated to/redeveloped into these SPO Workflow Options
Out-of-Box Designer Workflow MS Flow Nintex for Office 365
Out-of-Box As Is Redevelop Redevelop Redevelop
Designer Workflow   As Is Redevelop Redevelop
Nintex     Redevelop* Redevelop (Confirm with Vendor). Some third-party tools (ShareGate) provide capability to migrate Nintex workflows.
Custom Code Workflow     Redevelop* Redevelop*

*Migration is not simple/straightforward due to limitations of SPO/MS Flow/Nintex.

Limitations

  1. Select Workflow option based on support by each option for scenarios:
 Requirement SharePoint OOTB Workflows SharePoint Designer Microsoft Flow Nintex
Multi-Stage Approvals Yes Yes Yes Yes
CRUD SharePoint Data Yes Yes Yes Yes
CRUD External Data No Yes Yes Yes
Provisioning No Yes Yes Yes
Document Generation No No Yes* Yes
Batch Processing No Yes Yes* Yes
Text Manipulation No Yes Yes Yes

*These need custom Flow components.

References:

Recreate Any SharePoint Search Components in existing topology

In this example, we will be recreating the Query Processing component on search because it had some issues preventing it from starting.
Review following script before proceeding with execution

Add-PSSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue
 # Clone the active search topology

$spssa = Get-SPEnterpriseSearchServiceApplication
 $current = Get-SPEnterpriseSearchTopology -SearchApplication $spssa -Active
 $clone = New-SPEnterpriseSearchTopology -SearchApplication $spssa -Clone –SearchTopology $current
 Get-SPEnterpriseSearchComponent -SearchTopology $clone 

Locate the search component QueryProcessingComponent entry and copy the ComponentId:

Remove the component by using the ComponentId above as the -Identity value in the following:

# Remove Orphaned Component
 Remove-SPEnterpriseSearchComponent -Identity 61c1a336-40dd-407f-aa96-fc9909bfd992 -SearchTopology $clone -confirm:$false 

# Add New Search Component
 $server = Get-SPEnterpriseSearchServiceInstance -Identity "server hosting this component"
 New-SPEnterpriseSearchQueryProcessingComponent -SearchTopology $clone -SearchServiceInstance $server

#Depending on which component is failed you can use appropriate command
#New-SPEnterpriseSearchAdminComponent -SearchTopology $clone -SearchServiceInstance $server
#New-SPEnterpriseSearchAnalyticsProcessingComponent -SearchTopology $clone -SearchServiceInstance $server
#New-SPEnterpriseSearchContentProcessingComponent -SearchTopology $clone -SearchServiceInstance $server
#New-SPEnterpriseSearchCrawlComponent -SearchTopology $clone -SearchServiceInstance $server
#New-SPEnterpriseSearchIndexComponent -SearchTopology $clone -SearchServiceInstance $server
 #New-SPEnterpriseSearchQueryProcessingComponent -SearchTopology $clone -SearchServiceInstance $server

# Activate  Search Topology
 Set-SPEnterpriseSearchTopology -Identity $clone

After Successful execution, your topology should be restored. Same script can be used to move your entire topology for part of topology to another server.

 

List of errors you might see during this execution and solutions:

Sr.No.

1
Description
Set-SPEnterpriseSearchTopology : Rollback prending due to the last activation
failure. Cannot start Activation of another topology now.
At line:1 char:1
+ Set-SPEnterpriseSearchTopology -Identity $clone
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidData: (Microsoft.Offic...tSearchTopology:
   SetSearchTopology) [Set-SPEnterpriseSearchTopology], SearchTopologyActivat
  ionException
    + FullyQualifiedErrorId : Microsoft.Office.Server.Search.Cmdlet.SetSearchT
   Opology
Resolution Go to timer jobs and Run “Application Server Administration Service Timer Job” once.
Sr.No. 2
Description
New-SPEnterpriseSearchQueryProcessingComponent : The search service instance
on this server is not online
At line:1 char:1
+ New-SPEnterpriseSearchQueryProcessingComponent -SearchTopology $clone
-SearchSer ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~
    + CategoryInfo          : InvalidData: (Microsoft.Offic...essingComponent:
   NewSearchQueryProcessingComponent) [New-SPEnterpris...essingComponent], In
  validOperationException
    + FullyQualifiedErrorId : Microsoft.Office.Server.Search.Cmdlet.NewSearchQ
   ueryProcessingComponent
Resolution Start the search windows service  or consider using different server to host this search component.