15 Oct 2010

Move WSS3.0 from one to another server

Move WSS3.0 from one to another server

Configuration:

Source: SQL 2000 Std Server SP4+Win 2003 Server SP+WSS3.0
Destination: SQL 2005 Std Server+Win 2003 Server SP2 +WSS3.0

STEP1: BACKUP:

1. On Source SQL Server: Backup SharePoint Content databases.

Open SQL Server Enterprise manger
Right Click a database (For ex: WSS_Content)->All Tasks->;Backup Database->Database Complete->Backup to disk->Add->Filename->Provide a path &; filename->Ok->Ok
Repeat above procedure for all SharePoint databases (Sharepoint_AdminContent_xxx, Sharepoint_Config) however we will not restore all of them.
(Do not restore database Sharepoint_AdminContent_xxx, Sharepoint_Config on new SQL Server)

How to find name of Content databases:
Central Admin->Application Management->Content databases->Select web application from Right Hand Side Top drop down list. Database name will be displayed

-------------

2. On SharePoint Server: Take screenshots of all configured setting on Central administration page

Central Admin->Operations->Global Configuration->Alternate access mappings
Central Admin->Operations->Outgoing email settings
Central admin->Application management->Define managed paths
etc.

--------------

STEP 2: PREPARE DESTINATION SQL SERVER

We must install either same or later version than source SQL Server
Open SQL Server Enterprise manger
Security->Logins->Right Click->New Login
Add SharePoint Service Account in Domain\user format
This account must be either Domain admin or Domain user with Local admin rights on SharePoint server.
Security->Logins->Right Click Service Account->Properties->Server Roles Tab
Check Security Administrators & Database Creators
Click Ok

STEP 3: RESTORE CONTENT DATABASE TO DESTINATION SERVER

Copy backup Content database files to Destination SQL Server
Open SQL Server Enterprise manger
Databases->Right Click->All Tasks->Restore database->Restore as Database->Type name of Content Database->From device->Select device->disk->Add->Browse to backup files->Ok->Ok
Similarly restore all Content databases from backup
Security->Logins->Service Account->Database Access Tab->In upper pane select Content database->In lower pane check DB_OWNER checkbox->Click Ok

Pls noted that the restore process may take hours to complete depends on database size and how powerful your SQL server is. Mine is Proliant ML370G5 Quad Core Xeon, 4GB RAM takes 4 hours to restore 10GB database :-(

STEP 4: INSTALL WSS ON NEW SERVER
Install WSS3.0 on new server

STEP 5: CONNECT TO NEW SQL SERVER

Run SharePoint Products and Technologies Configuration (PSCONFIG ) Wizard
Select No, I want to create a new server farm
Database Server: Give Destination SQL Server name (same sql server name or instance as in step 2)
Database Name: Type new Config Database Name
Username: Use same Service account as used in existing old server
Password: Password for that account
We should get configuration successful message.
After PSCONFIG finishes successfully Central admin page will open automatically.

STEP 6: RESTORING SITES FROM DATABASES

Create a new web application http://app on port 80 with content database name WSS_Content_TEST

Go to V3 Central Administration Page->Application Management->Create or extend Web Application
Click on Create a new web application
Choose any unused port number
Enter Database Server Name and enter Database name as WSS_Content_TEST
Wait for operation to complete
After application is created create a site collection
Fill the details and select Team site template click Ok
Browse to test site http://app
Check if it is working

To remove dummy_content_db (WSS_Content_TEST) from a web application

Click on Content Databases
On right hand side select the newly created web application if not already present
Click on Database name WSS_Content_TEST
Check remove content database checkbox and click OK

To attach restored content database to a new web application:

Go to V3 Central Administration Page->Application Management->Sharepoint Web Application management->Content Databases->Add a content database->Enter database server and database name (WSS_Content)-> Click OK

Now browse to http://app and check if it is working
Similarly add content databases for other web applications.

NOTE:
=====
Do NOT discard Source SQL Server and Databases until the functionality of New SQL Server and WSS3.0 is tested and confirmed.

12 Oct 2010

Copy A WSS 3.0 Site to Another

This is a method I use for small business customers to provide them with a 'sandbox' environment they can play in. But this applies to you as well.

Your 'Production' environment would be the old site/server, the 'sandbox' site would be your new server/site -- http://blog.brainlitter.com/archive/2009/03/09/how-to-refresh-a-sharepoint-sandbox-collection-with-production.aspx

However, if you aren't moving a whole site collection, here's your solution for moving just a subsite with all the various bits and bobs (there are other methods like save site as template, etc. but they have severe limitations, like 10MB, etc.) http://blog.brainlitter.com/archive/2009/05/10/save-sharepoint-list-as-template-with-content-maxes-out-at-10mb-%e2%80%93-but-i-want-more%e2%80%a6.aspx

~~~~~~~~~~~~~~~~~~~~~~~~

How to Refresh a SharePoint Sandbox Collection with Production

This guide has been created to provide the necessary steps to 'refresh' a Sandbox Collection (Different Web Application) with Production Data, so that it can be 'played with' without breaking the Production Implementation.

Note on Authentication/Permissions: Ensure you perform these tasks with an account that has full SharePoint Administrative privileges such as an 'SPSAdmin' account.

First, determine the Web Applications for the Source (Production) Web Application/Site Collection and the Destination (Sandbox) Web Application/Site Collection.
- Open Central Administration and choose the "Application Management" tab
- Open the Web Application List
- Make note of the URL's
- Document the URL's in the table below

	Application URL	Collection Description
Source	http://harvey:56000	Production Portal
Destination	http://harvey:56001	Sandbox

Perform a current Backup of the Production Site Collection
- Go to a DOS Prompt and if the path to the STSADM.EXE application is not already in your System Path (a good idea for convenience), then change to the appropriate directory in order to run the utility.
  - cd %COMMONPROGRAMFILES%\Microsoft shared\Web server extensions\12\Bin
- Perform the following command, using the URL of the SourceD:\TOP\ProductionToSandBoxTransfer\March-3-2009-Backup.bak Collection and modify your Output destination of the backup file, to suit (in this example, the path is going to be
  - stsadm -o backup -url http://harvey:56000 -filename D:\TOP\ProductionToSandBoxTransfer\March-3-2009-Backup.bak
- Ensure the backup completed successfully. Your result should look something like this:
Restore your latest backup over your existing Sandbox Web Application (the assumption is you have one in place already), being sure to use the -overwrite option. Note that the restore typically takes much longer than the backup, to complete.
- Go to a DOS Prompt (if you aren't there already) and if the path to the STSADM.EXE application is not already in your System Path (a good idea for convenience), then change to the appropriate directory in order to run the utility.
  - cd %COMMONPROGRAMFILES%\Microsoft shared\Web server extensions\12\Bin
- Perform the following command, using the URL of the DestinationD:\TOP\ProductionToSandBoxTransfer\March-3-2009-Backup.bak Collection and utilizing the file you created in step 2 -
  - stsadm -o restore -url http://harvey:56001 -filename D:\TOP\ProductionToSandBoxTransfer\March-3-2009-Backup.bak -overwrite
- Ensure the restore completed successfully. Your result should look something like this:
Login and test that the application is healthy
Finally, if you have any customizations to perform, such as modification of the Quick Launch or Top Link Bar (hard coded URL references to the Production Site), be sure to make those now. As well, we always recommend setting the 'Theme' for the Sandbox site to a different colour scheme. This is a simple solution for ensuring that you know when you are working in the Sandbox and when you are working in production (I often go for the 'lime green' look, as it is especially eye catching and ugly).
- To change the theme to Lime Green
  - Login to the Sandbox Site
  - Choose Site Actions, Site Settings
  - Choose Site Theme, under Galleries
  - Select the Verdant Theme and click Apply
Repeat Step 5 for any remaining sub sites (For example our test site has Manufacturing and Quality Assurance Sites)

~~~~~~~~~~~~~~~~~~~~~~

Save SharePoint List as Template (with Content) maxes out at 10MB – But I want more…

I'm often shuttling around content that a client wanted in a new location and sometimes, Saving a SharePoint list as a template (with content) fits the bill nicely. But with a (default) 10MB limit, this can be quite obtrusive. Thankfully, this can be modified (up to a maximum of 500MB) with the following syntax (note that this applies to List AND Site Template saves.

Note: when you try to save a list as a template with content that exceeds the default of 10MB, you'll get this…
The list is too large to save as a template. The size of a template cannot exceed 10485760 bytes

How to increase the List (and Site) save as Template limit

To increase the maximum size, simply run the following stsadm command (from the C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN directory) replacing the propertyvalue to the new maximum size (in bytes). Note, in this example, we are changing it from 10MB to roughly 100MB:

stsadm -o setproperty -propertyname max-template-document-size -propertyvalue 100000000

~~~~~~~~~~~~~~~~~~~~~~

29 Sept 2010

How to Change Windows XP Version Between Retail, OEM and Volume License Channel

Each piece of Windows XP CD disc media or ISO image has been created for specific channel of distributions, namely retail, OEM or volume licensing. Each channel has specific installation CD and product key or CD key that required to register and activate the installed system. Activation with product serial keys from other channel version are simply not accepted, causing end-user to encounter problem when installation as a CD-key is not accepted even though it’s genuine, valid and correct.

The main problem is that not many people may be aware there is difference between various Windows XP media and the Windows XP product key that they’re having, especially users who download Windows XP images (popularly in ISO, IMG or BIN format) from Internet through file sharing sites or BT (BitTorrent) torrents. These images may not be labeled properly by indicating it’s Windows XP retail, OEM or volume licensing version. Besides, the downloaded image is mostly for Windows XP VL edition, and is not suitable for OEM product key, which pasted on COA sticker on PC. Even for IT professionals who legitmatelly download Windows XP and obtain serial numbers from MSDN or TechNet subscriptions, the ISO images and product keys may get mixed up between OEM, retail or volume license (VL) version if not been labeled or managed properly.

For users who have an incorrect edition of Windows XP CD or have installed an incorrect version of Windows XP, here are two tricks or hacks to change a live version of Windows XP installation, and change the version of Windows XP installation files. Why? Well, because end-user cannot change their product key easily, that’s why the only possible way to properly activate is to change the channel version of Windows XP.

How to Change the Distribution Channel Version of Existing Windows XP Installation

Boot up the computer

using the CD of the Windows XP edition (retail, OEM or volume licensing) that user wants to upgrade or convert the existing installation

to. Note: User may have to change the boot device priority or sequence in BIOS.
Windows XP setup wizard will launch and ask user to setup Windows XP, press Enter. Note: Do not press R or select the option “To repair a Windows XP installation using the Recovery Console, press R” option.
Accept the License Agreement.
Then, select the Windows XP installation you want to repair (change the channel) from the list and press R to start the repair process.
Setup will copy some files.
Reboot the computer.
Windows XP installation is now properly changed for retail, OEM or volume license according to the version of CD been used.

How to Change the Distribution Channel Version of A Windows XP CD

Tip: A more easier way is probably to download a new Windows XP with SP3 ISO image.

Note: This step can be used to check or verify the channel version of a Windows XP CD or image too. And it does not convert CD or image to royalty OEM Windows XP, which requires some OEM files to be existed.

Copy all content of Windows XP CD to hard disk drive, or extract Windows XP disc image to a folder.
Open the file \i386\setupp.ini in any text editor such as Notepad.
Inside the setupp.ini, there is a “Pid” parameter with [Pid] header. The Pid variable consists of 2 parts. The first 5 digits is Microsoft product code (MPC) which determines the version of Windows XP that will be installed, the last 3 digits is channel ID that determines which CD-keys or product keys that the installation wizard will accept. Some example of standard combination for Pid for various editions of Windows XP: Windows XP RTM
Retail: 51882335 (Retail edition accepting Retail CD keys)
Volume License: 51883270 (Volume License edition accepting Volume License keys or VLK)
OEM: 82503OEM (OEM edition accepting OEM keys or COA keys)
Windows XP SP2
Retail: 55274335
Volume License: 55274270
OEM: 55277OEM
Windows XP SP3
Retail: 76487335
Volume License: 76487270
OEM: 76487OEM
The first 5 digits of Pid is normally stayed the same for same version of Windows XP (i.e. RTM, SP1, SP2 or SP3). Thus, only the last 3 digits of Pid needs to be modified according to example above. Generally, channel ID for retail is 335, OEM is OEM, and volume licensing is 270.
Use nLite or other disc imaging program to re-create or re-burn the modified Windows XP installation disc media or image.

Note: Newer Windows XP discs may check whether the CD’s volume label matches the type of CD too. In this case, the wrong volume label may still render the disc unworkable. Here’s a brief list of known English version of Windows XP CD volume labels.

XP Home and Professional Combo = WXPHFPP_EN

XP Home Retail = WXHFPP_EN
XP Home Retail with SP1 = XRMHFPP_EN
XP Home Retail with SP1a = X1AHFPP_EN
XP Home Retail with SP2 = VRMHFPP_EN
XP Home Upgrade = WXHCCP_EN
XP Home Upgrade with SP1 = XRMHCCP_EN
XP Home Upgrade with SP1a = X1AHCCP_EN
XP Home Upgrade with SP2 = VRMHCCP_EN
XP Home OEM = WXHOEM_EN
XP Home OEM with SP1 = XRMHOEM_EN
XP Home OEM with SP1a = X1AHOEM_EN
XP Home OEM with SP2 = VRMHOEM_EN
XP Home Volume = WXHVOL_EN
XP Home Volume with SP1 = XRMHVOL_EN
XP Home Volume with SP1a = X1AHVOL_EN
XP Home Volume with SP2 = VRMHVOL_EN

XP Professional Retail = WXPFPP_EN
XP Professional Retail with SP1 = XRMPFPP_EN
XP Professional Retail with SP1a = X1APFPP_EN
XP Professional Retail with SP2 = VRMPFPP_EN
XP Professional Upgrade = WXPCCP_EN
XP Professional Upgrade with SP1 = XRMPCCP_EN
XP Professional Upgrade with SP1a = X1APCCP_EN
XP Professional Upgrade with SP2 = VRMPCCP_EN
XP Professional OEM = WXPOEM_EN
XP Professional OEM with SP1 = XRMPOEM_EN
XP Professional OEM with SP1a = X1APOEM_EN
XP Professional OEM with SP2 = VRMPOEM_EN
XP Professional Volume = WXPVOL_EN
XP Professional Volume with SP1 = XRMPVOL_EN
XP Professional Volume with SP1a = X1APVOL_EN
XP Professional Volume with SP2 = VRMPVOL_EN
XP Professional Tablet PC with SP1 Disc1 = XRMPFPP_EN
XP Professional Tablet PC with SP1a Disc1 = X1APFPP_EN
XP Professional Tablet PC with SP2 Disc1 = VRMPFPP_EN
XP Professional MSDN = WXPFPP_EN
XP Professional MSDN with SP1 = XRMPFPP_EN
XP Professional MSDN with SP1a = X1APFPP_EN
XP Professional MSDN with SP2 = VRMPFPP_EN
XP Professional Evaluation = WXPEVL_EN

http://www.mydigitallife.info/2009/08/16/how-to-change-windows-xp-version-between-retail-oem-and-volume-license-channel/

Flan

Nguyên liệu
10 trứng hột gà
1 lon sữa đặc có đường
Đường 20g

Chuẩn bị
Xửng hấp
Khuôn để hấp bánh

Cách làm
- Đập trứng lấy 4 lòng đỏ và 6 trứng vừa lòng đỏ + lòng trắng vào ray. Ray lòng đỏ và trắng vào 1 cái tô.
- Sữa đặc + 1 lương nước đúng bằng số lượng sữa hòa vào tô trứng vừa ray. Quậy đều.
- Cho đường + 1 ít nước vào khuôn hấp bánh quậy cho tan đường và đặt lên lò để làm caramen. Chờ cho có màu vàng của đường sủi bọt thì quậy nhanh cho đến khi nào đạt được màu vừa ý rồi nhấc xuống để nguội.
- Cho tô trứng + sữa vào khuôn và hấp cách thủy (nhớ để lửa vừa và để hở nắp) khoảng 15-20 phút hoặc nướng ở 350 độ F từ 20-30 phút cho tới khi đặc bánh.

Bitterbuds