Ĭ:\Windows\assembly\Ĭ:\Windows\assembly\. ‘C:\Program Files (x86)\Microsoft SDKs\Windows\v8.1A\bin\NETFX 4.5.1 Tools\gacutil.exe’ Copy the new (or old as the case may be) files into the c:\windows\assembly.Make a registry change to allow Orchestrator play with later PowerShell versions.Copy the old files into Assembly and register.The ones from a 2012 r2 version, which support PowerShell V2 aka default to Orchestrator are as follows: 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 system cannot find the file specified.
#How to install gacutil exe on windows server 2012 keygen#
Retrieve the LoaderExceptions property for more information.Ĭould not load file or assembly ‘, Version=.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35’ or one of its dependencies. So, you then repeat the same in a Runbook:Ĭannot load Windows PowerShell snap-in C:\Program files\Common Files\SMLets\ because of the following error: Unable to load one or more of the requested types.
However, once you think all the configuration is complete and you are working in PowerShell: There are some really good guides on getting this working: Using in System Center Orchestrator really enhances the automation ability of SCSM, mixed with the integration pack. Using the tool to install an assembly into the cache is simple: C: > gacutil /i BigAssembly.dll However, the gacutil executable did not exist anywhere on the server. For integration into SCSM, SMLets is great and can be downloaded from the following location: The ( gacutil.exe) allows you to install assemblies into the cache, remove them from the cache, and list the contents of the cache.