Jump to content


rdevos

Established Members
  • Content Count

    4
  • Joined

  • Last visited

  • Days Won

    1

rdevos last won the day on April 21 2017

rdevos had the most liked content!

Community Reputation

1 Neutral

About rdevos

  • Rank
    Newbie

Profile Information

  • Gender
    Male
  • Location
    Haarlem, The Netherlands

Recent Profile Visitors

453 profile views
  1. Hi All, We are experiencing a weird issue with BitLocker when re-installing existing Windows 10 1709 machines with Windows 10 1903. The machines are hybrid AD joined and the BitLocker recovery information is stored in Active Directory. During a new installation of the device with Windows 10 1903, the BitLocker key fails on storing the recovery information in Active Directory. After examining the Windows event log, it turns out the device is trying to store the recovery information in Azure AD. Is this new behavior of Windows 10 1903 and can we modify this behavior?
  2. Did the format and partition step run? The "Use Toolkit Package" step needs local storage to put the files on.
  3. You might want to look at this page: https://www.andersrodland.com/configmgr-client-health/ It could help you achieve your goals.
  4. There is no way to set a servicing plan as available. You can give your users an extended period before you force the upgrade, by setting the dealine to some thing like 2 months. You don't see the 'Upgrade to Windows 10 1703', as 1703 has not been declared Business Ready yet. You probably will see a "Feature Update to Windows 10 1703".
×
×
  • Create New...