Friday, October 23, 2009

How to remove field codes (eg: {page})from my Word documents

Simply click: Alt + F9
If they're TC or XE fields, they're formatted as Hidden text, so the usual
Alt+F9 toggle doesn't work for them; you have to hide Hidden text instead.
In Word, click on Tools | Options | View | uncheck the "Hidden text" box
| OK.

Wednesday, October 21, 2009

Enabling Account Privileges in WMI of a Vista or Server 2008 computer

The account you specify in the Credentials Library must possess security access to the namespace and subnamespaces of the monitored target computer. To enable these privileges, complete the following procedure.
To enable namespace and subnamespaces privileges:
1. Log on to the computer you want to monitor with an administrator account.
2. Navigate to Start > Control Panel > Administrative Tools > Computer Management > Services and Applications. You need to switch to the Classic View of the Control Panel to use this navigation path.
3. Click WMI Control, and then right-click and select Properties.
4. Select the Security tab, and then expand Root and click CIMV2.
5. Click Security and then select the user account used to access this computer and ensure you grant the following permissions:
Enable Account
Remote Enable

6. Click Advanced, and then select the user account used to access this computer.
7. Click Edit, select This namespace and subnamespaces in the Apply to field, and then click OK.
8. Click OK on the Advanced Security Settings for CIMV2 window.
9. Click OK on the Security for Root\CIMV2 window.
10. Click Services in the left navigation pane of Computer Management.
11. Select Windows Management Instrumentation in the Services result pane, and then click Restart.

Allowing WMI through the Windows Firewall of a Vista or Server 2008 computer

You must allow WMI traffic through the firewall of the monitored application server. The following procedure walks you through allowing WMI through the Windows Firewall.
To allow WMI traffic through the Windows Firewall:
1. Log on to the computer you want to monitor with an administrator account.
2. Navigate to Start > Control Panel > Security Center. You need to switch to the Classic View of the Control Panel to use this navigation path.
3. Click Windows Firewall in the left navigation pane.
4. Click Allow a program through Windows Firewall in the left navigation pane.
5. Check Windows Management Instumentation (WMI), and then click OK.

Enabling DCOM of a Vista or Server 2008 computer

Windows Management Instrumentation (WMI) uses DCOM to communicate with monitored target computers. Therefore, for enable WMI, DCOM must be enabled and properly configured.
To enable DCOM permissions for your credentials:
1. Log on to the computer you want to monitor with an administrator account.
2. Navigate to Start > Control Panel > Administrative Tools > Component Services. You need to switch to the Classic View of the Control Panel to use this navigation path. (You can also launch this console by double-clicking comexp.msc in the /windows/system32 directory. Configuring WMI on Windows Vista and Windows Server 2008 for your requirment.
3. Expand Component Services > Computers.
4. Right-click My Computer, and then select Properties.
5. Select the COM Security tab, and then click Edit Limits in the Access Permissions grouping.
6. Ensure the user account you want to use to collect WMI statistics has Local Access and Remote Access, and then click OK.
7. Click Edit Default, and then ensure the user account you want to use to collect WMI statistics has Local Access and Remote Access,
8. Click OK.
9. Click Edit Limits in the Launch and Activation Permissions grouping.
10. Ensure the user account you want to use to collect WMI statistics has Local Launch, Remote Launch, Local Activation, and Remote Activation, and then click OK.
11. Click Edit Default, and then ensure the user account you want to use to collect WMI statistics Local Launch, Remote Launch, Local Activation, and Remote Activation.
12. Click OK.

Allowing WMI through the Windows Firewall of a Vista or Server 2008 computer

If you are monitoring a target in a workgroup, you need to disable remote User Account Control (UAC). This is not recommended, but it is necessary when monitoring a workgroup computer. Disabling remote user account control does not disable local user account control functionality.
Warning: The following procedure requires the modification or creation of a registry key. Changing the registry can have adverse effects on your computer and may result in an unbootable system. Consider backing up your registry before making these changes.
To disable remote UAC for a workgroup computer:
1. Log on to the computer you want to monitor with an administrator account.
2. Click Start > Accessories > Command Prompt.
3. Enter regedit.
4. Expand HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System.
5. Locate or create a DWORD entry named LocalAccountTokenFilterPolicy and provide a DWORD value of 1.
Note: To re-enable remote UAC, change this value to 0.

To add your monitor account to the local administrator group of a Vista or Server 2008 computer:

1. Log on to the computer you want to monitor with an administrator account.
2. Navigate to Start > Control Panel > Administrative Tools > Computer Management >Local Users and Groups > Groups. You need to switch to the Classic View of the Control Panel to use this navigation path
3. Right-click Administrators, and then click Add to group
4. If the account you want to use is not currently a member of this group, complete the following procedure
a. Click Add on the Administrators Properties window
b. Type the name of the account you want to use to gather WMI statistics, and then click OK
5. Click OK on the Administrators Properties window, and then close the Computer Management window

Tuesday, October 13, 2009

HOW TO: Configure the Simple Network Management Protocol (SNMP) Service in Windows Server 2003

How to Configure SNMP Agent Information
To configure SNMP agent information:
Click Start, point to Control Panel, point to Administrative Tools, and then click Computer Management.
In the console tree, expand Services and Applications, and then click Services.
In the right pane, double-click SNMP Service.
Click the Agent tab.
Type the name of the user or administrator of the computer in the Contact box, and then type the physical location of the computer or contact in the Location box.

These comments are treated as text and are optional.
Under Service, click to select the check boxes next to the services that are provided by your computer. Service options are:
Physical: Specifies whether the computer manages physical devices, such as a hard disk partition.
Applications: Specifies whether the computer uses any programs that send data by using TCP/IP.
Datalink and subnetwork: Specifies whether this computer manages a TCP/IP subnetwork or datalink, such as a bridge.
Internet: Specifies whether this computer acts as an IP gateway (router).
End-to-end: Specifies whether this computer acts as an IP host.
Click OK.
NOTE: If you have installed additional TCP/IP network devices, such as a switch or a router, see Request for Comments (RFC) 1213 for additional information. To view RFC 1213, visit the following Internet Engineering Task Force (IETF) Web site:


http://www.ietf.org/rfc/rfc1213.txt (http://www.ietf.org/rfc/rfc1213.txt)
Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.


Back to the top
How to Configure SNMP Communities and Traps
To configure traps:
Click Start, point to Control Panel, point to Administrative Tools, and then click Computer Management.
In the console tree, expand Services and Applications, and then click Services.
In the right pane, double-click SNMP Service.
Click the Traps tab.
In the Community name box, type the case-sensitive community name to which this computer will send trap messages, and then click Add to list.
Under Trap destinations, click Add.
In the Host name, IP or IPX address box, type the name, IP or IPX address of the host, and then click Add.

The host name or address appears in the Trap destinations list.
Repeat steps 5 through 7 to add the communities and trap destinations that you want.
Click OK.
Back to the top
How to Configure SNMP Security
To configure SNMP security for a community:
Click Start, point to Control Panel, point to Administrative Tools, and then click Computer Management.
In the console tree, expand Services and Applications, and then click Services.
In the right pane, double-click SNMP Service.
Click the Security tab.
Click to select the Send authentication trap check box (if it is not already selected) if you want a trap message sent whenever authentication fails.
Under Accepted community names, click Add.
To specify how the host processes SNMP requests from the selected community, click the permission level that you want in the Community Rights box.
In the Community Name box, type the case-sensitive community name that you want, and then click Add.
Specify whether or not to accept SNMP packets from a host. To do so, do one of the following:
To accept SNMP requests from any host on the network, regardless of identity, click Accept SNMP packets from any host.
To limit the acceptance of SNMP packets, click Accept SNMP packets from these hosts, click Add, and then type the appropriate host name, IP or IPX address in the Host name, IP or IPX address box.
Click Add.
Click OK.
IMPORTANT: If you remove all of the community names, including the default name "Public", SNMP does not respond to any community names that are presented.

User Profile Hive Cleanup Service

The User Profile Hive Cleanup service helps to ensure user sessions are completely terminated when a user logs off. System processes and applications occasionally maintain connections to registry keys in the user profile after a user logs off. In those cases the user session is prevented from completely ending. This can result in problems when using Roaming User Profiles in a server environment or when using locked profiles as implemented through the Shared Computer Toolkit for Windows XP