Additional domain controller in remote site
-
@IT-ADMIN said:
What about Read Only DC, is it a good idea ??
Doesn't feel like it is needed here. Now that you have the DC at the main site... is it causing a problem?
-
@scottalanmiller said:
@IT-ADMIN said:
What about Read Only DC, is it a good idea ??
Doesn't feel like it is needed here. Now that you have the DC at the main site... is it causing a problem?
no problem at all, but i need a backup logon server in the branch office so that if the VPN go down, ---> users in the branch can login from the DC in the branch
-
but if i have only one DC in the main, if the vpn go down, new login cannot be made, only cached users who can login
-
@IT-ADMIN said:
@scottalanmiller said:
@IT-ADMIN said:
What about Read Only DC, is it a good idea ??
Doesn't feel like it is needed here. Now that you have the DC at the main site... is it causing a problem?
no problem at all, but i need a backup logon server in the branch office so that if the VPN go down, ---> users in the branch can login from the DC in the branch
We don't use one. We use central Domain Controllers and VPN (Pertino) to our offices and don't worry about DCs in the branches. Not a problem at all for us. Branches cache credentials, so no one notices if a DC is unavailable.
-
@IT-ADMIN said:
but if i have only one DC in the main, if the vpn go down, new login cannot be made, only cached users who can login
Correct. How often do you have new logins happening in the branches? Is this common? For us, it would be weeks between new people logging in. Do you hire new people in the branches all of the time? Or do they constantly switch machines?
-
@scottalanmiller said:
@IT-ADMIN said:
but if i have only one DC in the main, if the vpn go down, new login cannot be made, only cached users who can login
Correct. How often do you have new logins happening in the branches? Is this common? For us, it would be weeks between new people logging in. Do you hire new people in the branches all of the time? Or do they constantly switch machines?
yes they switch machines toooooo ofen, no one stay in his machines and create big problem for me, even problem with outlook, i hope they stay in one place but unfortunately they change their places all the time
-
@IT-ADMIN said:
@scottalanmiller said:
@IT-ADMIN said:
but if i have only one DC in the main, if the vpn go down, new login cannot be made, only cached users who can login
Correct. How often do you have new logins happening in the branches? Is this common? For us, it would be weeks between new people logging in. Do you hire new people in the branches all of the time? Or do they constantly switch machines?
yes they switch machines toooooo ofen, no one stay in his machines and create big problem for me, even problem with outlook, i hope they stay in one place but unfortunately they change their places all the time
i'm thinking of RODC in the branch hopefully this project will be successful !!!
-
@IT-ADMIN said:
@scottalanmiller said:
@IT-ADMIN said:
but if i have only one DC in the main, if the vpn go down, new login cannot be made, only cached users who can login
Correct. How often do you have new logins happening in the branches? Is this common? For us, it would be weeks between new people logging in. Do you hire new people in the branches all of the time? Or do they constantly switch machines?
yes they switch machines toooooo ofen, no one stay in his machines and create big problem for me, even problem with outlook, i hope they stay in one place but unfortunately they change their places all the time
Oh, very odd. Yes a DC would be needed then.
-
@scottalanmiller said:
@IT-ADMIN said:
@scottalanmiller said:
@IT-ADMIN said:
but if i have only one DC in the main, if the vpn go down, new login cannot be made, only cached users who can login
Correct. How often do you have new logins happening in the branches? Is this common? For us, it would be weeks between new people logging in. Do you hire new people in the branches all of the time? Or do they constantly switch machines?
yes they switch machines toooooo ofen, no one stay in his machines and create big problem for me, even problem with outlook, i hope they stay in one place but unfortunately they change their places all the time
Oh, very odd. Yes a DC would be needed then.
off course, because we have kind of call center, staff don't care where they sit, they don't have specific software, where ever they find free computer they login into it
-
@scottalanmiller said:
@IT-ADMIN said:
@scottalanmiller said:
@IT-ADMIN said:
What about Read Only DC, is it a good idea ??
Doesn't feel like it is needed here. Now that you have the DC at the main site... is it causing a problem?
no problem at all, but i need a backup logon server in the branch office so that if the VPN go down, ---> users in the branch can login from the DC in the branch
We don't use one. We use central Domain Controllers and VPN (Pertino) to our offices and don't worry about DCs in the branches. Not a problem at all for us. Branches cache credentials, so no one notices if a DC is unavailable.
Sure we do. NTG has 2 datacenter locations, with DCs in each. IT-ADMIN only has 1 datacenter location, so putting a DC at the remote site would be a good idea. If he/she had another datacenter location, it would be less of a concern.
-
Sure we do. NTG has 2 datacenter locations, with DCs in each. IT-ADMIN only has 1 datacenter location, so putting a DC at the remote site would be a good idea. If he/she had another datacenter location, it would be less of a concern.
he not she, hhhh
thanks for your suggestion, i know that the best idea is to have an additional DC in the remote location, i will try another machine and promote it in the branch office, i will not give up, because i doubt the previous ADC has something wrong in its system, if it doesn't work i will try RODC
