{"id":962,"date":"2020-09-08T13:24:23","date_gmt":"2020-09-08T18:24:23","guid":{"rendered":"http:\/\/zewwy.ca\/?p=962"},"modified":"2021-08-17T10:46:04","modified_gmt":"2021-08-17T15:46:04","slug":"veeam-adding-a-windows-managed-server","status":"publish","type":"post","link":"https:\/\/zewwy.ca\/index.php\/2020\/09\/08\/veeam-adding-a-windows-managed-server\/","title":{"rendered":"Veeam &#8211; Adding a Windows Managed Server"},"content":{"rendered":"<p>Unlike most other blog posts that seem to love to follow the &#8220;happy path&#8221;, that never happens with me so I&#8217;m going to go over this cause something WILL go wrong&#8230;<\/p>\n<p><a href=\"https:\/\/helpcenter.veeam.com\/docs\/backup\/hyperv\/add_windows_server.html?ver=100\">Pre-required reading.<\/a><\/p>\n<p>Now I got this as my first error attempting to add the server:<\/p>\n<p><a href=\"https:\/\/i.imgur.com\/H3hJj9y.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter\" src=\"https:\/\/i.imgur.com\/H3hJj9y.png\" alt=\"\" width=\"364\" height=\"138\" \/><\/a><\/p>\n<p>Things to check here:<\/p>\n<ol>\n<li>Network and services:<br \/>\nIn my case first issue was DNS, and DNS cache, since I added a newly created hostname the Veeam server was attempting to query it&#8217;s local DNS cache, I had to ensure all DNS servers had a valid record (nslookup\/dig) then validate those on the local system (ping) which failed and required a local DNS cache flush (ipconfig \/flushdns).Also make sure you didn&#8217;t click &#8220;No&#8221; when connected to the network, else it would have set the firewall zone to &#8220;Public&#8221;, <a href=\"https:\/\/winaero.com\/blog\/network-location-type-powershell-windows-10\/\">change it back to Private<\/a> or open the firewall accordingly.<\/li>\n<li>File and Print Services on target:<br \/>\nNext I had to create a temp share folder to ensure share services were started (since I was using Windows 10, and not Server 2016\/2019), otherwise much like others have mentioned&#8230; somewhere (I&#8217;ll link if I find the Veeam thread again).<\/li>\n<li>This can also show up if the user account is incorrectly entered or if used as &#8220;.\\user&#8221;. <a href=\"https:\/\/forums.veeam.com\/veeam-backup-replication-f2\/failed-to-create-persistent-connection-to-admin-t36932.html\">While this was stated as a solution to an alternative issue<\/a> (to be mentioned below), I got the error above using the account in that syntax. I had to use &#8220;HOSTNAME\\USERNAME&#8221;.<\/li>\n<\/ol>\n<p>The second error I got was:<\/p>\n<p><a href=\"https:\/\/i.imgur.com\/fc1wc30.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter\" src=\"https:\/\/i.imgur.com\/fc1wc30.png\" alt=\"\" width=\"422\" height=\"199\" \/><\/a><\/p>\n<p>Things to check here:<\/p>\n<ol>\n<li>Are you using local accounts? (Managed Server being added not part of domain) More than likely yes (otherwise you haven&#8217;t granted the domain account local administrative rights on the server being added).In this case <a href=\"https:\/\/forums.veeam.com\/veeam-backup-replication-f2\/failed-to-create-persistent-connection-to-admin-t36932.html\">as covered in this Veeam thread.<\/a><\/li>\n<\/ol>\n<p>This issue is not Veeam specific rather MS specific, <a href=\"https:\/\/support.microsoft.com\/en-ca\/help\/951016\/description-of-user-account-control-and-remote-restrictions-in-windows\">which has been the case since the inception of Windows Vista<\/a>.<\/p>\n<p>If you are in this boat you have 3 options:<\/p>\n<ol>\n<li>Join the host to the same domain as Veeam. Created a dedicated domain account and place into the managed server local admins groups (preferably via GPO).*Most recommend\n<p>If domain joining is out of the question these are the other 2 options&#8230;<\/li>\n<li>Enable and use the built in local administrator account &#8220;HOSTNAME\\Administrator)*Recommend if domain join not possible (It&#8217;s less likely that this account would be directly compromised vs the alternative solution). This is also mentioned by Gostev directly in the Veeam thread shared above.<\/li>\n<li>\u00a0<a href=\"https:\/\/www.adamcouch.co.uk\/localaccounttokenfilterpolicy-accessing-the-c-with-a-local-account\/\">Disable UAC for local account to utilize remote calls<\/a>:<\/li>\n<\/ol>\n<pre>cmd \/c reg add HKLM\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Policies\\system \/v LocalAccountTokenFilterPolicy \/t REG_DWORD \/d 1 \/f<\/pre>\n<p>This adds a reg key to disable UAC. as Mentioned by Gostev why this isn&#8217;t done automatically as it&#8217;s a security risk. No solution seems good here (besides domain joining). In this case it&#8217;s better to just use to local admin account&#8230; ughhh.<\/p>\n<p><a href=\"https:\/\/i.imgur.com\/5m61rDw.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter\" src=\"https:\/\/i.imgur.com\/5m61rDw.png\" alt=\"\" width=\"765\" height=\"543\" \/><\/a><\/p>\n<p>and sure enough using the local administrator account worked and the wizard moved on&#8230;<\/p>\n<p><a href=\"https:\/\/i.imgur.com\/0mTfRbx.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter\" src=\"https:\/\/i.imgur.com\/0mTfRbx.png\" alt=\"\" width=\"765\" height=\"535\" \/><\/a><\/p>\n<p>The rest of it&#8217;s a wizard, if you got to this point there should be no other major issues moving on&#8230;<\/p>\n<p>*UPDATE* Veeam 11, if you can&#8217;t get option 2 to work, you&#8217;ll have to update to Veeam 11a, whenever that&#8217;s set to be released. See <a href=\"https:\/\/forums.veeam.com\/vmware-vsphere-f24\/v-11-lacks-backwards-compatibility-related-to-vix-guest-processing-t74994.html\">this Veeam Forum post<\/a> for more details. Only option for V11 is to disable UAC&#8230; :S<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Unlike most other blog posts that seem to love to follow the &#8220;happy path&#8221;, that never happens with me so I&#8217;m going to go over this cause something WILL go wrong&#8230; Pre-required reading. Now I got this as my first error attempting to add the server: Things to check here: Network and services: In my &hellip; <\/p>\n<p class=\"link-more\"><a href=\"https:\/\/zewwy.ca\/index.php\/2020\/09\/08\/veeam-adding-a-windows-managed-server\/\" class=\"more-link\">Continue reading<span class=\"screen-reader-text\"> &#8220;Veeam &#8211; Adding a Windows Managed Server&#8221;<\/span><\/a><\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"sfsi_plus_gutenberg_text_before_share":"","sfsi_plus_gutenberg_show_text_before_share":"","sfsi_plus_gutenberg_icon_type":"","sfsi_plus_gutenberg_icon_alignemt":"","sfsi_plus_gutenburg_max_per_row":"","footnotes":""},"categories":[8,236],"tags":[298,82],"class_list":["post-962","post","type-post","status-publish","format-standard","hentry","category-server-administration","category-veeam","tag-managed-server","tag-veeam"],"_links":{"self":[{"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/posts\/962","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/comments?post=962"}],"version-history":[{"count":3,"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/posts\/962\/revisions"}],"predecessor-version":[{"id":1211,"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/posts\/962\/revisions\/1211"}],"wp:attachment":[{"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/media?parent=962"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/categories?post=962"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/zewwy.ca\/index.php\/wp-json\/wp\/v2\/tags?post=962"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}