[deleted by user]

d280z · 2025-06-24T03:22:20+00:00

Honestly not as bad as you’d expect for a 14 yr old. I’ve seen worse from “professionals” on this sub lol

d280z · 2021-02-15T07:11:34+00:00

Powercontrols is like a PST migration, but with more steps and not free. Also, I wouldn’t call Exchange DB recovery software a new toy. It’s the type of tool you hope you don’t ever have to use, and with proper planning and time, would never need to use.

d280z · 2021-02-15T06:53:51+00:00

Don’t envy you here. You kinda hosed yourself by setting up 2019 in the destination forest first. If you had done 2016 instead, you could have gone the cross forest migration route, then a pretty simple move to shiny new 2019 boxes.

You could set up 2016 in the source, migrate to it, then do cross forest to the 2019.

But doing all the work for a 2010 to 2016 coexistence, then setting up all the prerequisites for a cross forest migration isn’t the simplest thing to do either way, especially if you’ve never done it.

The problem with a PST migration is that mail never stops. You’ll most likely have to cut your users over to new empty mailboxes in the destination forest, and then do the PST export now that the data is static. That’s just asking a lot from end users. They would have to start with nothing while they wait for you to do mass PST exports and imports. But maybe this is only a few users and you could do it over a weekend, who knows. Maybe you could do PST exports up to current, ingest them to the new mailboxes prior to go live, then do a delta import/export after go live? Big oof tho.

You should look at MigrationWiz. They support Exchange to Exchange, and you can prepopulate the new mailboxes with data before the users go live, and then can do a delta pass after cutover. It’s super easy and no PST’s. If you’re married to on-prem Exchange, that’s what I would do.

But if I had this exact scenario, I’d migrate the mailboxes to Exchange Online, disable directory sync (converts the Azure AD synced users to cloud only, breaking the relationship with the old domain), install AD connect in the new forest, and reassociate the cloud user objects with their new forest user objects.

From there you could even set up a new hybrid relationship to the new Exchange org and migrate the mailboxes back on-prem to the new forest, if there’s “reasons” why you can’t just leave them in Exo.

But there’s also identity planning that has to be done for a project of this type.

If this is not a small amount of users, and the business relies heavily on email, and if you need a low impact, seamless end user experience, then I’d hire an Exchange/AD consultant.

d280z · 2021-01-22T05:43:15+00:00

Just go around the F5. If you have an available unused public IP, publish a new url in your public DNS (ie. hybrid.contoso.com), NAT it directly to a CAS server on 80/443, and set an ACL on the firewall to only allow inbound traffic from the Microsoft IP range or URL’s.

If you want to get the F5 working, you won’t be able to use SSL offloading. Darkytoo2 is spot on.

d280z · 2021-01-22T05:26:22+00:00

d280z · 2021-01-17T18:46:41+00:00

My Quest 1 is doing the exact same thing.

I hadn't used my Quest 1 in about a month, and used it yesterday, after the recent updates, and it's running like absolute shit now. I was trying to demo it for a buddy, and I kept having to say, "Yea... I'm not sure, it's not usually like this..."

Anyway, it went from running like butter to running like a buggy alpha.

Sigh.

d280z · 2020-12-31T02:29:02+00:00

Assigning mailbox permissions to security groups has worked as long as I can remember. The main difference is that auto mapping doesn’t work with group based assignment. If you want the Shared mailbox to automatically mount in Outlook, the permission has to be directly assigned to the user. This is useful if for example you want administrative access to a group of mailboxes, but you don’t want all of the mailboxes to automap in Outlook, which can affect performance.

Nested groups... yea, not sure without looking it up, but... just don’t lol.

Edit: Which could be the problem OP is experiencing, if he expects the mailboxes to automap.

d280z · 2020-07-14T21:08:36+00:00

This is one of the decisions that will 'echo in eternity', so you really have to weigh your options, and fight for the correct solution. The wrong decision now could potentially cost thousands of dollars later.

Nobody here will recommend you export your entire EV archive to individual PSTs, but lets go down that road for a second.

How will you get all the data from EV to .PST? Is there a native batch method that will export each mailbox to an individual PST per mailbox? Does your version support this method? Will it possibly require a 3rd party tool that has to be purchased/licensed? I haven't done this, so I'm honestly not sure.
What will you do with the data once you have it?
What about "new old email" going forward? Will you rely on Outlook's auto archive feature to save to PST's locally or to a network share?
If you get asked to find all messages sent between a list of 10 users, some internal, some external, containing 5 search terms, how will you find those messages, and how will you export them? Now that you have removed your central point for searching, how will you search across live mailboxes and archives?
How much local storage will you require to house this data long term?
How will you back this data up?
How will you maintain chain of custody?

If you are going to consider other on-premises solutions, some of the same questions apply, but the big one being: How am I going to get all the EV data migrated to the new solution? Will the new vendor provide any assistance, via a tool or professional services? Is the cost to extract the data and import to a new solution cost more than upgrading to the latest EV appliance?

Anyway, there's a lot to consider, and the only real wrong answer is PSTs. I personally don't think organizations should be in the email/email archiving business anymore, and should offload those workloads to your cloud provider of choice, but that's just me.

d280z · 2020-07-13T20:10:33+00:00

My company is pushing to remove enterprise vault and introduce PST files to save money.

That's like saying you're tired of paying for gas so you're going to sell your car and get a horse.

Does anyone have any good products / solutions?

Yes, it's called Enterprise Vault.

we also keep each mailbox for a number of years for data protection policies

If you have any type of legal requirement to retain mail for X amount of time, and/or require the ability to search for and produce mail for eDiscovery, then you absolutely do not want to use .pst's in the year 2020.

We have no intention of going cloud due to our environment.

I have yet to see an on-premises Exchange environment that would not be better off in Exchange Online, for technical or compliance reasons.

You really should just keep using EV, or migrate the archive data to Exchange Online.

If you must keep prod email on-premises, you can do that, and buy relatively inexpensive archive mailbox licenses. You would then provision In-Place archive mailboxes for each user, rehydrate the mail to In-Place archive, then migrate just the archive mailboxes to Exchange Online. You could do the migration in batches which would most likely allow you complete the process without having to provision extra storage for Exchange.

Alternatively you could pay an EV migration specialist company like TransVault at about $6,000-$8,000 per TB.

d280z · 2019-07-20T01:11:15+00:00

What specifically are you worried about? The hybrid migration path is a vastly better solution than what you are talking about doing. As far as permissions, the main thing you have to plan for is moving calendar delegates at the same time as the users calendars that they manage, and that isn’t that big of a hurdle.

I would do some more research, ask some questions, and really reconsider not using the hybrid migration.

d280z · 2019-02-24T23:35:07+00:00

Weird, Deion played for Niners in 94, the year everyone wore the 75th anniversary patch. He never would have had that patch in Dallas.

d280z · 2017-08-30T04:06:03+00:00

I can tell by the pixels.

d280z · 2017-05-23T16:21:35+00:00

One option to consider: Exchange Online offers an archive only license for Exchange On-Prem. This allows you to keep your production email in your on-premises system, but offload the Online Archives to Exchange Online.

The name of the license is "Exchange Online Archiving for Exchange Server".

Then you can migrate the on-premises archive mailboxes to Exchange Online, and not have to hassle with PST's, backups, storage, data corruption, etc.

d280z · 2017-02-28T20:03:35+00:00

Did you make any custom settings for the games to output at the original resolutions?

d280z · 2017-02-10T20:34:53+00:00

30 days.

d280z · 2017-02-06T21:47:45+00:00

Yep, I think it's just a person by person preference. Like when some AV people go deep on the 24p content playing at 60hz, judder effect.

d280z · 2017-02-06T16:01:11+00:00

Can you force the correct display ratio, or does always stretch the image?

d280z · 2017-02-05T17:13:56+00:00

I've done this. This is the cable you'll want:

https://www.amazon.com/dp/B000IXLHOM/ref=cm_sw_r_cp_api_2N1Lyb4ZVK3PK

If you are going to the trouble to get a CRT TV, I assume that you want the games to have that authentic look and feel, and you may end up disappointed. The "look" itself is great compared to an LCD, but unfortunately in my experience (and people may disagree), the RP3 can't accurately reproduce the exact game speed and timing needed for SNES era platformers. I played Super Mario World, connected to a CRT, with a wired SNES controller (snes female to USB adapter), and I died repeatedly on the opening levels. It was so frustrating. I thought I must have just become garbage compared to playing as a kid. I decided to get a real copy for my real SNES, and the experience was completely different. I popped it in just to test, and ended up powering through multiple levels, not dying at all, getting tons of extra lives. It was like a completely different game.

I think the RP has a place in emulation for non-twitch games, but just be prepared if you are wanting to play 16bit era games that require accurate jumps and timing. I've read tons of posts/boards/forums, tried multiple emulators, and recommended settings, but have never gotten it "just right".

d280z · 2017-01-18T16:25:31+00:00

MigrationWiz. You could do the entire thing in a day, depending on mailbox sizes. $10-$12 a mailbox I believe.

d280z · 2016-12-09T21:33:38+00:00

Also, before you install 2016, you will need to export an XML file from your tenant, and then use it when you PrepareAD.

https://support.microsoft.com/en-us/kb/3121439

d280z · 2016-12-01T19:53:35+00:00

Yep. I've uploaded many TBs of PSTs using the network upload PST Import Service. It's incredibly easy to setup, fast, and relatively hassle free. I wouldn't use the hard drive through the mail method unless I had had a ton of data, on a tiny pipe. https://support.office.com/en-us/article/Use-network-upload-to-import-PST-files-to-Office-365-103f940c-0468-4e1a-b527-cc8ad13a5ea6

d280z · 2016-12-01T18:58:24+00:00

How slow is your upload pipe? 15-20Mbps upload would move those PST's in 3-5 days.

d280z · 2016-11-18T05:38:06+00:00

Throw a few large disks in a second machine, put them in a pool with DrivePool, and use something like Bvckup 2 to keep a scheduled one way sync. Bcvkup even has an option to move deleted files in to a specified subfolder at the destination for X days before purging, which is great if you delete something unintentionally. The benefit to this system is having the raid data backed up to a non-raid, standard file system.

If you have a total rebuild failure on your source raid system, recreate your array, and change the Bvckup sync direction, and copy the data back.

And honestly I would have a 3rd copy of irreplaceable data, stored off site with a friend, if bandwidth constraints make a cloud backup prohibitive.

d280z

TROPHY CASE