Hi have recently started getting the following error message when setting up new accounts with Outlook 2007:
The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action.
Outlook then prompts me to enter the username and password, i do so and get message again. This happens on Windows XP Professional and Vista, i cannot setup any accounts for new machines.
Points to note are that OWA works fine, and previous users who are already setup work fine also. It seems to be limited to setting up new Outlook 2007 accounts.
It can find the username fine. It comes up with green ticks underr the Online Search for your server settings
Quick update i removed Exchange from the mail001 box. I then rebooted the DC, and then rebooted mail box. Then it started working again.
This is great in that it works, however i am a bit concerned about migrating my 2003 server box mail server to Windows Server 2008 in case i get the same problems again.
Indeed not sure if its 100% fixed i hope it doesnt come back. Any ideas as to why it would have stopped working?
what made the most impact, as i was intermittently getting the domain controller could not be found, was to update the system bios and all hardware updates and drivers for the server itself (not microsoft stuff, manufacturer stuff) which made a big difference. so go to your hardware manufacturer and get the updates.
One solution I found...don't know if this will work for you.
On the local box, I removed the MS Office update: KB972363 and then I was able to connect to the account to my Exchange Server.
Here's the description of this KB from microsoft: http://support.microsoft.com/default.aspx/kb/972363?p=1
at the bottom are "known issues".
Connection to Microsoft Exchange Server is not available...Outlook must be online or connected to compete this activ
Explain your issue in full detail here:
Can not send or receive any email due to the above error popping up as soon as I log on to Outllok...using Vista as software and Outllook 2003 and have Webroot antivirus
Please Also Include:
Operating system (e.g. WinXP):
Program and version you use to access Gmail (e.g. Internet Explorer 7 or Outlook 2003):
Your antivirus software (e.g. Norton 2007):
Any extensions, toolbars or plug-ins
You haven't provided enough info. I have to assume that you're talking about trying to send mail with your Gmail account. Are you using Outlook to manage your Gmail? If so, which version? If I had to guess, you're doing this at work but your Exchange server has crapped out temporarily. If so, it probably hijacked Outlook, which will continue polling the Exchange server till it comes out of its coma. I recommend using gmail.com with your favorite browser till then
Tuesday, February 1, 2011
How to configure Outlook to a specific global catalog server or to the closest global catalog server
In some situations, you may notice excessive network traffic when Microsoft Outlook attempts to contact the global catalog server.
This article describes how to configure Outlook to a specific global catalog server or to the closest global catalog server.
Note If the global catalog server and the Exchange Server computer are in the same site as the Outlook client, you do not need to make this registry setting. The normal referral mechanism provides the best performance.
This behavior occurs when the Exchange Server computer (where the Outlook client is homed) and the global catalog server are both located in a site that is remote from the Outlook client location.
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 (http://support.microsoft.com/kb/322756/ ) How to back up and restore the registry in Windows
How to set the closest global catalog server
To have us set the closest global catalog server for you, go to the "Fix it for me" section. To set the closest global catalog server yourself, go to the "Let me fix it myself" section.
Fix it for me
To set the closest global catalog server automatically, click the Fix it button or link. Click Run in the File Download dialog box, and then follow the steps in the Fix it wizard.
Note this wizard may be in English only; however, the automatic fix also works for other language versions of Windows.
Note if you are not on the computer that has the problem, save the Fix it solution to a flash drive or a CD and then run it on the computer that has the problem.
Let me fix it myself
Use the following steps to force Outlook to identify and use the closest global catalog server yourself.
Click Start, and then click Run.
In the Open box, type regedit.exe, and then click OK.
Locate and then click the following key in the registry:
HKEY_CURRENT_USER\Software\Microsoft\Exchange\Exchange Provider
Note You may have to create the registry path.
On the Edit menu, click Add Value, and then add the following registry value:
Value name: Closest GC
Data type: REG_DWORD
Radix: Hexadecimal
Value data: 0x00000001
Quit Registry Editor.
How to set a specific global catalog server
In other topologies, you may want to force Outlook to communicate with a specific global catalog server, not necessarily the global catalog server that is closest to the Outlook client.
Note although you can manually change the registry parameter in the MAPI profile, it is overwritten the next time that you start Outlook.
To force Outlook to use a pre-defined global catalog server, use the following steps to set the following special registry parameter to point to the Fully Qualified Domain Name (FQDN). Doing this over-rides any setting in the MAPI profile.
Click Start, and then click Run.
In the Open box, type regedit.exe, and then click OK.
Locate and then click the following key in the registry:
HKEY_CURRENT_USER\Software\Microsoft\Exchange\Exchange Provider
Note You may have to create the registry path.
On the Edit menu, click Add Value, and then add the following registry value:
Value name: DS Server
Data type: REG_SZ (string)
Value data: FQDN of the global catalog server
Quit Registry Editor. If Outlook stops responding after you set the closest global catalog server or set a specific global catalog server, Outlook returns to the DSProxy process on the Exchange 2000 server and requests a new referral. The following are two possible limitations if you configure Outlook to a specific global catalog server:
The client-detected global catalog server may be out of date or semi-functional. If the global catalog server is having problems but still responds to Named Service Provider Interface (NSPI) requests, Outlook may not stop responding, and Outlook may return to the DSProxy for a new referral.
In multidomain environments, the global catalog server that you select may not be in the same domain as group objects in the Active Directory directory service. Therefore, users cannot update group membership because the local global catalog server has a read-only copy of the group.
This behavior can also affect how you add delegate permissions to a third party's account.
This behavior was recently changed so that you receive an error message when the "Send on Behalf Of" permission is not written. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
This article describes how to configure Outlook to a specific global catalog server or to the closest global catalog server.
Note If the global catalog server and the Exchange Server computer are in the same site as the Outlook client, you do not need to make this registry setting. The normal referral mechanism provides the best performance.
This behavior occurs when the Exchange Server computer (where the Outlook client is homed) and the global catalog server are both located in a site that is remote from the Outlook client location.
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 (http://support.microsoft.com/kb/322756/ ) How to back up and restore the registry in Windows
How to set the closest global catalog server
To have us set the closest global catalog server for you, go to the "Fix it for me" section. To set the closest global catalog server yourself, go to the "Let me fix it myself" section.
Fix it for me
To set the closest global catalog server automatically, click the Fix it button or link. Click Run in the File Download dialog box, and then follow the steps in the Fix it wizard.
Note this wizard may be in English only; however, the automatic fix also works for other language versions of Windows.
Note if you are not on the computer that has the problem, save the Fix it solution to a flash drive or a CD and then run it on the computer that has the problem.
Let me fix it myself
Use the following steps to force Outlook to identify and use the closest global catalog server yourself.
Click Start, and then click Run.
In the Open box, type regedit.exe, and then click OK.
Locate and then click the following key in the registry:
HKEY_CURRENT_USER\Software\Microsoft\Exchange\Exchange Provider
Note You may have to create the registry path.
On the Edit menu, click Add Value, and then add the following registry value:
Value name: Closest GC
Data type: REG_DWORD
Radix: Hexadecimal
Value data: 0x00000001
Quit Registry Editor.
How to set a specific global catalog server
In other topologies, you may want to force Outlook to communicate with a specific global catalog server, not necessarily the global catalog server that is closest to the Outlook client.
Note although you can manually change the registry parameter in the MAPI profile, it is overwritten the next time that you start Outlook.
To force Outlook to use a pre-defined global catalog server, use the following steps to set the following special registry parameter to point to the Fully Qualified Domain Name (FQDN). Doing this over-rides any setting in the MAPI profile.
Click Start, and then click Run.
In the Open box, type regedit.exe, and then click OK.
Locate and then click the following key in the registry:
HKEY_CURRENT_USER\Software\Microsoft\Exchange\Exchange Provider
Note You may have to create the registry path.
On the Edit menu, click Add Value, and then add the following registry value:
Value name: DS Server
Data type: REG_SZ (string)
Value data: FQDN of the global catalog server
Quit Registry Editor. If Outlook stops responding after you set the closest global catalog server or set a specific global catalog server, Outlook returns to the DSProxy process on the Exchange 2000 server and requests a new referral. The following are two possible limitations if you configure Outlook to a specific global catalog server:
The client-detected global catalog server may be out of date or semi-functional. If the global catalog server is having problems but still responds to Named Service Provider Interface (NSPI) requests, Outlook may not stop responding, and Outlook may return to the DSProxy for a new referral.
In multidomain environments, the global catalog server that you select may not be in the same domain as group objects in the Active Directory directory service. Therefore, users cannot update group membership because the local global catalog server has a read-only copy of the group.
This behavior can also affect how you add delegate permissions to a third party's account.
This behavior was recently changed so that you receive an error message when the "Send on Behalf Of" permission is not written. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
Wednesday, January 5, 2011
Ten ways to troubleshoot a slow PC
Over time, users begin to notice that their system is slow or that it hangs. While the possibilities for system slowdown are endless, we identify 10 common troubleshooting areas to examine before you suggest to management that it's time for an upgrade.
User complaints are minimal when new PCs are rolled out. They start up quick, and programs seem to open in a snap. But over time, users begin to notice that their system is slow or that it hangs up often. While the possibilities for system slowdown are endless, I have identified 10 common troubleshooting areas you should examine first before you suggest to management that it's time for an upgrade.
1. Processor overheating -- Modern processors generate a lot of heat. That's why all processors require some sort of cooling element, typically a fan of some type. When the processor temperature goes over spec, the system can slow down or run erratically. The processor fan may fail for several reasons:
Dust is preventing the fan from spinning smoothly.
The fan motor has failed.
The fan bearings are loose and "jiggling".
Often you can tell if there is a fan problem by listening and/or touching the computer. A fan that has loose bearings starts jiggling and vibrates the case, making a characteristic noise. You may barely notice the noise at first, and it's common for even the experienced computer pro to overlook this change. But as time goes by, the sounds and vibrations will become so prominent that you'll change the fan out just to stop the racket!
You don't always need to replace the fan. If it is covered with dust, you can often spray away the dust with compressed air. Note that even though you might get the fan running again, its life span has likely been reduced because of the overwork. You should keep an extra fan in reserve in case of failure.
There are a number of utilities that will track the temperature of your processor and case.
2. Bad RAM -- Several situations can lead to a bad RAM relationship with a particular machine:
RAM timing is slower than optimal machine spec.
RAM has minor flaws that only appear on detailed testing.
RAM is overheating.
In the "old days" of Fast Page RAM, buying new RAM for your computer was a pretty simple affair. You just needed to know what speed your motherboard supported and the maximum each slot would take. Today, there are many different speeds of RAM, and the better motherboards may be tolerant of using RAM that does not match the motherboard's maximum specs. For example, your motherboard may support PC133 RAM but will still work with PC100 RAM. But be aware that you may see performance decreases if you install RAM that is slower than the maximum spec.
Minor flaws in RAM chips can lead to system slowdowns and instability. The least expensive chips often have minor flaws that will cause your system to slow down or Blue Screen intermittently. Although built-in mechanisms may allow the system to keep working, there is a performance hit when it has to deal with flawed RAM chips.
In the past, no one worried about RAM chips getting hot, because they didn't seem to generate much heat. But that's changed with newer RAM types, especially SDRAM. To check for overheating, open your computer's case, power down, and pull the plug out. Ground yourself and touch the plastic on one of your RAM chips. Ouch! They get pretty hot. If you find that your RAM chips are overheating, you should consider buying a separate fan to cool your memory. If your motherboard doesn't support a RAM fan, you might be able to get enough additional cooling by installing a fan card that plugs in to a PCI slot.
Tip: Some motherboards will even allow you to mix speeds but will default to the slowest RAM installed.
3. Failing hard disk -- There are many signs of imminent failure before a hard disk finally gives up. Some of these signs include:
Slow access times on the affected drive.
An increasing number of bad sectors when running scandisk and chkdsk.
Unexplained Blue Screens.
Intermittent boot failures.
Detecting a failing hard disk can be tricky because the early signs are subtle. Experienced computer professionals can often hear a change in the normal disk spin. After the disk deteriorates further, you'll see the system crawl to a standstill. Write processes will take a long time as the system tries to find good blocks to write to. (This will occur if you're using a robust file system such as NTFS; other file systems will likely Blue Screen the computer.)
When you notice the system slow down, run scandisk or chkdsk, depending on your operating system. If you notice a bad sector where a good sector existed earlier, that's a clue that the disk is going bad. Back up the data on the disk and prepare for it to fail soon. Make sure you have a spare disk ready so you can replace it when it fails, or replace the disk as soon as you notice the early signs of failure.
Disk noise and scandisk/chkdsk are your best indicators for identifying a failing drive that's leading to a system slowdown. However, if you are managing a system remotely, or you can't take the system down for a full chkdsk/R, you can use tools that monitor disk health, such as Executive Software's DiskAlert.
4. BIOS settings -- One often-ignored culprit of system slowdown is the machine's BIOS settings. Most people accept the BIOS settings as they were configured in the factory and leave them as is. However, slowdowns may occur if the BIOS settings do not match the optimal machine configuration. Often you can improve machine performance by researching your motherboard's optimal BIOS settings -- which may not be the same as the factory defaults.
There is no centralised database of optimal BIOS settings, but a simple Web search on your motherboard name and BIOS as keywords should yield the correct settings.
5. Disk type/controller compatibility -- You've just purchased a new UDMA-66 disk drive, and it doesn't seem any faster than any of the other drives in your machine. You do some benchmark testing, and the new disk tests the same as the other drives in your system. So what's the problem?
It could be that your motherboard doesn't support the UDMA 66 specification. Check your manual to determine what type of IDE interface it supports. If the motherboard only supports UDMA 33, then your UDMA 66 throttles down for backwards compatibility. You can get around this problem by installing a PCI UDMA 66 add-on card and plugging the new drive in to that interface.
Another potential problem may be the cable type you are using. UDMA 66+ drives require a different cable than older drive types. The drive may not work at all with the old cable type. Aged cables will break down over time, especially if they are tightly folded and the temperature of the case remains consistently high. It's always worthwhile to change out the drive cable to see if performance improves.
6. Windows services -- Many Windows services are enabled by default. Many of these services, however, are not required for your machine to run properly. You should review the services running on your Windows 2000/Windows XP computer and disable those that you don't need.
One way to see what services are running is to use the Services applet found in the Administrative Tools menu. Rightclick My Computer and select Manage. Important information contained in the Services console includes the service Name, Status, and Startup Type. You can get more details on a service by double-clicking on it to bring up the service's Properties.
You can stop the service by clicking the Stop button. If you are sure that you don't need the service, click the down arrow in the Startup Type drop-down list box and set the service to Disabled. If you are not sure if you need the service, change the Startup Type to Manual. Then you'll have the option of manually starting the service if you find that you need it.
Another way of controlling which services start is using the msconfig utility. Open the Run dialog box and type msconfig in the Open text box. The Essential column shows services Microsoft considers essential to running the computer. However, note that many required services are not defined as essential in the System Configuration Utility window. You can prevent a service from starting at bootup by unchecking the check box to the left of the service.
One service that is well known for slowing down Windows 2000/Windows XP systems is the Indexing Service. This service indexes the content of each hard disk and makes it easier for the Search utility to find files. Unless you are running a Web site that uses the indexing service, you may want to disable it to improve performance.
7. Runaway processes -- Runaway processes take up all of the processors' cycles. The usual suspects are badly written device drivers, and legacy software installed on a newer operating system. You can identify a runaway process by looking at the process list in the Windows Task Manager. Any process that takes almost 100 percent of the processing time is likely a runaway process.
There are exceptions to this rule. On a smoothly running system, the System Idle Process should be consuming the majority of the processor cycles most of the time. If any other process were to take up 98 percent of the processor cycles, you might have a runaway process.
If you do find a runaway process, you can right-click the process and click the End Process command. You may need to stop some processes, such as runaway system services, from the Services console. If you can't stop the service using the console, you may need to reboot the system. Sometimes a hard reboot is required.
8. Disk fragmentation -- As files are added, deleted, and changed on a disk, the contents of the file can become spread across sectors located in disparate regions of the disk. This is file fragmentation. Some operating systems, such as Windows NT, don't have a built-in defrag utility; you must obtain a third-party solution, such as Executive Software's Diskeeper.
Disk fragmentation can significantly slow down your machine. The disk heads must move back and forth while seeking all the fragments of a file. A common cause of disk fragmentation is a disk that is too full. You should keep 20 percent to 25 percent of your hard disk space free to minimise file fragmentation and to improve the defragmenter's ability to defrag the disk. Thus, if a disk is too full, move some files off the drive and restart the defragmenter.
9. Background applications -- Have you ever visited an end-user's desktop and noticed a dozen icons in the system tray? Each icon represents a process running in either the foreground or background. Most of them are running in the background, so the users may not be aware that they are running 20+ applications at the same time.
This is due to applications starting up automatically in the background. Look first for such programs in the Startup folder in the Start menu. Many applications place components in the Startup folder to run in the background. Some of these, such as the Microsoft Office Findfast, can really chew up processor and disk time and noticeably slow down a system. Review each of the entries in the Startup folder and delete any that are unnecessary.
10. File system issues -- Some file systems work better than others for large disk partitions. If the machine runs Windows NT 4.0, Windows 2000, or Windows XP, you should use the NTFS file system for best performance.
File system performance is closely related to cluster size and the number of clusters on the disk. NTFS file systems will bog down if you have a 60-GB hard disk configured with a cluster size of 512 bytes. This creates an enormous number of clusters, which the file system must track and seek. This becomes especially problematic when the drive is highly fragmented. One solution is to use larger cluster sizes. If you set the cluster size to 4K or larger, you will see noticeable improvement in file load times. Please note, however, that large clusters can significantly increase the amount of cluster slack space and lead to a lot of wasted disk space.
Another trick to alleviate file system issues involves tweaking some Registry values (Start Menu|Run|Regedit):
The first Registry value you can tweak is NtfsDisable8dot3NameCreation, which can be found at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Filesystem. When you set this value to 1, it stops NTFS from generating the 8.3 file-naming convention used for backward compatibility. If you do not need these old filenames, you can improve performance by preventing NTFS from creating them.
Another useful NTFS entry is the NtfsDisableLastAccess value, which can be found at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Filesystem. This is a REG_DWORD entry, and when it is set to 1, it will prevent NTFS from updating the date and time stamp of directories after they are browsed. However, this does not prevent an update to the file-access information when a file is opened or changed.
If you are not using the NTFS file system, you may be able to improve performance by moving files and folders out of the root directory. With FAT partitions, you may notice a big slowdown in system performance after running scandisk because a large number of .chk files are placed in the root directory. Users sometimes fill their root directories by making it the default file storage location. Move as many files and folders as possible out of the root directory, and performance should improve significantly.
Debra Littlejohn Shinder is a technology consultant, trainer and writer who has authored books on computer operating systems, networking, and security. She currently specialises in security issues and Microsoft products. Debra has been an MCSE since 1998 and has been awarded Microsoft's Most Valuable Professional (MVP) status in Windows Server Security. A former police officer and police academy instructor, she teaches computer networking and security and criminal justice courses at Eastfield College in Texas.
TechRepublic is the online community and information resource for all IT professionals, from support staff to executives. We offer in-depth technical articles written for IT professionals by IT professionals. In addition to articles on everything from Windows to e-mail to firewalls, we offer IT industry analysis, downloads, management tips, discussion forums, and e-newsletters.
User complaints are minimal when new PCs are rolled out. They start up quick, and programs seem to open in a snap. But over time, users begin to notice that their system is slow or that it hangs up often. While the possibilities for system slowdown are endless, I have identified 10 common troubleshooting areas you should examine first before you suggest to management that it's time for an upgrade.
1. Processor overheating -- Modern processors generate a lot of heat. That's why all processors require some sort of cooling element, typically a fan of some type. When the processor temperature goes over spec, the system can slow down or run erratically. The processor fan may fail for several reasons:
Dust is preventing the fan from spinning smoothly.
The fan motor has failed.
The fan bearings are loose and "jiggling".
Often you can tell if there is a fan problem by listening and/or touching the computer. A fan that has loose bearings starts jiggling and vibrates the case, making a characteristic noise. You may barely notice the noise at first, and it's common for even the experienced computer pro to overlook this change. But as time goes by, the sounds and vibrations will become so prominent that you'll change the fan out just to stop the racket!
You don't always need to replace the fan. If it is covered with dust, you can often spray away the dust with compressed air. Note that even though you might get the fan running again, its life span has likely been reduced because of the overwork. You should keep an extra fan in reserve in case of failure.
There are a number of utilities that will track the temperature of your processor and case.
2. Bad RAM -- Several situations can lead to a bad RAM relationship with a particular machine:
RAM timing is slower than optimal machine spec.
RAM has minor flaws that only appear on detailed testing.
RAM is overheating.
In the "old days" of Fast Page RAM, buying new RAM for your computer was a pretty simple affair. You just needed to know what speed your motherboard supported and the maximum each slot would take. Today, there are many different speeds of RAM, and the better motherboards may be tolerant of using RAM that does not match the motherboard's maximum specs. For example, your motherboard may support PC133 RAM but will still work with PC100 RAM. But be aware that you may see performance decreases if you install RAM that is slower than the maximum spec.
Minor flaws in RAM chips can lead to system slowdowns and instability. The least expensive chips often have minor flaws that will cause your system to slow down or Blue Screen intermittently. Although built-in mechanisms may allow the system to keep working, there is a performance hit when it has to deal with flawed RAM chips.
In the past, no one worried about RAM chips getting hot, because they didn't seem to generate much heat. But that's changed with newer RAM types, especially SDRAM. To check for overheating, open your computer's case, power down, and pull the plug out. Ground yourself and touch the plastic on one of your RAM chips. Ouch! They get pretty hot. If you find that your RAM chips are overheating, you should consider buying a separate fan to cool your memory. If your motherboard doesn't support a RAM fan, you might be able to get enough additional cooling by installing a fan card that plugs in to a PCI slot.
Tip: Some motherboards will even allow you to mix speeds but will default to the slowest RAM installed.
3. Failing hard disk -- There are many signs of imminent failure before a hard disk finally gives up. Some of these signs include:
Slow access times on the affected drive.
An increasing number of bad sectors when running scandisk and chkdsk.
Unexplained Blue Screens.
Intermittent boot failures.
Detecting a failing hard disk can be tricky because the early signs are subtle. Experienced computer professionals can often hear a change in the normal disk spin. After the disk deteriorates further, you'll see the system crawl to a standstill. Write processes will take a long time as the system tries to find good blocks to write to. (This will occur if you're using a robust file system such as NTFS; other file systems will likely Blue Screen the computer.)
When you notice the system slow down, run scandisk or chkdsk, depending on your operating system. If you notice a bad sector where a good sector existed earlier, that's a clue that the disk is going bad. Back up the data on the disk and prepare for it to fail soon. Make sure you have a spare disk ready so you can replace it when it fails, or replace the disk as soon as you notice the early signs of failure.
Disk noise and scandisk/chkdsk are your best indicators for identifying a failing drive that's leading to a system slowdown. However, if you are managing a system remotely, or you can't take the system down for a full chkdsk/R, you can use tools that monitor disk health, such as Executive Software's DiskAlert.
4. BIOS settings -- One often-ignored culprit of system slowdown is the machine's BIOS settings. Most people accept the BIOS settings as they were configured in the factory and leave them as is. However, slowdowns may occur if the BIOS settings do not match the optimal machine configuration. Often you can improve machine performance by researching your motherboard's optimal BIOS settings -- which may not be the same as the factory defaults.
There is no centralised database of optimal BIOS settings, but a simple Web search on your motherboard name and BIOS as keywords should yield the correct settings.
5. Disk type/controller compatibility -- You've just purchased a new UDMA-66 disk drive, and it doesn't seem any faster than any of the other drives in your machine. You do some benchmark testing, and the new disk tests the same as the other drives in your system. So what's the problem?
It could be that your motherboard doesn't support the UDMA 66 specification. Check your manual to determine what type of IDE interface it supports. If the motherboard only supports UDMA 33, then your UDMA 66 throttles down for backwards compatibility. You can get around this problem by installing a PCI UDMA 66 add-on card and plugging the new drive in to that interface.
Another potential problem may be the cable type you are using. UDMA 66+ drives require a different cable than older drive types. The drive may not work at all with the old cable type. Aged cables will break down over time, especially if they are tightly folded and the temperature of the case remains consistently high. It's always worthwhile to change out the drive cable to see if performance improves.
6. Windows services -- Many Windows services are enabled by default. Many of these services, however, are not required for your machine to run properly. You should review the services running on your Windows 2000/Windows XP computer and disable those that you don't need.
One way to see what services are running is to use the Services applet found in the Administrative Tools menu. Rightclick My Computer and select Manage. Important information contained in the Services console includes the service Name, Status, and Startup Type. You can get more details on a service by double-clicking on it to bring up the service's Properties.
You can stop the service by clicking the Stop button. If you are sure that you don't need the service, click the down arrow in the Startup Type drop-down list box and set the service to Disabled. If you are not sure if you need the service, change the Startup Type to Manual. Then you'll have the option of manually starting the service if you find that you need it.
Another way of controlling which services start is using the msconfig utility. Open the Run dialog box and type msconfig in the Open text box. The Essential column shows services Microsoft considers essential to running the computer. However, note that many required services are not defined as essential in the System Configuration Utility window. You can prevent a service from starting at bootup by unchecking the check box to the left of the service.
One service that is well known for slowing down Windows 2000/Windows XP systems is the Indexing Service. This service indexes the content of each hard disk and makes it easier for the Search utility to find files. Unless you are running a Web site that uses the indexing service, you may want to disable it to improve performance.
7. Runaway processes -- Runaway processes take up all of the processors' cycles. The usual suspects are badly written device drivers, and legacy software installed on a newer operating system. You can identify a runaway process by looking at the process list in the Windows Task Manager. Any process that takes almost 100 percent of the processing time is likely a runaway process.
There are exceptions to this rule. On a smoothly running system, the System Idle Process should be consuming the majority of the processor cycles most of the time. If any other process were to take up 98 percent of the processor cycles, you might have a runaway process.
If you do find a runaway process, you can right-click the process and click the End Process command. You may need to stop some processes, such as runaway system services, from the Services console. If you can't stop the service using the console, you may need to reboot the system. Sometimes a hard reboot is required.
8. Disk fragmentation -- As files are added, deleted, and changed on a disk, the contents of the file can become spread across sectors located in disparate regions of the disk. This is file fragmentation. Some operating systems, such as Windows NT, don't have a built-in defrag utility; you must obtain a third-party solution, such as Executive Software's Diskeeper.
Disk fragmentation can significantly slow down your machine. The disk heads must move back and forth while seeking all the fragments of a file. A common cause of disk fragmentation is a disk that is too full. You should keep 20 percent to 25 percent of your hard disk space free to minimise file fragmentation and to improve the defragmenter's ability to defrag the disk. Thus, if a disk is too full, move some files off the drive and restart the defragmenter.
9. Background applications -- Have you ever visited an end-user's desktop and noticed a dozen icons in the system tray? Each icon represents a process running in either the foreground or background. Most of them are running in the background, so the users may not be aware that they are running 20+ applications at the same time.
This is due to applications starting up automatically in the background. Look first for such programs in the Startup folder in the Start menu. Many applications place components in the Startup folder to run in the background. Some of these, such as the Microsoft Office Findfast, can really chew up processor and disk time and noticeably slow down a system. Review each of the entries in the Startup folder and delete any that are unnecessary.
10. File system issues -- Some file systems work better than others for large disk partitions. If the machine runs Windows NT 4.0, Windows 2000, or Windows XP, you should use the NTFS file system for best performance.
File system performance is closely related to cluster size and the number of clusters on the disk. NTFS file systems will bog down if you have a 60-GB hard disk configured with a cluster size of 512 bytes. This creates an enormous number of clusters, which the file system must track and seek. This becomes especially problematic when the drive is highly fragmented. One solution is to use larger cluster sizes. If you set the cluster size to 4K or larger, you will see noticeable improvement in file load times. Please note, however, that large clusters can significantly increase the amount of cluster slack space and lead to a lot of wasted disk space.
Another trick to alleviate file system issues involves tweaking some Registry values (Start Menu|Run|Regedit):
The first Registry value you can tweak is NtfsDisable8dot3NameCreation, which can be found at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Filesystem. When you set this value to 1, it stops NTFS from generating the 8.3 file-naming convention used for backward compatibility. If you do not need these old filenames, you can improve performance by preventing NTFS from creating them.
Another useful NTFS entry is the NtfsDisableLastAccess value, which can be found at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Filesystem. This is a REG_DWORD entry, and when it is set to 1, it will prevent NTFS from updating the date and time stamp of directories after they are browsed. However, this does not prevent an update to the file-access information when a file is opened or changed.
If you are not using the NTFS file system, you may be able to improve performance by moving files and folders out of the root directory. With FAT partitions, you may notice a big slowdown in system performance after running scandisk because a large number of .chk files are placed in the root directory. Users sometimes fill their root directories by making it the default file storage location. Move as many files and folders as possible out of the root directory, and performance should improve significantly.
Debra Littlejohn Shinder is a technology consultant, trainer and writer who has authored books on computer operating systems, networking, and security. She currently specialises in security issues and Microsoft products. Debra has been an MCSE since 1998 and has been awarded Microsoft's Most Valuable Professional (MVP) status in Windows Server Security. A former police officer and police academy instructor, she teaches computer networking and security and criminal justice courses at Eastfield College in Texas.
TechRepublic is the online community and information resource for all IT professionals, from support staff to executives. We offer in-depth technical articles written for IT professionals by IT professionals. In addition to articles on everything from Windows to e-mail to firewalls, we offer IT industry analysis, downloads, management tips, discussion forums, and e-newsletters.
Speed up your slow PC, 10 ways to tuneup your computer
Is your PC slower than the day it was born?
A new PC is a joy because it is fast and efficient which makes it fun to use. Over time, that PC gets slower, and slower and can eventually become a chore to operate. There are steps you can take to restore some of that "new PC" performance.
Look all around this article. You will find helpful suggestions to improve your PC performance and solve problems.
Get Organized
Print these steps for a PC tuneup checklist. Make notes as you go; it'll be easier to get assistance if you need it. Reserve enough time. Review the Related Links for more details on some of these steps. Follow these steps in order, where practical. {Click sequences are shown for Windows XP Professional and are only meant to be a general guide}.
Make Some Backups
You need a fall back position in case bad things happen. Create an XP restore point. Consider saving: Email files and account settings, desktop and favorites, My Documents, other files? You've been meaning to backup anyhow, haven't you?
Add Memory
New programs are larger and tax the memory of an older PC. To effectively operate today you need at least 1 GB of RAM. When I spec a new PC I usually include 2 GB of RAM. Check your RAM size and seriously consider an upgrade; easy to do and could have a big impact. {Start -> Control Panel -> System, to see RAM installed}
Check your PC memory...
Memory upgrades made easy with free system scan
Crucial Technologies, my recommendation for memory, will scan your PC on-line. Check it out.
De-fragment your hard drive
Over time, the files on your hard drive become fragmented. The files are still there and usable, but they are scattered all over the hard drive and become inefficient for the operating system to access and move around. Think of it as a messy drawer - everything is there; it just takes longer to locate things. Windows has a tool to regroup your file pieces (defrag) and reorganize the hard drive. {My Computer -> C Drive Properties -> Tools -> De-fragment Now -> select the C drive -> De-fragment} This can take a while so it's a good task to run overnight.
Check hard drive capacity (after you do all the cleanup steps)
When you bought the PC, that hard drive seemed big enough and it probably was. In the last couple of years, data file sizes (e.g. pictures and audio/video clips) have exploded. New programs also take more space. You need a minimum of 15% free space, and should really have more (25-50%) to operate efficiently. Open "My Computer" to see the capacity and free space on your C drive.
Stop unnecessary services
Many programs install and run services for their convenience. Sometimes these services are running unnecessarily and can slow things down. Places to check for unnecessary services: System Icon Tray (lower right of Start line where time is shown), the Startup Folder {All Programs, Startup) and run MSCONFIG to see all services and programs started by the operating system for you when you start your PC (you will probably be surprised at the things that are running).
Repeat these steps periodically
Accumulated digital debris caused your PC to slow down in the first place. Don't wait so long before doing a good cleanup on your PC. It will pay off in better performance and you will get to know your PC a little better. Pick a schedule (monthly? quarterly?) that you are comfortable with.
Consider a new PC
Try these steps first and you should get back some of the missing speed and performance. It may not be enough. Consider carefully the cost of additional memory, new hard drive and service costs, versus the cost of a new PC system.
Warnings!
-Back up! You should be doing backups anyhow. This is a perfect time to catch up.
-Be sure you know what program you are dealing with before uninstalling any program. Research it if you are not completely sure.
-Be sure you know what service you are disabling in MSCONFIG before disabling any startup operation or service. Research it if you are not completely sure.
-Be sure you know what files you are dealing with before deleting any files. Research it if you are not completely sure.
-Unplug your PC from the electrical outlet before opening the PC case to add memory or clean it out. Be properly grounded. Be careful what and where you touch. Follow the manufacturer's instructions, which might involve reading the manuals.
Tips
-For Windows XP, create a restore point before making any changes to your PC.
-Use this HubPage as a guide. The steps are independent. Skip a step if you don't get it.
-Be organized - have a checklist and take notes at each step. This will give you more control over the process.
-If you need more detailed information on the steps suggested, refer to the External Links.
-Allow enough time - don't rush and you'll make fewer mistakes. Some steps can take an hour or more and will be ok to run overnight.
-Pay attention. The computer jargon and procedure steps can seem confusing
and sometimes intimidating. However, the average user can work through most
of this and get the desired result by staying focused.
Things you'll need
Time - set aside enough time. Some procedures like de-fragmenting can take quite a while. Tinkering with your system should not be rushed.
Lifeline - it's a good idea to have a PC professional on-call or within reach in case you need advice.
Manuals - the original computer manuals and any literature provided with upgrades.
Confidence - many PC users don't do these simple steps because the technology can seem intimidating. These steps are within the average persons reach. Have confidence.
Checkout these related articles on PC support, enhancement and maintenance.
Scan your hard drive
Windows has a tool to scan hard drives. This can resolve file location errors and other disk management issues. {My Computer -> C Drive Properties -> Tools -> Check Now -> check to "automatically fix..." and to "scan for...", then Start} This test requires you to restart your PC. This can take a while on a large hard drive so it's a good task to run overnight.
A new PC is a joy because it is fast and efficient which makes it fun to use. Over time, that PC gets slower, and slower and can eventually become a chore to operate. There are steps you can take to restore some of that "new PC" performance.
Look all around this article. You will find helpful suggestions to improve your PC performance and solve problems.
Get Organized
Print these steps for a PC tuneup checklist. Make notes as you go; it'll be easier to get assistance if you need it. Reserve enough time. Review the Related Links for more details on some of these steps. Follow these steps in order, where practical. {Click sequences are shown for Windows XP Professional and are only meant to be a general guide}.
Make Some Backups
You need a fall back position in case bad things happen. Create an XP restore point. Consider saving: Email files and account settings, desktop and favorites, My Documents, other files? You've been meaning to backup anyhow, haven't you?
Add Memory
New programs are larger and tax the memory of an older PC. To effectively operate today you need at least 1 GB of RAM. When I spec a new PC I usually include 2 GB of RAM. Check your RAM size and seriously consider an upgrade; easy to do and could have a big impact. {Start -> Control Panel -> System, to see RAM installed}
Check your PC memory...
Memory upgrades made easy with free system scan
Crucial Technologies, my recommendation for memory, will scan your PC on-line. Check it out.
De-fragment your hard drive
Over time, the files on your hard drive become fragmented. The files are still there and usable, but they are scattered all over the hard drive and become inefficient for the operating system to access and move around. Think of it as a messy drawer - everything is there; it just takes longer to locate things. Windows has a tool to regroup your file pieces (defrag) and reorganize the hard drive. {My Computer -> C Drive Properties -> Tools -> De-fragment Now -> select the C drive -> De-fragment} This can take a while so it's a good task to run overnight.
Check hard drive capacity (after you do all the cleanup steps)
When you bought the PC, that hard drive seemed big enough and it probably was. In the last couple of years, data file sizes (e.g. pictures and audio/video clips) have exploded. New programs also take more space. You need a minimum of 15% free space, and should really have more (25-50%) to operate efficiently. Open "My Computer" to see the capacity and free space on your C drive.
Stop unnecessary services
Many programs install and run services for their convenience. Sometimes these services are running unnecessarily and can slow things down. Places to check for unnecessary services: System Icon Tray (lower right of Start line where time is shown), the Startup Folder {All Programs, Startup) and run MSCONFIG to see all services and programs started by the operating system for you when you start your PC (you will probably be surprised at the things that are running).
Repeat these steps periodically
Accumulated digital debris caused your PC to slow down in the first place. Don't wait so long before doing a good cleanup on your PC. It will pay off in better performance and you will get to know your PC a little better. Pick a schedule (monthly? quarterly?) that you are comfortable with.
Consider a new PC
Try these steps first and you should get back some of the missing speed and performance. It may not be enough. Consider carefully the cost of additional memory, new hard drive and service costs, versus the cost of a new PC system.
Warnings!
-Back up! You should be doing backups anyhow. This is a perfect time to catch up.
-Be sure you know what program you are dealing with before uninstalling any program. Research it if you are not completely sure.
-Be sure you know what service you are disabling in MSCONFIG before disabling any startup operation or service. Research it if you are not completely sure.
-Be sure you know what files you are dealing with before deleting any files. Research it if you are not completely sure.
-Unplug your PC from the electrical outlet before opening the PC case to add memory or clean it out. Be properly grounded. Be careful what and where you touch. Follow the manufacturer's instructions, which might involve reading the manuals.
Tips
-For Windows XP, create a restore point before making any changes to your PC.
-Use this HubPage as a guide. The steps are independent. Skip a step if you don't get it.
-Be organized - have a checklist and take notes at each step. This will give you more control over the process.
-If you need more detailed information on the steps suggested, refer to the External Links.
-Allow enough time - don't rush and you'll make fewer mistakes. Some steps can take an hour or more and will be ok to run overnight.
-Pay attention. The computer jargon and procedure steps can seem confusing
and sometimes intimidating. However, the average user can work through most
of this and get the desired result by staying focused.
Things you'll need
Time - set aside enough time. Some procedures like de-fragmenting can take quite a while. Tinkering with your system should not be rushed.
Lifeline - it's a good idea to have a PC professional on-call or within reach in case you need advice.
Manuals - the original computer manuals and any literature provided with upgrades.
Confidence - many PC users don't do these simple steps because the technology can seem intimidating. These steps are within the average persons reach. Have confidence.
Checkout these related articles on PC support, enhancement and maintenance.
Scan your hard drive
Windows has a tool to scan hard drives. This can resolve file location errors and other disk management issues. {My Computer -> C Drive Properties -> Tools -> Check Now -> check to "automatically fix..." and to "scan for...", then Start} This test requires you to restart your PC. This can take a while on a large hard drive so it's a good task to run overnight.
PC is Slow
Help! My PC is slow
Can you knit a sweater or wash the car in the time it takes your PC to open a file? If your PC has suddenly started running slower than normal, there are a few tips you can use to make it run faster.
Have you done anything new?
Try removing any newly installed hardware, such as a printer, or uninstalling any newly installed applications, such as a computer game, and see if that resolves the problem. Make sure that your computer meets the minimum requirements recommended by the hardware manufacturer or software publisher before installing anything new.
Reboot your computer
Are you one of those people who leaves their computer on for days or weeks at a time? If so, temporary files will build up on your hard disk, taking up space in your computer’s memory and clogging up other resources. By rebooting, or restarting, your computer, you can clear out these temporary files and improve your PC’s performance.
Verify your system resources
People get computers for various reasons: e-mail, Internet access, games, word processing. Make sure your computer’s RAM (or memory), hard disk space, and other components are adequate for what you’re using the computer for.
Run the Windows Live OneCare safety scanner
The Windows Live OneCare safety scanner can help you increase your computer’s performance by removing temporary files, cleaning the registry, and fixing disk fragmentation. Such optimization can help your PC run more efficiently.
To remove obsolete temporary files and invalid registry items that can accumulate on your hard disk over time and slow down your PC, go to the Clean Up Center and click Clean Up Scan. Temporary files and stray registry items can be safely removed without deleting any data needed by your computer.
To fix hard disk fragmentation, which allows your PC to find all the pieces of a file faster because it only has to look in one place for them, go to the Tune Up Center and click Tune Up Scan.
If you’ve never defragmented your hard disk or cleaned out temporary files, or if it’s been awhile since you’ve last done so, run the full service scan to do it all in one fell swoop!
Scan for viruses
Malicious code (also known as malware)—such as viruses, Trojans, spyware, and worms—uses your computer’s resources to do all sorts of nasty things to it, including causing it to slow down. One of the most important aspects of the protection scanner is its ability to check your PC for malicious software.
How long the scan will take varies, and can depend on such things as your processor speed, the amount of memory your computer has, and how many issues the scanner finds. Generally, a complete scan will take anywhere from two to five minutes.
Ideally, you should run the full service scanner at least once a month, but if your computer is running slower than normal or programs don’t seem to be behaving the way they should, you might want to run the scan before then.
Try starting in safe mode
Normally, when you start your computer, Windows loads a huge amount of data into your computer’s memory. In safe mode, however, you only have access to basic files and drivers (for example, mouse, monitor, keyboard, default system services, and no network connections). Therefore, the processor is only running at a fraction of its capacity.
If your system is significantly faster in safe mode, one or more applications or drivers may be causing the slowdown in normal mode. If you’ve recently added new software or a new device, try uninstalling it or removing the hardware to see if your computer speeds up.
To start in safe mode:
1. Click Start, then click Shut Down.
2. Click Restart, then click OK.
3. As your computer restarts but before Windows launches, press F8.
On a computer that is configured for booting to multiple operating systems, you can press F8 when the boot menu appears.
4. Select Safe Mode, then press ENTER.
Can you knit a sweater or wash the car in the time it takes your PC to open a file? If your PC has suddenly started running slower than normal, there are a few tips you can use to make it run faster.
Have you done anything new?
Try removing any newly installed hardware, such as a printer, or uninstalling any newly installed applications, such as a computer game, and see if that resolves the problem. Make sure that your computer meets the minimum requirements recommended by the hardware manufacturer or software publisher before installing anything new.
Reboot your computer
Are you one of those people who leaves their computer on for days or weeks at a time? If so, temporary files will build up on your hard disk, taking up space in your computer’s memory and clogging up other resources. By rebooting, or restarting, your computer, you can clear out these temporary files and improve your PC’s performance.
Verify your system resources
People get computers for various reasons: e-mail, Internet access, games, word processing. Make sure your computer’s RAM (or memory), hard disk space, and other components are adequate for what you’re using the computer for.
Run the Windows Live OneCare safety scanner
The Windows Live OneCare safety scanner can help you increase your computer’s performance by removing temporary files, cleaning the registry, and fixing disk fragmentation. Such optimization can help your PC run more efficiently.
To remove obsolete temporary files and invalid registry items that can accumulate on your hard disk over time and slow down your PC, go to the Clean Up Center and click Clean Up Scan. Temporary files and stray registry items can be safely removed without deleting any data needed by your computer.
To fix hard disk fragmentation, which allows your PC to find all the pieces of a file faster because it only has to look in one place for them, go to the Tune Up Center and click Tune Up Scan.
If you’ve never defragmented your hard disk or cleaned out temporary files, or if it’s been awhile since you’ve last done so, run the full service scan to do it all in one fell swoop!
Scan for viruses
Malicious code (also known as malware)—such as viruses, Trojans, spyware, and worms—uses your computer’s resources to do all sorts of nasty things to it, including causing it to slow down. One of the most important aspects of the protection scanner is its ability to check your PC for malicious software.
How long the scan will take varies, and can depend on such things as your processor speed, the amount of memory your computer has, and how many issues the scanner finds. Generally, a complete scan will take anywhere from two to five minutes.
Ideally, you should run the full service scanner at least once a month, but if your computer is running slower than normal or programs don’t seem to be behaving the way they should, you might want to run the scan before then.
Try starting in safe mode
Normally, when you start your computer, Windows loads a huge amount of data into your computer’s memory. In safe mode, however, you only have access to basic files and drivers (for example, mouse, monitor, keyboard, default system services, and no network connections). Therefore, the processor is only running at a fraction of its capacity.
If your system is significantly faster in safe mode, one or more applications or drivers may be causing the slowdown in normal mode. If you’ve recently added new software or a new device, try uninstalling it or removing the hardware to see if your computer speeds up.
To start in safe mode:
1. Click Start, then click Shut Down.
2. Click Restart, then click OK.
3. As your computer restarts but before Windows launches, press F8.
On a computer that is configured for booting to multiple operating systems, you can press F8 when the boot menu appears.
4. Select Safe Mode, then press ENTER.
Sunday, December 26, 2010
Windows Vista Deployment
Introducing Microsoft Deployment Toolkit
The Windows AIK provides a collection of tools and documentation for performing unattended installs of Windows Vista, but these tools are not integrated with one another. For instance, you must use one tool (Windows SIM) to create your answer file, another tool (ImageX) to capture an image of your sysprepped reference computer, yet another tool (Package Manager) to service your images, another tool (WinPE) to boot your bare-metal destination computers, and so on. By adding Windows DS to the mix, you can centralize the management and deployment of your images, but you still have to work with a collection of disparate tools to perform your deployment.
To simplify desktop deployment, Microsoft first created Microsoft Solution Accelerator for Business Desktop Deployment (BDD), an integrated toolset together with comprehensive guidance for deploying Windows Vista and the 2007 Office System. BDD went through several versions including:
BDD 2.0 and 2.5 – Used for deploying Windows XP that was released in two editions: Standard edition for smaller midmarket customers, and Enterprise edition for larger organizations that had an Microsoft Systems Management Server 2003 infrastructure deployed.
BDD 2007 – Used for deploying Windows XP, Windows Vista, and the 2007 Office System and released in a single edition for both midmarket and enterprise customers.
BDD has now morphed into Microsoft Deployment Toolkit 2008 (MDT 2008) which lets you deploy the following versions of Microsoft Windows:
Windows Vista
Windows XP Professional
Windows Server 2008
Windows Server 2003
In addition, you can use MDT 2008 to deploy the 2007 Microsoft Office system and Microsoft Office 2003 to your desktop computers.
MDT 2008 simplifies the task of deploying Windows Vista (the focus of this present series of articles) by providing the following benefits:
Provides an integrated workspace from which you can perform hardware/software inventories, mitigate application compatibility issues, migrate user profiles, package and deploy applications, create and manage distribution shares and deployment points, and to build, service and deploy your images.
Supports integration with Windows DS for centralized server-based deployments.
Supports integration with your existing systems management infrastructures that use SMS 2003 and Microsoft System Center Configuration Manager 2007 (SCCM 2007).
Allows you to customize various aspects of the deployment process to suit the needs of your organization.
Understanding LTI vs. ZTI
Depending on your infrastructure, MDT 2008 enables you to perform two basic types of deployments:
Light Touch Installation (LTI) – Lets you deploy Vista without having any systems management infrastructure in place in your organization. LTI is an ideal solution for small to medium-sized organizations who need to deploy Vista to dozens or even hundreds of systems at a site or in a department. LTI deployments can be performed manually, partially unattended, or almost fully unattended as desired. In its simplest form, LTI can even be used to deploy Vista in a workgroup scenario from a single computer running Windows XP. For greater scalability, you can integrated MDT with Windows DS to perform centralized, server-based LTI deployments.
Zero Touch Installation (ZTI) – Lets you deploy Vista by leveraging the capabilities of your existing SMS 2003 or SCCM 2007 infrastructure. ZTI deployments are usually completely automated in nature and are also usually integrated with Windows DS.
Note: This present series of articles will focus on LTI deployments of Windows Vista SP1 Enterprise Edition.
Types of Deployment Scenarios
MDT 2008 supports a variety of different deployment scenarios:
New Computer Scenario – Deploy Vista onto a bare-metal system that has no operating system for a user who does not have an existing computer or user profile on your network. Use this scenario when deploying systems for new employees.
Upgrade Computer Scenario – Upgrade a system running Windows XP to Windows Vista and retain the user's existing profile settings. Use this scenario when you have existing systems whose hardware will support running Vista.
Refresh Computer Scenario – Re-image an existing system that is already running Vista in order to resolve problems the user is experiencing with her computer.
Replace Computer Scenario – Deploy Vista onto a bare-metal system for a user who has an existing computer running Windows XP. During the deployment process, the user's existing profile settings and data are migrated from her old XP computer to her new Vista computer.
Note:
This present series of articles will focus mainly on demonstrating the New Computer deployment scenario.
Installing MDT 2008
You can install MDT 2008 on x86 or x64 systems running the following operating systems:
Windows Server 2008 Standard or Enterprise edition
Windows Server 2003 SP1 or later Standard or Enterprise edition
Windows Vista Business, Enterprise or Ultimate edition
Windows XP Professional SP2 or later
Depending on the platform you choose to install upon, you may also need to download and install the .NET Framework 2.0, MMC 3.0, and various updates.
It's also a good idea to have a second hard disk drive in the computer you are installing MDT on so that you can use this drive to host MDT's distribution share and (depending on your setup) deployment point. This will be explained in more detail in the next article of this series.
Be sure you begin by downloading the latest version of MDT 2008, which at the time of writing is MDT 2008 Update 1. For the scenario used in this series of articles, we're going to install MDT on a server named SEA-MDT that is running Windows Server 2003 R2 SP2 and which belongs to the contoso.com domain. This means that the only additional software we need to preinstall on the system is the .NET Framework 2.0, which can be obtained from Microsoft Download Center.
Begin by downloading MicrosoftDeploymentToolkit_x86.msi or MicrosoftDeploymentToolkit_x64.msi as needed from here, and double-click on the Windows Installer package to launch the setup process (Figure 1):
Figure 1: Installing MDT 2008 Update 1
A complete install of both tools and documentation is selected by default (Figure 2):
Figure 2: Select installation options
Once you have finished installing MDT, launch the Deployment Workbench by clicking Start, All Programs, Microsoft Deployment Toolkit, Deployment Workbench (Figure 3):
Figure 3: The MDT Deployment Workbench
The Workbench is the integrated workspace from which you can perform all of your deployment-related tasks. As you can see from the above figure, the Workbench has four main areas:
Information Center – Provides access to the Getting Started guide and other MDT documentation, news updates concerning MDT, and the latest version of MDT components (see Figure 5 below):
Distribution Share – This is where you bring together your operating system installation files and package files, your application installation files, and any out-of-box device drivers you will need to perform your deployment.
Task Sequences – This is where you define the steps that will take place during your deployment (essentially configuring your answer file).
Deploy – this is where you create your deployment points (the actual sets of OS, app and driver files needed for performing your deployments) and the MDT database (stores configuration information used for customizing your deployments).
Figure 4: The Components node of the Workbench
The Windows AIK provides a collection of tools and documentation for performing unattended installs of Windows Vista, but these tools are not integrated with one another. For instance, you must use one tool (Windows SIM) to create your answer file, another tool (ImageX) to capture an image of your sysprepped reference computer, yet another tool (Package Manager) to service your images, another tool (WinPE) to boot your bare-metal destination computers, and so on. By adding Windows DS to the mix, you can centralize the management and deployment of your images, but you still have to work with a collection of disparate tools to perform your deployment.
To simplify desktop deployment, Microsoft first created Microsoft Solution Accelerator for Business Desktop Deployment (BDD), an integrated toolset together with comprehensive guidance for deploying Windows Vista and the 2007 Office System. BDD went through several versions including:
BDD 2.0 and 2.5 – Used for deploying Windows XP that was released in two editions: Standard edition for smaller midmarket customers, and Enterprise edition for larger organizations that had an Microsoft Systems Management Server 2003 infrastructure deployed.
BDD 2007 – Used for deploying Windows XP, Windows Vista, and the 2007 Office System and released in a single edition for both midmarket and enterprise customers.
BDD has now morphed into Microsoft Deployment Toolkit 2008 (MDT 2008) which lets you deploy the following versions of Microsoft Windows:
Windows Vista
Windows XP Professional
Windows Server 2008
Windows Server 2003
In addition, you can use MDT 2008 to deploy the 2007 Microsoft Office system and Microsoft Office 2003 to your desktop computers.
MDT 2008 simplifies the task of deploying Windows Vista (the focus of this present series of articles) by providing the following benefits:
Provides an integrated workspace from which you can perform hardware/software inventories, mitigate application compatibility issues, migrate user profiles, package and deploy applications, create and manage distribution shares and deployment points, and to build, service and deploy your images.
Supports integration with Windows DS for centralized server-based deployments.
Supports integration with your existing systems management infrastructures that use SMS 2003 and Microsoft System Center Configuration Manager 2007 (SCCM 2007).
Allows you to customize various aspects of the deployment process to suit the needs of your organization.
Understanding LTI vs. ZTI
Depending on your infrastructure, MDT 2008 enables you to perform two basic types of deployments:
Light Touch Installation (LTI) – Lets you deploy Vista without having any systems management infrastructure in place in your organization. LTI is an ideal solution for small to medium-sized organizations who need to deploy Vista to dozens or even hundreds of systems at a site or in a department. LTI deployments can be performed manually, partially unattended, or almost fully unattended as desired. In its simplest form, LTI can even be used to deploy Vista in a workgroup scenario from a single computer running Windows XP. For greater scalability, you can integrated MDT with Windows DS to perform centralized, server-based LTI deployments.
Zero Touch Installation (ZTI) – Lets you deploy Vista by leveraging the capabilities of your existing SMS 2003 or SCCM 2007 infrastructure. ZTI deployments are usually completely automated in nature and are also usually integrated with Windows DS.
Note: This present series of articles will focus on LTI deployments of Windows Vista SP1 Enterprise Edition.
Types of Deployment Scenarios
MDT 2008 supports a variety of different deployment scenarios:
New Computer Scenario – Deploy Vista onto a bare-metal system that has no operating system for a user who does not have an existing computer or user profile on your network. Use this scenario when deploying systems for new employees.
Upgrade Computer Scenario – Upgrade a system running Windows XP to Windows Vista and retain the user's existing profile settings. Use this scenario when you have existing systems whose hardware will support running Vista.
Refresh Computer Scenario – Re-image an existing system that is already running Vista in order to resolve problems the user is experiencing with her computer.
Replace Computer Scenario – Deploy Vista onto a bare-metal system for a user who has an existing computer running Windows XP. During the deployment process, the user's existing profile settings and data are migrated from her old XP computer to her new Vista computer.
Note:
This present series of articles will focus mainly on demonstrating the New Computer deployment scenario.
Installing MDT 2008
You can install MDT 2008 on x86 or x64 systems running the following operating systems:
Windows Server 2008 Standard or Enterprise edition
Windows Server 2003 SP1 or later Standard or Enterprise edition
Windows Vista Business, Enterprise or Ultimate edition
Windows XP Professional SP2 or later
Depending on the platform you choose to install upon, you may also need to download and install the .NET Framework 2.0, MMC 3.0, and various updates.
It's also a good idea to have a second hard disk drive in the computer you are installing MDT on so that you can use this drive to host MDT's distribution share and (depending on your setup) deployment point. This will be explained in more detail in the next article of this series.
Be sure you begin by downloading the latest version of MDT 2008, which at the time of writing is MDT 2008 Update 1. For the scenario used in this series of articles, we're going to install MDT on a server named SEA-MDT that is running Windows Server 2003 R2 SP2 and which belongs to the contoso.com domain. This means that the only additional software we need to preinstall on the system is the .NET Framework 2.0, which can be obtained from Microsoft Download Center.
Begin by downloading MicrosoftDeploymentToolkit_x86.msi or MicrosoftDeploymentToolkit_x64.msi as needed from here, and double-click on the Windows Installer package to launch the setup process (Figure 1):
Figure 1: Installing MDT 2008 Update 1
A complete install of both tools and documentation is selected by default (Figure 2):
Figure 2: Select installation options
Once you have finished installing MDT, launch the Deployment Workbench by clicking Start, All Programs, Microsoft Deployment Toolkit, Deployment Workbench (Figure 3):
Figure 3: The MDT Deployment Workbench
The Workbench is the integrated workspace from which you can perform all of your deployment-related tasks. As you can see from the above figure, the Workbench has four main areas:
Information Center – Provides access to the Getting Started guide and other MDT documentation, news updates concerning MDT, and the latest version of MDT components (see Figure 5 below):
Distribution Share – This is where you bring together your operating system installation files and package files, your application installation files, and any out-of-box device drivers you will need to perform your deployment.
Task Sequences – This is where you define the steps that will take place during your deployment (essentially configuring your answer file).
Deploy – this is where you create your deployment points (the actual sets of OS, app and driver files needed for performing your deployments) and the MDT database (stores configuration information used for customizing your deployments).
Figure 4: The Components node of the Workbench
Thursday, December 9, 2010
Computer Restarts
We have received lot many problems from our readers complaining that their computer restarts abruptly. It seems like that the computer restarts without any reason, but it is not so, every-time your computer restarts abruptly, there must be some or other reason that you might not have noticed.
In this post we will look into those reasons and the possible solutions to fix computer restart problem. So lets have a look at the possible reasons:
Computer restart due to overheating
Computer restart due to faulty RAM
Computer restart due to faulty Hard-disk
Computer restart due to overheating up of hard-disk
Computer restart on attaching some external USB device
Computer restart due to other hardware problem
Some software causing operating system crash causes computer restart
There may be some rare typical reasons also, but let us focus on these common reasons and lets have a look on how to fix computer restart problem because of above reasons.
Going one by one, lets see how these problems can be fixed:
Computer restart due to overheating:
Computer restarts due to over-heating when the processor fan goes faulty. See this post for detailed solution.
Computer restart due to faulty RAM:
Computer restarts abruptly if RAM goes faulty, or if you install some in-compatible RAM or more than one RAM modules of different frequency or type. See the RAM upgrade post for details.
Computer restart due to faulty Hard-disk:
Faulty hard disk is one of the most common reasons for abrupt computer restart. Run a hard disk scan to fix this issue. If there are bad-sectors on your hard-disk, its the time to get it replaced.
Computer restart due to overheating up of hard-disk:
If there is not proper ventilation around your computer, the hard disk may also reach temperatures where it starts to malfunction and computer restarts in some of these cases. The fix is to keep the computer at a ventilated place. Also installing some cabinet fans also solves this problem to big extent.
Computer restart on attaching some external USB device:
I have experienced that when I attached my memory-card-reader to my computer, the computer restarted. I tried it again, it again re-started, it was not a co-incidence, it was a faulty device. So the fix is, remove all external USB devices and insert one by one, and see which device is causing problem.
Computer restart due to other hardware problem:
Computer restart problem is also caused by faulty motherboard sometimes,for example my desktop’s BIOS went corrupt a few weeks back. But the chances of motherboard are relatively low, so if nothing else seems to help, get the motherboard checked by hardware vendor or technician.
Some software causing operating system crash causes computer restart:
Sometimes a software can also be the culprit behind the computer restart. If you have recently installed any new application or game, and computer has started to restart when using that application or game, you need to un-install it to fix the issue.
everything's gone. Be it a random reboot, or the infamous "blue screen of death", it's very, very frustrating.
The problem is that this can be caused by so many things, it's difficult to nail it down quickly.
Let's run through some of the possibilities, and what I'd do.
•
Malware
You've touched on one thing I always look at first: viruses and spyware. Do make sure that your scanners are running, and are being regularly updated with the latest databases of spyware and virus definitions. For anti-spyware tools, that should happen daily - anti-spyware tools typically do so less often.
Software
If you're running Windows 9x (meaning Windows 95, 98 or Me), there's about a 50/50 chance that the problem is a software problem. Because of how their design evolved, those versions of Windows were all somewhat more vulnerable to crashing bugs in the software. A poorly written device driver, or even an application bug, could in the worst case scenario cause a system reboot or blue screen.
If you're running Windows XP (or Windows NT, 2000 or 2003), the system is designed more robustly - meaning that it's more difficult for these types of problems to result in a random reboot or crash. Not impossible, just much less likely.
If you've made a recent change to your system, perhaps installed a new software package, or a new piece of hardware, and these problems started happening thereafter, that's a likely clue. Depending on the software or hardware, my first reaction would be to look to the vendor for reported problems and possible updates. In particular, device drivers are the most likely to cause crashes and reboots without warning.
As I said, software related reboots and blue screens have become more rare under Windows XP. However you should still make sure that your system is as up-to-date as possible, particularly including drivers for recently installed hardware.
"... Which leads to the ultimate predicament... it could be anything. Quite literally.I know that many folks have become suspicious of Windows Automatic Update for various reasons, but I've not heard of any crashes resulting its use. I still recommend it as the best way to keep Windows up to date.
Hardware
I will say that if your computer is still under warranty, you need to talk to the manufacturer first. You should exhaust all your options in getting them to repair a failing machine before you head out on your own and possibly void your warranty.
Naturally, if you've recently installed new hardware, that's a possible clue. You might consider removing it temporarily to see if the problem abates. If it does, it points to either the device itself being the cause, or perhaps the system power supply, as I'll discuss in just a minute.
If your computer has been running fine for some time, and you haven't installed any new hardware or software recently, then my tendency would be to start suspecting various hardware components.
Perhaps the most common are failing fans. The fans that move air through your machine to keep it cool are critical to its operation, and are often the first to fail - either due to accumulated dust and dirt, or simple age. When the fan stops working, the machine overheats, and when the machine overheats - it crashes. Randomly.
Next most common is a failing power supply. Power supplies can fail slowly - meaning that they can become 'marginal' before they fail completely. And the symptoms of a marginal power supply are - you guessed it - random crashes. This is one of those cases where replacing the power supply (or having someone replace it for you) is often an inexpensive test. Particularly if you've added more hardware to your system over time, you may simply be demanding more of the power supply than it was designed to provide, so an upgrade might well be in order as well.
I have this gut feeling that memory is failing just a little more frequently than in the past. I won't speculate as to why, or even if my observation is accurate. The good news is that there are tools specifically designed for testing memory. Memtest86 is one such tool that performs an exhaustive test of your computer's memory. Microsoft also provides a Windows memory Diagnostic. Both tools run from a bootable floppy or CD (Windows cannot be running for the tests to exercise all memory), and both tools are free.
Naturally, it's also possible that the fault lies elsewhere. Your motherboard, an add-in card, even your disk drives or video card. Which leads to the ultimate predicament ... it could be anything. Quite literally.
One of the more common repair techniques is to make an educated guess at what might be wrong, replace that component, and keep repeating until all the components of your computer have been replaced, or the problem goes away.
Unfortunately, doing that is beyond the resources or desire of most computer owners.
My approach
So here's what I would do, when faced with a randomly rebooting computer:
Yes, I would consider upgrading to Windows XP, if the machine is capable of it.
Make sure that anti-virus and anti-spyware utilities are running and up-to-date.
Make sure that the operating system and all device drivers are as up-to-date as possible.
Run a memory diagnostic such as Memtest86 or Windows memory Diagnostic.
Run a hard disk diagnostic such as SpinRite.
Run a motherboard temperature monitoring tool such as Motherboard Monitor - it's a free tool that will report your CPU's temperature among other things, and will let you see if the machine is overheating for some reason.
At this point I've done pretty much everything I can that doesn't involve opening the computer. If the problem isn't evident or resolved, we need to get a little more serious. This might also be the time for some to simply take their computer in to a technician for diagnosis.
Next, I'd open up the computer and:
Carefully vacuum all the dust out of the machine.
Make sure that the fans which are accessible are running properly. If not, I replace them. If the machine doesn't crash as quickly with the cover off, that's often a sign of overheating.
Remove as many optional hardware components as possible that would still allow the machine to run. If the problem disappeared, I would re-install components until it reappeared, and then remove other components to make sure that the problem was associated with only a specific component.
Re-seat all remaining and accessible connectors and expansion cards - sometimes problems are as simple as a loose connection.
At this point we've done pretty much everything we can with what we have on hand. Next up, we start spending money (or, perhaps if you're a geek, pulling from your spare parts bin), and go down the "replace parts until it works" path. This is another jump off point for many - it's definitely easier to simply take the computer in to a technician for diagnosis.
I'd replace the power supply first. Unless there's other data that says the problem is likely to be elsewhere, I'm just playing the odds here. If I went this far, and I planned to keep the computer for some time, I'd also consider upgrading to a higher wattage supply at the same time. Replacing a power supply is only moderately difficult.
Next up, would be the motherboard. This is a bit of work, as it often involves tearing the entire computer apart.
Lastly, I'd consider replacing the computer.
In reality, unless you're really interested in playing with the hardware and trying the "replace it 'til it works" approach, I'd recommend skipping this last set of items completely and taking it into a repair shop to let them figure it out.
And, naturally, before you do so, it might also be time for a cost/benefit analysis: will it be cheaper or more effective to simply replace the computer than to fix it? I'm not at all saying that it will be - it depends on the availability and going rates for computer repair in your area, and the potential cost of fixing whatever is broken. But this is the time to at least do the math and compare.
In this post we will look into those reasons and the possible solutions to fix computer restart problem. So lets have a look at the possible reasons:
Computer restart due to overheating
Computer restart due to faulty RAM
Computer restart due to faulty Hard-disk
Computer restart due to overheating up of hard-disk
Computer restart on attaching some external USB device
Computer restart due to other hardware problem
Some software causing operating system crash causes computer restart
There may be some rare typical reasons also, but let us focus on these common reasons and lets have a look on how to fix computer restart problem because of above reasons.
Going one by one, lets see how these problems can be fixed:
Computer restart due to overheating:
Computer restarts due to over-heating when the processor fan goes faulty. See this post for detailed solution.
Computer restart due to faulty RAM:
Computer restarts abruptly if RAM goes faulty, or if you install some in-compatible RAM or more than one RAM modules of different frequency or type. See the RAM upgrade post for details.
Computer restart due to faulty Hard-disk:
Faulty hard disk is one of the most common reasons for abrupt computer restart. Run a hard disk scan to fix this issue. If there are bad-sectors on your hard-disk, its the time to get it replaced.
Computer restart due to overheating up of hard-disk:
If there is not proper ventilation around your computer, the hard disk may also reach temperatures where it starts to malfunction and computer restarts in some of these cases. The fix is to keep the computer at a ventilated place. Also installing some cabinet fans also solves this problem to big extent.
Computer restart on attaching some external USB device:
I have experienced that when I attached my memory-card-reader to my computer, the computer restarted. I tried it again, it again re-started, it was not a co-incidence, it was a faulty device. So the fix is, remove all external USB devices and insert one by one, and see which device is causing problem.
Computer restart due to other hardware problem:
Computer restart problem is also caused by faulty motherboard sometimes,for example my desktop’s BIOS went corrupt a few weeks back. But the chances of motherboard are relatively low, so if nothing else seems to help, get the motherboard checked by hardware vendor or technician.
Some software causing operating system crash causes computer restart:
Sometimes a software can also be the culprit behind the computer restart. If you have recently installed any new application or game, and computer has started to restart when using that application or game, you need to un-install it to fix the issue.
everything's gone. Be it a random reboot, or the infamous "blue screen of death", it's very, very frustrating.
The problem is that this can be caused by so many things, it's difficult to nail it down quickly.
Let's run through some of the possibilities, and what I'd do.
•
Malware
You've touched on one thing I always look at first: viruses and spyware. Do make sure that your scanners are running, and are being regularly updated with the latest databases of spyware and virus definitions. For anti-spyware tools, that should happen daily - anti-spyware tools typically do so less often.
Software
If you're running Windows 9x (meaning Windows 95, 98 or Me), there's about a 50/50 chance that the problem is a software problem. Because of how their design evolved, those versions of Windows were all somewhat more vulnerable to crashing bugs in the software. A poorly written device driver, or even an application bug, could in the worst case scenario cause a system reboot or blue screen.
If you're running Windows XP (or Windows NT, 2000 or 2003), the system is designed more robustly - meaning that it's more difficult for these types of problems to result in a random reboot or crash. Not impossible, just much less likely.
If you've made a recent change to your system, perhaps installed a new software package, or a new piece of hardware, and these problems started happening thereafter, that's a likely clue. Depending on the software or hardware, my first reaction would be to look to the vendor for reported problems and possible updates. In particular, device drivers are the most likely to cause crashes and reboots without warning.
As I said, software related reboots and blue screens have become more rare under Windows XP. However you should still make sure that your system is as up-to-date as possible, particularly including drivers for recently installed hardware.
"... Which leads to the ultimate predicament... it could be anything. Quite literally.I know that many folks have become suspicious of Windows Automatic Update for various reasons, but I've not heard of any crashes resulting its use. I still recommend it as the best way to keep Windows up to date.
Hardware
I will say that if your computer is still under warranty, you need to talk to the manufacturer first. You should exhaust all your options in getting them to repair a failing machine before you head out on your own and possibly void your warranty.
Naturally, if you've recently installed new hardware, that's a possible clue. You might consider removing it temporarily to see if the problem abates. If it does, it points to either the device itself being the cause, or perhaps the system power supply, as I'll discuss in just a minute.
If your computer has been running fine for some time, and you haven't installed any new hardware or software recently, then my tendency would be to start suspecting various hardware components.
Perhaps the most common are failing fans. The fans that move air through your machine to keep it cool are critical to its operation, and are often the first to fail - either due to accumulated dust and dirt, or simple age. When the fan stops working, the machine overheats, and when the machine overheats - it crashes. Randomly.
Next most common is a failing power supply. Power supplies can fail slowly - meaning that they can become 'marginal' before they fail completely. And the symptoms of a marginal power supply are - you guessed it - random crashes. This is one of those cases where replacing the power supply (or having someone replace it for you) is often an inexpensive test. Particularly if you've added more hardware to your system over time, you may simply be demanding more of the power supply than it was designed to provide, so an upgrade might well be in order as well.
I have this gut feeling that memory is failing just a little more frequently than in the past. I won't speculate as to why, or even if my observation is accurate. The good news is that there are tools specifically designed for testing memory. Memtest86 is one such tool that performs an exhaustive test of your computer's memory. Microsoft also provides a Windows memory Diagnostic. Both tools run from a bootable floppy or CD (Windows cannot be running for the tests to exercise all memory), and both tools are free.
Naturally, it's also possible that the fault lies elsewhere. Your motherboard, an add-in card, even your disk drives or video card. Which leads to the ultimate predicament ... it could be anything. Quite literally.
One of the more common repair techniques is to make an educated guess at what might be wrong, replace that component, and keep repeating until all the components of your computer have been replaced, or the problem goes away.
Unfortunately, doing that is beyond the resources or desire of most computer owners.
My approach
So here's what I would do, when faced with a randomly rebooting computer:
Yes, I would consider upgrading to Windows XP, if the machine is capable of it.
Make sure that anti-virus and anti-spyware utilities are running and up-to-date.
Make sure that the operating system and all device drivers are as up-to-date as possible.
Run a memory diagnostic such as Memtest86 or Windows memory Diagnostic.
Run a hard disk diagnostic such as SpinRite.
Run a motherboard temperature monitoring tool such as Motherboard Monitor - it's a free tool that will report your CPU's temperature among other things, and will let you see if the machine is overheating for some reason.
At this point I've done pretty much everything I can that doesn't involve opening the computer. If the problem isn't evident or resolved, we need to get a little more serious. This might also be the time for some to simply take their computer in to a technician for diagnosis.
Next, I'd open up the computer and:
Carefully vacuum all the dust out of the machine.
Make sure that the fans which are accessible are running properly. If not, I replace them. If the machine doesn't crash as quickly with the cover off, that's often a sign of overheating.
Remove as many optional hardware components as possible that would still allow the machine to run. If the problem disappeared, I would re-install components until it reappeared, and then remove other components to make sure that the problem was associated with only a specific component.
Re-seat all remaining and accessible connectors and expansion cards - sometimes problems are as simple as a loose connection.
At this point we've done pretty much everything we can with what we have on hand. Next up, we start spending money (or, perhaps if you're a geek, pulling from your spare parts bin), and go down the "replace parts until it works" path. This is another jump off point for many - it's definitely easier to simply take the computer in to a technician for diagnosis.
I'd replace the power supply first. Unless there's other data that says the problem is likely to be elsewhere, I'm just playing the odds here. If I went this far, and I planned to keep the computer for some time, I'd also consider upgrading to a higher wattage supply at the same time. Replacing a power supply is only moderately difficult.
Next up, would be the motherboard. This is a bit of work, as it often involves tearing the entire computer apart.
Lastly, I'd consider replacing the computer.
In reality, unless you're really interested in playing with the hardware and trying the "replace it 'til it works" approach, I'd recommend skipping this last set of items completely and taking it into a repair shop to let them figure it out.
And, naturally, before you do so, it might also be time for a cost/benefit analysis: will it be cheaper or more effective to simply replace the computer than to fix it? I'm not at all saying that it will be - it depends on the availability and going rates for computer repair in your area, and the potential cost of fixing whatever is broken. But this is the time to at least do the math and compare.
Subscribe to:
Posts (Atom)