Jump to content


anyweb

Root Admin
  • Posts

    9208
  • Joined

  • Last visited

  • Days Won

    367

Everything posted by anyweb

  1. is there anything different OS wise with the 50 that have issues versus the rest that don't ? are they using the same client version ?
  2. anyweb

    pki, nps and vlan problem

    you'd need to supply a lot more details about your issues to get some traction on this, thanks
  3. sure thing, done.
  4. personally I think those days are over and that it's better to deploy an up to date ISO/WIM of the latest OS version of Windows 11 available, how will you manage your clients ? how do you intend to get an 'image' on these clients ? will you use Windows Autopilot ? without knowing more it's hard to advise
  5. hi @shintest, i'm working on it just now so plan on releasing yet another release soon, please stay tuned !
  6. in the blog post you'll see it's deployed to 'autopilot users' that can be whatever users you want, it's up to you who get's this behaviour (or not)
  7. thanks for posting your solution so that others may learn from it
  8. from you log i saw this line and a quick search brought me here https://learn.microsoft.com/en-us/troubleshoot/mem/configmgr/os-deployment/pxe-boot-not-work can you try the advice there and report back ?
  9. ok sorry for the delay in getting to the bottom of this, but after our Teams meeting I have a better understanding of your problem... first of all, in SCCM 2403 in my lab, i also do not see the Recovery Audit Report, and that is intentional as that report was moved out of SCCM in version 2002 see here > https://learn.microsoft.com/en-us/mem/configmgr/protect/deploy-use/bitlocker/view-reports#bkmk-audit and > https://www.reddit.com/r/SCCM/comments/pot0qu/bitlocker_management_recovery_audit_report_missing/?rdt=38888 so now that we know it shouldn't show up in SCCM versions greater than 2002, where do you find that report now ? the answer is below so go to your BitLocker Administration and Monitoring Website and click the Recovery Audit link, if that does nothing at all, then maybe we've found an issue. In my Technical Preview lab (2405) it does nothing. In my Current Branch 2403 lab, it does nothing in Edge, Chrome, Firefox, it looks like it trys but nada. So I tried IE. yeah I still have that installed on this server, and it prompted me with this > notice the 'only secure content is displayed' message ? after clicking Show all content I get this at this point, clicking Cancel, shows the actual report ! so i think this could be a bug, or at least an annoyance or a web browser setting that we need to 'change' to read the reports, i'll ping the Microsoft Product group and see what they say about it, if they reply i'll post back here cheers niall
  10. ping me a pm, we can do it via Microsoft Teams later this evening, not sure what timezone you are in, but i'm in Sweden/Europe
  11. what version of SCCM are we talking about here ?
  12. would you like me to do a short remote session with you so I can take a look ?
  13. so what DO you see in Reports in SCCM under BitLocker Management ? or is that completely missing ? are you using MBAM or ConfigMgr to manage BitLocker policy ?
  14. take a look at part 7 here, does it help ? https://www.niallbrady.com/2019/11/13/want-to-learn-about-the-new-bitlocker-management-in-microsoft-endpoint-manager-configuration-manager/
  15. @Chazh if you post your smsts*.logs we can take a look at the cause
  16. did you look at part 2 of this blog series ? it's all there
  17. share the logs with me and i'll take a look are you sure you deployed this to the right group ?
  18. great to hear it's working now ?
  19. see here, i explain how this happens (after 10:28...) and how to resolve it (after 13:00)
  20. i'm guessing it's your NIC (network) drivers, what are they shown as in device manager ? have you tried installing the latest drivers+bios version from dell ?
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.