woo!!! are you already upgrade your sharepoint server up to SP 2? if not please act faster!!! Microsoft going to stop the support for SP1 soon. http://support.microsoft.com/lifecycle/?p1=12200Windows SharePoint Services 3.0 Service Pack 1 Retired at 13/07/2010
I have some blog to share about the SP2 installation step at here, feel free to have a look. or you can just do search over internet than you will see a lot people share on this :) . If you environment not really have a lot customization then you will easy for the upgrade :)
keep track and sharing on my sharepoint knowledge :) nice to meet you all
which country user step here?
Tag Cloud
MOSS
(47)
SharePoint 2007
(37)
SharePoint 2013
(31)
SharePoint 2010
(23)
MOSS admin
(17)
PowerShell
(17)
admin
(17)
developer
(16)
List
(15)
WSS
(14)
sql query
(14)
MOSS SP2
(13)
end user
(11)
scripting
(11)
wss V3
(11)
permission
(10)
sql
(9)
Moss issue
(8)
search
(8)
database
(7)
RBS
(6)
Service Pack
(6)
reportadmin
(6)
workflow
(6)
CU
(5)
Excel
(5)
Patch
(5)
client object model
(5)
Client Code
(4)
Command
(4)
Cumulative Updates
(4)
IIS
(4)
SharePoint 2019
(4)
SharePoint designer
(4)
office 365
(4)
stsadm
(4)
user porfile
(4)
ASP.NET
(3)
Content Database
(3)
Groove
(3)
Host Named Site Collections (HNSC)
(3)
SharePoint 2016
(3)
Tutorial
(3)
alert
(3)
authentication
(3)
batch file
(3)
codeplex
(3)
domain
(3)
error
(3)
incomming email
(3)
issue
(3)
restore
(3)
upload
(3)
Caching
(2)
DocAve 6
(2)
Folder
(2)
Index
(2)
Internet
(2)
My Site Cleanup Job
(2)
My Sites
(2)
News
(2)
People Picker
(2)
Share Document
(2)
SharePoint admin
(2)
View
(2)
Web Development with ASP.NET
(2)
add user
(2)
audit
(2)
coding
(2)
column
(2)
deploy solution
(2)
download
(2)
enumsites
(2)
exam
(2)
export
(2)
june CU
(2)
load balance
(2)
mySites
(2)
network
(2)
orphan site
(2)
performance
(2)
profile
(2)
project server
(2)
query
(2)
security
(2)
server admin
(2)
theme
(2)
timer job
(2)
training
(2)
web master
(2)
web.config
(2)
wsp
(2)
70-346
(1)
70-630
(1)
AAM
(1)
Anonymous
(1)
Approval
(1)
AvePoint
(1)
Cerificate
(1)
Consultants
(1)
Content Deployment
(1)
Content Type
(1)
DOS
(1)
Document Library
(1)
Drive Sapce
(1)
Excel Services
(1)
Export to Excel
(1)
Feature
(1)
GAC
(1)
Get-SPContentDatabase
(1)
Get-WmiObject
(1)
HTML calculated column
(1)
ISA2006
(1)
IT Knowledge
(1)
ITIL
(1)
Install
(1)
Link
(1)
MCTS
(1)
Macro
(1)
Masking
(1)
Migration
(1)
NLBS
(1)
Nintex
(1)
Office
(1)
Open with Explorer
(1)
ROIScan.vbs
(1)
Reporting Services
(1)
SPDisposeCheck.exe
(1)
SQL Instance name
(1)
SSRS
(1)
Sandbox
(1)
SharePoint Online
(1)
SharePoint farm
(1)
Shared Services Administration
(1)
Site Collection Owner
(1)
Site template
(1)
Skype for business
(1)
Steelhead
(1)
Teams
(1)
URLSCAN
(1)
VLOOKUP
(1)
WSS SP2
(1)
XCOPY
(1)
abnormal incident
(1)
admi
(1)
app
(1)
application pool
(1)
aspx
(1)
availabilty
(1)
backup
(1)
binding
(1)
blob
(1)
branding sharepoint
(1)
cache
(1)
calendar
(1)
change password
(1)
connection
(1)
copy file
(1)
counter
(1)
crawl
(1)
custom list
(1)
domain security group
(1)
event
(1)
excel 2013
(1)
facebook
(1)
filter
(1)
fun
(1)
group
(1)
iis log
(1)
import
(1)
import list
(1)
improment
(1)
interview
(1)
keberos
(1)
licensing
(1)
log in
(1)
metada
(1)
migrate
(1)
mossrap
(1)
notepad++
(1)
onedrive for business
(1)
operation
(1)
owa
(1)
process
(1)
publishing feature
(1)
resource
(1)
send email
(1)
size
(1)
sps2003
(1)
sql201
(1)
sql2012
(1)
sub sites
(1)
system
(1)
table
(1)
task list
(1)
today date
(1)
trial
(1)
vbs
(1)
video
(1)
web part
(1)
web server
(1)
widget
(1)
windows 2008
(1)
windows 2012 R2
(1)
windows Azura
(1)
windows account
(1)
windows2012
(1)
wmi
(1)
Showing posts with label Service Pack. Show all posts
Showing posts with label Service Pack. Show all posts
Wednesday, March 17, 2010
Thursday, July 30, 2009
STOP!!! to deploy MOSS SP2 and June CU plan for Project server 2007
Look like the MOSS SP2 will cause some problem for the PWA, and the June CU is not really help on this. So decide to wait for August CU to see this will help or not .
Due to the testing is done by other group, so i have no detail about the problem of the PWA corruption. Maybe you interested to try on your environment and let me know? :)
Due to the testing is done by other group, so i have no detail about the problem of the PWA corruption. Maybe you interested to try on your environment and let me know? :)
Thursday, June 25, 2009
Hotfix for MOSS SP2 issue
Microsoft has released a fix for the SP2 problem that reverts the license into a Trial version after installing Service Pack 2.
More details can be found in the following KB article:
971620 - When you install the 2007 Microsoft Office servers Service Pack 2, the product expiration date is activated incorrectly
As the link to the fix binaries in the KB are currently broken here are the correct download locations:
Personally think manually is simple, what do you guys think? let discuss hereThursday, June 4, 2009
How to upgrade to SharePoint 2007 SP2 - Step by Step
i have found out one web sites is very detail in the MOSS SP2 installation step , so here is the websites to shared with you all.
http://blogs.architectingconnectedsystems.com/blogs/cjg/archive/2009/05/10/How-to-upgrade-to-SharePoint-2007-SP2-_2D00_-Step-by-Step.aspx
if you are deploying to MOSS larger farm (have minimum 2 web front end servers with NLBS) , you need to take care on the post step.
that mean after you install the sp2, you are going to run the psconfig wizard right? For large farm you need to run all wizad for web front end at the same time.
the step as below:
Run the wizard start from Node A , until the step 2/9 task will prompt up the button to click ok , you need to stop here and go to node B start run the wizard, until the 2/9 step then you go to node C to do the same.
when all the node is at same step then only you get back to Node A click ok to continue let the wizard running until complete then continue for other Node. (one time run for one node only!!)
http://blogs.architectingconnectedsystems.com/blogs/cjg/archive/2009/05/10/How-to-upgrade-to-SharePoint-2007-SP2-_2D00_-Step-by-Step.aspx
if you are deploying to MOSS larger farm (have minimum 2 web front end servers with NLBS) , you need to take care on the post step.
that mean after you install the sp2, you are going to run the psconfig wizard right? For large farm you need to run all wizad for web front end at the same time.
the step as below:
Run the wizard start from Node A , until the step 2/9 task will prompt up the button to click ok , you need to stop here and go to node B start run the wizard, until the 2/9 step then you go to node C to do the same.
when all the node is at same step then only you get back to Node A click ok to continue let the wizard running until complete then continue for other Node. (one time run for one node only!!)
Sunday, May 24, 2009
Bug for MOSS SP2 !!!
What is the bug ?
During the installation of SP2, a product expiration date is improperly activated. This means SharePoint will expire as though it was a trial installation 180 days after SP2 is deployed. The activation of the expiration date will not affect the normal function of SharePoint up until the expiration date passes. Furthermore, product expiration 180 days after SP2 installation will not affect customer’s data, configuration or application code but will render SharePoint inaccessible for end-users.
Which products are affected by this?
Applying Service Pack 2 to any of the following products will result in this issue: Office SharePoint Server 2007, Project Server 2007, Form Server 2007, Search Server 2008 and Search Server 2008 Express.
Windows SharePoint Services 3.0 is not affected by this issue.
What can I do to fix it?
To work around this issue customers will need to re-enter their Product ID numbers (PID) on the Convert License Type page in Central Administration. Please see this KB article for detailed steps.
More information here :
http://blogs.msdn.com/sharepoint/archive/2009/05/21/attention-important-information-on-service-pack-2.aspx
http://blogs.msdn.com/brismith/archive/2009/05/20/project-server-2007-license-type-set-to-trial-after-loading-office-server-service-pack-2-sp2.aspx
During the installation of SP2, a product expiration date is improperly activated. This means SharePoint will expire as though it was a trial installation 180 days after SP2 is deployed. The activation of the expiration date will not affect the normal function of SharePoint up until the expiration date passes. Furthermore, product expiration 180 days after SP2 installation will not affect customer’s data, configuration or application code but will render SharePoint inaccessible for end-users.
Which products are affected by this?
Applying Service Pack 2 to any of the following products will result in this issue: Office SharePoint Server 2007, Project Server 2007, Form Server 2007, Search Server 2008 and Search Server 2008 Express.
Windows SharePoint Services 3.0 is not affected by this issue.
What can I do to fix it?
To work around this issue customers will need to re-enter their Product ID numbers (PID) on the Convert License Type page in Central Administration. Please see this KB article for detailed steps.
More information here :
http://blogs.msdn.com/sharepoint/archive/2009/05/21/attention-important-information-on-service-pack-2.aspx
http://blogs.msdn.com/brismith/archive/2009/05/20/project-server-2007-license-type-set-to-trial-after-loading-office-server-service-pack-2-sp2.aspx
Tuesday, May 12, 2009
WSS & MOSS SP2 is Avaiable - April 2009
yeah... this round i have involved on WSS & MOSS SP2 deployment for our environment , so the first step i have do is (Guess what is my first step ??) .... As usual as a engineer the first step is google it , ha ha..see what SP2 is talking about.
After google around then get to understand what is going on but for the detail to install i have some doubt about it.. example, what is the prequest if my system not yet SP1 should i update to SP1 before go to SP2...and some other doubt.
At last i get the MS sharepoint team blog about the SP2 , that is very good information to start for SP2 deploment,Announcing Service Pack 2 for Office SharePoint Server 2007 and Windows SharePoint Services 3.0
some information from the blog:
FAQ
Q: Can I install SP2 on RTM? Can I install SP2 on RTM + SP1? Can I install SP2 on RTM + SP1 + IU? Can I insall SP2 on RTM + SP1 + some CU?
A: All yes. SP2 can be installed directly on any build before Febrary 2009. For CU releases after SP2, we suggest you install SP2 first, then apply those CU packages.
Q: Do I need to run psconfig after the install of every package?
A: No, apply all the packages, then run psconfig once. In this way the database will only be updated once, to the newest version. Otherwise it would be updated several times, which is a waste of time.
Q: Do I need to run psconfig on every machine in the farm? I already run it on one of the machines and the database is already updated.
A: Yes. Although database is already updated. The files on each servers needed to be set permissions using psconfig. Since the database is already updated, the process would be much faster.
Q: Will Windows Server 2008 SP2 and WIndows Server 2008 R2 be supported?
A: Yes, they will be supported on their release
Q: Will there be a MOSS slipstream build?
A: So far there is no plan to create a MOSS slipstream build. Customers can refer to the slipstream guide on TechNet mentioned earlier in the blog to create their own build based on their needs.
Look like is easy for the service pack deployment, but the more complicated step is.... the process for deployment.. ha ha ha.. need to ready the document , get the control board to approve and before this need to do testing on lab, QA...then only go for production.
not sure when we can have the faster way for service pack?? ha ha ha..why microsoft always have service pack...cannot have the perfect product before RTM ?? maybe human is too complicated ... too much combination then cause the error...hi hi.. why have no AI to auto correct the bug??
After google around then get to understand what is going on but for the detail to install i have some doubt about it.. example, what is the prequest if my system not yet SP1 should i update to SP1 before go to SP2...and some other doubt.
At last i get the MS sharepoint team blog about the SP2 , that is very good information to start for SP2 deploment,Announcing Service Pack 2 for Office SharePoint Server 2007 and Windows SharePoint Services 3.0
some information from the blog:
FAQ
Q: Can I install SP2 on RTM? Can I install SP2 on RTM + SP1? Can I install SP2 on RTM + SP1 + IU? Can I insall SP2 on RTM + SP1 + some CU?
A: All yes. SP2 can be installed directly on any build before Febrary 2009. For CU releases after SP2, we suggest you install SP2 first, then apply those CU packages.
Q: Do I need to run psconfig after the install of every package?
A: No, apply all the packages, then run psconfig once. In this way the database will only be updated once, to the newest version. Otherwise it would be updated several times, which is a waste of time.
Q: Do I need to run psconfig on every machine in the farm? I already run it on one of the machines and the database is already updated.
A: Yes. Although database is already updated. The files on each servers needed to be set permissions using psconfig. Since the database is already updated, the process would be much faster.
Q: Will Windows Server 2008 SP2 and WIndows Server 2008 R2 be supported?
A: Yes, they will be supported on their release
Q: Will there be a MOSS slipstream build?
A: So far there is no plan to create a MOSS slipstream build. Customers can refer to the slipstream guide on TechNet mentioned earlier in the blog to create their own build based on their needs.
Look like is easy for the service pack deployment, but the more complicated step is.... the process for deployment.. ha ha ha.. need to ready the document , get the control board to approve and before this need to do testing on lab, QA...then only go for production.
not sure when we can have the faster way for service pack?? ha ha ha..why microsoft always have service pack...cannot have the perfect product before RTM ?? maybe human is too complicated ... too much combination then cause the error...hi hi.. why have no AI to auto correct the bug??
Subscribe to:
Posts (Atom)