So this little ridiculous issue has been haunting me for two days until I finally got a moment to troubleshoot it.
My Word page zoom has been stuck at 70%-something the last few days, even though I had plenty of white space (or gray space) on both sides of the document.
Turns out the page view layout was setup to use “Page-to-page” instead of “Vertical”.
Change layout to “Vertical” and the issue is resolved!
So a colleague just bought a new PC and it came pre-installed with “Windows 10 in S mode”. This is a locked down version of Windows where you can only install apps from the app store. Regular exe files etc are blocked.
Luckily you can disable the locked down mode rather easily. However, as of today, there’s no way to reactivate it again, so keep that in mind. Your 85 y/o grandma might be better off having it enabled as it’s a good way to block potential viruses.
The annoying thing is that in order to disable S mode, you actually have to “download” or run an app from the app store, and this requires a Microsoft account. So, for those of us who likes to use a local user account instead of logging on with a Microsoft account, we still have to login in order to run the app from the Microsoft Store.
1: Open Settings
2: Go to Updates & Security
3: Open the Activation tab.
You will see that your current Windows edition is set to “Windows 10 X in S mode” (where X is probably Home or Pro).
4. Click on the Go to the Store button. This will open the necessary “app” you need to run in order to unlock the regular Windows mode.
5. Run the app. Login with your Microsoft account when prompted (or create a throwaway account). Your PC is now unlocked.
6. Alternative step: Install Ubuntu
It’s actually really simple, but you’ll need administrator access on the domain controller in order to read the security event log so you might have to consult upper sys admins.
It seems to not want to filter/sort by username though so if you’re managing a huge enterprise with thousands of users this could be a bit tedious. On the other side, if that’s the case I suppose you already have better tools for the job.
Anyway, all invalid login attempts are logged as event id 4776 (Credential Validation).
Windows Logs -> SecurityFilter Current Log... in the right navigation menu4776 into the input field which says <All Event IDs>
netsh wlan show profile <SSID> key=clear | find "Key Content"
You can type
netsh wlan show profile
to list all wireless networks you’ve saved earlier.
netsh -r "hostname" interface ipv4 show interfaces
wmic path SoftwareLicensingService get OA3xOriginalProductKey
set
Filter output
set prog
Online version:
DISM.EXE /Online /Add-Capability /CapabilityName:NetFx3~~~~
Offline version (requires .cab installer for the .NET framework):
DISM.EXE /Online /Add-Package /PackagePath:C:\Temp\microsoft-windows-netfx3-ondemand-package.cab
taskkill /F /IM taskname.exe
/F = Force kill (ignores any prompts etc)
/IM = Image Name (name of process)
netsh wlan show wlanreport
net view /all /domain:company.com
msg /server:hostname username
Example:
msg /server:pc01 johndoe
getmac /v
net use x: \\server\share /user:domain\username password
msinfo32 /computer hostname
net stats srv
if not available, use
net stats workstation
nltest /dclist:example.com
setx /s hostname /u domain\user /p pw variable value
Example:
setx /s PC1234 /u itdb\kek /p 123456 JAVA_HOME "C:\Program Files\Java\jre1.8.0_73"
slmgr /xpr
Alternatively run slmgr /dli for detailed information about your Windows license
For remote computers: slmgr hostname username password /dli
lusrmgr.msc (Local Users Management)sysdm.cpl (System Properties)appwiz.cpl (Programs & Features)eventvwr (Event Viewer)compmgmt.msc (Computer Management)printmanagement.msc (Print Management)devmgmt.msc (Device Management)services.msc (Services)taskschd.msc (Task Scheduler)This post will be continually updated with useful tips for remote troubleshooting and various tools for Microsoft environments
Related posts:
From time to time my Alt Gr button seems to stop working, which I use for several special characters like @.
Turns out the problem is related to the process mstsc.exe (Microsoft Windows Remote Desktop).
Solution: Close any RDP windows you have open (no need to logout, just close them). Voila, Alt Gr works as intended again. Now you can reopen them and hope it doesn’t happen again.
You should also be aware of the temporary solution: Pressing CTRL + ALT is the same as Alt Gr – in case you can’t close the current RDP windows for any reason.
This minor, yet very infuriating issue, has been present at my computer(s) for several years, both Windows 7 and Windows 10.
Open the Powershell shell (pun intended) on your domain controller and run the following command:
Get-ADGroupMember 'groupname'
This will list all members of the ‘groupname’ group in your shell. List pipe it into a text file instead:
Get-ADGroupMember 'groupname' > list.txt
We don’t need those unecessary columns though, so let’s just list the NAME column and nothing else:
Get-ADGroupMember 'groupname' | select name > list.txt
Run the shell as admin…