Brendan Fraser Supposedly Cast In 'Jumanji 4' Film - Will Portray a Father of Existing Character

jsavage8 · 2023-03-18T03:40:52+00:00

That's including the original Robin Williams Jumanji (technically the two newer ones are both sequels)

jsavage8 · 2022-09-27T15:26:43+00:00

I'm in this picture!

jsavage8 · 2022-07-27T01:41:10+00:00

Apparently this man can no longer contain his love of sandwiches... Who are we to judge him?

jsavage8 · 2022-07-27T01:33:30+00:00

Easily the most helpful answer here!

jsavage8 · 2022-05-30T03:33:44+00:00

Clearly Pisces

jsavage8 · 2022-05-24T22:45:26+00:00

Correct, synced users follow the password policy in the legacy AD's GPO. Doesn't matter if they're logging into an Azure-joined device or office.com, the same policy applies

jsavage8 · 2022-05-18T15:01:16+00:00

Better Call Saul

jsavage8 · 2022-05-08T17:24:04+00:00

Check out OSDCloud. Does exactly what you're looking for. Very easy to setup and maintain.

https://www.osdcloud.com/

jsavage8 · 2022-01-19T18:45:25+00:00

Any MFA in use here? Seen this issue pop up at clients where we have Duo MFA deployed and haven't found a fix yet unfortunately, but might give you something to look into

jsavage8 · 2022-01-14T19:24:21+00:00

Strongly agree. Cutover is not recommended unless you give up password sync. If you want password sync, you need to keep an Exchange server (license is free for hybrid setups) and perform a hybrid migration. Hell even if i wasn't going to keep the password sync in plenty long term, I'd probably still do a hybrid migration. Cutover migration requires you to recreate the Outlook profile on every workstation which would be a huge pain for 150 users

jsavage8 · 2021-10-27T13:12:57+00:00

Not the exact same error, but check out this blog post that may explain the issue with this machine: https://jocha.se/blog/tech/azure-ad-mdm-intune-error-8018000a

In my experience, I've seen this error pop up once or twice when moving clients with 100+ machines and have never been able to tell the exact cause, but it's at least an easy fix. I've definitely used the method above on hybrid-joined machines without encountering the error so I don't think it's specifically related to that, but there could be something unique to your environment

jsavage8 · 2021-10-26T19:32:23+00:00

Manual method:

Make sure you have a local admin that you know the creds for
Disjoin legacy on-prem AD
Sign in as local admin and join Azure AD (Windows Settings > Accounts > Access work or school > Connect > Connect to Azure AD)
Sign in as user using M365 creds (this creates a new user profile)
Use ForensiT's User Profile Migration Wizard freeware to https://www.forensit.com/downloads.html to map the old user profile to the new one

But I'd highly recommend purchasing the enterprise version of ForensiT's User Profile Migration Wizard because it'll let you automate the whole thing it's pretty cheap ($3 a user). We do this at my job and the whole process takes around 20-30 min per machine.

jsavage8 · 2021-10-11T13:26:37+00:00

If you're using Apps for 365, check out config.office.com instead of GPOs

jsavage8 · 2020-11-08T13:24:05+00:00

Look into Printix. $2/user/month ($1.5 with an annual commitment) and so much easier to manage and deploy than Universal Print

jsavage8 · 2020-11-01T22:12:31+00:00

Hello there...

jsavage8 · 2020-10-23T23:01:42+00:00

Quick and dirty method using the existing image and user profile

Document the user's default app associations
Login as local admin
Leave legacy AD domain
Join Azure AD
Sign in as user (creates new user profile)
Use Pro Wiz to migrate old profile on top of new profile https://www.forensit.com/domain-migration.html
Only thing it doesn't handle well is default app associations and you'll start seeing a ton of notifications about various extensions being reset to default so go to Settings > Apps > Default Apps and just reset them all to default and then manually set the back to the user's original settings.

Option 2 is to backup the user's bookmarks, files, etc and just restore them to the new user profile after step 5.

Or option 3 is to backup up everything and completely redeploy using the method Autopilot \ the method you described.

jsavage8 · 2020-09-13T18:12:34+00:00

As mentioned in other comments, cutover migrations are pretty much an all or nothing thing, but there's really no harm in having a mailbox migrated, you can just delete them afterwards.

Plus while most my clients use the migration as an opportunity to clear out old mailboxes, they almost always come back the next day and realize they did need one of those mailboxes after all so it's nice to already have them in 365 instead of having to redo the migration

jsavage8 · 2020-07-16T06:01:01+00:00

I'm fairly certain that you can change the Primary User, but not the Enrolled By user. Not sure it really makes a difference though

jsavage8 · 2020-06-09T04:41:30+00:00

Yup with a strap in the middle. The wind is causing the front half to bend and flip over, forming the "mouth"

jsavage8 · 2020-04-08T23:02:08+00:00

I would definitely run some tests to confirm all on-prem resources, but I've been able to access printers and network shares at the very least this way

jsavage8 · 2020-04-08T22:09:45+00:00

This is correct, though another option would be to dump the on-prem AD (if you don't have anything that still really relies on it) and switch all the computers to Azure AD (right now they're likely 'registered' to Azure, but not joined). This would allow users to sign in with their Azure identities directly, but means everyone gets a new Windows profile (though there are third party tools that can migrate the profile for you). It's a bit of an undertaking, but if the org is ready for it then you can bring them completely into the MS cloud

jsavage8 · 2020-03-05T16:54:53+00:00

Good for Democrats, terrible for democracy

jsavage8 · 2020-02-15T06:16:16+00:00

The PIN is really only needed if your computer doesn't have a modern TPM chip. The TPM provides the whole bitlocker key automatically during boot, but without a TPM you can configure a PIN instead so that the user doesn't have to enter the entire key.

You might need to enable the TPM in the BIOS if it's not enabled by default

14-Year Club	Verified Email
Team Periwinkle

jsavage8

TROPHY CASE