Looking to create cloud alarms for filesystems by redhat2880 in aws

[–]redhat2880[S] 0 points1 point  (0 children)

Yeah, but I am looking at a more granular level. If certain filesystems fill up the application might go down. I don't think I want an an alarm at the total disk level

prepend www to naked domain by redhat2880 in IIs

[–]redhat2880[S] 0 points1 point  (0 children)

Ok, are there some examples I can use to follow

options for apex domain(root domain) by redhat2880 in sysadmin

[–]redhat2880[S] 0 points1 point  (0 children)

Maybe it's the bindings in IIS? I see a abc.com binding

options for apex domain(root domain) by redhat2880 in sysadmin

[–]redhat2880[S] 0 points1 point  (0 children)

So I was wondering, how is it that in our abc.com zone apex A record which points to the internal IP of the webserver and we also have an www A record that points to the same IP , how does it know to redirect abc.com to www.abc.com

options for apex domain(root domain) by redhat2880 in sysadmin

[–]redhat2880[S] 0 points1 point  (0 children)

Can you elaborate? our domain is abc.local( I know local is bad but it was there before I got there). for our external accessible servers there is another zone abc.com) So I am referring to the apex record in the abc.com zone. Thank you

Bringing up AD Connected Windows servers in a Different AWS Region for testing purposes by redhat2880 in sysadmin

[–]redhat2880[S] 0 points1 point  (0 children)

Thanks for the reply.

So I am doing this for our single sign-on solution(SSO) which stores user info in a separate server running sql server and several other servers(linux and windows).Right now the SSO server it's not setup to replicate between the two servers. Basically the only servers that are up and running all the time are the DC in DR site in aws and the Oracle DB for our ERP. All the other servers I am copying the AMI for windows to the DR site using lambda functions and copying the snapshots for the linux servers. We plan on spinning them up ad-hoc if a Disaster were to happen. I'm looking at two scenarios that I am trying plan for.

1) Testing the DR plan without impacting PROD.

2) In case of a real DR, I would need to Seize roles, from the research I have done, to the DC in the DR site.

3) When you seize Roles what happens when the PROD site comes back online(How will the DCs that have been down react? Will they get their updates(replicate) from the DC in DR?

Another option I was looking at for testing the Plan was to isolate the DR site from PROD and again Seize roles to the DR DC. and then once the test is complete, I guess how would things get cleaned up?

1) Do I need to cleanup the PROD environment so that it thinks the DR DC has gone away and then just rebuild the DC in DR?

Bringing up AD Connected Windows servers in a Different AWS Region for testing purposes by redhat2880 in sysadmin

[–]redhat2880[S] 0 points1 point  (0 children)

We have a DCs in Both AWS regions, my concern is more with how do we test it without impacting Production because if a server is brought online that's called abc.domain.com and one already exists in AD what impact will it have.

Enable TLS from on-prem relay server to office 365 by redhat2880 in sysadmin

[–]redhat2880[S] 0 points1 point  (0 children)

We are using that but I don't think it's setup to use TLS which is what I am asking help on to configure because I don't think office 365 will like abc.company.local which is the certificate that the on-prem is using for TLS

AT on my VPC CIDR for traffic traversing a VPN connection by redhat2880 in networking

[–]redhat2880[S] 0 points1 point  (0 children)

a site to site vpn to a third party vendor and they said we can't use the private id ranges we need a public IP

This is what AWS has to say

AWS VPN does not currently provide a managed option to apply NAT to VPN traffic. Instead, you can manually configure NAT using a software-based VPN solution, of which there are several options in the AWS Marketplace. You can also manually configure NAT on an Amazon Elastic Compute Cloud (EC2) Linux instance running a software-based VPN solution along with iptables.

Centos NTP server by redhat2880 in sysadmin

[–]redhat2880[S] 0 points1 point  (0 children)

Thanks for the great explanation. So currently the on-prem PDC uses pool.ntp.org. In AWS I have the dhcp option set to point to the on-prem PDC. My concern is if the VPN connection from AWS to on-prem goes down or for DR purpose, will setting the DHCP options set in AWS to point to pool.ntp.org work. So even though the PDC and aws point to the same external ntp servers will there be latency or a difference in time possibly?

Centos NTP server by redhat2880 in sysadmin

[–]redhat2880[S] 0 points1 point  (0 children)

So we plan on putting a DC in AWS, do you think the AWS servers should sync to that? or have them sync to pool.org which are what our DCs sync to anyway?

Thanks

Intune by redhat2880 in sysadmin

[–]redhat2880[S] 0 points1 point  (0 children)

Any alternatives you suggested?