{"id":80255,"date":"2016-10-05T00:01:03","date_gmt":"2016-10-05T07:01:03","guid":{"rendered":"https:\/\/blogs.technet.microsoft.com\/heyscriptingguy\/?p=80255"},"modified":"2019-02-18T09:10:26","modified_gmt":"2019-02-18T16:10:26","slug":"part-2-install-net-core-and-powershell-on-linux-using-dsc","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/scripting\/part-2-install-net-core-and-powershell-on-linux-using-dsc\/","title":{"rendered":"Part 2 \u2013 Install .NET Core and PowerShell on Linux Using DSC"},"content":{"rendered":"

Summary<\/strong>: Learn how to configure and use PowerShell, Bash, and desired state configuration (DSC) with Linux.<\/p>\n

Today, Cloud and Data Center MVP Stefan Roth returns for Part 2\u00a0of his three-part series about how to configure and use PowerShell, Bash, and desired state configuration (DSC) with Linux. Take it away Stefan \u2026<\/p>\n

My previous post<\/a> installed the foundation for this second part. It installed the OMI CIM server and DSC on Linux. In this part, the goal is to run a DSC configuration on Linux to download and install .NET core libraries and Windows PowerShell for Linux.<\/p>\n

There is a multi-step process to get this done.<\/p>\n

    \n
  1. Open firewall TCP port 5986 on the Linux machine<\/li>\n
  2. Connect via CIM session to the OMI CIM server<\/li>\n
  3. Install nx DSC module locally on your Windows 10 system<\/li>\n
  4. Create MOF file locally on your Windows 10 system<\/li>\n
  5. Copy and execute the DSC configuration (MOF file) on Linux<\/li>\n<\/ol>\n

    Sounds cool? Yeah it is!<\/p>\n

    Just to recap, my Ubuntu Bash is running on my client computer and a Linux server CentOS 7 x64. I think to test and develop a DSC configuration, which we want to run from Azure Automation, the best way is to write the configuration file locally and connect to the OMI CIM server via WinRM. By default, the OMI CIM server is listening on port 5986 for incoming traffic.<\/p>\n

    You can figure this out by looking at the omiserver.conf file in the \/etc\/opt\/omi\/conf\/ <\/em>directory.<\/p>\n

    \"Contents<\/a><\/p>\n

    Because my CentOS 7 server has a firewall running, you need to open the firewall TCP port 5986.<\/p>\n

    To open TCP port 5986 (inbound), use the following commands:<\/p>\n

    firewall-cmd --zone=public --add-port=5986\/tcp --permanent<\/code><\/p>\n

    firewall-cmd \u2013reload<\/code><\/p>\n

    The next step is to use PowerShell on my Windows 10 system to connect to the OMI CIM server. For this, I use the New-CIMSession<\/strong> cmdlet. Because we do not use a valid certificate for https to successfully connect, we need to skip certificate authority (CA), certificate common name (CN) and revocation status check. So, the command looks like this.<\/p>\n

    Connect via CIM session to OMI CIM server:<\/p>\n

    $Credentials = Get-Credential -UserName:'root' -Message 'Enter Root Credentials'<\/code><\/p>\n

    $CIMOptions = New-CimSessionOption -SkipCACheck -SkipCNCheck -UseSsl -SkipRevocationCheck<\/code><\/p>\n

    $CIMSession = New-CimSession -Credential $Credentials -ComputerName '192.168.32.18' -Port 5986 -Authentication Basic -SessionOption $CIMOptions<\/code><\/p>\n

    If you look at the $CIMSession<\/strong> object, you will see the connection.<\/p>\n

    \"The<\/a><\/p>\n

    The next step is to install the nx DSC module on your Windows 10 system. You need this module so you can develop and compile the managed object format (MOF) file locally on Windows 10. The nx DSC module has several included resources. You need nxArchive, nxScript, and nxPackage.<\/p>\n

    Built-in resources<\/a><\/p>\n

    The following list of resources and links to topics describe the resources in detail.<\/p>\n