Skip to main content

What is The Network Administrator Survival Kit ?

The Network Administrator Survival Kit (NAS Kit) was conceived many years ago when I was a network administrator. It contained information such as troubleshooting procedures, tricks and tips. It was written in HTML and sits on a network share. My colleagues access it via a browser and only two of us who knew HTML was able to modify it.

It was so useful because the information was specific to our organisation. No more re-inventing the wheel. The first thing we would do if we can't figure out the solution is to check out the NAS Kit. If we can't find the solution there, we would obviously research until we are able to resolve the issue. The next entry in the NAS Kit would be the steps that we have just used.

Over the years, I have also found it so useful that there are so many sites across the web that are providing information that have helped me so often in my job.

So now, here's a chance for me to pay it back.

With 24 years of experience in IT ranging from desktop support, network administration, to IT Infrastructure Manager, I have decided to setup this Network Administrator Survival Kit blog site.

Obviously it will not contain the information in the original NAS Kit, but I will build it up one blog at a time. It will be based on real technical issues ranging from desktop support, server administration, virtualisation, scripting, and Amazon Web Services.

Yes, I had wore many hats, and have had to learn snippets of different technologies and scripting languages, and programming languages to solve many different problems at a given point in time.

Perhaps this was due to the fact that most of my working life, I have been working for small companies with small IT teams. In some companies, I was the only IT person. These small environments in-still in you the need to do more with less, and improvisation became the norm.

Anyway, enough about myself.  Enjoy this site, and I hope you get something out of my posts.




Popular posts from this blog

How To Migrate Mailboxes from Exchange 2010 to Exchange 2016 using PowerShell

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 '' -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 since it's uniqu…

How to Schedule an Exchange PowerShell Script in Task Scheduler

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 to run it under a …

Getting a List of Installed Applications on Local and Remote Computers


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.

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 at the local re…