Description: The article is about microsoft office 365 login. You can learn the fundamentals of an Office 365 migration. You can read the topics about traditional infrastructure basics,standard challenges and types of migration.
Today’s whiteboard session is going to be a high-level overview of Microsoft Office 365. We have a traditional infrastructure with the standard layout,starting at the top you have your file servers which will serve multiple roles within your environment,you will have your user home drives,you also have shared storage that can be utilized across your environment.
Second,you have Active Directory,this controls all of your users and your authentication both internally,your remote users who are utilizing VPN will come in. You have your exchange server which is your mail server,that’s used to communicate both internally across your environment as well as clients and your external users.
Going along with your exchange,you also need a mail archive,this will store all of your old mail based on whatever retention policies you have set,you’re going to need some backup attached to that. You also have all of your end-users that are utilizing all of this infrastructure internally whether there’s the connectivity or not.
Let’s talk about some of the challenges that revolve around an infrastructure. First of all,with all of these servers in this small scale version,we have eight physical servers,that’s a lot of maintenance for a single individual of this size.
The second thing that you need to take into account is your server migrations or upgrades,that goes for operating systems and software within your environment. The third thing that you need to take into account is that all of this is required by your end-users,it means you have to have some backup,disaster recovery or some off site usage capability.
The final component that becomes a major challenge is resources. You have power cooling and network,they are all utilized by every one of these devices. After you’ve decided to migrate,the next thing is evaluation. The first thing that you must do is to take a look at your current environment to make sure that it supports the cloud-based solutions that you are investigating.
What items should you and your team evaluate? You need to start with network traffic capabilities,the internet speed,versions of software both server and user based,user count,the data size,the user roles and the needs of each one of those users.
When it comes to the who section,you should break things down by department,user type,location and primary work location,when it comes to the what section,you should make a list of what will change and how it will change not for your users but also for you as the administrator.
Everything will be affected in your network from where your files are stored to how your users authenticate to specific resources,from where the mail flow comes from to how things are archived and how your remote users interact with your network and the resources.
You need to evaluate licensing needs,based on the list that you’ve made,you should be able to determine the licensing needs of those users. One of the best updates made to office 365 last year was the ability to mix and match licensing,which means you’re no longer bound to one type of license for all of your users,it can be a huge cost saving benefit to your environment,let’s take a minute to talk about the different types of migrations that you could utilize within your environment.
The first one is a remote move migration,you will use this for one or two reasons. If you’re going to do an exchange hybrid deployment with mailboxes both on-premise and cloud based or if you’re going to move mailboxes over a long period of time,this is supported by exchange 2010 and later.
Your next option is a staged migration,you will use this if you’re planning to move all your mailboxes to exchange online over a period of time,but this option is only supported when you are using exchange 2003 or 2007.
Your third option is a cut over migration,this is a short-term migration where users will be migrated in one batch and then cut over in a single swoop,this is used for 2000 or less mailboxes and when the users identity are managed in office 365.
The final one is an IMAP migration,this is used for other types of messaging systems other than exchange such as AOL Lotus or Google Mail. We know what type of migrations exist,let me show you what your infrastructure could look like and how the migration data will flow,let’s start with one of the components that has been added.
This ingest server will take your mail out of exchange,process it and then upload into your office 365 tenant. The purpose of this design however is to make sure that during the migration it won’t tax to your server and affect your end users.
Are there other ways to do this? The short answer is yes. There are a lot of items that needed to be taken into account when making a decision as to which solution you go with during your migration. The final piece is about when this additional infrastructure can be moved. All of this will get taken out once you’re ready to do your final cut over to your cloud-based solution,let’s take a look at your environment post migration.
The first thing is the decreased amount of infrastructure for you to manage,maintain and upgrade. This leads to increased operational efficiencies,how do we do that? Let’s start with our file server. We’ve only got one listed,we have taken all of our shared files and we’ve moved them to SharePoint Online in office 365.
We’ve taken all of our users’ home drives and we have moved those to onedrive for business in office 365. We only have a single Active Directory server,we have the possibility of a second depending on the amount of load that you need for internal based applications,but for our purposes,we’ll only utilize one.
Everyone who accesses cloud based services is authenticating to your Azure Active Directory as opposed to your internal Active Directory,those two will synchronize together,every time a user changes their password,it automatically updates on an office 365.
One of the biggest components you will notice is your exchange server and the need for your mail archive. Neither one of those are needed because those services are handled by office 365. Your remote users are no longer fully connected into your environment at all times,they are authenticating directly to add your Active Directory,they are utilizing all of these cloud-based services that you’ve moved out to here.
As a matter of fact,the only reason that these users would need to connect into your environment is whether you have internal based applications that these users are using.
This is a high-level overview with the basic considerations of an office 365 migration,a project like this requires a detailed approach when you are developing your migration strategy. To begin your transition to the cloud,you can contact our team at data networks,we’re available to assist you with your environment assessment at any time.