This is a bit of a catch-22 situation. Powershell Remoting is really just a nice feature built on top of/around WinRM/WSMan/CIM, so to say that you cannot enable powershell remoting is the visible symptom of not being able to access WinRM/WSMan, which means you cannot use WMI/CIM.
If things were already in a desired state, you could just run Test-WSMan
. Unfortunately, that doesn't seem to be your situation.
Assuming you are using no automation, such as SCCM or loading scripts into an image you're deploying, you're in a tough spot for these primary reasons:
- WinRM service does not have listeners configured by default
- Firewall is closed to WinRM ports
- Hyper-V does not provide access to this information by default
- ICMP is disabled by default
Your remedy depends a lot on your environment. In our environment we:
- Use DISM to load a powershell script into a stock image from Microsoft
- Configure WDS with the bare minimum to install the OS and start the script
- Join the computer to the domain through the script
Once joined to the domain, GPP allows us to ensure, among other things:
- WinRM listeners are configured
- Necessary firewall ports are opened
- ICMP is enabled
You could also:
- Create a golden image
- Manually join to the domain to get the GPP configurations
- Use SCCM or some other desired state system
- Create a golden VHD that you clone for other machines
You did not provide much more about the details of your environment, so this is just a 1,000 meter view.