Introducing

Recommendations

Info

VERBOSE: Importing function 'Unregister-PSRepository'. VERBOSE: Importing function 'Update-Module'. VERBOSE: Importing function 'Update-ModuleManifest'. VERBOSE: Importing function 'Update-Script'. VERBOSE: Importing function 'Update-ScriptFileInfo'. VERBOSE: Importing alias 'fimo'. VERBOSE: Importing alias 'inmo'. VERBOSE: Importing alias 'pumo'. VERBOSE: Importing alias 'upmo'. Using the Verbose switch with the Import-Module cmdlet displays all imported functions, cmdlets, and aliases on the console. There are eight functions, two variables, and four aliases available in this module. The first time you use the PowershellGet cmdlet, it verifies the installation of NuGet on the machine. If NuGet is not installed, a confirmation message box appears, as follows: PowershellGet requires NuGet_anycpu.exe to interact with NuGet-based galleries. NuGet_anycpu.exe must be available in 'C:\ProgramData\OneGet\ProviderAssemblies' or 'C:\Users\\AppData\Local\OneGet\ProviderAssemblies'. For more information about NuGet, see http://www.nuget.org. Do you want PowershellGet to download NuGet_anycpu.exe now? Clicking Yes downloads and installs NuGet on the machine. The cmdlets provided by PowershellGet are divided into two broad categories: modules and repository cmdlets. PowershellGet provides cmdlets for finding, installing, publishing, and updating modules from the repository. It also provides cmdlets for reading current repository settings as well as updating, registering, and unregistering them. Two repositories are available by default: PSGallery and MSPSGallery. PowershellGet uses the NuGet provider to connect to these repositories. Running Get-PSRepository displays all existing repositories on the machine. PS C:\users\me>> Get-PSRepository Name SourceLocation OneGetProvider InstallationPolicy ---- -------------- -------------- ------------------ PSGallery https://msconfiggallery.cloudapp.net/api/v2/ NuGet Untrusted MSPSGallery http://www.microsoft.com/ NuGet Trusted Running the Get-PSRepository cmdlet with a repository name displays configurations related to that repository. PS C:\WINDOWS\system32> get-PSRepository -name PSGallery |Format-list * Name : PSGallery SourceLocation : https://www.powershellgallery.com/api/v2/ Trusted : False Registered : True InstallationPolicy : Untrusted PackageManagementProvider : NuGet PublishLocation : https://www.powershellgallery.com/api/v2/package/ ScriptSourceLocation : https://www.powershellgallery.com/api/v2/items/psscrip ScriptPublishLocation : https://www.powershellgallery.com/api/v2/package/ ProviderOptions : {} Within the output, SourceLocation indicates the URL of the repository location, PackageManagementProvider identifies the package provider used to connect to the repository (NuGet in this case), Trusted indicates whether the repository is trusted, and PublishLocation shows the URL used for submission of modules. Running the Set-PSRepository cmdlet sets the configuration values of a repository. For example, the Set-PSRepository cmdlet that follows changes the configuration value Untrusted to Trusted for the PSGallery repository. After changing a value, you can review the new configuration by running the Get-PSRepository cmdlet. PS C:\Users\me> Set-PSRepository -Name "PSGallery" -InstallationPolicy Trusted PS C:\Users\me> Get-PSRepository 134 CHAPTER 5 | Systems management
Name InstallationPolicy SourceLocation ---- ------------------ -------------- PSGallery Trusted https://www.powershellgallery.com/api/v2/ You use the Register-PSRepository cmdlet to add and register a new repository. To work properly with the repository, the cmdlet needs the name of the repository, its source location for downloading modules, the publish location for publishing new modules to the repository, an installation policy, and the package manager. Running this cmdlet with Chocolatey as the name, http://chocolatey.org/ api/v2/ as both source and publish location, Trusted as the installation policy value, and NuGet as the package manager Name adds a new module repository to the machine, as follows: Register-PSRepository -Name "Chocolatey" -SourceLocation "http://chocolatey.org/api/v2/" ` -PublishLocation "http://chocolatey.org/api/v2/" -InstallationPolicy Trusted ` -PackageManageMentProvider NuGet After registering, the Find-Module cmdlet can search repositories, and the Install-Module cmdlet can download and install modules. Chocolatey is shown here just as an example; it can be any repository hosting Windows PowerShell modules. Running Unregister-PSRepository with the Name parameter removes a previously registered repository. PS C:\Users\me> Unregister-PSRepository -Name Chocolatey The most important function of the PowershellGet module is to find and install modules. Running the Find-Module cmdlet without any parameter outputs all of the modules available within all the repositories, as shown here: PS C:\Users\me> Find-Module Version Name Repository Description ------- ---- ---------- ----------- 2.0.1 AzureRM.profile PSGallery Microsoft Azure PowerShell - Profile credential ... 2.0.1 Azure.Storage PSGallery Microsoft Azure PowerShell - Storage service cmd... 1.7.6 Posh-SSH PSGallery PowerShell module for automating tasks using the... 2.0.1 AzureRM PSGallery Azure Resource Manager Module .. .. Running the Find-Module cmdlet with the Name parameter outputs modules related to that name. Running this cmdlet with Bing as the value for the Name parameter provides information about Bing, as shown here: PS C:\Users\me> Find-Module -Name "Bing" Version Name Repository Description ------- ---- ---------- ----------- 5.0 Bing PSGallery A few functions for working with the new Bing APIs 5.0 Bing Choclatey A few functions for working with the new Bing APIs PS C:\Users\me> Find-Module -Name "*ing" Version Name Repository Description ------- ---- ---------- ----------- 2.11.0.0 xNetworking PSGallery Module with DSC Resources for Networking area 0.9.4 AzureRM.MachineLearning PSGallery Microsoft Azure PowerShell - Machine Learning We.. 1.0.0.0 xWindowsEventForwarding PSGallery This module can be used to manage configuration .. 2.5.2 PSLogging PSGallery Creates and manages log files for your scripts. 1.2.1 PowerShellLogging PSGallery Captures PowerShell console output to a log file. 5.0 Bing PSGallery A few functions for working with the new Bing APIs 2.0.1 Remote_PSRemoting PSGallery Enable PSRemoting Remotely using WMI Note The Name parameter also accepts wildcard characters. The Find-Module cmdlet takes the additional parameters MinimumVersion and RequiredVersion. You cannot use them both at the same time. To download a specific version, use the RequiredVersion parameter. Specify MinimumVersion to download the most recent version higher or equal to the 135 CHAPTER 5 | Systems management
Page 1 and 2:
Introducing Windows Server 2016 Joh
Page 3 and 4:
Visit us today at microsoftpresssto
Page 5 and 6:
Creating a cloud witness by using A
Page 7 and 8:
DSC Local Configuration Manager ...
Page 9 and 10:
Ramnish Singh Ritesh Modi Jason M.
Page 11 and 12:
C H A P T E R 1 Introduction to Mic
Page 13 and 14:
The following subsections dive deep
Page 15 and 16:
Offer greater service availability
Page 17 and 18:
Self-Service In the area of self-se
Page 19 and 20:
C H A P T E R 2 Software-defined da
Page 21 and 22:
Each nested guest VM needs to have
Page 23 and 24:
A VM collection group is a logical
Page 25 and 26:
Using the Get-VM cmdlet, you can se
Page 27 and 28:
Figure 2-5: Multitier management gr
Page 29 and 30:
Windows Server 2012 R2 took live mi
Page 31 and 32:
Figure 2-12: VM shortcut menu To do
Page 33 and 34:
You can confirm this by using Windo
Page 35 and 36:
ParentSnapshotName : MemoryStartup
Page 37 and 38:
Figure 2-19: Message indicating tha
Page 39 and 40:
Figure 2-23: VM Task Manager showin
Page 41 and 42:
Failover cluster By John Marlin and
Page 43 and 44:
Figure 2-30: Entering storage accou
Page 45 and 46:
Figure 2-34: Extending a volume in
Page 47 and 48:
[=== Microsoft-Windows-ClusterAware
Page 49 and 50:
Troubleshooting an event such as th
Page 51 and 52:
Figure 2-40: Pausing cluster node N
Page 53 and 54:
-IncludeAllSubFeature 5. Add the Wi
Page 55 and 56:
Figure 2-50: VM Configuration Versi
Page 57 and 58:
As Figure 2-51 illustrates, when ap
Page 59 and 60:
There is no need for schema updates
Page 61 and 62:
In the Configure Storage Replica Wi
Page 63 and 64:
There are many options for the New-
Page 65 and 66:
Deployment Choice Storage Spaces Di
Page 67 and 68:
Figure 2-60: The Storage Spaces Dir
Page 69 and 70:
on node A, B, and C, and the extent
Page 71 and 72:
Figure 2-63: Old mapping versus the
Page 73 and 74:
Multi-instance With multi-instance
Page 75 and 76:
Figure 2-66 Network virtualization
Page 77 and 78:
Figure 2-68: NVGRE Network Controll
Page 79 and 80:
More info In this book, we cannot p
Page 81 and 82:
When you have a service that requir
Page 83 and 84:
Figure 2-72: Post deployment config
Page 85 and 86:
Auditing access to resources Window
Page 87 and 88:
Figure 2-77: Published web applicat
Page 89 and 90:
Figure 2-81: Relying party options
Page 91 and 92:
Figure 2-85: The Edit Claim Rules d
Page 93 and 94:
This will provide you with the toke
Page 95 and 96: Figure 2-92: Viewing details from t
Page 97 and 98: Hear about it first. Get the latest
Page 99 and 100: Figure 3-1: Diagram showing the thr
Page 101 and 102: DNS server Web server running IIS A
Page 103 and 104: Figure 3-5: Architecture of differe
Page 105 and 106: Remotely managing Nano Server Nano
Page 107 and 108: Monitoring Nano Server You can now
Page 109 and 110: Figure 3-6: Conceptual container la
Page 111 and 112: Figure 3-7: Windows Server 2016 con
Page 113 and 114: Figure 3-10: Containers can write o
Page 115 and 116: Firewalls Every container host has
Page 117 and 118: C H A P T E R 4 Security and identi
Page 119 and 120: At this point, it might be self-def
Page 121 and 122: UEFI BIOS configured to prevent an
Page 123 and 124: Better protection against advanced
Page 125 and 126: When a user attempts to remote desk
Page 127 and 128: New fields in the process creation
Page 129 and 130: The core areas of interest to chang
Page 131 and 132: credentials for this account with s
Page 133 and 134: Long-term plan The long-term goals
Page 135 and 136: A REST Endpoint Windows PowerShell
Page 137 and 138: Bring Your Own Device (BYOD) equipm
Page 139 and 140: Users can add their personal Micros
Page 141 and 142: More info For further information,
Page 143 and 144: C H A P T E R 5 Systems management
Page 145: Like Linux, we have some common ter
Page 149 and 150: uri='https://www.powershellgallery.
Page 151 and 152: Figure 5-1: Sample code in the Wind
Page 153 and 154: The first runspace, ID 1, is always
Page 155 and 156: ConfigurationRepositoryShare This r
Page 157 and 158: IISInstall is responsible for downl
Page 159 and 160: DSC partial configurations One of t
Page 161 and 162: You also need to provide the pull s
Page 163 and 164: The .mof file is generated on the p
Page 165 and 166: this information. Figure 5-9 shows
Page 167 and 168: Backup and recovery Security and co
Page 169 and 170: Figure 5-15: Connecting a storage a
Page 171 and 172: Figure 5-19 depicts the first step
Page 173 and 174: Figure 5-23: Adding logs From here
Page 175 and 176: Figure 5-26: Sample deployment for
Page 177 and 178: Figure 5-28: The Windows PowerShell
Page 179 and 180: Deployment Deployment of SMT is rel
Page 181: Free ebooks From technical overview
show all

Introducing

Create successful ePaper yourself

Delete template?

Save as template?