Archive

Archive for the ‘Setup’ Category

Loopback Check configuration Tool released – free download

December 12, 2013 Leave a comment

Win2012  logo  SharePoint2013Logo70x338

Hi All.

It is here! Free for all! DOWNLOAD

I am happy to announce that the Loopback Check Tool has finally been made available at Codeplex – https://loopbackchecktool.codeplex.com
No more last minute t-shooting the loopback check and ending up disabling it, trying to find the KB or a decent blog post on how to do it.

This Tool takes care of it all for you. Download the exe, put it on your servers, run it to configure the Loopback Check feature simple and easy.

Its simple.
Its small (21kb zipped)
Only click and make it happen
No installation, one single exe that works on most Windows Servers (and clients)
Disable the Loopback check completely (Not recommended)
Enable or Disable the Loopback Check function
Enable it and add excluded URLs (Recommended, now easy to do)

This is a preview image of what the tool looks like

Form

The tool works fine on:

Windows Server 2012
Windows Server 2012 R2
Windows Server 2008 R2
Windows Server 2008
Windows 7
Windows 8
Windows 8.1
And probably a few more…

References:

You receive error 401.1 when you browse a Web site that uses Integrated Authentication and is hosted on IIS 5.1 or a later version
http://support.microsoft.com/kb/896861/en-us

A quick guide to configuring the Loopback check
http://blog.blksthl.com/2013/05/07/a-quick-guide-to-configuring-the-loopback-check/

DisableLoopbackCheck & SharePoint: What every admin and developer should know.
http://www.harbar.net/archive/2009/07/02/disableloopbackcheck-amp-sharepoint-what-every-admin-and-developer-should-know.aspx

Thanks to:

Herakles and Gutke!

Win2012  logo  SharePoint2013Logo70x338

___________________________________________________________________________________________________

Enjoy!

Regards

Twitter | Technet Profile | LinkedIn

Create a bootable Windows Server 2012 R2 installation USB flash drive

October 18, 2013 6 comments

2012R2 logo

Hi Windows connoisseurs! (wiki)

(This is essentially a remake of my Create a bootable Windows 8.1 installation USB flash drive post.) The setps are the same so you can easily follow that post or use this slightly updated version.

In this guide I will help you find a way to install Windows Server 2012 R2 quick and easy, from a simple USB flash drive. It’s really easy, but you still need to Think about a few things.
I’ll list them here and if you want, you can follow the step by step guide below.

Quicksteps:

1. Get a USB Flash drive formatted with FAT32, it has to be AT LEAST 8GB! (The Windows Server 2012R2 installation bits will not fit on a 4GB USB drive…)
2. Download and install the Windows 7 USB/DVD Download tool from Microsoft Store here or Codeplex here  (It is an official Microsoft tool, totally wierdly named from the Windows 7 release but still very much valid!)
3. Download or locate a ‘Windows Server 2012 R2′ .iso file and store it locally on your harddrive.
4. Start the Windows 7 USB/DVD Download tool (from startbutton or ‘windows 8/Metro’ style startmenu’?)
5. Complete the steps 1-4
6. Insert the USB flash drive into the powered off PC to install, Power on and boot from USB drive (F9 at HP logo on HP Machines).
7. Install Windows Server as you would normally.
8. Done!

This guide in its entirety works just as well if you replace the Windows Server 2012 R2 .iso file with Windows 8.1, Windows 7, Windows Server 2012 or plain Windows 8 (Windows Server 2008 R2 not verified but willmost likely also work)

Step by step:

1. USB Flash Drive

Prepare a USB flash drive for installation, is has to be at least 8 GB in size and it has to be formatted with FAT32. It does not have to be erased, the tool will do that for you if needed.

USB

Before

2. Download and install the Windows 7 USB/DVD Download tool from Microsoft Store or Codeplex. The Links are as follows:

http://images2.store.microsoft.com/prod/clustera/framework/w7udt/1.0/en-us/Windows7-USB-DVD-tool.exe
or
http://wudt.codeplex.com

Run the .exe file, you will have to be a local administrator on your machine for it to install properly.

1

Click Next

2

Click Install

3

Click Finish

3. Locate a Windows Server 2012 R2 .iso file. This file should be placed on a local harddrive. It does not matter where you put it, as long as it is on a local HD and it is accessable to you when running the tool, meaning that you have access to where the file is stored in the filesystem.

4. After the installation of the tool has completed, you will suddenly notice this tile:

MetroIcon

You can also just use the search function, in ‘metro mode’ simply type Windows 7 and you will see it and its uninstall app.
Start the tool
Click Ok at the User Account Control popup dialog
The first screen should now look like this:

ChooseISO

5. Hit the Browse button to locate your Windows Server 2012 R2 installation iso file.

Step1

In my test, I’m using an .iso file downloaded from TechNet Subscriber downloads (soon to be no more)
It does not have to be from TechNet, it can be MSDN or Volume Licensing or really any form of Windows Server 2012 R2 installation iso.

Click ‘Next’

Step2ChooseMedia

Click on ‘USB device’
If you see the window below, that means that the USB drive is either not plugged in properly, or it has the wrong formatting or insufficient storage or similar. Make sure that you have a USB flash drive that meets: 4GB minimum+FAT32.

Step2ChooseMediaNoUSB

Insert a USB drive that meets the requirements and press the refresh button
Now, click on the ‘Begin copying’ button.

If the USB drive was ok, the copying will begin, but if not, if it still had files still on it, you will see this dialog:

Erase1

Click Erase to continue

Erase2

Click Yes and the formatting and copying process will begin.

Step4

Step42

Let it do its thing until it reaches 100%

When it has finished formatting and copying files, you are done.

USB

After!

6. Next step, is to insert the USB drive into the PC you want to install Windows Server 2012 R2 on, Power it off completely and Power on again.
Use BIOS settings to select ‘boot from USB’ or like on a HP machine, hit F9 at the HP logo screen to boot directly from USB.

7. Let the Installation begin! The Windows installation is pretty much standard. A Clean install is described here.  The setup of Windows 8, which is pretty much the same, is described here

8. Done!

References:

Install and Deploy Windows Server 2012 (R2)
http://technet.microsoft.com/en-us/library/hh831620.aspx

Thanks to:

Herakles and Gutke!

2012R2 logo

___________________________________________________________________________________________________

Enjoy!

Regards

Twitter | Technet Profile | LinkedIn

Create a bootable Windows 8.1 installation USB flash drive

October 8, 2013 12 comments

win8.1logo

Hi Windows Lovers!?

(Looking to install Windows Server? The same steps apply, but for a server specific guide, go here Create a bootable Windows Server 2012 R2 installation USB flash drive)

This time I’ll help you find a way to install Windows 8.1 quick and easy, from a simple USB flash drive. It’s a piece of cake really, but a few things you need to know about.
I’ll list them here and if you want, you can follow the step by step guide below.

Quicksteps:

1. Get a USB Flash drive formatted with FAT32, it has to be AT LEAST 4GB!
2. Download and install the Windows 7 USB/DVD Download tool from Microsoft Store HERE or Codeplex HERE  (It is an official Microsoft tool, totally wierdly named from the Windows 7 release but still very much valid!)
3. Download or locate a ‘Windows 8.1′ .iso file and store it locally on your harddrive.
4. Start the Windows 7 USB/DVD Download tool (from startbutton or ‘windows 8 style startmenu’?)
5. Complete the steps 1-4
6. Insert the USB flash drive into the powered off PC to install, Power on and boot from USB drive (F9 at HP logo on HP Machines).
7. Install Windows as you would normally.
8. Done!

This guide in its entirety works just as well if you replace the Windows 8.1 .iso file with Windows 7, Windows Server 2012 or plain Windows 8 (Windows Server 2008 R2 not verified but willmost likely also work)

Step by step:

1. USB Flash Drive

Prepare a USB flash drive for installation, is has to be at least 4 GB in size and it has to be formatted with FAT32. It does not have to be erased, the tool will do that for you if needed.

USB

Before

2. Download and install the Windows 7 USB/DVD Download tool from Microsoft Store or Codeplex. The Links are as follows:

http://images2.store.microsoft.com/prod/clustera/framework/w7udt/1.0/en-us/Windows7-USB-DVD-tool.exe
or
http://wudt.codeplex.com

Run the .exe file, you will have to be a local administrator on your machine for it to install properly.

1

Click Next

2

Click Install

3

Click Finish

3. Locate a Windows 8.1 .iso file. This file should be placed on a local harddrive. It does not matter where you put it, as long as it is on a local HD and it is accessable to you when running the tool, meaning that you have access to where the file is stored in the filesystem.

4. After the installation of the tool has completed, you will suddenly notice this tile:

MetroIcon

You can also just use the search function, in ‘metro mode’ simply type Windows 7 and you will see it and its uninstall app.
Start the tool
Click Ok at the User Account Control popup dialog
The first screen should now look like this:

ChooseISO

5. Hit the Browse button to locate your Windows 8.1 installation iso file.

ChooseISO2

In my test, I’m using an .iso file downloaded from TechNet Subscriber downloads (soon to be no more)
It does not have to be from TechNet, it can be MSDN or Volume Licensing or really any form of Windows 8.1 installation iso.

Click ‘Next’

Step2ChooseMedia

Click on ‘USB device’
If you see the window below, that means that the USB drive is either not plugged in properly, or it has the wrong formatting or insufficient storage or similar. Make sure that you have a USB flash drive that meets: 4GB minimum+FAT32.

Step2ChooseMediaNoUSB

Insert a USB drive that meets the requirements and press the refresh button
Now, click on the ‘Begin copying’ button.

If the USB drive was ok, the copying will begin, but if not, if it still had files still on it, you will see this dialog:

Erase1

Click Erase to continue

Erase2

Click Yes and the formatting and copying process will begin.

Step4

Step42

Let it do its thing until it reaches 100%

When it has finished formatting and copying files, you are done.

USB

After!

6. Next step, is to insert the USB drive into the PC you want to install Windows 8.1 on, Power it off completely and Power on again.
Use BIOS settings to select ‘boot from USB’ or like on a HP machine, hit F9 at tghe HP logo screen to boot directly from USB.

7. Let the Installation begin! The Windows installation is pretty much standard. A Clean install is described here.  The setup of Windows 8, which is the same, is described here

8. Done!

References:

Thanks to:

As Always, Mattias Gutke! At CAG for some strange reason….Always a friend, a great help and a second opinion!

GetItNow
___________________________________________________________________________________________________

Enjoy!

Regards

Twitter | Technet Profile | LinkedIn

Move your SharePoint IIS sites from the systemdrive(C:)

August 31, 2013 3 comments

Move your SharePoint IIS sites from the systemdrive(C:)
or avoid putting them there in the first Place.

Lionx

Do you see the lion that is totally in the wrong Place…or is it the Jeeps that are…?

Deal fellow SharePointlovers!

This time, I’ll try to show you how to avoid the messed up situation most SharePoint installations are in, with everything on the systemdrive, or C:
Now, us people have over time been better and better at one thing, we understand that the logfiles should not be located on the systemdrive, so we have learned over time to move the ULS log and the Usage and Health log from C:, some have even been clever enough to move even the IIS log from C:

But, what do we still always, always, always, find installed on C:?… … …yes, C:\inetpub!

It not very strange though, the developers of Windows Server have made a point out of not giving us an option to install inetpub on a different path, not unless you do an unattended installation or otherwise script or Control your installation. The ‘Add/Remove roles’ wizards in Server 2008, 2008R2 and 2012 all lack this option (for a reason).

BUT! This is intentially, the default inetpub location should and must be in the systemdrive, IIS is considered an operating system Component and has to be there for a number of reasons. At the end you will find a link to a KB article that explains this in more detail. Leave inetpub and its subfolders where it is!

So, why would we want to do this anyway
why move the inetpub and all of its content, or at least the separate site catalogs to a different drive?
- Separation (Performance and Security)
- Compartmentalization (Performance and Security)
Having averything on the same drive is bad for a few reasons, primarily performance and security. Perfomance since the OS is on the C drive and security because if an attacker by some means gets access to a different less secure applications sitecatalog, they also get access to the systemdrive and possible also all other webapplication sitecatalogs. Moving them to other drives, same or different, helps mitigate both possible issues.
I therefore recommend doing this:

Do your regular installation, add the Web Server role and let the inetpub folder end up on C:, like I said, no worries. Whats important for us will not be located there anyway.
Next, edit the registry to make the default location of inetpub be for example D: (unless this is were you will be putting all of your logfiles, then select a third or fourth drive)
Install the SharePoint as you would normally do, Central administration will now end up were you pointed the default location.
Create your Web Applications using the GUI or PowerShell and leave out the path, the IIS sites will be were you wanted them.

So, how do we do this in more detail? A Guide…

Configure the Web Server(s)

1. Configure the default location

On all of your web servers in the farm, and on your Central Administration server(s), edit the registry key that Controls the default location:

Start regedit by, Right clicking in the very lower left corner and you will get a list of actions, click on Run.

Reg1x

Type Regedit and click Ok.

Reg2x

Click Yes in the UAC dialog.

Reg3

In Registry Editor, we locate the following path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\InetStp

Reg4x

Reg5x

Under ‘InetStp’ we have a number of keys.

Reg6x

Locate and Edit the key PathWWWRoot from the default: (%systemdrive%)

Regbeforex

to: (D: or where you prefer to locate it, E: F: G: H:…)

Regafterx

There you go! All set, no IIS reset or restarts of any kind required.
Like said before, go on and do this on all servers that will host a webserver (WFE or CA). If you don’t, then you will have an inconsistent setup making Everything very hard to setup and t-shoot.

2. Add SharePoint
After this has been changed on all of you r web servers, you can go ahead and install the SharePoint binaries and configure your farm, The Central Administration site will now be located on the drive you have specified, it will be in the exact same path as it normally would but on a different drive. For example: ‘D:\inetpub\wwwroot\wss\VirtualDirectories\20000\’

Note that the Central Administration UI will now be default suggest a different path:

NewWeb1x

If you create a new site using PowerShell, it will also by default put it in D: even if you don’t specify any path:

New-SPWebApplication -Name TheVeryFirst -ApplicationPool SharePoint -HostHeader theveryfirst.corp.balkestahl.se -Port 80 -Url theveryfirst.corp.balkestahl.se -DatabaseServer blksthl-sql -DatabaseName SP11_Content_TheVeryFirst

As you can see, were done! :-)

Donex

For the logfiles, I’ll make a separate post, they should also be moved, more so even than the sitefolders. Logfiles will fill up the disks, they will slow performance and maybe most importantly, they contain delicate information that you want to keep separated from the OS and IIS.

References:

Guidance for relocation of IIS 7.0 and IIS 7.5 content directories
http://support.microsoft.com/kb/2752331

Configure ULS log and Usage and Health log location
http://blog.blksthl.com/2013/06/05/configure-uls-log-and-usage-and-health-log-location/

Thanks to:

Mikael Nyström (The Deployment Bunny) - Truesec
Mattias Gutke – CAG


___________________________________________________________________________________________________

Good Luckl!!

Regards

Twitter | Technet Profile | LinkedIn

Hardware requirements for all SharePoint 2013 components summarized

November 19, 2012 2 comments


Update 2013-01-28 - New note added : Certain Installation Scenarios not supported


-

Listed below are all of the Hardware requirements that have been announced for SharePoint 2013 and it’s connected services and products.
Covered in the list are, in this order:

 SharePoint_logo_small  SharePoint Forundation 2013
 SharePoint_logo_small  SharePoint Server 2013
 Office_logo_small  Office Web Applications 2013
 Project_logo_small  Project Server 2013
 SQL_logo_small  SQL Server 2012 Reporting Services in Integrated mode
 SQL_logo_small  SQL Server 2012 PowerPivot
 SQL_logo_small  SQL Server 2012 Analysis Services Server
 blksthl_B_small  Reference links


-
-
-

Note: In addition to the listed HW requirements below, note that certain Microsoft SharePoint Server 2013 installation scenarios are not supported
Not supported are: Dynamic Memory, ReFS(Resilient File system), Install on a DC, Install in a Workgroup, Install on Windows Web Server.

see Microsoft KB: http://support.microsoft.com/kb/2764086

-

-

SharePoint Foundation 2013                 Deployment type and scale                 RAM                 Processor                 Hard disk space
Single server with a built-in database or single server that uses SQL Server Development or evaluation installation of SharePoint Foundation 2013 8 GB 64-bit, 4 cores 80 GB for system drive
Web and application server in a two-tier farm Pilot, user acceptance test, or production deployment of SharePoint Foundation 2013 8 GB 64-bit, 4 cores 80 GB for system drive
database servers in a two-tier farm Pilot, user acceptance test, or production deployment of SharePoint Foundation 2013 8 GB 64-bit, 4 cores 80 GB for system drive

Back to table of contents
-

-

-

SharePoint Server 2013 Deployment type and scale RAM Processor Hard disk space
Single server with a built-in database or single server that uses SQL Server Development or evaluation installation of SharePoint Server 2013 24 GB 64-bit, 4 cores 80 GB for system drive
Web server or application server in a three-tier farm Pilot, user acceptance test, or production deployment of SharePoint Server 2013 12 GB 64-bit, 4 cores 80 GB for system drive
database servers in environments that have multiple servers in the farm/multi tier Small deployments 8 GB 64-bit, 4 cores 80 GB for system drive
database servers in environments that have multiple servers in the farm/multi tier Medium deployments 16 GB 64-bit, 8 cores 80 GB for system drive
database servers in environments that have multiple servers in the farm/multi tier Large deployments See link See link See link

Back to table of contents
-

-

-

Office Web Applications 2013 Deployment type and scale RAM Processor Hard disk space
Office Web Apps server Development or evaluation installation of Office Web Apps 8 GB 64-bit, 4 cores 80 GB for system drive
Office Web Apps server Pilot, user acceptance test, or production deployment of Office Web Apps 12 GB 64-bit, 4 cores 80 GB for system drive

Back to table of contents
-

-

-

Project Server 2013, Small dataset scenario Deployment type and scale RAM Processor Hard disk space
Minimum requirement, single–server deployment Development or evaluation installation of Project Server 2013 24 GB 64-bit, 4 cores 80 GB for system drive
Front-end web and Application server hardware Development or evaluation installation of Project Server 2013 8 GB 64-bit, 4 cores 80 GB for system drive
Front-end web and Application server Pilot, user acceptance test, or production deployment of Project Server 2013 16 GB 64-bit, 4 cores 80 GB for system drive
Database server Pilot, user acceptance test, or production deployment of Project Server 2013 16 GB 64-bit, 4 cores 80 GB for system drive

Back to table of contents
-

Project Server 2013, Medium dataset scenario Deployment type and scale RAM Processor Hard disk space
Minimum requirement, front-end web server Development or evaluation installation of Project Server 2013 8 GB 64-bit, 4 cores 80 GB for system drive
Minimum requirement, application server Development or evaluation installation of Project Server 2013 8 GB 64-bit, 4 cores 80 GB for system drive
Minimum requirement, database server Development or evaluation installation of Project Server 2013 16 GB 64-bit, 4 cores 100 GB for system drive
Recommended, front-end web server Pilot, user acceptance test, or production deployment of Project Server 2013 16 GB 64-bit, 4 cores 80 GB for system drive
Recommended, application server Pilot, user acceptance test, or production deployment of Project Server 2013 16 GB 64-bit, 4 cores 100 GB for system drive
Recommended, database server Pilot, user acceptance test, or production deployment of Project Server 2013 32 GB 64-bit, 8 cores 160 GB for system drive
Note: Ideally, you should separate and prioritize data among disks. Place your data files and your SQL Server transaction logs on separate physical hard disks. RAID 5 should provide a good compromise between reliability, and throughput.

Back to table of contents
-

Project Server 2013, Large dataset scenario Deployment type and scale RAM Processor Hard disk space
Recommended, front-end web server Pilot, user acceptance test, or production deployment of Project Server 2013 16 GB 64-bit, 4 cores 80 GB for system drive
Recommended, application server Pilot, user acceptance test, or production deployment of Project Server 2013 16 GB 64-bit, 4 cores 100 GB for system drive
Minimum requirement, database server Pilot, user acceptance test, or production deployment of Project Server 2013 32 GB 64-bit, 4 cores 250 GB for system drive
Recommended, database server Pilot, user acceptance test, or production deployment of Project Server 2013 64 GB 64-bit, 8 cores 300 GB or more
Note: Ideally, you should separate and prioritize data among disks. Place your data files and your SQL Server transaction logs on separate physical hard disks. RAID 5 should provide a good compromise between reliability, and throughput.

Back to table of contents
-

-
-

SQL Server 2012 Reporting Services, SharePoint Integrated mode Deployment type and scale RAM Processor Hard disk space
Reporting Services 2012 Add-on Must be Installed on a SharePoint Server 2013 Web Server 12 GB 64-bit, 4 cores 80 GB for system drive
Reporting Services 2012 Service Application Must be Installed on a SharePoint Server 2013 Application Server 12 GB 64-bit, 4 cores 80 GB for system drive

Back to table of contents
-

-

-

PowerPivot in SharePoint Mode Deployment type and scale RAM Processor Hard disk space
Standalone PowerPivot for SharePoint 2013 server that is not part of the SharePoint farm Minimum requirement 8 GB 64-bit, 2 cores 80 GB or more
Standalone PowerPivot for SharePoint 2013 server that is not part of the SharePoint farm Recommended 64 GB 64-bit, 16 cores 80 GB or more

Back to table of contents
-

-

-

SQL Server 2012 SP1 Analysis Server in SharePoint mode Deployment type and scale RAM Processor Hard disk space
SQL Server 2012 SP1 Analysis Server in SharePoint mode Runs outside a SharePoint 2013 farm SQL, see link SQL, see link SQL, see link

Back to table of contents

-

-
References:

Software, hardware, and configuration requirements for Office Web Apps Server
http://technet.microsoft.com/en-us/library/jj219435.aspx#software

Hardware and software requirements for SharePoint 2013
http://technet.microsoft.com/en-us/library/cc262485(v=office.15)#hwforwebserver

Hardware and software requirements for Project Server 2013
http://technet.microsoft.com/en-us/library/ee683978

Hardware and Software Requirements for Reporting Services Server in SharePoint Mode for SharePoint 2013
http://msdn.microsoft.com/en-us/library/jj714188.aspx

Hardware and Software Requirements for Analysis Services Server in SharePoint Mode (SQL Server 2012 SP1)
http://msdn.microsoft.com/en-us/library/fb86ca0a-518c-4c61-ae78-7680c57fae1f

Hardware and Software Requirements for Installing SQL Server 2012
http://msdn.microsoft.com/en-us/library/09bcf20b-0a40-4131-907f-b61479d5e4d8

Certain Microsoft SharePoint Server 2013 installation scenarios are not supported
http://support.microsoft.com/kb/2764086

Use best practice configurations for the SharePoint 2013 virtual machines and Hyper-V Environment
http://technet.microsoft.com/en-us/library/ff621103.aspx

I know I will use this to make my life easier until I get it all memorized…I hope that it may help you as well. Any feedback or recommended additions to the tables will be appreciated.
Back to table of contents

_________________________________________________________

Enjoy!

Regards

Twitter | Technet Profile | LinkedIn

Passphrases in SharePoint- why do we bother?

September 26, 2012 1 comment

You all know about the passphrase in SharePoint (2010 and later) right? You name it during farm Creation using Powershell or the Config Wizard. It must be a complicated string of characters and it has to hold a certain length (exact requirements stated below)

Do we really need it?

Since you can replace the passphrase (Change your PassPhrase using PowerShell) without having the old one, all you need is to be a member of the farm administrators SharePoint Group. So…the use of the PassPhrase is what? You don’t need to save it since all you have to do when it is required (join farm) is to change it…and if you have the passphrase, you still have to enter the farm account (Database Access Account) username and password, so you still need the permissions…

The Passphrase in SharePoint 2013 Preview is described as:
(From the ‘Deployment guide for Microsoft SharePoint 2013 Preview’)
Although a passphrase resembles a password, it is usually longer to improve security. It is used to encrypt credentials of accounts that are registered in SharePoint 2013 Preview. For example, the SharePoint 2013 Preview system account that you provide when you run the SharePoint Products Configuration Wizard. Ensure that you remember the passphrase, because you must use it every time that you add a server to the farm.

Ensure that the passphrase meets the following criteria:

  • Contains at least eight characters
  • Contains at least three of the following four character groups:
    • English uppercase characters (from A through Z)
    • English lowercase characters (from a through z)
    • Numerals (from 0 through 9)
    • Nonalphabetic characters (such as !, $, #, %)

So…now that you have read all this, do we really need it? Why bother? Is it one more layer of real security or more more layer of persieved security?

-It’s easily replaced/reset (see Change your PassPhrase using PowerShell)
-You still need the farmaccount credentials to join
-It’s seldom used and thus easily lost (in real life! yes)
-For the encryption purposes, SharePoint could use a random key that you never have to see or know about…
_________________________________________________________

Please Comment!

Regards

Twitter | Technet Profile | LinkedIn

Change your PassPhrase using PowerShell

September 12, 2012 1 comment

Changing the Farm’s PassPhrase, is it difficult and something that canb possible screw Everything up? Or is it an easy and pretty trival task?

I’d say the latter, changing it is easy, what is important and hard, is to make sure that dokumentation and possibly secure stores and such are updated to reflect the change. Remember, as long as you have at least one SharePoint server still connected/joined to the farm, you can Always reset the PassPhrase again. It’s when you have a single Config Database without a single server that you really really want to have the PassPhrase documented and in order.

So, how to do it practically? There is really only one way, and that is using PowerShell:

Open a PowerShell Prompt as Administrator.
Load the SharePoint Module:

Add-PSSnapin Microsoft.SharePoint.PowerShell

Enter this at the PowerShell prompt:

$passphrase = ConvertTo-SecureString -asPlainText -Force

Input the new passphrase and hit Enter


Enter this at the PowerShell prompt:

Set-SPPassPhrase -PassPhrase $passphrase -Confirm

You will be asked to confirm the passphrase by re-entering it in cleartext
Re-enter the passphrase and hit Enter
You will be asked if you are sure that you want to perform this action, type Y (for Yes) and hit Enter


Your farm passphrase has now been reset!

Next time, use the new PassPhrase when joining the farm.

!! And remember to update any documentation !!

Why I had to do this now? Well, this is, I’m currently helping a customer setting up Resporting Services for SharePoint, that requires an extra server joined to the farm with SSRS and SP installed on them. I installed the server and added all the SP’s and LP’s and CU’s and soon, until we were good to go to join it into the farm. Now, I got prompted for the PassPhrase…hmm. This farm was setup some time ago by a different firm and they are not around anymore…
My customer sent me the documentation on the farm setup but no luck. The PassPhrase was forgotten and gone…
So, instead of panicking and screaming for a complete reinstall, I started to look for the way to retrieve it or reset it. Turns out, you can reset it but never retrieve it. You must have one server still in the farm to be able to reset it, this server is wehere you run the Powershell commands from.

So, now my PassPhrase is reset, I quickly added it to textfile on the server and also emailed it to my customer. Later, I will also add it to the Farm documentation for future reference.

_________________________________________________________

Enjoy!

Regards

Twitter | Technet Profile | LinkedIn

Installing Cumulative updates – current best practice

November 17, 2011 Leave a comment

This is not brand new info, but I think it is important enough to mention again. Huge improvement!

Just a repeat on the current(August 31, 2011) best practice:

Updates for SharePoint 2010 Products
http://technet.microsoft.com/en-us/sharepoint/ff800847

Best practice

The packaging of cumulative updates changed as of August 31, 2011. The following packages are provided for cumulative updates:

  • SharePoint Foundation 2010
  • SharePoint Foundation 2010 + SharePoint Server 2010
  • SharePoint Foundation 2010 + SharePoint Server 2010 + Project Server 2010

As a result of the new packaging, it is no longer necessary to install the SharePoint Foundation cumulative update and then install the SharePoint Server cumulative update.

Previously, the recommendation was to install first foundation, then server, then project if you had project server installed. What this means is that you no longer have to do all of them, just the package that contains all of your updates. If you are running server, install the server package only. (these packages have before been called Überpackages, they are now ‘reinstated’)

Happy patching

SharePoint prerequisites, this is how you do it!

October 18, 2011 2 comments

This post will cover most of what you need to know about the prerequisites of SharePoint Server 2010.
There are a few tricks to it that can help you out, there are a few things never before documented…and there are links that need to be collected into one place.
That, is what will show up in this post eventually…

Adding the obvious starting point for now, this is an absolute must before starting to fiddle with alternate ways of installing the prerequisites:
Install prerequisites from a network share (SharePoint Server 2010)
http://technet.microsoft.com/en-us/library/ff686793.aspx

Finding them and Collecting them:
All of the requirements needed for a successful installation of SharePoint Server 2010 or SharePoint Foundation 2010 are listed in the technet article:
Hardware and software requirements (SharePoint Server 2010)
http://technet.microsoft.com/en-us/library/cc262485.aspx

There is a full set of prerequisites that have to be on the servers before installing the SharePoint binaries.
IIS:
Server (IIS) role
Application Server role
Add-ons:
Microsoft .NET Framework version 3.5 SP1
SQL Server 2008 Express with SP1
Microsoft Sync Framework Runtime v1.0 (x64)
Microsoft Filter Pack 2.0
Microsoft Chart Controls for the Microsoft .NET Framework 3.5
Windows PowerShell 2.0
SQL Server 2008 Native Client
Microsoft SQL Server 2008 Analysis Services ADOMD.NET
ADO.NET Data Services Update for .NET Framework 3.5 SP1
Windows Identity Foundation (WIF) (If the Geneva framework is previouisly installed, it needs to be uninstalled before WIF is installed)
(A hotfix for the .NET Framework 3.5 SP1 that provides a method to support
token authentication without transport security or message encryption in WCF.)
For Windows Server 2008 SP2, download the Windows6.0-KB979917-x64.msu (Vista) file.
For Windows Server 2008 R2, download the Windows6.1-KB979917-x64.msu (Win7) file.
The prerequisites installer will take care of it for you in most cases, but in a controlled environment you do not want everyserver to download every package from the internet.
Either you have full access to internet when setting up your server nd don’t care about downloading them over and obver, then there is no real need to download the files separately or even know here to find them. But, if you are looking for a way to install from local files, then this is the way, use the script download.ps1 at the end of this post to down load all of the prereqs to a specified subfolder, name it PrerequisiteInstallerFiles and you can use the installer script as well.

If you don’t want to run the script, collect the prerequisites one by one:

http://download.microsoft.com/download/C/9/F/C9F6B386-824B-4F9E-BD5D-F95BB254EC61/Redist/amd64/Microsoft%20Sync%20Framework/Synchronization.msi
http://go.microsoft.com/fwlink/?LinkID=141237&clcid=0×409
Microsoft Sync Framework Runtime v1.0 (x64)

http://download.microsoft.com/download/c/c/4/cc4dcac6-ea60-4868-a8e0-62a8510aa747/MSChart.exe
http://go.microsoft.com/fwlink/?LinkID=141512
Microsoft Chart Controls for the Microsoft .NET Framework 3.5

http://download.microsoft.com/download/2/0/e/20e90413-712f-438c-988e-fdaa79a8ac3d/dotnetfx35.exe
http://go.microsoft.com/fwlink/?LinkId=131037
Microsoft .NET Framework 3.5 Service Pack 1

http://download.microsoft.com/download/2/8/6/28686477-3242-4E96-9009-30B16BED89AF/Windows6.0-KB968930-x64.msu
http://download.microsoft.com/download/2/8/6/28686477-3242-4E96-9009-30B16BED89AF/Windows6.0-KB968930-x64.msu
Windows PowerShell 2.0

http://download.microsoft.com/download/D/7/2/D72FD747-69B6-40B7-875B-C2B40A6B2BDD/Windows6.1-KB974405-x64.msu
http://go.microsoft.com/fwlink/?LinkID=166363
Windows Identity Framework (Win2008 R2)

http://download.microsoft.com/download/6/8/1/681F5144-4092-489B-87E4-63F05E95079C/Windows6.0-KB976394-x64.msu
http://go.microsoft.com/fwlink/?linkID=160770
WCF fix for Win2008 SP2

http://download.microsoft.com/download/E/C/7/EC785FAB-DA49-4417-ACC3-A76D26440FC2/Windows6.1-KB976462-v2-x64.msu
http://go.microsoft.com/fwlink/?LinkID=166231
WCF fix for Win2008 R2

http://download.microsoft.com/download/D/7/2/D72FD747-69B6-40B7-875B-C2B40A6B2BDD/Windows6.0-KB974405-x64.msu
http://go.microsoft.com/fwlink/?LinkID=160381
Windows Identity Framework (Win2008 SP2)

http://download.microsoft.com/download/3/5/5/35522a0d-9743-4b8c-a5b3-f10529178b8a/sqlncli.msi
http://go.microsoft.com/fwlink/?LinkId=123718&clcid=0×409
SQL Server 2008 Native Client

http://download.microsoft.com/download/b/9/a/b9a78047-d269-4a25-88a1-9c4321d90677/SQLSERVER2008_ASADOMD10.msi
http://go.microsoft.com/fwlink/?LinkId=130651&clcid=0×409
Microsoft SQL Server 2008 Analysis Services ADOMD.NET

http://download.microsoft.com/download/1/7/1/171CCDD6-420D-4635-867E-6799E99AB93F/ADONETDataServices_v15_CTP2_RuntimeOnly.exe
http://go.microsoft.com/fwlink/?LinkId=158354
ADO.NET Data Services v1.5 CTP2 (Win2008 SP2)

http://download.microsoft.com/download/B/8/6/B8617908-B777-4A86-A629-FFD1094990BD/iis7psprov_x64.msi“,
http://go.microsoft.com/?linkid=9655704
IIS management cmdlets

http://download.microsoft.com/download/1/0/F/10F1C44B-6607-41ED-9E82-DF7003BFBC40/1033/x64/rsSharePoint.msi
http://go.microsoft.com/fwlink/?LinkID=166379
SQL 2008 R2 Reporting Services SharePoint 2010 Add-in

http://download.microsoft.com/download/8/D/F/8DFE3CE7-6424-4801-90C3-85879DE2B3DE/Platform/x64/SpeechPlatformRuntime.msi
http://go.microsoft.com/fwlink/?LinkID=166378
Microsoft Server Speech Platform Runtime

http://download.microsoft.com/download/E/0/3/E033A120-73D0-4629-8AED-A1D728CB6E34/SR/MSSpeech_SR_en-US_TELE.msi
http://go.microsoft.com/fwlink/?LinkID=166371
Microsoft Server Speech Recognition Language – TELE(en-US)

Or you can create and run the script download.ps1 mentioned at the bottom of this post. This will put all of the requirement add-on’s into one folder to be used during intall.
For the server roles to be added and configured no extra software is needed.

Applying them:

Ok, to install and apply all of the prerequisites you can choose one out of several options.

Online.
Online will be the simplest way to install the prerequisites, perhaps in a lab or test environemnt, on a single server, but in a real scenario, perhaps not.

Online 1.
Install manually…I guess this is an option but I can’t think of why you would want to…pick the roles you need manually and install them, install all of the add-ons one by one…
This is not a good or safe way to do it, but possible.

Online 2.
The absolutely simplest way, no major braining needed, execute the PrerequisitesInstaller.exe. Done!
It can be that simple…and it usually is. The prerequisites installer is one of the best little helpers you have ever seen, thank you Microsoft for this. It collects all the software and installs them all into the right place. This works…if you are only installing one server, and you have a fast internet connection, and your server is connected to Internet, and you enjoy not having full control…
Normally, if you are installing a single server environment and the server is fully connected to the Internet and all is swell, run the PrerequisitesInstaller and let it fix up the server for you. (For all other scenarios, I would have a look at the Offline section below.)
But, what if you were…offline…

Offline.
Offline is a completely different matter. The PrerequisitesInstaller.exe is still a great tool and you will want to use it, but you need to do some thinking first. How will the Installer get the files it needs to install if it can’t download them from the internet?

Offline 1.
Run the prerequisitesinstaller with an Arguments file in order to use the add-on files you have downloaded.
Create a textfile, name it PrerequisitesInstaller.Arguments.txt (Important! this has to be exactly right) and paste the second scripttext located at the end of this post.

Offline 2.
Create and run a script that will do it all for you, add the roles, use the local files….
This is a pretty good solution, it will be the same every time and you will only download the files once. The indiciduals installing SharePoint can only be told to run a script that does it all.
In order to do this, you can create a textfile, name it installPrerequisitesFromShare.ps1 and paste the code under InstallPrerequisitesFromFileshare.ps1 at the bottom of the post. This script assumes that you have all of the requirements in one folder located in a subfolder named PrerequisiteInstallerFiles. This method works very well and will install it all for you, you will only have to execute one powershellscript and it will install it all, roles, add-ons and all.

What if:

You uninstall SharePoint from the server, what then?

I will try to ad dmore value here later, but I can say one thing for certain now, uninstall SharePoint and the RSservice will be broken. The Resporting services add on for SharePoint, installs before SHarePoint, during SharePoint install(or before?) it adds a lot of folders and files under the 14 Hive. If you uninstall SHarePoint and delete the 14 hive to get the server clean, you will have to first uninstall the rsservice, then install it again, then reinstall SharePoint.

You uninstall a prereq, what then?

This will hopefully be covered later. Time did not permit it at this point in time.

* * * * SCRIPTS * * * *

Paste into a textfile, rename to: ‘download.ps1′.

Start copy ‘download.ps1′ here:

Import-Module
BitsTransfer
## Prompt
for the destination path
$DestPath =
Read-Host -Prompt "- Enter the destination path for downloaded files"
## Check
that the path entered is valid
If
(Test-Path "$DestPath" -Verbose)
{
    ##
If destination path is valid, create folder if it doesn't already exist
    $DestFolder
= "$DestPath\PrerequisiteInstallerFiles"
    New-Item
-ItemType Directory $DestFolder -ErrorAction SilentlyContinue
}
Else
{
    Write-Warning
" - Destination path appears to be invalid."
    ##
Pause
    Write-Host
" - Please check the path, and try running the script again."
    Write-Host
"- Press any key to exit..."
    $null
= $host.UI.RawUI.ReadKey("NoEcho,IncludeKeyDown")
    break
}
## We use
the hard-coded URL below, so that we can extract the filename (and use it to
get destination filename $DestFileName)
## Note:
These URLs are subject to change at Microsoft's discretion - check the
permalink next to each if you have trouble downloading.
$UrlList =
("http://download.microsoft.com/download/C/9/F/C9F6B386-824B-4F9E-BD5D-F95BB254EC61/Redist/amd64/Microsoft%20Sync%20Framework/Synchronization.msi",
# http://go.microsoft.com/fwlink/?LinkID=141237&clcid=0x409
- Microsoft Sync Framework Runtime v1.0 (x64) 
            "http://download.microsoft.com/download/c/c/4/cc4dcac6-ea60-4868-a8e0-62a8510aa747/MSChart.exe",
# "http://go.microsoft.com/fwlink/?LinkID=141512"
- Microsoft Chart Controls for the Microsoft .NET Framework 3.5
            "http://download.microsoft.com/download/2/0/e/20e90413-712f-438c-988e-fdaa79a8ac3d/dotnetfx35.exe",
# http://go.microsoft.com/fwlink/?LinkId=131037
- Microsoft .NET Framework 3.5 Service Pack 1
            "http://download.microsoft.com/download/2/8/6/28686477-3242-4E96-9009-30B16BED89AF/Windows6.0-KB968930-x64.msu",
# "http://download.microsoft.com/download/2/8/6/28686477-3242-4E96-9009-30B16BED89AF/Windows6.0-KB968930-x64.msu"
- Windows PowerShell 2.0    
            "http://download.microsoft.com/download/D/7/2/D72FD747-69B6-40B7-875B-C2B40A6B2BDD/Windows6.1-KB974405-x64.msu",
# "http://go.microsoft.com/fwlink/?LinkID=166363"
- Windows Identity Framework (Win2008 R2)
            "http://download.microsoft.com/download/6/8/1/681F5144-4092-489B-87E4-63F05E95079C/Windows6.0-KB976394-x64.msu",
# http://go.microsoft.com/fwlink/?linkID=160770
- WCF fix for Win2008 SP2
            "http://download.microsoft.com/download/E/C/7/EC785FAB-DA49-4417-ACC3-A76D26440FC2/Windows6.1-KB976462-v2-x64.msu",
# http://go.microsoft.com/fwlink/?LinkID=166231
- WCF fix for Win2008 R2
            "http://download.microsoft.com/download/D/7/2/D72FD747-69B6-40B7-875B-C2B40A6B2BDD/Windows6.0-KB974405-x64.msu",
# "http://go.microsoft.com/fwlink/?LinkID=160381"
- Windows Identity Framework (Win2008 SP2)
            "http://download.microsoft.com/download/3/5/5/35522a0d-9743-4b8c-a5b3-f10529178b8a/sqlncli.msi",
# "http://go.microsoft.com/fwlink/?LinkId=123718&clcid=0x409"
- SQL Server 2008 Native Client
            "http://download.microsoft.com/download/b/9/a/b9a78047-d269-4a25-88a1-9c4321d90677/SQLSERVER2008_ASADOMD10.msi",
# "http://go.microsoft.com/fwlink/?LinkId=130651&clcid=0x409"
- Microsoft SQL Server 2008 Analysis Services ADOMD.NET
            "http://download.microsoft.com/download/1/7/1/171CCDD6-420D-4635-867E-6799E99AB93F/ADONETDataServices_v15_CTP2_RuntimeOnly.exe",
# "http://go.microsoft.com/fwlink/?LinkId=158354"
- ADO.NET Data Services v1.5 CTP2 (Win2008 SP2)
            "http://download.microsoft.com/download/B/8/6/B8617908-B777-4A86-A629-FFD1094990BD/iis7psprov_x64.msi",
# http://go.microsoft.com/?linkid=9655704
- IIS management cmdlets
            "http://download.microsoft.com/download/1/0/F/10F1C44B-6607-41ED-9E82-DF7003BFBC40/1033/x64/rsSharePoint.msi",
# http://go.microsoft.com/fwlink/?LinkID=166379
- SQL 2008 R2 Reporting Services SharePoint 2010 Add-in
            "http://download.microsoft.com/download/8/D/F/8DFE3CE7-6424-4801-90C3-85879DE2B3DE/Platform/x64/SpeechPlatformRuntime.msi",
# http://go.microsoft.com/fwlink/?LinkID=166378
- Microsoft Server Speech Platform Runtime
            "http://download.microsoft.com/download/E/0/3/E033A120-73D0-4629-8AED-A1D728CB6E34/SR/MSSpeech_SR_en-US_TELE.msi"
# http://go.microsoft.com/fwlink/?LinkID=166371
- Microsoft Server Speech Recognition Language - TELE(en-US)
            )
ForEach
($Url in $UrlList)
{
    ##
Get the file name based on the portion of the URL after the last slash
    $DestFileName
= $Url.Split('/')[-1]
    Try
    {
        ##
Check if destination file already exists
        If
(!(Test-Path "$DestFolder\$DestFileName"))
        {
            ##
Begin download
            Start-BitsTransfer
-Source $Url -Destination $DestFolder\$DestFileName -DisplayName
"Downloading `'$DestFileName`' to $DestFolder" -Priority High
-Description "From $Url..." -ErrorVariable err
            If
($err) {Throw ""}
        }
        Else
        {
            Write-Host
" - File $DestFileName already exists, skipping..."
        }
    }
    Catch
    {
        Write-Warning
" - An error occurred downloading `'$DestFileName`'"
        break
    }
}
## View the
downloaded files in Windows Explorer
Invoke-Item
$DestFolder
## Pause
Write-Host
"- Downloads completed, press any key to exit..."
$null =
$host.UI.RawUI.ReadKey("NoEcho,IncludeKeyDown")

:End copy ‘download.ps1‘ here.

Paste below into a textfile, name it ‘PrerequisitesInstaller.Arguments.txt‘ and put it in your SharePoint media folder, same folder as the PrerequisitesInstaller.exe. The string has to be formatted exactly like it is here, with a single newline and a space between each argument and nothing else.

Start copy ‘PrerequisitesInstaller.Arguments.txt‘ here:

/SQLNCli:Prerequisites\sqlncli.msi /ChartControl:Prerequisites\MSChart.exe /Sync:Prerequisites\Synchronization.msi /KB976462:Prerequisites\Windows6.1-KB976462-v2-x64.msu /IDFXR2:Prerequisites\Windows6.1-KB974405-x64.msu /FilterPack:Prerequisites\FilterPack\FilterPack.msi /ADOMD:Prerequisites\SQLSERVER2008_ASADOMD10.msi /ReportingServices:Prerequisites\rsSharePoint.msi /Speech:Prerequisites\SpeechPlatformRuntime.msi /SpeechLPK:Prerequisites\MSSpeech_SR_en-US_TELE.msi /NETFX35SP1:Prerequisites\dotnetfx35.exe

:End copy ‘PrerequisitesInstaller.Arguments.txthere.

Paste below into a textfile, name it ‘InstallPrerequisitesFromFileshare.ps1′

Start copy ‘InstallPrerequisitesFromFileshare.ps1′ here:

# get current folder $folder = Get-Location # install requirements Start-Process "$folder\PrerequisiteInstaller.exe" -Wait -ArgumentList "/unattended ` /SQLNCli:`"$folder\PrerequisiteInstallerFiles\sqlncli.msi`" ` /ChartControl:`"$folder\PrerequisiteInstallerFiles\MSChart.exe`" ` /NETFX35SP1:`"$folder\PrerequisiteInstallerFiles\dotnetfx35.exe`" ` /PowerShell:`"$folder\PrerequisiteInstallerFiles\Windows6.0-KB968930-x64.msu`" ` /KB976394:`"$folder\PrerequisiteInstallerFiles\Windows6.0-KB976394-x64.msu`" ` /KB976462:`"$folder\PrerequisiteInstallerFiles\Windows6.1-KB976462-v2-x64.msu`" `
/IDFX:`"$folder\PrerequisiteInstallerFiles\Windows6.0-KB974405-x64.msu`" ` /IDFXR2:`"$folder\PrerequisiteInstallerFiles\Windows6.1-KB974405-x64.msu`" ` /Sync:`"$folder\PrerequisiteInstallerFiles\Synchronization.msi`" ` /FilterPack:`"$folder\PrerequisiteInstallerFiles\FilterPack\FilterPack.msi`" ` /ADOMD:`"$folder\PrerequisiteInstallerFiles\SQLSERVER2008_ASADOMD10.msi`" ` /ReportingServices:`"$folder\PrerequisiteInstallerFiles\rsSharePoint.msi`" ` /Speech:`"$folder\PrerequisiteInstallerFiles\SpeechPlatformRuntime.msi`" ` /SpeechLPK:`"$folder\PrerequisiteInstallerFiles\MSSpeech_SR_en-US_TELE.msi`""

:End copy ‘InstallPrerequisitesFromFileshare.ps1′ here.

* * * * END SCRIPTS * * * *

Follow

Get every new post delivered to your Inbox.

Join 182 other followers