AD Domains and Trusts
domain.msc
Active Directory Management
admgmt.msc
AD Sites and Serrvices
dssite.msc
AD Users and COmputers
dsa.msc
ADSI Edit
adsiedit.msc
Authorization manager
azman.msc
Certification Authority Management
certsrv.msc
Certificate Templates
certtmpl.msc
Cluster Administrator
cluadmin.exe
Computer Management
compmgmt.msc
Component Services
comexp.msc
Configure Your Server
cys.exe
Device Manager
devmgmt.msc
DHCP Managment
dhcpmgmt.msc
Disk Defragmenter
dfrg.msc
Disk Manager
diskmgmt.msc
Distributed File System
dfsgui.msc
DNS Managment
dnsmgmt.msc
Event Viewer
eventvwr.msc
Indexing Service Management
ciadv.msc
IP Address Manage
ipaddrmgmt.msc
Licensing Manager
llsmgr.exe
Local Certificates Management
certmgr.msc
Local Group Policy Editor
gpedit.msc
Local Security Settings Manager
secpol.msc
Local Users and Groups Manager
lusrmgr.msc
Network Load balancing
nlbmgr.exe
Performance Montior
perfmon.msc
PKI Viewer
pkiview.msc
Public Key Managment
pkmgmt.msc
QoS Control Management
acssnap.msc
Remote Desktops
tsmmc.msc
Remote Storage Administration
rsadmin.msc
Removable Storage
ntmsmgr.msc
Removalbe Storage Operator Requests
ntmsoprq.msc
Routing and Remote Access Manager
rrasmgmt.msc
Resultant Set of Policy
rsop.msc
Schema management
schmmgmt.msc
Services Management
services.msc
Shared Folders
fsmgmt.msc
SID Security Migration
sidwalk.msc
Telephony Management
tapimgmt.msc
Terminal Server Configuration
tscc.msc
Terminal Server Licensing
licmgr.exe
Terminal Server Manager
tsadmin.exe
UDDI Services Managment
uddi.msc
Windows Mangement Instumentation
wmimgmt.msc
Wednesday, December 1, 2010
When opening the Word document users are getting error “Word cannot start the converter mswrd632.wpc” or “Cannot load Word for Windows 6.0 files”
When opening the Word document users are getting error “Word cannot start the converter mswrd632.wpc” or “Cannot load Word for Windows 6.0 files”
Problem: - When attempting to open a Word document, users are getting one of following error
1) Word cannot start the converter mswrd632.wpc
2) Cannot load Word for Windows 6.0 files
Cause: - This issue may be started happening after you applied following security update. You may be trying to open a file has the ".doc" file name extension, but the content is a plain text file or another kind of file that is not a Microsoft Word binary file.
Resolution: - The registry fix for this issue is already provided in the KB 973904. Following solution is the updated solution which is provided by Microsoft Word Team. You can use the following steps for the resolution.
Update:- Fix-IT solution for this registry changes is released. Check KB973904
WARNING : If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
To resolve this issue, an affected user can unregister the mswrd632 converter by editing the registry as follows:
a. Click Start, click Run, type regedit, and then click OK.
b. Locate and then click the following registry subkey:
2. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools
\Text Converters\Import\MSWord6.wpc
c. On the Edit menu, click Delete.
d. Click Yes.
e. Exit Registry Editor.
This change will effectively unregister the converter and disable it for third-party applications and for Microsoft Office. Microsoft Office will use its own text converters to open these kinds of files.
==============================================================================================
In case you want to re-enable the converter, you can add an AllowConversion registry entry with a DWORD value of 1. After you set this registry key value to 1, third-party applications can load the Word 6.0/95 for Windows and Macintosh to RTF converter. Please be aware that setting this registry key removes the protection that was added by this security update. Therefore, it should be done only when you trust the source of the files that are loaded by this converter. You can also disable this converter by setting the registry key value to 0.
To do this, follow these steps:
a. Click Start, click Run, type regedit, and then click OK.
b. Locate and then click the following registry subkey. Or, create it if it is not present.
For 32-bit versions of Windows
2. HKEY_LOCAL_MACHINE\Software\Microsoft\Windows
\CurrentVersion\Applets\Wordpad
c. For Microsoft Windows on Windows 64 (WOW) mode
HKEY_LOCAL_MACHINE\Software\Wow6432Node\microsoft
\Windows\CurrentVersion\Applets\Wordpad
d. On the Edit menu, point to New, and then click DWORD Value.
e. Type AllowConversion for the name of the DWORD, and then press ENTER.
f. Right-click AllowConversion, and then click Modify.
g. In the Value data box, type 1, and then click OK.
h. Exit Registry Editor.
Problem: - When attempting to open a Word document, users are getting one of following error
1) Word cannot start the converter mswrd632.wpc
2) Cannot load Word for Windows 6.0 files
Cause: - This issue may be started happening after you applied following security update. You may be trying to open a file has the ".doc" file name extension, but the content is a plain text file or another kind of file that is not a Microsoft Word binary file.
Resolution: - The registry fix for this issue is already provided in the KB 973904. Following solution is the updated solution which is provided by Microsoft Word Team. You can use the following steps for the resolution.
Update:- Fix-IT solution for this registry changes is released. Check KB973904
WARNING : If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
To resolve this issue, an affected user can unregister the mswrd632 converter by editing the registry as follows:
a. Click Start, click Run, type regedit, and then click OK.
b. Locate and then click the following registry subkey:
2. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools
\Text Converters\Import\MSWord6.wpc
c. On the Edit menu, click Delete.
d. Click Yes.
e. Exit Registry Editor.
This change will effectively unregister the converter and disable it for third-party applications and for Microsoft Office. Microsoft Office will use its own text converters to open these kinds of files.
==============================================================================================
In case you want to re-enable the converter, you can add an AllowConversion registry entry with a DWORD value of 1. After you set this registry key value to 1, third-party applications can load the Word 6.0/95 for Windows and Macintosh to RTF converter. Please be aware that setting this registry key removes the protection that was added by this security update. Therefore, it should be done only when you trust the source of the files that are loaded by this converter. You can also disable this converter by setting the registry key value to 0.
To do this, follow these steps:
a. Click Start, click Run, type regedit, and then click OK.
b. Locate and then click the following registry subkey. Or, create it if it is not present.
For 32-bit versions of Windows
2. HKEY_LOCAL_MACHINE\Software\Microsoft\Windows
\CurrentVersion\Applets\Wordpad
c. For Microsoft Windows on Windows 64 (WOW) mode
HKEY_LOCAL_MACHINE\Software\Wow6432Node\microsoft
\Windows\CurrentVersion\Applets\Wordpad
d. On the Edit menu, point to New, and then click DWORD Value.
e. Type AllowConversion for the name of the DWORD, and then press ENTER.
f. Right-click AllowConversion, and then click Modify.
g. In the Value data box, type 1, and then click OK.
h. Exit Registry Editor.
Tuesday, September 21, 2010
Migrate MS Outlook Autocomplete cache to new PC or profile
The file is located under
C:\Documents and Settings\\Application Data\Microsoft\Outlook\
The folder C:\Documents and Settings\\Application Data\ is hidden and hence choose to show hidden files under “Folder Options”.
Once into the folder look for the file with the extension “NK2″. This filename will be “outlookprofilename.NK2″. For instance, on my PC, outlook profile name is “outlook” and hence the file name is “outlook.NK2″
C:\Documents and Settings\
The folder C:\Documents and Settings\
Once into the folder look for the file with the extension “NK2″. This filename will be “outlookprofilename.NK2″. For instance, on my PC, outlook profile name is “outlook” and hence the file name is “outlook.NK2″
Outlook 2007 -Removing an add-in that no longer exists?
Outlook 2007 -Removing an add-in that no longer exists?
Solution 1:
Delete "extend.dat", because the add-ins are cached there.
Go to My Computer (Windows Explorer)
Navigate the menus through: Tools | Folder Options | [View] tab | "Advanced Settings" section | Hidden Files and Folders
Tick (x) Show Hidden Files and Folders, and click [Ok]
In Windows Explorer, navigate to C:\documents and settings\{username}\Local Settings\Application Data\Microsoft\Outlook
Delete "extend.dat"
Close Windows Explorer, and reopen Outlook
Solution 2:
Use the Outlook 2007 Trust Center:
Open Outlook
Navigate the menus through: Tools | Trust Center... | Add-ins (on the left)
Ensure "COM Add-ins" is showing next to "Manage:", at the bottom of the dialog
Click [Go...]
Untick "[ ] The offending extension"
Click [Ok]
Restart Outlook and verify that it worked.
Solution 1:
Delete "extend.dat", because the add-ins are cached there.
Go to My Computer (Windows Explorer)
Navigate the menus through: Tools | Folder Options | [View] tab | "Advanced Settings" section | Hidden Files and Folders
Tick (x) Show Hidden Files and Folders, and click [Ok]
In Windows Explorer, navigate to C:\documents and settings\{username}\Local Settings\Application Data\Microsoft\Outlook
Delete "extend.dat"
Close Windows Explorer, and reopen Outlook
Solution 2:
Use the Outlook 2007 Trust Center:
Open Outlook
Navigate the menus through: Tools | Trust Center... | Add-ins (on the left)
Ensure "COM Add-ins" is showing next to "Manage:", at the bottom of the dialog
Click [Go...]
Untick "[ ] The offending extension"
Click [Ok]
Restart Outlook and verify that it worked.
Friday, September 10, 2010
Pathping
PathPing
PathPing is similar to Tracert except that PathPing is intended to find links that are causing intermittent data loss. PathPing sends packets to each router on the way to a final destination over a period of time and then computes the percentage of packets returned from each hop. Since PathPing shows the degree of packet loss at any given router or link, you can use PathPing to pinpoint which routers or links might be causing network problems.
To use the PathPing utility, at a command prompt type PathPing remote_host, where remote_host is the name or address of a destination computer, server, or router on whose path to which you want to test intermittent data loss.
The following shows a sample PathPing output:
D:\>pathping -n testpc1
Tracing route to testpc1 [7.54.1.196]
over a maximum of 30 hops:
0 172.16.87.35
1 172.16.87.218
2 192.168.52.1
3 192.168.80.1
4 7.54.247.14
5 7.54.1.196
Computing statistics for 25 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 172.16.87.35 0/ 100 = 0% |
1 41ms 0/ 100 = 0% 0/ 100 = 0% 172.16.87.218
13/ 100 = 13% |
2 22ms 16/ 100 = 16% 3/ 100 = 3% 192.168.52.1
0/ 100 = 0% |
3 24ms 13/ 100 = 13% 0/ 100 = 0% 192.168.80.1
0/ 100 = 0% |
4 21ms 14/ 100 = 14% 1/ 100 = 1% 7.54.247.14 0/ 100 = 0% | 5 24ms 13/ 100 = 13%
0/ 100 = 0% 7.54.1.196 Trace complete.
Notice how the output above first lists the five hops on the path to the specified destina- tion and then computes the percentage of data lost over each of these hops. In this case, PathPing shows that data loss at a rate of 13% is occurring between the local computer (172.16.87.35) and the first hop (172.16.87.218).
PathPing is similar to Tracert except that PathPing is intended to find links that are causing intermittent data loss. PathPing sends packets to each router on the way to a final destination over a period of time and then computes the percentage of packets returned from each hop. Since PathPing shows the degree of packet loss at any given router or link, you can use PathPing to pinpoint which routers or links might be causing network problems.
To use the PathPing utility, at a command prompt type PathPing remote_host, where remote_host is the name or address of a destination computer, server, or router on whose path to which you want to test intermittent data loss.
The following shows a sample PathPing output:
D:\>pathping -n testpc1
Tracing route to testpc1 [7.54.1.196]
over a maximum of 30 hops:
0 172.16.87.35
1 172.16.87.218
2 192.168.52.1
3 192.168.80.1
4 7.54.247.14
5 7.54.1.196
Computing statistics for 25 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 172.16.87.35 0/ 100 = 0% |
1 41ms 0/ 100 = 0% 0/ 100 = 0% 172.16.87.218
13/ 100 = 13% |
2 22ms 16/ 100 = 16% 3/ 100 = 3% 192.168.52.1
0/ 100 = 0% |
3 24ms 13/ 100 = 13% 0/ 100 = 0% 192.168.80.1
0/ 100 = 0% |
4 21ms 14/ 100 = 14% 1/ 100 = 1% 7.54.247.14 0/ 100 = 0% | 5 24ms 13/ 100 = 13%
0/ 100 = 0% 7.54.1.196 Trace complete.
Notice how the output above first lists the five hops on the path to the specified destina- tion and then computes the percentage of data lost over each of these hops. In this case, PathPing shows that data loss at a rate of 13% is occurring between the local computer (172.16.87.35) and the first hop (172.16.87.218).
Ping & ICMP
ICMP is, however, blocked by default by Windows Fire- wall in Windows Vista and Windows Server 2008, and it is also blocked by some routers and stand-alone firewalls. Consequently, to perform adequate troubleshooting of network con- nectivity, you need to ensure that ICMP is not blocked by the remote host. To enable a fire- wall exception for ICMP in Windows Vista and Windows Server 2008, enable File Sharing in Network and Sharing Center.
If you want to be able to ping a computer, you don't have to turn off the firewall. You only need to TURN ON the file sharing in network sharing center.
If you want to be able to ping a computer, you don't have to turn off the firewall. You only need to TURN ON the file sharing in network sharing center.
Subscribe to:
Posts (Atom)