{"id":61,"date":"2017-07-05T12:00:00","date_gmt":"2017-07-05T11:00:00","guid":{"rendered":"http:\/\/www.lucidusit.co.uk\/?p=61"},"modified":"2020-11-19T13:42:04","modified_gmt":"2020-11-19T13:42:04","slug":"scsm-automation-with-smlets-and-orchestrator","status":"publish","type":"post","link":"http:\/\/www.lucidusit.co.uk\/2017\/07\/05\/scsm-automation-with-smlets-and-orchestrator\/","title":{"rendered":"SCSM Automation with SMLets and Orchestrator"},"content":{"rendered":"
For integration into SCSM, SMLets is great and can be downloaded from the following location: https:\/\/smlets.codeplex.com\/<\/a><\/p>\n Using in System Center Orchestrator really enhances the automation ability of SCSM, mixed with the integration pack.<\/p>\n There are some really good guides on getting this working:<\/p>\n However, once you think all the configuration is complete and you are working in PowerShell:<\/p>\n So, you then repeat the same in a Runbook:<\/p>\n And\u2026\u2026 arrggghhhh:<\/p>\n The detail being:<\/p>\n 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:<\/p>\n The ones from a 2012 r2 version, which support PowerShell V2 aka default to Orchestrator; are as follows:<\/p>\n Solution So, there are two options:<\/p>\n Okay I know you want the registry\u2026. but wait:<\/p>\n Completed by PowerShell: .‘C:\\Program Files (x86)\\Microsoft SDKs\\Windows\\v8.1A\\bin\\NETFX 4.5.1 Tools\\gacutil.exe’<\/span> .‘C:\\Program Files (x86)\\Microsoft SDKs\\Windows\\v8.1A\\bin\\NETFX 4.5.1 Tools\\gacutil.exe’<\/span> copy<\/span> .‘C:\\Program Files (x86)\\Microsoft SDKs\\Windows\\v8.1A\\bin\\NETFX 4.5.1 Tools\\gacutil.exe’<\/span> .‘C:\\Program Files (x86)\\Microsoft SDKs\\Windows\\v8.1A\\bin\\NETFX 4.5.1 Tools\\gacutil.exe’<\/span> \n \n Yes, indeed; a single registry change will allow Orchestrator to unleash later PowerShell; thanks’ go to the following post:<\/p>\n It is a simple reg fragment to tell 32Bit to use the latest version as follows:<\/p>\n Voila! That is it\u2026. No reboot, just give it a whirl. I try the same runbook test, without even coming out of it:<\/p>\n For integration into SCSM, SMLets is great and can be downloaded from the following location: https:\/\/smlets.codeplex.com\/ Using in System Center Orchestrator really enhances the automation ability of SCSM, mixed with the integration pack. There are some really good guides on… Continue Reading →<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[21,4,6,3],"tags":[],"_links":{"self":[{"href":"http:\/\/www.lucidusit.co.uk\/wp-json\/wp\/v2\/posts\/61"}],"collection":[{"href":"http:\/\/www.lucidusit.co.uk\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.lucidusit.co.uk\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.lucidusit.co.uk\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.lucidusit.co.uk\/wp-json\/wp\/v2\/comments?post=61"}],"version-history":[{"count":5,"href":"http:\/\/www.lucidusit.co.uk\/wp-json\/wp\/v2\/posts\/61\/revisions"}],"predecessor-version":[{"id":243,"href":"http:\/\/www.lucidusit.co.uk\/wp-json\/wp\/v2\/posts\/61\/revisions\/243"}],"wp:attachment":[{"href":"http:\/\/www.lucidusit.co.uk\/wp-json\/wp\/v2\/media?parent=61"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.lucidusit.co.uk\/wp-json\/wp\/v2\/categories?post=61"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.lucidusit.co.uk\/wp-json\/wp\/v2\/tags?post=61"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}\n
<\/p>\n
<\/p>\n
<\/p>\n
\n<\/em><\/span><\/p>\n
\n<\/em><\/span><\/p>\n
\n<\/em><\/span><\/p>\n
\n<\/em><\/span><\/p>\n
\n<\/em><\/span><\/p>\n<\/p>\n
<\/p>\n
\n<\/strong><\/span><\/p>\n\n
Option 1 – Replace the files:<\/h2>\n
\n
\n<\/span><\/p>\n
\n-u<\/span>
\nMicrosoft.EnterpriseManagement.Core<\/span>
\n<\/span><\/p>\n
\n-u<\/span>
\nMicrosoft.EnterpriseManagement.ServiceManager
\n<\/span><\/span><\/p>\n
\nD:\\nobackup\\2012R2\\*<\/span>
\nC:\\Windows\\assembly
\n<\/span><\/span><\/p>\n
\n-i<\/span>
\nC:\\Windows\\assembly\\Microsoft.EnterpriseManagement.Core.dll<\/span>
\n<\/span><\/p>\n
\n-i<\/span>
\nC:\\Windows\\assembly\\Microsoft.EnterpriseManagement.ServiceManager.dll
\n<\/span><\/span><\/p>\nOption 2 \u2013 Registry change<\/h2>\n
\n
\n
<\/p>\n
<\/p>\n","protected":false},"excerpt":{"rendered":"