@syko24 said in Migrate to O365 best method:

@JaredBusch said in Migrate to O365 best method:

@syko24 said in Migrate to O365 best method:

@JaredBusch said in Migrate to O365 best method:

@syko24 said in Migrate to O365 best method:

I have 2 clients that are both currently on SBS2011 (Server 2008R2 and Exchange 2010). What is the preferred method to migrate to O365 Hosted Exchange? In the past I have always just exported PST files and the recreated email accounts online and then imported the PSTs. This method seems to work alright with the exception of cached autofill accounts that we usually just clear from Outlook. I was looking at the option of using Azure AD Sync and then moving the mailboxes but seems like more effort than what is needed. The file shares are being moved to Sharepoint/OneDrive and the server is going away. Anyways, what is your typical migration plan? The clients have about 15 accounts a piece.

Don't even make the PST.

Just create a remote migration sever in O365 and suck the data up.
I just did it for 139 mailboxes.

The two clients are both on different networks with their own SBS servers. Can I use Azure AD connect to migrate both servers users to the same O365 account? We basically want to merge the two environments into one online account. There are not duplicate usernames on the two servers so I don't think this will be a problem but just curious if you've ever had to do something like that.

Thanks

AzureAD has nothing to do with the migration of email. You are mixing things.

If you are wanting to switch to Azure AD and have disparate environments, then you need to just import the email as I mentioned. Then have everyone sign in to O365 and update their passwords, then disjoin the local computers form AD and rejoin AzureAD.

I would completely skip the disaster of merging two unrelated, on-premises, AD forests.

So which tool or method do you use to migrate the mailbox? Powershell? Everything I have seen/read shows that you first create your users with the connect tool and then move the mailboxes.

I did this in O365 itself. You download their excel template, fill out the information, then run through the O365 module for importing the data and go...

In my case I was coming from SMTP, not Exchange, so I had to create all the users on O365 first, you might have to do the same.

@JaredBusch said in Migrate to O365 best method:

@syko24 said in Migrate to O365 best method:

I have 2 clients that are both currently on SBS2011 (Server 2008R2 and Exchange 2010). What is the preferred method to migrate to O365 Hosted Exchange? In the past I have always just exported PST files and the recreated email accounts online and then imported the PSTs. This method seems to work alright with the exception of cached autofill accounts that we usually just clear from Outlook. I was looking at the option of using Azure AD Sync and then moving the mailboxes but seems like more effort than what is needed. The file shares are being moved to Sharepoint/OneDrive and the server is going away. Anyways, what is your typical migration plan? The clients have about 15 accounts a piece.

Don't even make the PST.

Just create a remote migration sever in O365 and suck the data up.
I just did it for 139 mailboxes.

I did it two months ago for 8 mailboxes... worked slick.

@wrx7m said in RDS 2019 Setup and RDS License Role:

When using UPD, is there anyway to access various users profiles' folders and files from the RDS server file system?
Example:
C:\Users\Bob\Desktop

Edit: I found that I can path to it via UNC (\ \server\c$\users\Bob\Desktop), but get permissions error when I go locally, from C:\Users\Bob\Desktop. Also, the Bob folder is only a shortcut (LNK file) in the users directory.

That is what I HATE about roaming folders... they simply do not act the same as local folders!

I typically download things to the desktop and execute from there. But when on a system that has a desktop redirected to the server - that fails 99% of the time, I have to move the executable to something actually local, then execute it.

@Obsolesce said in Looking For Alternate IT roles:

@Dashrender said in Looking For Alternate IT roles:

Development typically means writing code. And while PowerShell is a type of code, I don't think the kinds of scripts IT Admins write are generally considered development.

Then there is DevOps - I'll let someone else explain that one though.

PowerShell scripting is typically for IT OP's and Admin tasks. That's nothing to do with Software Engineering, programming, etc.

That was basically my point.

@hobbit666 said in What Are You Doing Right Now:

@JaredBusch said in What Are You Doing Right Now:

Always on a VPS.

who do you prefer?

Vultr, $5 +1 for backup, super cheap haven't had any issues using the Chicago DCs.

Development typically means writing code. And while PowerShell is a type of code, I don't think the kinds of scripts IT Admins write are generally considered development.

Then there is DevOps - I'll let someone else explain that one though.

@scottalanmiller said in Converting VMware VMs to KVM:

@DustinB3403 said in Converting VMware VMs to KVM:

@scottalanmiller said in Converting VMware VMs to KVM:

Thanks everyone. Turns out Hyper-V 2016 has been found and that is what they are going to use. So it is moot now. Now we get to migrate VMware to Hyper-V

But an old version of Hyper-V . . .

Yeah, I prefer the KVM approach.

even so - why 2016 and now 2019?

@NDC said in Handling Downvotes:

If you click the counter there's a popup with the breakdown.

oh - yeah, bad UI choice.

well, the picture isn't showing my cursor over the -1, but it was there... still not showing.

because it's not uncommon to do 2+ searches in a row. Now they have to close the window between searches... which means it's broken.