Turn off the Low Disk Space Notification alert iin Windows XP

Click Start, Run from the Start menu, type regedit and clicking OK. Once in the Registry Editor, navigate to:

HKEY CURRENT USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer

In the right side, look for the value NoLowDiskSpaceChecks. If it's not there, add a new DWORD Value from the Edit menu, name it NoLowDiskSpaceChecks and press Enter.

Now, double-click on the NoLowDiskSpaceChecks entry and change the its value to 1 in the Value Data field. Click OK and you are done.

How To: Transfer your PuTTY settings between computers

Posted Feb 1st 2007 4:00PM by Grant Robertson

Original post here:

http://www.downloadsquad.com/2007/02/01/howto-transfer-your-putty-settings-between-computers/

PuTTY is tops on the short list of applications I install first on any Windows machine. Over the years I've used PuTTY, I've installed it on a huge number of computers but I've always had one complaint; There isn't a configuration file I can backup or move to a new machine.

Getting all the little comfort settings correct for each SSH connection can be a pain. The third time you set emulation, keys, encryption type, etc. for each machine you regularly access, you lose patience. The fifth time you find yourself re-entering settings you might do what I did, find a better way.
Moving PuTTy settings between computers is an easy task once you know what's involved. We'll find the registry keys where PuTTy stores its configuration information and export them to a file. We'll then use that file we've made to import our configuration on the target machine.

Exporting Your PuTTy Configuration

Putty stores its settings in the Windows registry. To save a backup of your Putty settings, you'll need to export this registry key to a file.

HKEY_CURRENT_USER\Software\SimonTatham

(Simon Tatham is the original developer responsible for PuTTy)

1. Click Start->Run and type "RegEdt32" in the "Open" dialog. Click "Ok"

2. One RegEdt32 starts, you'll be presented with an application which looks something like:

3. Press "Ctrl+F" to bring up the Find dialog. Enter the name of the key, "SimonTatham" in the "Find What" field, and make sure only "Keys" is checked in the "Look At" section of the dialog. Finally, click "Find Next"

4. The search may take a while, reminding us that the Windows Registry is a large and mysterious place where dragons be. Let's use these few seconds to reflect on the fact that you should never, ever, never change things in the registry unless you are absolutely, positively, totally, completely, 100% dead sure that you know exactly what you're doing. When the search completes we'll see the key name for which we're looking.

5. Click File->Export. Give your file an appropriate name like, "putty.reg" and click "Save"

6. We're done! Save the putty.reg file somewhere safe. The file doesn't contain any passwords or actual SSH key values so, it's relatively safe from prying eyes. Still, it does contain your configuration and that kind of data is a private matter.

Importing Your PuTTy Configuration

To import your saved PuTTy configuration on any other Windows computer simply copy your exported registry key, right click on the file and click "Merge"

Windows will ask you for confirmation that you want to import this set of registry values. We know this file is safe, because we created it but, you should never import registry information from an unknown source.

That's all you need to know about moving your PuTTy configuration from one machine to another. This can be really useful information when upgrading to a new PC or, if you're an office IT guy where your users all have a standard list of servers they need to connect via SSH, you can create a reference configuration on once machine and "share" it between every computer in the office.

What command line parameters does WinZip support?

Below is some information about the undocumented command line options for using the WinZip program module, winzip32.exe.

WinZip supports command line options to add and extract from files. Be sure to read the Notes section below for additional important information.

Adding Files

The command format is:

    winzip32 [-min] action [options] filename[.zip] files

where:

-min specifies that WinZip should run minimized. If -min is specified, it must be the first command line parameter.

action
-a for add, -f for freshen, -u for update, and -m for move. You must specify one (and only one) of these actions. The actions correspond to the actions described in the section titled "Add dialog box options" in the online manual.

options
-r corresponds to the Include subfolders checkbox in the Add dialog and causes WinZip to add files from subfolders. Folder information is stored for files added from subfolders. If you add -p, WinZip will store folder information for all files added, not just for files from subfolders; the folder information will begin with the folder specified on the command line.

-ex, -en, -ef, -es, and -e0 determine the compression method: eXtra, Normal, Fast, Super fast, and no compression. The default is "Normal". -hs includes hidden and system files. Use -sPassword to specify a case-sensitive password. The password can be enclosed in quotes, for example, -s"Secret Password".

filename.zip
Specifies the name of the Zip file involved. Be sure to use the full filename (including the folder).

files
Is a list of one or more files, or the @ character followed by the filename containing a list of files to add, one filename per line. Wildcards (e.g. *.bak) are allowed.

Extracting Files

The command format is:

    winzip32 -e [options] filename[.zip] folder

where -e is required.

options
-o and -j stand for "Overwrite existing files without prompting" and "Junk pathnames", respectively. Unless -j is specified, folder information is used. Use -sPassword to specify a case-sensitive password. The password can be enclosed in quotes, for example, -s"Secret Password".

filename.zip
Specifies the name of the Zip file involved. Be sure to specify the full filename (including the folder).

folder
Is the name of the folder to which the files are extracted. If the folder does not exist it is created.

Notes

• VERY IMPORTANT: always specify complete filenames, including the full folder name and drive letter, for all file IDs.

• To run WinZip in a minimized inactive icon use the "-min" option. When specified this option must be the first option.

• Only operations involving the built-in zip and unzip are supported.

• Enclose long filenames in quotes.

• When using a list ("@") file, no leading or trailing spaces should appear in file IDs in the list.

• The action and each option must be separated by at least one space.

• WinZip can be used to compress files with cc:Mail . Change the compress= line in the [cc:Mail] section of the appropriate WMAIL.INI files to specify the full path for WinZip followed by "-a %1 @%2". For example, if WinZip is installed in your c:\winzip folder, specify

      compress=c:\winzip\winzip.exe -a %1 @%2

How to Use Nslookup to Verify MX record configuration

1. At a command prompt, type nslookup, and then press ENTER.

2. Type server , where IP address is the IP address of your external DNS server, and then press ENTER.

3. Type set q=MX, and then press ENTER.

4. Type <domain name>, where domain name is the name of your domain, and then press ENTER. The MX record for the domain you entered should be displayed. If the MX record is not displayed, DNS is not configured properly.

he example below shows how MX records appear for the fictitious domain, example.com.

C:\> nslookup

Default Server: pdc.corp.example.com

Address: 192.168.6.13

> server 172.31.01.01

Default Server: dns1.example.com

Address: 172.31.01.01

> set q=mx

> example.com.

Server: dns1.example.com

Address: 10.107.1.7

example.com MX preference = 10, mail exchanger = mail1.example.com

example.com MX preference = 10, mail exchanger = mail2.example.com

example.com MX preference = 10, mail exchanger = mail3.example.com

example.com MX preference = 10, mail exchanger = mail4.example.com

example.com MX preference = 10, mail exchanger = mail5.example.com

mail1.example.com internet address = 172.31.31.01

mail2.example.com internet address = 172.31.31.02

mail3.example.com internet address = 172.31.31.03

mail4.example.com internet address = 172.31.31.04

mail5.example.com internet address = 172.31.31.05

In this example, the preconfigured DNS server is behind a proxy server. Therefore, an external or Internet DNS server with a known IP address of 172.31.01.01 was used to perform the query. Next, the query type was set to MX to locate the mail exchangers for example.com. In this example, five SMTP servers are equally balanced, each with its own IP address. However, your domain might only have a single entry, as seen in the following example:

contoso.com MX preference = 10, mail exchanger = mailbox.contoso.com

mailbox.contoso.com internet address = 10.57.22.3

How to determine the appropriate page file size for 64-bit versions of Windows Server 2003 or Windows XP

Article ID	:	889654
Last Review	:	November 7, 2007
Revision	:	10.4

SUMMARY

The 64-bit versions of Microsoft Windows Server 2003 and Microsoft Windows XP can support more RAM than the 32-bit versions of these products. When lots of memory is added to a computer, a paging file may not be required. When you use the Pages/sec counter to measure paging file use, the value that is returned may not be accurate. To obtain an accurate measurement of paging file use, you must also use other performance counters. You can use System Monitor measurements to calculate the size of the paging file that your computer requires.

Windows Server 2003 Domain Controllers are not supported without a configured pagefile. Because the algorithm the LSASS database cache depends on the "transition pages repurposed/second" perfmon counter, a pagefile is required to make sure that the database cache is capable to release memory if memory is requested by other services or applications.

INTRODUCTION

When you set up a 64-bit version of Microsoft Windows Server 2003 or Microsoft Windows XP, the operating system will create a page file that is one and a half times the amount of RAM that is installed in your computer. However, as the amount of RAM in a computer increases, the need for a page file decreases. The following guidelines and methods will help you determine the appropriate page file size for your system.

Comparison of memory and CPU limits in the 32-bit and 64-bit versions of Windows

When you set up a 32-bit version or a 64-bit version of Windows Server 2003 or Windows XP, a page file is created that is one and a half times the amount of RAM that is installed in the computer provided there is sufficient free space on the system hard disk. However, as more RAM is added to a computer, the need for a page file decreases. If you have enough RAM installed in your computer, you may not require a page file at all, unless one is required by a specific application.

When no page file exists, or the page file is insufficient, the system reserves some virtual memory in the physical memory for its paging needs.

The following chart illustrates the amount of RAM and the number of CPUs that can be installed on a computer depending on the operating system that is installed. RAM and CPU limits are much larger in 64-bit operating systems than in 32-bit operating systems.

General memory limits	32-bit	64-bit
Total virtual address space	4 gigabytes (GB)	16 terabytes
Virtual address space per 32-bit process	2 GB, 3 GB if the system is booted with the /3GB switch	2 GB, 4 GB if the application is compiled with the /LARGEADDRESSAWARE switch
Virtual address space per 64-bit process	Not applicable	8 terabytes
Paged pool	470 megabytes (MB)	128 GB
Non-paged pool	256 MB	128 GB
System cache	1 GB	1 terabyte

Physical memory and CPU limits	32-bit	64-bit
Windows XP Professional	4 GB / 1-2 CPUs	128 GB / 1-2 CPUs
Windows Server 2003, Standard Edition	4 GB / 1-4 CPUs	32 GB / 1-4 CPUs
Windows Server 2003, Enterprise Edition	32 GB / 1-8 CPUs	1 terabyte / 1-8 CPUs
Windows Server 2003, Datacenter Edition	64 GB / 1-32 CPUs	1 terabyte / 1-64 CPUs
Windows Server 2003 SP1, Enterprise Edition	64 GB / 1-8 CPUs	1 terabyte / 1-8 CPUs
Windows Server 2003 SP1, Datacenter Edition	128 GB / 1-32 CPUs	1 terabyte / 1-64 CPUs

There is no specific recommendation for page file size. Your requirements will be based on the hardware and software that you use and the load that you put on the computer. To monitor page file usage and requirements, run System Monitor, and gather a log during typical usage conditions. Focus on the following counters.

Counter threshold	Suggested value
Memory\\Available Bytes	No less than 4 MB
Memory\\Pages Input/sec	No more than 10 pages
Paging File\\% Usage	No more than 70 percent
Paging File\\% Usage Peak	No more than 70 percent
Process\\Page File Bytes Peak	Not applicable

Note Page file use should be tracked periodically. When you increase the use or the load on the system, you generally increase the demand for virtual address space and page file space.

The Pages/sec counter

When you use System Monitor, the values that are returned by the Pages/sec counter for the Memory performance object may be more than you expect. These values may not be related to either paging file activity or cache activity. Instead, these values may be caused by an application that is sequentially reading a memory-mapped file.

The Pages/sec counter counts the number of pages that are read from the disk or that are written to the disk to resolve memory references to pages. These pages were not in memory at the time of the reference. The Pages/sec value is the sum of the Pages Input/sec and Pages Output/sec counter values. The Pages/sec counter includes paging traffic on behalf of the system cache to access file data for applications.

Pages/sec is the primary counter to watch if you are concerned about excessive memory pressure (thrashing) and the excessive paging that may result.

However, the Pages/sec counter also accounts for other activity, such as the sequential reading of memory-mapped files that are either cached or not. Typically, the Pages/sec counter is counting other activity when you see the following:

•	A high value for the Memory: Pages/sec counter.
•	An average value, relative to the system being monitored, or a high value for the Memory: Available Bytes counter.
•	An average or small value for the Paging File: % Usage counter.
•	For a non-cached memory-mapped file, you also see average or low cache activity. (Low cache activity is also known as cache fault activity.)

Therefore, a high value for the Memory: Pages/sec counter does not necessarily indicate memory pressure or a System Monitor reporting error. To gain an accurate reading of your system, you must also monitor other counters.

How to calculate page file size

Use one or more of the following methods to help you calculate page file size.

Method 1: Use performance logs to understand the paging activity on your computer

1.	Click Start, point to Administrative Tools, and then click Performance.
2.	Expand Performance Logs and Alerts, click Counter Logs, right-click the blank space in the right-pane, and then click New Log Settings.
3.	In the Name box, type a name for the log, and then click OK.
4.	On the General tab, click Add Counters.
5.	Click Use local computer counters.
6.	In the Performance object list, click Paging File.
7.	Click Select counters from list, click % Usage, and then click Add.
8.	In the Performance object list, click Memory.
9.	In Select counters from list, click Available Bytes, and then click Add.
10.	In Select counters from list, click Pages Input/sec, click Add, and then click Close.
11.	Click OK.

Use the log that you collect during typical computer use to understand the paging activity on your computer. Then, adjust the page file size accordingly.

Method 2: Use the Page File Bytes Peak counter to calculate page file size

1.	Click Start, point to Administrative Tools, and then click Performance.
2.	Click System Monitor.
3.	In the right pane, click + (the Add button).
4.	Click Use local computer counters.
5.	In the Performance object list, click Process.
6.	Click Select counters from list, click Page File Bytes Peak, click Add, and then click Close.
7.	Let the counter run during typical use of your computer.
8.	Note the maximum value for the Page File Bytes Peak counter, and then multiply the value by 0.70. The sum of the equation is the size to set for your page file.

Method 3: Calculate the minimum and maximum page file size

To determine the approximate minimum page file that is required by your system, calculate the sum of peak private bytes that are used by each process on the system. Then, subtract the amount of memory on the system.

To determine the approximate maximum page file space that is required for your system, calculate the sum of peak private bytes that are used by each process on the system. Then, add a margin of additional space. Do not subtract the amount of memory on the system. The size of the additional margin can be adjusted based on your confidence in the snapshot data that is used to estimate page file requirements.

Note This estimate is accurate only if the snapshot of data that is used to make the calculations is accurate.

Page file input/output rates

To avoid overloading the system or other disks with page input/output (I/O) activity, use the following guidelines when you set up the page file on your computer:

•

If the page I/O (real disk I/O) rate is more than 10 pages per second, we recommend that you do not put the page file where the I/O activity occurs on the system disk. When the page I/O rate is 10 pages per second or more, we recommend that you dedicate a separate hard disk for paging.

•

If the page I/O rate to a particular disk that is used for paging is more than 60 disk I/O operations per second, use more than one dedicated page hard disk to obtain better performance. To do this, use multiple non-striped disks for paging, or use raid 0 striped disks for paging. Dedicate approximately one I/O hard disk to paging for every 60 pages per second of I/O activity. For example, if a system is averaging 150 pages of I/O activity per second, use three individual hard disks, or a three-disk raid 0 stripe set for the page file. Note These estimates are for hard disks that run at 7200 revolutions per minute (rpm). If you use a hard disk that runs faster, the I/O rate a disk can handle for page I/O will increase. Note If peak performance is critical to your system, use peak I/O rates instead of average I/O rates for these calculations.

Important Supportability Information: This article is specifically for computers that do not need kernel mode or full memory dump analysis. For business-critical servers where business processes require to server to capture physical memory dumps for analysis, the traditional model of the page file should be at least the size of physical ram plus 1 MB, or 1.5 times the default physical RAM. This makes sure that the free disk space of the operating system partition is large enough to hold the OS, hotfixes, installed applications, installed services, a dump file, and the page file. On a server that has 32 GB of memory, drive C may have to be at least 86 GB to 90 GB. This is 32 GB for memory dump, 48 GB for the page file (1.5 times the physical memory), 4 GB for the operating system, and 2 to 4 GB for the applications, the installed services, the temp files, and so on. Remember that a driver or kernel mode service leak could consume all free physical RAM. Therefore, a Windows Server 2003 x64 SP1-based server in 64-bit mode with 32GB of RAM could have a 32 GB kernel memory dump file, where you would expect only a 1 to 2 GB dump file in 32-bit mode. This behavior occurs because of the greatly increased memory pools. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

294418 (http://support.microsoft.com/kb/294418/) Comparison of 32-bit and 64-bit memory architecture for 64-bit editions of Windows XP and Windows Server 2003

MORE INFORMATION

Technical support for Windows x64 editions

Your hardware manufacturer provides technical support and assistance for Microsoft Windows x64 editions. Your hardware manufacturer provides support because a Windows x64 edition was included with your hardware. Your hardware manufacturer might have customized the Windows x64 edition installation with unique components. Unique components might include specific device drivers or might include optional settings to maximize the performance of the hardware. Microsoft will provide reasonable-effort assistance if you need technical help with your Windows x64 edition. However, you might have to contact your manufacturer directly. Your manufacturer is best qualified to support the software that your manufacturer installed on the hardware.

For product information about Microsoft Windows XP Professional x64 Edition, visit the following Microsoft Web site:

http://www.microsoft.com/windowsxp/64bit/default.mspx (http://www.microsoft.com/windowsxp/64bit/default.mspx)

For product information about Microsoft Windows Server 2003 x64 editions, visit the following Microsoft Web site:

http://www.microsoft.com/windowsserver2003/64bit/x64/editions.mspx (http://www.microsoft.com/windowsserver2003/64bit/x64/editions.mspx)

---

APPLIES TO

•	Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems
•	Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
•	Microsoft Windows Server 2003, Standard x64 Edition
•	Microsoft Windows Server 2003, Datacenter x64 Edition
•	Microsoft Windows Server 2003, Enterprise x64 Edition
•	Microsoft Windows XP Professional 64-Bit Edition (Itanium)
•	Microsoft Windows XP Professional x64 Edition

Keywords:

kbhowtomaster kbdiskmemory kbvirtualmem kbtshoot kbinfo KB889654

Copying files on NTFS preserving existing permissions

How are permissions handled when you copy and move files and folders?

By default, an object inherits permissions from its parent object, either at the time of creation or when it is copied or moved to its parent folder. The only exception to this rule occurs when you move an object to a different folder on the same volume. In this case, the original permissions are retained.

Additionally, note the following rules:

•	The Everyone group is granted Allow Full Control permissions to the root of each NTFS drive.
•	Deny permissions always take precedence over Allow permissions.
•	Explicit permissions take precedence over inherited permissions.
•	If NTFS permissions conflict -- for example, if group and user permissions are contradictory -- the most liberal permissions take precedence.
•	Permissions are cumulative.
•	To preserve permissions when files and folders are copied or moved, use the Xcopy.exe utility with the /O or the /X switch. The object’s original permissions will be added to inheritable permissions in the new location.
•	To add an object's original permissions to inheritable permissions when you copy or move an object, use the Xcopy.exe utility with the –O and –X switches.
•	To preserve existing permissions without adding inheritable permissions from the parent folder, use the Robocopy.exe utility, which is available in the Windows 2000 Resource Kit. For additional information about the Windows 2000 Resource Kit, visit the following Microsoft Web site: http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/default.mspx?mfr=true

You can modify how Windows Explorer handles permissions when objects are copied or moved to another NTFS volume. When you copy or move an object to another volume, the object inherits the permissions of its new folder. However, if you want to modify this behavior to preserve the original permissions, modify the registry as follows.

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

1.	Click Start, click Run, type regedit in the Open box, and then press ENTER.
2.	Locate and then click the following registry key: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer
3.	On the Edit menu, click Add Value, and then add the following registry value: Value name: ForceCopyAclwithFile Data type: DWORD Value data: 1
4.	Exit Registry Editor.

You can modify how Windows Explorer handles permissions when objects are moved in the same NTFS volume. As mentioned, when an object is moved within the same volume, the object preserves its permissions by default. However, if you want to modify this behavior so that the object inherits the permissions from the parent folder, modify the registry as follows:

1.	Click Start, click Run, type regedit, and then press ENTER.
2.	Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer
3.	On the Edit menu, click Add Value, and then add the following registry value: Value name: MoveSecurityAttributes Data type: DWORD Value data: 0
4.	Exit Registry Editor.

Note The MoveSecurityAttributes registry value only applies to Windows XP and to Windows Server 2003. The value does not affect Windows 2000.

Symantec Endpoint Protection Client configuration changes for performance optimization

Question/Issue:
My system is running slowly since installation of Symantec Endpoint Protection. How do I configure Symantec Endpoint Protection to alleviate performance issues?


Solution:

Communication between the Endpoint Client and Manager are causing network and server slowdown.

Modify the default communication settings:
1. Click the Clients Tab.
2. Select the client group you would like to modify.
3. Click the Policies tab.
4. If this is not the Global group, uncheck Inherit policies and settings from parent group. Ensure that Policy inheritance is OFF.
5. Under Location-independent Policies and Settings, with in the Settings box, click Communications Settings.
6. In the Download box select Pull mode.
7. Modify the default Heartbeat Interval from "5 minutes" to fit your needs. This modifies how often clients check-in with the manager to receive policies, settings, and content (definition) updates.
8. Click OK to save settings.

Network file sharing is slow or a network-hosted application runs slowly.

Disable Network Drive Scanning:
1. Click the Policies Tab.
2. Click Antivirus and Antispyware.
3. Click the policy you would like to modify and then click Edit the Policy.
4. Click File System Auto-Protect.
5. Under Network Settings, uncheck Network.
6. Click OK.
7. Assign the policy by clicking Assign the Policy, then check each group to which the policy should apply.
8. Click Assign, then click Yes.

All systems in a group run slowly and Endpoint Protection processes are using a abnormally high level of system resources once a week.

Modify the default weekly scan:
1. Click the Policies Tab.
2. Click Antivirus and Antispyware.
3. Click the policy you would like to modify and then click Edit the Policy.
4. Click Administrator-defined Scans.
5. Select Weekly Scheduled Scan and click Edit...
6. Modify this scan so that it will run at the least intrusive time.
*There are no randomization options for this scan so all Endpoint Protection Clients in this group will run the scan at the same time.

The Application event log on the system is filled with tamper protection alerts.

Disable Tamper Protection:
1. Click the Clients Tab.
2. Select the client group you would like to modify.
3. Click the Policies tab.
4. If this is not the Global group, uncheck Inherit policies and settings from parent group. Ensure that Policy inheritance is OFF.
5. Under Location-independent Policies and Settings, with in the Settings box, click General Settings.
6. Click the Tamper Protection tab.
7. Uncheck Protect Symantec security software from being tampered with or shut down.

The system has trouble delivering email. The email server, with the Symantec Endpoint Protection client installed, runs slowly.

Deactivate the email tools on Endpoint Protection Clients within a group:

Part I - Create a custom feature set
1. Click the Admin tab.
2. Click Install Packages.
3. Under View Install Packages, click Client Install Feature Sets.
4. Under Tasks, click Add Client Install Feature Set...
5. Type All except AntiVirus Email Protection in the Name box.
6. Uncheck AntiVirus Email Protection.
7. Click OK. You should see All except AntiVirus Email Protection listed under the default Client Install Feature Sets.

Part II - Assign and deploy the custom feature set
1. Click the Clients Tab.
2. Select the client group you would like to modify.
3. Click the Install Packages tab.
4. Double-click the install package that is currently in use, for example Symantec Endpoint Protection version 11.0.780.1109 for WIN32BIT. If there is no package present in this list click Add Client Install Package, then select the package you would like to use from the drop down menu.
5. Under Client Features select All except AntiVirus Email Protection from the Select the features you want to use: drop-down menu.
6. Click OK.
7. Click the Clients tab. Under the Tasks menu click Run Command on Group and select Update Content.

Note: The above steps can be useful for adding or removing any product feature.


Original Article here

How to create multiple network profiles on Windows XP/2000

While looking for a convenient way to create network profiles, I found the note below on the personal blog of Pat Burm, which you can find here

Original post:

I normally just use DHCP everywhere I connect. But sometimes I need special configs for networks that don’t have a DHCP server running. The problem with those special configs is that they just waste time when you need to go back to the office or your home network. Nothing works and it takes you a few minutes to remember you hosed your network settings to connect to some obscure network somewhere.

In case that link ever dies, the original content follows …

1. First, save your network profile with all you need (ip, subnet, gateway, dns, wins…)
2. Now you can open a DOS shell with start -> run; then type cmd
3. On shell write: netsh -c interface dump > c:/windows/system32/homesettings.txt
   the path is optional, you save this as you want, and also the name of file (homenetwork.txt) can be different.
4. Now you can setup a different netrwok, like the first profile, and repeat the point 3.
5. On you Desktop, in a free area, click on right button of mouse and choose new -> link
6. write: %windir%\system32\netsh.exe -f c:\windows\system32\homesettings.txt
7. Next write the name of link that appear as title of icon, eg: home
8. Repeat the step 6 and 7 for other network, change the name of txt in step six…
9. you are ready, if you want, you can change the two new icons on desktop, with right button, properties, change icon (the default icon file is c:/windows/system32/shell32.dll).

Offering Remote Assistance in Windows XP

How to create an icon on your desktop to launch Offer Remote Assistance in Windows XP

Right click on your desktop
Click on New
Click on Shortcut
Under "Type the location of the item" enter:

hcp://CN=Microsoft%20Corporation,L=Redmond,S=Washington,C=US/Remote%20Assistance/Escalation/Unsolicited/Unsolicitedrcui.htm

Click next
Under "Type a name for this shortcut" enter:

Offer Remote Assistance

Click finish

And that's it. From now on, whenever you'd like to offer remote assistance to any of your users just double click on the newly created icon and enter the appropriate IP address or computer name. Note that you can only do this if you have admin privileges on the remote computer

To launch Offer Remote Assistance from a command line:

"%ProgramFiles%\Internet Explorer\iexplore" hcp://CN=Microsoft%20Corporation,L=Redmond,S=Washington,C=US/Remote%20Assistance/Escalation/Unsolicited/Unsolicitedrcui.htm 

You can also start Remote Assistance from a command line, or shortcut:

%SystemRoot%\System32\rcimlby.exe -LaunchRA

Sysadmin Notes

Notes from a syadmin on windows / linux