To retrieve the Azure VM NIC using PowerShell, we need to first get the VM details. For this example, we have the VM name “TestMachine2k16”. To retrieve the VM details use the Get-AzVM command but before that make sure you are connected to the Azure Account using PowerShell session.PS C:\> $vm = Get-AzVM -VMName Testmachine2k16VM NIC information is stored inside the NetworkProfile property.PS C:\> $vm.NetworkProfileThis will retrieve all the NICs attached to the VM. If there are multiple NICs then we need to store the nic information into the array and have to perform some string operation to get the ... Read More

To install the MSI package using DSC, we need to use the DSC resource “Package”. Let see which properties are available for this resource.PS C:\> Get-DscResource -Name Package | Select -ExpandProperty Properties Name PropertyType IsMandatory Values ---- ------------ ----------- ------ Name [string] True {} Path [string] True {} ProductId [string] True {} Arguments [string] False {} Credential [PSCredential] False {} DependsOn [string[]] False {} Ensure [string] False {Absent, Present} LogPath [string] False {} PsDscRunAsCredential [PSCredential] False {} ReturnCode [UInt32[]] False {}Name, Path, and ProductID parameters are mandatory for this DSC resource.The best way to retrieve the above details is ... Read More

To install the MSI file with PowerShell, we can use cmdlet Start-Process.Let say we want to install the 7ZIP MSI file on the local computer and we have downloaded and stored the source file on the C:\temp location. Once we run the below command it will start the MSI installation.Start-Process C:\Temp\7z1900-x64.msiThe above command will open the GUI to install the MSI file but we use PowerShell to avoid GUI interaction so we can add the argument to install the file.If you check which arguments are available to run the MSI file, use the below command.C:\Temp\7z1900-x64.msi /?It will popup box like ... Read More

All the new user profiles are created on the windows system at the path,'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList\'To retrieve all the user profiles, we can usegci 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList\' | ForEach-Object { $_.GetValue('ProfileImagePath') }ProfileImagePath property shows the location of the user profiles.Another way to retrieve the User Profile is using WMI.PS C:\> gwmi win32_userprofile |Select -ExpandProperty LocalPathOutputC:\Users\.NET v2.0 Classic C:\Users\.NET v4.5 Classic C:\Users\.NET v2.0 C:\Users\.NET v4.5 C:\Users\Classic .NET AppPool C:\Users\Administrator.AUTOMATIONLAB C:\Users\delta

To get the IIS application Pool to recycle settings using GUI, you need to check the Application pool advanced settings.To retrieve the above settings using PowerShell, we can use the Get-IISAppPool command with the specific application pool name. We have the application pool, DefaultAppPool and we need to retrieve its Recycling settings.PS C:\> (Get-IISAppPool -Name DefaultAppPool).RecyclingOutputBelow settings will be for the Periodic restart.PS C:\> (Get-IISAppPool -Name DefaultAppPool).Recycling.PeriodicRestartOutputMemory          : 0 PrivateMemory   : 102400 Requests        : 0 Schedule        : {add} Time            : 1.05:00:00 Attributes     ... Read More

Using GUI from the IIS Manager, you can get the Application Pool Failure settings using App pool advanced settings from the Rapid-Fail Protection section as shown below.To retrieve the above settings using PowerShell, (Get-IISAppPool -Name DefaultAppPool).failureTo run the above command we need the IISAdministration module. You can retrieve the same settings using the WebAdministration module and using IIS PSDrive.(Get-ItemProperty IIS:\AppPools\DefaultAppPool\).failureTo retrieve the specific settings like Failure Interval or Maximum failures, use the below command.Failure Intervals, PS C:\> (Get-IISAppPool -Name DefaultAppPool).failure.rapidFailProtectionInterval Days              : 0 Hours             : 0 Minutes         ... Read More

From the GUI, to retrieve the Application Pool queue length you need to check the Advanced Settings of the Application Pool.To get the IIS application Pool queue length using PowerShell, first, we need to the application pool name. There are two ways (and maybe others) to retrieve once we have the name of the application pool.For example, we need to retrieve the queue length for the application pool DefaultAppPool.(Get-IISAppPool -Name DefaultAppPool).queuelengthTo run the above command, you need the IISAdministration Module. You can also use the IIS PS drive but for that WebAdministration module should be loaded.(Get-ItemProperty IIS:\AppPools\DefaultAppPool).queuelengthRead More

To get the IIS application pool names using PowerShell, you need to use the IIS PSDrive but for that, we need the IIS PowerShell module WebAdministration or IISAdministration on the server we are running the command.If the WebAdministration module is already installed, use the below command to import the module.Import-Module WebAdministration -VerboseOnce you Import the above module, you can see the IIS PSDrive will be activated in the current session.To get all the application Pools run the below command, Get-ChildItem IIS:\AppPools\OutputName                     State        Applications ----       ... Read More

When we have multiple branches in a git repository, we would need to bring the changes from all the branches to the main line of work that is the master branch. So, if we are currently in master branch and need to see which branches need to be merged, we can use the following commands.$git branch --no-mergedWe would also need to verify which branches are already merged, so that we can delete the unused branches$git branch --mergedExampleLet us create an example to understand how to view the branches that are merged and unmerged. The following diagram shows that there are ... Read More

Fast forward merges can be disabled −At the time of mergingFor the entire repositoryFor all repositories.Disabling fast forward merges has both pros and cons.When we disable fast forward merge, git will perform a merge commit to merge the changes from both the branches. The drawback of merge commit is that it becomes hard to read and understand the commit history, especially when we have many branches. If your team prefers to keep a linear history of branches, then one should go for fast forward merge. Disabling fast forward merge will create merge commits, which pollutes the commit history.The benefits of ... Read More