Skip to main content

Microsoft System Center 2016

Microsoft System Center 2016 is a bundled suite of systems management software. It is the latest version in the System Center line.

The suite comes with the following management softwares :

Configuration Manager, Operations Manager, Virtual Machine Manager, Data Protection Manager, Orchestrator, and Service Manager.

Here is a link to the Microsoft site to get more information about System Center 2016 :

https://www.microsoft.com/en-us/cloud-platform/system-center

Of the above softwares, Configuration Manager and Operations Manager are the most known so far. Most often Configuration Manager and Operations Manager are referred to as SCCM and SCOM respectively.

SCCM 2012R2 and SCOM 2012R2 skills are currently high in demand with regards to IT Systems Engineer roles.

Also in demand are the ability to upgrade the 2012R2 versions to 2016.

I've written a few tutorials on installing SCCM 2012 R2 and SCOM2012 R2, with the plan to write tutorials on how to upgrade these to 2016 version.

The following is a tutorial on How To Install SCCM 2012 R2:

https://turbofuture.com/computers/How-To-Install-Microsoft-SCCM-2012R2

The following is a tutorial on How To Install SCOM 2012 R2:

https://hubpages.com/technology/How-to-Install-Microsoft-SCOM-2012-R2



Comments

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 '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 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

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