Quantcast
Channel: AutoSPInstaller
Viewing all 2279 articles
Browse latest View live
↧

Commented Feature: Add farm account to db_owner role on search databases after creation [21520]

December 12, 2014, 12:43 am
$
0
0
To remedy a potential issue as written here: http://techmikael.blogspot.no/2014/10/caution-if-you-have-used.html, would it be possible to patch this using autospinstaller, granting the correct rights to the farm account?
Comments: ** Comment from web user: Wobba **

I just did a report when re-creating my SSA.

Ran PowerShell as the SPInstall user. SPAdmin is the farm account. I scriptet up the SSA, then went to the UI and added my local miksven user as an admin. Boom... lot's of errors in the ULS on db permission issues and query does not work. I then manually gave back db_owner rights to my searchadmin user on the search db and it worked again.

↧
Search

Created Unassigned: Add a check for PowerShell version [21606]

December 12, 2014, 7:45 am
$
0
0
Could I suggest adding an initial check for the Powershell version as the scripts do not work with version 2?
↧
↧

Reviewed: AutoSPInstaller for SharePoint 2010 + 2013 (Dec 12, 2014)

December 12, 2014, 8:06 am
$
0
0
Rated 5 Stars (out of 5) - Must have tool!
↧

Commented Unassigned: Add a check for PowerShell version [21606]

December 13, 2014, 8:46 pm
$
0
0
Could I suggest adding an initial check for the Powershell version as the scripts do not work with version 2?
Comments: ** Comment from web user: brianlala **

AutoSPInstallerLaunch.bat (the recommended way to kick off the script) already checks for PowerShell v2.

Brian

↧

Closed Unassigned: Add a check for PowerShell version [21606]

December 13, 2014, 8:47 pm
$
0
0
Could I suggest adding an initial check for the Powershell version as the scripts do not work with version 2?
↧
↧

Commented Issue: STS#0 Template Not Creating Membership Groups with AutoSPInstaller [20605]

December 14, 2014, 11:56 am
$
0
0
With my XML for AutoSPInstaller I create 6 Web Applications - 4 of these are created using the STS#0 template. Each has XML like this:

```
<WebApplication type="Other" name="Site Name" applicationPool="ConnectApplication Pool" url="https://SiteName.corp.company.com" port="443" UseHostHeader="true" AddURLToLocalIntranetZone="true" GrantCurrentUserFullControl="false" useClaims="true" useBasicAuthentication="false" useOnlineWebPartCatalog="false">
<Database>
<Name>Content_SiteName</Name>
<DBServer />
<DBAlias Create="false" DBInstance="SERVER\INSTANCE" DBPort="" />
</Database>
<ManagedPaths />
<SiteCollections>
<SiteCollection siteUrl="https://SiteName.corp.Company.com" HostNamedSiteCollection="false" Owner="Company\james" Name="SiteName" Description="Site Name" SearchUrl="https://portal.corp.company.com/search" CustomTemplate="false" Template="STS#0" LCID="1033" Locale="en-us" Time24="false" />
</SiteCollections>
</WebApplication>

```

I'll also Clarify and say that all 4 other sites are categorized as WebApplication type "Other" - not sure if that has any bearing.

Under Site Settings > People and Groups - None of the site Have the usual SharePoint security groups created for them.

* _SiteName_ Owners
* _SiteName_ Members
* _SiteName_ Visitors

Instead There is only one security group listed - __Excel Services Viewers__ - Why it picked this I have no idea

After AutoSPInstaller is done If I create a Site Collection manually using STS#0 (Team Site) It does get the security groups. Also, if I delete the site collection and recreate it, it gets the expected groups.

I can supply the complete XML config file if it helps.
Comments: ** Comment from web user: webguynj **

Glad I could help with this issue

↧

New Post: Creating Index Partitions using AutoSPInstaller

December 15, 2014, 8:56 am
$
0
0
Has @davobo;s Search topology code made it into, or is it planned to be added to a future release of AutoSPInstaller?
↧

Commented Issue: Checking Index component - fail [20230]

December 15, 2014, 8:44 pm
$
0
0
Experienced a fail during a 2013 installation. Had previously installed on the same server, uninstalled SP2013 and deleted DB's. When reinstalling script failed at creating the Search Index as files from the previous installation still existed.

_System.Management.Automation.ParameterBindingException: Cannot bind parameter 'RootDirectory'
to the target. Exception setting "RootDirectory": "___New index location must be empty___" --->
System.Management.Automation.SetValueInvocationException: Exception setting "RootDirectory":
"New index location must be empty" ---> System.ArgumentException: New index location must be
empty_

Fix is probably just a simple case of checking for any existing files in the location, and if exist delete, prior to creating ??
Comments: ** Comment from web user: bobchauvin **

The following Technet article talks about manual clean up of the index location when deleting the SSA
http://technet.microsoft.com/en-us/library/jj219721%28v=office.15%29.aspx

↧
Search

New Post: Enable SSL on SharePoint 2013 HNCs

December 17, 2014, 9:12 am
$
0
0
Hi

For the purposes of expediency, I am currently provisioning a number of HNSCs on my Server farm using standard HTTP urls with AutoSpInstaller. I should be getting my wildcard cert in a couple of weeks. Do I take it the config script just needs to be changed with HTTPS URLS to enable SSL in my various HNSCs: essentially verify the cert and setting up the AAMs etc. Alternatively, should I manually configure SSL for a more user defined setup, say extending any web apps or whatever.

Will be interested to hear your thoughts.

Daniel
↧
↧

Commented Issue: Corner case bug in MatchComputerName function [21419]

December 17, 2014, 1:53 pm
$
0
0
On line 6894 of AutoSPInstallerFunctions.ps1 is the following line of code:

```
If ($computersList -like "*$computerName*") { Return $true; }
```

While this is a nice one-liner, it will not work correctly if one computer name is subset of another. For example, assume that there is an app server named Box1 and a WFE named Box11. In this case Box1 will match both of these and the app server will get the WFE bits installed (assuming server names are used).

Interestingly, the fix is to just delete this line. The following lines, 6895 - 6904, achieve the same goal without this potential bug.
Comments: ** Comment from web user: CCCPSpy **

I just discovered this issue after I was creating a test lab with a SharePoint server named "SPRTM" and a SQL Server named "SPRTM-SQL."

↧

Commented Unassigned: SP 2013 Farm with SSL offloading or termination at the load balancer [21517]

December 17, 2014, 7:20 pm
$
0
0
I posted this elsewhere as a comment but reposting here since it seems to be the better place.

There seems to be an issue when trying to set up a 2013 environment to be configured with SSL offloading or termination to the LB. In this case we want the URL to read https but port to be 80.

1. This fails the creation of the web app and site collection.
2. It attempts to auto configure and import a self signed certificate just because the url is https. We don't want that since we are offloading.

Should we be doing things differently? SSL offloading is quite common and hoping someone else has dealt with this before.
Comments: ** Comment from web user: mongey **

Usually with SSL offloading, the SharePoint Web Application is configured as HTTP, and the Load Balancer has the certificate and will change the URL to HTTPS when users browse to your SharePoint site.

↧

Commented Unassigned: SP 2013 Farm with SSL offloading or termination at the load balancer [21517]

December 18, 2014, 4:13 am
$
0
0
I posted this elsewhere as a comment but reposting here since it seems to be the better place.

There seems to be an issue when trying to set up a 2013 environment to be configured with SSL offloading or termination to the LB. In this case we want the URL to read https but port to be 80.

1. This fails the creation of the web app and site collection.
2. It attempts to auto configure and import a self signed certificate just because the url is https. We don't want that since we are offloading.

Should we be doing things differently? SSL offloading is quite common and hoping someone else has dealt with this before.
Comments: ** Comment from web user: brianlala **

@mongey is correct. Plus I doubt you'd ever want your protocol to be https:// but your port to be 80 - that's just confusing.

Brian

↧

New Post: Enable SSL on SharePoint 2013 HNCs

December 18, 2014, 4:16 am
$
0
0
No, it's actually pretty simple - you should set everything up with HTTPS/SSL from the get-go. AutoSPInstaller will provision and install a temporary self-signed wildcard certificate, which you can replace with your real cert once you get it. That way all the URLs/ports/zones will be set up correctly from the start and all you'll need to do is swap out the certificate.

Brian
↧
↧

Closed Unassigned: SP 2013 Farm with SSL offloading or termination at the load balancer [21517]

December 18, 2014, 4:17 am
$
0
0
I posted this elsewhere as a comment but reposting here since it seems to be the better place.

There seems to be an issue when trying to set up a 2013 environment to be configured with SSL offloading or termination to the LB. In this case we want the URL to read https but port to be 80.

1. This fails the creation of the web app and site collection.
2. It attempts to auto configure and import a self signed certificate just because the url is https. We don't want that since we are offloading.

Should we be doing things differently? SSL offloading is quite common and hoping someone else has dealt with this before.
↧

New Post: Enable SSL on SharePoint 2013 HNCs

December 18, 2014, 4:49 am
$
0
0
Brian



Thanks very much. Funnily enough, I thought this morning my plan B would be to use a self-cert if this was an issue. Your advice makes sense as there is less chance of reconfigure changes later on. One thing I noticed is the config file (3.66) schema hasn't needed to changed to accommodate the latest cert provisioning which is also neat.




Daniel
↧
Search

New Post: Enable SSL on SharePoint 2013 HNCs

December 21, 2014, 11:28 am
$
0
0
Brian


Just to let you know this is one of the smoothest installs I have now have SSL access on all my site collections. Copying host files to my testers until the DNS entries are implemented. One thing of interest is that I did get a error when I didn't specify the Myhost URL and path . Even though I __did __provision a dedicated a dedicated web app for it without a HNSC. entered the URL etc and re-run and tested mysites. all good
" MySiteHostLocation and MySiteManagedPath are for when you are NOT provisioning a dedicated MySite host web application and would instead like to specify a MySite host site collection and the managed path at which personal sites will be created. Again, this is ONLY required if you did not specify a dedicated MySite host web application earlier in the XML."
Daniel
↧

Commented Unassigned: Access Denied at Site Collection, 0x80070005 [20065]

December 31, 2014, 1:29 pm
$
0
0
Title actually says it all already. I'm trying to do the automatic installation and I'm stuck at that point now since I must create a Site Collection.

Errorcode: 0x80070005

Does anyone have an idea how to fix this? I tried using any account for SharePoint. I even tried the local System Administrator.

WRONG IMAGE BELOW.
Comments: ** Comment from web user: ndrepebx **

Hi

I had the same issue and it turned out to be the Firewall. Disabled the firewall during the install and then it worked fine. Ports 22233,22234,22235 and 22236. need to be opened for the distributed cache.

↧
↧

New Post: Enable SSL on SharePoint 2013 HNCs

January 5, 2015, 2:30 am
$
0
0
Happy New Year to your all....

One thing to note. When you get AutoSPInstaller to auto create a SSL certificate. You need to ensure that certificate is exported to the all the other servers such as your office web apps server. We found we had certificates with the same domain scattered around our farm caused some cert related errors. For example when I attempt create a new word document in a lib hosted in one of my HNSCs I get:

Content was blocked because it was not signed by a valid security certificate.


__
For more information, see “About Certificate Errors” in Internet Explorer Help.__


Our live cert arrived so we're in the process of exporting this to the various servers but we could do the same with the temp self-cert.


Daniel
@westerdaled
↧

Source code checked in, #112238

January 5, 2015, 7:26 am
$
0
0
Changes in this release: - Updated script version and XML schema to 3.98 - please ensure you compare and update your old XML files! - Initial support for SharePoint Foundation (yes, finally), including checks throughout for service apps / commands that aren't supported in SPF - Removed some old commented code - Broadened search strings for updates to install to include sharepointsp2013*.exe,coreserver201*.exe - Significant update to Enterprise Search service app in that it now leverages the ShouldIProvision function to determine which servers to provision which Search components on. This brings it in line with every other service app in AutoSPInstaller. - Added ability to continue script if connection to SQL server fails, e.g. if we know SQL hasn't been provisoned yet but we just want to install binaries on the SharePoint farm servers first
↧

New Post: Install of SP2013 failing...

January 5, 2015, 9:45 am
$
0
0
Hi,

In the event that this may help somebody else out. If you are trying to use Windows Server 2012 R2, it may not be clear that you need to use the SharePoint Server 2013 SP1 install bits (specfically for the updated prerequisites installer). Since I have existing 2013 farms, I tried to build a Development environment in Azure and I tried to use my slipstreamed installer bits which weren't SP1.

HTH,
Cory
↧
Viewing all 2279 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>