Excellent. I shall look that up. Kurt
On Sun, Apr 30, 2017 at 4:28 PM, Michael B. Smith <[email protected]> wrote: > You can look it up as easily as I can, but you can set the timeout values for > wsman/winrm. By default I think the timeout is 5 seconds. > > -----Original Message----- > From: [email protected] [mailto:[email protected]] > On Behalf Of Kurt Buff > Sent: Sunday, April 30, 2017 3:11 PM > To: [email protected] > Subject: Re: [powershell] Error with powershell and Add-DfsrMember > > A bit of followup. > > If I run add-dfsmember (with the same parameters) on the DC in the AU office, > then it works for the local file server, and not for the file server in the > US.. > > Except when it works - about one time in five. > > Even though I enables WSMAN via a GPO a long time ago, per this article: > https://msdn.microsoft.com/en-us/powershell/reference/5.1/microsoft.powershell.core/enable-psremoting?f=255&MSPPError=-2147217396 > > I ran "Set-NetFirewallRule -Name "WINRM-HTTP-In-TCP-PUBLIC" > -RemoteAddress Any", just in case, but that doesn't seem to make a difference > - and the Domain firewall is turned off anyway. > > This begins to smell like a distance/timeout problem. > > If that's the case, any ideas on how to work around that? > > Kurt > > On Sun, Apr 30, 2017 at 6:23 AM, Kurt Buff <[email protected]> wrote: >> Bad email editing on my part, sorry for that. >> >> In the script they do match. >> >> Kurt >> >> On Sun, Apr 30, 2017 at 5:23 AM, Webster <[email protected]> wrote: >>> To me, it looks like the variable name you used ($SourceComputer) is >>> not the same the error is showing ($SourceComputerNam...) >>> >>> >>> Webster >>> >>> -----Original Message----- >>> From: [email protected] >>> [mailto:[email protected]] On Behalf Of Kurt Buff >>> Sent: Sunday, April 30, 2017 2:44 AM >>> To: [email protected] >>> Subject: [powershell] Error with powershell and Add-DfsrMember >>> >>> I'm setting up DFSR between two file servers. The following line in the >>> script updates the US server ($SourceComputer), but fails with the message >>> shown against the AU server ($DestinationComputer). I'm a bit stumped. >>> >>> Add-DfsrMember -GroupName $GroupName -ComputerName >>> $SourceComputer,$DestinationComputer >>> >>> Add-DfsrMember : Could not add the computer to the replication group. >>> Computer: AUFS01P Replication group: "InfrastructureSoftware" >>> The remote procedure call failed >>> At line:1 char:1 >>> + Add-DfsrMember -GroupName $GroupName -ComputerName >>> $SourceComputerNam ... >>> + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >>> + CategoryInfo : NotSpecified: (AUFS01P:String) >>> [Add-DfsrMember], DfsrException >>> + FullyQualifiedErrorId : >>> Add-DfsrMember.NonTerminatingOMException,Microsoft.DistributedFileSys >>> temReplication.Commands.AddDfsrMemberCommand >>> >>> I've checked GPOs, and the same GPOs are applied to both machines. >>> I've checked the firewall, and it's WFO (which I intend to fix at some >>> point). I've also run enable-psremoting on the machine. >>> >>> I've verified that the varial $DestinationComputer contains the correct >>> machine. >>> >>> What else should I be checking? >>> >>> More context from the script can be provided if desired. >>> >>> Kurt >>> >>> >>> >>> >> >> >> > > > >
