For a long time, I’ve just dealt with having a massively long list of old VM servers in my vSphere client but today I finally decided to take a minute to do something about it as it was just getting too ridiculous to navigate to find the servers I wanted to use. A quick scour of the web led me to the following registry key, all you need to do is edit the comma separated list, delete out the entries you no longer want, and be on your merry way.
HKCU\Software\VMware\VMware Infrastructure Client\Preferences\RecentConnections
I thought I would share with you the master icon removal list for File Explorer that I’ve compiled from various sites. All of the articles I’ve come across tend to delete the icons for all user’s, but I’ve found that it is possible to delete some of them on a per user basis by creating the key structure in the HKCU section of the registry instead. You’ll just have to fiddle around with them if you want to try it.
My biggest bitch by far about Server 2012 is that it doesn’t appear to even be a finished product in regards to Group Policy lockdown procedures. On almost every account, you have to hack the damn registry to get rid of unwanted items from File Explorer not to mention the god damned Ribbon UI which I’m going to do a whole nother post to rant and rave about and explain how to customize/remove icons from it. I’m not going to go into great detail here on how to add them through Group Policy Preferences or anything so if you need to know how to do that, check out some of my other articles where I explain how to do it.
Continue reading “Server 2012/Windows 8 – Complete File Explorer Icon/Shortcut/Folder Removal List”
After much research, some poking around in the registry, and a little dumb luck, I’ve discovered a way to disable the Network icon from the left side of the File Explorer navigation pane on a PER USER basis using Group Policy Registry Preferences.
Basically, I borrowed the concept from other posts and made it work for the current user profile. One problem that I ran into trying to use the HKLM key was that I couldn’t update the key using the SYSTEM account via Group Policy and I didn’t want to manually edit registry permissions on a bunch of RDS Servers. On top of that, more importantly, I didn’t want to disable the Network icon for my administrator accounts too! So here’s what you need to do… Continue reading “Server 2012 – Remove Network Icon from File Explorer Navigation Pane via Group Policy”
Instead of using the PowerShell or VB scripts that are out there to address the User Profile Redirection display problem mentioned in Microsoft’s KB947222 article, I didn’t like the idea of having to waste precious CPU cycles on calling one of these scripts every couple of minutes so I decide to take matters into my own hands to come up with a different approach.
Those solutions do indeed work, but even if you’re running this script like once a minute, you still run into the possibility that a user might log in, which in turn creates their redirected documents folders, and then, anyone attempting to access the network share that contains the user profiles at that exact moment, would still run into the same issue until the next time the script ran via task scheduler. Not exactly a great solution.
In addition to that, at least for me, using the PowerShell script seemed to add a whole nother layer of document shortcuts that was reflected upon inside of the user’s environment making it to where they had to click on documents twice just to get into their documents folder. Again not an ideal solution.
Continue reading “KB947222 – Addressing the User Profile Redirection Display Problem with a Different Approach”
Classic Shell is a necessary evil for any normal Windows user who wants to be able remain productive with introduction of the Start Screen in Server 2012 and Windows 8. As a network administrator, I highly recommend Classic Shell because it even has it’s own Group Policy templates that you can add in with the PolicyDefinitions inside your domain’s SYSVOL folder so you can at least somewhat try to put the Start Menu back to the way it once was. The Start Screen is a technical support person’s worst nightmare for novice users who don’t deal well with change (and trust me they don’t).
If you’re trying to customize a Remote Desktop Server environment, one somewhat annoying thing you will run into is trying to get rid of the first run wizard for Classic Shell. Obviously, the first run wizard is handy for anybody who wants to customize the look and feel of their Start Menu, but more than likely in a Remote Desktop environment, you’re going to want all this predefined with no user interaction so the chances of them screwing things up is slim to none.
Continue reading “Classic Shell – Remove First Run Wizard with Group Policy”