-
- Service Provider
- Posts: 122
- Liked: 17 times
- Joined: Apr 25, 2022 6:18 pm
- Full Name: Bostjan UNIJA
- Contact:
VBR disjoin from domain
Hi.
VBR was a part of a domain now due to Veeam hardening we will disjoin it from domain.
Is disjoining VBR from domain supported?
Or do we need to reinstall VBR?
VBR was a part of a domain now due to Veeam hardening we will disjoin it from domain.
Is disjoining VBR from domain supported?
Or do we need to reinstall VBR?
-
- Veeam Software
- Posts: 2813
- Liked: 641 times
- Joined: Jun 28, 2016 12:12 pm
- Contact:
Re: VBR disjoin from domain
Hi Bostjan,
Yes, it's supported, but please see our KB here for potential side-effects and common solutions. You may not hit all (or any) of these, but these are typically the most common considerations to prepare for.
Yes, it's supported, but please see our KB here for potential side-effects and common solutions. You may not hit all (or any) of these, but these are typically the most common considerations to prepare for.
David Domask | Product Management: Principal Analyst
-
- Service Provider
- Posts: 122
- Liked: 17 times
- Joined: Apr 25, 2022 6:18 pm
- Full Name: Bostjan UNIJA
- Contact:
Re: VBR disjoin from domain
David,
Thank you for your reply.
Thank you for your reply.
-
- Expert
- Posts: 116
- Liked: 31 times
- Joined: Mar 16, 2023 5:47 pm
- Contact:
Re: VBR disjoin from domain
Our Veeam and proxies all run in a workgroup in an isolated vLan. You can certainly do itBostjanUNIJA wrote: ↑Jul 29, 2024 12:12 pm Hi.
VBR was a part of a domain now due to Veeam hardening we will disjoin it from domain.
Is disjoining VBR from domain supported?
Or do we need to reinstall VBR?
-
- Service Provider
- Posts: 122
- Liked: 17 times
- Joined: Apr 25, 2022 6:18 pm
- Full Name: Bostjan UNIJA
- Contact:
Re: VBR disjoin from domain
@pmicheli thank you for your reply.
Yes, we always keep VBR servers outside domain at all customers due to security considirations.
This specific customer had VBR joined into the domain by other IT company and now we are optimising/tweaking the situation.
Yes, we always keep VBR servers outside domain at all customers due to security considirations.
This specific customer had VBR joined into the domain by other IT company and now we are optimising/tweaking the situation.
-
- Service Provider
- Posts: 25
- Liked: 10 times
- Joined: Nov 23, 2017 7:20 am
- Full Name: Jacob Palm
- Contact:
Re: VBR disjoin from domain
We did this a couple of years ago, in an environment with one VBO server and three separate proxy/repository servers. Followed the KB linked to by David above and had zero issues.
-
- Veteran
- Posts: 948
- Liked: 223 times
- Joined: Jul 19, 2016 8:39 am
- Full Name: Michael
- Location: Rheintal, Austria
- Contact:
Re: VBR disjoin from domain
Did that as well some months ago. Didn't know that there was a KB, so I figured it out by myself beforehand. DNS and firewall was the most important aspect, but all in all it went well.
If you disjoin components from the domain and some jobs fail, you can have a look at the job.log, most of the time you get a perfect hint why it failed and then you know what you have to fix.
If you disjoin components from the domain and some jobs fail, you can have a look at the job.log, most of the time you get a perfect hint why it failed and then you know what you have to fix.
-
- Novice
- Posts: 4
- Liked: 3 times
- Joined: Mar 09, 2024 10:54 pm
- Contact:
Re: VBR disjoin from domain
We did this in our environment with our production VBR setup and had zero problems.
-
- Influencer
- Posts: 22
- Liked: 7 times
- Joined: Jul 27, 2022 5:31 am
- Contact:
Re: VBR disjoin from domain
If you were replacing a physical domain-joined VBR server with new hardware in a workgroup, would you
1. disjoin the current server from the domain and make changes, take a config backup and restore to new (workgroup) server, or
2. take a config backup and restore to new server, then fix up domain issues like 'log on as' services?
I can see arguments for both scenarios. Which would you consider cleaner?
1. disjoin the current server from the domain and make changes, take a config backup and restore to new (workgroup) server, or
2. take a config backup and restore to new server, then fix up domain issues like 'log on as' services?
I can see arguments for both scenarios. Which would you consider cleaner?
Who is online
Users browsing this forum: pybfr, Semrush [Bot] and 17 guests