Blog and Wiki Posts

IT News (sign in to comment or post)

Site Activity

  • Sweet...I will change that around and test it out a little later. Thanks!

  • Profile picture of Dan Franciscus

    Yep, I believe that is it. Nothing to be sorry about as I probably should have stated that in the article or the script. It may work if you just change Invoke-Command to -ComputerName localhost. I would have to do some testing though.

  • No thats exactly what is going on and what I was starting to look at yesterday. This script is and will be ran from the MDT server itself going forward. So I'm guessing I would need to update the script to remove the Invoke commands and instead just run them as if it was a normal script executing on the box? Sorry my PS skills are lacking in some areas. 🙂

    Also thanks a lot for your help on this!

  • Profile picture of Dan Franciscus

    Just to be clear, you are running this script ON the MDT server? Meaning you login to the MDT server and then run this script on it?

    Just want to make sure we are on the same page because the function assumes you are running it from a server that is NOT the MDT server.

  • Profile picture of Paolo Maffezzoli

    I have not tried Windows Server 2016 Core Edition but it seems that is not supported :

    Operating system

    The following table lists the supported operating systems for Exchange 2016.

    We don’t support the installation of Exchange 2016 on a computer that’s running Windows Server Core or Nano Server. The Windows Server Desktop Experience feature needs to be installed.

    To install Exchange 2016, you need to do one of the following to install the Desktop Experience on Windows

    Server prior to starting Exchange 2016 Setup:

    Windows Server 2012 and Windows Server 2012 R2 Run the following command in Windows PowerShell

    Install-WindowsFeature Server-Gui-Mgmt-Infra, Server-Gui-Shell -Restart

    Windows Server 2016 Install Windows Server 2016 and choose the Desktop Experience installation option. If a computer is running Windows Server 2016 Core mode and you want to install Exchange 2016 on it, you'll need to reinstall the operating system and choose the Desktop Experience installation option.

    Source : Microsoft Technet - Exchange 2016 system requirements

     

     

  • Profile picture of Paolo Maffezzoli

    I found an interesting PDF manual that describe how to prevent infections, and what to do when you are hit with ransomware.

    Link : Ransomware Hostage Rescue Manual

    Hope it helps.

  • Profile picture of Karim Buzdar

    Hi,

    Can I install Microsoft Exchange Server 2016 on Windows Server 2016 Core Edition? Although I know, we can install Exchange 2016 with the help of PowerShell but not sure about Server 2016 core edition.

    Thank you,

  • Alright, all good data, but doesn't address my issue.  Here's the problem - sharing files between Windows 7 and 10.  Most systems are on 7, and all can share easily.  The single Windows 10 system can see files from the others, as well.  However, they cannot access files from the Windows 10 system.  I can SEE the file folders, but cannot open any of them.  Permissions are set to "read/write" for all of the folders - pictures, documents, music - and all sharing access is turned on, as it should be.  The group name is "HOMEGROUP" for all systems.  When accessing "Network" from a Win7 system, I can see the 10 system, and see the actual folders for all of these.  It's accessing those that won't work; I get a message that I don't have permission.  Have rechecked everything, and nothing seems to work.  Any ideas?

  • PS C:scripts> $serv = (Get-adcomputer -Searchbase "OU=Servers,DC=domain,DC=local" -Filter {OperatingSystem -like "*Windows*"}).Name
    PS C:scripts> .checklocaladminsonservers.ps1 -ComputerName ($serv) -OutputDir C:scripts
    
  • I'm currently running it against the MDT server and it probably will be normally used this way by the client. They are not super savvy with Powershell so I'm doing my best to set up this server so they can run everything from it.

  • Profile picture of Dan Franciscus

    Are you running this function from the MDT server itself? Or from another server? Just trying to figure out why you are getting that.

  • Profile picture of Dan Franciscus

    Hmm. Well I ran the script straight from Github, seems to work fine with my MDT so I don't believe it is the script itself, could be wrong.

    I believe the problem has to do with the Invoke-Command. Doesn't appear remoting is working for you. I do not think its the MDT service at all actually now that I look at the error.

     

  • yessir. Status pages/service ports are available on the server and remotely. Same with WINRM. I can enter a PS session and run commands locally (through invoke-command) and from a remote system.

  • Profile picture of Dan Franciscus

    Are you able to test to see if the event service port is available from the server you are running the script from? http://MDTServer:9800. Are you able to remote into the MDT server as well from the server you are running the script from?

  • Hey Dan,

    Sorry to be a pest; I'm having some issues with the monitoring portion of your script, although I think it may be my MDT setup thats causing the problem. Everything works great as far as actually pushing out the update. However after that point, the script cannot seem to properly query my MDT monitoring service.

    I get this error first:

    Invoke-Windows10Upgrade : Connecting to remote server failed with the following error message
    : The WinRM client sent a request to an HTTP server and got a response saying the requested HTTP URL was not
    available. This is usually returned by a HTTP server that does not support the WS-Management protocol. For more
    information, see the about_Remote_Troubleshooting Help topic.
    At line:1 char:1
    + Invoke-Windows10Upgrade -ComputerName vmwin10mdttest -Credential $cre ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : NotSpecified: (:) , WriteErrorException
    + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Invoke-Windows10Upgrade

    and then after hitting continue, I get this:

    Connecting to remote server failed with the following error message : The WinRM client sent a
    request to an HTTP server and got a response saying the requested HTTP URL was not available. This is usually returned
    by a HTTP server that does not support the WS-Management protocol. For more information, see the
    about_Remote_Troubleshooting Help topic.
    At C:\automateMDTupgrade.psm1:137 char:13
    + $Results = Invoke-Command -ComputerName $MDTComputerName ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : OpenError: (String) , PSRemotingTransportException
    + FullyQualifiedErrorId : URLNotAvailable,PSSessionStateBroken

    If I run the commands (line 117 - 120) manually, I don't get any errors but I also don't get any results. I can connect to the MDT monitoring pages as well.

    I can also connect to the server via WINRM locally and remotely.

    One thing of note; I do not have a MDT Monitoring service installed on my server. I have enabled/disabled monitoring several times and rebooted the server as well. I assume its working because the websites appear but maybe that is where my problem lies.

    Thanks

  • Profile picture of Dan Franciscus

    Absolutely, just edit it in the function parameters:

    $MDTLiteTouchPath = '\MDTServerWIN10UPGRADE$ScriptsLiteTouch.vbs',

    $MDTComputerName = 'MDTServer',

    $MDTRoot = 'E:MDT',

  • Fantastic, been working on deploying .reg files via GPO.
    This did the work.
    Thanks a lot. !!!

View All Activity

CONTACT US

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

Sending
© 4sysops 2006 - 2017

Log in with your credentials

or    

Forgot your details?

Create Account