sepago Spezialisten bloggen über Citrix und Microsoft

Commenter Steven asked in response to my article on how not to delete local user profiles for the correct way to script the deletion of user profiles. Here is how. For completeness sake I start with the manual method.

Deleting Profiles Manually

1. Open the control panel applet „System Properties“ and navigate to the tab „Advanced“. I know of the following shortcuts for this often needed dialog box:
   • Press Win+Break
   • Press Win+R to open the run dialog box.

In many environments it is a common practice to delete user profiles prior to conducting tests in order to start with a clean slate. However, this may prove more difficult than anticipated.

Most people think that a local user profile only consists of the directory %USERPROFILE% typically located below C:\Users on Vista and Server 2008 (and newer). But there is more. Windows keeps track of the local profile incarnations in the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList.

This is the seventh part of a mini-series on Windows x64, focusing on behind the scene changes in the operating system. In the last article I explained that mixed 32-/64-bit processes are not allowed and how that rule affects both administrators and script-writers. In this context I mentioned the strangely named directory SysWOW64. Today I am going to explain what it is used for by starting with redirection. File System Redirector As you know,

This is the sixth part of a mini-series on Windows x64, focusing on behind the scene changes in the operating system. In the last article I discussed how 32-bit applications are wrapped up in the WoW64 subsystem. Today we will take a deeper look at some limitations of 64-bit Windows and what they mean in practice. RulesApplication interoperability and execution on Windows x64 is governed by a few simple rules, most of which you already know:

1. The kernel cannot execute 32-bit code.

Most technical folks have stumbled across the registry hive HKEY_USERS\.Defaultat some point. Many of them think they know what it is used for. Interestingly, most who do are wrong. The misconception about what HKU\.Default is used for dates back to the good old days when Windows NT 4.0 was still considered „new technology“. This misconception has been, and still is, passed on to future generations by means of books, magazine articles, blog entries and geek talk.

Update: The ADM file can now be downloaded here.

I recently came across a post in the Windows Server Performance Team’s blog that lists several registry values which can be used to tune Explorer’s SMB performance by modifying the following:

• Searches for Desktop.ini files used for folder customization
• Periodic refreshes of folder contents
• Searches for supporting library (.dll) files
• Individual file details and attributes pulled for each file
• Thumbnail extraction

I found the tips very interesting,

A question on the terminal services newsgroup brought this topic to my attention: how can be determined programmatically if a Windows Server 2008 system is a terminal server and whether it runs in application server or remote administration mode? With Windows Server 2008 „terminal server“ is a role that can be installed with the GUI tool Server Manager. If the role „terminal server“ is installed then the system runs in application server mode. If not,