https://community.microfocus.com/cyberres/fortify/fortify-education-after-hours/w/fortify-digital-learning-tips-info/42723/installation-of-fortify-22-1-0-scancentral-dast-in-easy-steps-on-windows-2019-server

check the above link, may be it can help!

Thank you vjohari for rapid answer, but I think this manual is dedicated to docker enviroment configuration. I used it before and it was very helpfull  due to DASTConfigurationToolCLI fight with. 
But I dont get how to configure standalone WI.

check the page no 35 of https://community.microfocus.com/cyberres/fortify/fortify-education-after-hours/w/fortify-digital-learning-tips-info/40038/installation-of-fortify-20-2-0-scancentral-dast-in-easy-steps it may give your some hint.

ok, thanks, that is what I'm looking for. 

So I should:
- unpack "ScanCentral DAST - Sensor Service.zip" package to app folder (f.exmpl. %PathToScannerService%),
- configure appsettings.json file (I used file form DAST.ConfigurationToolCLI) (remember to edit paths)
- create (local or domain) service account, and grant permitions to %AppsPath%
- register service 

sc create ScannerWorkerService binpath= "%PathToScannerService%
\DAST.ScannerWorkerService.exe" start= auto depend= "WebInspect API"
displayname= "WebInspect DAST Scanner Worker Service" obj=".\(custom_service_account)" password="(password)"

In my case when I'had try to start service I received message "Error 1053: The Service did not Respond to the Start or Control Request in a Timely Fashion" .
Starting DAST.ScannerWorkerService.exe in cmd finished with error "The required library hostfxr.dll could not found."

I will try to set %DOTNET_ROOT% variable. 

Thank you vjohari very much for your usefull tips. 

edit:
Thank you ThatCanadaGuy for your tip. 
After "dotNet SDK 5.0.408 (x64)" install scanner service has started.

-- 
Pawel

DAST Sensor Service is installed on Windows Server 2019. "dotNet Framework 4.7 Featues" are installed with Server Manager, but hosfxr.dll file is unavailable. 

When I tried to install .NET Framework 4.8, I received error "NET Framework 4.8 or a later update is already installed on this computer". 
The workaround is to install ".NET Framework 4.8 Developer Pack"

https://dotnet.microsoft.com/download/dotnet-framework/thank-you/net48-developer-pack-offline-installer

File hosfxr.dll is still unavailable despite installing DevPack. Installing dotNet Framework 5.0 doesnt resolve problem too. 

problem still persists

-- 
Pawel

DAST Sensor Service is installed on Windows Server 2019. "dotNet Framework 4.7 Featues" are installed with Server Manager, but hosfxr.dll file is unavailable. 

When I tried to install .NET Framework 4.8, I received error "NET Framework 4.8 or a later update is already installed on this computer". 
The workaround is to install ".NET Framework 4.8 Developer Pack"

https://dotnet.microsoft.com/download/dotnet-framework/thank-you/net48-developer-pack-offline-installer

File hosfxr.dll is still unavailable despite installing DevPack. Installing dotNet Framework 5.0 doesnt resolve problem too. 

problem still persists

-- 
Pawel

I posted a link to our documentation which tells you how to resolve your issue.  Please review the PDF.

Page 86

https://www.microfocus.com/documentation/fortify-ScanCentral-DAST/2210/SC_DAST_Guide_22.1.0.pdf

Also, I wanted to point out that the error messages regarding AMP indicate that you inadvertently were trying to configure the Sensor using the WebInspect Enterprise Sensor configuration screen (e.g. "https://servername/wie/"), within the Fortify Monitor application.  This is only used for WebInspect Enterprise ("WIE"), the predecessor product prior to ScanCentral DAST, and it is not used to configure the SCDAST Sensor you are attempting to build here.  Unfortunately they all get named "Sensor" at some point in the WebInspect User Guide.    :-/

If you are opting for a "bare metal" implementation of your ScanCentral DAST Sensor rather than using the WebInspect Docker image, you will find in the WebInspect User Guide that the process is:

1. Install WebInspect desktop
2. Install an additional client piece ("ScanCentral DAST Sensor Service") to make it into a Sensor
3. Configure the Sensor settings so it dynamically leases the necessary license from the LIM License Server.
4. Sensor connects to and is now visible in the GUI of the ScanCentral DAST Controller (i.e. a pane within the SSC Server screen).

Refs:

https://www.microfocus.com/en-us/support/documentation

> https://www.microfocus.com/documentation/fortify-ScanCentral-DAST/ 

>> https://www.microfocus.com/documentation/fortify-ScanCentral-DAST/2210/ 

>>> https://www.microfocus.com/documentation/fortify-ScanCentral-DAST/2210/SC_DAST_Help_22.1.0/index.htm  (pages 85-89)

Also see:  page 32 of 304 - https://www.microfocus.com/documentation/fortify-ScanCentral-DAST/2210/SC_DAST_Guide_22.1.0.pdf 

Thank you HansEnders for your links too.
Here is many valuable knowledge to acuire :). 

At this moment service has started and registered in SSC console. 
Thank you for your quick and detailed reply.

Have a nice day

-- 
Pawel

Hi Guys,

I have same issue when start service got error 1053, already install dotNet SDK 5.0.408 (x64) still unable to start

I have concern on appsetting.json on line 9 DASTroot URL need fill IP of WI API or DAST API running on Container which already add to SSC?

Because previusly i used DAST API container and also sensor container, got error ssctoken not authenticated. so i try to use WI as a Sensor Service. But got issue error 1053

anyone can give advice

Thanks

Rizal S