letters@winnetmag.com

EDITOR'S NOTE: Windows & .NET Magazine welcomes feedback from readers about the magazine. Please send comments to letters @winnetmag.com and include your full name, email address, and daytime phone number with your letter. We edit all letters and replies for style, length, and clarity.

Weighing In on Software Upgrades
I read Michael Otey's Editorial: "Microsoft's Worst Enemy" (March 2004, InstantDoc ID 41673), and I agree with most of the points he made about companies not upgrading to new products because earlier versions are "good enough." However, Microsoft can force companies to upgrade by discontinuing support for a given product, especially server products.

I'm the program manager for EDS's Windows NT 4.0 migration program.

Microsoft's decision to discontinue support for NT 4.0 prompted us to undertake a major program initiative to migrate all of our NT 4.0 servers. Yes, NT 4.0 might be "good enough" for some companies who currently run the OS, but with proliferating virus threats and security holes, NT 4.0 is no longer good enough for our company. We know that we can't expect Microsoft to support products forever, so we must upgrade.

—Kendall Pierce kendall.pierce@eds.com

I remember a time when a Microsoft software upgrade gave me more features for my money. I could install an upgrade and gain a better functioning system with more options than the previous software version had. Now, however, some of the latest upgrades are more like downgrades.

Take Microsoft Exchange Server 2003, for example. I recently purchased this version of Exchange only to find out after the fact that Microsoft removed the Instant Messaging Server functionality and recommends replacing it with Microsoft Office Live Communications Server 2003. When I contacted Microsoft about the change, I found out that Live Communications Server is available only for an additional charge.

In another example, one of my clients purchased Windows Server 2003 to use solely as a terminal server. I found out that Microsoft's change in licensing for Terminal Services requires a separate Client Access License (CAL) for every OS, including XP Pro and Win2K Pro. (Win2K Terminal Services doesn't require a CAL for XP Pro or Win2K Pro clients—only for Windows Me, Windows 9x, and other OSs.) So, my client ended up upgrading a server to the latest version only to have to pay more to achieve the same level of functionality of an earlier version.

I believe in Microsoft and its products. I truly believe those products are the best available, but this abuse has to stop. I urge everyone with a similar complaint to write to your local Microsoft representatives and tell them how angry you are with this situation. In the past, an upgrade was simply an upgrade. Now, I have no idea what I'm going to end up with when I install a new product without combing through the fine print.

—Jared Shapiro jared@infinitysol.com

Offline File Synchronization
I've been looking for the answer to a problem and haven't had much luck. If I create a folder under a folder that has offline file synchronization enabled, will the folder that I create automatically become an offline folder? My client OS is XP Pro, and I connect my XP machine to synchronize with Win2K Server in a domain environment.

—Walter Flynn walter@protekcc.com

The answer to your question is yes and no. Yes because subfolders under an offline file folder are part of the parent folder's synchronization process. No because by default the client side (e.g., XP Pro) won't synchronize the subfolders unless you change the default policy.

To change XP Pro's client-side policy to include subfolders in synchronization, click Start, Run, then enter mmc and click OK. On the File menu, choose Add/Remove Snap-in, and Click Add. Select Group Policy, then click Add. Select Local Computer in the Group Policy Object box and click Finish. Click Close, then click OK. Now, find Local Computer Policy under Console Root and click the plus sign (+) to its left to expand it. Expand Computer Configuration\AdministrativeTemplates\Network\Offline Files in the left pane. In the right pane, double-click Subfolders Always Available Offline. Click Enabled, then click OK. Close the MMC, but don't save the settings to the console.

After you make these changes, subfolders will be synchronized on the client computer when the parent offline folder is synchronized. A domainwide policy is available (i.e., on Domain Group Policy). I haven't tested it, but I assume it works for all client computers on a domain.

If you want a particular workstation to synchronize subfolders, change Group Policy by taking the steps above on that workstation (or on selected multiple workstations). If you want all workstations that access the Offline Files folder on a domain to be able to synchronize subfolders, edit Group Policy for the domain. Be aware that offline files tend to be flaky, with unexpected and unexplainable events, such as a reported synchronization that doesn't really sync or error messages that a synchronization failed when it succeeded. Also, synchronization doesn't work well for roaming user profiles. You might want to test the changes on one workstation, and if synchronization works well, make a domain Group Policy change to apply to all workstations on the domain.

End of Article