Windows – Cannot Delete Thumbs.db

KB ID 0000683

Problem

Thumbs.db is a small hidden system file that gets generated when you view media in a folder, you know when you look at all your MP3 songs and you can see the album cover as a thumbnail? Or you can see what all your photos are as a tiny thumbnail before you open them, well thats what the thumbs.db file is doing. It’s a tiny cache of all that information so next time someone visits this folder it displays those pictures quicker. Well that’s great! But when you try and delete a folder with one in (particularly a folder on another machine) you can see the error below.

The file Thumbs.db is a system file if you remove it, Windows or another program may no longer work correctly.

Then it won’t let you delete it, and if you persist, you end up with a folder with just this file in it, that you cant delete.

Solution

First Step – Delete the Thumbs.db file

OK, lets solve the initial problem first and get rid of the one thats annoying us at the moment.

1. In Windows 8/2012 whilst in the folder > File > Open command prompt as administrator. (With older versions of windows hold down SHIFT and right click).

2. Issue the following commands;

[box] attrib -s -h thumbs.db del thumbs.db [/box]

Stop your PC Generating Thumbs.db Files

Option 1

Open Windows Explorer > View Options > Change folder and Search Options > View > Enable ‘always show icons, never thumbnails’ > Apply > OK.

Option 2 (Use the Local Policy of the Machine)

1. Press Windows Key+R to launch the run menu > gpedit.msc > OK.

2. Navigate to;

[box] User Configuration > Administrative Templates > Windows Components > File Explorer {or Windows Explorer} [/box]

Locate the ‘Turn off caching of thumbnail pictures’ policy.

3. Enable > Apply > OK.

Option 3 (Use the Registry)

You can simply run the following command;

[box] REG ADD “HKCUSoftwarePoliciesMicrosoftWindowsExplorer” /v “DisableThumbsDBOnNetworkFolders” /t REG_DWORD /d 1 /f [/box]

Or to do it manually,

1. Press Windows Key+R to launch the run menu > gpedit.msc > OK.

2. Navigate to;

[box] HKEY_CURRENT_USER > Software > Microsoft > Windows > CurrentVersion > Explore > Advanced [/box]

Create a New DWORD Value.

3. Call it DeleteThumbnailCache and set its value to 1.

Remove all Thumbs.db Files

Finally lets tidy up any remaining thumbs.db files.

Option 1

1. Open Windows Explorer (Windows Key+E) > Right click the drive > Properties > Disk Cleanup.

2. Select Thumbnails > OK.

Option 2

1. From command line, issue the following commands;

[box] cd del thumbs.db /s /q [/box]

 

Related Articles, References, Credits, or External Links

NA

Stop ‘Open File – Security Warning’

KB ID 0000804 

Problem

I put in a Remote Desktop Services Server this week, and every time the users launched their line of business app,

Open File - Security Warning
The publisher of this file can not be verified. Are you sure you want to run this software.
Name: {Application name}
Publisher: Unknown Publisher
Type: Application
From: {PathApplication name}
This file does not have a valid digital signature that verifies its publisher. You should only run 
software from publishers you trust.

Solution

OK the program is not digitally signed, but this is going to annoy the client even more, I need to suppress this warning.

1. Open the local group policy editor on the machine in question. (Start > Run > gpedit.msc {enter}).

2. Navigate to;

[box]
Computer Configuration > Administrative Templates > Windows Components > Internet Explorer
[/box]

3. Locate the ‘Turn off the Security Settings Check feature’ > Set it to enabled.

Related Articles, References, Credits, or External Links

NA

Configure Wireless Network Stings via Group Policy

KB ID 0000923 

Problem

If you have a corporate wireless network, you can send the settings out to your clients, rather than have them all ask you what the wireless settings are, and how do they connect.

Here I’m going to use Domain group policies, but the procedure is the same for local policies (just run gpedit.msc instead). And the dialog boxes are exactly the same as if you were configuring them on the client machine. (You can import the settings form a working client if you like).

Solution

1. On a Domain Controller > Administrative Tools > Group Policy Management Console > Navigate to an OU that contains your computer objects and either create a new GPO, or edit an existing one.

2. Navigate to;

[box]

Computer Configuration >
Policies > Window Settings > Security Settings > Wireless Network (IEEE 802.11) Policies > Create A New Wireless Network Policy for Windows Vista and Later Releases

[/box]

3. Give the policy a name and add in an ‘Infrastructure’ type network profile.

4. Name the profile > Add in the SSID of the wireless network > Security Tab.

5. Set your authentication type, here I’m using WPA2/AES.

Optional

6. Here I want my client computers to see the wireless network, before the users log on (so that their logon scripts will run and their drives get mapped) Advanced > Enable Single Sign On > OK.

7. Properties > Remove the tick from ‘Validate server certificate’ > OK.

Note: I’m configuring for use with an HP MSM controller, if I leave this option ticked, I will have to upload the CA Cert from my domain, into the controller, or clients cannot join the wireless network.

8. I’m not making any changes to the Network Permissions tab > Apply > OK.

9. Now either wait a couple of hours, run gpupdate /force on a client, (or reboot it).

Related Articles, References, Credits, or External Links

NA

Windows Server 2008 – Enable Aero

KB ID 0000321

Problem

You might ask why? But I needed to do this the other day for some screen shots, and if I had to work out how to do it then someone else will want to use Aero on Windows Server 2008. Besides I’ve seem people running this OS on their Laptops etc, so if it were me, I’d rather look at Aero than the standard windows “Theme”.

Solution

Minimum Requirements for Aero

CPU = 1 GHz or Higher RAM = 1 GB or better Graphics Card = 128MB or better Graphics Card = DirectX 9 & Pixel shader 2.0 with 32 bits per pixel

Rule of thumb

Single monitor up to 1280×1024 = 64MB Graphics Memory Single monitor up to 1600×1200 = 128MB Graphics Memory</br? Single monitor up to 2560×1600 = 256MB Graphics Memory

Enabling Aero Theme Fore Remote Desktop Services (RDP) Users

(Updated 01/12/12). I had a user that needed his Remote Desktop Services (Terminal Services) users, to get an Aero themed desktop, so his RemoteApp applications would run with the correct icons. In this case the easiest solution is to setup a LOCAL policy on the Remote Desktop Services server to force this.

1. On the server, Windows Key+R > gpedit.msc {enter} > When the policy editor opens > Navigate to;

[box]User Configuration > Administrative Templates > Control Panel > Personalization > Force a Specific Visual Style file or force Windows Classic[/box]

Enable the policy > Set the ‘Path to Visual Style’ to;

[box]%WinDir%resourcesThemesAeroaero.msstyles[/box]

Copy that path to the clipboard > Apply > OK.

2. The next policy is directly above and is called ‘Load a specific theme’ > Enable the policy > Paste in the same path as above.

3. Close the policy editor > Then either reboot, or from command line run;

[box]gpupdate /force[/box]

Related Articles, References, Credits, or External Links

Enable Aero for RDP “One or more of the themes has been disabled by Remote Desktop Connection settings”

Original Article Written 09/09/10

Thanks to Michael Dixon at Springvale EPS for his assistance.

 

Windows Server – Enable Multiple RDP sessions

KB ID 0000471

Problem

Server 2012/2008 R2 unlike their predecessors, comes with the multiple remote desktop session restriction enabled. If you are only connecting to a server for remote administration purposes that can get a bit annoying, especially if you have a generic administrative account that multiple techs are using, and you keep kicking each other off the server.

Just as with earlier versions of Windows server you CAN have two RDP sessions at any one time, the restriction is one logon for one account. Thankfully you can disable the restriction and there are a number of ways to do so.

Solution

Server 2008 R2 Option 1: Enable Multiple RDP sessions from TSCONFIG

Note: tsconfig.msc does not work on Windows Server 2012

1. On the server, click Start and in the search/run box type tsconfig.msc{enter}. Locate “Restrict each user to a single session” Right click > Properties.

2. Remove the tick from “Restrict each user to a single session” > Apply > OK.

Server 2012 and 2008 R2 Option 2: Enable Multiple RDP sessions via the registry

1. Start > in the search/run box type regedit {enter} > Navigate to:

[box] HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlTerminal Server [/box]

Locate the fSingleSessionPerUser value > Set it to 0 (Multiple sessions allowed), or 1 (Multiple sessions NOT allowed).

Server 2012 and 2008 R2 Option 3: Enable Multiple RDP sessions via Local Policy

1. Start > in the search/run box type gpedit.msc {enter}.

2. Navigate to:

[box] Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections [/box]

Locate the “Restrict Remote Desktop Services users to a single Remote Desktop Services session” setting.

3. To enable multiple sessions set the policy to disabled > Apply > OK.

Server 2012 and 2008 R2 Option 4: Enable Multiple RDP sessions via Group Policy

1. On a domain controller > Start > in the search/run box type gpmc.msc {enter}.

2. Either edit an existing GPO that’s linked to your COMPUTERS, or create a new one and give it a sensible name.

3. Navigate to:

[box] Computer Configuration > Policies > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections [/box]

Locate the “Restrict Remote Desktop Services users to a single Remote Desktop Services session” setting.

4. To enable multiple sessions set the policy to disabled > Apply > OK.

5. Then either reboot the clients, wait a couple of hours, or manually run “gpupdate /force” on them.

 

Related Articles, References, Credits, or External Links

Original Article Written 27/06/11

Prevent Users changing Desktop Wallpaper with Group Policy

KB ID 0000461 

Problem

If you need to lock down your client machines desktops and prevent your users from changing the wallpaper, then here’s a run through on how to do it.

Solution

1. On your domain controller , Start > Administrative Tools > Group Policy Management Console > Either create a new policy and link it to your targeted USERS or edit an existing one, then navigate to;

[box] User Configuration > Administrative Templates > Control Panel > Personalization [/box]

Locate “Prevent Changing Desktop Background”.

2. Set the policy to enabled, then either reboot the clients, wait a couple of hours, or manually run “gpupdate /force” on them.

3. Your users will no longer be able to select the “Desktop Background” link to change it.

4. If your users locate a picture on the internet they cannot select “Set as Background”.

5. If your users download a graphic and preview it, the option to “Set as desktop Background” is there but it no longer works.

My users can still “Set as Background” and “Set as desktop Background”

The above procedure works fine with Windows 7 and 2008, however some older versions of Windows still have access to these options. To fix that you need to lock active desktop then disable it.

If that’s the case, in addition to the above also do the following.

1. On the policy you edited above, navigate to;

[box] User Configuration > Administrative Templates > Desktop > Desktop [/box]

Locate “Desktop Wallpaper”.

2. Enable the policy > Set the wallpaper name to ??? (a value that does not exist) > Set the wallpaper style to Stretch.

3. On the policy you edited above, navigate to;

[box] User Configuration > Administrative Templates > Desktop > Desktop [/box]

Locate “Disable Active Desktop”.

4. Set it to enabled, then either reboot the clients, wait a couple of hours, or manually run “gpupdate /force” on them.

 

Related Articles, References, Credits, or External Links

NA

Windows – Disable the ‘Lock Screen’

Lock Screen KB ID 0000670

Problem

Also See: Stop Windows Servers ‘Locking’ with Group Policy

The Windows  lock screen is all well and good if you have a slate/tablet, but I don’t see the point of it on a Desktop PC or Laptop, (it just adds to login time).

Note: don’t get this confused with Stop Windows Asking For Password After Sleep / Standby

Lock Screen: Solution

1. Bring up the Windows run command (Press Windows Key+R). Then execute the gpedit.msc command, (Local Policy Editor)

2. Navigate to the following location;

[box]

Computer Configuration > Administrative Templates > Control Panel > Personalization > Do not display the lock screen

[/box]

3. Open the policy and set it to enabled.

Stop Windows Lock Screen via Domain Group Policy

Same place as above!

 

Related Articles, References, Credits, or External Links

NA

Stop Windows Rebooting Due To Updates

KB ID 0000773

Problem

I realise that updates are important, and Microsoft made updating easier by only releasing them once a month. But my laptop always wants to reboot at the point where I’m doing something critical! and Windows 8 unilaterally decides that its updates are far more important than my work.

OK this will only happen once a month, (normally) and it will only happen a maximum of 72 hours after the update. It affects me because I never shut my machine down, (I just close the lid).

Warning: Like I said updates are a good thing, if you disable this feature the onus is on you to keep your machine up to date!

Solution

Stop Windows 8 Rebooting Due To Updates with Group Policy

1. Press Windows Key+R > In the run box type gpedit.msc {Enter}.

2. Navigate to;

[box] Computer Configuration > Administrative Templates > Windows Components > Windows Update [/box]

3. Locate the ‘No auto-restart with logged on users for scheduled automatic updates installations’ policy. Set its value to enabled > Apply > OK.

4. Press Windows Key+R > In the run box type cmd {Enter} > At command line issue the following command;

[box] gpupdate /force [/box]

Stop Windows 8 Rebooting Due To Updates via the Registry

Note: If you have already set this in policy (above) you don’t need to do this as well.

5. Press Windows Key+R > In the run box type regedit {Enter} > Navigate to;

[box]HKEY_LOCAL_MACHINE > SOFTWARE > Policies > Microsoft > Windows[/box]

If there is not a Key Called WindowsUpdate create one.

6. And within the WindowsUpdate Key create another key.

7. Call that key AU.

8. Within that create a new DWORD (32 bit) value called ‘NoAutoRebootWithLoggedOnUsers’.

9. Set its value to 1 (one).

 

Related Articles, References, Credits, or External Links

NA

Windows 8/8.1 Stop The New User Animation

KB ID 0001078 

Problem

After spinning up quite a few Windows 8 virtual machines over the past few days, it struck me how annoying the new user account animation was.

It’s only setting up a user profile, why on earth does it take so long?

Solution

To Disable New User Animation On A Stand Alone Machine

1. Press the Windows Key and launch gpedit.msc.

2. Navigate to;</p?

[box]Computer Configuration > Administrative Tools > System > Logon > Show first sign-in animation[/box]

3. Change the policy to disabled > Apply > OK > Close the policy editor.

To Disable New User Animation On A Domain

1. On a DC or machine running the RSAT tools > Press the Windows Key and launch gpmc.msc.

2. Create a new GPO or edit a new one linked to the domain or OU containing the computers you want to enforce the policy on.

3. Navigate to;

[box]Computer Configuration Policies > > Administrative Tools > System > Logon > Show first sign-in animation[/box]

4. Change the policy to disabled > Apply > OK > Close the policy editor.

 

Related Articles, References, Credits, or External Links

NA

Disable ‘Fast user Switching’

KB ID 0000320 

Problem

Fast user switching was introduced with Windows XP (though XP can’t do this when joined to a domain). Starting with Windows Vista you COULD do this in a domain environment. Some users and sysadmins see this as a bad thing (having users logged on with sessions open that may get forgotten about).

Should you with to disable this feature then do the following,

Solution

Option 1 – Via the registry

1. On the machine in question, Start > run > regedit.

2. Navigate to HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionPoliciesSystem

3. Create (or modify if it exists) a 32 bit DWORD called HideFastUserSwitching and set its value to 1 (disabled).

4. Or simply download and run this registry file.

Option 2 – via Local Policy

1. On the machine in question, Start > run > gpedit.msc (Note not available on Windows 7 Home/Home Premium).

2. Navigate to Local Computer Policy > Computer Configuration > Administrative Templates > System > Logon.

3. In the right hand pane locate “Hide entry points for Fast User Switching” and enable.

Option 3 – via Domain Policy

1. On a domain controller, Start > administrative tools > Group Policy Editor > Either edit an existing policy or create a new one (Remember its a computer policy you need to link it to something with computers in it, if you link it to a users OU nothing will happen).

2. Navigate to, Local Computer Policy > Computer Configuration > Policies > Administrative Templates > System > Logon.

3. In the right hand pane locate ” Hide entry points for Fast User Switching” and enable.

4. Either reboot the computers or run “gpupdate/force” to apply the policy.

 

Related Articles, References, Credits, or External Links

NA