ms-iot / azure-client-tools Goto Github PK

When the user clicks 'Install' or 'Start' in WDP, it is assumed that the agent will be configured to auto-restart when the device reboots. However, currently, it is not which causes confusion as to why the agent did not start - or "it stopped" running.

coreypottebaum wrote:

I am attempting to connect a Windows 10 IoT Enterprise VM with the device agent and am running into issues (or I am just misunderstanding the documentation). Am I correct to create a device in the IoT Hub, copy the connection string, then modify the AzureDeviceManagementClient.json file with the connection string in the "debugConnectionString" variable? The devices we will be using do not have TPM so we cannot use that method.

I have performed these steps but the device has no connectivity in the IoT hub. I have already enabled embedded mode.

Thanks in advance.

Copied from #13.

The method names in the DeviceExplorer project did not meet standards. They begin with a lower case character. private async void updateButton_Click(object sender, EventArgs e)
The first letter should be upper case.

Reprovisioning and disenrollment through Azure Device Provisioning Service, are these features supported? From our tests, it doesn't seem like the Azure DM client is communicating with the DPS service once provisioned. Neither on reboot.

I'd like to move devices from one hub to another, either by migrating data, or resetting to initial configuration, or disabling devices altogether, from accessing the hubs.

And in case of device re-location to another customer or similar, we'd like to reset configuration, or disenroll/deprovision the device.

Bug description

While the Device Agent is communicating with the Diagnostic Logs handler, it crashes.

Steps to reproduce

1. Configure the Agent to run on a desktop machine.
2. Start the agent
3. Configure the diagnostic logs with a new collector/provider.

Observed behavior

Device agent crashes.

Expected behavior

Device agent should not crash.

Version (please provide the following information):

• OS: Windows IoT Enterprise 10.0.17763.437
• branch: master

Hi,

It is recommended to use a TPM in device provisioning for because of its security benefits. However, I have noticed that Limpet.exe which is used for TPM operations requires access to PowerShell (a remote session), at least once, to get the enrollment info limpet.exe -azuredps -enrollmentinfo required for the device provisioning service.

I have found that getting a remote PowerShell session to the device requires the IOT_TOOLKIT feature (see https://docs.microsoft.com/en-us/windows-hardware/manufacture/iot/iot-core-feature-list) which is not recommended for Retail Image. If you are deploying to a fresh device from the factory, what would you advise to be the process to get enrollment info?

Thanks in advance

Motivation

We are planning a migration from https://github.com/ms-iot/iot-core-azure-dm-client but as of Jan 2020 (that not Jan 2019) there is still not official release of device client libraries and the device client service.

Describe the solution you'd like

Understand the timelines, roadmap and release schedules, for Iot Hub Device Management.

Describe alternatives that you've considered

Saying with https://github.com/ms-iot/iot-core-azure-dm-client and SystemConfigurator

Additional context

We are afraid of the repeat of the situation with https://github.com/ms-iot/iot-core-azure-dm-client where both the device client service and the device client lib reached end of life quickly.

I want to load custom plugin ,So I create a new plugin and put it to Correct position and modify Related configuration file.
The above operations are completely in accordance with the guidance of this document.
-- https://github.com/ms-iot/azure-client-tools/blob/master/docs/device-agent/development-scenario/developer-plugin-creation.md .

But when I execute ".\AzureDeviceManagementClient.exe -debug" will can't normally running.
below is log picture. the plugin name is DroneCtlPlugin.dll.

The direct method docs refer to the payload as 'parameters'. This is not consistent with the Azure portal/Device Explorer terminology.

(originally posted by leesiyuan here).

Hi, I have an associate question, I also want to use TPM Provisioning in Retail Image, but I can't get the sTPM well installed.
In the Windows Device Portal, every time I try to install Software TPM Emulator, my Raspberry Pi reboot and show No TPM installed.
I also tried PowerShell command
Limpet.exe -azuredps –enrollmentinfo
and i got a result like:

TpmNotSupported

The TPM works fine in Test Image but even I use the same Features for the Retail image, I can’t use the TPM.
So how could I use the sTPM in a Retail image? Thanks!

Hi.
There seems to be no plugin that handles application management. Is that right? Do I have to develop it myself or will it be included in the next release?

Dear I would like to find a simple way (nuget…) (I am not C and C++ expert) C# yes, where I could manage using IoT Hub new versions of my applications.

We are developing many types of applications on Windows 10 IoT Core (Background and foreground) and we are looking a simple way to send messages to our applications to download the new releases delivered on the storage.
Of course we know the solution using Device Manager, but we have full of problems trying to compile. We lost many days and at today we have not find the fast way.
Please could you provide a nuget components and a simple indications how integrate to our Iot device application?
Thanks

Bug description

When I try to downgrade uwp app's version it gives error: "Windows cannot install package because it has version 1.2.xx.xx. A higher version 1.3.xx.xx of this package is already installed." But in documentation you can see how behavior is designed https://github.com/ms-iot/azure-client-tools/blob/master/docs/device-agent/schema/configuration-groups/uwpapplication-management.md.

When I try to downgrade 1.3.xx.xx to 1.3.xx.xx it succeed with no problem.

Steps to reproduce

1. Try to downgrade app version from 1.3.xx.xx to 1.2.xx.xx
2. Device agent throws error given above to iot hub with no downgrade

Observed behavior

"Windows cannot install package because it has version 1.2.xx.xx A higher version 1.3.xx.xx of this package is already installed."

Expected behavior

It should to downgrade the app just like from 1.3.xx.xx to 1.3.xx.xx

Version (please provide the following information):

• OS: Windows 10 IoT Core 10.0.17763.615

I am attempting to connect a Windows 10 IoT Enterprise VM with the device agent and am running into issues (or I am just misunderstanding the documentation). I have created a device in the IoT Hub, copied the connection string, then modified the AzureDeviceManagementClient.json file with the connection string in the "ConnectionString" variable

I have performed these steps but the device has no connectivity in the IoT hub. I have already enabled embedded mode.

The files came directly from the repo (device.agent.2.0.0.1.x64) and I added the device connection string to the AzureDeviceManagementClient.json file in field "connectionString".

I understand that passing the connection string in the configuration file is only for testing but I'm trying to simply set this up for a PoC. My logs are attached below. Thanks in advance for the help!

Thanks in advance.

logs.zip

We're currently evaluating Azure IoT Hub and Azure Client Tools for a new IoT related product. Since the number of messages affects the Azure price, I'm trying to estimate the number of messages that Azure Client Tools requires. Both when keeping the connection to the hub alive, reporting status and when doing the different operations.

Do you have any such numbers, or is there some way to log the messages sent to/from the hub so we can see for ourselves? Either in the IoT Hub, or on the device.

Is there any way to control how often some messages is sent to the hub?

I'm trying to get the Device Agent up and running, but I'm having issues invoking methods on my device. No matter what command I'm invoking, it's the same error:

Error: [DeviceAgentPlugin] Code: 183, Message: Version not found

What version? Any ideas?

It's a clean IoT Core install, with device agent configured as described in Quick start with Azure DPS.

Here's some log output:

[192.168.1.200]: PS C:\dm\logs> cat AzureDM.Core.2019_05_03_23_08_10.log
11-17-55 PM [00003704] [00001228] Microsoft::Azure::DeviceManagement::Client::AzureRawHost::OnDirectMethodInvoked
11-17-55 PM [00003704] [00001228] ---- Direct Method Start >> ---------------------------------------------------------------------------
11-17-55 PM [00003704] [00001228] Device Method Name:StartRebootCmd
11-17-55 PM [00003704] [00001228] Parameters        :null
11-17-55 PM [00003704] [00001228] Microsoft::Azure::DeviceManagement::Client::AzureRawHost::InvokeHandler
11-17-55 PM [00003704] [00001228] Looking for handler for: StartRebootCmd
11-17-55 PM [00003704] [00001228] Found handler for: StartRebootCmd
11-17-55 PM [00003704] [00001228] Microsoft::Azure::DeviceManagement::Client::OutOfProcPluginBinaryProxy::CacheHandlerState
11-17-55 PM [00003704] [00001228] [Transport Layer] Microsoft::Azure::DeviceManagement::Common::PluginNamedPipeTransport::SendAndGetResponse
11-17-55 PM [00003704] [00001228] [Transport Layer] Microsoft::Azure::DeviceManagement::Common::PluginNamedPipeTransport::Initialize
11-17-55 PM [00003704] [00001228] [Transport Layer] Microsoft::Azure::DeviceManagement::Common::PluginNamedPipeTransport::ClientInitialization
11-17-55 PM [00003704] [00001228] [Transport Layer] Microsoft::Azure::DeviceManagement::Common::PluginNamedPipeTransport::LaunchPluginHost
11-17-55 PM [00003704] [00001228] [Transport Layer] Pluginhost has been launched.
11-17-55 PM [00003704] [00001228] [Transport Layer] Monitoring thread created.
11-17-55 PM [00003704] [00001224] [Transport Layer] Microsoft::Azure::DeviceManagement::Common::PluginNamedPipeTransport::PluginHostMonitor
11-17-55 PM [00003704] [00001228] Connecting to client pipe...11-17-55 PM [00003704] [00001228] Connecting to plugin pipe...11-17-55 PM [00003704] [00001696] [Transport Layer] Microsoft::Azure::DeviceManagement::Common::PluginNamedPipeTransport::MessageHandlerWorker
11-17-55 PM [00003704] [00001228] Microsoft::Azure::DeviceManagement::Client::OutOfProcPluginBinaryProxy::SendCreatePluginRequest
11-17-55 PM [00003704] [00002216] [Transport Layer] Microsoft::Azure::DeviceManagement::Common::PluginNamedPipeTransport::ProcessRequest
11-17-55 PM [00003704] [00001228] [Transport Layer] Microsoft::Azure::DeviceManagement::Common::PluginNamedPipeTransport::SendAndGetResponse
11-17-55 PM [00003704] [00001696] [Transport Layer] Recieved a Response Message
11-17-55 PM [00003704] [00001696] [Transport Layer] Response notification sent
11-17-55 PM [00003704] [00001228] Microsoft::Azure::DeviceManagement::Client::OutOfProcPluginBinaryProxy::SendCachedHandlerState
11-17-55 PM [00003704] [00001228] Microsoft::Azure::DeviceManagement::Client::OutOfProcPluginBinaryProxy::CacheHandlerState
11-17-55 PM [00003704] [00001228] [Transport Layer] Microsoft::Azure::DeviceManagement::Common::PluginNamedPipeTransport::SendAndGetResponse
11-17-55 PM [00003704] [00001696] [Transport Layer] Recieved a Response Message
11-17-55 PM [00003704] [00001696] [Transport Layer] Response notification sent
11-17-55 PM [00003704] [00001228] Microsoft::Azure::DeviceManagement::Client::OutOfProcPluginBinaryProxy::CacheHandlerState
11-17-55 PM [00003704] [00001228] [Transport Layer] Microsoft::Azure::DeviceManagement::Common::PluginNamedPipeTransport::SendAndGetResponse
11-17-55 PM [00003704] [00001696] [Transport Layer] Recieved a Response Message
11-17-55 PM [00003704] [00001696] [Transport Layer] Response notification sent
11-17-55 PM [00003704] [00001228] Microsoft::Azure::DeviceManagement::Client::OutOfProcPluginBinaryProxy::CacheHandlerState
11-17-55 PM [00003704] [00001228] [Transport Layer] Microsoft::Azure::DeviceManagement::Common::PluginNamedPipeTransport::SendAndGetResponse
11-17-55 PM [00003704] [00001696] [Transport Layer] Recieved a Response Message
11-17-55 PM [00003704] [00001696] [Transport Layer] Response notification sent
11-17-55 PM [00003704] [00001228] Microsoft::Azure::DeviceManagement::Client::OutOfProcPluginBinaryProxy::CacheHandlerState
11-17-55 PM [00003704] [00001228] [Transport Layer] Microsoft::Azure::DeviceManagement::Common::PluginNamedPipeTransport::SendAndGetResponse
11-17-55 PM [00003704] [00001696] [Transport Layer] Recieved a Response Message
11-17-55 PM [00003704] [00001696] [Transport Layer] Response notification sent
11-17-55 PM [00003704] [00001228] Microsoft::Azure::DeviceManagement::Client::OutOfProcPluginBinaryProxy::CacheHandlerState
11-17-55 PM [00003704] [00001228] [Transport Layer] Microsoft::Azure::DeviceManagement::Common::PluginNamedPipeTransport::SendAndGetResponse
11-17-55 PM [00003704] [00001696] [Transport Layer] Recieved a Response Message
11-17-55 PM [00003704] [00001696] [Transport Layer] Response notification sent
11-17-55 PM [00003704] [00001228] Microsoft::Azure::DeviceManagement::Client::OutOfProcPluginBinaryProxy::CacheHandlerState
11-17-55 PM [00003704] [00001228] [Transport Layer] Microsoft::Azure::DeviceManagement::Common::PluginNamedPipeTransport::SendAndGetResponse
11-17-55 PM [00003704] [00001696] [Transport Layer] Recieved a Response Message
11-17-55 PM [00003704] [00001696] [Transport Layer] Response notification sent
11-17-56 PM [00003704] [00001696] [Transport Layer] Recieved a Request Message
11-17-56 PM [00003704] [00001696] [Transport Layer] Request notification sent
11-17-56 PM [00003704] [00002216] [Transport Layer] Message Processing Thread: Received new request notification
11-17-56 PM [00003704] [00002216] [Transport Layer] Microsoft::Azure::DeviceManagement::Common::PluginNamedPipeTransport::ProcessRequestMessage
11-17-56 PM [00003704] [00002216] [Transport Layer] Received reverse-invoke call. Calling reverse invoke...
11-17-56 PM [00003704] [00002216] Microsoft::Azure::DeviceManagement::Client::AzureRawHost::Report
11-17-56 PM [00003704] [00002216] Microsoft::Azure::DeviceManagement::Common::ReportedSummary::ToJsonObject
11-17-56 PM [00003704] [00002216] Microsoft::Azure::DeviceManagement::Client::AzureRawHost::ReportAll
11-17-56 PM [00003704] [00002216] Microsoft::Azure::DeviceManagement::Client::AzureRawHost::ReportAll
11-17-56 PM [00003704] [00002216] {
	"StartRebootCmd" : 
	{
		"__errors" : 
		{
			"StartRebootCmd" : 
			{
				"code" : 183,
				"context" : "StartRebootCmd",
				"message" : "Version not found",
				"parameters" : {},
				"subsystem" : "DeviceAgentPlugin"
			}
		},
		"__meta" : 
		{
			"deploymentId" : "unspecified",
			"deploymentStatus" : "failed",
			"deviceInterfaceVersion" : "",
			"time" : "2019-05-03T23:17:56"
		}
	},
	"__summary" : 
	{
		"deployments" : "",
		"failedCount" : 1,
		"failedGroups" : "StartRebootCmd",
		"pendingCount" : 0,
		"pendingGroups" : "",
		"time" : "2019-05-03T23:17:56"
	}
}

11-17-56 PM [00003704] [00002216] [Transport Layer] Reverse invoke returned with error code 0
11-17-56 PM [00003704] [00002216] [Transport Layer] Deleted ReverseInvoke buffer
11-17-56 PM [00003704] [00002216] [Transport Layer] Sending response
11-17-56 PM [00003704] [00002216] [Transport Layer] Response sent
11-17-56 PM [00003704] [00001696] [Transport Layer] Recieved a Response Message
11-17-56 PM [00003704] [00001696] [Transport Layer] Response notification sent
11-17-56 PM [00003704] [00001228] Device Method Returned->payload: {
	"code" : 183,
	"context" : "StartRebootCmd",
	"message" : "Version not found",
	"parameters" : {},
	"subsystem" : "DeviceAgentPlugin"
}

11-17-56 PM [00003704] [00001228] Device Method Returned->code: 400
11-17-56 PM [00003704] [00001228] ---- Direct Method End << -----------------------------------------------------------------------------
11-17-56 PM [00003704] [00001228] Microsoft::Azure::DeviceManagement::Client::AzureRawHost::OnReportedStateSent
11-17-56 PM [00003704] [00001228] OnReportedStateSent() - statusCode: 200

[192.168.1.200]: PS C:\dm\logs> cat AzureDM.rebootInfo.2019_05_03_23_17_55.log
11-17-55 PM [00001308] [00000456] Logging configured.
11-17-55 PM [00001308] [00000456] Microsoft::Azure::DeviceManagement::RebootPlugin::RebootStateHandler::OnConnectionStatusChanged
11-17-55 PM [00001308] [00000456] Connection Status: Online.
11-17-55 PM [00001308] [00000456] Microsoft::Azure::DeviceManagement::RebootPlugin::RebootCmdHandler::Invoke
11-17-55 PM [00001308] [00000456] Microsoft::Azure::DeviceManagement::Common::Operation::RunOperation
11-17-55 PM [00001308] [00000456] Sub-Group: StartRebootCmd
11-17-55 PM [00001308] [00000456] SubSystem              : DeviceAgentPlugin
11-17-55 PM [00001308] [00000456] Exception code         : 183
11-17-55 PM [00001308] [00000456] Exception debug message: Version not found
11-17-56 PM [00001308] [00000456] Error: [DeviceAgentPlugin] Code: 183, Message: Version not found
11-17-56 PM [00001308] [00000456] Microsoft::Azure::DeviceManagement::Common::ReportedErrorList::AddError
11-17-56 PM [00001308] [00000456] Microsoft::Azure::DeviceManagement::Common::ReportedErrorList::ToJsonObject
11-17-56 PM [00001308] [00000456] Microsoft::Azure::DeviceManagement::Common::ReportedError::ToJsonObject
11-17-56 PM [00001308] [00000456] Microsoft::Azure::DeviceManagement::Common::ReportedErrorList::ToJsonObject
11-17-56 PM [00001308] [00000456] Microsoft::Azure::DeviceManagement::Common::ReportedError::ToJsonObject

[192.168.1.200]: PS C:\dm\logs> cat AzureDM.StartRebootCmd.2019_05_03_23_17_55.log
11-17-55 PM [00001308] [00000456] Logging configured.
11-17-55 PM [00001308] [00000456] Microsoft::Azure::DeviceManagement::RebootPlugin::RebootCmdHandler::OnConnectionStatusChanged
11-17-55 PM [00001308] [00000456] Connection Status: Online.
11-17-55 PM [00001308] [00000456] Microsoft::Azure::DeviceManagement::Plugin::Common::RawHandlerStub::CreateHandler
11-17-55 PM [00001308] [00000456] Microsoft::Azure::DeviceManagement::RebootPlugin::RebootStateHandler::Start

Bug description

Device throws

"windowsUpdate": {
"__meta": {
"deploymentId": "unspecified",
"deploymentStatus": "failed",
"deviceInterfaceVersion": "",
"time": "2020-01-24T16:30:27Z"
},
"activeHoursEnd": 23,
"activeHoursStart": 0,
"allowAutoUpdate": 1,
"allowUpdateService": 0,
"branchReadinessLevel": 16,
"deferFeatureUpdatesPeriodInDays": 0,
"deferQualityUpdatesPeriodInDays": 0,
"pauseFeatureUpdates": 0,
"pauseQualityUpdates": 0,
"scheduledInstallDay": 5,
"scheduledInstallTime": 0,
"__errors": {
"windowsUpdate": {
"code": 1001,
"context": "windowsUpdate",
"message": "Desired configuration is Null",
"parameters": {},
"subsystem": "DeviceAgent"
}
}
},
error when tried to update win 10 version.

Steps to reproduce

add windowsUpdate key to desiredProperties:

"windowsUpdate": {
"__meta": {
"deploymentId": "windows_update_v1",
"deviceInterfaceVersion": "1.0.0",
},
"activeHoursEnd": 23,
"activeHoursStart": 0,
"allowAutoUpdate": 1,
"allowUpdateService": 0,
"branchReadinessLevel": 16,
"deferFeatureUpdatesPeriodInDays": 0,
"deferQualityUpdatesPeriodInDays": 0,
"pauseFeatureUpdates": 0,
"pauseQualityUpdates": 0,
"scheduledInstallDay": 5,
"scheduledInstallTime": 0,
}

Observed behavior

Error given above thrown

Expected behavior

windows 10 version must be upgraded

Version (please provide the following information):

• OS:Windows 10.0.17763.615
• branch: master

Dear All
Now VS2019 build MSIX packeg not APPX package, How i update dwice twind propery to use msix file like in appx file i use
"desired" : {
"uwpApps" : {
"__meta": {
"deploymentId": "app_install1",
"serviceInterfaceVersion": "1.0.0"
},
"connectionString" : "Azure storage connection string",
"apps" : {
"8112d70e-a549-4378-96a9-63e8491e3d66_7ywy5sjsre78e" : {
"pkgFamilyName" : "8112d70e-a549-4378-96a9-63e8491e3d66_7ywy5sjsre78e",
"version" : "1.0.0.0",
"appxSource" : "dmtest\UwpApp1_1.0.0.0_x64.appx",
"depsSources": "dmtest\Microsoft.NET.Native.Framework.1.7.appx;dmtest\Microsoft.NET.Native.Runtime.1.7.appx;dmtest\Microsoft.VCLibs.x64.14.00.appx",
"startup" : "foreground",
"launchAfterInstall": true
}
}
}
}
now please guide me for msix packeg
nainesh

Bug description

when i connect my telemetry application dm client disconnected

Steps to reproduce

1. Do something
2. Do something else
3. See error

Observed behavior

install dm client on device
intall small telemetry application on same device

Expected behavior

when i connect my telemetry application to hub dm client is disconnected

Version (please provide the following information):

• OS: window iot core
• branch:

Additional notes

dm client run as service not background or foreground application,

Bug description

Please provide a clear and concise description of the problem.
The quick start guide for the timeInfo plugin does not work. There is an error in the reported properties of the Device Twin as shown below
"timeInfo": {

"__meta": {

"deploymentStatus": "failed",

"deploymentId": "time_info_v1",

"deviceInterfaceVersion": "",

"time": "2019-05-07T16:34:24Z"

},

"__errors": {

"timeInfo": {

"code": -2,

"context": "timeInfo",

"message": "missing json value: serviceInterfaceVersion",

"parameters": {},

"subsystem": "deviceManagement"

}

Steps to reproduce

1. Follow the steps to make changes to the Desired properties of the TimeInfo plugin
2. The Reported section has the above error and the device still shows the older timestamp

Observed behavior

Please provide a description of the observed behavior.

Expected behavior

The plugin needs to change the timezone on the device

Version (please provide the following information):

• OS:
• branch:

Additional notes

Feel free to provide any additional notes.

Bug description

DMValidator compares the output of an operation to an expected state by traversing the json trees of each. When the leaf node is of type boolean, DMValidator always returns true even if the values differ.

Steps to reproduce

1. Write a new test case.
2. In the output include a boolean expected value.
3. Make sure the handler reports something different from the expected value.
4. Run the agent.
5. Run the test.

Observed behavior

DMValidator does not report an error.

Expected behavior

DMValidator should flag the test as a failure and catch the mismatch.

Version (please provide the following information):

• OS: Windows IoT Enterprise 10.0.17763.437
• branch: master

According to: https://github.com/ms-iot/iot-core-azure-dm-client this repo is the future of the DM capability.
Have I got it right that the device-agent in this repo logically replaces the dm-client?

We have not gotten far with the dm-client yet, so we are considering adopting this device-agent instead.

However, I am not seeing any support in this device-agent for app update, or app install like there is in dm-client.

Can this device-agent still install a UWP app, and then upgrade the app with a new version of the app, installed from a package file in Azure Storage blob?

I just finished building an entire solution based around the iot-core-azure-dm-client project. Our UWP application is set up to use a completely custom provisioning endpoint we built into our api. Our solution does not use the Azure Provisioning Service. Instead, we have out own process that the device goes through and in the end receives it's api key to our Azure Iot Hub.

If we migrate from the dm-client to this new approach will we still be able to do this? From reading the documentation so far in this project it seems like it's tied into the Azure Provisioning Service. Is it possible for our UWP app to handle provisioning with this new Azure Client?

To clarify a little more, basically my UWP application has similar code to this in it which manages the communication with SystemConfigurator.exe:

https://github.com/ms-iot/iot-core-azure-dm-client/blob/master/samples/IoTDMBackground/DMClientBackgroundApplication.cs

My version implements GetConnectionStringAsync() in the above example differently since we have our own provisioning system which provides the Iot Hub credentials that are used for the device to build it's connection string.

Will it be possible to handle the provisioning process without using Azure Provisioning service with this library as I am doing with dm-client?

Thanks

For Windows IoT Core, updating the device agent using DUC is pretty straightforward, however for Windows IoT Enterprise, the instructions are vague and left up to interpretation. I'm hoping for a more straightforward approach to updating the device agent on Windows IoT Enterprise. If anyone could provide that I think that would be helpful.

Specifically, I'm not sure what mechanisms are even supported for delivering cabs to devices and deploying using dism. I use the Microsoft Store to update my application and can not find any information anywhere on how this could be used to deliver cabs.

Bug description

The twin has a storage limit of 8k - so, handlers need to be conservative in what they report to the twin. The Diagnostics Log handler reports all defined collectors - which is excessive because when debugging an issue, developers are not interested in all collectors.

Steps to reproduce

1. Run the agent.
2. Configure a collector.
3. Inspect the reported properties.

Observed behavior

All collectors on the system are reported even thought that are not configured through the twin.

Expected behavior

Only the collectors configured through the twin should be reported.

Version (please provide the following information):

• OS: Windows Enterprise IoT 10.0.17763.437
• branch: master

Hi ,
so far, I know that azure-client-tools has provided two way(device twin & direct method) for client to manage device.

But now , I am Facing scene that device send the real time of data to cloud. I think that D2C is most Effective way for this scene. but, I don't know that the azure-client-tools whether support that device send message to cloud by D2C command, because i not found Similar call in azure-client-tools sample and the azure-client-tools document doesn't seem to introduce D2C .

who knows this tool whether support D2C ?

Thanks!!

Bug description

The Certificate details get command handle identifier is wrong in the docs. In the docs it is shows as getDetailedCertificateInfo. The correct identifier is GetDetailedCertificateInfoCmd

Steps to reproduce

1. https://github.com/ms-iot/azure-client-tools/blob/master/docs/device-agent/schema/configuration-groups/certificate-details-get-cmd.md These docs needs to be corrected

Observed behavior

Expected behavior

The handler id should be correct on all pages

Version (please provide the following information):

• OS:
• branch:

Additional notes

Feel free to provide any additional notes.

Hi,
When DeviceInfoPlugin.dll runs to DeviceInfoHandler::OnConnectionStatusChanged will occur error and below is log message:

According to log message,I know that the program error is due to it can't get xml file.
but I don't know what should I do for resolve the problem.

Thanks.

Attempting to install a package using the uwp application management plugin fails with exception code 183 version not found.

This appears to be related to #21 involving setting versioning on a direct method. However, installing an app package uses a desired property and not a direct method. No instructions exist for how to set the serviceInterfaceVersion on a property.

The plugin runs normally when initialized and can execute the direct methods successfully:

GetInstalledUwpAppsCmd
{
    "__meta": {
          "serviceInterfaceVersion": "1.0.0"
    }
}

However when the DesiredProperty is set, the package does not download and the 183 error appears in the log file (see below).

There is a broken link in the documentation that is supposed to explain how to link to Azure Blob Storage https://github.com/ms-iot/azure-client-tools/blob/master/docs/device-agent/schema/configuration-groups/uwpapplication-management.md
"The access to the blob storage is performed as described here"...

Here is our twin segment:

"desired": {
      "uwpApps": {
        "connectionString": "<<Azure storage connection string>>",
        "apps": {
          "<<PackageName>>": {
            "pkgFamilyName": "<<PackageFamilyName>>",
            "version": "1.9.3.1",
            "appxSource": "downloads\\iotcore\\myapp.appx",
            "depsSources": "downloads\\lnl\\Microsoft.NET.CoreRuntime.2.1.appx;downloads\\lnl\\Microsoft.VCLibs.ARM.Debug.14.00.appx",
            "startup": "foreground",
            "launchAfterInstall": true
          }
        }
      },

From DM.Core log:

08-45-23 PM [00000688] [00001240] {
	"__summary" : 
	{
		"deployments" : "",
		"failedCount" : 1,
		"failedGroups" : "uwpApps",
		"pendingCount" : 0,
		"pendingGroups" : "",
		"time" : "2019-05-08T20:45:23"
	},
	"uwpApps" : 
	{
		"__errors" : 
		{
			"uwpApps" : 
			{
				"code" : 183,
				"context" : "uwpApps",
				"message" : "Version not found",
				"parameters" : {},
				"subsystem" : "DeviceAgentPlugin"
			}
		},
		"__meta" : 
		{
			"deploymentId" : "unspecified",
			"deploymentStatus" : "failed",
			"deviceInterfaceVersion" : "",
			"time" : "2019-05-08T20:45:23"
		}
	}
}

From the uwpApps log:
07-44-22 PM [00001996] [00001932] Logging configured.
07-44-22 PM [00001996] [00001932] Microsoft::Azure::DeviceManagement::UwpAppManagementPlugin::UwpAppManagementHandler::OnConnectionStatusChanged
07-44-22 PM [00001996] [00001932] Connection Status: Online.
07-44-23 PM [00001996] [00001932] Microsoft::Azure::DeviceManagement::UwpAppManagementPlugin::UwpAppManagementHandler::Invoke
07-44-23 PM [00001996] [00001932] Microsoft::Azure::DeviceManagement::Common::Operation::RunOperation
07-44-23 PM [00001996] [00001932] Sub-Group: uwpApps
07-44-23 PM [00001996] [00001932] SubSystem : DeviceAgentPlugin
07-44-23 PM [00001996] [00001932] Exception code : 183
07-44-23 PM [00001996] [00001932] Exception debug message: Version not found
07-44-23 PM [00001996] [00001932] Error: [DeviceAgentPlugin] Code: 183, Message: Version not found
07-44-23 PM [00001996] [00001932] Microsoft::Azure::DeviceManagement::Common::ReportedErrorList::AddError
07-44-23 PM [00001996] [00001932] Microsoft::Azure::DeviceManagement::Common::ReportedErrorList::ToJsonObject
07-44-23 PM [00001996] [00001932] Microsoft::Azure::DeviceManagement::Common::ReportedError::ToJsonObject

Hi,

Opening the iot-core-azure-dm-client repository states that the future is in this repository. I have a few questions:

1. Is there any documentation on how to migrate to this new client tools?
2. Are the new tools in this repository backward compatible?
3. I could not find any examples for C# or dotnet. Does it mean that the client tools will only support UWP on cpp?

Hello, friends

Today I try to use Azure Client Tools on Windows 10 IoT Core Build 17763.107. However, it seems that this tool cannot be shown on Microsoft Edge 44.17763.1.0. Meanwhile, it works on Google Chrome. See the picture as follows. The left part is Microsoft Edge, while the right part is Google Chrome. They connect to the same device. And the Azure Client Tools is not shown on Microsoft Edge.

Bug description

I am currently testing the Azure Device Agent on Win10 IoT Enterprise 32bit and 64bit.
However, if you install the UWP app through Device Twin, the application installs, but an error occurs when iotstartup.exe is executed.
And the Reported property has the following error.

"uwpApps": {
"__errors": {
"335344b1-60f3-46a7-927d-d992735bb566": {
"code": -1,
"context": "335344b1-60f3-46a7-927d-d992735bb566",
"message": "invalid map<K, T> key",
"parameters": {},
"subsystem": "unknown"
}
},
"__meta": {
"deploymentId": "app_install1",
"deploymentStatus": "failed",
"deviceInterfaceVersion": "1.0.0",
"time": "2019-07-23T17:32:36Z"
},
"apps": {
"335344b1-60f3-46a7-927d-d992735bb566_65ts46eahwtf2": {
"pkgFamilyName": "335344b1-60f3-46a7-927d-d992735bb566_65ts46eahwtf2",
"version": "not installed"
}
}
}

Also, when I run the Device Agent in debug mode, the following iotstartup.exe error occurs.

09-14-10 AM [00032724] [00031596] property to find = apps
09-14-10 AM [00032724] [00031596] Microsoft::Azure::DeviceManagement::UwpAppManagementPlugin::UwpHelpers::IotStartupExePath
09-14-10 AM [00032724] [00031596] Microsoft::Azure::DeviceManagement::Utils::Process::Launch
09-14-10 AM [00032724] [00031596] Child process has been launched.
09-14-10 AM [00032724] [00031596] Child process has exited.
09-14-10 AM [00032724] [00031596] Command return Code: -214702489409-14-10 AM [00032724] [00031596] Command output : No headed application registered

09-14-10 AM [00032724] [00031596] property to find = startup
09-14-10 AM [00032724] [00031596] Microsoft::Azure::DeviceManagement::UwpAppManagementPlugin::UwpAppManagementHandler::FindApp
09-14-10 AM [00032724] [00031596] Finding package: 335344b1-60f3-46a7-927d-d992735bb566_65ts46eahwtf2
09-14-43 AM [00032724] [00031596] Microsoft::Azure::DeviceManagement::UwpAppManagementPlugin::UwpHelpers::UpdateAppStartup
09-14-43 AM [00032724] [00031596] Updating app startup for: 335344b1-60f3-46a7-927d-d992735bb566_65ts46eahwtf2
09-14-43 AM [00032724] [00031596] Microsoft::Azure::DeviceManagement::UwpAppManagementPlugin::UwpHelpers::IotStartupExePath
09-14-43 AM [00032724] [00031596] Microsoft::Azure::DeviceManagement::UwpAppManagementPlugin::UwpHelpers::GetAppStartupType
09-14-43 AM [00032724] [00031596] Getting app startup for: 335344b1-60f3-46a7-927d-d992735bb566_65ts46eahwtf2
09-14-43 AM [00032724] [00031596] Microsoft::Azure::DeviceManagement::UwpAppManagementPlugin::UwpHelpers::IotStartupExePath
09-14-43 AM [00032724] [00031596] Microsoft::Azure::DeviceManagement::Utils::Process::Launch
09-14-43 AM [00032724] [00031596] Child process has been launched.
09-14-43 AM [00032724] [00031596] Child process has exited.
09-14-43 AM [00032724] [00031596] Command return Code: -214702489409-14-43 AM [00032724] [00031596] Command output : No headed application registered
09-14-43 AM [00032724] [00031596] Generic standard exception occured: invalid map<K, T> key
09-14-43 AM [00032724] [00031596] Microsoft::Azure::DeviceManagement::Common::ReportedErrorList::AddError

Is iotstartup.exe not supported on enterprise?

Version (please provide the following information):

• OS: Windows 10 IoT Enterprise 1809
• branch: master

'RegistryManager.GetDevicesAsync(int)' is obsolete: 'Use CreateQuery("select * from devices", pageSize);' DeviceExplorer

Because of this you cannot use an enumeration. The entire function would need to be modified.

Hi,
I wants to use TRACELINEP interface for prints format message ,
below is my writing:

but can't found this message after program runs.
So I wants to consult What should I write.

Thanks !!

AFAIK, anything capable of connecting to IoTHub can also connect through an Azure Edge instance as though it were a gateway by simply modifying the connection string.
https://docs.microsoft.com/en-us/azure/iot-edge/iot-edge-as-gateway

I was able to muddle my way through the documentation for DeviceAgent and connect my device directly to IoTHub. While I wouldn't say it was "no touch", it did require minimal steps to be performed on the device which was nice. Now instead of directly connecting it to IoTHub, I want to route connections through my edge gateway instance. That should only require DPS to send the Edge connection string to my provisioned device but I don't see any way to do that.

What else changed with the version updated 7 days ago?
azure-client-tools/downloads/device.agent.1.0.0.1.x64.zip
This version only creates 1 log file and will not connect to DPS.
The one prior to this creates 12 log files and works.

Bug description

I can build for x86 and x64 successfully. But when I run build.cmd arm Debug 10.0.16299.0 I get the following error:

d:\sample\azure-client-tools\deps\azure-iot-sdk-c\c-utility\src\gbnetwork.c(14): fatal error C1083: Cannot open include
 file: 'sys/socket.h': No such file or directory [D:\Sample\azure-client-tools\deps\azure-iot-sdk-c\arm\c-utility\aziot
sharedutil.vcxproj]

Steps to reproduce

I followed this document: https://github.com/ms-iot/azure-client-tools/blob/master/docs/limpet/limpet.md#set-up-limpet

Version (please provide the following information):

• OS: Windows 10 1903
• branch: master

Bug description

DMValidator can be configured with an Azure Storage connection string so that if a test needs it, it can be provided. This does not work for direct methods.

Steps to reproduce

1. Configure DMValidator with an Azure Storage connection string.
2. Run the DiagnosticsLog test.

Observed behavior

The test fails to upload files to Azure storage.

Expected behavior

The test should succeed in uploading files to Azure storage.

Version (please provide the following information):

• OS: Windows Enterprise IoT 10.0.17763.437
• branch: master

Is it possible to follow the Quick Start using a Raspberry Pi 3 Model B?

I know, the RPi doesn't have TPM, so I'm using MSFT TPM Simulator.

Where I'm stuck is Configure the Device and Start the Device Agent. as it seems there is no 'Azure Clients' on left pane.

Tested with 10.0.17744.1001 and 10.0.17763.316.

Most of the documentation is for IoT core. I'm not finding a lot of resources for IoT Enterprise. There is a reference that Win10 Enterprise requires embedded mode, but there isn't a mention of why. Is it that the azuredevicemanagementclient.exe needs to be run as an embedded application? Is there more specific documentation and examples for IoT Enterprise connecting to IoT hub?

The docs seem to imply that an out of proc plugin could be implemented in .net. Please create a c# template like you have for c++ and update the docs.

https://github.com/ms-iot/azure-client-tools/blob/master/docs/device-agent/extensibility-and-discovery-model.md