Warning: Undefined variable $file in /customers/a/e/3/tunecom.be/httpd.www/stg_ba12f/wp-content/plugins/fix-my-feed-rss-repair/rss-feed-fixr.php on line 14 Warning: Cannot modify header information - headers already sent by (output started at /customers/a/e/3/tunecom.be/httpd.www/stg_ba12f/wp-content/plugins/fix-my-feed-rss-repair/rss-feed-fixr.php:14) in /customers/a/e/3/tunecom.be/httpd.www/stg_ba12f/wp-includes/rest-api/class-wp-rest-server.php on line 1637 Warning: Cannot modify header information - headers already sent by (output started at /customers/a/e/3/tunecom.be/httpd.www/stg_ba12f/wp-content/plugins/fix-my-feed-rss-repair/rss-feed-fixr.php:14) in /customers/a/e/3/tunecom.be/httpd.www/stg_ba12f/wp-includes/rest-api/class-wp-rest-server.php on line 1637 Warning: Cannot modify header information - headers already sent by (output started at /customers/a/e/3/tunecom.be/httpd.www/stg_ba12f/wp-content/plugins/fix-my-feed-rss-repair/rss-feed-fixr.php:14) in /customers/a/e/3/tunecom.be/httpd.www/stg_ba12f/wp-includes/rest-api/class-wp-rest-server.php on line 1637 Warning: Cannot modify header information - headers already sent by (output started at /customers/a/e/3/tunecom.be/httpd.www/stg_ba12f/wp-content/plugins/fix-my-feed-rss-repair/rss-feed-fixr.php:14) in /customers/a/e/3/tunecom.be/httpd.www/stg_ba12f/wp-includes/rest-api/class-wp-rest-server.php on line 1637 Warning: Cannot modify header information - headers already sent by (output started at /customers/a/e/3/tunecom.be/httpd.www/stg_ba12f/wp-content/plugins/fix-my-feed-rss-repair/rss-feed-fixr.php:14) in /customers/a/e/3/tunecom.be/httpd.www/stg_ba12f/wp-includes/rest-api/class-wp-rest-server.php on line 1637 Warning: Cannot modify header information - headers already sent by (output started at /customers/a/e/3/tunecom.be/httpd.www/stg_ba12f/wp-content/plugins/fix-my-feed-rss-repair/rss-feed-fixr.php:14) in /customers/a/e/3/tunecom.be/httpd.www/stg_ba12f/wp-includes/rest-api/class-wp-rest-server.php on line 1637 Warning: Cannot modify header information - headers already sent by (output started at /customers/a/e/3/tunecom.be/httpd.www/stg_ba12f/wp-content/plugins/fix-my-feed-rss-repair/rss-feed-fixr.php:14) in /customers/a/e/3/tunecom.be/httpd.www/stg_ba12f/wp-includes/rest-api/class-wp-rest-server.php on line 1637 Warning: Cannot modify header information - headers already sent by (output started at /customers/a/e/3/tunecom.be/httpd.www/stg_ba12f/wp-content/plugins/fix-my-feed-rss-repair/rss-feed-fixr.php:14) in /customers/a/e/3/tunecom.be/httpd.www/stg_ba12f/wp-includes/rest-api/class-wp-rest-server.php on line 1637 {"id":977,"date":"2021-01-15T14:24:14","date_gmt":"2021-01-15T14:24:14","guid":{"rendered":"https:\/\/www.tunecom.be\/stg_ba12f\/?p=977"},"modified":"2021-01-15T14:24:16","modified_gmt":"2021-01-15T14:24:16","slug":"how-to-resolve-wvd-agent-service-is-being-stopped-name_already_registered-this-vm-needs-to-be-properly-registered-in-order-to-participate-in-the-deployment","status":"publish","type":"post","link":"https:\/\/www.tunecom.be\/stg_ba12f\/?p=977","title":{"rendered":"How to resolve WVD-Agent service is being stopped: NAME_ALREADY_REGISTERED, This VM needs to be properly registered in order to participate in the deployment"},"content":{"rendered":"\n
On some occasions, you might find yourself battling with an unavailable Windows Virtual Desktop Host in your WVD Host pool and restarting the RDAgentBootLoader service like a maniac.<\/p>\n\n\n\n
The following picture shows our host which is unavailable.<\/p>\n\n\n\n Logged on to the host, we can see that the RDAgentBootloader has stopped.<\/p>\n\n\n\n Looking at the event log of the specific host, you’ll see an error entry each time you try to restart the RDAgentBootLoader service. <\/p>\n\n\n\n Error message: How to resolve WVD-Agent service is being stopped: NAME_ALREADY_REGISTERED, This VM needs to be properly registered in order to participate in the deployment<\/p>\n\n\n\n <\/p>\n\n\n\n Navigate to the host pool section, select your host. When you click on the settings icon, you can remove the host from the host pool.<\/p>\n\n\n\n If you have just installed the RDAgent & RDAgentBootloader, please skip step 2 and go to step 3.1. If you are not sure whether the RDAgent install went fine and you’ve entered a registration key before. Continue here.<\/p>\n\n\n\n Navigate to your host pool and select “Registration key”.<\/p>\n\n\n\n Select “Generate new key”.<\/p>\n\n\n\n Enter an expiration date and time for this specific key and select “OK”.<\/p>\n\n\n\n You can now copy or download the registration key.<\/p>\n\n\n\n Continue to step 3.2<\/p>\n\n\n\n Restart the RDAgentBootloader service or restart the entire virtual machine if you feel more comfortable in doing so.<\/p>\n\n\n\n On your WVD host download the latest version of the following software:<\/p>\n\n\n\n<\/figure>\n\n\n\n
<\/figure>\n\n\n\n
<\/figure>\n\n\n\n
Below you can find the steps to resolve this issue<\/h3>\n\n\n\n
Step 1: Remove the session host from the host pool<\/h4>\n\n\n\n
<\/figure>\n\n\n\n
Step 2: Generate a new host pool registration token<\/h4>\n\n\n\n
<\/figure>\n\n\n\n
<\/figure>\n\n\n\n
<\/figure>\n\n\n\n
<\/figure>\n\n\n\n
Step 3.1: Restart RDAgentBootloader service<\/h4>\n\n\n\n
Step 3.2: Re-install RD Agents<\/h4>\n\n\n\n