+1 to the Vigor130. Yes it supports SNMP and I've got it running on a few
sites with Cacti + Nagios. Upstream sync, Downstream sync and operational
status (e.g. SHOWTIME, TRAINING) is all I need.
___
AusNOG mailing list
AusNOG@lists.ausnog.net
http://list
Overall find it pretty good and comparable in most cases to on prem exchange.
The biggest difference/issue we have with o365 vs on prem is the time taken to
sync new copies of mailboxes – so on new computers, or users changing computers
and it has to sync their mailbox. It can very easily flood
odd question for the afternoon... has anyone come across a cabling vendor
who sells bulk patch leads without being individually wrapped and
twist-tied?
cutting 1200 cables out of their plastic bags & undoing/cutting the twist
ties not an experience i'd like to repeat so i'm curious if anyone knows
"user experience can never equal local Exchange."
The cached mode Outlook client comes VERY close.
Stop treating email as an instant messaging service or calendar as if it
updates immediately, and it works perfectly fine.
I reckon I can count on one hand the number of situations where running
yo
I had an experience where a business group was using shared mailboxes to store
emails with large attachments. There was an issue where these mailboxes
couldn’t be cached so every morning 30+ people would log in, saturate our
internet link for hours. We had all up around 900 users with a 100Mbi
The migration effort itself can be staged so you can sync 95% of the mailboxes
within a batch prior to cutover, then go in and complete the migration batch at
a later date, which copies the remaining 5% + delta of changes since the
previous sync. We found the biggest problem to be large mailboxe
On Tue, 2018-06-19 at 12:19 +1000, Jim Woodward wrote:
> I have used MigrationWiz before but found CodeTwo Office365 Migration
> to be excellent too, I could tune the migration to use as many
> threads that were reliable, could pause migration and resume when
> needed without having to resend every
You can pause/resume the Office 365 migration as well (which is a free
migration option).
On 19 June 2018 at 12:19, Jim Woodward wrote:
> Hi,
>
>
>
> I have used MigrationWiz before but found CodeTwo Office365 Migration to be
> excellent too, I could tune the migration to use as many threads th
Paul,
Tell us about your existing environment (Exchange 2010/2013/2016)? Whats
your uplink speed? The number of mailboxes? Total mailbox size?
I had Exchange 2010, 50mb uplink and 3Tb of mail to migrate, it was
stressful as this link was also our internet WAN link too.
In the end, I migrated 200
Hi,
I have used MigrationWiz before but found CodeTwo Office365 Migration to be
excellent too, I could tune the migration to use as many threads that were
reliable, could pause migration and resume when needed without having to resend
everything that had already been moved.
Product was w
Hi Paul,
We only had pretty small internet links (300M) before migrating to office365
and rather quickly had to upgrade (600M) due to peak usage from 8-9am most days.
We currently had 2 * 600M links and megaport connection which takes a fair bit
of that bandwidth. We still hit 550M+ on Monday m
I'll also praise MigrationWiz, it's a fantastic product with a lot more
features than a few years ago (think profile migration client that you can
deploy to endpoints). Exchange Online is very stable, not like the days of
what felt like endless downtime.
Like everything, you learn the ins and outs
We used a product called MigrationWiz to migrate our 7000 users.
The only issue with using a product like that is the rate limit into the
tenant. However you can request MS turn it off for a period of time.
We’ve been running with Exchange Online since 2013. There have been occasional
network
Never equal local Exchange? I would argue the complete opposite – unless we
want to go back to having 200MB mailboxes, regular outages, and such. I’ve been
at numerous large organisations and have never seen an on-prem Exchange system
run as smoothly as O365 does.
Sure it’s not without its faul
Hi Paul,
I was involved in migrations a few years back for some larger organisations
around the 150k-200k seat mark. The user experience ultimately relies on a
number of factors; as you’ve noted, network performance is a large factor,
however IMO this should only be an issue on the initial migr
We’ve had a lot of success, once the nuances were learned. Things that were
tricky the first time around, but are okay once you get the hang of it:
- AD sync
- managing the users after AD sync is in place (having to edit the actual ADSI
attributes is a bit strange)
- importing PST files into Onl
I'd be interested to hear general opinions and lessons learned from o365
migrations. So far as I've seen, the architecture (network and services) is
complex, and user experience can never equal local Exchange.
So much so it leaves me wondering if the effort of migration can be
justified? At the en
I believe they support SNMP for line stats as well btw which is
fantastically rare in the cheaper end of town.
I've used the 120 and it does, the 130 says it does but I haven't had
one to try.
On 15/06/18 22:20, Shane Clay wrote:
Recommend the DrayTek Vigor130.
Getting good sync speed on the
The company I work for has a position available for a VMware engineer
with good Cisco R&S skills. This is a 6 week contract role (which could
possibly lead to something longer term) and is based in the Brisbane
CBD.
This role will be assisting a team in the design and rollout of a
Private LTE Ne
Thanks to everyone who submitted a proposal. If you submitted something
but didn't get a confirmation from me then let me know ASAP.
Regards,
Mark.
___
AusNOG mailing list
AusNOG@lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog
Definetly need to make sure you upgrade the VDSL firmware on those. While the
config can take a little bit of getting used to. I found it easier to template
in Jinja2 than Cisco, since Junos could do the config merge on my behalf.
So I ended up with
Base template + dhcp template + ipsec templa
21 matches
Mail list logo
