More on remote/parallel install of a full farm

Aug 3, 2012 at 2:49 PM

1. A previous post raised a question that is not clear from the documentation (http://autospinstaller.codeplex.com/discussions/389866)

If you use a AutoSPInstallerInput file for a domain (AutoSPInstallerInput-G01), do you also need to use AutoSPInstallerInput files customized for each server, or would the domain file be enough if you specify which server various components are provisioned on?

2. For the 3 settings (PauseAfterInstall, RemoteInstall, ParallelInstall), are these intended to be used sepearately or can they be used all together? How would it look if all 3 are used, in terms of prompts or messages on the screen?

3. On my first attempt at a 2 VM installation, it prompted for credentials for remote PowerShell access to the second VM, but never did anything there and never errored until the first server was fully installed. I am guessing a PS permissions issue, but am new to remote PS.

The utility did create a WordPad file that indicated it could not download the PSExec.

Suggestions and clarification would be appreciated.

 

Aug 3, 2012 at 6:24 PM

**********************
Windows PowerShell Transcript Start
Start time: 20120803130624
Username  : S01\S-S01SPConfig
Machine   : S01A-SP02 (Microsoft Windows NT 6.1.7600.0)
**********************
Transcript started, output file is C:\Users\S-S01SPConfig\Desktop\AutoSPInstall
er-S01A-SP07-2012-08-03_1-06.rtf
 - Testing connection (via Ping) to "S01A-SP07"...Success.
 - PsExec.exe not found; downloading...
Start-BitsTransfer : Access is denied. (Exception from HRESULT: 0x80070005 (E_A
CCESSDENIED))
At \\S01a-sp02\sp2010\AutoSPInstaller\AutoSPInstallerFunctions.ps1:4177 char:21
+         Start-BitsTransfer <<<<  -Source $PsExecUrl -Destination $PsExec -Dis
playName "Downloading Sysinternals PsExec..." -Priority High -Description "From
 $PsExecUrl..." -ErrorVariable err
    + CategoryInfo          : NotSpecified: (:) [Start-BitsTransfer], Unauthor
   izedAccessException
    + FullyQualifiedErrorId : System.UnauthorizedAccessException,Microsoft.Bac
   kgroundIntelligentTransfer.Management.NewBitsTransferCommand
 
WARNING:  - Could not download PsExec!
Press any key to exit...
**********************
Windows PowerShell Transcript End
End time: 20120803130650
**********************

Aug 5, 2012 at 3:58 PM

Hi DancingFoolVB !

 

2) Yes ! you can use them all together !
You will be prompted to "press any key to proceed with farm configuration" on each server you're deploying.

Also, you'll see a new console opening for each remote server, showing each deployment steps running.

 

3) You'll find PsExec here : http://technet.microsoft.com/en-us/sysinternals/bb897553.aspx

Just download this package, then extract it.

It contains PsExec.exe, that you have to copy directly in \SP2010\AutoSPInstaller\ 

 

1) Sorry, no idea about his point at the moment.

 

Hope this helps !

 

Nicolas

 

Aug 6, 2012 at 2:47 PM
Edited Aug 6, 2012 at 2:47 PM

Downloaded PSExec and placed it in the AutoSPInstaller folder.

Result:

Transcript started, output file is C:\Users\SPConfig\Desktop\AutoSPInstall
er-SP07-2012-08-06_9-14.rtf
 - Testing connection (via Ping) to "SP07"...Success.
 - Updating PowerShell execution policy on "SP07" via PsExec...

PsExec v1.98 - Execute processes remotely
Copyright (C) 2001-2010 Mark Russinovich
Sysinternals - www.sysinternals.com


powershell.exe exited on SP07 with error code -1.
 - Enabling PowerShell remoting on "SP07" via PsExec...

PsExec v1.98 - Execute processes remotely
Copyright (C) 2001-2010 Mark Russinovich
Sysinternals - www.sysinternals.com


Configuring PowerShell remoting...
WinRM already is set up to receive requests on this machine.
WinRM has been updated for remote management.
Created a WinRM listener on HTTP://* to accept WS-Man requests to any IP on thi
s machine.
WinRM firewall exception enabled.

powershell.exe exited on SP07 with error code -1.
 - Starting remote session to SP07...
[s01a-sp07] Connecting to remote server failed with the following error message
 : The WinRM client cannot process the request. A computer policy does not allo
w the delegation of the user credentials to the target computer because the com
puter is not trusted. The identity of the target computer can be verified if yo
u configure the WSMAN service to use a valid certificate using the following co
mmand: winrm set winrm/config/service '@{CertificateThumbprint="<thumbprint>"}'
  Or you can check the Event Viewer for an event that specifies that the follow
ing SPN could not be created: WSMAN/<computerFQDN>. If you find this event, you
 can manually create the SPN using setspn.exe .  If the SPN exists, but CredSSP
 cannot use Kerberos to validate the identity of the target computer and you st
ill want to allow the delegation of the user credentials to the target computer
, use gpedit.msc and look at the following policy: Computer Configuration -> Ad
ministrative Templates -> System -> Credentials Delegation -> Allow Fresh Crede
ntials with NTLM-only Server Authentication.  Verify that it is enabled and con
figured with an SPN appropriate for the target computer. For example, for a tar
get computer name "myserver.domain.com", the SPN can be one of the following: W
SMAN/myserver.domain.com or WSMAN/*.domain.com. Try the request again after the
se changes. For more information, see the about_Remote_Troubleshooting Help top
ic.
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:Re
   moteRunspace) [], PSRemotingTransportException
    + FullyQualifiedErrorId : PSSessionOpenFailed
 - Pre-installing .Net Framework feature on SP07...
Invoke-Command : Cannot validate argument on parameter 'Session'. The argument
is null or empty. Supply an argument that is not null or empty and then try the
 command again.
At \\......\SP2010\AutoSPInstaller\AutoSPInstallerFunctions.ps1:4211 char:70
+                                 $ProgressPreference = $pref} -Session <<<<  $
Session
    + CategoryInfo          : InvalidData: (:) [Invoke-Command], ParameterBind
   ingValidationException
    + FullyQualifiedErrorId : ParameterArgumentValidationError,Microsoft.Power
   Shell.Commands.InvokeCommandCommand

 - Starting remote session to SP07...
[s01a-sp07] Connecting to remote server failed with the following error message
 : The WinRM client cannot process the request. A computer policy does not allo
w the delegation of the user credentials to the target computer because the com
puter is not trusted. The identity of the target computer can be verified if yo
u configure the WSMAN service to use a valid certificate using the following co
mmand: winrm set winrm/config/service '@{CertificateThumbprint="<thumbprint>"}'
  Or you can check the Event Viewer for an event that specifies that the follow
ing SPN could not be created: WSMAN/<computerFQDN>. If you find this event, you
 can manually create the SPN using setspn.exe .  If the SPN exists, but CredSSP
 cannot use Kerberos to validate the identity of the target computer and you st
ill want to allow the delegation of the user credentials to the target computer
, use gpedit.msc and look at the following policy: Computer Configuration -> Ad
ministrative Templates -> System -> Credentials Delegation -> Allow Fresh Crede
ntials with NTLM-only Server Authentication.  Verify that it is enabled and con
figured with an SPN appropriate for the target computer. For example, for a tar
get computer name "myserver.domain.com", the SPN can be one of the following: W
SMAN/myserver.domain.com or WSMAN/*.domain.com. Try the request again after the
se changes. For more information, see the about_Remote_Troubleshooting Help top
ic.
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:Re
   moteRunspace) [], PSRemotingTransportException
    + FullyQualifiedErrorId : PSSessionOpenFailed
 - Checking for KB974405 (Windows Identity Foundation)...Invoke-Command : Cannot
 validate argument on parameter 'Session'. The argument
is null or empty. Supply an argument that is not null or empty and then try the
 command again.
At \\......\SP2010\AutoSPInstaller\AutoSPInstallerFunctions.ps1:4228 char:11
9
+     $wifHotfixInstalled = Invoke-Command -ScriptBlock {Get-HotFix -Id KB97440
5 -ErrorAction SilentlyContinue} -Session <<<<  $Session
    + CategoryInfo          : InvalidData: (:) [Invoke-Command], ParameterBind
   ingValidationException
    + FullyQualifiedErrorId : ParameterArgumentValidationError,Microsoft.Power
   Shell.Commands.InvokeCommandCommand

needed.
Invoke-Command : Cannot validate argument on parameter 'Session'. The argument
is null or empty. Supply an argument that is not null or empty and then try the
 command again.
At \\....\SP2010\AutoSPInstaller\AutoSPInstallerFunctions.ps1:4238 char:10
0
+         $remoteQueryOS = Invoke-Command -ScriptBlock {Get-WmiObject Win32_Ope
ratingSystem} -Session <<<<  $Session
    + CategoryInfo          : InvalidData: (:) [Invoke-Command], ParameterBind
   ingValidationException
    + FullyQualifiedErrorId : ParameterArgumentValidationError,Microsoft.Power
   Shell.Commands.InvokeCommandCommand

You cannot call a method on a null-valued expression.
At \\.....\SP2010\AutoSPInstaller\AutoSPInstallerFunctions.ps1:4239 char:41
+         If ($remoteQueryOS.Version.contains <<<< ("6.1"))
    + CategoryInfo          : InvalidOperation: (contains:String) [], RuntimeE
   xception
    + FullyQualifiedErrorId : InvokeMethodOnNull

 - Pre-installing Windows Identity Foundation on "SP07" via PsExec...

PsExec v1.98 - Execute processes remotely
Copyright (C) 2001-2010 Mark Russinovich
Sysinternals - www.sysinternals.com


 

Aug 7, 2012 at 9:25 AM

Hi !

 

Did you tried this ?

 

gpedit.msc and look at the following policy: Computer Configuration -> Administrative Templates -> System -> Credentials Delegation -> Allow Fresh Credentials with NTLM-only Server Authentication

 

Give a look to this post : http://dustin.hatch.name/post/24589312635/enable-powershell-remoting-with-credssp-using-group

 

Nicolas

Jun 5, 2013 at 11:01 PM
Dancing - Did you ever get an anser for this?