Forum Widgets
Latest Discussions
Moved 2.5"ssd from old Intel NUC to new Intel Nuc, can't find docs/pics
So not sure if this is the right place after wading through all the options so here goes: I moved a ssd from my old NUC that was on it's last legs (pwr supply). It was windows 10 and I needed a new system as the hardware was too old to upgrade to WN11 and the pwr supply was on the blink anyways. I installed two brand new SSD's in the new NUC and installed a new version of WN11 on one (Linux mint on the other). I got the new system up running both OS's w/o much trouble (other than my old HP laser printer which is so old that HP doesn't support it anymore). I took the old 2.5" ssd out of the failing nuc and connected it to the new system via usb-c. wn11 recognizes it as drive F but show two identical F drives...? why two F's? I can open it via File explorer but I can't find any of my word docs. Doing a search in the search box with drive F selected, all wn11 does is state : "working on it" and never finds anything (the little spinning circle spins itself senseless) and I finally give up and end the task :) If I boot my Linux ssd, I can find the docs and also pics too. What am I doing wrong? I can find docs using the linux OS but I can't in the OS that they originally were created in (windows/word)Windows 10 21H2 and Windows 11 21H2 both show up as "2009" release
I'm not real sure where to post this, so will try here. I have noticed that for both Windows 10 - 21H2 and Windows 11 - 21H2, the "ReleaseID" value in the Registry is incorrectly shown as "2009". (We are using Windows 10/11 Enterprise.) This is located at this key in the registry: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion We rely on inventorying this value to determine which computers have which "Feature Update" installed, and therefore, which computers we still need to update. Has Microsoft migrated away from using this value to indicate which Feature Update is installed? Do we need to change our approach to look at the "DisplayVersion" instead of the "ReleaseID"? Or some other value in the registry? Also, Windows 11 has another issue. In the same registry key location, the "ProductName" value is listed as "Windows 10 Enterprise", which of course is incorrect. Are others seeing these same results with these items? Anyone heard if Microsoft has plans to fix these issues?Microsoft Lens The Ultimate PDF Scanner Mobile App
In today’s fast-paced world, having a reliable document scanning app on your mobile device is essential. Microsoft Lens, formerly known as Office Lens, is a powerful PDF scanner that helps users digitize documents, receipts, whiteboards, business cards, and more with ease. Whether you’re a professional, student, or simply someone looking for an efficient way to manage paperwork, Microsoft Lens is a must-have app. https://dellenny.com/microsoft-lens-the-ultimate-pdf-scanner-mobile-app/Unlocking Productivity with the Microsoft Remote Desktop Mobile App
In today’s fast-paced digital world, professionals need seamless access to their work environments, no matter where they are. Microsoft’s Remote Desktop Mobile App is a powerful tool that enables users to connect to their Windows devices remotely from their smartphones or tablets. Whether you’re working from home, on the go, or managing remote servers, this app ensures you stay productive and connected. https://dellenny.com/unlocking-productivity-with-the-microsoft-remote-desktop-mobile-app/
Fetch Email of Login User Using Command or Script
Dear Team, We are working on retrieving email address of the user joined to Entra ID from Entra-joined Windows devices, specifically while running in a system context.The whoami /upn command successfully returns the joined user’s email address in a user context, but it does not work in a system context, particularly when using an elevated terminal via the psexec utility. We also tested the dsregcmd /status command; however, in a system context, the User Identity tab in the SSO State section only appears when there is an error in AzureAdPrt. Under normal, healthy operating conditions, this command does not provide the user identity or the full domain username. We would greatly appreciate guidance on how to retrieve the Entra ID joined user’s email address in a system context, especially from those with prior experience in this area. Thank you for your support.
Deploy 802.1x Policies to Windows 10 Devices using traditional management tools
Hi Folks, We've been asked to implement 802.1x endpoint policies to Windows 10 devices using traditional tools such as AD, GPO etc.. Has anyone achieved this and is it a possibility? Thanks and much appreciate any helpful information!Recurring Work or School Account Sign-In Error Notifications (Hybrid-Joined Devices)
We're seeing a recurring issue where users receive frequent notifications from Windows saying, “There is a problem with your work or school account”, prompting them to sign in. However, when they attempt to sign in to resolve it, the process fails—despite everything else seemingly working fine (e.g., no impact on Teams, Outlook, or other M365 services). All affected devices are hybrid Azure AD-joined (on-prem AD + Entra ID). This has been occurring across both Windows 10 and Windows 11 machines, including recent test deployments. Using dsregcmd /status, I noticed the following in the logs: SSO: Invalid Grant AADSTS7000022: VSM Binding Key missing from Ticket Granting Ticket Request Additionally, Azure AD Connect was found to be running an outdated version, which might be a factor—but I’m not certain if this is the root cause. Has anyone encountered this before or found a reliable fix? Appreciate any insight![On demand] Let's talk Windows and Intune
Microsoft Technical Takeoff started off with candid, unique insights on today's device, update, security, and management landscape. Watch Let's talk Windows and Intune – now on demand – and join the conversation at https://aka.ms/LetsTalkWindowsAndIntune. For more free technical skilling on the latest in Windows, Windows in the cloud, and Microsoft Intune, view the full Microsoft Technical Takeoff session list.Problematic, uninstallable program? Here's how to break it
Let's say a program aint doing ya much good, and is actually working against you. You try to uninstall it, but for some reason, you can't! Never fear, here's the solution. Find the program's EXE file. Open it in Notepad. Press Control + A to select all the text, and then press Backspace. This will destroy the EXE and render it unopenable. Press Control + S to save it. Check to make sure the EXE is for sure busted by attempting to open it (In File Explorer, double-click the EXE, or right-click and select "Open"). If it worked, it should say this: If it does, you're done! 👍 Has this helped you? Leave a comment!Getting to the bottom of it: Remote Computer Management\Storage\Disk Management - SOLVED
I just wanted to share a solution to a challenging, poorly documented issue (as far as my research found). 3 parts to allow managing a remote system with Computer Management\Storage\Disk Management: On both systems (one you are trying to manage, and the one you are on), enable firewall rule group Remote Volume Access (I turned on rules only for Domain profile) On both systems (again, one you are using and your target system) need to have Virtual Disk Service started (or at least set to Automatic Startup, I believe default is Manual) On the system YOU (the manager) are on, you probably need to ensure that somehow, someway, the TARGET COMPUTER ACCOUNT (it's DOMAIN computer account) has, on YOUR SYSTEM, the User Logon Right Access this computer from the network. I achieved this by adding the target system to my local system's Remote Desktop Users group, because that and Administrators are the only two groups granted this URA by the "MSFT Windows 10 2020 - Computer" baseline GPO. BOOM! Totally works to a remote system now. In my case, both systems are Windows 10 2004. You probably wouldn't want to add "Domain Computers" permanently to all your IT Techs' PCs as Remote Desktop Users, but you could add them temporarily just when you need to remote disk manage something for a ticket, then remove it. Cheers!
