Windows

Creating a custom default user profile

This will describes how to create a custom default user profile in Windows XP. A custom default user profile is helpful if several people use the same computer but each user wants a separate profile and access to shared resources. When multiple users log on locally to the same computer, Windows XP uses the built-in default user profile as a template to assign a profile to each new user. You can replace this built-in profile with a custom default user profile so that each new user receives a custom version of the profile.

How to create a custom default user profile

Because this change is permanent, it is a good idea to make a backup copy of the default user profile, in case you ever want to use it again. The default user profile is in the Default User folder under Documents and Settings.

Create a custom default user profile

1. Log on to the computer as the administrator, and then create a local user account.
2. Log off as the administrator, and then log on to the computer through the local user account that you just created.

Caution You will cause permissions issues if you create the custom user profile when you are logged on as the administrator.
3. Customize the profile appropriately. For example, install printers and map the drives that you need.
4. Log off as the local user, and then log back on as the administrator.
5. Because several of the files in the profile are hidden and must be copied to the new custom default user profile, turn on the Show hidden files and folders option. To do so, follow these steps:
a. Double-click My Computer, click Tools, and then click Folder Options.
b. On the View tab, under Advanced settings, click Show hidden files and folders, and then click OK.
6. Replace the current default user profile with the customized default user profile. To do so, follow these steps:
a. In Control Panel, double-click System.
b. In the System Properties dialog box, click the Advanced tab.
c. Under User Profiles, click Settings.
d. In the User Profiles dialog box, click the user profile that you just created, and then click Copy To.
e. In the Copy To dialog box, under Copy profile to, click Browse, click the C:\Documents and Settings\Default User folder, and then click OK.
f. Under Permitted to use, click Change, click Everyone, and then click OK. If Everyone is not available, click Advanced, click Find Now, click Everyone, and then click OK.
Windows XP will now assign the custom default user profile to any new user who logs on to the computer.

Note: You can use this custom profile on other Windows XP-based computers by copying the profile you saved in C:\Documents and Settings\Default User to the same folder on a different computer.

Important Windows Commands

  1. Opening Active Directory Replicating Monitor – replmon
  2. Scheduling Shutdown – C:\windows\system32\shutdown.exe –r
  3. Remote Desktop Connection – mstsc

How to schedule automatic updates in Windows Server 2003, in Windows XP, and in Windows 2000

If you are logged on as an administrator, the Automatic Updates feature in Windows notifies you when critical updates are available for your computer. There is a new Automatic Updates feature that you can use to specify the schedule that Windows follows to install updates on your computer. This article describes how to install this new Automatic Updates feature in Microsoft Windows XP and in Microsoft Windows 2000 and how to use it to schedule automatic updates.

Note This new Automatic Updates feature is included with Microsoft Windows Server 2003.

For additional information about how to configure other Automatic Updates settings in Windows XP, click the following article number to view the article in the Microsoft Knowledge Base:

306525 (http://support.microsoft.com/kb/306525/) How to configure and use Automatic Updates in Windows XP

For additional information about how to configure other Automatic Updates settings in Windows 2000, click the following article number to view the article in the Microsoft Knowledge Base:

327850 (http://support.microsoft.com/kb/327850/) How to configure and use Automatic Updates in Windows 2000

Back to the top

Updating the Automatic Updates feature (Windows XP and Windows 2000 only)

Note If you use Automatic Updates, the feature may have been automatically updated on your computer. To make sure that the new feature is installed, use the procedure that is described in the Schedule Automatic Updates section of this article to confirm that the Automatically download the updates, and install them on the schedule that I specify option is available on your computer.

To use the new Automatic Updates feature, install any one of the following updates:

The “Windows Automatic Updates June 2002″ update.

To install this update, visit the following Microsoft Web site:

http://www.microsoft.com/downloads/details.aspx?FamilyID=799432fb-c196-4f01-8cce-4f9ea58d6177&DisplayLang=en (http://www.microsoft.com/downloads/details.aspx?FamilyID=799432fb-c196-4f01-8cce-4f9ea58d6177&DisplayLang=en)

Note This update is a Windows Installer package that is used for corporate deployment. You must use the new Automatic Updates feature if you are a network administrator who is using Microsoft Software Update Services. To use Automatic Updates with a server that is running Software Update Services, see the white paper on the following Microsoft Web site:

Software Update Services Deployment White Paper (http://www.microsoft.com/windowsserversystem/updateservices/techinfo/previous/susdeployment.mspx)

Windows XP Service Pack 1 (SP1). For additional information about how to obtain SP1, click the following article number to view the article in the Microsoft Knowledge Base:

322389 (http://support.microsoft.com/kb/322389/) How to obtain the latest Windows XP service pack

Windows 2000 Service Pack 3 (SP3). For additional information about how to obtain SP3, click the following article number to view the article in the Microsoft Knowledge Base:

260910 (http://support.microsoft.com/kb/260910/) How to obtain the latest Windows 2000 service pack

Note You must restart your computer after you install this update. Automatic Updates does not download any updates until you have configured it to do so. If Automatic Updates is not configured in 24 hours after you install it, either the network administrator or the user who is logged on locally as an administrator is prompted to configure it.

Back to the top

Scheduling automatic updates

Note To modify Automatic Updates settings, you must be logged on as an administrator or a member of the Administrators group. If your computer is connected to a network, network policy settings may prevent you from completing this procedure.

In Windows Server 2003 and in Windows XP

To configure a schedule for Automatic Updates:

1. Click Start, click Control Panel, and then double-click System.
2. On the Automatic Updates tab, click Automatically download the updates, and install them on the schedule that I specify.
3. Click to select the day and time that you want to download and install updates.

When critical updates are detected, Automatic Updates automatically downloads these updates in the background while you are connected to the Internet. After the download is complete, Automatic Updates waits until the scheduled day and time to install the updates. On the scheduled day and time, all local users receive the following message that has a five minute countdown timer:

Windows is ready to begin installing the updates available for your computer.

Do you want Windows to install the updates now?

(Windows will restarts your computer if no action is taken within 5:00 minutes)

If you are logged on as an administrator, when you receive this message, you can either click Yes to install the updates or click No to have Automatic Updates install the updates at the next scheduled day and time. If you do not take any action in five minutes, Windows automatically installs the updates.

Important You may have to restart your computer to complete the update installation.

In Windows 2000

1. Click Start, click Control Panel, and then double-click Automatic Updates.
2. Click Automatically download the updates, and install them on the schedule that I specify.
3. Click to select the day and time that you want to download and install updates.

When critical updates are detected, Automatic Updates automatically downloads these updates in the background while you are connected to the Internet. After the download is complete, Automatic Updates waits until the scheduled day and time to install the updates. On the scheduled day and time, all local users receive the following message that has a five minute countdown timer:

Windows is ready to begin installing the updates available for your computer.

Do you want Windows to install the updates now?

(Windows will restart your computer if no action is taken within 5:00 minutes)

If you are logged on as an administrator, when you receive this message, you can either click Yes to install the updates or click No to have Automatic Updates install the updates at the next scheduled day and time. If you do not take any action in five minutes, Windows automatically installs the updates.

Important You may have to restart your computer to complete the update installation.

Vista in Virtual Machine

A tip to installa Windows Vista in a Virtual Machine (VMWare/Virtual PC) :

Peoples who are attached to Windows Vista they can use virtualization technology to create a virtual machine on top of their current operating system which will enable the ability to fresh install Windows Vista on the newly created virtual machine. Virtual machine (VM) allows user to try and use the Windows Vista without the need to give up and format the existing partitions installed with other operating system such as Windows XP. However, using VM virtualization products (VMware, Microsoft, Parallels) to host Windows Vista on your existing hardware will likely not be able to benefit from Vista much hyped new graphic interface Aero Glass.

VMWare has (currently experimental support) support for Windows Vista as guest OS in several virtualisation products such as VMware Workstation 5.0, 5.5, 5.5.1, 5.5.2, 5.5.3, 6.0 and VMware Server 1.0, 1.0.1 (for both 32-bit and 64-bit Windows Vista), VMware ACE 1.0, 1.0.1, 1.0.2, and VMware GSX Server 3.0, 3.1, 3.2, 3.2.1 (32-bit OS only) and ESX Server 3.0, 3.0.1 (64-bit OS only). Users are encouraged to install VMWare Tools and must set the virtual machine RAM to be a least 512MB of RAM, with hard disk space of at least 16 GB (32-bit Vista) and 24 GB (64-bit Vista). Beside, all configuration changes and drivers installation must be done before activating Windows Vista, as any future changes after product activation might trigger reactivation of Windows Vista gain.

Installation of Windows Vista as guest operating system in Virtual Machine is simple. After creating the virtual machine:

  1. Insert the Windows Vista CD in the CD-ROM drive.
  2. Power on the virtual machine to start installing Windows Vista.
  3. Follow the remaining installation steps as you would for a physical machine.

If you have slow graphics performance and mouse responsiveness in the Windows Vista guest operating system, this is due to Windows Vista has display adapter hardware acceleration disabled by default. To enable display hardware acceleration in a Windows Vista guest OS, open the Control Panel, then click on Display Properties control panel and go to the Settings tab, and click Advanced. Open the Troubleshoot tab, drag the Hardware acceleration slider all the way to Full.

Other than VMWare, Microsoft has also released Virtual PC 2007 for Windows beta free virtualization software on Microsoft Connect. Virtual PC 2007 supports Windows Vista as both host operating system and guest operating system, plus some other enhancements and features:

  • Hardware-assisted virtualization

Virtual PC 2007 includes support for virtualization technology from Intel and AMD. By default, hardware-assisted virtualization is enabled if the feature is enabled on the physical computer. You can turn this assistance on or off for each virtual machine by modifying the virtual machine settings.

  • Support for Windows Vista as a host operating system

This beta release of Virtual PC 2007 introduces support for Windows Vista as a host operating system.

Following flavors of Windows Vista are supported : Windows Vista Business, Windows Vista Enterprise, Windows Vista Ultimate.

  • Support for Windows Vista as a guest operating system

This beta release of Virtual PC 2007 introduces support for Windows Vista as a guest operating system.

Following flavors of Windows Vista are supported : Windows Vista Business, Windows Vista Enterprise, Windows Vista Ultimate.

  • Support for 64-bit host operating system

This beta release of Virtual PC 2007 supports 64-bit host operating systems. However, there is no support for 64-bit guest operating systems.

Windows Vista no longer starts after you install an earlier version of the Windows operating system in a dual-boot configuration

Solution provided by Microsoft :

SYMPTOMS

After you install an earlier version of the Windows operating system on a Microsoft Windows Vista-based computer in a dual-boot configuration, you may experience one of the following issues:
  • If you install an earlier version of the Windows operating system on a Windows Vista-based computer, Windows Vista no longer starts. In this case, only the earlier version of the Windows operating system starts.
  • If you install an additional instance of Microsoft Windows XP on a computer where Windows XP and Windows Vista are already installed in a dual-boot configuration, you may receive the following error message:

         Disk read error has occurred

CAUSE

These issues occur because earlier versions of the Windows operating system are incompatible with the new Windows Vista startup method. Windows Vista uses a new Boot Configuration Database (BCD) store. This store contains a boot menu and all the information about operating systems that are installed on the computer. Therefore, a Boot.ini file that is from an earlier version of the Windows operating system cannot be used to start Windows Vista.

In earlier versions of the Windows operating system that run on a basic input/output system (BIOS)-based computer, such as Windows XP, the boot process starts with the system BIOS. The BIOS determines the boot device, and then loads the first physical sector. This physical sector is named the master boot record (MBR). The MBR contains the partition table and the necessary boot execution code. This code searches the partition table to find the active partition and passes control to the boot sector on the active partition. Then, the boot sector on the active partition loads the Ntldr program. The Ntldr program parses the Boot.ini file. This file is used to enumerate the operating systems that are installed. When Windows Vista starts on a BIOS-based computer, the BIOS loads the MBR and then loads the boot sector. However, boot code loads the new Windows Boot Manager program (Bootmgr). The Windows Boot Manager program parses the Boot Configuration Data file, enumerates the installed operating systems, and then displays the boot menu. If an earlier version of the Windows operating system is installed in a dual-boot configuration with Windows Vista, the Windows Boot Manager program transfers control to the Ntldr program for the earlier version of the Windows operating system. The Windows Boot Manager program does this when you select Windows Vista from the boot menu. When you install an earlier version of the Windows operating system on a Windows Vista-based computer, Setup overwrites everything from the MBR, the boot sector, and the boot files. Therefore, the earlier version the Windows operating system loses forward compatibility with Windows Vista.

RESOLUTION

To resolve these issues, follow these steps.

Note You can run the commands in the following procedure by using the command prompt. If you run these commands in Windows Vista, run them at a command prompt that has elevated user rights. To do this, click Start, click Accessories, right-click the command-prompt shortcut, and then click Run as Administrator.

1. Use Bootsect.exe to restore the Windows Vista MBR and the boot code that transfers control to the Windows Boot Manager program. To do this, type the following command at a command prompt: Drive:\boot\Bootsect.exe /NT60 AllIn this command, Drive is the drive where the Windows Vista installation media is located.Note The boot folder for this step is on the DVD drive.
2. Use Bcdedit.exe to manually create an entry in the BCD Boot.ini file for the earlier version of the Windows operating system. To do this, type the following commands at a command prompt.Note In these commands, Drive is the drive where Windows Vista is installed.

Drive:\Windows\system32\Bcdedit /create {ntldr} /d “Description for earlier Windows versionNote In this command, Description for earlier Windows version can be any text that you want. For example, Description for earlier Windows version can be “Windows XP” or “Windows Server 2003″.
Drive:\Windows\system32\Bcdedit /set {ntldr} device partition=x:Note In this command, x: is the drive letter for the active partition.
Drive:\Windows\system32\Bcdedit /set {ntldr} path \ntldr
Drive:\Windows\system32\Bcdedit /displayorder {ntldr} /addlast
3. Restart the computer.

Windows Vista Management Features

Vista features are:

Windows Vista offers many new and improved management and troubleshooting features designed to minimize IT departments’ support and maintenance costs. This document describes the most important manageability improvements and their benefits.

Overview

Windows Vista represents a significant step in Microsoft’s commitment to reducing Windows computers’ total cost of ownership (TCO). Windows Vista is designed to reduce the cost of desktop support, to simplify desktop configuration management, to enable better centralized management of the desktop, and to decrease the cost of keeping systems updated.

Windows Vista helps lower desktop support costs through several key innovations. Administrators can automate many common management tasks, reducing maintenance requirements. Windows Vista also helps reduce time required to resolve support issues, improving user productivity.

Windows Vista gives administrators more control over their environments and provides tools to simplify common administrative tasks. First, Windows Vista offers a greater number of configuration settings, and more of these settings are centrally configurable using Microsoft Active Directory Group Policy settings. The new Event Logging Infrastructure and other instrumentation in Windows Vista are enhanced to provide greater visibility and control over the desktop environment. Windows Vista also includes newly redesigned tools, such as the Task Scheduler, Event Viewer and Performance Monitor. Even the Microsoft Management Console (MMC) has been enhanced to make management applications more flexible and easier to use. These improvements make it easier for IT professionals to achieve and maintain a standardized client platform.

Windows Vista makes substantial improvements in update management. In Windows Vista, update management will be less disruptive to end users.

Reducing Desktop Support Costs

Reducing the cost of servicing the desktop is a Windows Vista guiding principle. Many Windows Vista features support this goal, either directly or indirectly.

The first step in reducing support costs is to reduce the number of support incidents. Windows Vista includes built-in diagnostics that can automatically detect and diagnose common support problems and then help users resolve the problems themselves. Problems that Windows Vista diagnostics address include failing disks, degraded performance, lack of network connectivity, and failure to shut down properly.

IT departments can add custom content to User Assistance—Windows Vista’s version of help files—to provide answers to questions about custom applications and internal network resources. User Assistance can also be customized to link users directly to an internal support center.

Remote Assistance, originally included with Microsoft Windows XP, enables support center personnel to resolve problems more quickly by viewing and controlling a remote computer’s desktop across the network. Windows Vista offers several significant improvements to make Remote Assistance even more efficient. Windows Vista Remote Assistance is faster, uses less bandwidth, and can function through Network Address Translation (NAT) firewalls.

Performance problems are some of the most complex and time-consuming challenges to troubleshoot. To reduce the time spent on these types of issues, Windows Vista provides new performance counters and an improved Performance console that offers more detailed information. These tools give support personnel detailed insight into Windows Vista’s inner workings, information they can use to isolate the type of complex, persistent problems that might otherwise remain unresolved for months or years.

Improvements to the Windows event logging infrastructure make the Windows Vista desktop easier to manage and monitor and provide better information for troubleshooting. Strict standards ensure that events are meaningful, actionable, and well-documented. Many components that stored logging information in text files in previous versions of Windows now add events to the event log. With event forwarding, administrators can centrally manage events from computers anywhere on the network, making it easier to proactively identify problems and to correlate problems that affect multiple computers. Finally, the Event Viewer has been completely rewritten to allow users to create custom views, to easily associate events with tasks, and to remotely view logs from other computers. This input makes it much more practical for administrators to use the event log to troubleshoot users’ problems.

Overview

Windows Vista represents a significant step in Microsoft’s commitment to reducing Windows computers’ total cost of ownership (TCO). Windows Vista is designed to reduce the cost of desktop support, to simplify desktop configuration management, to enable better centralized management of the desktop, and to decrease the cost of keeping systems updated.

Windows Vista helps lower desktop support costs through several key innovations. Administrators can automate many common management tasks, reducing maintenance requirements. Windows Vista also helps reduce time required to resolve support issues, improving user productivity.

Windows Vista gives administrators more control over their environments and provides tools to simplify common administrative tasks. First, Windows Vista offers a greater number of configuration settings, and more of these settings are centrally configurable using Microsoft Active Directory Group Policy settings. The new Event Logging Infrastructure and other instrumentation in Windows Vista are enhanced to provide greater visibility and control over the desktop environment. Windows Vista also includes newly redesigned tools, such as the Task Scheduler, Event Viewer and Performance Monitor. Even the Microsoft Management Console (MMC) has been enhanced to make management applications more flexible and easier to use. These improvements make it easier for IT professionals to achieve and maintain a standardized client platform.

Windows Vista makes substantial improvements in update management. In Windows Vista, update management will be less disruptive to end users.

Increasing Automation

Windows Vista greatly increases the administrator’s ability to automate tasks, reducing the time needed to manage the desktop and decreasing the likelihood of manual errors.

Task Scheduler is much more powerful in Windows Vista than in earlier versions of Windows. Task Scheduler can still be used to launch tasks at specific times or when the computer starts up, and it is entirely backward-compatible with Windows XP. However, with the new Windows Vista Task Scheduler, IT professionals can also schedule tasks to launch when:

  • A specific event occurs, such as insufficient disk space. Administrators can use Task Scheduler to notify the support center of problems or even automatically resolve common issues.
  • A user locks or unlocks their workstation. Administrators can use Task Scheduler to launch a script or application whenever a user returns to their desk.
  • The computer is idle. Administrators can use this feature to run maintenance tasks such as defragmenting the disk or backing up the computer when it is not in use.

Additionally, tasks can be run in sequence, enabling administrators to schedule multiple tasks with the confidence that the tasks will not run simultaneously. To improve security and reduce maintenance related to password expirations, credentials for the accounts used to run a task can be stored in the Active Directory domain, rather than on the local computer where they are more vulnerable to attack.

Windows Remote Management (WinRM) also makes Windows Vista easier to manage remotely. WinRM is Microsoft’s implementation of the WS-Management standard, an industry-standard Web services protocol for protected remote management of hardware and software components, WinRM—along with the proper software tools—allows administrators to remotely run scripts and perform other management tasks. Communications can be both encrypted and authenticated, limiting security risks.

Microsoft Management Console (MMC) is a framework for administrative tools that is used by Microsoft Windows 2000, Windows Server 2003, Windows XP, and Windows Vista. Windows Vista includes several improvements to MMC that make administrative tools easier to use. First, Windows Vista allows administrators to run multiple tasks in parallel, keeping administrative tools responsive even after launching a complex or slow management task. Instead of requiring administrators to right-click objects, a separate action pane shows them exactly what they can do with any particular object. MMC makes life easier for developers, too, meaning that more non-Microsoft applications are likely to utilize the MMC framework.

Reducing Update Management Costs

Although it is important to keep current with the latest software updates, update management can be costly, time-consuming, and disruptive to IT Professionals and end users. Windows Vista includes platform technology that can be used to prevent reboots or reduce the impact of reboots, in cases where they cannot be avoided. This new technology is used by the Windows Installer, so adding or removing applications with the Windows Add/Remove programs feature will be less likely to require a reboot.

While new applications are installed, applications currently in use may be automatically restarted. To reduce the disruption caused by the installation, some applications, including key Microsoft Office 2007 applications and Internet Explorer, can automatically restore their state after installation. And in cases where reboots cannot be avoided, the same technology may be used to restore the application’s state after the reboot.

Windows Server Update Services (WSUS), a new version of Software Update Services (SUS), also helps improve update management. Administrators can use WSUS to more easily review the new updates that are available and assess whether these updates are needed in their environments. For environments that use Automatic Updates, administrators can use WSUS to deploy all updates. In previous versions of Windows, only critical updates could be deployed using the Automatic Updates feature.

The Windows Update Agent (WUA) is now a stand-alone application that can download updates either directly from Microsoft or from an internal WSUS server. Because the WUA provides a single interface to updates downloaded either from Microsoft or from an internal enterprise server, users do not have to learn how to use two separate tools.