Why when I click on a shortcut "folder" I find I cannot delete it if any items within that container are currently in view?

Hi, Thanks for posting here. Based on this description, I understand it's unsuccessful to delete a shortcut of folder. For the further troubleshooting, could you please advise me this behavior is just a specific shortcut or all shortcut? There are some common reasons for failing to delete a file, such as we do not have enough privilege to do this, this file is occupied by other process, this file is system-critical, this file is corrupted etc. Please check and remove this common factors gradually. Additionally, we can also use "filemon.exe" (which has been replaced by Process Monitor in Windows Server 2008) to inspect what process occupy this file that we fail to delete. About how to use "Filemon.exe", please refer to the below article: About Filemon for Windows v7.04 http://www.microsoft.com/technet/sysinternals/SystemInformation/Filemon.mspx You can download Process Monitor from: http://technet.microsoft.com/en-us/sysinternals/default.aspx I hope this helps. Best wishes --------------Morgan Che Microsoft Online Community Support

Hi Morgan,Thank you for your reply and for the links to sysinternals products; I am aware they are very good and have used them a number of times.My assessment of the issue is that it would most likely be related to privileges even though I only use an Administrator account and having said that I do appreciate that it requires a "real" username and password combination, as this is much safer but I was wondering as well, can I set it up so that it doesn't ask me again when the machine is "locked"?Thank you

Dear Lambaste, Thanks for posting back. I am a bit unclear about " can I set it up so that it doesn't ask me again when the machine is "locked"? Please advise me. I look forward to your reply. Thanks. Best wishes --------------Morgan Che Microsoft Online Community Support

Thanks for your reply.As you'd be aware, Microsoft platforms in the past have allowed the use of simple or "blank" passwords even for Administrator Accounts, however with Windows Server 2008 RC1, this is no longer possible and although I think it's great for security, it can also be a painwhen leaving the platformeven for a short time, then having tore-enter a password, notwithstanding any physical access controls being implemented.Thanks again for your time.

In Windows Server 2008 the option 'Password must meet complexity requirements' is on by default. (other password policies are not in effect by default) The default behavior This will forcecomplex passwords. New passwords must meet the following minimum requirements: The password is at least six characters long. The password contains characters from three of the following four categories: English uppercase characters (from A through Z) English lowercase characters (from a through z) Base 10 digits (from 0 through 9) Non-alphanumeric characters (for example: !, $, #, or %) The password does not contain three or more characters from the users account name. If the account name is less than three characters long, this check is not performed because the rate at which passwords would be rejected would be too high. When checking against the users full name, several characters are treated as delimiters that separate the name into individual tokens: commas, periods, dashes, hyphens, underscores, spaces, number signs (#), and tab characters. Each token that is three or more characters long is searched for in the password, and if it is present, the password change is rejected. For example, the name Erin M. Hagens would be split into three tokens: Erin, M, and Hagens. Because the second token is only one character long, it would be ignored. Therefore this user could not have a password that included either erin or hagens as a substring anywhere in the password. None of these checks are case-sensitive. Changing thedefault behavior There are two ways to change this default behavior: It is possible to create your own passfilt.dll and replace the default filter. This will give you more granular control over the requirements for new password, but will not allow you to usea blankpassword. Disable the 'Require password complexity' option. Domain Joined serversFor Domain joined servers you can create a domain wide policy that will allow you to set a password policy, that will apply to all users in your domain.In Windows Server 2008 you can also create a Fine Grained Password Policy. Non-Domain Joined serversFor Windows Server 2008 boxes that are not a member of the domain you can disable the option using Local Policies. The process on Windows Server 2008 is similar to Windows Vista. After you changed the behavior you can change your password to anything you'd like, inclusing a blank password. Note:When you use a blank password for an account, the account cannot be used as a network credential.

Hi Sander,Thanks for the information and links, it is appreciated.I understand about complexity requirements, and also the three or more character rule and that is all fine, however notwithstanding creating my own pasfilt.dll file and then allowing specification of a blank password (non-network credential) I simply need a way to stop it asking me to enter a password post locking of the machine and I don't see why any of these kinds of options are contained within power settings.Hoping you can help.Best regards.