Hello, what I understand is windows admin center using PowerShelI to connect to target ,that is manage target via Powershell , However,in my case, the default port 5985 is block by security software on my windows 10 client. But it's reachable via port 80 , I try to find an option to use port 80 when I connect to windows 10 client within windows admin center , but seems no way to do that.

Any advise ?

BR

SDK has been broken for some time now, has this repo been officially abandoned?

It seems there has been an upgrade in the wac api as now its importing modules classes from '@microsoft/windows-admin-center-sdk/angular' instead of '@msft-sme/angular' and due to this there is some inconsistency, at least in the wizard control.
I am trying to implement the wizard control and getting the following error :
Error: : Can't bind to 'wizardBuilder' since it isn't a known property of 'sme-wizard'

I am stuck in this for quite sometime now. Any kind of help is appreciated, Thankyou.

Regards.

Create a project wac create --company "{!Company Name}" --tool "{!Tool Name}" with "@microsoft/windows-admin-center-sdk": "4.52.0", however, can't compile successfully

Hi,

I have seen this functionality for extensions provied by Microsoft, but have not found documentation on how to achieve it in custom extensions.

From the "Available Extensions" Tab:

Best Regards

Hi all

Quick Question: Is it possible to develop an extension to manage connections. My idea is creating a custom extension for our company to load all servers as connections from a central database, in our case the CMDB, So none of our admins need to add them manually.

Hello,

I've tried to get Windows credentials using GatewayPlugInIdentityExample code ManageAsIdentityExample.cs
But it throws error:
"The service ICredentials requires the following capabilities which were not declared: UserCredentialsCapability"
at line 36: var credentials = this.GetWindowsCredential(url.TargetNode);

Can you fix this example, please? Or provide a solution how to get Windows credentials in gateway plugin.

Thanks.

Propose changes

Line 17 Link is pointing to 404

original>>>

To actually see the code in action, Use the Extension Manager to find the "Windows Admin Center Developer Tools (Preview)" extension and install it. This will add a new solution to your gateway instance that has tools to help you explore the development environment.

pointing to>>>
https://github.com/microsoft/windows-admin-center-sdk/blob/master/https:/docs.microsoft.com/en-us/windows-server/manage/windows-admin-center/configure/using-extensions...

suggestion:>>>
https://learn.microsoft.com/en-us/windows-server/manage/windows-admin-center/configure/using-extensions

This can be reproduced in the Dev tools available in 1904 build.

1. Go to Settings Control page. Go to tab "multiple forms"
2. Change the value Name to "test"
3. Switch to tab 2.
4. Switch to tab 1.
5. Switch to tab 2.
6. Switch to tab 1. Value "test" is now lost.

There are important files that Microsoft projects should all have that are not present in this repository. A pull request has been opened to add the missing file(s). When the pr is merged this issue will be closed automatically.

Microsoft teams can learn more about this effort and share feedback within the open source guidance available internally.

Merge this pull request

For example, I would like to modify the notification component so that instead of providing a link, I can provide a button which can execute some particular code.

Another example is modifying the header of a DataTable so that I can make it a button instead of text. This could be useful as a "select all" checkbox if all cells in a column are checkboxes.

Yet another example is tooltips. I would like to be able to display a tooltip for a DataTable cell only if the data is cutoff.

There have been other instances where I would love to tweak an existing component as it doesn't quite work as it is provided.

In general is this the place to ask for help with WAC extension development? I have made comments on the doc.microsoft.com site, but never get any response.

I just started developing a WAC extension and managed to get the sample running. The link to the SDK Developer Tools (https://github.com/microsoft/windows-admin-center-sdk/blob/master/windows-admin-center-developer-tools) in the repository is broken. Is this deliberate? The core dependencies (like python 2.x, node 10.x) are pretty old and is there an updated version coming?

Hi @mattatmsft,
We want to call Yarp(microsoft reverse proxy) library to implement our Gateway Plugin. Yarp is developed under .NET5.0, so I try to build this sample under .NET5.0. After deployed this dll to WAC, error appeared when I connect to the gateway, error message is "{"error":{"code":"FileNotFoundException","message":"Could not load file or assembly 'System.Runtime, Version=5.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified."}}"
I'm a new guy in windows .net development, my question is there a way to implement Gateway Plugin under .net5?

I've been able to get the Gateway Plugin example working but due to some other dependencies in my extension I require a minimum of .Net 472. When I build the plugin to target net472 the previously working extension now fails with the following error:

{"error":{"code":"TypeLoadException","message":"Method 'Process' in type 'MyPlugin.SampleHttpPlugIn' from assembly 'MyPlugin, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' does not have an implementation."}}

I'm using the web browser to access the endpoint. Running WAC 1.3.2103.01006.

Has anyone run into this? Is net452 the only target allowed?

All one needs to do to reproduce is to change the target framework to net472 and access the plugin service via a browser.

I have a simple module that shows a dialog after a button press. This works as expected.

this.appContextService.frame.showDialogMessage({
      buttonText: 'OK',
      message: 'This is a test message.',
      title: 'Test'
}).subscribe();

However as soon as I import the WizardModule (in the module.ts imports array) the dialog does not work anymore. The showDialogMessage fails and the following error is printed to the JavaScript console.

company.tool01 -- appErrorHandler -- Rpc: TargetWindows is not configured.
09:54:45.040 logging.js:184 logLevel: Error
09:54:45.040 logging.js:185 timestamp: 2018-09-20T07:54:45.040Z
09:54:45.040 logging.js:192 message: Rpc: TargetWindows is not configured.
09:54:45.040 logging.js:201 stack
09:54:45.040 logging.js:202 Error: Rpc: TargetWindows is not configured.
    at RpcChannel.post (rpc-channel.js:253)
    at RpcInbound.dialog (rpc-inbound.js:167)
    at RpcService.Rpc.dialog (rpc.js:527)
    at FrameService.FrameConnection.requestDialog (frame-connection.js:136)
    at FrameService.FrameConnection.openAndLongPolling (frame-connection.js:121)
    at Observable.eval [as _subscribe] (frame-connection.js:78)
    at Observable._trySubscribe (Observable.js:172)
    at Observable.subscribe (Observable.js:160)
    at DefaultComponent.showDialog (default.component.ts:24)
    at Object.eval [as handleEvent] (DefaultComponent.html:3)

It seems that the WizardModule adds/defines the AppContextService in the wizard.module.js providers array. That reinitializes the RPC service, which breaks the dialog. Can this be somehow avoided?

I tested with multiple versions of WAC (1804.25, 1807, 1808), the SDK (0.533.0, 0.736.0) and different browsers (Edge 42.17134.1.0, Chrome 69).

hi author,
An error occurred during running case by jest

● Test suite failed to run
    Cannot find module './backdrop.component.html' from 'microsoft-windows-admin-center-sdk-angular.umd.js'
      at Resolver.resolveModule (node_modules/jest-resolve/build/index.js:221:17)
      at node_modules/@microsoft/windows-admin-center-sdk/angular/bundles/microsoft-windows-admin-center-sdk-angular.umd.js:710:2039
      at node_modules/@microsoft/windows-admin-center-sdk/angular/bundles/microsoft-windows-admin-center-sdk-angular.umd.js:710:2332
      at node_modules/@microsoft/windows-admin-center-sdk/angular/bundles/microsoft-windows-admin-center-sdk-angular.umd.js:1:109
      at Object.<anonymous> (node_modules/@microsoft/windows-admin-center-sdk/angular/bundles/microsoft-windows-admin-center-sdk-angular.umd.js:1:12840)

package.json

"dependencies": {
        "@angular/animations": "11.2.14",
        "@angular/common": "11.2.14",
        "@angular/core": "11.2.14",
        "@angular/forms": "11.2.14",
        "@angular/platform-browser": "11.2.14",
        "@angular/platform-browser-dynamic": "11.2.14",
        "@angular/router": "11.2.14",
        "@microsoft/windows-admin-center-sdk": "2.166.0",
        "@ngrx/effects": "^11.0.0",
        "@ngrx/router-store": "^11.0.0",
        "@ngrx/store": "^11.0.0",
        "core-js": "2.6.0",
        "rxjs": "6.6.0",
        "zone.js": "0.11.3"
    },
    "devDependencies": {
        "@angular-devkit/build-angular": "0.1102.13",
        "@angular-devkit/build-ng-packagr": "0.1002.0",
        "@angular-devkit/build-optimizer": "0.1102.13",
        "@angular/animations": "11.2.14",
        "@angular/cli": "11.2.14",
        "@angular/common": "11.2.14",
        "@angular/compiler": "11.2.14",
        "@angular/compiler-cli": "11.2.14",
        "@angular/core": "11.2.14",
        "@angular/forms": "11.2.14",
        "@angular/language-service": "11.2.14",
        "@angular/platform-browser": "11.2.14",
        "@angular/platform-browser-dynamic": "11.2.14",
        "@angular/router": "11.2.14",
        "@microsoft/windows-admin-center-sdk": "2.166.0",
        "@ngrx/store-devtools": "^11.0.0",
        "@types/chart.js": "2.9.32",
        "@types/jest": "^22.1.3",
        "@types/node": "^12.11.1",
        "ajv": "6.4.0",
        "ansi-colors": "1.0.1",
        "body-parser": "^1.18.2",
        "chart.js": "2.9.4",
        "codelyzer": "^6.0.0",
        "core-js": "2.6.0",
        "express": "^4.16.2",
        "gulp": "4.0.0",
        "gulp-clean": "0.4.0",
        "gulp-inline-ng2-template": "5.0.1",
        "gulp-jasmine": "4.0.0",
        "gulp-plumber": "1.1.0",
        "gulp-rename": "1.2.2",
        "gulp-sourcemaps": "2.6.4",
        "gulp-tslint": "8.1.3",
        "gulp-watch": "4.3.11",
        "jasmine-reporters": "2.4.0",
        "jest": "^23.6.0",
        "jest-preset-angular": "^6.0.2",
        "jquery": "3.6.0",
        "jsdom": "9.10.0",
        "ng-mocks": "11.10.1",
        "ng-packagr": "11.2.4",
        "plugin-error": "1.0.1",
        "protractor": "~7.0.0",
        "readline-sync": "1.4.9",
        "run-sequence": "2.2.0",
        "rxjs": "6.6.0",
        "rxjs-tslint": "0.1.8",
        "rxjs-tslint-rules": "4.10.0",
        "selenium-webdriver": "3.6.0",
        "ts-helpers": "^1.1.1",
        "ts-jest": "^23.1.4",
        "ts-node": "~8.3.0",
        "tsickle": "0.37.0",
        "tslint": "~6.1.0",
        "tslint-consistent-codestyle": "1.14.0",
        "tslint-eslint-rules": "5.4.0",
        "tslint-microsoft-contrib": "5.2.1",
        "typescript": "4.1.5",
        "zone.js": "0.11.3"
    },
        "jest": {
        "testURL": "http://localhost",
        "preset": "jest-preset-angular",
        "moduleNameMapper": {
            "\\.(jpg|jpeg|png|gif|eot|otf|webp|svg|ttf|woff|woff2|mp4|webm|wav|mp3|m4a|aac|oga)$": "<rootDir>/__mocks__/fileMock.js",
            "\\.(css|less)$": "<rootDir>/__mocks__/styleMock.js"
        },
        "setupTestFrameworkScriptFile": "<rootDir>/src/setupJest.ts",
        "testMatch": [
            "**/src/**/*.spec.ts"
        ],
        "globals": {
            "ts-jest": {
                "tsConfigFile": "<rootDir>/src/tsconfig.spec.json"
            },
            "__TRANSFORM_HTML__": true
        },
        "coveragePathIgnorePatterns": [
            "node_modules/"
        ],
        "transformIgnorePatterns": [
            "node_modules/(?!@ngrx|@microsoft)"
        ]
    }

tsconfig.spec.json

{
  "extends": "../tsconfig.json",
  "compilerOptions": {
    "allowJs": true,
    "module": "commonJs",
    "outDir": "spec",
    "types": ["jest", "node"]
  },
  "files": ["polyfills.ts"],
  "include": ["**/*.spec.ts", "**/*.d.ts", "../__mocks__/*.ts"]
}

How to solve such an error

I'm developing an extension to gateway server with RBAC, however when it's installed, it only show for users in Administrator role. Is that by design, or is there a settings to allow for all roles? This seems not to be covered in documentation.

Thanks

I'm brand new to typescript so this may be a stupid issue :-).

I've followed the MS docs for setting up my environment, then I've downloaded and unziped this repo. When I go to the "windows-admin-center-developer-tools" directory and issue the 'gulp build' command I'm getting an error:

ERROR in D:/MyStuff/Downloads/windows-admin-center-sdk-master/windows-admin-center-sdk-master/windows-admin-center-developer-tools/src/main.ts
Module build failed: Error: D:\MyStuff\Downloads\windows-admin-center-sdk-master\windows-admin-center-sdk-master\windows-admin-center-developer-tools\src\main.ts is missing from the TypeScript compilation. Please make sure it is in your tsconfig via the 'files' or 'include' property.
at AngularCompilerPlugin.getCompiledFile (D:\MyStuff\Downloads\windows-admin-center-sdk-master\windows-admin-center-sdk-master\windows-admin-center-developer-tools\node_modules@ngtools\webpack\src
angular_compiler_plugin.js:662:23)
at plugin.done.then (D:\MyStuff\Downloads\windows-admin-center-sdk-master\windows-admin-center-sdk-master\windows-admin-center-developer-tools\node_modules@ngtools\webpack\src\loader.js:467:39)
at
@ multi ./src/main.ts

I'm not sure how to fix this as in the tsconfig it seems that the pattern src***.ts should include 'src\main.ts'.

Trying to follow the provided SDK example guides at this stage is not complete enough to actually get anything working except perhaps a tool icon showing up under the extensions as side loaded but does nothing.

If I had the matching 'sample' project to the documentation I could check where I went wrong and this would be a huge help.

I'd love to progress the ability to write an extension, so ANYONE with a small working example from a tool, module & solution to using PowerShell and gateways etc would be most welcome.

Hello,

We've updated @microsoft/windows-admin-center-sdk
Now we cannot build our solutions: there are lot of changes in sdk. And it is not documented anywhere.
E.g.
https://docs.microsoft.com/en-us/windows-server/manage/windows-admin-center/extend/guides/create-connection-provider
Here there are code samples, but the new sdk has no this.appContextService.rpc.updateData method anymore. So how can we add new connections?
Paths for imported modules were changed too.
Can you provide uptodate documentation for developers?

Also, Developer Tools extension is not available now. Are you bring it back and when?

Thanks

I have already known the solutionIds for server and windows client by reading the example extension template. But what are the solutionIds and connectionTypes for failover and hyper-converged cluster ? I need to know to fulfill in the manifest.json file.

hi,
I tried to load my dev tool extension created after following the steps mentioned in https://docs.microsoft.com/en-us/windows-server/manage/windows-admin-center/extend/develop-tool

but when i run gulp serve -p 4201 nothing happens.

installed wac in dev mode. "msiexec /i WindowsAdminCenter1910.msi DEV_MODE=1"
2 .i ran the gulp command from cmd line
3. i went to wac browser and on console dialog (after pressing f12 in browser) i gave "MsftSme.sideLoad("http://localhost:4201")"
4 then i refresh my browser but my new extension is never loaded.
Please help

Hi ,
Our project need a WAC gateway plugin to communicate with node.
Under WAC DEV_MODE, we can use HTTP to communicate with gateway plugin successfully.
But for security purpose, we need use HTTPs to communicate with plugin gateway. We found that, if we want to use HTTPS, we should not use DEV_MODE. So we reinstall WAC without DEV_MODE opt. But after we copy dll to plugins director, the WAC can not restart, the log shows the error below, seems we need to sign the dll.

Then, we signed the dll, this time, the error disappeared, WAC can start. But we got another error when we try to access the gate plugin from browser.

I wonder the correct way to using https in gateway plugin. Do we need to use a special certificate to sign the dll? Is there any special steps?

Running NPM INSTALL after WAC CREATE result in the following error:

`> [email protected] install C:\Code\wac\demo01\OPTION-Migration-Suite\node_modules\node-sass

node scripts/install.js

Downloading binary from https://github.com/sass/node-sass/releases/download/v4.10.0/win32-x64-72_binding.node
Cannot download "https://github.com/sass/node-sass/releases/download/v4.10.0/win32-x64-72_binding.node":`

As a consequense the build fails

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] postinstall: node scripts/build.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2019-07-16T19_49_52_350Z-debug.log

Hey All,

i have just started looking into Windows Admin Center development and followed this guide:
https://docs.microsoft.com/de-de/windows-server/manage/windows-admin-center/extend/prepare-development-environment
to setup my development environment.

After that i started my first project with wac create like pointed out in this guide:
https://docs.microsoft.com/de-de/windows-server/manage/windows-admin-center/extend/develop-solution

But then i try to install the dependencies with npm install all i get is a bunch of deprecated and error messages (for example its checking for pyhton2 that is EOL since 2020-01-01).

I am pretty new to typescript development so pardon me if i miss something .. but for me it looks like the wac sdk is pretty outdated.

Please point me into the right direction where i can find updated documentation/wac sdk. I really like to start developing for wac :-)

Thx in advance and best regards
Mirko

Hi,

first of all, I'm pretty new to Angular and Typescript so my question might be a bit noob-ish...

I just cloned the sdk repo and tried to build the Developer Tools which told me to not Build the Sample but create a new Extension using the CLI and "reference?" example source.

So I just created a new Extension using the CLI and tried to Sideload it into Admin Center which then showed the string "Congratulations, you have now created a new Windows Admin Center extension!". So basicly I was able to sideload a new Extension.

Then I removed the "src" Folder of my created Extension and copied the "src" Folder from the Developer Tools over to my Extension. After fixing an Issue in the alert-bar-example Component the build was successfull. When starting the Server with "Gulp serve" everyhing seemed to work fine, but when trying to sideload the modified Extension I doesn't even show up as sideloaded extension. There is not even an error Message in the Output.

So what do I have to do to get the Dev Tools working from wihin Admin Center?

A more step by step guide of "how to run the Dev Tools" would be nice instead of linking to the Documentation of how to create an empty extension.

Thanks and kind regards

Issue: examples, such as FormTest, do not build with gulp

(Disclaimer: I'm new to this, so user error is extremely likely)

Steps to Reproduce:

1. Prepare environment per https://docs.microsoft.com/en-us/windows-server/manage/windows-admin-center/extend/prepare-development-environment
2. Clone sdk repo, cd to Examples\FormTest
3. Run npm install
4. Run gulp build

Environment:
windows-admin-center-sdk: 1.278.0
windows-admin-center-cli: 0.1.26

Output:

PS .\Examples\FormTest> gulp build
[18:03:19] Using gulpfile .\Examples\FormTest\gulpfile.js
[18:03:19] Starting 'build'...
[18:03:19] Starting 'clean'...
[18:03:19] Finished 'clean' after 44 ms
[18:03:19] Starting 'generate'...
[18:03:19] Starting 'generate-powershell'...
[18:03:19] Starting 'generate-svg'...
[18:03:19] Starting 'generate-resjson'...
[18:03:19] Starting 'generate-resjson-json'...
[18:03:19] Starting 'generate-resjson-interface'...
(node:3784) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
[18:03:19] Finished 'generate-resjson-json' after 25 ms
[18:03:19] Finished 'generate-resjson-interface' after 25 ms
[18:03:19] Starting 'merge-localized-json'...
[18:03:19] Finished 'generate-svg' after 38 ms
[18:03:19] Finished 'merge-localized-json' after 6.72 ms
[18:03:19] Finished 'generate-resjson' after 39 ms
[18:03:19] Finished 'generate-powershell' after 58 ms
[18:03:19] Finished 'generate' after 60 ms
[18:03:19] Starting 'lint'...
[18:03:23] Finished 'lint' after 3.6 s
[18:03:23] Starting 'inline'...
[18:03:23] Finished 'inline' after 191 ms
[18:03:23] Starting 'compile'...
[18:03:23] Starting 'copy'...
Error at ./FormTest/node_modules/@microsoft/windows-admin-center-sdk/core/rpc/rpc-base.d.ts:158:13: Cannot find namespace 'MsftSme'.
Error at ./FormTest/node_modules/@microsoft/windows-admin-center-sdk/core/rpc/rpc-base.d.ts:161:15: Cannot find namespace 'MsftSme'.
Error at ./FormTest/node_modules/@microsoft/windows-admin-center-sdk/core/rpc/rpc-base.d.ts:161:33: Cannot find namespace 'MsftSme'.
Error at ./FormTest/node_modules/@microsoft/windows-admin-center-sdk/core/security/authorization-manager.d.ts:60:17: Cannot find namespace 'MsftSme'.
Error at ./FormTest/node_modules/@microsoft/windows-admin-center-sdk/core/security/authorization-manager.d.ts:61:30: Cannot find namespace 'MsftSme'.
Error at ./FormTest/node_modules/@microsoft/windows-admin-center-sdk/core/security/authorization-manager.d.ts:76:17: Cannot find namespace 'MsftSme'.
Error at ./FormTest/node_modules/@microsoft/windows-admin-center-sdk/core/security/authorization-manager.d.ts:166:71: Cannot find namespace 'MsftSme'.
Error at ./FormTest/node_modules/@microsoft/windows-admin-center-sdk/core/data/disposable.d.ts:10:42: Cannot find namespace 'MsftSme'.
Error at ./FormTest/node_modules/@microsoft/windows-admin-center-sdk/core/manifest/environment-modules.d.ts:37:18: Cannot find namespace 'MsftSme'.
Error at ./FormTest/node_modules/@microsoft/windows-admin-center-sdk/core/manifest/environment-modules.d.ts:94:53: Cannot find namespace 'MsftSme'.
Error at ./FormTest/node_modules/@microsoft/windows-admin-center-sdk/core/manifest/environment-modules.d.ts:160:23: Cannot find namespace 'MsftSme'.
Error at ./FormTest/node_modules/@microsoft/windows-admin-center-sdk/core/manifest/environment-modules.d.ts:257:21: Cannot find namespace 'MsftSme'.
Error at ./FormTest/node_modules/@microsoft/windows-admin-center-sdk/core/manifest/environment-modules.d.ts:279:17: Cannot find namespace 'MsftSme'.
Error at ./FormTest/node_modules/@microsoft/windows-admin-center-sdk/core/manifest/environment-modules.d.ts:482:14: Cannot find namespace 'MsftSme'.
Error at ./FormTest/node_modules/@microsoft/windows-admin-center-sdk/core/manifest/environment-modules.d.ts:498:9: Cannot find namespace 'MsftSme'.
Error at ./FormTest/node_modules/@microsoft/windows-admin-center-sdk/core/manifest/environment-modules.d.ts:499:11: Cannot find namespace 'MsftSme'.
Error at ./FormTest/node_modules/@microsoft/windows-admin-center-sdk/core/manifest/environment-modules.d.ts:543:31: Cannot find namespace 'MsftSme'.
Error at ./FormTest/node_modules/@microsoft/windows-admin-center-sdk/core/manifest/environment-modules.d.ts:547:29: Cannot find namespace 'MsftSme'.
Error at ./FormTest/node_modules/@microsoft/windows-admin-center-sdk/core/manifest/environment-modules.d.ts:555:36: Cannot find namespace 'MsftSme'.
Error at ./FormTest/node_modules/@microsoft/windows-admin-center-sdk/core/manifest/environment-modules.d.ts:559:34: Cannot find namespace 'MsftSme'.
Error at ./FormTest/node_modules/@microsoft/windows-admin-center-sdk/core/manifest/environment-modules.d.ts:620:14: Cannot find namespace 'MsftSme'.
Error at ./FormTest/node_modules/@microsoft/windows-admin-center-sdk/core/security/connection.d.ts:5:47: Cannot find namespace 'MsftSme'.
Error at ./FormTest/node_modules/@microsoft/windows-admin-center-sdk/core/security/connection.d.ts:11:43: Initializers are not allowed in ambient contexts.
Error at ./FormTest/node_modules/@microsoft/windows-admin-center-sdk/core/security/connection.d.ts:12:36: Initializers are not allowed in ambient contexts.
Error at ./FormTest/node_modules/@microsoft/windows-admin-center-sdk/core/security/connection.d.ts:13:43: Initializers are not allowed in ambient contexts.
Error at ./FormTest/node_modules/@microsoft/windows-admin-center-sdk/core/security/connection.d.ts:14:44: Initializers are not allowed in ambient contexts.
Error at ./FormTest/node_modules/@microsoft/windows-admin-center-sdk/core/data/websocket-stream.d.ts:99:14: Cannot find namespace 'MsftSme'.
Error at ./FormTest/node_modules/@microsoft/windows-admin-center-sdk/core/base/json.d.ts:13:37: Cannot find namespace 'MsftSme'.
Error at ./FormTest/node_modules/@microsoft/windows-admin-center-sdk/core/data/asset-manager.d.ts:15:39: Cannot find namespace 'MsftSme'.
Error at ./FormTest/node_modules/@microsoft/windows-admin-center-sdk/core/data/powershell-alternate.d.ts:14:39: Initializers are not allowed in ambient contexts.
Error at ./FormTest/node_modules/@microsoft/windows-admin-center-sdk/core/dom/dom.d.ts:163:57: Cannot find namespace 'MsftSme'.
Error at ./FormTest/node_modules/@microsoft/windows-admin-center-sdk/core/shared/cluster-inventory/cluster-inventory.d.ts:64:14: Cannot find namespace 'MsftSme'.
Error at ./FormTest/node_modules/@microsoft/windows-admin-center-sdk/core/shared/cluster-inventory/cluster-inventory.d.ts:126:14: Cannot find namespace 'MsftSme'.
Error at ./FormTest/node_modules/@microsoft/windows-admin-center-sdk/core/data/extension-broker/model/extension-broker-response-payload.d.ts:71:49: Cannot find namespace 'MsftSme'.
Error at ./FormTest/node_modules/@microsoft/windows-admin-center-sdk/core/data/extension-broker/model/extension-instance.d.ts:15:18: Cannot find name 'DOMRect'.
Error at ./FormTest/node_modules/@microsoft/windows-admin-center-sdk/core/data/extension-broker/model/extension-broker-request-payload.d.ts:95:11: Cannot find name 'DOMRect'.
Error at ./FormTest/inlineSrc/app/app-routing.module.ts:3:31: Cannot find module '@microsoft/windows-admin-center-sdk/angular'.
Error at ./FormTest/inlineSrc/app/app.component.ts:2:76: Cannot find module '@microsoft/windows-admin-center-sdk/angular'.
Error at ./FormTest/inlineSrc/app/app.module.ts:18:8: Cannot find module '@microsoft/windows-admin-center-sdk/angular'.
Error at ./FormTest/inlineSrc/app/default/default.module.ts:5:32: Cannot find module '@microsoft/windows-admin-center-sdk/angular'.
[18:03:32] 'compile' errored after 9.05 s
[18:03:32] Error in plugin 'gulp-ngc'
Message:
    Compilation error.
See details in the ngc output
Details:
    fileName: .\FormTest\tsconfig-inline.json
[18:03:32] 'build' errored after 13 s
[18:03:32] Error in plugin 'run-sequence(compile)'
Error
    at finish (.\FormTest\node_modules\run-sequence\index.js:81:12)
    at Gulp.onError (.\FormTest\node_modules\run-sequence\index.js:92:3)
    at Gulp.emit (events.js:194:15)
    at Gulp.Orchestrator._emitTaskDone (.\FormTest\node_modules\orchestrator\index.js:264:8)
    at .\FormTest\node_modules\orchestrator\index.js:275:23
    at finish (.\FormTest\node_modules\orchestrator\lib\runTask.js:21:8)
    at DestroyableTransform.<anonymous> (.\FormTest\node_modules\orchestrator\lib\runTask.js:52:4)
    at DestroyableTransform.f (.\FormTest\node_modules\orchestrator\node_modules\once\once.js:17:25)
    at DestroyableTransform.emit (events.js:194:15)
    at onwriteError (.\FormTest\node_modules\readable-stream\lib\_stream_writable.js:449:12)
[18:03:32] Finished 'copy' after

It's not compiling/ running!
There seems to be a problem with the dependencies.
Could you please update them?

this sdk has a set of usefull angular component
It'll be great if you can open source thous components and make it as separte project

a preview in powerpoint is not enough, we need sample codes to rapid coding.

Hi,
in the new version of windows-admin-center-sdk the form fields have started to act extremely weird. Some of them are now stacked horizontally and some of them are stacked vertically. Inspecting the elements shows that a new class has appeared: sme-form-field-orientation-horizontal or sme-form-field-orientation-vertical. There is no consistency or a possibility to set it myself.
E.g.:

because plugin's constructor is lazy loading,
sometimes if lots of requests comes in and the constructor is not finished quickly, sme initiate second instance of plugin.

we notice this symptom many times, we only use 4 concurrent requests.

Hi ,
I try the Gateway Plugin sample, build and put the DLL to target directory.

Then as the document said , I restart the Windows Admin Center process.

But it can't be started.

Log at EVENT VIEW:

Can you offer some suggestions on how to troubleshoot this problem?

Hello, what I understand is windows admin center using PowerShelI to connect to targets ,that is manage target via Powershell , However,in my case, the default port 5985 is block by security software on my windows 10 client. But winrm can listen on 5985 and 80 at the same time, by enable EnableCompatibilityHttpListener ,than poewershell can reach remote target with 80 , but in WAC there is no way to instruct powershell to use another port ,only the default behavior.WAC should make an improvement on this matter.

-- This is the second time for this question , I hope someone can give me some tips

Hi there,

is there any documentation available on how to use, for example the sme-pivot style to get a tabbed experience?

I must be doing something wrong, as I always get the error "Pivot must contain child tabs. Expected at least one (1) tab".

Regards