The new copy-item options to use a possession to copy files is great, please also support making an new-pssession with a vm name so it can be used with copy-item1 vote
With all Microsoft Tools going to PowerShell, I think it would be better for this config tool to be a PowerShell rather than VB Script.35 votes
Enable PowerShell Remoting login using private key authentication similar to the SSH protocol. Entering passwords all the time the log into remote PowerShell is tedious. Being able to use local secure private key to log into many cloud server instances would ease the process of creating new remote sessions.28 votes
A second or third hop WinRM session should support the usage of the primary session's ticket if Kerberos delegation is enabled for WinRM. CredSSP is not always wanted or might be limited due to security policies10 votes
We've now got the the DSC modules for this, but a standalone module for use outside of DSC would be extremely useful0 votes
After upgrade from Windows 1803 to Windows 1809 `Mount-DiskImage $iso_path` starts failing with the following error:
Exception calling "EndProcessing" with "0" argument(s): "Win32 internal error "Access is denied" 0x5 occurred while reading the console output buffer. Contact Microsoft Customer Support Services."
At line:352 char:17
+ CategoryInfo : NotSpecified: (:) , ParentContainsErrorRecordException
+ FullyQualifiedErrorId : HostException
The powershell command is executed under Administrator user in packer. It actually mounts specified image path, but throws this exception on attempt to interact with stdout.0 votes
BUG: Preserve the current directory name as stored in the filing system and not as entered by the user
The PowerShell console uses the path as entered by the user and not as stored in the filing system. This is inconsistent with the Command Console behaviour and causes applications that rely on the correct casing of the path to fail. IMHO the console should be case insensitive when searching for fils system paths but should preserve the case when returning the file path.0 votes
It would be awesome if powershell core was released as a package on nuget.org as well as the regular means.
The reason for this is build systems like cake build can have tools referenced via nuget packages and will pull them down as part of the build.0 votes
I understand that on Windows 7 SP1-Machines we have to install WMF 4.0 before upgrading to WMF 5.0.
On all our Windows 7 machines, before installing WMF 4.0 KB2819745, a sample output for Path Environmental Variable, getting with [Environment]::GetEnvironmentVariable(“Path”), looks like this:
After installing WMF 4.0 KB2819745, it looks like this:
There is a multiple path to the Powershell.exe.
After installing KB3134760 to upgrade to WMF 5.0, it’s getting even worse as path-variable looks like this:
Is this a known issue?
Thanks in advance
In the help text about_WorkFlowCommonParameters, in the KEYWORDS section of the full text, it shows two about_* files. The first (About_WorkFlowCommon_Parameters) does not exist.0 votes
bug filed, thanks!
- Don't see your idea?