Useful freeware & sites

FREEWARE

Screenshot pilot
PDFcreator
Freeundelete


------
FREE SITES

Mail server, blacklist etc checks
www.mxtools.com

Share local and domain user profile & cannot load error

To share local and domain user profiles:
Log in once as each so registry hives have been created. If both are local admins, no additional file permission need to be given, if not, grant full access to respective documents and settings folder.

in regedit; find HKLM\software\microsoft\currentcontrolset\profilelist\xxxxxxxxx look for profile path and set both to have the same one.

done.

if log out from one and can't log in as the other, being prompted cannot log profile. Registry hive has problem being freed up, a bug in Windows, can download hotfix. Or just restart and log in as the other user.

Client rejected the Link error in Netsupport Manager

After careful observation of the support tool information, we have identified that the following error message "Client rejected the Link" that you encountered is due to the fact the Client Machine has a Security Key setup whereas the Control Machine does not have one.

Therefore, in order to resolve this issue you will need to carry-out 1 of the following options below:

Option 1
Because a Security Key has been setup on the Client's Machine you will need ensure that the Control Machine has the same Security key as the Client in order to Connect to the client. If you know the Security Key details on the Clients Machine then follow the steps below to setup the same Security Key on the Control's Machine:

1. Launch your NetSupport Manager
2. From the Menu-bar at the top - Please select {Network}
3. From the drop down list click on {Configure...}
4. Next click on the plus symbol next to {Security} then {Settings}
5. On the right you will see the Security Key Option. Please click on "Set" button and entered the key here that matches the security key on the Client, otherwise if you do not enter the Security Key you will be denied access to the Client Machine.

Option 2
As an alternative option the Security key Configuration can be removed if you have administrator rights. Therefore, in order to remove the Security Key please follow the steps below:

1. Click on {Start} then {Programs}
2. From the Programs drop down list select {NetSupport} then {NetSupport Configurator}
3. When the NetSupport Client Configurator Dialog Window appears click {Advanced} then {Master Profile}
4. When Master Profile Window Opens up Click on the plus symbol next to {Security} then from the drop down list click on {Connect}.
5. On the Right Hand Side you will see the Security key section, Please click on the "Set" button and when the Security Window appears remove the Security key that has been entered.
6. Once the Security key is removed click on the OK button, and OK again and when the NSM Client Configurator appears click on the Save icon button.

If you have any further inquiries regarding our software please do not hesitate to contact us anytime at the following email address: support@netsupportsoftware.com







Regards,
Michael Schawsmidth

NetSupport Technical Support
Support@netsupportSoftware.com
NetSupport Limited
Tel: +44 (0)1778 382272 Fax: +44 (0)1778 382290
Email Disclaimer: The information in this email is intended only for the addressee named above. Access to this email by anyone else is unauthorised. As this email may contain confidential or privileged information, if you are not the intended recipient any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any opinions or statements contained within this email are expressly those of the individual and not necessarily those of NetSupport Group.

________________________________________________________________________
This e-mail has been scanned for all viruses by MessageLabs.
________________________________________________________________________

hotfix is available to modify the way that Exchange Server 2003 handles a disabled Active Directory user account that is associated with an Exchange S

hotfix is available to modify the way that Exchange Server 2003 handles a disabled Active Directory user account that is associated with an Exchange Server 2003 mailbox

http://support.microsoft.com/default.aspx?scid=kb;EN-US;903158

Terminal services BEST practice

http://technet2.microsoft.com/WindowsServer/en/library/d0aa8673-cc55-4c70-a540-49fbc106834b1033.mspx?mfr=true

Terminal Server Best practices
Updated: January 21, 2005

 
Best practices
•

Install Terminal Server on a standalone server and not on a domain controller.

Installing Terminal Server on a domain controller can affect the performance of the server because of the additional memory, network traffic, and processor time required to perform the tasks of a domain controller in a domain.
•

Install Terminal Server on an NTFS file system partition.

NTFS provides greater security for users in a multisession environment who access the same data structures.
•

When shutting down a terminal server, use the tsshutdn command instead of the Shut Down option on the Start menu. This will shut down the server in a controlled manner. The Shut Down option on the Start menu does not notify users before ending user sessions and is not recommended. Ending a user's session without warning can result in loss of data at the client. For more information about using tsshutdn, see Tsshutdn.
•

Back up your license server regularly.

Backing up your license server regularly protects data from accidental loss due to hardware or storage failure. Create a duplicate copy of the data on your hard disk and then archive the data on another storage device such as a removable disk or tape. In the event that the original data on your hard disk is accidentally erased or overwritten, or becomes inaccessible because of a hard disk failure, you can easily restore the data from the archived copy.
Top of pageTop of page
Program installation
•

Use Add or Remove Programs in Control Panel to install applications on the terminal server. Using this method, you can install programs for multisession use. For more information about installing applications on a terminal server, see Starting the installation.
•

After you install Terminal Server, do not use Add or Remove Programs to switch Terminal Server on and off.

Terminal Server installs programs for use in a multisession environment. Programs that were installed while Terminal Server was installed might not work correctly when Terminal Server is uninstalled. Instead, reinstall all programs for use without Terminal Server if you decide to remove the component.
•

Check for application compatibility scripts before installing programs for use with Terminal Server.

Many commonly used programs have been tested for compatibility. Some programs require minor changes to the installation. Scripts are available for these programs and must be run after the program installation is complete. Scripts are located in the systemroot in \Application Compatibility Scripts\Install.
Top of pageTop of page
Configuring Terminal Services
•

Use Terminal Services Group Policy to configure one or more terminal servers, or to manage Terminal Server user settings. Terminal Server Group Policies can be applied on individual computers or on groups of computers belonging to a single organizational unit.
Managing users
•

Use Terminal Services-specific groups

Create User Groups that are specifically for Terminal Services users. Maintaining users through groups is much easier and less time consuming than managing users individually.

Windows Server 2003 family server operating systems contain a default User group called Remote Desktop Users, which has been specifically created to manage Terminal Server users. This group is not populated by default. You must add users to the Remote Desktop Users group if you want them to be able to establish remote connections.
•

Use Terminal Services-specific profiles

Assign a separate profile for logging onto Terminal Services. Many of the common options that are stored in profiles, such as screen savers and animated menu affects, are not desirable when using Terminal Services. Assigning a specific profile allows users to get the most out of the system they are using without expending additional server resources. For information about assigning a Terminal Services specific profile, see Change a user's Terminal Services profile path.
•

Use mandatory profiles

Use a mandatory Terminal Services profile that is created to suit the needs of all of the different types of clients and that provides the best server performance. Be aware that 16-bit computers and Windows-based terminals might not support some screen resolutions.
•

Set time limits

Setting limits on the duration of client connections can improve server performance. You can set the limits on how long a session lasts, how long a disconnected session is allowed to remain active on the server, and the time allowed for a session to remain connected, yet idle. For information about setting session limits, see Configuring session limits.
•

Use the Starting program option

If you have users who need access to only one application on the terminal server, use the Starting program option to restrict users to that application. For more information, see Specify a program to start on session connection.
•

Create preconfigured connection files for users or groups of users

To make connecting to Terminal Services easier, you can supply users with preconfigured connection files. Collections of connection files can also be made either for different departments within your organization or for different job titles. preconfigured connection files are created using Remote Desktop Connection. For more information, see Managing Terminal Services connection files.

Sharing profiles between local and AD domain accounts (XP tested)

http://www.jsifaq.com/SF/Tips/Tip.aspx?id=2240

To create a local account that shares your domain profile:

01. Log on as the local Administrator and create a local account with the same UserName as your domain account.

NOTE: Your PC can not be a domain controller.

02. Logon as this new account and logoff.

03. Logon as your domain account.

04. Use Regedt32 and select the HKEY_CURRENT_USER key.

05. On the Security menu, press Permissions.

06. Press the Add button.

07. In the Look in: box, toggle your local computer name. Select the new UserName account you created in step 01.

08. Press Add and then press OK.

09. On the Security tab, select the new ComputerName\UserName account and check both Read and Full Control.

10. Press the Advanced button and check both boxes at the bottom of the Permissions tab.

11. Press Apply and Press OK until all dialog boxes are closed.

12. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList

and locate the new SID by inspecting each ProfileImagePath for \Documents and Settings\UserName.ComputerName.

13. Double click this ProfileImagePath and remove the .ComputerName, so it is equal to your domain profile.

14. Exit Regedt32.

15. Delete the \Documents and Settings\UserName.ComputerName folder.

16. Grant the local UserName full control on the \Documents and Settings\UserName folder / sub-folders.

17. Logoff and logon locally as UserName. You will see your domain (and local) profile.

Sharing profiles between local and AD domain accounts (XP tested)

http://www.jsifaq.com/SF/Tips/Tip.aspx?id=2240

To create a local account that shares your domain profile:

01. Log on as the local Administrator and create a local account with the same UserName as your domain account.

NOTE: Your PC can not be a domain controller.

02. Logon as this new account and logoff.

03. Logon as your domain account.

04. Use Regedt32 and select the HKEY_CURRENT_USER key.

05. On the Security menu, press Permissions.

06. Press the Add button.

07. In the Look in: box, toggle your local computer name. Select the new UserName account you created in step 01.

08. Press Add and then press OK.

09. On the Security tab, select the new ComputerName\UserName account and check both Read and Full Control.

10. Press the Advanced button and check both boxes at the bottom of the Permissions tab.

11. Press Apply and Press OK until all dialog boxes are closed.

12. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList

and locate the new SID by inspecting each ProfileImagePath for \Documents and Settings\UserName.ComputerName.

13. Double click this ProfileImagePath and remove the .ComputerName, so it is equal to your domain profile.

14. Exit Regedt32.

15. Delete the \Documents and Settings\UserName.ComputerName folder.

16. Grant the local UserName full control on the \Documents and Settings\UserName folder / sub-folders.

17. Logoff and logon locally as UserName. You will see your domain (and local) profile.

HP warranty lookup

http://h20000.www2.hp.com/bizsupport/TechSupport/WarrantyLookup.jsp?lang=en&cc=us&prodSeriesId=472277&prodTypeId=12454

SNMP trap configuration

To configure agent properties

1.	Open Computer Management
2.	In the console tree, click Services. Where? Services and Applications > Services
3.	In the details pane, click SNMP Service.
4.	On the Action menu, click Properties.
5.	On the Agent tab, in Contact, type the name of the user or administrator for this computer.
6.	In Location, type the physical location of the computer or the contact.
7.	Under Service, select the appropriate check boxes for this computer, and then click OK.