The documentation doesn't appear to give this up very easily: to reset to Factury Defaults, you'll need to restart the switch while having a serial console open, and hit CTRL-F (lots of times) until the boot completes, and it drops down to a boot-rom style prompt. One of the options once you see that is "Reset to Factory Defaults?" select that and reboot. At the login prompt the next time, you should get logged in using a username of "admin" with a password of "admin" Good luck from there... Here is my sequence to then add a management IP address to VLAN 1 - the default VLAN:

Console#sh ip interface
 IP address and netmask: 0.0.0.0 255.0.0.0 on VLAN 1,
 and address mode: DHCP.

Console#show vlan
VLAN Type    Name             Status    Ports/Channel groups
---- ------- ---------------- --------- ----------------------------------------
   1  Static      DefaultVlan    Active Eth1/ 1 Eth1/ 2 Eth1/ 3 Eth1/ 4 Eth1/ 5
                                        Eth1/ 6 Eth1/ 7 Eth1/ 8 Eth1/ 9 Eth1/10
                                        Eth1/11 Eth1/12 Eth1/13 Eth1/14 Eth1/15
                                        Eth1/16 Eth1/17 Eth1/18 Eth1/19 Eth1/20
                                        Eth1/21 Eth1/22 Eth1/23 Eth1/24
Console#
Console#configure
Console(config)#interface vlan 1
Console(config-if)#ip address 192.168.3.80 ?
  A.B.C.D  Netmask
Console(config-if)#ip address 192.168.3.80 255.255.255.0
Console(config-if)#?
Configure commands:
  end        Exit from configure mode
  exit       Exit from interface configure mode
  help       Description of the interactive help system
  interface  Into the privileged interface configuration mode
  ip         Internet protocol
  no         Negate a command or set its defaults
Console(config-if)#end

Console#copy running-config startup-config

Console#show ip interface
 IP address and netmask: 192.168.3.80 255.255.255.0 on VLAN 1,
 and address mode: User specified.
Console#
Console#ping 192.168.3.1
Type ESC to abort.
PING to 192.168.3.1, by 5 32-byte payload ICMP packets, timeout is 5 seconds
response time: 10 ms
response time: 10 ms
response time: 10 ms
response time: 10 ms
response time: 10 ms
Ping statistics for 192.168.3.1:
 5 packets transmitted, 5 packets received (100%), 0 packets lost (0%)
Approximate round trip times:
 Minimum = 10 ms, Maximum = 10 ms, Average = 10 ms
Console#

The Twitter module for Drupal now needs to use the new OAuth module for authentication in Twitter.  This has broken many web sites.  I use this feature on this site to automatically post a tweet whenever I add a new blog entry.  I use a global account in Drupal to do it, rather than individual Twitter accounts for each drupal user. In order to get the Twitter module to work now, you'll need to do the following things (note that this sequence is for a single global Twitter account for all users wanting to have their tweets posted by the Twitter Module)

Steps to take:

1. Upgrade the Twitter Module from 6.x-2.6 to 6.x-3.0-beta2 or better
2. Install OAuth 2.0 (OAuth 3.0 doesn't work with Twitter 6.x-3.0-beta2) - in the drupal Oauth settings be sure to set OAuth cryptography as "HMAC-SHA1" and not Plain Text or RSA.
3. As ADMIN (User 1) Run update.php -> this will update the database to support the new version of the twitter module
4. Register your application with twitter: In your Twitter application settings ensure you have "Application Type" set as Browser and the "Callback URL" should be http://yoursite.com/twitter/oauth
5. Set up the Twitter Module on your website (at http://www.yoursite.com/admin/settings/twitter ) to use the registered Consumer Tokens: "Consumer Key" & "Consumer Secret"
6. Login as the admin user whose twitter account has been setup
7. Go to My accounts -> Edit -> Twitter Accounts (click on the "Make Global" link to the right for the global user you assign)

You should now be able to post to twitter using OAuth. Twitter should also show that the tweet has been made from the global Twitter user.

This looks really cool:
http://scopeport.org/

ScopePort

ScopePort offers a lot of features that may revolutionize your server monitoring and management. You can control everything over the web interface. No need to touch any configuration files after the quick initial installation.

Easy to configure

You usually only touch one configuration file per client. After that first configuration of a few parameters you can do everything using the web interface. This will keep your running costs low! Add a new host or service to monitor in just a few minutes

TLS encrypted communication of clients and server

The ScopePort client is encrypting all health values of the host before sending by default. This allows you to monitor your servers over public networks!

Profile data

ScopePort collects hardware information of clients (e.g. Hostname, Harddisk models, total amount of RAM or CPU model) so that even the hardware profiles of your hosts are filled out automatically. You get an automatically updated server database!

Service checks

Monitor service and their response times on any reachable host without installing anything on it. Example: Check port 80 on example.org for HTTP protocol and get warned if the response time climbs over a defined maximum or the service is not reachable anymore.

Notification methods

Email, XMPP/Jabber or SMS notification of groups of persons if some server or service has failed. You can also use the Clickatell SMS API if you don't have your own SMS gateway.

Integrated host and alarm management

Add comments or tasks for hosts. Comment triggered alarms and acknowledge them. Coordinate all your work via the web interface!

ScopePort Headquarters

ScopePort Headquarters is a dedicated Ruby On Rails application that connects to your ScopePort Web Interface and allows you to build your own overview screen. (Those that look so cool that you place them flashy in the IT office). You can design the screen for yourself: Every element is movable.

ScopePort proxy

The ScopePort proxy can collect data of multiple hosts (e.g. in one data center) and redirect it to the ScopePort server. You only need to allow the connection to the ScopePort server from one host.

Downtimes

Schedule downtimes for hosts or services. Because you don't want to get notified if a host goes down for a scheduled downtime.

Integrated emergency management

You can declare emergencies and have a dedicated web interface page per emergency that coordinates the emergency recovery.

ScopePort health

The health of all ScopePort Server and Proxy processes is visible in the web interface.

From: http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/1999121717035848

Message: "Scan stopped by user" when launching a manual scan

Question/Issue:
You start a manual scan in Symantec AntiVirus (SAV) or in the Symantec System Center, and then you see the message "Scan stopped by user." Scans will not complete.

Cause:
Low disk space; low resources.


Solution:

---

Before you begin:

In early May, 2010, this error message has been reported on systems that are still running builds of Symantec Antivirus that are no longer supported (versions 8.x, 9.x). It is strongly recommended that users migrate up to a supported build to resolve this error message.

This problem can also happen when Symantec AntiVirus 10.x or Symantec Client Security 3.x is installed on the same computer as APC PowerChute 6.x or earlier.
For details, read the document Various problems occur with Symantec AntiVirus and APC PowerChute 6.x.

---

This problem has more than one cause, so more than one solution is provided. To fix the problem, try each of the following solutions in the order that they appear.

To correct the problem

1. Delete all temporary files on the system.
2. Verify that the computer has a valid directory specified for the TEMP variable.
   1. Open a Command Prompt.
   2. Type set and then press Enter.
   3. The TEMP= line indicates the path to the TEMP folder. Make sure that a folder exists at this path.
3. Verify the amount of free space on the drive. A rule of thumb is to have at least 200 MB or 10% of the drive available as free space.
4. After removing temporary files, defragment the drive.
5. Create a permanent swap file to improve the performance.
6. Restart the computer.

Some customers reported that disabling boot sector scanning eliminates the scan failure.

---

WARNING: In the following procedure you will modify the Windows registry. We strongly recommend that you back up the system registry before you make any changes. Incorrect changes to the registry could result in permanent data loss or corrupted files. Modify only the keys that are specified. See the document How to back up the Windows registry before proceeding.

---

To modify boot sector scan policy in the registry

1. Open the Registry Editor, and then go to the following key:
   
   HKEY_LOCAL_MACHINE\SOFTWARE\INTEL\LANDesk\VirusProtect6\CurrentVersion\LocalScans\ManualScan
   
2. Set the ScanBootSector value to 0
3. For scheduled scans on Norton AntiVirus Corporate Edition servers or clients, configured using the local GUI, set the ScanBootSector value in the right pane to 0 for the following registry keys:
   
   HKEY_USERS\.DEFAULT\Software\INTEL\LANDesk\VirusProtect6\CurrentVersion\Custom Tasks\Default\BootScan
   HKEY_USERS\.DEFAULT\Software\INTEL\LANDesk\VirusProtect6\CurrentVersion\Custom Tasks\Default Scan Options
   

---

Note: An alternative on Norton AntiVirus Corporate Edition clients is to set the ScanBootSector value for the following keys to 0. The HKEY_USERS... will automatically update.

HKEY_CURRENT_USER\Software\INTEL\LANDesk\VirusProtect6\CurrentVersion\Custom Tasks\BootScan
HKEY_CURRENT_USER\Software\INTEL\LANDesk\VirusProtect6\CurrentVersion\Custom Tasks\Default Scan Options

This command will give you all of the known info regarding the processor(s) under linux:

# less /proc/cpuinfo

Configuring DHCP address for your network card

If you want to configure DHCP address you need to edit the /etc/network/interfaces and you need to enter the following lines replace eth0 with your network interface card

sudo vi /etc/network/interfaces

# The primary network interface: DHCP address assignment
auto eth0
iface eth0 inet dhcp

Configuring Static IP address for your network card

If you want to configure Static IP address you need to edit the /etc/network/interfaces and you need to enter the following lines replace eth0 with your network interface card

sudo vi /etc/network/interfaces

# The primary network interface
auto eth0
iface eth0 inet static
address 192.168.88.8
gateway 192.168.88.1
netmask 255.255.255.0
network 192.168.88.0
broadcast 192.168.88.255

After entering all the details you need to restart networking services using the following command

sudo /etc/init.d/networking restart

Secondary IP addresses or Virtual IP address in Ubuntu/Debian Linux

Sometimes it is useful to have a secondary IP address on Ubuntu. To do this at the command line, you need to edit /etc/network/interfaces file and add the following entries:

sudo vi /etc/network/interfaces

auto eth0:1
iface eth0:1 inet static
address 192.168.77.7
netmask 255.255.255.0
network 192.168.77.0
broadcast 192.168.77.255
gateway 192.168.77.1

To stop the GUI:

Code: The easist way is to open a terminal and execute these commands:

sudo /etc/init.d/gdm stop

And then ctrl+alt+backspace to end your current session

To restart the GUI:

sudo /etc/init.d/gdm start

If you have hung print jobs in Windows 7 or Vista, you can clear the print queue easily by using these steps.

1. Click Start.

2. Type Command.

3. Right-click Command Prompt and select Run as administrator.

4. Type net stop spooler then press Enter.

5. Type del %systemroot%\System32\spool\printers\* /Q then press Enter.

6. Type net start spooler then press Enter.

The print queue on your Windows 7/Vista system should now be cleared. Type exit and press Enter to exit the command window.

Those out there that use(ed) Outlook Express should know that there is no such thing in Windows 7. Also true in Vista, where "Windows Mail" was released. Yet another major change for Windows 7: the new (free) email client is called "Windows Live Mail" and the most annoying new "Feature" is the missing menus. To see the old menu you are looking for; hit the "ALT" key by itself. Then, the menu will magically appear. Mystery solved!

See the entire document (Table of Contents) here: http://www.opalsoft.net/qos/CDS.htm