@dbeato said in Mapping OneDrive Business to a drive letter:

@bigbear said in Mapping OneDrive Business to a drive letter:

ituations like these I have been using Azure Files. The SMB 3.0 stuff allows you to map drives directly to the cloud and you get the usual SMB features (and file locking). You can also install a premise server for caching of larger active datasets. SMB 3.0 includes all the good stuff from the Storsimple acquisition. Combine with Azure Domain Servers and Azure Active Directory, lots of options.

For that, I would recommend enabling Recycle Bin of the whole Sharepoint Share and also users will get versioning instead of locking as you stated.

Sharepoint versioning doesn’t help in an excel spreadsheet that is constantly being updated, there would just be versions with disparate data.

Azure Files on a decent internet connection feels just like a file server. Was skeptical at first but haven’t had any issues yet.

A side note, per MigrationWiz support docs, you can no longer use Get-ThrottlingPolicy powershell commands against EWS/365 I had never thought of trying it before now...

https://help.bittitan.com/hc/en-us/articles/115008099387-How-do-I-view-the-EWS-throttling-limits-imposed-on-me-

@brrabill said in Potential Office365 (Exchange Online) Throttling Issue:

@bigbear said

And the EWS limits being increased has never made an Outlook import for a large mailbox go faster or finish for me. But will be interesting to see if it does for you. I just wouldnt bet my lunch on it.

So you are saying you saw the same thing as me .. they said the took off the throttling, but nothing actually changes...

They dont remove throttling but they increase the limits per your specific, kindly worded request

You would want to ask for throttling limits to be increased for 60 or 90 days in a new ticket and we always include these details (which came from MigrationWiz I think)

I always ask for xx (number of users) to be set for concurrent migration as well in the ticket.

EwsCutoffBalance = Unlimited
EwsMaxSubscriptions = xx
EwsMaxBurst = Unlimited
EwsMaxConcurrency = xx
EwsRechargeRate = Unlimited

And it did not seem to help Outlook import on a specific 15GB mailbox I recall, I had a dozen larger ones that also needed to complete so I moved on to MigrationWiz on that particular project.

@brrabill said in Potential Office365 (Exchange Online) Throttling Issue:

@bigbear said in Potential Office365 (Exchange Online) Throttling Issue:

@brrabill said in Potential Office365 (Exchange Online) Throttling Issue:

Right, but according to that link, MS throttles 3rd party migrations to .1 to .3 GB per hour.

We always open a ticket to request a temp lift on EWSLimits. I believe this has already been lifted for you per your comment above, but per my comment I don't believe the support guys know what you are talking about. And the EWS limits being increased has never made an Outlook import for a large mailbox go faster or finish for me. But will be interesting to see if it does for you. I just wouldnt bet my lunch on it.

How long does that take to go into effect once you request it?

We always do it a week or so in advance and they give you 90 days. As we are discussing this I am curious as to whether you could run powershell command Get-ThrottlingPolicy to see if its working on EWS...

@brrabill said in Potential Office365 (Exchange Online) Throttling Issue:

Right, but according to that link, MS throttles 3rd party migrations to .1 to .3 GB per hour.

We always open a ticket to request a temp lift on EWSLimits. I believe this has already been lifted for you per your comment above, but per my comment I don't believe the support guys know what you are talking about. And the EWS limits being increased has never made an Outlook import for a large mailbox go faster or finish for me. But will be interesting to see if it does for you. I just wouldnt bet my lunch on it.

I assume from ops original question that he is considering connecting his file server to a SAN vs local storage, but there really isn't enough detail to tell.

@joel said in DKIM records Office 365:

I was asked to setup DKIM records for Office 365.

Unless, are they asking you to configure DKIM so that another service you are using can send email on behalf of your domain?

@joel said in DKIM records Office 365:

set our own key?

If you don't want MS to know your private key, you can do this all manually and configure it yourself. When you use DKIM and send a message your private key will be used to generate an encrypted signature. The receiving mail server (if it supports DKIM) will use your public key to decrypt the signature.

If you do nothing MS generates these keys automatically for you and enables DKIM.

@brrabill said in Potential Office365 (Exchange Online) Throttling Issue:

How long does the actual migration take?

If you are talking about Outlook import I have never seen one complete over 15GB. Left one out there for 2 weeks.

If you are talking about Migrationwiz its all server to server and doesn't affect the user. You could manually import the last few weeks and all contact, setup their new Outlook and let the import run overnight. Outlook should only be caching 90 days or so of email anyway.

Are you going to configure an archiving policy?

Not enough info. How many people, how many files and how much storage space? What is the performance load expected?

You only need to do this if you want to set your own key.. If you do nothing, MS automatically creates a private and public key pair and enables DKIM signing.

@brrabill said in Potential Office365 (Exchange Online) Throttling Issue:

If they would just open the pipe up for a few days for me, this would be so simple.

BTW are you using Outlook 2016? Just curious because of PST file limits in older versions.

I have always just setup the new user, run a migrationwiz pass for the last 2 weeks, contacts, calendar etc, let the user into their new 365 mailbox then started the full pass migration. This is what MS refers to as a "dial tone" migration. Then I run another pass a couple weeks later before shutting down the old server or services.

I would imagine the upload limits to be DoS Security best practices of some sort.

@brrabill said in Potential Office365 (Exchange Online) Throttling Issue:

I might also try IMAP migration

The IMAP tool I have found leaves out data, the MigrationWiz IMAP migration is probably worth the few dollars for the single large mailbox. Just to save you another headache. The Microsoft tools has missed large date ranges of data for me in the past. MIgrationwiz has always come through for me.

@brrabill said in Potential Office365 (Exchange Online) Throttling Issue:

I used IMAP to download the messages to a new profile with no issue.

What file format did you download to? You can still create a non-exchange profile and import to a PST file, then upload that to Azure using AzCopy.

Also for $10 or $12 you can use IMAP to 365 with BitTitan Migrationwiz which you may find much simpler, since its only this single mailbox.

I will admit MigrationWiz is much simpler and it does multiple passes. Just gets expensive when you have hundreds of mailboxes.

@dashrender said in Potential Office365 (Exchange Online) Throttling Issue:

@bigbear said in Potential Office365 (Exchange Online) Throttling Issue:

You are going to want to do a network upload of your PST files using AzCopy to free Azure storage space MS offers for migrations. I have done hundreds of larger PST files like the one you are stuck on and I can tell your current import won't complete ever.

Just google "365 pst network upload".

MS365 has become more and more useless with the shift to CSP and "partner first" initiatives. Do everything you can to get escalated back to the U.S. if you ever need real help.

I gave him the link to that 4 hours ago.
he didn't want to do that.

Did not see anything in this thread about it. The method he is using has never worked for larger files for me.

@nerdydad said in Mapping OneDrive Business to a drive letter:

These are all just webDAV pointers without synchronizing OneDrive to all of the computers.

You are correct. We couldn't afford the storage that it would take for us to sync up everybody's OneDrive profiles across all of our servers, plus the backups that it would cost us. Dedup would help, but wouldn't be enough.

Onedrive has gotten better with Files on Demand but I would only recommend for user's individual files, not file shares. There is no file locking, and its just a mess for larger data sets. Those webdav scripts are a joke, wasted a lot of time on it. Your users will hate you.

For situations like these I have been using Azure Files. The SMB 3.0 stuff allows you to map drives directly to the cloud and you get the usual SMB features (and file locking). You can also install a premise server for caching of larger active datasets. SMB 3.0 includes all the good stuff from the Storsimple acquisition. Combine with Azure Domain Servers and Azure Active Directory, lots of options.

https://support.office.com/en-us/article/use-network-upload-to-import-your-organization-s-pst-files-to-office-365-103f940c-0468-4e1a-b527-cc8ad13a5ea6?ui=en-US&rs=en-US&ad=US

Here is a link to MS instructions.

You are going to want to do a network upload of your PST files using AzCopy to free Azure storage space MS offers for migrations. I have done hundreds of larger PST files like the one you are stuck on and I can tell your current import won't complete ever.

Just google "365 pst network upload".

MS365 has become more and more useless with the shift to CSP and "partner first" initiatives. Do everything you can to get escalated back to the U.S. if you ever need real help.

https://support.polycom.com/content/dam/polycom-support/products/Voice/polycom_uc/other-documents/en/2015/BLF_HuntGroups_EA91820.pdf

Page 3 half way down

Can all VVX Business Media Phones handle 50 BLF lines out of the box?

Due to screen limitations of the phone hardware, there are limits on the number of BLF lines that can be monitored, depending on the phone model. These limits are purely a factor of the number of physical line keys available on each phone.

If more than the maximum number of lines is configured, the phone will not monitor those additional lines.

To reach the maximum of 50 BLF lines, expansion modules must be attached to the phone.

Okay I read the whole thread.

You should know Polycom has a hard limit of 50 BLF keys on most models. I know you said 48 but you probably aren’t counting line buttons.