@dashrender said in Potential Office365 (Exchange Online) Throttling Issue:
You uploaded a file that was .6 MB and now MS is telling you it's 550 MB? damn, that's some expansion.
647K KB (647,000 KB) is .6 MB?
@dashrender said in Potential Office365 (Exchange Online) Throttling Issue:
You uploaded a file that was .6 MB and now MS is telling you it's 550 MB? damn, that's some expansion.
647K KB (647,000 KB) is .6 MB?
@bigbear said in Potential Office365 (Exchange Online) Throttling Issue:
@brrabill said in Potential Office365 (Exchange Online) Throttling Issue:
@dbeato said in Potential Office365 (Exchange Online) Throttling Issue:
@brrabill said in Potential Office365 (Exchange Online) Throttling Issue:
You uploaded a file that was .6 MB
How is it going, I didn't even know you had a thread on this and I told you the same thing about PST
It ended up taking about 70 minutes, but it completed. Now I have to look at the file and compare folders and see if everything copied over, especially since the PST file sizes were reported as different.
Was that the test upload or the 20Gb file
The test upload.
I am checking through it now ... it seems to have worked.
I got thrown off by the stupid filter setting Outlook has ... had to go through the folders and de-select that, but it seems to have gotten them all.
Trying the PST import method. Honestly, it isn't much better.
Have a 3.28 GB PST upload to Office365 already. Started the import at 2:03. It is now 6 hours later and it is only 59% done. So this seems like it might even be SLOWER than the other way.
WTH, Microsoft. Why do you make it so hard to switch to your product?
@dbeato said in Potential Office365 (Exchange Online) Throttling Issue:
@brrabill said in Potential Office365 (Exchange Online) Throttling Issue:
Trying the PST import method. Honestly, it isn't much better.
Have a 3.28 GB PST upload to Office365 already. Started the import at 2:03. It is now 6 hours later and it is only 59% done. So this seems like it might even be SLOWER than the other way.
WTH, Microsoft. Why do you make it so hard to switch to your product?
I am still amazed at how long it has taken you, I am not sure from what email system you are coming from but usually I do importa initially a month or 2 weeks before and then do deltas every week with the Builtin migration tool.
I guess my mistake is expecting it to happen it like every other file transfer would happen.
I mean, the upload of the PST to Azure went almost full ISP speed of 65 Mbps. Why the F do they import the data at .5GB an hour or less. Just makes no sense why they would want such a delay in allowing people to switch over to their system.
@wrx7m said in Potential Office365 (Exchange Online) Throttling Issue:
They are throttling. I just went through a 100 mailbox migration and a user with a 15 GB mailbox took 3 days. I have a 150/150 Mbps dedicated fiber circuit.
Yeah this is basically what I am saying.
Plus these "higher speeds" they discuss are with concurrent users.
So that could be why. If you happen to have 100 users and they are all 5GB mailboxes you will complete over a weekend.
You have 100 users with 20GB mailboxes, you are in for a world of hurt.
@bigbear said in Potential Office365 (Exchange Online) Throttling Issue:
@wrx7m said in Potential Office365 (Exchange Online) Throttling Issue:
@bigbear said in Potential Office365 (Exchange Online) Throttling Issue:
I like either the Azure method or the MigrationWiz. With the latter you can migrate ahead of time and sync up after the switch or do a dial tone migration if you don’t have the time to plan.
Azure is more work but when migration hundreds of large mailboxes it’s better than the outlook import method.
Soemthing to note, when you migrate a premise exchange server you get full speed upload automatically from MS.
Seems like with the limits raised we complete Terrabytes of mail migrations over a weekend without anyone left behind. I’ll have to pay attention next weekend on what speeds were seeing in live migration.
I was in hybrid mode and it still took a long time.
I did not have that experience, have done it twice.
Maybe they are throttling it more.
My next step with be the IMAP product you mentioned. We'll see where we get with that.
Was having a few issues with my XenServer this morning. The host itself eventually froze up with this:
So I rebooted it. It took a long time for it to come up, and then it booted into Emergency Mode.
It boots off a 64GB USB stick. The VMs are stored on a 1.8TB SSD array (DELL H710).
Here is the first thing it says in emergency mode:
And here is a listing of the drives and partitions.
Anyone have any thoughts? sbd is a unused partition I am considering reinstalling XS on to see if I can re-see the array. But thought I'd maybe see if it is fixable first.
Though wondering if the USB drive just finally gave up the ghost.
@dustinb3403 said in XenServer Not Booting:
The culprit is likely that you'd didn't point your logs to a different directory, and those logs being written destroyed the USB.
No logs written to USB.
We spent forever going over all that, remember?
@jaredbusch said in Dell Perc H710 predicted failure:
Don’t wait don’t delay just fucking do it
You should start making tshirts with this quote
I think I might be having some trouble with my domain.
The other day I rebooted one of my DCs, and it took a while for me to be able to log in. I kept saying that it could not find a domain controller.
Today, I tried joining a clean install Windows 10 machine to the domain, and am getting a
"DNS name does not exist" error
The query was for the SRV record for _ldap._tcp.dc._msdcs.BANDR
No issue logging in or anything, so I tok another WIn10 machine off the domain and tried to add it back in, and got the same error message.
I have the original DC that we've had forever on the network. I added a second DC a while back, the does AD and DNS.
Thoughts on where to start?
Still on "Server 2003"
I know, I know ... working as fast as I can to get all this upgraded.
Literally almost to the point of being able to upgrade to 2016, but had a few road bumps, and now this road bump.
I think I have found the culprit.
When I added the most recent DC, I demoted another one, named ORCA.(I am a JAWS fan, what can I say?)
In DCDIAG DNS testing, that server is still listed, and as an error. I looked through the AD DNS and noticed it is still in there in multiple places.
Is it safe/proper to delete all orphaned entries/mentions of that?
From DCDIAG:
DNS server: 10.0.2.1 (orca.domain.com.)
2 test failures on this DNS server
This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 10.0.2.1
[Error details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
Delegation is broken for the domain _msdcs.domain.com. on the DNS server 10.0.2.1
[Error details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.) - Delegation is broken for the domain _msdcs.domain.com. on the DNS server 10.0.2.1]
Yeah the IT guy at this place is a real jackhole, let me tell you...
@jaredbusch said
Restoring a DC is nothing in a SMB with only a single DC.
As has been discussed many times here on ML, it really is so easy, it's a wonder why it isn't done more. (AKA, the single DC route.)
I was curious how everyone manages their color printing.
We have no desire to track individual users. However, we want to ensure they don't inadvertently print 100 pages in color that they wanted it in B&W.
On the previous devices, we would create a "color" printer share and a "B&W" printer share, and manage it that way. (True, a mistake could still be made, but it seemed to work great.)
What is everyone else doing? Just having the user set it in the app they print from? A similar dual print share arrangement? Or something totally different?
I asked the same question after reading all the CEntOS love here and deploying my WordPress site on it.
Then people (cough @scottalanmiller ) were like ... why would you do that?
Only because everyone said ti was the best time and time and time again.
Good question.
@dbeato said in CentOS 7 - Why Did [Almost] Everyone Switch to Fedora?:
@brrabill said in CentOS 7 - Why Did [Almost] Everyone Switch to Fedora?:
@jmoore said in CentOS 7 - Why Did [Almost] Everyone Switch to Fedora?:
@brrabill I put 2 different wordpress sites on fedora. While not exactly centos it is similar. Worked fine for me for a few years now. So who knows if I'm doing it right lol
Even though it's not difficult, moving WP betweens servers always seems to spook me, LOL.
That's why no motion on that yet.
Backupbuddy is a great plugin for backups and migration of WP sites.
Yeah the last time I did it ... it was easy.
@jmoore said in CentOS 7 - Why Did [Almost] Everyone Switch to Fedora?:
I hate to admit this but now that I think about it I don't think ive restarted either one in about 2 years now. I just keep them updated and they keep running.
Hope you put your flame suit on before you typed that.
Though you seem to have gotten away easy.