# Create a proxy for the Subscription Settings service application. $appSubSvc = New-SPSubscriptionSettingsServiceApplication –ApplicationPool $appPoolSubSvc –Name “Subscription Settings Service” –DatabaseName “MSS_Dev_SP13Ent1_SVC_SubSet” # Create the Subscription Settings service application, using the variable to associate it with the application pool that was created earlier. $appPoolSubSvc = New-SPServiceApplicationPool -Name “PoolSVC_SubSet” -Account $account # Create an application pool for the Subscription Settings service application. $account = Get-SPManagedAccount "AJB\SP13_SVCSubSet" #Gets the name of the managed account and sets it to the variable $account for later use. Run the following PowerShell from the SharePoint 2013 APP Server:.Create an account called “SP13_SVCSubSet” in AD and add it as a managed account in SharePoint Central Admin.Administrators group on the local server.db_owner fixed database role on all databases that are to be updated.securityadmin fixed server role on the SQL Server instance.Verify you have the following permissions (The SP_Install account should have this access):.Also, Spencer Harbar has a great article on the changes of Multi Tenancy in SharePoint 2013 at Therefore, even if you are not hosting multiple tenants, you must still establish a name for the default tenant for your environment (any SharePoint site that is not associated with a tenant will be in the default tenant). These service applications use the multi-tenancy features to provide app permissions and create the subdomains for apps. Setup Subscription Settings Service Application (Using PowerShell Only)Īnswer (From ): Apps rely on the App Management and Microsoft SharePoint Foundation Subscription Settings service applications. You would still need to purchase a SSL Certificate for *. because each app has its own subdomain. Many people try to use subdomains for apps so that they don’t have to purchase an additional certificate, but what they don’t realize is *.ajb.local will not work for the app subdomain of *.
![sharepoint 2013 http 404 not found sharepoint 2013 http 404 not found](https://i.ytimg.com/vi/TzyOQrcrOb4/maxresdefault.jpg)
In this example I would need to pull a certificate for *.ajbapps.local. At this point if we are using port 443 for SharePoint sites/Apps (recommended) you will need to create a Wildcard SSL Certificate at this time.Type * for the alias name and type the FQDN of the target host (SharePoint Server) and Click OK.Right click the new zone name and select New Alias (CNAME).Create a wildcard CNAME Record for the new app domain.
![sharepoint 2013 http 404 not found sharepoint 2013 http 404 not found](http://ericoverfield.com/wp-content/uploads/2013/08/August-CU-Navigation-Demo.jpg)
#Sharepoint 2013 http 404 not found update