This blog post is also available in PDF format as a cialis dosages target=”_blank”>TechRepublic download.

Sometimes, depending on the manufacturer and on the particular layout, your keyboard can be a great source of frustration. For TechRepublic reader Frank Reeves, the Caps Lock key is the one that drives him crazy. After seeing the TechRepublic How do I… about how to disable the Insert key in Word, he asked for information on how to similarly disable the Caps Lock key.

There are several ways to accomplish this task. One way is to discover the scan code for the Caps Lock key and for the key you want to map it to and then edit the Windows registry. The folks at Annoyances.org explain this method. However, their explanation is more complicated than it needs to be, and there are easier and safer ways to accomplish the same thing.

Third-party keyboard layout and mapping tools are available that will allow you to change the behavior of the Caps Lock key, but many of these really boil down to a .reg file, which edits the Windows registry for you. In general, these .reg files are fine and come from people and organizations just trying to help make your life easier, but it still involves a stranger editing your Windows registry files. That makes me uncomfortable.

The best way to remap the Caps Lock key or any key on your keyboard is with a free utility from Microsoft called remapkey.exe. This little utility is available in the Windows Server 2003 Resource Kit Tools. It is one of many utilities included in the kit and works with Windows 2000, Windows XP, Windows Server 2003, and Windows Vista. This TechRepublic How do I… shows you how to use the remapkey.exe utility to remap the Caps Lock key.

Remapping

Once you download and run the Windows Server 2003 Resource Kit Tools file, you will have a long laundry list of utilities located in a single directory. I used the default location (Figure A):

Figure A

Tools

When you start the remapkey utility, it presents a screen displaying two keyboards, as shown in Figure B.

Figure B

Remapkey utility

The top keyboard is the standard base keyboard layout. To remap the Caps Lock key, in the top keyboard, click on the key you would like the Caps Lock to be remapped to, drag it to the bottom keyboard, and drop it on the Caps Lock key there. In my example, I am remapping the Caps Lock key to the left Shift key. (Note the red key in Figure C.)

Figure C

Caps Lock is now left Shift.

When you are satisfied with your remapping choices, click the Save And Exit icon to implement the change (Figure D). A reboot of the operating system will be required for the change to take effect.

Figure D

Save your settings and exit.

As you can see in Figure E, the remapkey utility is writing to the Windows registry, just like the methods mentioned earlier were going to do, but this gives you more control over that delicate editing process.

Figure E

Remapkey writes to the Windows registry.

Note: For Windows Vista, you will have to run the remapkey utility in administrator mode.

When you take a look at Windows Server 2008, you’ll discover big changes — including some legitimate improvements.  Justin James outlines a few of the unexpected aspects of the new OS, both good and bad.

Windows Server 2003 felt like a refresh of Windows Server 2000. There were few radical changes, and most of the improvements were fairly under the surface. Windows Server 2008, on the other hand, is a full-size helping of “new and improved.” While the overall package is quite good, there are a few surprises, “gotchas,” and hidden delights you will want to know about before deciding if you will be moving to Windows Server 2008 any time soon.

Note: This information is also available as a PDF download.

#1: The 64-bit revolution is not complete

There have been 64-bit editions of Windows Server for years now, and Microsoft has made it quite clear that it wants all of its customers to move to 64-bit operating systems. That does not mean that you can throw away your 32-bit Windows Server 2008 CD, though! Over the last few months, I have been shocked on more than one occasion by the pieces of Microsoft software that not only do not have 64-bit versions, but will not run under a 64-bit OS at all. This list includes Team Foundation Server and ISA Server. If you are planning on moving to 64-bit Windows Server 2008, be prepared to have a 32-bit server or two around, whether it be on physical hardware or in a VM.

#2: Who moved my cheese?

While the UI changes in Windows Server 2008 are not nearly as sweeping as the Aero interface in Vista, it has undergone a dramatic rearrangement and renaming of the various applets around the system. In retrospect, the organization of these items is much more sensible, but that hardly matters when you have years of experience going to a particular area to find something, only to have it suddenly change. Expect to be a bit frustrated in the Control Panel until you get used to it.

#3: Windows Workstation 2008 might catch on

In an odd turn of events, Microsoft has provided the ability to bring the “Vista Desktop Experience” into Windows Server 2008. I doubt that many server administrators were asking for this, but the unusual result is that a number of people are modifying Windows Server 2008 to be as close to a desktop OS as possible. There have always been a few people who use the server edition of Windows as a desktop, but this makes it much easier and friendlier. These home-brewed efforts are generally called “Windows Workstation 2008,” in case you’re interested in trying it out on your own.

#4: Hyper-V is good, but…

Hyper-V was one of the most anticipated features of Windows Server 2008, and it’s surprisingly good, particularly for a version 1 release from Microsoft. It is stable, easy to install and configure, and does not seem to have any major problems. For those of us who have been beaten into the “wait until the third version” or “don’t install until SP1″ mentality, this is a refreshing surprise.

#5: …Hyper-V is limited

Hyper-V, while of high quality, is sorely lacking features. Considering that it was billed as a real alternative to VMWare and other existing solutions, it is a disappointment (to say the least) that it does not seem to include any utilities for importing VMs from products other than Virtual PC and Virtual Server. Even those imports are not workaround-free. Another real surprise here is the lack of a physical-to-virtual conversion utility. Hyper-V may be a good system, but make sure that you fully try it out before you commit to using it.

#6: NT 4 domain migration — it’s not happening

If you have been putting off the painful migration from your NT 4 domain until Windows Server 2008 was released, don’t keep waiting. The older version (3.0) Active Directory Migration Tool (ADMT) supports migrations from NT 4, but not to Windows Server 2008. The latest version (3.1) support migrations to Windows Server 2008, but not from NT 4. Either migrate from NT 4 before changing your domain to be a Windows 2008 domain or get your NT 4 domain upgraded first.

#7: The ashtrays are now optional

In prior versions of Windows Server, a lot of applications came installed by default. No one ever uninstalled them because they did not cause any harm, even if you didn’t use them or installed an alternative. Now, even the “throwaway” applications, like Windows Backup, are not installed by default. After installation, you need to add “features” to get the full Windows Server suite of applications. This can be frustrating if you are in a hurry, but the reduced clutter and resource overhead are worth it.

#8: Licensing is bewildering

Continuing a hallowed Microsoft tradition, trying to understand the licensing terms of Windows Server 2008 feels like hammering nails with your forehead. So maybe this isn’t so much a surprise as a gotcha. The Standard Edition makes sense, but when you get into the issues around virtualization in Enterprise and Datacenter Editions, things can be a bit confusing. Depending upon your need for virtual machines and the number of physical CPUs (not CPU cores, thankfully) in your server, Enterprise Edition may be cheaper — or it may be more expensive than Datacenter Edition. One thing to keep in mind is that once you start using virtual machines, you start to like them a lot more that you thought you would. It’s easy to find yourself using a lot more of them than originally expected.

#9: There’s no bloat

Maybe it’s because Vista set expectations of pain, or because hardware has gotten so much cheaper, but Windows Server 2008 does not feel bloated or slow at all. Microsoft has done a pretty good job at minimizing the installed feature set to the bare minimum, and Server Core can take that even further. Depending upon your needs, it can be quite possible to upgrade even older equipment to Windows Server 2008 without needing to beef up the hardware.

#10: Quality beats expectations

Microsoft customers have developed low expectations of quality cialis dosage 20mg over the years, unfortunately, with good reason. While its track record for initial releases, in terms of security holes and bug counts, seems to be improving customers are still howling about Vista. As a result, it has come as a real surprise that the overall reaction to Windows Server 2008 has been muted, to say the least. The horror stories just are not flying around like they were with Vista. Maybe it’s the extra year they spent working on it, or different expectations of the people who work with servers, but Windows Server 2008 has had a pretty warm reception so far. And that speaks a lot to its quality. There is nothing particularly flashy or standout about it. But at the same time, it is a solid, high quality product. And that is exactly what system administrators need.

For the end user, increased productivity can be dependent on the familiarity of their working environment, which is encompassed in the Windows XP user profile.

——————————————————————————————————————-

A user profile on a Microsoft Windows XP system contains all the files and settings needed to configure your work environment. If the user profile becomes damaged, Windows XP will display one of two error messages when you log on to the system:

OR:

The system has recovered from a serious error.

The operating system will then automatically create a new user profile and log you in to this new profile. When this occurs, you’ll immediately discover that all your personalized settings — such as color scheme, wallpaper, and icons — are gone. Even more disturbing is that the My Documents folder doesn’t show any of your documents. You’ll also discover that Outlook Express and Internet Explorer will be void of any of your personal settings and data.

When this happens, it’s very easy to quickly go into panic mode and think that you’ve lost everything. However, in most cases, all you’ve actually lost is the user profile and most, if not all, of your data is safe and sound.

This blog post is also available in PDF format as a TechRepublic download.

Must be an administrator

Keep in mind that in order to perform the recovery operations discussed in this article, you must be working from an account with Computer Administrator privileges. If the temporary account that Windows XP creates for you when your original becomes damaged has Computer Administrator privileges, you can use it as a staging area for the recovery operation. If it’s not, you’ll need to log off, then log on to the default Administrator account or to another account that has Computer Administrator privileges. I’ll refer to this as the “working account” throughout this article.

Backing up your data

The first thing that you’ll want to do is make sure that the data in your original account is safe and then back it up. To begin the backup operation, launch Windows Explorer and navigate to the C:\Documents and Settings folder. Then, locate and cialis cheapest open your original account folder. At this point, you should see all the files and folders in your original user profile, as shown in Figure A.

Figure A

You can open your original account folder and back up all the files and folders containing crucial data.

You’ll then want to copy your crucial data files to another location. For example, you’ll definitely want to copy the contents of your My Documents folder, which will appear as UserName’sDocuments. (On my example system, it’s called Greg Shultz’s Documents.) You may also want to copy the contents of the Favorites folder. If you’re using Outlook Express, you can find the files that make up your e-mail messages stored in the Local Settings\Application Data\Identities\{#####}\Microsoft\Outlook Express folder. You’ll find your Address Book file in the Application Data\Microsoft\Address Book folder. If you’re using Outlook 2000/XP, you’ll find the PST file in the Local Settings\Application Data\Microsoft\Outlook folder.

Once you’ve backed up your crucial data files, you can proceed with the recovery operation knowing that your data is indeed safe and sound.

Using System Restore

The first thing to try when attempting to recover a damaged user profile is a System Restore operation. As you know, the System Restore utility is designed to allow you to return your computer to the state it was at an earlier time period. In this case, the goal is to return your system to the state it was in before the user profile was damaged.

Before you attempt this operation, there are two things you need to be aware of. First, if there are multiple user accounts on the system, performing a System Restore operation will return all user profiles to the state they were in at that earlier time. Second, depending on the severity of the damage to the user profile, performing a System Restore operation may not be able to rectify the problem.

You’ll find the System Restore utility on the All Programs | Accessories | System Tools menu. Once you launch System Restore, you’ll see the Welcome To System Restore page and can simply click Next. On the Select A Restore Point page, select the last restore point created before the damage to the user profile became apparent, then click Next. When you’re prompted to confirm the operation, click Next, and the restore operation will begin.

Once System Restore finishes, it will restart the system. When it does, you can attempt to log on using your original user account. If System Restore was able to successfully recover the user profile, everything should be the way it was.

If you’re still unable to log on to your original account, it’s time to escalate your user profile recovery operation to the next level. However, you may first want to undo the System Restore operation.

To undo the System Restore operation, log on to the working account and launch System Restore. When you see the Welcome To System Restore page, you’ll discover a new option titled Undo My Last Restoration. Just select that option, click Next, and follow the onscreen instructions.

Copying your user profile

In this user profile recovery technique, you’ll attempt to revive the user profile by creating a new account and, subsequently, a new user profile. You’ll then copy your old user profile in its entirety to the new account. While this may sound like an operation that will simply replicate the problem over to the new account, it does indeed revive the user profile on occasion. Again, keep in mind that the success of this attempt depends on the severity of the damage to the user profile. However, since it’s a relatively painless operation, it’s worth a shot.

To begin, access the Control Panel and launch the User Accounts tool. Next, select the Create A New Account link. Then, give the account a name and click Next. When prompted to pick an account type, make sure the Computer Administrator option button is selected, and then click the Create Account button.

Once you create the new account, close the User Accounts tool. Then, click Start | Log Off. When you see the Log Off Windows dialog box, click the Log Off button. When either the Welcome Screen or the Log On To Windows dialog box opens, select or type the name you used for the new account. As soon as you do, Windows XP will create a user profile for the new account.

When the user profile creation procedure is complete and the system starts up, immediately click Log Off. Then, log back on to the working account.

Now, open the Start menu, right-click My Computer, and select Properties. When you see the System Properties dialog box, select the Advanced tab. Then, locate and click the Settings button in the User Profiles section. You’ll now see a User Profiles dialog box that looks like the one shown in Figure B.

Figure B

You’ll use the User Profiles tool to copy your old user profile to the new account.

In this example, I’ll be copying the user profile from the Greg Shultz account to the Greg Shultz2 account. I’ll begin by selecting the Greg Shultz user profile and clicking the Copy To button. When the Copy To dialog box appears, click the Browse button and then use the resulting Browse For Folder dialog box to locate the Documents and Settings folder and select the new account.

At this point, the Copy To dialog box will look like the one shown in Figure C. To continue, just click OK. You’ll then see a confirmation dialog box that informs you that the original files will be deleted and prompts you to confirm the copy operation. Just click Yes.

Figure C

At this point, you’ll see the path to your new account in the Copy To dialog box.

Once the copy operation finishes, close the User Profiles dialog box and the System Properties dialog box, then log off. At this point, you can attempt to log on to the new account. If this technique was able to successfully recover the user profile, everything should be the way it was.

If you’re still unable to log on to your account, it’s time to move to the next level. However, you’ll first need to completely remove the new user account and user profile. To do so, log on to the working account, access the User Profiles dialog box again, select the profile, and click the Delete button. Then, access the User Accounts tool and delete the new account and its files.

Moving to a new user profile

In this user profile recovery technique, you’ll move to a new user profile by creating a new account and, subsequently, a new user profile. You’ll then copy your data files and other portions of the user profile from your original to the new one. Keep in mind that when you move to a new user profile in this manner, you will lose all your personalized settings, such as color scheme, wallpaper, and icons.

You’ll follow the instructions I presented earlier for creating a new account and a new user profile. In short, you’ll access the User Accounts tool to create a new account. Then, log on to the new account to create a default new user profile. Finally, log off and then log back on to the working account.

To begin this operation, launch Windows Explorer and navigate to the C:\Documents and Settings folder. Then, locate and open your original account folder. At this point, you should see all the files and folders in your original user profile, as shown earlier in Figure A.

Copy the contents of the folders containing the data that you want to move to your new user profile. In the case of my example system, I’d begin by copying the contents of the C:\Documents and Settings\Greg Shultz\Greg Shultz’s Documents folder to the C:\Documents and Settings\Greg Shultz2\Greg Shultz2’s folder.

In addition, you’ll want to copy the contents of the Favorites, Outlook Express, and Address Book folders if you’re using that e-mail program, or the Outlook folder. You may also want to copy the contents of Cookies, Templates, and any other folders that contain critical data files.

Be careful not to copy any files that are specifically related to the operating system, as any one of those files could be the culprit in the case of the corrupted user profile. For example, you definitely won’t want to copy Ntuser.dat, Ntuser.pol, or Ntuser.ini from your old user profile to your new one.

When you’re finished copying files, log out of the working profile, and then log on to your new user profile. When you do, you should be able to access all your data files and most of your applications, just as you did with your old profile. However, keep in mind that you may have to reinstall or at least reconfigure some of your applications. And, of course, you’ll need to recreate all your personalized settings.

Cleaning out your old profile

Once you’ve totally moved into your new user profile, you’ll want to permanently delete your old, corrupted user profile. While you may be tempted to do so from within Windows Explorer, you shouldn’t because it won’t completely remove all the settings associated with your old user profile.

To do it the right way, access the User Profiles tool from the Advanced tab of the System Properties dialog box. Once you do, select the old user profile from the list and click the Delete button.

The automatic user profile backup technique

So you won’t ever have to go through all these troubleshooting steps should the user profile ever get corrupted again, you can trick Windows XP into administering the local user profile as if it were a roaming user profile. When you do so, Windows XP will back up your user profile each time you log off.

To use this trick, you have to log off your new account and log on to the working account. Then, access the User Profiles tool from the Advanced tab of the System Properties dialog box, select your user profile, click the Copy To button, and type the name of a folder on another drive in the Copy Profile To text box.

Once you complete that part of the operation, launch the Computer Management console, which you can do by pressing [Windows]-R and typing compmgmt.msc in the Open text box. Then, drill down to System Tools\Local Users and Groups\Users folder. Next, double-click on your account name and select the Profile tab. Then, type the path to the backup in the Profile Path text box, as shown in Figure D.

Figure D

You can configure Windows XP to automatically back up the local user profile each time you log off.

Although remote desktop is one of the Windows administrator’s most essential tools, some functionality is removed in Windows Server 2008. Rick Vanover dives into what this means and explains why this is not exactly bad news.

——————————————————————————————————————-
Starting with Windows Server 2003, administrators have been able to redirect the server’s console to a remote desktop session. This is referred to as session zero, and it is invoked like this:

mstsc /v:servername /console

Now that we’re accustomed to this connection opportunity, Windows Server 2008 has removed the session zero connection option.

While the console redirection was a nice way to connect to a server when the existing two sessions were in use, it had its limitations. The number one problem with session zero is interactive device driver installations that occur via a plug and play enumeration of multiple devices. This most frequently occurs when adding multi-port serial adapters, a USB hub with multiple ports, or any other device that has a controller and subsequent individual devices. The root device would install correctly, but whenever the individual ports were enumerated, this functionality would not work correctly via a console redirected remote desktop session.

True console access is still best served by device extension mechanisms (such as a keyboard/video/mouse device), hardware controller (such as the Dell DRAC, HP iLO, cialis cheapest price VNC, pcAnywhere, DameWare), or other products that do a true console redirection.

If you attempt to connect to a Windows Server 2008 system with the /console parameter, it will ignore that option and pass the session on for a connection.

For the newest version of the remote desktop client software (6.1), the /admin parameter is a new feature, but it doesn’t really change much based on how administrators have used remote desktop over the years. These changes are outlined in the Microsoft KB article 947723.

October 29th, 2008

Posted by Ed Bott

It’s impossible to offer a comprehensive evaluation of a product as big and sprawling as Windows 7 with just screenshots and specs. That’s doubly true when looking at a preliminary release that’s still missing some key features. My first look at the pre-beta PDC release of Windows 7 inspired plenty of great feedback and questions, along with an understandable amount of confusion and apprehension. I’ll address some of the most prevalent questions and comments in this post.

Isn’t the new Windows 7 user interface just a coat of paint slapped over the Vista UI?

Short answer: no. The build I have to work with is very Vista-like, missing the new Start menu, desktop, and taskbar enhancements. The demos I’ve seen here at PDC use more recent builds where those features are available. Those features will reach users in the form of a beta “early next year.”

In the past 48 hours, I’ve had a chance to get a closer look at those new UI features. One thing becomes obvious after only a few minutes of playing with the new interface: The Windows 7 design team has paid an enormous amount of attention to small details and have focused on workflows and end-to-end experiences, not just on dialog boxes and feature sets. The result feels comfortingly familiar cialis 20 mg cost to any Windows user, although the overall experience is often significantly different when you break down its small details.

One example that illustrates the point is the difference between Backup programs in Windows Vista and Windows 7. The Windows 7 version, shown below, includes a key feature missing from its Vista predecessor – the ability to include or exclude a folder from a backup set. But that’s not all: the entire workflow of the backup process has been streamlined dramatically. It takes 10-15 clicks to perform an image backup in Windows Vista; on a Windows 7 notebook I tested, the operating system offered to perform a backup when I plugged in an external hard drive. The entire process took three clicks and less than 10 minutes. The customization screen shown here added only two clicks to the entire process.

Is it faster? Really?

Measuring performance is tough enough with released code. For something billed as a “pre-beta” release and offered primarily for developers, it’s inappropriate and frankly foolish to even attempt granular measurements of speeds and startup times. My subjective impression is that this OS feels quick and impressively responsive, but I’m not prepared to break out the stopwatch until I have a more polished build.

In fact, when I sat down with Windows boss Steven Sinofsky for a one-on-one chat on Monday, he noted that much of the work Microsoft has done with Windows 7 involves interaction with hardware OEMs, helping them see how decisions they make – tuning the BIOS, choosing drivers, and pre-installing software – impact overall performance.

Sinofsky noted that the system I’m currently traveling with – a Sony Vaio TZ2000 with Windows Vista Business – will start up the PDC build of Windows 7 in 15 seconds. I’ll be installing the Windows 7 bits on this machine to see that level of performance for myself.

Isn’t this just a blatant ripoff of OS X/KDE/etc.?

Tracing the ancestry of UI innovations is tricky. There are, after all, only so many ways to interact with pixels on a screen to make things happen. And it’s foolish not to pay attention to what competitors past and present have done. As I pointed out in my first look, the new taskbar clearly borrows some concepts from the OS X dock, but it retains the Windows DNA and adds some smart behaviors that one-up Apple, most notably Jump Lists and live, clickable previews.

Ironically, the company with the most right to complain about UI ripoffs is Microsoft itself. In a presentation at PDC yesterday, Microsoft Senior Program Manager Chaitanya Sareen traced the lineage of those big taskbar buttons back to Windows 1.01, which was released in 1985. Desktop gadgets? Those were a key part of IE4’s Active Desktop in 1997.

What’s in it for corporate customers?

If you’re an IT pro who’s chosen to stick with XP and eschew Vista, many of the enterprise-focused benefits of Windows 7 are features you could have gotten with a Vista deployment, most notably improvements in group policy and image-based deployment. But there’s plenty of good stuff in Windows 7 as well, as my ZDNet colleague Mary Jo Foley outlined earlier today.

Microsoft hasn’t spent a lot of its Windows 7 demo time on corporate features. But the most noteworthy addition I’ve seen so far is native support for virtual hard drive (VHD) images. Using Windows 7, you’ll be able to mount a VHD as a local drive and, more importantly, boot from that virtual image. The most obvious application is rolling out a standard corporate image to remote workers, such as those in a call center, who don’t require local data storage and are capable of working in a strictly managed, locked-down configuration.

Is the Shut Down button fixed?

Yes. It’s not in the PDC builds, but the new Start menu that will be available in the beta release next year has replaced the confusing Vista power-button icon with an easy-to-customize alternative, shown here.

I know that you, dear readers, have questions of your own. Hit the Talkback button and ask away. I’ll answer the most interesting questions in my next installment.