The Network Administrator Survival Kit

Introduction A few months ago, I was asked to have a look at a PowerShell script which was supposed to be able to list installed applications on the local and remote Windows computers on the network. The script was from the Microsoft Gallery site. Here is the original script, with explanations of what it's supposed to do. https://gallery.technet.microsoft.com/scriptcenter/Get-a-List-of-Installed-c47393ed/view/Discussions Unfortunately if you run the script, it will only list the applications installed on the local PC but outputs the same results for all the computers that you are trying to inventory. I found that the program was very well structured so perhaps the author did this on purpose. Anyhow, I modified the  Function FindInstalledApplicationInfo($ComputerName) and used .NET's remote registry functions in place of the original PowerShell registry functions which looks at the local registry only. In this way, the .NET's remote registry functions can look ...

The Scenario Your organisation have decided to migrate from Exchange 2010 to Exchange 2016. The Exchange 2016 server have been installed into your current Exchange Organization. The Mailbox role have been installed on the Exchange 2016 server and you are ready to start moving mailboxes from the Exchange 2010 server to the Exchange 2016 server. Migrating a Mailbox from Exchange 2010 to Exchange 2016 Using New-MoveRequest Migrating a single mailbox involves invoking the cmdlet New-MoveRequest from the Exchange Management Shell on the Exchange 2016 server . Make sure that your user account that you have logged into the server with have the Organization Management role. The common parameters that I use for the New-MoveRequest cmdlet is : New-MoveRequest -Identity 'useralias@somedomain.com' -TargetDatabase "DB02" -BadItemLimit 10 The -Identity parameter identifies the mailbox to be migrated. I usually use the e-mail address of the mailbox for the identity...

Exchange Management Shell Since Exchange 2007, Microsoft has provided the Exchange Management Shell so administrators can manage all aspects of the Exchange server from the command line. The Exchange Management Shell has Exchange specific PowerShell cmdlets. These Exchange cmdlets are not normally available in an ordinary PowerShell command environment. An example of what can be done in the Exchange Management Shell is to run a PowerShell script to list all the mailboxes on the Exchange server to a file. You can output columns based on display name, size of the mailbox, last logon, and other available mailbox attributes. You can also schedule a batch migration of mailboxes from one database to another such as the migration of mailboxes from Exchange 2010 to Exchange 2013. Scheduling the PowerShell Script Once you have written a PowerShell script and utilised the Exchange cmdlets, you can run it with no problems inside the Exchange Management Shell. If you were to try...

Description Sometimes it is necessary to do a ping test to find out if there are dropped packets. It is not practical to keep watch on the continuous ping test overnight. I wrote a little PowerShell script to make use of the Test-Connection cmdlet. It writes to a log file the change in network status. I didn't want it to record every ping responses. Basically it will record the date and time initially of the network status of a host. Then when there's a change in status, it will record the date and time and the state of the host i.e. UP or DOWN. From the logs, you can see if there had been dropped packets by looking at the change in status. The Code is below : ## Get current date and time $currentdate = get-date $count = 1 $myHost = "10.0.1.1" $maximumcount = 10 $networkstatus = 0    # 0 = up and 1 = down $outputfile = "C:\PowerShell\ pinglog.txt" # Do the initial ping test $currentdate = get-date $pingResponse = Test-Connec...