Steps to reproduce:
1. Install this component on a standalone server (with both BTS + SQL Server)
2. Set a New-PSDrive specifying both –Instance and –Database options to target the DB for a distinct BizTalk Server Group;
3. Get-ChildItem ‘mydrive:\Applications’ will return the applications on the remote BizTalk Server Group. This is the behavior I would expect;
4. Get-ChildItem ‘mydrive:\Platform Settings\Host Instances’ returns local server host instances. This is NOT the behavior I would expect. The same applies to all items underneath Platform Settings.
Comments: ** Comment from web user: mlabelle **
1. Install this component on a standalone server (with both BTS + SQL Server)
2. Set a New-PSDrive specifying both –Instance and –Database options to target the DB for a distinct BizTalk Server Group;
3. Get-ChildItem ‘mydrive:\Applications’ will return the applications on the remote BizTalk Server Group. This is the behavior I would expect;
4. Get-ChildItem ‘mydrive:\Platform Settings\Host Instances’ returns local server host instances. This is NOT the behavior I would expect. The same applies to all items underneath Platform Settings.
Comments: ** Comment from web user: mlabelle **
As this is an old outstanding issue, you might have guessed that no, sorry, I cannot give estimates as to the release cycle. I still haven't found a satisfying correction.
However, you can work around this by using PowerShell Remoting in order to execute the command remotely.