Do you have windows which are stuck off screen and there is no Move options in the right click menu on the taskbar, even if you hold the Shift key? Read on for a solution!
- Left click the app’s icon on the taskbar icon. If the app has more than one window open, click on the appropriate thumbnail.
- Press and hold the Alt key on your keyboard then press the spacebar and release. This will bring up a menu on one of your visible screens.
- Click ‘Move’ on the list, and use the cursor keys (the arrow keys) on your keyboard to move the program. The window will continue move while the key is held down. The window will usually be to the left or right of the screen where the menu popped up, but you may have to experiment to see where it is to move it back.
That it! Good luck!
This is a super quick tip from an online forum…
[Sevenforums.com: Where is the location for the windows logon script?]
If you’re looking for the location of the active logon script in a Windows domain network on a workstation, or just to figure out which logon script is being used for a workstation
TLDR; ‘Get to the point, where is the bleeding thing?!’:
To find the location of a user’s logon script, while logged in as the user, run the command:
net user “%USERNAME%” | find “Logon script”
or for a domain user,
net user “%USERNAME%” /domain | find “Logon script”
The logon scripts themselves can be found on the network in the standard domain network share location:
Additionally, the commands:
net user “%USERNAME%” /domain
Give interesting results for the current user and what Group policy rules are active for the currently logged in user/(machine?) respectively.
Obviously this is only relevant to windows computers in active directory with primary domain controller and group policy ordaining that each machine should run a logon script.
Things i searched for in order to try and find this out:
- find out what logon script a computer is using
- find path of logon script from workstation
- find path of logon script from workstation registry
(I couldn’t find the registry location as it turns out!)
If this post helped you, or you have additional tips, please leave them in the comments!