kinton
asked on
AD and Network Migration to the cloud
Overview
We currently host AD on our own servers in our own server room and a second AD (set up with trust) on our remote network hosted at Rackspace. We want to move everything into the cloud. Including AD within the next 30 days.
We use Office 365 and our preference would be to ONLY use the Azure AD within our O365 subscription, however, we believe this may not be possible. We have detailed below our current network configuration.
We would like someone to
a) Provide us with a list of options detailing pros and cons
b) Once we have picked one of the options we would like someone to provide us with a detailed plan explaining how we implement the solution
Current Network Configuration
We have
1. 8 SQL servers
2. 1 File server
3. 3 servers and a SAN making a virtual environment hosting several machine
All servers are windows servers on 2008, 2008r2 and 2012
We currently use AD for
• Local users authentication
• SQL server authentication and user permissions
• Windows server authentication (Windows 2008 onwards)
• External user authentication – we deliver a remote Vb6 application to ‘00’s of external users using RDP who authenticate using our local AD
AD permissions on the above are managed via groups and at individual level. We also use AD to manage our SQL server permissions and group policy to manage devices on the network.
We also have some servers with our hosting partner Rackspace
1. 2 machine cluster hosting our private Virtual environment – hosting web servers and SQL servers (Windows 2016)
2. 2 SQL servers (Windows 2012)
3. Remote AD – with a trust between our AD and Rackspace AD. This means our end users do not need to re-authenticate when using Rackspace.
4. Several SQL databases in the Rackspace cloud (Windows 2016)
Again, at Rackspace we use AD to manage our SQL permissions, all machines at Rackspace are on our own private network set up using Rack connect.
We connect to Rackspace from our office using a VPN
Some key points to note:
• All of our PC’s are on Windows 2010
• Our servers are not all on Windows 2016 (We understand this to be a minimum requirement for servers to authenticate for Azure AD)
• We currently use office 365 as an exchange server
Overview
We currently host AD on our own servers in our own server room and a second AD (set up with trust) on our remote network hosted at Rackspace. We want to move everything into the cloud. Including AD within the next 30 days.
We use Office 365 and our preference would be to ONLY use the Azure AD within our O365 subscription, however, we believe this may not be possible. We have detailed below our current network configuration.
We would like someone to
a) Provide us with a list of options detailing pros and cons
b) Once we have picked one of the options we would like someone to provide us with a detailed plan explaining how we implement the solution
Current Network Configuration
We have
1. 8 SQL servers
2. 1 File server
3. 3 servers and a SAN making a virtual environment hosting several machine
All servers are windows servers on 2008, 2008r2 and 2012
We currently use AD for
• Local users authentication
• SQL server authentication and user permissions
• Windows server authentication (Windows 2008 onwards)
• External user authentication – we deliver a remote Vb6 application to ‘00’s of external users using RDP who authenticate using our local AD
AD permissions on the above are managed via groups and at individual level. We also use AD to manage our SQL server permissions and group policy to manage devices on the network.
We also have some servers with our hosting partner Rackspace
1. 2 machine cluster hosting our private Virtual environment – hosting web servers and SQL servers (Windows 2016)
2. 2 SQL servers (Windows 2012)
3. Remote AD – with a trust between our AD and Rackspace AD. This means our end users do not need to re-authenticate when using Rackspace.
4. Several SQL databases in the Rackspace cloud (Windows 2016)
Again, at Rackspace we use AD to manage our SQL permissions, all machines at Rackspace are on our own private network set up using Rack connect.
We connect to Rackspace from our office using a VPN
Some key points to note:
• All of our PC’s are on Windows 2010
• Our servers are not all on Windows 2016 (We understand this to be a minimum requirement for servers to authenticate for Azure AD)
• We currently use office 365 as an exchange server
We currently host AD on our own servers in our own server room and a second AD (set up with trust) on our remote network hosted at Rackspace. We want to move everything into the cloud. Including AD within the next 30 days.
We use Office 365 and our preference would be to ONLY use the Azure AD within our O365 subscription, however, we believe this may not be possible. We have detailed below our current network configuration.
We would like someone to
a) Provide us with a list of options detailing pros and cons
b) Once we have picked one of the options we would like someone to provide us with a detailed plan explaining how we implement the solution
Current Network Configuration
We have
1. 8 SQL servers
2. 1 File server
3. 3 servers and a SAN making a virtual environment hosting several machine
All servers are windows servers on 2008, 2008r2 and 2012
We currently use AD for
• Local users authentication
• SQL server authentication and user permissions
• Windows server authentication (Windows 2008 onwards)
• External user authentication – we deliver a remote Vb6 application to ‘00’s of external users using RDP who authenticate using our local AD
AD permissions on the above are managed via groups and at individual level. We also use AD to manage our SQL server permissions and group policy to manage devices on the network.
We also have some servers with our hosting partner Rackspace
1. 2 machine cluster hosting our private Virtual environment – hosting web servers and SQL servers (Windows 2016)
2. 2 SQL servers (Windows 2012)
3. Remote AD – with a trust between our AD and Rackspace AD. This means our end users do not need to re-authenticate when using Rackspace.
4. Several SQL databases in the Rackspace cloud (Windows 2016)
Again, at Rackspace we use AD to manage our SQL permissions, all machines at Rackspace are on our own private network set up using Rack connect.
We connect to Rackspace from our office using a VPN
Some key points to note:
• All of our PC’s are on Windows 2010
• Our servers are not all on Windows 2016 (We understand this to be a minimum requirement for servers to authenticate for Azure AD)
• We currently use office 365 as an exchange server
Overview
We currently host AD on our own servers in our own server room and a second AD (set up with trust) on our remote network hosted at Rackspace. We want to move everything into the cloud. Including AD within the next 30 days.
We use Office 365 and our preference would be to ONLY use the Azure AD within our O365 subscription, however, we believe this may not be possible. We have detailed below our current network configuration.
We would like someone to
a) Provide us with a list of options detailing pros and cons
b) Once we have picked one of the options we would like someone to provide us with a detailed plan explaining how we implement the solution
Current Network Configuration
We have
1. 8 SQL servers
2. 1 File server
3. 3 servers and a SAN making a virtual environment hosting several machine
All servers are windows servers on 2008, 2008r2 and 2012
We currently use AD for
• Local users authentication
• SQL server authentication and user permissions
• Windows server authentication (Windows 2008 onwards)
• External user authentication – we deliver a remote Vb6 application to ‘00’s of external users using RDP who authenticate using our local AD
AD permissions on the above are managed via groups and at individual level. We also use AD to manage our SQL server permissions and group policy to manage devices on the network.
We also have some servers with our hosting partner Rackspace
1. 2 machine cluster hosting our private Virtual environment – hosting web servers and SQL servers (Windows 2016)
2. 2 SQL servers (Windows 2012)
3. Remote AD – with a trust between our AD and Rackspace AD. This means our end users do not need to re-authenticate when using Rackspace.
4. Several SQL databases in the Rackspace cloud (Windows 2016)
Again, at Rackspace we use AD to manage our SQL permissions, all machines at Rackspace are on our own private network set up using Rack connect.
We connect to Rackspace from our office using a VPN
Some key points to note:
• All of our PC’s are on Windows 2010
• Our servers are not all on Windows 2016 (We understand this to be a minimum requirement for servers to authenticate for Azure AD)
• We currently use office 365 as an exchange server
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
I am here to help you with your open question. Do you still need help? I have the ability to alert more experts if you still need help.
If you solved the problem on your own, would you please post the solution here in case others have the same problem?
If you need me to delete this question just say "Delete."
Thank you for using Experts Exchange.
Regards,
Kyle Santos
Customer Relations