Quick way to Remote reboot PC's

if you need to quickly reboot remote PC's on your network use the following from the command prompt
shutdown /i

This pulls up an easy to use GUI where you can add in any PC on your network

SharePoint Designer Server error: There is no Web named " ".

This issue happens if you try to remove FP2000 Extensions from a Virtual Directory from the IIS server

discovered in IIS 5.0 XP version.
I experienced this issue with one directory, while all the others worked just fine. The strange part was that I was able to open the subdirectories of the failing directory. With this in mind, I made a new directory and began copying separate files to the new folder. After a few files, I tried to open it with SharePoint Designer and this was always succesfull. When I copied one of the last folders - which was a hidden folder - I got the error again! From that moment I knew what the cause of the problem was.
When using SharePoint Designer to open a site directly from it's directory (like E:\site\ ) via the "Open Site" button, it is possible to receive the above error.

Solution to solve the error:

It is the hidden folder "_vti_pvt".

Delete the folder and all its contents everything will open like it should.

Issues might arise with FP extensions if files were in the folder but you should be able to recreate it if needed

Changing RDP Listening Port

If you need to access Multiple Windows machines from other locations outside your firewall


To Alter the Port on the Client Side

SUMMARY

By default Terminal Server and Windows 2000 Terminal Services uses TCP port 3389 for client connections. Microsoft does not recommend that this value be changed. However, if it becomes necessary to change this port, follow these instructions.

MORE INFORMATION

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 How to back up and restore the registry in Windows

To change the default port for all new connections created on the Terminal Server:

1.Run Regedt32 and go to this key:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp

NOTE: The above registry key is one path; it has been wrapped for readability.

2.Find the "PortNumber" subkey and notice the value of 00000D3D, hex for (3389). Modify the port number in Hex and save the new value.

To change the port for a specific connection on the Terminal Server:

•Run Regedt32 and go to this key:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\WinStations\connection

NOTE: The above registry key is one path; it has been wrapped for readability.

3.Find the "PortNumber" subkey and notice the value of 00000D3D, hex for (3389). Modify the port number in Hex and save the new value.

NOTE: Because the use of alternate ports has not been fully implemented for Terminal Server 4.0, support will be provided as "reasonable effort" only, and Microsoft may require you to set the port back to 3389, if any problems occur.


Back to the top

To Alter the Port on the Client Side

1.Open Client Connection Manager.

2.On the File menu, click New Connection, and then create the new connection. After running the wizard, you should have a new connection listed there.

3.Making sure that the new connection is highlighted, on the File menu, click Export. Save it as name.cns.

4.Edit the .cns file using Notepad changing "Server Port=3389" to "Server Port=xxxx" where xxxx is the new port that you specified on Terminal Server.

5.Now import the file back into Client Connection Manager. You may be prompted to overwrite the current one, if it has the same name. Go ahead and overwrite it. You now have a client that has the correct port settings to match your change Terminal Server settings.

NOTE The Windows 2000 Terminal Server ActiveX client connects only to TCP port 3389. This configuration cannot be changed. The Terminal Server ActiveX client that is available in Microsoft Windows XP and in Microsoft Windows Server 2003 supports the ability to modify the port settings. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

326945 How to change the listening port in the Windows Terminal Server Web client


http://support.microsoft.com/kb/187623