When the Application log on a Windows 2000 Server machine with default settings reaches capacity at 512KB, the log produces an error message that it's full, even though the default setting lets it overwrite events older than 7 days. How can I prevent the log from generating the error message?
Your system is probably generating enough events within the 7-day period to exceed the 512KB maximum log size. To prevent the error message, you can either set the event-log settings for each of your logs to Overwrite events as needed or increase the maximum log size (I typically use 5MB—5120KB—on my servers). To change these settings, open Windows NT Event Viewer (either from the Administrative Tools program folder or as a component within Microsoft Management Console—MMC), highlight the log in Event Viewer's left pane, right-click it, and choose Properties to configure that log's maximum size and how the system handles situations in which the log reaches the maximum size, as Figure 1 shows.
I've tried to use the Microsoft Windows 2000 Server Resource Kit's RDPClip utility with Windows XP's Remote Desktop Connection (RDC—XP's universal RDP client) connected to a Win2K Server Terminal Services server, but I can't copy files to or from the terminal server. Using RDPClip to copy files worked fine with the Win2K RDP client. How can I reenable this functionality?
Unfortunately, the XP RDC client (which you can install and run under both XP and Win2K) seems to break the functionality of RDPClip. This situation is particularly true on Win2K systems that have been upgraded to the XP RDC client. One possible solution is to make the following registry change:
- Open a registry editor (e.g., regedit.exe or regedt32.exe).
- Locate the HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Default\AddIns registry subkey.
- From the Edit menu, select New, Key.
- Name the new subkey RDPDR and press Enter.
- Exit the registry editor.
If you still experience problems with file copying after you implement this fix, another solution is to use AnalogX's freeware TSDropCopy utility (http://www.analogx.com/contents/download/system/tsdc.htm). You run the utility, which Figure 2, page 42, shows, on both the terminal server and the local client. The program creates a small window on both systems' desktops. When you drag a file into one of the windows, the utility transfers the file to a designated folder on the system (i.e., server or client) at the other end of the connection. Note that TSDropCopy requires XP's RDC client software. You can download the RDC client setup utility (msrdpcli.exe) from http://www.microsoft.com/windowsxp/pro/downloads/rdclientdl.asp. The utility is also on the XP CD-ROM in the \support\tools folder. To run the setup program, insert the CD-ROM, select Perform Additional Tasks from the menu that appears, then click Set Up Remote Desktop Connection.
How can I connect a Macintosh client to a Windows terminal server?
Microsoft recently released a version of the RDP-based Remote Desktop Connection Client for Mac OS X. This client lets you connect to any RDP-based Microsoft terminal server, including Windows .NET Server (Win.NET Server) 2003 terminal servers, Remote Desktopenabled Windows XP Professional Edition clients, Windows 2000 Server Terminal Services servers, and Windows NT Server 4.0, Terminal Server Edition (WTS) servers. You can download the client from Microsoft's Mactopia site at http://www.microsoft.com/mac/download/misc/rdc.asp. Note that the Remote Desktop Connection Client for Mac OS X is, as of this writing, available only for Mac systems with one PowerPC processor; however, Microsoft is developing a version that supports dual-processor systems.
I run a Windows 2000 Server Terminal Services environment. I installed Win2K Service Pack 3 (SP3), and now users can't print to their local printers. How can I fix this problem?
I investigated and discovered that the problem affects only certain applications running on SP3 terminal servers. (I found no information about which application characteristics cause the problem.) Microsoft is working on a fix that should soon be available through Windows Update and as a separate post-SP3 hotfix download.
I want to use the Microsoft Windows 2000 Server Resource Kit's createusers.vbs utility to automate user-account creation in our Active Directory (AD) domain. The tool's command syntax requires that I know each attribute's property name to set the attribute's value. Where can I find a list of the available property names? For example, if I want to configure the Win2K Server Terminal Services Profile Path, where can I find the attribute's property name?
You can find this information at http://msdn.microsoft.com/library/default.asp?url=/library/en-us/netdir/adschema/w2k.asp. This Web site provides an extensive reference for the AD schema, including all classes, attributes, syntax, control access rights, and display names.
Recently, we changed a computer name and workgroup on a Windows 2000 system. We also changed from manually assigned IP addresses to automatic IP addressing through DHCP. After rebooting, we couldn't log on no matter what logon and password combination we used. Any suggestions?
If the computer is truly on a workgroup rather than a domain, the changes you made shouldn't affect your ability to log on by using the (ostensibly untouched) Administrator name and password in the local machine's SAM database. If you can't use the Administrator account (or equivalent account) to log on, you might need to use an administrative password recovery tool such as Winternals Software's Locksmith (http://www.winternals.com) to reset the password.
Prev. page
[1]
2
next page 
