How to train on my own dataset?

Hello， I have a batch of expanded images and corresponding ldmk annotations. I want the model to be trained both on 300W and my own data at the same time. How should I do?

Hi, could you give more details, e.g., what do you mean by expanded images? Larger than 256x256?

Hi, could you give more details, e.g., what do you mean by expanded images? Larger than 256x256?

Hi, could you give more details, e.g., what do you mean by expanded images? Larger than 256x256?

Hi， thanks for your qucik reply， I'm going to use a batch of 256*256 face images generated by GAN to expand the 300W training set for training. I read the preprocess.py carefully. In fact, this should be a simple thing. Only need to add the expanded data in 300W and change a little code.


Update marketplace-saas-applications-technical-publishing-guide.md

Updated for upcoming marketplace metering service launch

@msjogarrig : Thanks for your contribution! The author(s) have been notified to review your proposed change. @keithcharlie

Hi @msjogarrig - just fyi:
Microsoft authors and contributors need to make content contributions through the private repository so the content can be staged and validated by the current validation rules.
After you review staging and fix all validation issues, you can tag an author for review or add the sign-off comment to let PR reviewers know that the updates are ready to be merged.
For this PR, we'll need @keithcharlie to review the changes. Or if now, perhaps @qianw211 knows who this PR should be assigned to.

Read about authors working in the public repo for more information.
If you need help getting set up to work in the private repo, see Set up Git repository locally for documentation.

#sign-off

@qianw211: I'm sorry - only the author of this article, @keithcharlie, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.


Fluentd with remote syslog filling up disk on Kubernetes workers

I have deployed the latest image: fluent/fluentd-kubernetes-daemonset:v1.2.5-debian-syslog
What I am seeing is that no logs are making it to my remote syslog endpoint at all, but there are a ton of match warnings in the stdout of the fluentd container, which seem to be caused by the container parsing its own logs.
2018-08-31T18:52:48.411182388Z stdout F \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\"
2018-08-31T18:52:48.411212802Z stdout F 2018-08-31 18:52:48 +0000 [warn]: #0 [in_tail_container_logs] pattern not match: "2018-08-31T18:47:54.867744575Z stdout F \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\""
2018-08-31T18:52:48.411225298Z stdout F 2018-08-31 18:52:48 +0000 [warn]: #0 [in_tail_container_logs] pattern not match: "2018-08-31T18:47:54.867753245Z stdout F 2018-08-31 18:47:54 +0000 [warn]: #0 [in_tail_container_logs] pattern not match: \"2018-08-31T18:45:28.946835964Z stdout F \\\\\\\"\""
2018-08-31T18:52:48.411596643Z stdout P 2018-08-31 18:52:48 +0000 [warn]: #0 [in_tail_container_logs] pattern not match: "2018-08-31T18:47:54.86811204Z stdout P 2018-08-31 18:47:54 +0000 [warn]: #0 [in_tail_container_logs] pattern not match: \"2018-08-31T18:45:28.94717287Z stdout P 2018-08-31 18:45:28 +0000 [warn]: #0 [in_tail_container_logs] pattern not match: \\\"2018-08-31T18:44:16.519536287Z stdout P \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\

The above lines are being written so quickly that it fills 100GB in a couple of hours.
Kubernetes cluster version is: v1.10.2
Here is my YAML configuration, mostly defaults:
apiVersion: v1
kind: ServiceAccount
metadata:
  name: fluentd-sa
  namespace: kube-system

---
kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1
metadata:
  namespace: kube-system
  name: fluentd
rules:
- apiGroups: [""]
  resources: ["pods", "namespaces"]
  verbs: ["get", "watch", "list"]

---
kind: ClusterRoleBinding
apiVersion: rbac.authorization.k8s.io/v1
metadata:
  name: fluentd
roleRef:
  kind: ClusterRole
  name: fluentd
  apiGroup: rbac.authorization.k8s.io
subjects:
- kind: ServiceAccount
  name: fluentd-sa
  namespace: kube-system

---
apiVersion: extensions/v1beta1
kind: DaemonSet
metadata:
  name: fluentd
  namespace: kube-system
  labels:
    k8s-app: fluentd-logging
    version: v1
    kubernetes.io/cluster-service: "true"
spec:
  template:
    metadata:
      labels:
        k8s-app: fluentd-logging
        version: v1
        kubernetes.io/cluster-service: "true"
    spec:
      tolerations:
      - key: node-role.kubernetes.io/master
        effect: NoSchedule
      containers:
      - name: fluentd
        image: fluent/fluentd-kubernetes-daemonset:v1.2.5-debian-syslog
        env:
          - name:  SYSLOG_HOST
            value: "<redacted>"
          - name:  SYSLOG_PORT
            value: "10514"
        resources:
          limits:
            memory: 1000Mi
          requests:
            cpu: 100m
            memory: 1000Mi
        volumeMounts:
        - name: varlog
          mountPath: /var/log
        - name: varlibdockercontainers
          mountPath: /var/lib/docker/containers
          readOnly: true
      serviceAccount: fluentd-sa
      serviceAccountName: fluentd-sa
      terminationGracePeriodSeconds: 30
      volumes:
      - name: varlog
        hostPath:
          path: /var/log
      - name: varlibdockercontainers
        hostPath:
          path: /var/lib/docker/containers

I just wanted to update this issue in case anyone else was curious. The temporary solution that seems to work for now is to modify the fluentd config to exclude the fluentd container logs, and mount the new fluentd config files as a ConfigMap for the DaemonSet.
Here is the modified portion of /fluentd/etc/kubernetes.conf with the exclude_path option:
<source>
  @type tail
  @id in_tail_container_logs
  path /var/log/containers/*.log
  exclude_path ["/var/log/containers/fluentd*"]
  pos_file /var/log/fluentd-containers.log.pos
  tag kubernetes.*
  read_from_head true
  <parse>
    @type json
    time_format %Y-%m-%dT%H:%M:%S.%NZ
  </parse>
</source>

With the other files left as-is, they all have to be added to the ConfigMap because mounting it at a path will overwrite all other files in the directory.
kubectl -n kube-system create configmap fluentd-config --from-file kubernetes.conf --from-file fluent.conf --from-file systemd.conf

Then just add it to the volumes and volumeMounts sections of the DaemonSet
apiVersion: extensions/v1beta1
kind: DaemonSet
metadata:
  name: fluentd
  namespace: kube-system
...
      containers:
      - name: fluentd
        image: fluent/fluentd-kubernetes-daemonset:v1.2.5-debian-syslog
...
        volumeMounts:
        - name: fluentd-config
          mountPath: /fluentd/etc/
        - name: varlog
          mountPath: /var/log
        - name: varlibdockercontainers
          mountPath: /var/lib/docker/containers
          readOnly: true
...
      volumes:
      - name: fluentd-config
        configMap:
          name: fluentd-config
      - name: varlog
        hostPath:
          path: /var/log
      - name: varlibdockercontainers
        hostPath:
          path: /var/lib/docker/containers

With all that said, the problem still exists with the default configuration, and there should be some way for fluentd logs to be sent to the same logging endpoint as the rest of the collected logs.

This should be originated from https://github.com/fluent/fluentd-kubernetes-daemonset/blob/master/templates/conf/kubernetes.conf.erb#L12-L21 and https://github.com/fluent/fluentd-kubernetes-daemonset/blob/master/templates/conf/tail_container_parse.conf.
This is because older fluentd-kubernetes-daemonset images couldn't handle CRI format container logs.
Could you try CRI parser on container logs?
ref: https://github.com/fluent/fluentd-kubernetes-daemonset#use-cri-parser-for-containerdcri-o-logs


Add a CONTRIBUTING.md file to the docs repo

We don't need this.  Nothing other than scripts should be contributing to the docs repo from our team.


Font-weight issue on Chrome browser for active slides

short description of the bug / issue, provide more detail below.

Font-weight getting bolder only on Chrome browser fora active-slide after several click on Next Button.
====================================================================
[ http://codepen.io/vcernomschi/pen/zNEoZo ]
====================================================================
Steps to reproduce the problem

Press 'Next' Button 3 times.
Compare text font-weight for "Pretitle Slide 4" vs "Pretitle Slide 5"

====================================================================
What is the expected behaviour?
Font-weight should be the same for all slides.
====================================================================
What is observed behaviour?
Font-weight has bolder visual effect, but has the same CSS font-weight value;
====================================================================
More Details

Which browsers/versions does it happen on?  Chrome
Which jQuery/Slick version are you using<EMAIL_ADDRESS><EMAIL_ADDRESS>Did this work before? It does not work for slides number more than 5 and depends on slidesToShow and slidesToScroll values.

The issue is reproducible also on simple example on jsfiddle:
http://jsfiddle.net/simeydotme/fmo50w7n/
Please compare visually font-weight for "Fifth Slide" vs "SixSlide"

The Font-weight issue is reproducible only on OS X with Chrome on non-Retina additional display;


Register LazyInverses.jl 1.0.0

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/49194
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v1.0.0 -m "<description of version>" b8e961dd755959dd332ab4e844838eb6064f65d4
git push origin v1.0.0


Time between loglines

As suggested in #46 the time between two loglines is quite often a useful statistic.
In one of the applications running on our cluster, we get loglines like the following :
[2018-11-26 11:12:26 +0000] INFO   com.somejavaclass.redacted.processingnode.verticle.ProcessingJobVerticle Received processing job with jobId: 9bfb55a0-ae31-42c6-a2df-00160e65986c
[2018-11-26 11:12:26 +0000] INFO   com.somejavaclass.redacted.processingnode.verticle.ProcessingJobVerticle Created path for source file: /data/input/0b487e4a-4d65-49b8-a321-4b8a1f83d6b8
[2018-11-26 11:12:26 +0000] FINE   com.somejavaclass.redacted.http.DownloadVerticle Received download message : {"com.somejavaclass.redacted.http.DownloadVerticle.save.path.key":"/data/input/0b487e4a-4d65-49b8-a321-4b8a1f83d6b8","com.somejavaclass.redacted.http.DownloadVerticle.download.url.key":"https://redacted.host.name/source/2F7dMYtNsRkMJGexWfLz-y/Eexz2sMfTiE89Gr536fSMc"}
[2018-11-26 11:12:26 +0000] FINE   com.somejavaclass.redacted.http.ZookeeperVerticle Received resolve url message.
[2018-11-26 11:12:26 +0000] FINE   com.somejavaclass.redacted.http.ZookeeperVerticle Url 'https://redacted.host.name/source/2F7dMYtNsRkMJGexWfLz-y/Eexz2sMfTiE89Gr536fSMc' is not an internal url, using it unmodified.
[2018-11-26 11:12:26 +0000] FINE   com.somejavaclass.redacted.http.DownloadVerticle Found https url, configuring all trusting ssl client options.
[2018-11-26 11:12:26 +0000] INFO   com.somejavaclass.redacted.http.DownloadVerticle Downloading file from 'https://redacted.host.name:-1/source/2F7dMYtNsRkMJGexWfLz-y/Eexz2sMfTiE89Gr536fSMc' and saving to: /data/input/0b487e4a-4d65-49b8-a321-4b8a1f83d6b8
[2018-11-26 11:12:26 +0000] WARNING io.netty.util.internal.logging.Slf4JLogger warn Failed to find a usable hardware address from the network interfaces; using random bytes: d2:41:fa:d0:d3:8c:b6:b9
[2018-11-26 11:12:26 +0000] INFO   com.somejavaclass.redacted.http.DownloadVerticle Beginning download...
[2018-11-26 11:12:29 +0000] FINE   com.somejavaclass.redacted.http.DownloadVerticle Closed file /data/input/0b487e4a-4d65-49b8-a321-4b8a1f83d6b8.
[2018-11-26 11:12:29 +0000] INFO   com.somejavaclass.redacted.processingnode.verticle.ProcessingJobVerticle Download finished from: https://redacted.host.name/source/2F7dMYtNsRkMJGexWfLz-y/Eexz2sMfTiE89Gr536fSMc. File saved at : /data/input/0b487e4a-4d65-49b8-a321-4b8a1f83d6b8

The time between Download started (11:12:26) and Download finished (11:12:29) for a job is actually really interesting to us.
For multiple events, my suggestion for the flow (least confusion and easiest to code) :
11:00 [event 2 fires] (without event 1), do nothing because we have nothing to time against
11:01 [event 1 fires] log time.
11:02 [event 2 fires] check for a tracked event 1 and store the time between now and then and output the metric
11:03 [event 1 fires] log time
11:04 [event 1 fires] log time, overwrite slot
11:05 [event 2 fires] check for a tracked event 1 and store the time between now and then and output the metric (1 minute)
11:06 [event 2 fires] check for a tracked event 1 and store the time between now and then and output the metric (2 minutes because 11:06-11:04)

Whilst this doesn't give the ability to correlate between events, it's the least surprising and easiest to code.  If there is some kind of correlation ID and events might nest or fire asynchronously, a regex for correlation id might be a nice to have, but that requires more storage, and lots more metric buckets.
@fstab thoughts?

Sounds like a good feature, thanks for creating the issue. I will implement it, but first I want to focus on #5, because I've been postponing this for a very long time...


fix(core): Omit unnecessary libraries for web

Description
Currently it seems that unnecessary web libraries are loaded on start of a Flutter Web application.
In our case, we only want to use Firebase Analytics to send tracking data. For this we need to install the firebase_core and firebase_analytics package as dependencies in our project. But when we launch the bundled app in the browser, there are additional JS libraries loaded to the expected firebase-app.js and firebase-analytics.js files. At launch of our app, these JS libraries are loaded.

firebase-app.js
firebase-analytics.js
firebase-app-check.js
firebase-remote-config.js
firebase-firestore.js

The firebase-firestore.jsdependency comes from the firebase_core and firebase_analytics using shared functionality from _flutterfire_internals, which has the cloud_firestore_platform_interface and cloud_firestore_web packages in its dependencies. But there does not seem to be any code used from these dependencies, so it seems that they could be removed.
The firebase-app-check.js and firebase-remote-config.js libraries are loaded because the app-check and remote-config JS libraries are installed as default web services in FirebaseCoreWeb platform interface. I have not found any explanation in the code, why this is necessary, because both web plugins register their web service on plugin registration, when they are added as discrete dependency to a project.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]).
This will ensure a smooth and quick review process. Updating the pubspec.yaml and changelogs is not required.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[x] All existing and new tests are passing.
[x] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (melos run analyze) does not report any problems on my PR.
[x] I read and followed the Flutter Style Guide.
[x] I signed the CLA.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change.
[x] No, this is not a breaking change.

Hey @kaptnkoala - do you intend to update this PR?

@russellwheatley I've update the PR so that web plugins that need override the Firebase Web product name, provide the override when registering them selfs. I felt like that is a more natural place to define those overrides, but let me know what you think.
The necessary change in the firebase_web_core is breaking though.

Thanks @blaugold! This is exactly what was needed. We don't consider this breaking as it is underlying implementation and not user facing API 😄

@blaugold - do you mind merging with master? I think it'll fix the Firestore web e2e tests

@russellwheatley Thanks for the ping. I think that did it.


Database seems not to persist in browser with mode PERM

Which version are you using?
2.3.7
Describe the bug
Data does not persist (after page refresh) in browser with mode: "PERM"
Expected behavior
Database to be persisted
Example
I have included the script the head. Then in the console:
nSQL().createDatabase({
    id: "abc", // can be anything that's a string
    mode: "PERM", // save changes to IndexedDB, WebSQL or SnapDB!
})
// wait

nSQL().listDatabases()
> ["abc"]

** refresh **
nSQL().listDatabases()
> []

I can see however the database is created in IndexedDB

Hello,
I have the same issue and its really a big problem!
same issue with mode "IDB"
-> its not possible to use an existing db, db and tables have to be created each time!
is it an expected behavior?

From docs "Keep in mind that nanoSQL has no way of saving database config data between reloads of your app (only table data), so the createDatabase method should be called on the first and every subsequent app load you intend to use the database in. If the database and tables already exist the createDatabase method just attaches nanoSQL to the existing data, otherwise the tables and indexes are created as needed"

Yes, the createDatabase call along with all the tables and data models needs to be shipped with client side code to persist data across page loads.
If this wasn't the case, you'd have to find a way to detect if each client is a new client (thus no existing database), download the data models from a remote URL (where they would have to be hosted), create the database, then load up everything.  This is far more complicated and unnecessary than just keeping them in the bundle since the create database call and the tables/data models use up minimal space in the client side bundle.


NMOS Controller specification

Squashed version of https://github.com/AMWA-TV/is-05/pull/148 for publication review.

There's a the discrepancy here between the final sentence of the Connection Management section:

When connecting a Receiver to an NMOS Sender, the Controller SHOULD communicate the Sender UUID to the receiver using the sender_id parameter of the /staged endpoint.

and the section Identifying Active Connections which says this:

The Controller MUST set and unset (using null) the sender_id or receiver_id parameters when modifying the transport_params or transport_file.

and the existing wording on the Interoperability with IS-04 page of the spec:

In order to populate the subscription attribute of IS-04 Senders and Receivers, the Connection API includes keys for sender_id and receiver_id in its staged parameters. These SHOULD be used to signal that a Sender or Receiver is being connected to another NMOS compatible Sender or Receiver. It is the client's responsibility to set and unset (using null) the sender_id or receiver_id parameters when modifying the transport_params or transport_file.

I think that the intention is to strengthen the requirement on Controllers so that they MUST correctly set sender_id and receiver_id when they know they're configuring a Receiver or Sender to connect to an NMOS Sender or Receiver as opposed to just configuring transport_params or transport_file, e.g. to point to a non-NMOS Sender/Receiver, in which case sender_id or receiver_id MUST be set to null.
To clarify this, I propose to move the paragraph from Identifying Active Connections into the Connection Management section (it's really nothing to do with interop with IS-04), replacing the single sentence there now.
We could also modify the existing wording on the Interoperability with IS-04 page of the spec? Something like:
< In order to populate the subscription attribute of IS-04 Senders and Receivers, the Connection API includes
< keys for `sender_id` and `receiver_id` in its staged parameters. These SHOULD be used to signal that a
< Sender or Receiver is being connected to another NMOS compatible Sender or Receiver. It is the client's
< responsibility to set and unset (using `null`) the `sender_id` or `receiver_id` parameters when modifying
< the `transport_params` or `transport_file`.
----
> In order to populate the subscription attribute of IS-04 Senders and Receivers, the Connection API includes
> keys for `sender_id` and `receiver_id` in its `/staged` and `/active` endpoints. It is the client's
> responsibility to set and unset (using `null`) the `sender_id` or `receiver_id` parameters when modifying
> the `transport_params` or `transport_file` to signal if a Receiver or Sender is being connected to another
> NMOS compatible Sender or Receiver.


:wheelchair: a11y(dropdown): start focus from selected option

Description of this issue
If nothing is selected when opening this listbox, the first option is focused. If there are selected options, the first selected option is focused when opening.
How to fix it
--
Additional Information
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

/cib


Out of date link?

The link in this section below may need to be updated.

Add the Hybrid Runbook Worker to your subscription by using the procedure at Add Azure Monitor logs to your workspace.

The URL is pointing to https://docs.microsoft.com/en-us/azure/log-analytics/log-analytics-add-solutions, but the page now redirects to https://docs.microsoft.com/en-us/azure/azure-monitor/insights/solutions, which is just a general page about solutions. How would that help you configure HRW on a machine?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: e38be5b8-d76d-a4f1-c014-7bf9248be2de
Version Independent ID: 976e5e90-b28c-d7ba-0495-69d92e62ea46
Content: Deploy a Linux Hybrid Runbook Worker in Azure Automation
Content Source: articles/automation/automation-linux-hrw-install.md
Service: automation
Sub-service: process-automation
GitHub Login: @MGoedtel
Microsoft Alias: magoedte

@dcbrown16  Thank you for your query, we will look into it and get back to you at the earliest.

I see a few things besides what you point out that need to also be addressed with this article.  Bugging now and will prioritize for next month's sprint.  The solution isn't what a customer should be importing into their workspace, rather it should be following what is described in the Windows HRW install article - enable a feature that depends on the workspace (e.g. Update Management or Change Tracking and Inventory).  Thanks!  #please-close