Step-by-step guide to documenting your network
http://www.networkworld.com/news/2014/051214-guide-documenting-network-281391.html
http://www.networkworld.com/news/2014/051214-guide-documenting-network-281391.html
A list of those random things you find really useful when fixing IT issues. It takes ages to track them down again later, and you KNOW you'll come across the issue again. So here they are for me...and YOU...to refer back to any time.
As a starter:- redirect the startmenu for all users to a shared location
- enable access based enumeration for that share
- copy shortcuts to applications to that share (best to make a folder for each application)
- create security groups for the applications you wish to restrict to certain groups of users
- replace the security on the folder in the redirected startmenu. remove authenticated users and such, and add the correct application security group with read rightsIf you look in the startmenu now, you will not only see the application folders as "groups" in the all programs part of the startmenu, you will also only see applications for which you were granted access rights.Login with a test user, arrange your tile-menu, and then, while this test user is logged on, export the .ms file holding the tile positions and such. Add this .ms readonly file to the correct location in the default user profile and mark it read-only, and make sure (script, gpo) that this .ms is marked read-write when a new user first logs on.
If you encounter the error message, you simply need to use Server Management Console to install the Windows PowerShell 2.0 Engine feature.Could not load file or assembly 'System.Management.Automation' or one of its dependencies.