The requirements for the toolkit, can be found here: https://docs.microsoft.com/en-us/system-center/orchestrator/orch-integration-toolkit/installation?view=sc-orch-2019

I have the following files, in order to complete the installation:

The installation has a requirement of the WIX (Windows Installer XML) toolset; if you try to install without this, you will receive the following message:

Install .Net Framework:

Command:

Dism /online /enable-feature /featurename:NetFx3 /All /LimitAccess /Source:\\sccmstore\SCCMDS\OSD\images\Source\Win101909Source

If you do not install the .net framework, you will receive this error:

Download the WIX toolset: https://wixtoolset.org/releases/

Install the WIX toolset:

Merge the registry entry, without completing, you
will still receive the error:

Use the file:

Which has the following content:

Install the ‘Orchestrator Integration Pack Wizard’:

Accept the license:

Enter user information:

Install:

Complete:

This is due to the reason that the AGPM archive cannot be found, I found that this had not been altered after I had completed a migration.

After googling with various links telling me to goto add remove programs to re-point the AGPM archive:

Found each time I ended up with different errors…

This can be completed easily within the registry, at location: HKLM\Software\Microsoft\Agpm and changing the ArchivePath value:

Then, simply refresh the ‘Change Control’ and the archive will connect, no service restart required:

By default, System Centre Orchestrator uses PowerShell version 2; of course this is slightly annoying, when you wish your code to make use of PowerShell version 3+ features, not mentioning the fact:

‘but this PowerShell works on the server ….’

Yes, indeed; a single registry change will allow Orchestrator to unleash later PowerShell;

It is a simple reg fragment to tell 32Bit to use the latest version as follows:

• Open regedit edit and goto location: [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework]
• Create a new DWORD with the name: OnlyUseLatestCLR with a decimal value of 1

Voila! That is it…. No reboot, just give it a whirl. I try the same runbook test, without even coming out of it:

Thanks’ go to the following post: https://scsmmercenary.blogspot.co.uk/2015/09/execute-native-powershell-version-4-in.html

Introduction

As one of my first steps into the world of ‘Azure’, I wanted to take a look at the idea of transition. This tutorial is taking the approach from an ‘Azure’ starter and scoped to the technical implementation.

During the same time, I am looking to also write the business ‘why’ case; why would I as a business do this and what are the benefits and flaws… lets be straight; I work with technology and am not a salesman, there are two sides to the coin, no matter whom tries to hide the fact.

Scenario

I want to keep my onsite services, but extend into Azure as a seamless hybrid approach, looking at how the various service opportunities can communicate and the how to ‘best plan for the future’ from a varying point of view. So, first topic to cover is connecting the world of Azure to my onsite infrastructure with the use of a Site-to-Site VPN.

• As an overview, the following components are required:
• Azure: Microsoft’s could offering
• A subscription in Azure: allowing yourself to use the service
• A virtual Network: created in Azure, think of it like your physical network infrastructure in the cloud
• Subnet: Network segments
• On-site Premise: your onsite infrastructure
• On-site VPN device: a device that will be the termination point at the edge of your onsite and also the access point into your infrastructure.

Now, the saying ‘a picture can paint a thousand words’ is my approach in most of my personal learning; I also think this seems to work with most people and therefore let’s start with a picture:

Not quite the correct hair colour (also a little too much). But this is my mindset in approaching Azure, with the amount of terminology and abbreviations; saying that, I think this is the same with any new technology, so rather than focus on a list of terms at the start, I will summarise at the end of the tutorial, rather than the start.

Key Data Technical Required

Do not worry if you do not understand each element or term, as you proceed through the tutorial.

Example data has been used in the table and will be used throughout the tutorial, however the hope is by the end, that you will understand exactly what the particular data is used for.

Setup

My setup is a little different than most, but in the simplest form:

[Example Visio Placeholder]

Process

Create the Virtual network, think of it like your physical network infrastructure, initially without the logical part…. A bit like you have just made yourself a little box inside the cloud…. Has to be somewhere. Whilst create  e.g. VNetwork01:

Change subnet, by selecting network and then custom DNS:

Add any subnets you want on the Azure side:

Add a gateway subnet:

Using in System Center Orchestrator really enhances the automation ability of SCSM, mixed with the integration pack.

There are some really good guides on getting this working:

• http://blogs.catapultsystems.com/mdowst/archive/2013/10/29/install-smlets-on-windows-server-2012-without-scsm-console/
• http://www.lazywinadmin.com/2014/09/powershell-scsm-install-and-config.html

However, once you think all the configuration is complete and you are working in PowerShell:

So, you then repeat the same in a Runbook:

And…… arrggghhhh:

The detail being:

Cannot load Windows PowerShell snap-in C:\Program files\Common Files\SMLets\SMLets.Module.dll because of the following error: Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.

Loader Exceptions:

Could not load file or assembly ‘Microsoft.EnterpriseManagement.Core, Version=7.0.5000.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35’ or one of its dependencies. The system cannot find the file specified.

Could not load file or assembly ‘Microsoft.EnterpriseManagement.Core, Version=7.0.5000.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35’ or one of its dependencies. The system cannot find the file specified.

Could not load file or assembly ‘Microsoft.EnterpriseManagement.Core, Version=7.0.5000.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35’ or one of its dependencies. The system cannot find the file specified.

So, the issue is my case; is that the version of the DLLs copied into the c:\windows\assembly folder and then registered are actually the SDK files from the SCORCH 2016 installation, which can only use PowerShell V3:

The ones from a 2012 r2 version, which support PowerShell V2 aka default to Orchestrator; are as follows:

Solution

So, there are two options:

1. Copy the old files into Assembly and register
2. Make a registry change to allow Orchestrator play with later PowerShell versions

Option 1 – Replace the files:

Okay I know you want the registry…. but wait:

1. Unregister the 2016 R2 DLLs
2. Copy the new (or old as the case may be) files into the c:\windows\assembly
3. Register the new / old files

Completed by PowerShell:

.‘C:\Program Files (x86)\Microsoft SDKs\Windows\v8.1A\bin\NETFX 4.5.1 Tools\gacutil.exe’
-u
Microsoft.EnterpriseManagement.Core

.‘C:\Program Files (x86)\Microsoft SDKs\Windows\v8.1A\bin\NETFX 4.5.1 Tools\gacutil.exe’
-u
Microsoft.EnterpriseManagement.ServiceManager

copy
D:\nobackup\2012R2\*
C:\Windows\assembly

.‘C:\Program Files (x86)\Microsoft SDKs\Windows\v8.1A\bin\NETFX 4.5.1 Tools\gacutil.exe’
-i
C:\Windows\assembly\Microsoft.EnterpriseManagement.Core.dll

.‘C:\Program Files (x86)\Microsoft SDKs\Windows\v8.1A\bin\NETFX 4.5.1 Tools\gacutil.exe’
-i
C:\Windows\assembly\Microsoft.EnterpriseManagement.ServiceManager.dll

Option 2 – Registry change

Yes, indeed; a single registry change will allow Orchestrator to unleash later PowerShell; thanks’ go to the following post:

• https://scsmmercenary.blogspot.co.uk/2015/09/execute-native-powershell-version-4-in.html

It is a simple reg fragment to tell 32Bit to use the latest version as follows:

• Open regedit edit and goto location: [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework]
• Create a new DWORD with the name: OnlyUseLatestCLR with a decimal value of 1

Voila! That is it…. No reboot, just give it a whirl. I try the same runbook test, without even coming out of it:

This is the version of me producing many blog articles!