Category Archives: Windows SharePoint WSS

Using a Lantronix MSS100 to check the status of a switch console port

Understanding the Lantronix MSS100

Lantronix Components

The MSS can be used to start outbound Ethernet connections to hosts on TCP/IP, IPX/SPX and LAT networks. It can also provide interactive access to a device connected to its serial port.

The MSS has three components.

  • The Power cord
  • A typical Ethernet cord
  • A serial cable: one end being “DB 25 female”, the other end being “DB 9 female”.

Setting up your Lantronix MSS100

  1. If you have any questions about these settings you can find the user guide download here MSS100 guide.
  2. Install puTTY from here; puTTY downloads.
  3. Assuming that you haven’t assigned an IP address, follow these steps to do so.
  4. Connect the serial port from your MSS100 to the back of your computer. Also, connect the MSS100 to your network with an Ethernet cord.
  5. Open “Putty” and click on the “Serial” button and hit enter.
  6. This will open a putty session to the MSS. You should see a login prompt similar to the image below.
  7. Type the command “SET PRIVILEGED”. For the password use the default password which is “system”.
  8. Type in the command
    “CHANGE IPADDRESS <IpAddressHere>”.
    Note: Ensure that nothing else on your network has the same IP address or you will possibly knock it offline!
  9. Next we will want to configure the MSS’s subnet mask and domain. Type in the commands
    “CHANGE SUBNET MASK <YourSubnetMask>”
    “CHANGE DOMAIN <YourDomian>”
  10. Next we want to change the gateway that the MSS will use. Type in the command
    “CHANGE GATEWAY <YourGateway>”
  11. At this point we want to control incoming logins to the MSS. I want to allow only Telnet logins and disable “LAT” logins. Type in the commands:
  12. To add a bit more security to the MSS, I am going to require a password at login. Type the command:
  13.  Next disable the IPX Parameter, with this command:
  14. Here is a list of recommended settings for the MSS100.
    All the commands (SET PRIVILEGED must be done first for these to work):
    CHANGE IPADDRESS <IpAddressHere>
    CHANGE SUBNET MASK <YourSubnetMask>
    CHANGE DOMAIN <YourDomian>
    CHANGE GATEWAY <YourGateway>
    CHANGE CHARSIZE <# of bits>
  15. Note: To see the changes you have made use the command:
  16. Note: If you need the 'break' key to send out through the serial port to a connected device, you must run the command:
  17. Note: If the connection doesn't work, it's worth adding a null modem adapter during diagnosis, this is a common problem.  

Testing the MSS100

A managed switch provides a good opportunity to test the MSS100 serial connectivity.

  1. Connect the MSS100 to your network via Ethernet.
  2. Connect a serial cable (DB 9) to the testing switch, and connect the other end to the MSS (DB 25).
  3. Connect Power to the MSS.
  4. When everything is hooked up correctly it should look something like this.

Connecting to the MSS100 Serial Port via IP

  1. Open puTTY.
  2. Under Host Name, enter the IP Address of the MSS.
  3. We will be preforming a “Telnet” connection, change the “Port” to 2001. Your settings should look similar to the image below.
  4. When you have achieved a successful connection, putty will open a cmd that looks something like this depending on your test switch.
Side Note: If you liked/disliked this blog please leave a comment! I want to know what you think!
Leave a comment

Posted by on November 14, 2011 in Windows SharePoint WSS


Exporting and Importing sites between WSS 3 and SharePoint Foundation 2010.

Exporting and Importing sites between WSS 3 and SharePoint Foundation 2010.

I was recently tasked with moving a list from a WSS3 server to a SharePoint Foundation 2010 server. After Googling around, I tried exporting the list as a template in WSS3, then importing the template into Foundation. However, I quickly learned that SharePoint Foundation cannot import WSS3 list templates. There didn’t seem to be a way to ‘update’ the WSS3 list template to Foundation; dead-end. To get around this limitation, I backed up the entire WSS3 site and performed a ‘database attach upgrade’ to a new temporary Sharepoint Foundation server, then transferred the list as a template.

Basic Process:

  1. Backup the SP_WSS3 database
  2. Restore it to a temporary SP_2010 server (SP_2010Temp)
  3. Copy the list (as a template) from the temporary server to your production SP_Foundation server

Things to note:

  • The Two SharePoint servers we are using are Windows Sharepoint Services 3.0  and SharePoint Foundation 2010
  • For reference, here are my version numbers:
    SP_WSS3′s version is:, SP
    SP_2010’s version is: 14.0.4762.1000, SP2010 RTM
  • SP_2010Temp’s version will be the same as SP_2010

Setting up your new SP_2010Temp site:

Note: I referenced this blog for lots of this information Installing a Standalone Sharepoint Foundation 2010 Server. However, we’re not going to complete every step because we shouldn’t need SSL for this temporary SharePoint Foundation server.

The basic outline:

  1. Install SQL Server 2008 R2 Express
  2. Download SharePoint Foundation. You do not need Search server Express
  3. Follow Prepare your system
  4. Install SharePoint Prerequisites
  5. Install SharePoint Foundation 2010
  6. Follow the Intial Configuration Wizard
  7. Follow Create Site Collection
  8. Ignore everything else!

To upgrade the actual WSS 3 content to SP2010, we will use the “database attach upgrade” method. See this blog post for more info: WSS3.0 to SharePoint Foundation 2010 upgrade

Backing up the WSS 3 Content Database:

  1. On your  SP_WSS3 server, Open SQL Server Management Studio and connect.
  2. Expand Databases, than right click WSS_Content -> tasks -> Back Up…
  3. When the back up window opens, set your destination to: “disk” then click “Add”.
  4. In the next menu, Choose a location , and give the backup a name.
  5. Now on your SP_2010Temp server, open SQL Server Management Studio
  6. Expand the databases, right click on the database you want to restore to. This database will be similar to the filename that you just backed up (e.g. WSS_Content_1)
  7. Right click on the database -> tasks -> Restore -> database
  8. In this Menu, check that the Destination for restore is the database you just backed up from SP_WSS3, Under “Source for restore” choose “From device”, then click the “…” button, This will open another menu prompting for you to choose your backup file, find the backup file of the WSS_Content and click ok.
  9. After you choose the backup file, you will notice that the selected backup file is now under your “Source for restore”, make sure its checked and proceed to the next step
  10. Open options and check “Overwrite”
  11. Click ok and you should get a message saying “The Restore of <database> completed successfully.”
  12. Login to SP_2010New’s central administration website.
  13. Go to “Manage Content Databases”
  14. If there is a database there, delete it, ignore the pop up
  15. The last step: We are going to add our new database to the SP_2010New’s Farm using this command, we should be still Remote desktop to SP_2010New
    cd “<programfiles>\common files\microsoft shared\web service extensions\14\bin”
    stsadm -o addcontentdb -url <URL> -databasename <database name>
  16. This will upgrade your database to 2010 format at the same time
  17. Navigate to the Central admin site for SP_2010New, the new database should be under “Manage Content Databases”
  18. Your Done!
    The two websites should look similar becuase we havent done a visual upgrade, you can see simularities in the menus and how the is website setup.
Side Note: If you liked/disliked this blog please leave a comment! I want to know what you think!

Tags: , , ,