Explore >> Select a destination
|
You are here 
|
oofhours.com | ||
| | | | |
petervanderwoude.nl
|
|
| | | | | This week is all about Windows 10 devices. More specifically about (re)naming Windows 10 devices. And all that by using standard available functionality without custom scripting. This post will bring different posts together that I did over the last couple of years and will introduce one new configuration option that was recently introduced within Windows... | |
| | | | |
oliverkieselbach.com
|
|
| | | | | It's been a while since I updated the Autopilot Manager solution but here we go with an update to support Windows Corporate Identifiers. Maybe a quick recap of what Autopilot Manger is. The idea is a more user friendly on-the-fly Autopilot hardware hash upload to the Intune tenant. Or with the new version publishing of... | |
| | | | |
eskonr.com
|
|
| | | | | Managing Windows endpoints with SCCM (System Center Configuration Manager) and co-management enabled can be challenging, especially when dealing with co-management issues. In this post, I'll share insights and troubleshooting steps to help you resolve issues with devices that are supposed to be co-managed by Intune but aren't appearing as expected. Background I recently worked on... | |
| | | | |
www.khyrenz.com
|
|
| | | Let me start by saying that, yes: many tools already exist to parse information out of the Windows Registry and/or the Event Log. However, while I was conducting my own tool validation processes (see https://github.com/khyrenz/tool_validation), I realised that very few tools parse this information out and automatically populate the kind of table that I would be adding into my forensic report.So... I did a bit of R&D, and I present to you a Python script that does just that; creatively named pars | ||
