That’s what I was thinking. Removing the pin is a major pain. My customer was thinking of having the user give their pin to desktop tech for the migration, then have the end user reset their pin after the migration. But that means it’s a manual migration. YUK!
From: [email protected] [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Saturday, May 7, 2016 1:56 PM To: [email protected] Subject: Re: [mssms] Migrating Bitlocker Clients? If you could get around the PIN, it would be pretty useless. You’ll have to disable bitlocker before the migration and then enable it after. J From: <[email protected]<mailto:[email protected]>> on behalf of James Avery <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Friday, May 6, 2016 at 10:44 AM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: [mssms] Migrating Bitlocker Clients? I don’t know if this is a correct group to ask this question. Has anyone migrated Clients with Bitlocker + PIN reporting to MBAM (not AD) to another domain? We’re trying to figure out how to get around the pin when using ADMT. James
