• I Michael. Thank you for your help.

    I Execute the install-Module PSWindowsUpdate with -Verbose option on both machine. So I suppose the module is installed and loaded. I have also execute Get-WUList command with -Verbose and the result so weird :

    It seems the command is lauched well but cannot have access to the availables updates. What do you think ?

    Regards.

  • I think the PSWindowsUpdate module is already installed :

  • Hello Michael.

    Here is the result of the "dir" command on both side :

    The result is the same.

    Regards.

  • Hello Michael.

    I have found a english translation of the error message :

    [remoteAddress] Connecting to remote server remoteAddress failed with the
    following error message : WinRM cannot complete the operation. Verify that
    the specified computer name is valid, that the computer is accessible over
    the network, and that a firewall exception for the WinRM service is enabled
    and allows access from this computer. By default, the WinRM firewall exception
    for public profiles limits access to remote computers within the same local
    subnet.
    For more information, see the about_Remote_Troubleshooting Help topic.
    + CategoryInfo : OpenError: (remoteAddress:String) [], PSRemotingTransportException
    + FullyQualifiedErrorId : WinRMOperationTimeout,PSSessionStateBroken

    Do you think the roots cause could be the NetConnectionProfile setting ?

    Regards.

  • Hello Powershell group members.

    I try to launch a windows 8 update by using powershell.

    But when I want to list the avaliable update by using Invoke-Command remoting command I have no result.

    And when I do the same on local virtual computer, I have a big list :

    My login is registered as an administrator on the Virtual Machine.

    Could you tell me whitch setting I have to activate if I want to have the Get-WUList result with Invoke-COmmand ?

    Best regards.

  • Hello, all of Powershell forum members.

    I meet a problem with "Invoke-Command" powershell command : I send exactly the same command on two Windows 8 Hyper-V Virtual Machines but the result is different.

    Here is a screenshot of the powershell command prompt :

    I follow the Michael Pietroforte recommendations on https://4sysops.com/wiki/enable-powershell-remoting/ on both VM.

    Could you give some suggestions to solve my problem ?

    Best regards.

  • Hello Leos.

    Thank you for your help.

    I try to activate Powershell Remoting before to use Invoke-Commad with -ComputerName parameter, but it's still not working.

    I have this error :

    PS C:Windowssystem32> Enable-PSRemoting -SkipNetworkProfileCheck -Force
    
    PS C:Windowssystem32> Enable-PSRemoting -Force
    
    PS C:Windowssystem32> $cred
    
    UserName                           Password
    --------                           --------
    EURSESA105951 System.Security.SecureString
    
    
    
    PS C:Windowssystem32> Invoke-Command -ComputerName "RDITS_win7_32_en" -Script {start "C:Program FilesMcAfeeVirusScan Enterprisemcupdate.exe"} -Credential $cred
    [RDITS_win7_32_en] La connexion au serveur distant RDITS_win7_32_en a échoué avec le message d’erreur suivant: Le client WinRM ne peut pas traiter la demande car le nom du serveur ne peut pas être résolu. Pour 
    plus d'informations, voir la rubrique d'aide about_Remote_Troubleshooting.
        + CategoryInfo          : OpenError: (RDITS_win7_32_en:String) [], PSRemotingTransportException
        + FullyQualifiedErrorId : ComputerNotFound,PSSessionStateBroken
    
    PS C:Windowssystem32>

    When I want to activate Powershell Remoting on "RDITS__win7_32_en" virtual Machine i have this error :

    PS C:Windowssystem32> Enable-PSRemoting -SkipNetworkProfileCheck -Force
    WinRM is already set up to receive requests on this computer.
    WinRM is already set up for remote management on this computer.
    PS C:Windowssystem32> Enable-PSRemoting -Force
    WinRM is already set up to receive requests on this computer.
    Set-WSManQuickConfig : <f:WSManFault xmlns:f="http://schemas.microsoft.com/wbem/wsman/1/wsmanfault" Code="2150859113"
    Machine="localhost"><f:Message><f:ProviderFault provider="Config provider"
    path="%systemroot%system32WsmSvc.dll"><f:WSManFault xmlns:f="http://schemas.microsoft.com/wbem/wsman/1/wsmanfault"
    Code="2150859113" Machine="RDITS7EN32VM.eur.gad.schneider-electric.com"><f:Message>WinRM firewall exception will not
    work since one of the network connection types on this machine is set to Public. Change the network connection type to
    either Domain or Private and try again. </f:Message></f:WSManFault></f:ProviderFault></f:Message></f:WSManFault>
    At line:116 char:17
    +                 Set-WSManQuickConfig -force
    +                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [Set-WSManQuickConfig], InvalidOperationException
        + FullyQualifiedErrorId : WsManError,Microsoft.WSMan.Management.SetWSManQuickConfigCommand

    I have to ask Firewall authorisations to the company administrator. Do you know what they are ?

    Regards.

  • Hello.

    I am using a Hyper-V server on a Windows 10 PC.

    This server as several VMs with following operating systems:

    - Windows 10 32 and 64 bit

    - Windows 7 32 and 64 bit

    - Windows 8.1 32 and 64 bit

    My objective is to automate the antivirus update. I manage to do this with Invoke-Command on Windows 10 VMs, but not in Windows 7.

    I have the following error :

    PS C:Windowssystem32> Invoke-Command -VMName "RDITS_win7_32_en" -Script {start "C:Program FilesMcAfeeVirusScan Enterprisemcupdate.exe"} -Credential (Get-Credential "EURSESA105951")
    
    Invoke-Command : L’ordinateur virtuel RDITS_win7_32_en ne présente pas l’état en cours d’exécution. Au caractère Ligne:1 : 1 + Invoke-Command -VMName "RDITS_win7_32_en" -Script {start "C:Program ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidArgument : (:) [Invoke-Command], ArgumentException + FullyQualifiedErrorId : InvalidVMState,Microsoft.PowerShell.Commands.InvokeCommandCommand

    The Powershell version on Windows 7 VM is 5.1. Could you tell me how execute a remote command on Windows 7 VM ?

    Thanks a lot and Best Regards.

    avatar
  • Bruno Bernardi became a registered member 1 year, 7 months ago

    avataravatar
© 4sysops 2006 - 2021

CONTACT US

Please ask IT administration questions in the forums. Any other messages are welcome.

Sending

Log in with your credentials

or    

Forgot your details?

Create Account