Try enter-pssession cmdlet to test. When I experience remote RPC issues is normally is due to firewall ports or WMI issues or DCOM permissions
Cesar A. On Jul 21, 2017 9:13 PM, "Kurt Buff" <[email protected]> wrote: There you go, trying to educate me again. I don't know. I will have to figure that out, because I've not heard that term before. I'll get back to you. Kurt On Fri, Jul 21, 2017 at 8:27 PM, Michael B. Smith <[email protected]> wrote: > What is the InnerException of the error? > > -----Original Message----- > From: [email protected] [mailto:listsadmin@lists. myitforum.com] On Behalf Of Kurt Buff > Sent: Friday, July 21, 2017 11:11 PM > To: ntsysadm > Subject: [NTSysADM] RPC not available on remote machine while doing DFSR config > > All, > > I'm re-doing the DFSR config for the file servers in our US and AU offices. The US has a bunch of directories that will be replicated to AU (but not back). No big deal, but the PowerShell script I'm writing is killing me. I don't know if I'm running into a time out problem, or what it might be. > > I'm running the script from Redmond on my laptop. > > Here's the script, which should Just Work(tm): > ---------- > $NewDFSR = import-csv -Delimiter "`t" c:\Batchfiles\data\NewDFSR.csv > > New-DfsReplicationGroup -GroupName US2AU-Engineering > $GroupName = Get-DfsReplicationGroup US2AU-Engineering > > Foreach ($Line in $NewDFSR) > { > $GroupName = $Line.GroupName > $SourceComputer = $Line.SourceComputer > $FolderName = $Line.FolderName > $SourceContentPath = $Line.SourceContentPath > $SourceStagingPathQuotaInMB = $Line.SourceStagingPathQuotaInMB > $SourcePrimaryMember = > [System.Convert]::ToBoolean($Line.SourcePrimaryMember) > $DestinationComputer = $Line.DestinationComputer > $DestinationContentPath = $Line.DestinationContentPath > $DestinationReadOnly = > [System.Convert]::ToBoolean($Line.$Line.DestinationReadOnly) > > New-DfsReplicatedFolder -GroupName $GroupName -FolderName $FolderName > Add-DfsrMember -GroupName $GroupName -ComputerName $SourceComputer, $DestinationComputer > Add-DfsrConnection -GroupName $GroupName -SourceComputerName $SourceComputer -DestinationComputerName $DestinationComputer > Set-DfsrMembership -GroupName $GroupName -FolderName $FolderName -ComputerName $SourceComputer -ContentPath $SourceContentPath -PrimaryMember $SourcePrimaryMember -StagingPathQuotaInMB $SourceStagingPathQuotaInMB -Force > Set-DfsrMembership -GroupName $GroupName -FolderName $FolderName -ComputerName $DestinationComputer -ContentPath $DestinationContentPath -ReadOnly $DestinationReadOnly -Force > } > ---------- > > But it fails the Add-DfsrMember command, when trying to add the AU file server: > ---------- > Add-DfsrMember : Could not add the computer to the replication group. Computer: ZAUFS01P Replication group: "US2AU-Engineering" The remote procedure call failed > At C:\BatchFiles\New-DfsrConfiguration.ps1:19 char:2 > + Add-DfsrMember -GroupName $GroupName -ComputerName $SourceCompute ... > + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > + CategoryInfo : NotSpecified: (ZAUFS01P:String) > [Add-DfsrMember], DfsrException > + FullyQualifiedErrorId : > Add-DfsrMember.NonTerminatingOMException,Microsoft. DistributedFileSystemReplication.Commands.AddDfsrMemberCommand > ---------- > > However, if I RDP to that file server, I see this, which to me indicates that it *is* listening: > ---------- > C:\Windows\system32>winrm enumerate winrm/config/listener > Listener [Source="GPO"] > Address = * > Transport = HTTP > Port = 5985 > Hostname > Enabled = true > URLPrefix = wsman > CertificateThumbprint > ListeningOn = 10.212.1.30, 127.0.0.1, ::1, fe80::a9e7:6f85:8115:b4ed%16 > ---------- > > Heck, I even stood up wireshark on my laptop, from which I'm running this script, and see traffic to that server, though I can't quite figure out the conversation - but I have a 48kb capture file detailing the transaction for the attempted configuration of a single directory, if anyone wants that. > > Kurt > >
