The PWD automatic variable is not set when the script block passed to InlineScript is executing within a workflow targetting a remote computer. Attempts to retrieve the variable (such as Get-Item Variable:\PWD) fail. The variable becomes present as soon as the first Set-Location statement is executed.

This differs from both powershell.exe and standard PS remoting behavior, where the variable is present from the start.

This issue breaks code which expects the PWD variable to always be available, such as IIS PowerShell Provider cmdlets (e.g. Get-WebApplication).

Client / workflow host: WMF 4.0 on Windows 7, also tested on 8.1
Workflow target: WMF 4.0 on Windows Server 2012 R2, also tested on 2008 R2

Consider the following scenario:
- a workflow sets $ErrorActionPreference to Stop
- that workflow contains a single-statement InlineScript activity
- the workflow is invoked targetting a remote server

After the InlineScript activity executes, all subsequent InlineScript activities in _any_ workflow targetting that server lose access to workflow variables - all $using:varname expressions return empty values. This condition persists until the WinRM service is restarted on the target server.

Putting any other statement inside the InlineScript seems to prevent the bug from occuring.

Tested client / workflow host: PowerShell 4.0 on Windows 7 and 8.1
Tested workflow target computers: PowerShell 2.0 on Windows Server 2008; PowerShell 4.0 on Windows Server 2012 R2 and 2008 R2

At first, I thought that the problem appeared only if the single statement inside InlineScript is an external script invocation and I wrote an elaborate repro script: https://gist.github.com/jberezanski/1b7f40fa20b2364b64f6#file-reproduce-inlinescriptusingbug-ps1
Later, however, I discovered that the problem is in fact triggered by any statement, provided it is the only one in the InlineScript. The much simpler repro workflow is here: https://gist.github.com/jberezanski/1b7f40fa20b2364b64f6#file-repro2-ps1

(migrated from Connect: https://connect.microsoft.com/PowerShell/Feedback/Details/1174240)

Votes from Connect: 3

Original Date Submitted: 9/25/2015 5:21:10 PM

Description:
********Contact Information********
Handle: Jan Egil Ring
Site Name: PowerShell
Feedback ID: 1833443
***************************************

Frequency: Desired State Configuration (DSC)
Regression: Update-DscConfiguration -ComputerName demohyper01 -Credential $TargetNodeCred -Wait -ErrorAction Stop

Problem Description:
Version: WMF 4 with 2014 November Update on Windows Server 2012 R2

I`ve run into access denied errors when using alternate credentials on Update-DscConfiguration:

PS C:\> Update-DscConfiguration -ComputerName demohyper01 -Credential $TargetNodeCred -Wait -ErrorAction Stop
VERBOSE: Perform operation 'Invoke CimMethod' with following parameters, ''methodName' = PerformRequiredConfigurationChecks,'className' = MSFT_DSCLocalConfigurationManager,'namesp
aceName' = root/Microsoft/Windows/DesiredStateConfiguration'.
VERBOSE: An LCM method call arrived from computer DEMORD01 with user sid S-1-5-21-2767021495-2328722188-4181787393-1106.
VERBOSE: Executing Get-Action with checksum: 2A4C8088BAE5F3220EA51E9B2B3F72829D3AEA6184863D96C857EBC461EDE3ED.
VERBOSE: Executing Get-Action returned result status: Ok.
VERBOSE: [DEMOHYPER01]: [] Updated configuration not found on pull server so no action taken. Ensure that a configuration with a different checksum exis
ts on the pull server for this node.
VERBOSE: Operation 'Invoke CimMethod' complete.
VERBOSE: Time taken for configuration job to complete is 0.205 seconds

The user sid S-1-5-21-2767021495-2328722188-4181787393-1106 is the SID of the currently logged on user, not the user specified in $TargetNodeCred.

It`s working fine when using PS Remoting to run the command (this is my current workaround):
#Update-DscConfiguration -ComputerName $VMHost.Hostname -Credential $using:TargetNodeCred -Wait -ErrorAction Stop

Invoke-Command -ComputerName $VMHost.Hostname -Credential $using:TargetNodeCred -ScriptBlock {
Write-Output -InputObject "Successfully connected using PS Remoting"
Update-DscConfiguration -Wait
}

Product Studio item created by Connect Synchronizer due to creation of feedback ID 1833443 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=1833443).

Repro Steps:
Update-DscConfiguration -ComputerName demohyper01 -Credential $TargetNodeCred -Wait -ErrorAction Stop

Expected Results:
The specified credentials should be used to invoke the DSC Configuration update, not the credentials of the currently logged on user.

Internal BugId: 15847

Votes from Connect: 4

Original Date Submitted: 8/24/2015 10:15:01 PM

Description:
********Contact Information********
Handle: herzbube
Site Name: PowerShell
Feedback ID: 1707779
***************************************

Frequency: PowerShell
Regression: 1. Create a folder C:\[foo]
2. Add a file "bar" to the folder
3. Run the following commands in PowerShell:

$path = 'C:\[foo]'
get-childitem -literalpath $path -recurse

Problem Description:
Let's say I have this file:

C:\[foo]\bar

I then run these PowerShell commands:

$path = 'C:\[foo]'
get-childitem -literalpath $path

Everything works fine, `get-childitem` shows me the file `bar`, then returns immediately.

Now I add the `-recurse` option:

$path = 'C:\[foo]'
get-childitem -literalpath $path -recurse

`get-childitem` no longer displays the file `bar`. In addition, the cmdlet runs a long time and displays various "permission denied" error messages for folders underneath `C:\Windows`, apparently because it scans the entire C: drive.

The problem is tied to the fact that the folder `[bar]` has brackets in the name. If I rename the folder to `bar`, i.e. without brackets, the result with recursion works as expected.

Environment: Windows 8.1, PowerShell 4.0.

Additional notes:

* I verified that in PowerShell 2.0 (on a Windows 7 machine) `get-childitem` returns the same result with or without `-recurse`. It appears that the behaviour has changed either in version 3.0 or 4.0.
* This post on technet.microsoft.com seems to describe the same problem. The poster uses PowerShell 3.0, so it would seem that the behaviour changed between versions 2.0 and 3.0: https://social.technet.microsoft.com/Forums/windowsserver/en-US/0fa34fab-cb35-4369-baad-a320ca610e24/getchilditem-file-recurse-literalpath-ctest-1-does-not-return-any-information?forum=winserverpowershell
* The post above also has a workaround: Use -path instead of -literalpath, then escape the square bracket characters.

Product Studio item created by Connect Synchronizer due to creation of feedback ID 1707779 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=1707779).

Repro Steps:
1. Create a folder C:\[foo]
2. Add a file "bar" to the folder
3. Run the following commands in PowerShell:

$path = 'C:\[foo]'
get-childitem -literalpath $path -recurse

Expected Results:
get-childitem displays the file "bar" and returns immediately.

Internal BugId: 15754

Votes from Connect: 7

Original Date Submitted: 8/6/2015 9:17:18 PM

Description:
********Contact Information********
Handle: June Blender
Site Name: PowerShell
Feedback ID: 1634561
***************************************

Problem Description:
Add a Scope parameter to Uninstall-Module so I can uninstall a module from a specified scope.

Install-Module has a scope parameter and multiple *Version parameters. On PowerShell 5.0+, you can install the same version in multiple scopes. However, because there's no Scope parameter for Uninstall-Module, you can specify only the version, not the scope.

Product Studio item created by Connect Synchronizer due to creation of feedback ID 1634561 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=1634561).

Repro Steps:

Internal BugId: 15715

Votes from Connect: 3

Original Date Submitted: 7/31/2015 8:55:14 AM

Description:
********Contact Information********
Handle: David Gardiner
Site Name: PowerShell
Feedback ID: 1611008
***************************************

Frequency: Always Happens
Regression: No, this is new to the most recent version

Problem Description:
Using Update-Help or Save-Help on a Windows 10 computer configured with en-GB as the Windows display language fails with an error.

Update-Help : Failed to update Help for the module(s) 'NetEventPacketCapture' with UI culture(s) {en-GB} : The value
of the HelpInfoUri key in the module manifest must resolve to a container or root URL on a website where the help
files are stored. The HelpInfoUri 'https://technet.microsoft.com/library/cc732148.aspx'; does not resolve to a
container.
At line:1 char:1
+ Update-Help
+ ~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (:) [Update-Help], Exception
+ FullyQualifiedErrorId : InvalidHelpInfoUri,Microsoft.PowerShell.Commands.UpdateHelpCommand

Product Studio item created by Connect Synchronizer due to creation of feedback ID 1611008 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=1611008).

Repro Steps:
1. Configure Windows 10 to use "English (United Kingdom)" as the display language.
2. Open PowerShell
3. Run Update-Help

Expected Results:
All help files should be downloaded and updated successfully.

Internal BugId: 15700

Votes from Connect: 8

Original Date Submitted: 7/28/2015 10:16:32 AM

Description:
********Contact Information********
Handle: Keith Hill MVP
Site Name: PowerShell
Feedback ID: 1599091
***************************************

Frequency: PowerShell
Regression: Run this script:

function Get-DummyData() {
for ($i = 0; $i -lt 10000000; $i++) {
"This is freaking huge!! I'm a ninja! More words, yay!"
}
}
Get-DummyData | Out-Null

BTW here's another example:

1..1000000 | foreach {if ($_ % 100000 -eq 0) {[GC]::Collect(2,'Forced',$true); $_}}

Problem Description:
It appears that for every pipeline object, bound to a pipeline parameter, a string like this is stuffed into a collection - where it waits to be written to the event log:

ParameterBinding(Out-Null): name = \\”InputObject\\”; value = \\“This is freaking huge!! I'm a ninja! More words, yay! \\”

Specifically I see these objects being held onto by a field in the internal PipelineProcessor class called eventLogBuffer. A couple of examples show that the eventLogBuffer holds onto all of this information until the pipeline is finished. In some examples, this can cause what appears to be a memory hoard and possibly OutOfMemory exceptions.

It would perhaps be better if PowerShell could monitor memory pressure during pipeline execution and periodically flush this data to the eventlog, allowing a subsequent GC to reclaim memory taken by that data.

Product Studio item created by Connect Synchronizer due to creation of feedback ID 1599091 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=1599091).

Repro Steps:
Run this script:

function Get-DummyData() {
for ($i = 0; $i -lt 10000000; $i++) {
"This is freaking huge!! I'm a ninja! More words, yay!"
}
}
Get-DummyData | Out-Null

BTW here's another example:

1..1000000 | foreach {if ($_ % 100000 -eq 0) {[GC]::Collect(2,'Forced',$true); $_}}

Expected Results:
Ideally, I'd expect the memory (PM) usage of the app to rise minimally above the baseline PM level considering we send one small string down the pipeline at a time. At the very least, the first script shouldn't need to top 2 GBs of PM to complete. I guess though you need to balance the perf issues of lots of GCs and potentially running of memory with the perf issue of writing to the event log.

Internal BugId: 15687

Votes from Connect: 3

Original Date Submitted: 7/23/2015 12:20:40 AM

Description:
********Contact Information********
Handle: John.Bevan
Site Name: PowerShell
Feedback ID: 1578010
***************************************

Frequency: PowerShell ISE
Regression: Run the below code / view the timings

$ip = '172.24.72.24' #amend for your environment
$hostname = [system.net.dns]::GetHostByAddress($ip).HostName

$begin=(get-date).ticks;test-connection $ip; $a=((get-date).ticks - $begin)
$begin=(get-date).ticks;test-connection $hostname; $b=((get-date).ticks - $begin)
$a-$b

#prove it's not caching; we can do this either way around
$begin=(get-date).ticks;test-connection $hostname; $b=((get-date).ticks - $begin)
$begin=(get-date).ticks;test-connection $ip; $a=((get-date).ticks - $begin)
$a-$b

#now let's see what measure-command says
(measure-command {test-connection $hostname}).ticks
(measure-command {test-connection $ip}).ticks
#that's not what we saw

NB: watching this you can see that the test-connection by IP is slow on each ping; not just on the first one.

Problem Description:
Running `Test-Connection` with an IP address, where the output is displayed performs significantly slower than `Test-Connection` does when passed a hostname (all else being equal).

However if output is not displayed (e.g. when using `Measure-Command` which hides the output from the pipeline, or when using the -`Quiet` parameter, `Test-Connection` is fractionally faster with an IP address than with HostName (as would be expected).

Product Studio item created by Connect Synchronizer due to creation of feedback ID 1578010 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=1578010).

Repro Steps:
Run the below code / view the timings

$ip = '172.24.72.24' #amend for your environment
$hostname = [system.net.dns]::GetHostByAddress($ip).HostName

$begin=(get-date).ticks;test-connection $ip; $a=((get-date).ticks - $begin)
$begin=(get-date).ticks;test-connection $hostname; $b=((get-date).ticks - $begin)
$a-$b

#prove it's not caching; we can do this either way around
$begin=(get-date).ticks;test-connection $hostname; $b=((get-date).ticks - $begin)
$begin=(get-date).ticks;test-connection $ip; $a=((get-date).ticks - $begin)
$a-$b

#now let's see what measure-command says
(measure-command {test-connection $hostname}).ticks
(measure-command {test-connection $ip}).ticks
#that's not what we saw

NB: watching this you can see that the test-connection by IP is slow on each ping; not just on the first one.

Expected Results:
Test-Connection performance should be negligibly faster when given an IP than when given a DNS name (all else being the same).
Instead it's an order of magnitude slower (when output is passed back to the host).

Internal BugId: 15673

Votes from Connect: 3

Original Date Submitted: 7/10/2015 6:50:26 PM

Description:
********Contact Information********
Handle: Dimitar Milov
Site Name: PowerShell
Feedback ID: 1529031
***************************************

Frequency: PowerShell
Regression:

Problem Description:
The issue seems to be OS specific and only reproduces on Windows 8/8.1 and Windows 10. When a .NET object instance is passed to a function as an argument the function calls the object's ToString method.

Product Studio item created by Connect Synchronizer due to creation of feedback ID 1529031 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=1529031).

Repro Steps:
Expected Results:
$Source = @"
using System;

namespace Test
{
public class TestClass
{
private bool _ts;
public bool ToStringCalled {
get {
return _ts;
}
}
public override string ToString() {
_ts = true;
return "test";
}
}
}
"@

Add-Type -TypeDefinition $Source -Language CSharp

$obj = new-object "Test.TestClass"

function test($o) {}

test $obj

$obj.ToStringCalled

> True

Internal BugId: 15638

Votes from Connect: 3

Original Date Submitted: 7/9/2015 7:50:44 AM

Description:
********Contact Information********
Handle: NICDoud
Site Name: PowerShell
Feedback ID: 1523059
***************************************

Problem Description:
I've watched a lot of MVA videos on Powershell and automation. I'm looking for something like Kaseya and other management programs for companies that do out sourced IT. I have a lot of customers on seperate networks, domains, locations that I want to manage with power shell or a web interface.

Something that can automate a lot of IT problems into a simple interface for users. Like System Center, but not limited to one domain or forest.

Product Studio item created by Connect Synchronizer due to creation of feedback ID 1523059 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=1523059).

Repro Steps:

Internal BugId: 15635

Votes from Connect: 5

Original Date Submitted: 7/7/2015 4:53:38 AM

Description:
********Contact Information********
Handle: June Blender
Site Name: PowerShell
Feedback ID: 1515009
***************************************

Frequency: PowerShell
Regression: PS C:\ps-test> Get-Help Get-Command -Parameter PipelineVariable
Get-Help : No parameter matches criteria PipelineVariable.
At line:1 char:1
+ Get-Help Get-Command -Parameter PipelineVariable
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidArgument: (System.Manageme...CommandHelpInfo:ProviderCommandHelpInfo) [Get-Help], PSArgumen
tException
+ FullyQualifiedErrorId : NoParmsFound,Microsoft.PowerShell.Commands.GetHelpCommand

PS C:\ps-test> Get-Command Get-Command -ParameterName PipelineVariable

CommandType Name ModuleName
----------- ---- ----------
Cmdlet Get-Command Microsoft.PowerShell.Core

Problem Description:
Commands in this format:
Get-Help <commandName> -Parameter <any_common_parameter>

return a PSArgumentException error, even when the command has the common parameter.

Get-Help Parameter parameter code needs a branch that gets the description from or displays a link to about_CommonParameters. The error implies that the parameter isn't valid for the command, which is confusing, especially for beginning users.

Product Studio item created by Connect Synchronizer due to creation of feedback ID 1515009 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=1515009).

Repro Steps:
PS C:\ps-test> Get-Help Get-Command -Parameter PipelineVariable
Get-Help : No parameter matches criteria PipelineVariable.
At line:1 char:1
+ Get-Help Get-Command -Parameter PipelineVariable
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidArgument: (System.Manageme...CommandHelpInfo:ProviderCommandHelpInfo) [Get-Help], PSArgumen
tException
+ FullyQualifiedErrorId : NoParmsFound,Microsoft.PowerShell.Commands.GetHelpCommand

PS C:\ps-test> Get-Command Get-Command -ParameterName PipelineVariable

CommandType Name ModuleName
----------- ---- ----------
Cmdlet Get-Command Microsoft.PowerShell.Core

Expected Results:
PS C:\ps-test> Get-Help Get-Command -Parameter PipelineVariable

-PipelineVariable <String>
PipelineVariable stores the value of the current pipeline element
as a variable, for any named command as it flows through the pipeline.

Valid values are strings, the same as for any variable names.

...

Required? false
Position? named
Default value None
Accept pipeline input? True (ByPropertyName)
Accept wildcard characters? false

Internal BugId: 15626

Votes from Connect: 4

Original Date Submitted: 6/17/2015 8:18:36 AM

Description:
********Contact Information********
Handle: Tom Nolan [MSFT]
Site Name: PowerShell
Feedback ID: 1441324
***************************************

Frequency: PowerShell
Regression: function Test-MyDebug
{
[cmdletbinding()]
param
(
[parameter(ValueFromPipeline=$true)]
$InputObject
)
process
{
write-host "Value: $_" -ForegroundColor Green

Write-Debug "Write-debug gets its own 'scope' for the last continue status of the debug preference"
Write-Debug "If you select 'Yes To All' on after any of these statements"
Write-Debug "It will have no effect, and you will continue to be prompted"
}
}

1,2,3 | Test-MyDebug -Debug

Problem Description:
When using the -Debug parameter with [cmdletbinding()] inside a script or function, this is known to set the $DebugPreference = "Inquire" for the scope of that script. When using Write-Debug within that script, you will be prompted as expected due to the inquire preference. However, if you select "Yes To All" on the prompt and have additional Write-Debug statements, they will still prompt you, even though you have specifically requested that it not prompt you.

I'm not sure if this behavior is truly by design or a side effect of the pipeline model and something that was overlooked when -Debug was implemented. Looking at decompiled code of System.Management.Automation.MshCommandRuntime, I can see that the "Yes To All" is actually being stored (internal ContinueStatus lastDebugContinueStatus) when the WriteDebug method calls the WriteHelper method.

However, due to the way the pipeline functions, Write-Debug is executing under a different context than the PSCmdlet script, and therefore the lastDebugContinueStatus is not updated when I select "Yes To All" after a Write-Debug statement.

This bug appears to be present in PowerShell 2.0 through the 5.0 pre-release

Product Studio item created by Connect Synchronizer due to creation of feedback ID 1441324 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=1441324).

Repro Steps:
function Test-MyDebug
{
[cmdletbinding()]
param
(
[parameter(ValueFromPipeline=$true)]
$InputObject
)
process
{
write-host "Value: $_" -ForegroundColor Green

Write-Debug "Write-debug gets its own 'scope' for the last continue status of the debug preference"
Write-Debug "If you select 'Yes To All' on after any of these statements"
Write-Debug "It will have no effect, and you will continue to be prompted"
}
}

1,2,3 | Test-MyDebug -Debug

Expected Results:
I would expect the lastDebugContinueStatus inside the Write-Debug context to apply back to the PScmdlet that is executing the Write-Debug cmdlet so that clicking "Yes To All" after using Write-Debug, will update the $DebugPreference to "Continue" rather than staying "Inquire"

Internal BugId: 15576

Votes from Connect: 4

Original Date Submitted: 6/5/2015 7:13:41 PM

Description:
********Contact Information********
Handle: William E. Anderson
Site Name: PowerShell
Feedback ID: 1402139
***************************************

Problem Description:
You know, it'd be kind of nice to be able to have a version of the Integrated Scripting Engine available as an installable feature for PowerShell Web Access. There's been a couple of times where a thought of how to script something popped into my head and all I had was my phone. Word for mobile doesn't really give me what I would like for building scripts in this way.

Product Studio item created by Connect Synchronizer due to creation of feedback ID 1402139 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=1402139).

Repro Steps:

Internal BugId: 14546

Votes from Connect: 4

Original Date Submitted: 6/5/2015 1:21:21 AM

Description:
********Contact Information********
Handle: Bob Dean IT Pro
Site Name: PowerShell
Feedback ID: 1399853
***************************************

Frequency: Desired State Configuration (DSC)
Regression: Build the LCM meta configuration.
Apply the LCM meta configuration to the target node.
Execute update-dscconfiguration on the target node.

Problem Description:
## The configuration for the LCM.

[DscLocalConfigurationManager()]
Configuration Meta
{

Node $AllNodes.NodeName
{
Settings
{
RefreshFrequencyMins = 30
RefreshMode = "PULL"
ConfigurationModeFrequencyMins = 60
AllowModuleOverwrite = $true
RebootNodeIfNeeded = $true
ActionAfterReboot = "ContinueConfiguration"
ConfigurationMode = "ApplyAndMonitor"

}

ConfigurationRepositoryWeb PullServer
{
ServerURL = $Node.PullServer
RegistrationKey = "My Registration Key"
ConfigurationNames = $Node.NodeName
AllowUnsecureConnection = $true #This needs to be fixed in the future.
CertificateID = $Node.Thumbprint

}

}
}

$ConfigData =
@{
AllNodes =
@(
@{
NodeName = $ComputerName;
PullServer = $DscPullServer;
ThumbPrint = $ThumbPrint;
}
)
}

# The status of the LCM after running set-dsclocalconfigurationmanager

>Get-DscLocalConfigurationManager

ActionAfterReboot : ContinueConfiguration
AgentId : CF19AC00-0ADB-11E5-80CA-005056010AE7
AllowModuleOverWrite : True
CertificateID :
ConfigurationDownloadManagers : {[ConfigurationRepositoryWeb]PullServer}
ConfigurationID :
ConfigurationMode : ApplyAndMonitor
ConfigurationModeFrequencyMins : 60
Credential :
DebugMode : {NONE}
DownloadManagerCustomData :
DownloadManagerName :
LCMCompatibleVersions : {1.0, 2.0}
LCMState : Idle
LCMStateDetail :
LCMVersion : 2.0
MaxPendingConfigRetryCount :
StatusRetentionTimeInDays : 10
PartialConfigurations :
RebootNodeIfNeeded : True
RefreshFrequencyMins : 30
RefreshMode : Pull
ReportManagers : {}
ResourceModuleManagers : {}
PSComputerName :

# Expanding on the settings of the ConfigurationDownloadManagers property.

>Get-DscLocalConfigurationManager | select -ExpandProperty ConfigurationDownloadManagers

ResourceId : [ConfigurationRepositoryWeb]PullServer
SourceInfo : C:\Development\tooling\lcm.ps1::42::9::ConfigurationRepositoryWeb
AllowUnsecureConnection : True
CertificateID : ACD69333FD3FC73ABB1722020373C484EF836916
ConfigurationNames : {rd-sndbx03}
RegistrationKey :
ServerURL : http://dscdev03:8080/psdscpullserver.svc
PSComputerName :

> Update-DscConfiguration -Wait -Verbose
VERBOSE: Perform operation 'Invoke CimMethod' with following parameters, ''methodName' =
PerformRequiredConfigurationChecks,'className' = MSFT_DSCLocalConfigurationManager,'namespaceName' =
root/Microsoft/Windows/DesiredStateConfiguration'.
VERBOSE: An LCM method call arrived from computer RD-SNDBX03 with user sid
S-1-5-21-3939769090-3111269998-2623241523-1001.
VERBOSE: [RD-SNDBX03]: [] Executing Get-Action with configuration 's checksum: .
VERBOSE: [RD-SNDBX03]: [] Executing Get-Action with configuration 's checksum returned
result status: GetConfiguration.
VERBOSE: [RD-SNDBX03]: [] Checksum is different. LCM will execute GetConfiguration to pull
configuration .
VERBOSE: [RD-SNDBX03]: [] Executing GetConfiguration succeed. Configuration is pulled from
server.
VERBOSE: [RD-SNDBX03]: [] Applying the new configuration(s) pulled.
VERBOSE: [RD-SNDBX03]: LCM: [ Start Resource ] [[User]A]
The Local Configuration Manager is not configured with a certificate. Resource '[User]A' in configuration 'DemoEnc'
cannot be processed.
+ CategoryInfo : ObjectNotFound: (root/Microsoft/...gurationManager:String) [], CimException
+ FullyQualifiedErrorId : MI RESULT 6
+ PSComputerName : localhost

VERBOSE: Operation 'Invoke CimMethod' complete.
VERBOSE: Time taken for configuration job to complete is 9.34 seconds

# The local machine certificate store.

> ls Cert:\LocalMachine\My

Directory: Microsoft.PowerShell.Security\Certificate::LocalMachine\My

Thumbprint Subject
---------- -------
ACD69333FD3FC73ABB1722020373C484EF836916 CN=rd-sndbx03
64892B98C1F2B7C8BB51BEA1F8B0307A5EB723DF CN=DSC-OaaS

Product Studio item created by Connect Synchronizer due to creation of feedback ID 1399853 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=1399853).

Repro Steps:
Build the LCM meta configuration.
Apply the LCM meta configuration to the target node.
Execute update-dscconfiguration on the target node.

Expected Results:
The pulled configuration that contains encrypted content will be applied by the LCM. Moving the certificateid to the settings block, and pushing the same configuration works successfully.

Internal BugId: 14545

Votes from Connect: 5

Original Date Submitted: 6/2/2015 10:28:19 PM

Description:
********Contact Information********
Handle: uniquedisplaynameformypublicprofile
Site Name: PowerShell
Feedback ID: 1392738
***************************************

Frequency: PowerShell
Regression: Create the function:
function Foo {
param([Parameter(mandatory)][int]$Bar)
"OK - $Bar"
}

This works:
Foo -Bar 1KB
(prints: OK - 1024)
Foo -Bar 1L
(prints: OK - 1)

But this fails:
Foo
cmdlet Foo at command pipeline position 1
Supply values for the following parameters:
Bar: 1KB
(prints: Cannot recognize "1KB" as a System.Int32 due to a format error.)
Bar: 1D
(prints: Cannot recognize "1L" as a System.Int32 due to a format error.)

Problem Description:
PowerShell does not accepts all integer literals (as defined by Windows PowerShell Language Specification Version 3.0) when accepting parameters interactively. Specifically, it does not accept valid numeric multipliers, nor valid numeric type suffixes.

Product Studio item created by Connect Synchronizer due to creation of feedback ID 1392738 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=1392738).

Repro Steps:
Create the function:
function Foo {
param([Parameter(mandatory)][int]$Bar)
"OK - $Bar"
}

This works:
Foo -Bar 1KB
(prints: OK - 1024)
Foo -Bar 1L
(prints: OK - 1)

But this fails:
Foo
cmdlet Foo at command pipeline position 1
Supply values for the following parameters:
Bar: 1KB
(prints: Cannot recognize "1KB" as a System.Int32 due to a format error.)
Bar: 1D
(prints: Cannot recognize "1L" as a System.Int32 due to a format error.)

Expected Results:
I can use the same valid PowerShell integer literals when specifying parameters either interactively or inline.

Internal BugId: 14538

Votes from Connect: 4

Original Date Submitted: 5/29/2015 3:12:46 AM

Description:
********Contact Information********
Handle: azhskr
Site Name: PowerShell
Feedback ID: 1377521
***************************************

Frequency: PowerShell
Regression: Find-Module -Tag DSC | Install-Module -> Hangs with no errors
Find-Module -Name xActiveDirectory | Install-Module -> Works

Problem Description:
Find-Module -Tag DSC | Install-Module just hangs in the PowerShell Console. There is no error displayed and I have let it sit for 20 minutes before I finally had to close the console and reopen it. If I run the command Find-Module -Name xActiveDirectory | Install-Module it works as expected.

Product Studio item created by Connect Synchronizer due to creation of feedback ID 1377521 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=1377521).

Repro Steps:
Find-Module -Tag DSC | Install-Module -> Hangs with no errors
Find-Module -Name xActiveDirectory | Install-Module -> Works

Expected Results:
Find-Module -Tag DSC | Install-Module should install all modules that are tagged with 'DSC'. It worked this way in previous Windows 10 Preview Builds.

Internal BugId: 14524