SOLVED

CCE on Windows Server 2016 host (Hyper V)

%3CLINGO-SUB%20id%3D%22lingo-sub-87867%22%20slang%3D%22en-US%22%3ECCE%20on%20Windows%20Server%202016%20host%20(Hyper%20V)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-87867%22%20slang%3D%22en-US%22%3E%3CP%3EMy%20hyper-v%20host%20is%20running%20windows%20server%202016%20and%20im%20attempting%20to%20install%20CCE.%20I%20know%20W2K16%20is%20not%20supported%20as%20yet%20but%20i%20was%20expecting%20the%20CCE%20.msi%20installer%20to%20work%20as%20the%20CCE%20host%20hyper%20visor%20requirements%20seem%20to%20be%20fairly%20generic.%20Whilst%20the%20installer%20goes%20through%20the%20motions%20and%20completes%20correctly%20CCE%20isnt%20actually%20installed%20correctly%20and%20none%20of%20the%20functions%20are%20installed.%26nbsp%3B%20When%20i%20run%20get-command%20*-Cc*%20only%20the%20aliases%20are%20returned%20and%20no%20functions.%20Is%20it%20possible%20to%20get%20CCE%20to%20work%20on%20a%202016%20host%3F%20I%20intend%20to%20install%20the%20VM's%20using%20a%20W2K12R2%20ISO%20which%20is%20supported%20but%20its%20just%20the%20hyper%20visor%20where%20im%20stuck.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-87867%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EVoice%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-88073%22%20slang%3D%22en-US%22%3ERe%3A%20CCE%20on%20Windows%20Server%202016%20host%20(Hyper%20V)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-88073%22%20slang%3D%22en-US%22%3E%3CP%3EAfter%20unzipping%20the%20CCE%20.msi%20i%20found%20this%20comment%20in%20the%20%22File_ReinstallCcMsi.ps1%22%20script%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%23%20CloudConnector%20module%20is%20not%20automatically%20loaded%20in%20Windows%20Server%202016%20when%20launch%20a%20process%20to%20reinstall%20MSI%20by%20the%20service%20(not%20sure%20if%20100%25%20repro)%3C%2FP%3E%3CP%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%20%23%20Import%20it%20explicitly%20as%20a%20workaround%20for%20Windows%20Server%202016%3C%2FP%3E%3CP%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Import-Module%20CloudConnector%20-Force%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAfter%20running%20this%20script%20and%20then%20using%20the%20-force%20parameter%20for%20the%20CloudConnector%20module%20i'm%20able%20to%20see%20all%20the%20functions.%20Judging%20by%20the%20comments%20it%20would%20appear%20the%20developers%20antipcated%20a%20Windows%20Server%202016%20host.%20Granted%20this%20is%20unsupported%20but%20it%20may%20be%20useful%20for%20anyone%20intending%20to%20use%202016.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-87871%22%20slang%3D%22en-US%22%3ERe%3A%20CCE%20on%20Windows%20Server%202016%20host%20(Hyper%20V)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-87871%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20Shawn%2C%26nbsp%3B%20CCE%201.4.2%20on%20Server%202016%20has%20not%20been%20tested%20thus%20not%20supported.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20beleive%20that%20future%20release%20of%20the%20CCE%20will%20provide%20support%20for%20Server%202016%20(Host%20and%20VMs)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%3C%2FP%3E%3C%2FLINGO-BODY%3E
Contributor

My hyper-v host is running windows server 2016 and im attempting to install CCE. I know W2K16 is not supported as yet but i was expecting the CCE .msi installer to work as the CCE host hyper visor requirements seem to be fairly generic. Whilst the installer goes through the motions and completes correctly CCE isnt actually installed correctly and none of the functions are installed.  When i run get-command *-Cc* only the aliases are returned and no functions. Is it possible to get CCE to work on a 2016 host? I intend to install the VM's using a W2K12R2 ISO which is supported but its just the hyper visor where im stuck.

2 Replies

Hello Shawn,  CCE 1.4.2 on Server 2016 has not been tested thus not supported.

 

I beleive that future release of the CCE will provide support for Server 2016 (Host and VMs)

 

Regards

Best Response confirmed by shawn harry (Contributor)
Solution

After unzipping the CCE .msi i found this comment in the "File_ReinstallCcMsi.ps1" script

 

# CloudConnector module is not automatically loaded in Windows Server 2016 when launch a process to reinstall MSI by the service (not sure if 100% repro)

    # Import it explicitly as a workaround for Windows Server 2016

    Import-Module CloudConnector -Force

 

After running this script and then using the -force parameter for the CloudConnector module i'm able to see all the functions. Judging by the comments it would appear the developers antipcated a Windows Server 2016 host. Granted this is unsupported but it may be useful for anyone intending to use 2016.